5, Cancel event setting on the catalog DB side. SQL> alter system set events '10046 trace name context off'; SQL> alter system set events '6502 trace name errorstack off'; The file generated is as follows: ■ Target DB side: <SID> _ora _ <SPID> _rman _ 10046.trc output to user...
RMAN> debug all level = 15 2, With the RMAN connection of the target DB held, the setting of the catalog DB SQL> alter system set events '10046 trace name context forever, level 12'; SQL> alter system set events '6502 trace name errorstack level 3'; 3, Reproduce the error on the ...
1, setting on the server that starts the RMAN client $ Export EVENT_10928 = 1 $ Rman target <username> / <password> @ <connection descriptor> catalog <username> / <password> debug trace = / tmp / rmanDebug.trc log = / tmp / rmanLog.txt RMAN> sql "alter session set tracefile_iden...
Action: MOUNT the target database, or add the DB_NAME parameter to its INIT.ORA file and restart the instance. RMAN-06008 connected to recovery catalog database Cause: This is an informational message. Action: No action is required. RMAN-06009 using target database controlfile instead of rec...
We got issue in one of the production environment, RMAN archivelog backup was failing with following errors: kgefec: fatal error 0 kgepop: no error frame to pop to for error 603 We were using following command in rcv file to backup archivelogs: BACKUP a
Action: MOUNT the target database, or add the DB_NAME parameter to its INIT.ORA file and restart the instance. RMAN-06008 connected to recovery catalog database Cause: This is an informational message. Action: No action is required. RMAN-06009 using target database controlfile instead of rec...