ORA-01105 and ORA-01677 errors after RAC establishes a data guard Environment

After a data guard is set up for the RAC environment, an instance of the RAC environment cannot be started after it is closed, and the error message is: ORA-01105 and ORA-1677.

When an instance in the RAC environment is disabled, the following error is reported during restart:

Bash-2.03 $ srvctl start inst-D testrac-I testrac2

PRKP-1001: Error starting instance testrac2 on node racnode2

Racnode2: ora. racnode2.vip: created new logical interface ce0: 1

Racnode2: ora. racnode2.asm2. ASM:

Racnode2: ora. racnode2.asm2. ASM: SQL * Plus: Release 10.2.0.3.0-production on Wed Jul 4 23:13:15 2007

Racnode2: ora. racnode2.asm2. ASM:

Racnode2: ora. racnode2.asm2. ASM: Copyright (c) 1982,200 6, Oracle. All rights reserved.

Racnode2: ora. racnode2.asm2. ASM:

Racnode2: ora. racnode2.asm2. ASM: enter user-Name: connected to an idle instance.

Racnode2: ora. racnode2.asm2. ASM:

Racnode2: ora. racnode2.asm2. ASM: SQL> ASM instance started

Racnode2: ora. racnode2.asm2. ASM:

Racnode2: ora. racnode2.asm2. ASM: total system global area 130023424 bytes

Racnode2: ora. racnode2.asm2. ASM: fixed size 2028368 bytes

Racnode2: ora. racnode2.asm2. ASM: variable size 102829232 bytes

Racnode2: ora. racnode2.asm2. ASM: ASM cache 25165824 bytes

Racnode2: ora. racnode2.asm2. ASM: ASM diskgroups mounted

Racnode2: ora. racnode2.asm2. ASM: SQL> disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.3.0-64bit Production

Racnode2: ora. racnode2.asm2. ASM: with the partitioning, real Application Clusters, OLAP and Data Mining options

Racnode2: ora. racnode2.asm2. ASM:

Racnode2: ora. racnode2.asm2. ASM:

Racnode2: ora. racnode2.asm2. ASM: SQL * Plus: Release 10.2.0.3.0-production on Wed Jul 4 23:13:54 2007

Racnode2: ora. racnode2.asm2. ASM:

Racnode2: ora. racnode2.asm2. ASM: Copyright (c) 1982,200 6, Oracle. All rights reserved.

Racnode2: ora. racnode2.asm2. ASM:

Racnode2: ora. racnode2.asm2. ASM: enter user-Name:

Racnode2: ora. racnode2.asm2. ASM: connected:

Racnode2: ora. racnode2.asm2. ASM: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0-64bit Production

Racnode2: ora. racnode2.asm2. ASM: with the partitioning, real Application Clusters, OLAP and Data Mining options

Racnode2: ora. racnode2.asm2. ASM:

Racnode2: ora. racnode2.asm2. ASM: SQL> ORA-15097: cannot shutdown ASM instance with connected RDBMS instance

Racnode2: ora. racnode2.asm2. ASM: SQL> disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.3.0-64bit Production

Racnode2: ora. racnode2.asm2. ASM: with the partitioning, real Application Clusters, OLAP and Data Mining options

Racnode2: ora. racnode2.asm2. ASM:

Racnode2: ora. racnode2.asm2. ASM:

Racnode2: ora. racnode2.asm2. ASM: SQL * Plus: Release 10.2.0.3.0-production on Wed Jul 4 23:13:56 2007

Racnode2: ora. racnode2.asm2. ASM:

Racnode2: ora. racnode2.asm2. ASM: Copyright (c) 1982,200 6, Oracle. All rights reserved.

Racnode2: ora. racnode2.asm2. ASM:

Racnode2: ora. racnode2.asm2. ASM: enter user-Name:

Racnode2: ora. racnode2.asm2. ASM: connected:

Racnode2: ora. racnode2.asm2. ASM: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0-64bit Production

Racnode2: ora. racnode2.asm2. ASM: with the partitioning, real Application Clusters, OLAP and Data Mining options

Racnode2: ora. racnode2.asm2. ASM:

Racnode2: ora. racnode2.asm2. ASM: SQL> ASM instance Shutdown

Racnode2: ora. racnode2.asm2. ASM: SQL> disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.3.0-64bit Production

Racnode2: ora. racnode2.asm2. ASM: with the partitioning, real Application Clusters, OLAP and Data Mining options

Racnode2: ora. racnode2.asm2. ASM:

CRS-0215 :???????????? 'Ora. testrac. testrac2.inst '??

Because the error information is not clear, you can use sqlplus to manually start ASM and DB:

Bash-2.03 $ export oracle_sid = + asm2

Bash-2.03 $ sqlplus "/As sysdba"

SQL * Plus: Release 10.2.0.3.0-production on Wednesday July 4
23:18:57 2007

Copyright (c) 1982,200 6, Oracle. All rights reserved.

Already connected to the idle routine.

SQL> startup

ASM instance started

Total system global area 130023424 bytes

Fixed size 2028368 bytes

Variable Size 102829232 bytes

ASM cache 25165824 bytes

ASM disk mounted
SQL> exit from Oracle Database 10g enterprise
Edition Release 10.2.0.3.0-64bit Production

With the partitioning, real Application Clusters, OLAP and Data Mining options disconnected
Bash-2.03 $ exit

Exit

$ Sqlplus "/As sysdba"

SQL * Plus: Release 10.2.0.3.0-production on Wednesday July 4
23:19:21 2007

Copyright (c) 1982,200 6, Oracle. All rights reserved.

Already connected to the idle routine.

SQL> startup

The Oracle routine has been started.

Total system global area 2147483648 bytes

Fixed size 2031480 bytes

Variable Size 503316616 bytes

Database buffers 1627389952 bytes

Redo buffers 14745600 bytes

ORA-01105 :?????????????????

ORA-01677 :????????????????

This shows the error message that caused the database to fail to start: ORA-1105 and ORA-1677.

An error message for the ORA-1105 is described:

ORA-01105: Mount is incompatible with mounts by other instances.

Cause: an attempt to mount the database discovered that another instance mounted a database by the same name, but the mount is not compatible. Additional errors are reported explaining why.

Action: See accompanying errors.

ORA-1677 error message is:

ORA-01677: standby file name convert parameters differ from other instance

Cause: the db_file_standby_name_convert or log_file_standby_name_convert initialization parameters are not the same as in other instancesthat already have the database mounted.

Action: Change initialization parameters db_file_standby_name_convert and log_file_standby_name_convert to match otherinstances.

It can be determined from the two information that the db_file_standby_name_convert and log_file_standby_name_convert parameters are inconsistent.

In retrospect, at the end of building data guard, we use alter system set... Scope = spfile mode. Because no Sid is specified, this modification will take effect for both instances. However, this parameter cannot be modified for started instances, therefore, only spfile is modified.

The modified db_file_standby_name_convert parameter is loaded when the instance testrac2 is restarted, causing a conflict with the testrac1 instance that has not been started, resulting in an error.

It is easy to solve the problem. Shut down instance 1 and restart both instances.

Establish data in the RAC Environment
The process of guard can refer to: http://yangtingkun.itpub.net/post/468/411898

Link: http://space.itpub.net/4227/viewspace-69495