Oracle Catalog was not sync with Legato

Question

Dear All, My situation as following: 1. I tried to delete CFI and Volume via Legato manage console 2. I want to use RMAN utility to sync catalog with legato index, the command as below: RMAN> REPORT OBSOLETE; using target database control file instead of recovery catalog RMAN retention policy will be applied to the command RMAN retention policy is set to redundancy 1 Report of obsolete backups and copies Type Key Completion Time Filename/Handle -------------------- ------ ------------------ -------------------- Backup Set 9 12-DEC-06 Backup Piece 9 12-DEC-06 SALES_09i4no9u_1_1 Backup Set 10 12-DEC-06 Backup Piece 10 12-DEC-06 SALES_0ai4noho_1_1 And I tried to crosscheck backup command. RMAN> CROSSCHECK BACKUP DEVICE TYPE SBT; using target database control file instead of recovery catalog allocated channel: ORA_SBT_TAPE_1 channel ORA_SBT_TAPE_1: sid=146 devtype=SBT_TAPE channel ORA_SBT_TAPE_1: NMO v4.2.0.0 The system was hung... is there a way to sync catalog at no catalog database environment? Thanks for any suggestion, Dennis

ble1 · Accepted Answer

Dennis, this is more Oracle than NetWorker, but here it goes:http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup008.htm

amediratta · Answer

Oracle has commands like resync catalog, register database etc. which synchronize the catalog. Please check with your DBA for their exact usage.

sarpydog · Answer

Thanks for you reply first.

I done the command "resync catalog" sucessfully,

but the obsolete backup still exist by "list backup recoverable;" command.

I manually labeled the volume, it should no backup exist in that volume?

amediratta · Answer

Sorry,Resync catalog etc. would work for sync your database, archives etc. with RMAN catalog. Ex. - if you manually delete archives and do not resync RMAN, would search for thos archives during next backup and backup terminates.I don't think you can sync RMAN catalog with Networker indexes. Atleast I am not aware of any such situation.

dpinink_silva · Answer

I haven't seen it too. RMAN catalog is one thing, and Nw indexes are another. They work together to do backups and recoveries, but are not in sync.

sarpydog · Answer

The problem was solved, and the procedure as following:

1. Using RMAN utility to register the catalog DB again

2. Run "crosscheck backup" command

3. Run "delete obsolete"

Thanks for everybody's information,

Dennis

amediratta · Answer

True but it does not sync RMAN catalog with NW index.

ble1 · Answer

It depends how you look at it. crosscheck will use SBT channel and will mark unavailable data as expired. After that you can do delete expired to remove them from catalog.

NetWorker

Was this post helpful?