Introduction: The dbms_backup_restore package is really powerful. The stored procedure related to dbid setting is as follows:
Procedure nidbegin (newdbname in varchar2,
Olddbname in varchar2,
Newdbid in number,
Olddbid in number,
Dorevert in binary_integer,
Dorestart in binary_integer,
Events in number );
Procedure nidprocesscf (chgdbid out binary_integer,
Chgdbname out binary_integer );
Procedure nidprocessdf (fno in number,
Istemp in binary_integer,
Skipped out binary_integer,
Chgdbid out binary_integer,
Chgdbname out binary_integer );
Procedure nidend;
Key points during use: newdbname, olddbname, newdbid, and olddbid in nidbegin must be uppercase letters and valid dbid strings!
Serious problems after use:
1. If nidprocessdf and nidprocesscf fail. Unable to mount or open
2. Even if they all succeed. Or open the database. The system tablespace file needs to be recovered! ORA-01194: File 1 needs more recovery to be consistent
3. Even if they all succeed.RMAN cannot catalog the backup set either, but you can view the backup information in it! Maybe this is what he meant..