Grep Embedded_SYSTEM_PASS= install/conf/.db.confįor example if it has Embedded_SYSTEM_PASS=90f8006cd6bc0dde, then: STANDBY = primstdb DB_TO_BE_DROPPED = primedb SYSTEM_PASSWD = use Step 5 ORACLE_BASE = /orahome/oracle ORACLE_USER = oracle ARCHIVED_LOG_LOCATION = output of ‘show parameter log_archive_dest_1 &rsquo ORACLE_DATA_FILES_LOCATION = output of ‘select name from v$datafile &rsquo REDO_LOG_LOCATION = output of ‘select member from v$logfile ’ Use these parameters and run the script mentioned in Step 3. Scenario 2: HA2 is active and needs to rebuild standby database on HA1. REDO_LOG_LOCATION = output of ‘select member from v$logfile ’ ORACLE_DATA_FILES_LOCATION = output of ‘select name from v$datafile &rsquo
PRIMARY = primedbĪRCHIVED_LOG_LOCATION = output of ‘show parameter log_archive_dest_1 &rsquo Make use of these parameters and run the script mentioned in Step 3. Scenario 1: HA1 is active and needs to rebuild standby database on HA2. Note: As an example it is assumed that HA1 is Primary Gateway/database and HA2 is secondary Gateway/Database Step 4. Identify any scenario with current status of your setup and proceed accordingly: Note: Script is copied under $ORACLE_BASE/standby folder and needs to run as an oracle user. Step 3. To rebuild the database, run this script in correct syntax after you identify the correct scenario described in step 4.
#Rebuild mozypro database archive
To find the archive log: SQL> show parameter log_archive_dest_1 To find the datafiles: SQL> select name from v$datafile Step 2. On Active and Standby database login as sysdba and find the directory path to the datafile and redo logs and archive log files. Note: Here = primedb or primstdb is based on primary or secondary. If, ORACLE_SID on either of Primary or Secondary Gateway is not as mentioned earlier, use this command to configure the correct SID : setenv ORACLE_SID = On Secondary Gateway/database ORACLE_SID = primdtdb On Primary Gateway/database ORACLE_SID = primedb Step 1. Verify the ORACLE_SID on both primary and secondary Gateway/databases. Root cause for database replication mostly could be network communication issue betwee Primary and Secondary Prime Central database, corrupt database or similary database related errors. SQL> select switchover_status from v$database Ĥ. Check open_mode, current_scn and switchover status on Primary and Secondary database. diag/rdbms/anadb/anadb/trace/alert_anadb.logģ. Check this database log on Primary to find any database related ORA errors: Check the network connectivity and/or latency related issues between Primary and Secondary Prime Network Gateway.Ģ. Troubleshootīefore you follow the solution you can perform basic trobleshooting steps:ġ. This results in both the primary and standby databses to either become active or standby at the same time. Prime Central GEO HA switch and/or failover/failback procedure fails when Active and Standby databses become out of sync to each other. On Secondary Gateway from oracle user: echo $ORACLE_SID -> output should be “primstdb” Problem On Primary Gateway from oracle user: echo $ORACLE_SID -> output should be “primedb” Use this command to know ORACLE_SID of primary and secondary database: Use this command to know the current mode of primary and secondary database: SQL> select open_mode from v$database ģ. Note: For all other cases, open SR with Cisco TAC to resolve database replication issue.Ģ.
Note: Prime Central Geo HA switchover fails abruptly leaving the Prime Central GEO HA system and/or database role status corrupt (both primay or both standby) and then you need to rebuild either primary or secondary depending upon last active/standby status. Use this command to know switchover_status of primary database: SQL> select switchover_status from v$database If your network is live, make sure that you understand the potential impact of any command. All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment.
#Rebuild mozypro database software
The information in this document is based on these software and hardware versions:
0 kommentar(er)
