[Oracle] A method of investigating ora-06502 RMAN error during the same period on catalog DB

Catalog DB Resync Error:

1, setting on the server that starts the RMAN client

$ Export event_10928 = 1
$ Rman Target <username>/<password> @ <connection descriptor> Catalog <username>/<password& Gt Debug trace =/tmp/rmandebug.trc log =/Tmp/rmanlog.txt

Rman> SQL "alter session set Tracefile_identifier = ' rman-10046 '" ";
Rman> SQL "alter session SET events" 10046 Trace name Context forever, Level 12 "" "
Rman> SQL "alter session SET events" 6502 Trace name Errorstack level 3 ' ";
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 target DB side.

rman> Resync Catalog;
Rman> exit;

4, Cancel event_10928 on the server that starts the RMAN client

$ Unset event_10928

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_dump_dest

Catalog DB side:
<SID> _ora _ <SPID> TRC output to User_dump_dest

Server that started RMAN client:
/tmp/rmandebug.trc
/tmp/rmanlog.txt

Note:the information in event_10928 are output to rmanLog.txt.

[Oracle] A method of investigating ora-06502 RMAN error during the same period on catalog DB