SCOPE
The article covers possible solutions to resolve warnings that appear in RMAN backups due to incorrect database configurations. Continuing from my previous post on RMAN backup failure warnings, I am now addressing another situation.
Sharing knowledge is the ultimate key to gaining knowledge…
The only two things that stay with you for life are you & your knowledge...
Live while you can! Teach & inspire while you could & Smile while you have the teeth.
SCOPE
The article covers possible solutions to resolve warnings that appear in RMAN backups due to incorrect database configurations. Continuing from my previous post on RMAN backup failure warnings, I am now addressing another situation.
The article covers consistency check before performing OPEN RESETLOGS after restoring a database using backup
SCOPE
Restoring
the database using RMAN backup.
After completion of cloning to the staging environment, OPEN RESETLOGS fails with error as below.
ORA-00392: log 1 of thread 1 is being cleared, operation not allowed
Sometimes RMAN backup files might get corrupted. Sometimes disk block corruption might happen. So it is better we do validate the database backups more frequently in order to make sure it is recoverable.
[oracle@host1 log]$ dgmgrl / DGMGRL for Linux: Version 12.1.0.2.0 - 64bit Production Copyright (c) 2000, 2013, Oracle. All rights reserved. Welcome to DGMGRL, type "help" for information. Connected as SYSDG. DGMGRL> show configuration Configuration – primdb1 Protection Mode: MaxPerformance Members: primdb1 - Primary database bcpdb1 - Physical standby database Fast-Start Failover: DISABLED Configuration Status: SUCCESS (status updated 7 seconds ago)
DGMGRL> show database verbose bcpdb1 Database - bcpdb1 Role: PHYSICAL STANDBY Intended State: APPLY-ON Transport Lag: 11 minutes (computed 0 seconds ago) Apply Lag: 0 seconds (computed 0 seconds ago) Average Apply Rate: 625.00 KByte/s Active Apply Rate: 523.00 KByte/s Maximum Apply Rate: 18.62 MByte/s Real Time Query: ON Instance(s): bcpdb1
Properties:
---------- ----------Binding = 'optional' ---------- ----------
DGMGRL> edit database bcpdb1 set property Binding='mandatory'; Property "binding" updated DGMGRL> exit
Read more
Configure Streaming Replication in PostgreSQL
Installation and configure Postgres 13 on RHEL
All about Physical Replication and Log shipping in Postgres
Possible ways to recover space from deleted rows with insufficient disk space
Streaming-Replication Sync and Async, benefits of streaming replication over Log-shipping
RMAN>run{
Allocate channel ch1 type disk format '\path of taking backup_\%d_data_%U';
Backup incremental level=0 database tag=’full_backup';
Release channel ch1;
Allocate channel t1 type disk format '\ backup location \%d_ctrl_%U';
Backup current controlfile;
Release channel t1;
}
rman target sys/db1@db1 cmdfile=\Path of cmd file\week_backup.cmd <-------- you need to mention the file location we created at Step 1 above. log=E:\Path of log file\Full_DB_Backup_%date:~4,2%_%date:~7,2%_%date:~10%.log The file will be created as follows Full_DB_Backup_<Current_Date>.log
run{
allocate channel ch1 type disk format '\path of backup location_\%d_data_%U';
backup incremental level=1 database tag=Level_1_Backup';
release channel ch1;
}
rman target sys/db1@DBNAME
cmdfile=\Path of cmd file created in Step1 above\ backup_incr_1.cmd
log=E:\Logfile location\Level_1_Backup_%date:~4,2%_%date:~7,2%_%date:~10%.log
SQL> recover database; ORA-00283: recovery session cancelled due to errors ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
SQL> recover database until cancel using BACKUP CONTROLFILE; ORA-00283: recovery session cancelled due to errors
SQL>shut immediate
SQL> startup mount pfile= ‘$ORACLE_HOME/dbs/initDBNAME.ora’; ORACLE instance started. Total System Global Area 1069252608 bytes Fixed Size 2188408 bytes Variable Size 436214664 bytes Database Buffers 616562688 bytes Redo Buffers 14286848 bytes Database mounted. SQL> select name,open_mode from v$database; NAME OPEN_MODE --------- -------------------- TEST MOUNTED SQL> alter database open resetlogs; Database altered. SQL> select name,open_mode from v$database; NAME OPEN_MODE --------- -------------------- TEST READ WRITE