Duplicate reports ORA-01017 permission issues

During the configuration of DG today, the preliminary environment has been ready, and the last step is to duplicate the RAC data to the standby end. However, this step is where something strange happens,

During the configuration of DG today, the preliminary environment has been ready, and the last step is to duplicate the RAC data to the standby end. However, this step is where something strange happens,

Environment:

OS: RedHat EnterPrise Linux 5.8x64

Cluster: Oracle Grid 11.2.0.4

Database: Oracle Database EnterPrise 11.2.0.4

Archive: RAC + DG

During the configuration of DG today, the preliminary environment has been ready, and the last step is to duplicate the RAC data to the standby end. However, this step is where something strange happens, I tried several times and couldn't copy the data duplicate in the past. Of course, I tried to copy rman back to the peer end and it couldn't be restored, and I reported a ORA-01017 error. After several hours of effort, the problem was finally solved.

Detailed illustration of the entire process of VMware + Linux + Oracle 10G RAC

Install Oracle 11gR2 (x64) in CentOS 6.4)

Steps for installing Oracle 11gR2 in vmwarevm

Install Oracle 11g XE R2 In Debian

Steps for installing Oracle 11gR2 in vmwarevm

As follows:

Fault symptom:

Rmantarget sys/oracle @ jetdb auxiliary sys/oracle @ standby

RecoveryManager: Release 11.2.0.4.0-Production on Mon May 26 16:14:36 2014

Copyright (c) 1982,201 1, Oracle and/or its affiliates. All rights reserved.
Connectedto target database: JETDB (DBID = 2170518470)
Connectedto auxiliary database: JETDB (not mounted)

RMAN> duplicate target database for standby from active database nofilenamecheck;

Startingrestore at 26-MAY-14
Usingtarget database control file instead of recovery catalog
Allocatedchannel: ORA_DISK_1
ChannelORA_DISK_1: SID = 416 device type = DISK

ChannelORA_DISK_1: restoring control file
RMAN-00571: ========================================================== ==============================
RMAN-00569: ==================== error message stack follows ==========================
RMAN-00571: ========================================================== ==============================
RMAN-03002: failure of restore command at 05/26/2014 16:14:54
ORA-19870: error while restoring backup piece/DBBackup/Phycal/stdb_cntl_0fp98vq2_1_1.bkp
ORA-19504: failed to create file "+ DATA001/jetdb/controlfile/control01.ctl"
ORA-17502: ksfdcre: 3 Failed to create file + DATA001/jetdb/controlfile/control01.ctl
ORA-15001: diskgroup "DATA001" does not exist or is not mounted.
ORA-15055: unable to connect to ASM instance
ORA-01017: invalid username/password; logon denied

Problem Analysis:

1, from the above alarm log, the ORA-01017 can be clearly seen is caused by permission issues.

Then, we begin to check the password file of the slave database. $ ORACLE_HOME/dbs/orapw {SID} exists.

[Oracle @ standby dbs] $ ll $ ORACLE_HOME/dbs/orapw *
-Rw-r ----- 1 oracle oinstall 1536 May 2617: 49/DBSoft/oracle/product/11.2.4/dbhome_1/dbs/orapwstandby

2. In this case, we should check the alter alarm file of the database:

Errorsin file/DBSoft/oracle/diag/rdbms/standby/trace/standby_asmb_11087.trc (incident = 24130 ):
ORA-00600: internal error code, arguments: [OSDEP_INTERNAL], [], [], [], [], [], [], [], [], [], []
ORA-27302: failure occurred at: skfnbeqOpenI
Incidentdetails in:/DBSoft/oracle/diag/rdbms/standby/incident/incdir_24130/standby_asmb_11087_i24130.trc
UseADRCI or Support Workbench to package the incident.
See Note411.1 at My Oracle Support for error and packaging details.
ORA-00210: cannot open the specified control file
ORA-00202: control file: '+ DATA001/jetdb/controlfile/control01.ctl'
ORA-17503: ksfdopn: 2 Failed to open file + DATA001/jetdb/controlfile/control01.ctl
ORA-15001: diskgroup "DATA001" does not exist or is not mounted.
ORA-15055: unable to connect to ASM instance
ORA-15055: unable to connect to ASM instance
ORA-00600: internal error code, arguments: [OSDEP_INTERNAL], [], [], [], [], [], [], [], [], [], []
ORA-27302: failure occurred at: skfnbeqOpenI
ORA-1013signalled during: alter database mount...
Mon May26 16:31:34 2014

From the alarm file, we can clearly see that there is a problem with the ASM disk. Go to the grid user and run the srvctl command to check the asm status:

[Grid @ standby ~] $ Srvctl status asm
ASM isrunning on standby

SQL> select name, state, free_mb from v $ asm_diskgroup;

Name state FREE_MB
-------------------------------
DATA001 mounted121112
ARC001 MOUNTED 122483
BAK001 MOUNTED 122826

As a result, there is no problem with ASM, so the only problem may be the problem of Oracle configuration.

3. At this time, we should first check whether it is a permission issue:

[Root @ standby ~] # Id oracle
Uid = 501 (oracle) gid = 504 (oinstall) groups = 504 (oinstall), 505 (dba)
[Root @ standby ~] # Id grid
Uid = 500 (grid) gid = 504 (oinstall) groups = 504 (oinstall), 503 (asmadmin), 506 (asmdba), 507 (asmoper)

For more details, please continue to read the highlights on the next page: