1- One of the obsolete integrated extract was causing Rman not to delete expired archive logs. orcl:/u02/DBA/scripts ->./delete_arch.sh The Oracle base remains unchanged with value /u01/app/oracle Recovery Manager: Release 22.214.171.124.0 – Production on Fri Feb 9 15:25:15 2018 Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved. connected to target database: ORCL (DBID=1450870477) RMAN> 2> 3> 4> 5> 6> using target database control … Continue reading GoldenGate – RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process.
A quick emergency FRA clean up when archived logs are full. Continue reading ORA-00257: archiver error – FRA Clean Up emergency
RMAN command to create level 0 backup which is needed before running of incremental backup RMAN> BACKUP INCREMENTAL LEVEL 0 DATABASE; RMAN command to run level 1 backup. Level 1 backup will backup all blocks changed since most recent cumulative or differential backup. If a level 0 backup doesn’t exists, when running INCREMENTAL backup Oracle will perform a full backup. RMAN> BACKUP INCREMENTAL LEVEL 1 … Continue reading RMAN – incremental backup
There are couple of ways to determine if RMAN database is registered with a catalog. Using RMAN when you connect to RMAN catalog and try to run a RMAN command like “list backup” it will generate an error as shown below calora4db01q:/home/oracle $ rman target / catalog rmancataloguser/rmancatalogpassword@catalogdb Recovery Manager: Release 10.2.0.4.0 – Production on Sun Jul 17 08:33:42 2011 Copyright (c) 1982, 2007, Oracle. … Continue reading How to check if RMAN catalog is installed for a database?
When using VALIDATE option, Oracle will validate backup and not create backups and will not restore when this option is used. # Validate if datafile exists and have no physical or logical corruptions that would prevent RMAN from running. If “archivelog” is specified it will also check if archive logs are valid too RMAN> backup validate database archivelog all; # Validate if datafile exists and … Continue reading Using RMAN to validate backup
To move/rename current block change tracking file, one would need to restart the database. # Get current block change tracking file SQL> SELECT filename FROM v$block_change_tracking; FILENAME ——————————————————————————– /tmp/blocktracking.f # Shutdown database and start database in mount state SQL> SHUTDOWN IMMEDIATE; SQL> STARTUP MOUNT; # Rename block tracking file and SQL> ALTER DATABASE RENAME FILE ‘/tmp/blocktracking.f’ TO ‘/u01/oradata/TEST/blocktracking.f’; # Move current block tracking file through … Continue reading How to rename block change tracking file?
Backup in RMAN can be compressed when they are being created. Using the following command one can compress backup to disk or tape. The commands used to backup database remain the same. # Enable compression when creating backup to disk RMAN> configure device type disk backup type to compressed backupset; # Enable compression when creating backup to tape RMAN> configure device type sbt backup type … Continue reading RMAN – to enable compression of backupset