Troubleshooting ORA-16191 and ORA-1017/ORA-1031 in Data Guard Log Transport Services or Data Guard Broker (Doc ID 1368170.1)

APPLIES TO:

Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.

PURPOSE

Reviewed for Relevance 15-Jul-2015

This Document presents various Causes, Solutions and Things to verify when ORA-16191 and/or ORA-1017/ORA-1031 is encountered in the Log Transport Services or in the Data Guard Broker.

TROUBLESHOOTING STEPS

Please follow the mentioned Points in the order presented to solve the ORA-16191 / ORA-01017 /ORA-1031 in Log Transport Services:

NOTE: For Steps 1. - 5. if the Primary and/or Standby Database is a RAC Database, the Passwordfile must be the same on all Instances. So it has to be copied to all Instances in Case.

1. Ensure the Initialization Parameter 'REMOTE_LOGIN_PASSWORDFILE' is set to 'SHARED' or 'EXCLUSIVE' on the Primary and Standby Database.

2. There exists a Passwordfile on the Primary and Standby Database in $ORACLE_HOME/dbs ($ORACLE_HOME\database on Microsoft Windows) typically having the Format 'orapw'

3. Verify if the Password for the SYS-User has been changed recently (possibly due to any Security Policies). In this Case the new Password is updated on the Physical Standby Database by the Log Apply Services, but Apply Services cannot update the Passwordfile. In this Case you have to copy/rename the Passwordfile from the Primary Database to the Standby Site again.

4. Verify if the 'Strong Authentification Framework' is used. This depends on the Setting for the Initialization Parameter 'SEC_CASE_SENSITIVE_LOGON' - when set to 'TRUE' it is used, when set to 'FALSE' it is not used. Note that if it is enabled you cannot create a Passwordfile for a Physical Standby Database any more, you have to copy (ang possibly rename) the Passwordfile from the Primary Database instead. So if you are not sure you can copy/rename the Passwordfile from the Primary Database to the Standby Database again.

5. If you do not use the 'Strong Authentification Framework' ensure the Passwordfile is created with the 'ignorecase=y' - Option on both Sites, eg.

$ orapwd file= password= ignorecase=y force=y

When using Microsoft Windows you have to use 'oradim' and drop/recreate the Windows Service (called 'OracleService') with a new Passwordfile instead, eg.

C:> oradim -delete -sid
C:> del $ORACLE_HOME\database\PWD.ora
C:> oradim -new -sid -syspwd

6. If you have setup the 'REDO_TRANSPORT_USER'-Initialization Parameter to a certain User, this User must be granted the 'SYSOPER'-Role and the Setting for this Parameter must be the same on the Primary and all Standby Databases. See

Note 1542132.1: Data Guard Standby Database log shipping failing reporting ORA-01031 and Error 1017 when using Redo Transport User

7. If you are still suffering from ORA-16191 and ORA-01017/ORA-01031 although all mentioned Items are in Place, set Event 16191 on the Primary Database, eg.

SQL> alter system set events '16191 trace name errorstack level 10'

This will create a new Tracefile in the Trace-Directory. Forward the Tracefile generated together with the ALERT.LOGs and your Log Transport Services-Setup to Oracle Global Customer Services for Review and Recommendations.

Please note if password file is changed it would be good to restart the standby database after new password file is copied from primary.

NOTE : If passwordfile is stored on ASM for RAC case,

Use srvctl to verify where the passwordfile is storaed and you can alter accordingly.

srvctl modify database -d -pwfile

Example,

srvctl modify database -d db121stb -pwfile +DATA/DB121STB/orapwdb1211

For releases 11.2 or later, when password file is stored in $ORACLE_HOME/dbs use md5sum to check if password files are matching,using steps below:

On each primary and standby node:

cd $ORACLE_HOME/dbs

echo $ORACLE_SID

后续精彩内容已被站长无情隐藏，请输入验证码解锁本文！

验证码：

获取验证码： 请先关注本站微信公众号，然后回复“验证码”，获取验证码。在微信里搜索“AiDBA”或者“dbaup6”或者微信扫描右侧二维码都可以关注本站微信公众号。