The article covers consistency check before performing OPEN RESETLOGS after restoring a database using backup
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.
-
ASM
- Creating ASM Instance and diskgroups manually without DBCA
- 20 ASM Realtime | Interview Questions
- How to make a cold backup for database running on ASM ( using RMAN )
- Moving a Single Datafile from File System to ASM System (METHOD 1)
- Moving a Single Datafile from File System to ASM System (METHOD 2)
- Things to consider while adding new disk/ Rebalancing existing Disk Group
-
Dataguard
- Dataguard Modes
- Dataguard Modes - II
- Oracle DataGuard Setup
- invalid archived log deletion policy
- recover from the Loss of a Datafile on a Standby Database ?
- MRP terminated with ORA-00600: internal error code, arguments
- Recover archive gaps in standby database - using 2 methodss
- Gap Resolution in Dataguard
- Convert Physical Standby to Snapshot Standby and Vice Versa
- Re-create Redo-logs on Standby/ Primary
- Pre-check for DataGuard switchover Process
- ORA-19815: WARNING: db_recovery_file_dest_size
- How do you purge old archivelogs which are applied on Standby DB
- Pre-check For SWITCHOVER using DG Broker
- https://oracle-dba-help.blogspot.com/2016/03/data-guard-modes.html
- ORA-01274 : RENAME THE UNKNOW FILE IN THE STANDBY DATABASE
- Database Creation in Easy 6 Steps
- Oracle Networking
- Tablespace management
- Housekeep : Quick Tips for DBA
- Health check for DB
- ORA-12537 While Connecting To Database Via Listener
- How to identify the applied patche-set of your Oracle Home
- Accessing a schema without knowing the password
- ORA-12505: TNS:listener does not currently know of SID given in connect descriptor
- Session Related Scripts
- How to check ORA Error on DB Server – Beginner Tip
- Working with Redo Logs
- Decommission of Oracle Database
- Roles in Oracle - Managing Users
- Oracle Release Number Format
- Troubleshooting Handy-Guide
- Understanding the Upgradation Process
- Query to find the session creating more redo
- Audit in Oracle
- Troubleshooting Internal Errors and Error-Look-up Tool on MOS
- Troubleshooting Issues with Undo Tablespace
- User Management
- User Management - II
- Data Pump Gets Better
- MEMORY_TARGET Parameter
- Installing PostgreSQL Server on CentOS, RHEL 6 / 7 Systems
- Creating a database in Postgres
- Initialize multiple Postgres instance on the same RHEL server
- How to stop starting of clusters while starting up services
- Setup a streaming replication
- Switchover- master server and warm standby (with streaming replication)
- All About Physical Replication and Log shipping
- PostgreSQL Upgrade and troubleshooting
- Timeline Switch issue
- Query to identify the lag in replication
- Drop table : ERROR: must be owner of relation table_name
- PgBadger
- PgCenter
- PgTune
- Internals of Toast Table
- Influencing Query Execution Plan
- Create Extension ERROR
- Find Uptime in PostgreSQL
- Set DB Timezone
- Clear RAM Cache, Buffer
- Read-Only User in Postgres
- Everything you need to know about Streaming Replication
- Ora2Pg Migrate Oracle to Postgres
- Total Page Cost
- PostgreSQL 13 - Everything you need to know
- Startup Failure - .conf file
- All About Postgres Upgrade
- Basic Guide
- Session Related Scripts
- AWR :: Beginners Guide
- All About ASH - Active Session History
- Wait Events : checkpoint busy waits or archiver busy waits
- Find sessions performing sort operations : TEMP Tablespace occupants
- Generate ADDM task and generate its report for Tuning
- Database Performance Tuning Scripts -Keep Handy
- Buffer Busy Wait
- Simulating the Deadlock
- Latches
- Steps to Schedule any RMAN Jobs In Windows Server
- ORA-01194: file 1 needs more recovery to be consistent
- Loss of Current Online Redo-Log
- RMAN "baby Steps"
- Recovery of ControlFiles
- Loss of Datafile
- Recovery from complete loss of all online redo log files
- Block Change Tracking
- RMAN Questions
- Instance Recovery
- Redundancy and Recovery window in RMAN
- Cold Backup
- Database Cloning
- Contact
- Drop Database using RMAN
- PITR to older Incarnation
Saturday 8 January 2022
Saturday 4 September 2021
Open Resetlog Failure : ORA-00392: log 1 of thread 1 is being cleared, operation not allowed
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
Monday 30 November 2020
RMAN Backup Validate
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.
Tuesday 2 October 2018
RMAN-08591: WARNING: invalid archived log deletion policy
For one of database we were getting backup failure alerts where the backup was configured on standby database.
We saw below Error messsages in backup-log :
-
[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' ---------- ----------
3. Set the "binding" Property as - MANDATORY
//This parameter controls whether the destination is mandatory or not
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
Sunday 31 December 2017
Steps to Schedule any RMAN Jobs In Windows Server
1) Weekly RMAN full backup
2) Daily Archive log backup
3) Daily incremental backup
The important steps to configure a scheduler are as follows :
First create a cmd file (command file ) in windows:
Let us create a file name week_backup.cmd using a text file editor(any editor) write the rman script to take the backup.
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;
}
Step 2.
Let us create a batch file week_backup.bat
week_backup.bat
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
1. backup_incr_1.cmd
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;
}
2. backup_incr_1.bat
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
Now, Configure the scheduler as we did above in Step 3 and simply change the Scheduler option > as ‘daily’ and timings whichever you want.
Wednesday 12 April 2017
ORA-01194: file 1 needs more recovery to be consistent
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
Viola…!!
SQL>shut immediate
And add below parameter in the pfile
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
Done . . !!