DBA Maestro - Helpful DBA tips

  Hey Oracle DBAs! It's been a while, Oracle community! But I'm back with a helpful post. :-) Today, I faced an issue while performing an RMAN duplicate to build out a standby database (Oracle version 19.25) on an ExaCS VM. The database is 110 TB in size. I was doing an active duplicate over the WAN for 2 days. Everything was going smoothly until it reached ~94% completion... and then it FAILED!! I didn't want to risk restarting the entire RMAN duplicate process again out of concern that the same issue would occur. Here's my error: RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of Duplicate Db command at 04/10/2025 09:57:48 RMAN-05501: aborting duplication of target database RMAN-03015: error occurred in stored script Memory Script ORA-19875: multisection restore or copy not complete ...

I was trying to create an Oracle Data Guard environment (physical standby) from an Oracle database running version 12.1.0.2. The database was running an older PSU version ("Database Patch Set Update : 12.1.0.2.161018 (24006101)") to be specific. Upon trying to build the standby by using RMAN DUPLICATE with ACTIVE DATABASE, I ran into the below error: executing Memory Script Starting backup at 16-JUL-18 RMAN-03009: failure of backup command on prm1 channel at 07/16/2018 13:51:46 ORA-17629: Cannot connect to the remote database server ORA-17630: Mismatch in the remote file protocol version client 2 server 3 continuing other job steps, job failed will not be re-run released channel: prm1 released channel: prm2 released channel: prm3 released channel: prm4 released channel: prm5 released channel: stb1 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: ====================...

A client that I was supporting asked me to complete a dry run of a database restore on their newly built ODA.  Below are the steps that I performed to complete the database restore. Prerequisites: I built the RAC database using OAKCLI. I backed up the database with RMAN incremental level 0 + cumulative level 1. I dropped the database using SQLPLUS commands vs. OAKCLI as to not remove the ACFS directories for the database. 1. Startup the database instance in NOMOUNT. RMAN> startup nomount force; startup failed: ORA-01078: failure in processing system parameters ORA-01565: error in identifying file '/u02/app/oracle/oradata/datastore/.ACFS/snaps/labtest/labtest/spfilelabtest.ora' ORA-27037: unable to obtain file status Linux-x86_64 Error: 2: No such file or directory Additional information: 3 starting Oracle instance without parameter file for retrieval of spfile Oracle instance started Total System Global Area    1073741824 bytes Fixed Size ...

RMAN-05001: auxiliary file name <file_name> conflicts with a file used by the target database I ran into an issue where I was trying to clone a new copy of non-production database (using production database as the source) by leveraging the RMAN clone via active database to save me some time and work.   I ran into the error where I couldn't successfully clone the database.  I made sure that my environment, pfile, RMAN script were configured correctly.  After much time of troubleshooting, I figured out the issue. After remembering that the source database had a DG environment, it occurred to me that was what was  causing  the error.  Reason being, the source had log_file_name_convert and db_file_name_convert configured which was being "carried over" onto my auxiliary instance hence causing the error mentioned above.  So all I needed to do was simply reset those two parameters within my RMAN script (as seen below) and I was able to suc...

I encountered an issue where standby fell out of sync with primary.  When trying to place the standby in auto recovery again, I received the following error in the alert log: ORA-00600: internal error code, arguments: [3020], [41], [41955], [172008419], [], [], [], [], [], [], [], [] ORA-10567: Redo is inconsistent with data block (file# 41, block# 41955, file offset is 343695360 bytes) ORA-10564: tablespace SYSTEM ORA-01110: data file 41: '+DATA/spl1adg/datafile/system.317.766442357' ORA-10561: block type 'TRANSACTION MANAGED DATA BLOCK', data object# 15 After researching this issue in metalink, the proposed solution was to rebuild the standby.  After pondering over this for a bit, I did the following which allowed me to remedy the issue: 1. Took the datafile offline on standby. SQL> alter database datafile 41 offline drop; 2. Took fresh backup of the datafile in question on primary. RMAN> backup as backupset datafile 41; 3. Copie...

After reviewing this error in the alert log, I found that this was pertaining to one particular datafile.  What I did to resolve this issue was the following: 1. Go to the primary database and backup the datafile in question.  In this case, it was datafile #56. Recovery Manager: Release 11.2.0.1.0 - Production on Tue Dec 20 21:52:01 2011 Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved. connected to target database: POC2 (DBID=1234567890) RMAN> backup as compressed backupset datafile 56; Starting backup at 20-DEC-11 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=1492 instance=poc22 device type=DISK channel ORA_DISK_1: starting compressed full datafile backup set channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00056 name=+DATA/poc2/datafile/tg_ods.256.767919427 channel ORA_DISK_1: starting piece 1 at 20-DEC-11 channel ORA_D...

Symptoms When attempting to delete obsolete backups from RMAN using the following command: RMAN> delete obsolete;  the following error occurs: RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of delete command at 05/07/2008 22:04:21 RMAN-06091: no channel allocated for maintenance (of an appropriate type) . Cause Tape channel had not being allocated when attempt to delete obsolete backup on tape or disk. Using the following command to verify that there are backup sets on tape. RMAN> list backup;   This will show you the backup details informing you which channel device type that needs to be allocated. Solution To implement the solution, please execute the following steps: Please run the following commands to delete obsolete bac...