Agile Application Server Fails to Start Up After Importing Agile and RCU Schema to New Database Instance (Doc ID 2556691.1)

Last updated on JANUARY 24, 2024

Applies to:

Symptoms

After importing Agile and RCU schema to new database instance and updating below files to switch to the new database,
AGILE_HOME\agileDomain\config\jdbc\CP-AgileContentPool-jdbc.xml
AGILE_HOME\agileDomain\config\agile.properties
Agile application server fails to start with below error:

Error

oracle.security.jps.internal.common.config.AbstractSecurityStore getSecurityStoreVersion
WARNING: Unable to get the Version from Store returning the default
oracle.security.jps.service.policystore.PolicyStoreException: javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection
Error Code: 17002


Facts

- Listener and Net Service is configured, and Listener is running in the new database instance
- Hostname, port number, SID is correct in CP-AgileContentPool-jdbc.xml and agile.properties
- Can connect to the new Agile database schema using sqlplus from Agile Application Server machine

Steps

The issue can be reproduced at will with the following steps:

1. Update below files to point to the new database:
   AGILE_HOME\agileDomain\config\jdbc\CP-AgileContentPool-jdbc.xml
   AGILE_HOME\agileDomain\config\agile.properties
2. Restart Agile Application Server
   
   
   
   

Changes

Agile and RCU database schema was moved to the new database instance, and the old database instance was shutdown

Cause

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