Return
-
Title
A Shareplex process stops due to "ORA-01017: invalid username/password logon denied" -
Description
Shareplex for Oracle
Some Shareplex processes such as sp_ocap (Capture), sp_tconf (Activation), sp_opst (Post), DBCopy (dbcopy), sp_ordr (Read) that make connection to database can error out with ORA-01017 as shown below for sp_tconf process:
10/23/02 11:53 Logging user command: oracle activate config config1
10/23/02 11:53 Process launched: sp_tconf (for o.SID queue *) [pid = 11008]
10/23/02 11:53 Compiling a configuration file: datasrc - o.SID; file - config1
10/23/02 11:53 Notice: sp_tconf(pdb) (for o.ASTEST queue *) Oracle env - ASTEST:/u01/app/oracle/product/8.1.7
10/23/02 11:53 Error: sp_tconf (for o.ASTEST queue *) OCI Error: ORA-01017: invalid username/password; logon denied..
10/23/02 11:53 Config compilation completed: datasrc - o.SID; file - config1
10/23/02 11:53 Bad config file: file - config1; ORA Error: connect failed for database o.SID - ORA-01017: invalid username/password; logon denied.
10/23/02 11:53 Process exited sp_tconf (for o.SID queue *) [pid = 11008] - exit(1)
The event log complains that the username and/or password is not correct so the process could not make connection to database. -
Resolution
This problem can happen due to a number of reasons as follows:
1. As a part of password rotation policy followed for security purpose, the password for Shareplex user in the database was changed by administrators. This renders entry in the paramdb file invalid. A Shareplex process makes connection to database using the username and password from paramdb file. The following is the sample entry where the password is encrypted:
SP_ORD_LOGIN_O.ILP "77bff9a39a0c36deb4362d"
SP_ORD_OWNER_O.ILP "SPLEX"
When Shareplex process attempts to make connection to the database using the invalid values for username/password from paramdb, it errors out with ORA-01017. The changes to password for Shareplex user should be done via ora_chpwd utility located in /proddir/bin directory and not directly by DBA users. This ensures that the paramdb file is updated with the value for password. The changes to username or password can also be done by running ora_setup.
Caution: For username change, one needs to take additional steps if there is currently replication happening on the system. Please consult Shareplex Admin Guide for details.
2. Duplicate entry for username in paramdb can cause this problem. Normally this should not happen if the username is entered via ora_setup. If done by editing paramdb directly, this can happen. The solution lies in removing the additional entry or remove all the entries for username/password and rerun ora_setup.
3. Incorrect setting of ORACLE_SID and ORACLE_HOME can also cause Shareplex to report this error. One should set the variables ORACLE_HOME, ORACLE_SID, SP_COP_UPORT, SP_COP_TPORT, SP_SYS_VARDIR, etc, correctly before starting Shareplex.