My Oracle Support Banner

ORA-01017: invalid username/password When Running LSH Post Installation Program (Doc ID 1569238.1)

Last updated on OCTOBER 14, 2014

Applies to:

Oracle Life Sciences Data Hub - Version and later
Information in this document applies to any platform.


On Oracle Life Sciences Data Hub the following occurs:

User is trying to run LSH Post Installation program but receiving "ORA-01017: INVALID USERNAME/PASSWORD; LOGON DENIED" inside OWB log file.

2013/07/10-11:27:55-CEST [16AEEA66][CDR_RTREPOS.CDR_RTREPOS] Attempting to create adapter 'class.Oracle Database.11.2.DDLDeployment'
2013/07/10-11:27:55-CEST [16AEEA66][CDR_RTREPOS.CDR_RTREPOS] java.sql.SQLException: ORA-01017: invalid username/password; logon denied

    at oracle.jdbc.driver.T2CConnection.checkError(
    at oracle.jdbc.driver.T2CConnection.logon(
    at oracle.jdbc.driver.PhysicalConnection.<init>(
    at oracle.jdbc.driver.T2CConnection.<init>(
    at oracle.jdbc.driver.T2CDriverExtension.getConnection(
    at oracle.jdbc.driver.OracleDriver.connect(
    at java.sql.DriverManager.getConnection(
    at java.sql.DriverManager.getConnection(
    at oracle.wh.runtime.platform.common.DatabaseConnectionFactory.connectUsingTNS(
    at oracle.wh.runtime.platform.common.DatabaseConnectionFactory.openUsingTNS(
    at oracle.wh.runtime.platform.adapter.odb.OdbDeploymentAdapter.deploy(
    at oracle.wh.runtime.platform.service.controller.DeploymentController.deploy(
    at oracle.wh.runtime.platform.service.controller.DeploymentController.deploy(
2013/07/10-11:27:55-CEST [16AEEA66][CDR_RTREPOS.CDR_RTREPOS] java.lang.NullPointerException
    at oracle.wh.runtime.platform.adapter.odb.OdbDeploymentAdapter.deploy(
    at oracle.wh.runtime.platform.service.controller.DeploymentController.deploy(
    at oracle.wh.runtime.platform.service.controller.DeploymentController.deploy(


1) Run below SQL statement with SYSTEM database user:

select * from dba_users where account_status <>'OPEN';

The result of the upper SQL statement will show you if there are any locked database users related to LSH.

In this case CDR_RTREPOS database user was locked.

You should proceed in unlocking users related to LSH without changing the password.

2) Script "$CDR_TOP/patch/115/sql/cdrresetowbstorepwd.sql" was ran in order to reset OWB stores passwords with no luck.

3) In order to understand what database user was raising the "ORA-01017" a database trace was used.

Result was not helpful because it was not giving more details on the actual database user that was erroring out.

*** 2013-07-10 16:16:02.744
*** SESSION ID:(71.7917) 2013-07-10 16:16:02.744
*** CLIENT ID:() 2013-07-10 16:16:02.744
*** SERVICE NAME:(LSH) 2013-07-10 16:16:02.744
*** MODULE NAME:(java@lsh (TNS V1-V3)) 2013-07-10 16:16:02.744
*** ACTION NAME:() 2013-07-10 16:16:02.744
dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=12, mask=0x0)
----- Error Stack Dump -----
ORA-01017: invalid username/password; logon denied
----- SQL Statement (None) -----
Current SQL information unavailable - no cursor.

4) Chapter 15 "5 Synchronizing an Apps Password Change" from the LSH Admin Guide was used as well with no luck.

5) Verify for what database users the failed logins are increasing:

select * from user$ where lcount!=0;

Result was returning LSH related database users like 'CDR_W%'.

6) Get the store id for 'CDR_W%' users returned at step 5.

With APPS database user run:

select store_id, store_name from owbsys.wb_rt_stores where store_name like 'CDR_W%';

 7) Check the parameters related to 'CDR_W%' users found at step 5 and the store ID taken from step 6)

select parameter_name,parameter_value from owbsys.wb_rt_store_parameters where parameter_name in ('Schema','ConnectAs','Host','Service') and store_id = ID_FROM_STEP_6;

Correct Output:

ConnectAs    CDR_W1B207_118C301
Host         HOST1.DAOMAIN.COM
Schema       CDR_W1B207_118C301
Service      SERVICE

In this case, for every Schema, the 'ConnectAs' was set to CDR_RTREPOS database user and not the corresponding 'CDR_W%' database user.

Also the 'Service' value was not corresponding to the TNS entries in user environment.



User had manually changed database user passwords.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.