Oracle ACE Pro
Oracle Solution Architect
Oracle E-Business Suite
Oracle Cloud Infrastructure
Oracle Fusion Middleware
Oracle Database Administration
Oracle Weblogic Administration
Oracle ACE Pro
Oracle Solution Architect
Oracle E-Business Suite
Oracle Cloud Infrastructure
Oracle Fusion Middleware
Oracle Database Administration
Oracle Weblogic Administration
Step 1. First, Check MEMBER present in Standby Database.
SQL> select member from v$logfile;
MEMBER
———————————-
E:\STANDBYLOGS\REDO03.LOG
E:\STANDBYLOGS\REDO02.LOG
E:\STANDBYLOGS\REDO01.LOG
Step 2. Cancel the recovery Process.
SQL> alter database recover managed standby database cancel;
Step 3. Check the standby_file_management parameter and set the parameter to MANUAL.
SQL> show parameter standby_file_management
NAME TYPE VALUE
———————————— ———– ——
standby_file_management string AUTO
SQL> alter system set standby_file_management=manual scope=both;
SQL> show parameter standby_file_standby_file_management;
NAME TYPE VALUE
———————————— ———– ——
standby_file_management string MANUAL
Step 4. Add Redo Logfiles in Standby Database.
SQL> alter database add logfile group 4 ‘E:\STANDBYLOGS\REDO04.LOG’ size 250M;
SQL> alter database add logfile group 5 ‘E:\STANDBYLOGS\REDO05.LOG’ size 250M;
SQL> alter database add logfile group 6 ‘E:\STANDBYLOGS\REDO06.LOG’ size 250M;
SQL> alter database add standby logfile group 7 ‘E:\STANDBYLOGS\STDREDO07.LOG’ size 250M;
SQL> alter database add standby logfile group 8 ‘E:\STANDBYLOGS\STDREDO08.LOG’ size 250M;
SQL> alter database add standby logfile group 9 ‘E:\STANDBYLOGS\STdREDO09.LOG’ size 250M;
SQL> alter database add standby logfile group 10 ‘E:\STANDBYLOGS\STdREDO10.LOG’ size 250M;
Step 5. Check the Redo Logfiles.
SQL> col members for 999999999
SQL> set lines 120 pages 1000
SQL> select group#,members,status from v$log;
GROUP# MEMBERS STATUS
———- ———- —————-
1 1 CLEARING
2 1 CLEARING
3 1 CLEARING
4 1 UNUSED
5 1 CLEARING_CURRENT
6 1 UNUSED
SQL> select member from v$logfile;
MEMBER
————————
E:\STANDBYLOGS\REDO03.LOG
E:\STANDBYLOGS\REDO02.LOG
E:\STANDBYLOGS\REDO01.LOG
E:\STANDBYLOGS\REDO04.LOG
E:\STANDBYLOGS\REDO05.LOG
E:\STANDBYLOGS\REDO06.LOG
E:\STANDBYLOGS\STDREDO07.LOG
E:\STANDBYLOGS\STDREDO08.LOG
E:\STANDBYLOGS\STDREDO09.LOG
E:\STANDBYLOGS\STDREDO10.LOG
10 rows selected.
Step 6. Check the standby_file_management parameter and set the parameter to AUTO.
SQL> alter system set standby_file_management=auto scope=both;
Step 7. Finally, Activate the Recovery Process.
SQL> alter database recover managed standby database disconnect from session;
Step 1. First, Cancel the Standby Recovery Process.
SQL> alter database recover managed standby database cancel;
Step 2. Check the standby_file_management parameter and set the parameter to MANUAL.
SQL> alter system set standby_file_management=manual scope=both;
Step 3. Check the status of the Logfiles Before Dropping them.
SQL> select group#,status from v$log;
GROUP# STATUS
———- —————-
1 CLEARING
2 CLEARING
3 CLEARING
4 UNUSED
5 CLEARING_CURRENT
6 UNUSED
6 rows selected.
NOTE: If the status is CLEARING or CURRENT_CLEARING or ACTIVE sync the logfiles with the primary. If you proceed without sync then the following error occurs.
SQL> alter database drop logfile group 1;
alter database drop logfile group 1
ERROR at line 1:
ORA-01156: recovery in progress may need access to files
3A. To sync the logfiles issue the following command.,
SQL> alter database clear logfile group 1;
SQL> alter database clear logfile group 2;
SQL> alter database clear logfile group 3;
3B. Check the status of the logfiles.
SQL> select group#, status from v$log;
GROUP# STATUS
———- —————-
1 UNUSED
2 UNUSED
3 UNUSED
4 UNUSED
5 CLEARING_CURRENT
6 UNUSED
6 rows selected.
3C. Drop the Logfiles accordingly.
SQL> alter database drop logfile group 1;
SQL> alter database drop logfile group 2;
SQL> alter database drop logfile group 3;
3D. Check the status of logfiles.
SQL> select group#, status from v$log;
GROUP# STATUS
———- —————-
4 UNUSED
5 CLEARING_CURRENT
6 UNUSED
SQL> select group#, members, status from v$log;
GROUP# MEMBERS STATUS
———- ———- —————-
4 1 UNUSED
5 1 CLEARING_CURRENT
6 1 UNUSED
Step 4. Check the standby_file_management parameter and set the parameter to AUTO.
SQL> alter system set standby_file_management=auto scope=both;
Step 5. Activate the Recovery Process.
SQL> alter database recover managed standby database disconnect from session;
Managing the Cluster |
|
starting | /etc/init.d/init.crs start
crsctl start crs |
stopping | /etc/init.d/init.crs stop
crsctl stop crs |
enable/disable at boot time | /etc/init.d/init.crs enable /etc/init.d/init.crs disable crsctl enable crs |
Managing the database configuration with SRVCTL |
|
start all instances | srvctl start database -d <database> -o <option>
Note: starts listeners if not already running, you can use the -o option to specify startup/shutdown options force |
stop all instances | srvctl stop database -d <database> -o <option>
Note: the listeners are not stopped, you can use the -o option to specify startup/shutdown options immediate |
start/stop particular instance | srvctl [start|stop] database -d <database> -i <instance>,<instance> |
display the registered databases | srvctl config database |
status | srvctl status database -d <database> srvctl status instance -d <database> -i <instance>,<instance> srvctl status service -d <database> srvctl status nodeapps -n <node> srvctl status asm -n <node> |
stopping/starting | srvctl stop database -d <database> srvctl stop instance -d <database> -i <instance>,<instance> srvctl stop service -d <database> -s <service>,<service> -i <instance>,<instance> srvctl stop nodeapps -n <node> srvctl stop asm -n <node> srvctl start database -d <database> |
adding/removing | srvctl add database -d <database> -o <oracle_home> srvctl add instance -d <database> -i <instance> -n <node> srvctl add service -d <database> -s <service> -r <preferred_list> srvctl add nodeapps -n <node> -o <oracle_home> -A <name|ip>/network srvctl add asm -n <node> -i <asm_instance> -o <oracle_home> srvctl remove database -d <database> -o <oracle_home> |
OCR utilities |
|
log file | $ORA_HOME/log/<hostname>/client/ocrconfig_<pid>.log |
checking | ocrcheck
Note: will return the OCR version, total space allocated, space used, free space, location of each device and the result of the integrity check |
dump contents | ocrdump -backupfile <file>
Note: by default it dumps the contents into a file named OCRDUMP in the current directory |
export/import | ocrconfig -export <file>
ocrconfig -restore <file> |
backup/restore | # show backups ocrconfig -showbackup # to change the location of the backup, you can even specify a ASM disk # perform a backup, will use the location specified by the -backuploc location # perform a restore # delete a backup Note: there are many more option so see the ocrconfig man page |
add/remove/replace | ## add/relocate the ocrmirror file to the specified location ocrconfig -replace ocrmirror ‘/ocfs2/ocr2.dbf’ ## relocate an existing OCR file ## remove the OCR or OCRMirror file |
OPROCd |
Process Monitor | provides basic cluster integrity services |
EVMd |
Event Management | spawns a child process event logger and generates callouts |
OCSSd |
Cluster Synchronization Services | basic node membership, group services, basic locking |
CRSd |
Cluster Ready Services | resource monitoring, failover and node recovery |
LMSn |
Lock Manager Server process – GCS | this is the cache fusion part, it handles the consistent copies of blocks that are tranferred between instances. It receives requests from LMD to perform lock requests. I rools back any uncommitted transactions. There can be upto ten LMS processes running and can be started dynamically if demand requires it. they manage lock manager service requests for GCS resources and send them to a service queue to be handled by the LMSn process. It also handles global deadlock detection and monitors for lock conversion timeouts. |
LMON |
Lock Monitor Process – GES | this process manages the GES, it maintains consistency of GCS memory in case of process death. It is also responsible for cluster reconfiguration and locks reconfiguration (node joining or leaving), it checks for instance deaths and listens for local messaging. A detailed log file is created that tracks any reconfigurations that have happened. |
LMD |
Lock Manager Daemon – GES | this manages the enqueue manager service requests for the GCS. It also handles deadlock detention and remote resource requests from other instances. |
LCK0 |
Lock Process – GES | manages instance resource requests and cross-instance call operations for shared resources. It builds a list of invalid lock elements and validates lock elements during recovery. |
DIAG |
Diagnostic Daemon | This is a lightweight process, it uses the DIAG framework to monitor the healt of the cluster. It captures information for later diagnosis in the event of failures. It will perform any neccessary recovery if an operational hang is detected. |
All Rights Reserved