New Installation of OFSAA 8.1 Fails to Start Weblogic After Installation
(Doc ID 2722925.1)
Last updated on JULY 17, 2023
Applies to:
Oracle Financial Services Analytical Applications Infrastructure - Version 8.1.0.0.0 and laterOracle Financial Services Asset Liability Management - Version 8.1.0.0.0 and later
Oracle Financial Services Funds Transfer Pricing - Version 8.1.0.0.0 and later
Oracle Financial Services Profitability Management - Version 8.1.0.0.0 and later
Oracle WebLogic Server for OCI Container Engine
Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Analytical Applications Infrastructure (OFSAAI)
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Profitability Management (PFT)
Oracle Financial Services Funds Transfer Pricing (FTP)
Oracle Financial Services Asset Liability Management (ALM)
Oracle Financial Services Enterprise Performance Management (EPM)
Symptoms
On OFSAA 8.1.0.0.0 version, after a new OFSAA 8.1.0 installation on RHEL 7. Post deployment of EAR/WAR file on Weblogic, OFSAA is not starting properly. Logs suggested that Weblogic is encountering errors.
ERROR
(06:55:14)LOG: Successfully loaded log file : /oracle/ofsaa_domain/applications/ofsaadev.ear/ofsaadev.war/logs/icc_servlet.log
setLog4jEnvforWeb
setLog4jEnvforWeb setiing paths
GlobalParameters.ISWEB in ofsaalogger true
serviceProps {DAC_CONN_RETRY=100, DAC_CONNECTION_POOL_SIZE=15, FIC_MASTER_DSN_NAME=ficmaster, TIME_BETWEEN_EVICTION_RUNS_MILLIS=600000, DAC_CONN_WAIT=10000, DEFAULT_DB_TYPE=ORACLE, DEFAULT_CONNECTION_URL=jdbc:oracle:thin:@<URL>:1521:<SID>, DAC_QUERY_FETCH_SIZE=10, FIC_MASTER_USER_ID=ofsaa_config, REMOVE_ABANDONED_CONNECTION_TIMEOUT=10800, DEFAULT_DRIVER=oracle.jdbc.driver.OracleDriver, DAC_DEF_ROW_PREFETCH_SIZE=10, DAC_USE_FETCH_SIZE_FOR_LONG=0, DAC_ENABLE_DEBUG=0, LOGGERLEVEL=20, DAC_ENABLE_LOG=0, DEBUG_MODE=false}
setLog4jEnvforWeb
setLog4jEnvforWeb setiing paths
GlobalParameters.ISWEB in ofsaalogger true
serviceProps {DAC_CONN_RETRY=100, DAC_CONNECTION_POOL_SIZE=15, FIC_MASTER_DSN_NAME=ficmaster, TIME_BETWEEN_EVICTION_RUNS_MILLIS=600000, DAC_CONN_WAIT=10000, DEFAULT_DB_TYPE=ORACLE, DEFAULT_CONNECTION_URL=jdbc:oracle:thin:@<URL>:1521:<SID>, DAC_QUERY_FETCH_SIZE=10, FIC_MASTER_USER_ID=<CONFIG>, REMOVE_ABANDONED_CONNECTION_TIMEOUT=10800, DEFAULT_DRIVER=oracle.jdbc.driver.OracleDriver, DAC_DEF_ROW_PREFETCH_SIZE=10, DAC_USE_FETCH_SIZE_FOR_LONG=0, DAC_ENABLE_DEBUG=0, LOGGERLEVEL=20, DAC_ENABLE_LOG=0, DEBUG_MODE=false}
logMessage..LineageController
...
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:39)
Caused by: java.sql.SQLException: SQL string is not a DML Statement
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1210)
..
... 17 more
java.sql.SQLException: Could not execute sql command - Original message: SQL string is not a DML Statement
at com.ofs.aai.service.wf.common.nextgen.adapter.PreparedStatementDecorator.executeUpdate(PreparedStatementDecorator.java:807)
The issue can be reproduced at will with the following steps:
1. Successfully complete PFT 8.1 App Pack installation with 0 fatal errors
2. Deploy .war / .ear file and attempt to start WebLogic
Cause
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
| Symptoms |
| Cause |
| Solution |