A series of problems occurred after dbid Modification

After modifying the dbid, a series of problems occur. Environment: OEL + Oracle11.2.0.3 Problem description: as a result of the Backup recovery test, according http://www.bkjia.com/database/201305/209268.html , Changed the dbid of the test database, it seems that the process has been completed successfully, and the fact is not that simple, after changing the dbid, there are a series of problems. First startup database appears ORA-01589, then resetlogs is ORA-01194 and so on, under the face slowly below: after changing the dbid, query dbid: SQL> select dbid from v $ database; the DBID----------1234567890 restarts the database to ensure that the changes are validated, encountered ORA-01589, ORA-01589 must use resetlogs or nosetlogs option for database openSQL> alter database open resetlogs; ORA-01194: file 1 needs more recovery to be consistentORA-01110: data file 1: '/oradata/orcl2/system01.dbf' SQL> recover database u Sing backup controlfile until cancel; ORA-01547: warning: RECOVER succeeded but open resetlogs wocould get error belowORA-01194: file 1 needs more recovery to be consistentORA-01110: data file 1: '/oradata/orcl2/system01.dbf' (you need to note that due to the change of dbid, the previous backup set cannot be used, so rman cannot use the previous backup set to restore the data file) solution: Try to modify the implicit parameter _ allow_resetlogs_upload uption = true first, shutdown the immediate database, create pfile, modify pfile, and recreate spfile. OK! SQL> create pfile from spfile; File created. modify initorcl2.ora and add the implicit parameter _ allow_resetlogs_upload uption = true. Use pfile to create spfile: SQL> create spfile from pfile; File created. start Database: SQL> startupORACLE instance started. total System Global Area 418484224 bytesFixed Size 1336932 bytesVariable Size 331352476 bytesDatabase Buffers 79691776 bytesRedo Buffers 6103040 bytesDatabase mounted. database opened. OK! Normal SQL> select dbid from v $ database; the DBID----------1234567890 failed to use the previous rman backup set due to a change to dbid, and backed up the database again, including logical backup: ORA-01187 and ORA-01110About to export the entire database .... exporting tablespace definitionsEXP-00008: ORACLE error 1187 encounteredORA-01187: cannot read from file because it failed verification testsORA-01110: data file 202: '/oradata/orcl2/temp02.dbf' EXP-00000: Export terminated unsu Ccessfully check temp temporary tablespace: SQL> select file_name, tablespace_name from dba_temp_files; select file_name, tablespace_name from dba_temp_files * ERROR at line 1: ORA-01187: cannot read from file because it failed verification testsORA-01110: data file 201: '/oradata/orcl2/temp01.dbf' my solution is to recreate the temp tablespace: SQL> alter database tempfile'/oradata/orcl2/temp01.dbf' drop; Database altered. SQL> alter database tempfile '/Oradata/orcl2/temp02.dbf' drop; Database altered. SQL> select * from v $ tempfile; no rows selected SQL> alter tablespace temp add tempfile '/oradata/orcl2/temp01.dbf' size 50 m; Tablespace altered. select file_name, tablespace_name, status from dba_temp_files; FILE_NAME TABLESPACE_NAME STATUS ------------------------- begin -------/oradata/orcl2/temp01.dbf temp online re-initiate logical backup; O K! This is normal, but the database is still extremely unstable. We recommend that you rebuild the database. We do not recommend that you modify the dbid on the production database.