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/)

RMAN / archive backup without catalog database…

… can cause a nasty ORA-19571. Reason? You are using a control file as RMAN catalog and obviously more space is needed than available..

sql> alter system set control_file_record_keep_time=14 scope=both;

More info: Oracle’s Metalink Doc ID: 563219.1

What’s in security – October 2009

Last Thursday I read that Oracle postpones the upcoming CPU patches. They state:

There is a change in the previously announced release date of the October 2009 Critical Patch Update.

Since many Oracle customers with responsibility for deploying the Critical Patch Update within their respective organizations will be attending Oracle OpenWorld October 11-15, 2009, the October 2009 Critical Patch Update originally scheduled to be published on Tuesday, October 13th 2009, will be released on October 20th 2009.

Please note: this date change only impacts the October 2009 Critical Patch Update. As usual, Oracle will issue a pre-release announcement on the Thursday before the publication of the Critical Patch Update (Thursday, October 15th). All other aspects of the Critical Patch Update (where to find the documentation, how to download the patches, etc.) remain the same.

(More info: see Metalink

A good reason would be that there are no important patches.. aren’t there..?