ORA-00214 mounting a RAC or Oracle Restart (ASM) database

ISSUE :

SQL> alter database mount;

alter database mount

*

ERROR at line 1:

ORA-00214: control file '+DATA/ISTDB/controlfile/Current.264.1037981987' version 72543 inconsistent with file

'+FRA/ISTDB/controlfile/Current.264.1037981945' version 72434

Solution :

SQL>   show parameter control

NAME                            TYPE                VALUE

------------------------------------ ----------- ------------------------------

control_files                  string       +DATA/ISTDB/controlfile/Current.264.1037981987,

                                                           +FRA/ISTDB/controlfile/Current.264.1037981945

==>  '+DATA/ISTDB/controlfile/Current.264.1037981987' version 72543 has latest version number

Use RMAN to restore that controlfile

RMAN> restore controlfile to '+FRA' from '+DATA/ISTDB/controlfile/Current.264.1037981987';

Starting restore at 19-APR-20

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=1 device type=DISK

channel ORA_DISK_1: copied control file copy

Finished restore at 19-APR-20

Remove the old and outdated conrolfile

[grid@dm04GG01 ~]$  asmcmd rm '+FRA/ISTDB/controlfile/Current.264.1037981945'

[grid@dm04GG01 ~]$ asmcmd ls +FRA/ISTDB/controlfile/

Current.256.1037981987_old

current.256.1038169995

Now change the control_files old with new in spfile;

SQL> alter system set control_files='+DATA/ISTDB/controlfile/Current.264.1037981987','+FRA/ISTDB/controlfile/current.256.1038169995';

System altered.

SQL> startup force mount

SQL> show parameter control

NAME                                 TYPE        VALUE

------------------------------------ ----------- ------------------------------

control_file_record_keep_time        integer     7

control_files                                          string       +DATA/ISTDB/controlfile/current.264.1037981987,                                

                                                                                  +FRA/ISTDB/controlfile/current.256.1038169

                                                                                   995

control_management_pack_access   string      DIAGNOSTIC+TUNING


If you get the recover error while startup (in case)

recover the database using command

Recover database ;

while startup you may get error

ORA-00600: internal error code, arguments: [4194], [26], [25], [], [], [], [],
[], [], [], [], []

Then follow the below Doc id : 

Doc ID 1428786.1 

1. Create pfile from spfile to edit
SQL> Create pfile='/tmp/initsid.ora' from spfile;

2. Shutdown the instance

3. set the following parameters in the pfile /tmp/initsid.ora
    undo_management = manual
    event = '10513 trace name context forever, level 2'

4. SQL>>startup restrict pfile='/tmp/initsid.ora'

5. SQL>select tablespace_name, status, segment_name from dba_rollback_segs where status != 'OFFLINE';

This is critical - we are looking for all undo segments to be offline - System will always be online.

If any are 'PARTLY AVAILABLE' or 'NEEDS RECOVERY' - Please open an issue with Oracle Support or update the current SR.  There are many options from this moment and Oracle Support Analyst can offer different solutions for the bad undo segments.

If all offline then continue to the next step

6. Create new undo tablespace - example
SQL>create undo tablespace <new undo tablespace> datafile <datafile> size 2000M;

7. Drop old undo tablespace
SQL>drop tablespace <old undo tablespace> including contents and datafiles;

8. SQL>shutdown immediate;

9 SQL>startup nomount;  --> Using your Original spfile

10. Modify the spfile with the new undo tablespace name

SQL> Alter system set undo_tablespace = '<new tablespace created in step 6>' scope=spfile;

11. SQL>shutdown immediate;

12. SQL>startup;  --> Using spfile

• Tweet
• Share
• Share
• Share
• Share

Related Post