Recently at my client place I implemented RMAN script for maintenance of backups through RMAN, so that my team don’t have to use GUI to do the same.
When running the script everthing was smooth, except at the end of the script result was showing error ORA-19569 as follows:
RMAN> run
2> {
3> allocate channel c1 device type disk format ‘F:\rmanbackup\incrementalbackup\%d_DB_%u_%s_%p’;
4> delete archivelog until time ’sysdate-7′;
5> delete noprompt obsolete;
6> }
7>
using target database controlfile instead of recovery catalog
allocated channel: c1
channel c1: sid=202 devtype=DISK
deleted archive log
archive log filename=D:\ARCHIVE\BIZWIZ\ARC67474_0566156678.001 recid=106781 stamp=635438642
Deleted 2 objects
RMAN retention policy will be applied to the command
RMAN retention policy is set to […]

[Read more →]

In this blog entry let me introduce you to a new capability in Oracle 10g called Block Change Tracking, which can help DBA’s do faster incremental backups via RMAN (Recovery Manager).
Once this new capability in Oracle 10g is enabled it start recording the modified since last backup and stores the log of it in a block change tracking file.
Later while doing backup RMAN uses this file to determine which blocks are needed to be backed up?
Logically as we can see, this process improves the performance as RMAN does not have to scan whole datafile to detect which block in it […]

[Read more →]