SQL Rules / SQL Rule Batches Are Not Working in Migrated / Cloned OFSAA Instance (Doc ID 1571264.1)

Last updated on SEPTEMBER 14, 2017

Applies to:

Oracle Financial Services Analytical Applications Infrastructure - Version 7.3 and later
Oracle Financial Services Funds Transfer Pricing - Version 6.0 and later
Oracle Financial Services Asset Liability Management - Version 6.0 and later
Oracle Financial Services Profitability Management - Version 6.0 and later
Information in this document applies to any platform.
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)

Symptoms

None of the SQL Rule successfully run in a migrated/cloned environment. After pressing the run button, the message states the rule was triggered successfully, but the procedure or the SQL Statement is not executed.
The View Log link does not appear and no row is written in FSI_MESSAGE_LOG for the process.

The following error appears in the nohup.out or similar file in $FIC_DB_HOME/bin:

sqlRuleID...206312
batchID...INFODOM_Task1_SQLRULE_DAILY_20160801_1
Making Socket connection..
Exception Occured..java.net.UnknownHostException: <serveraddress>
java.net.UnknownHostException: <serveraddress>
          at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:178)
          at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
          at java.net.Socket.connect(Socket.java:579)
          at java.net.Socket.connect(Socket.java:528)
          at java.net.Socket.<init>(Socket.java:425)
          at java.net.Socket.<init>(Socket.java:208)
          at com.ofs.reveleus.sqlrule.component.SqlRuleBuilder.main(SqlRuleBuilder.java:94)


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

1. Create SQL Rule with either procedure or SQL Statement. You can use the following simple SQL statement:

INSERT INTO TABLE_X VALUES ('111', '222', '333');
COMMIT;
END;

2. Execute the Rule
===> Although the process was triggered successfully, no row is written in TABLE_X. There is also nothing written to the FSI_MESSAGE_LOG table.

Changes

 Migrate/cloned the working environment.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms