Cloned OFSAA 8.0 Application Will Not Start (Doc ID 2163219.1)

Last updated on OCTOBER 01, 2024

Applies to:

Symptoms

On OFSAA 8.0.0, after cloning the OFSAA 8.0 application for production environment from the development instance using the officially published OFSAA Cloning Reference Guide Release 8.0, while running script startofsaai.sh in the foreground:

ERROR

Creating Logger Svc Code:800 LoggerName:SCDLOGGER oggerlevel:0
Creating Logger Svc Code:999 LoggerName:ESPLOGGER oggerlevel:0
LogConstants.log4jInited = true
#Comparing---DAPPINST99996666---DAPPINST99996666
Kindly enter CONFIG schema password
User has typed an incorrect password or account is locked, please check the log.
Please provide the system password again

Even after entering the correct password, same error occurs.  Check of the $FIC_APP_HOME/common/FICServer/logs/SMSService.log shows the following error:

[UMMLOG] Jul 8,16 20:00:39 : [INFORMATIONDOMAINSERVICES][AESCryptor] Security File Directory path is  : /app/ofsaa/conf/
[UMMLOG] Jul 8,16 20:00:39 : [INFORMATIONDOMAINSERVICES][AESCryptor] File exists at /app/ofsaa/conf/AESCryptKey.ext
[UMMLOG] Jul 8,16 20:00:39 : [SMSSERVICEPROVIDER]Checking Security file version..
[UMMLOG] Jul 8,16 20:00:39 : [SMSSERVICEPROVIDER]Version is correct
[UMMLOG] Jul 8,16 20:00:40 : [INFORMATIONDOMAINSERVICES]Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor

[UMMLOG] Jul 8,16 20:00:40 : [INFORMATIONDOMAINSERVICES]Exception
java.sql.SQLException: Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor

at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:743)
at oracle.jdbc.driver.PhysicalConnection.connect(PhysicalConnection.java:666)

The following errors appear

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

1. Have referred OFSAA cloning document from Oracle, steps was taken for cloning summarizing below.
       a. Took full import of Atomic and config schemas from development to production
       b. Transfer APP directory from dev server to prod server and give all priviledges to app folder.
       c. IP related changes in config file as mention in cloning documents

2. Given all privileges to ftpshare.
3. IP related changes in config tables attaching data for all tables.

Changes

 Newly cloned instance.

Cause

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