Cannot login to the Release Automation Server (ASAP) after upgrading the database server from Oracle 10g to Oracle 11g

Document ID : KB000048193
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Cannot login to the Release Automation Server (ASAP) after upgrading the database server from Oracle 10g to Oracle 11g.

The nolio_dm_all.log shows the following error:

Could not retrieve version info from DB. org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (ORA-01017: invalid username/password; logon denied)

The native oracle client connection and ODBC connection for the 'Nolio' user account works.

Solution:

This error occurs when the 'Nolio' database user account cannot connect to the database from the Release Automation context.

Note: In Oracle 10g the passwords were not case sensitive but from Oracle 11g onwards the passwords are case-sensitive.

If the 'nolio' password consisted of upper case and lower case characters, the connection to the database will fail after the upgrade if the same case characters were not used while specifying the 'nolio' password during installation.

To resolve the issue reset the 'nolio' password using the procedure outlined below:

  1. Stop the 'Release Automation Server' service.

  2. On the database server change the password for the 'nolio' user account.

  3. Open '<Release Automation Home Dir>\webapps\datamanagment\WEB-INF\distributed.properties' file and specify the password:

    data.management.database.pwd = <password>

  4. Start the 'Release Automation Server' service.

  5. Check whether you can login to Release Automation Studio (ASAP).

To encrypt the password:

  1. Navigate to the '<Release Automation Home Dir>\scripts' folder using the command prompt.

  2. The encrypt_password.bat file can be used to create the encrypted password. Open this file and replace the single dot with two dots as below in the relative paths section:

    Figure 1

  3. Execute the batch file to create an encrypted password.

    Syntax: encrypt_password.bat <password>

    Sample screenshot:

    Figure 2

  4. Stop the 'Release Automation Server' service.

  5. Replace the value of data.management.database.pwd property in the '<Release Automation Home Dir>\webapps\datamanagment\WEB-INF\ distributed.properties' file.

  6. Start the 'Release Automation Server' service.

  7. Check whether you can login to Release Automation Studio (ASAP).