RMAN duplicate fails to create BCT file despite fix of bug 11744544 ( RMAN-11003 ORA-19750 )

Remember http://oracle.powerbytes.nl/ever-ran-into-an-ora-19755-with-rman/ ?

RMAN duplicate fails to create BCT file despite fix of bug 11744544 !!

Bug 18371441 : RMAN DUPLICATE FAILS TO CREATE BCT FILE

Created 09-03-2014, fixed in version 12.2

ORA-00283: recovery session canceled due to errors
ORA-19755: could not open change tracking file
ORA-19750: change tracking file: '+DATA/rac2prd/changetracking/ctf.2646.835861329'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
---
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 01/23/2016 21:44:21
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
ORA-00283: recovery session canceled due to errors
RMAN-11003: failure during parse/execution of SQL statement: alter database reco
ver logfile '+DATA2/oracle/AUX/archivelog/2016_01_23/o1_mf_1_98404_urqs4ef3_.
arc'
ORA-00283: recovery session canceled due to errors
ORA-19755: could not open change tracking file
ORA-19750: change tracking file: '+DATA/rac2prd/changetracking/ctf.2646.835861329'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory

Solve with Patch 18371441

A workaround would be to disable change tracking before duplicating.

Ever ran into an ORA-19755 with RMAN?

Ever ran into an ORA-19755 with RMAN duplicate from target? When your source database uses block change tracking?

Try patch 11744544; it fixes the bug which could might cause block change tracking recreation fail in combination with OMF newnames.

A workaround would be to disable change tracking before duplicating.

 

 

Backup recovery area (FRA) without a tape device

Backup to disk

RMAN> run {
allocate channel d1 type disk format='/tmp/%U';
backup tablespace sysaux;
}

Backup to a fake tape

The fake tape library will call the MML APIs, essentially similar to an MML backup, but will place the file on disk (RMAN disksbt library emulates a SBT library). It cannot be used for production backups but can be used for verification purposes such as these:

RMAN> run {
allocate channel t1 type 'SBT' PARMS 'SBT_LIBRARY=oracle.disksbt,ENV=(BACKUP_DIR=/tmp)';
backup tablespace sysaux;
}

The fake tape backup comes in handy when one wants to backup the recovery area; the ‘backup recovery area’ command only works with SBT channels. FRA backup to disk does not work.

EM agent; ERROR-400 Data will be rejected for upload, bla bla

Darn, I had it also, the agent in GRID control in not uploading to the OMS and there is just too much to upload. One can change em.loader.maxDirectLoadFileSz but the following can be done to (you will lose some info but hey..)

Now fix it:

cd $AGENT_HOME/sysman/emd
rm lastupld.xml agntstmp.txt
cd $AGENT_HOME/sysman/emd/upload
rm *.*
cd $AGENT_HOME/sysman/emd/state
rm *.*

No need to remove storage directory under $AGENT_HOME/sysman/emd/state

cd $AGENT_HOME/bin
./emctl start agent
./emctl status agent

(source: http://gavinsoorma.wordpress.com/2009/12/03/how-to-manually-clear-em-grid-control-alerts/)