Is it Required to Restart OFSAA Agent Services / Message Server After Database Node Failover
(Doc ID 2904317.1)
Last updated on JANUARY 24, 2024
Applies to:
Oracle Financial Services Analytical Applications Infrastructure - Version 8.0.0 and laterInformation in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Analytical Applications Infrastructure (OFSAAI / AAI)
User Interface (UI)
Pluggable database (PDB)
Real Application Clusters (RAC)
Goal
In preparation of upgrade to OFSAA 8.1.2, have performed a node failover test of the Oracle 19 database which is in an RAC environment. The pluggable database failed over from one node to another within the same container.
During an uncontrolled failover of the pluggable database, application UI remained intact and team was able to resume activities on UI.
However, in the application message server logs the ORA-03114 error is showing up. Looking at existing MOS doc it is defined as an expected issue and in the past this has been fixed with a recycle of the OFSAA services.
On the server where the node failover test was done, the batch run timings are still shown in the 'Batch Monitor' screen. So that connectivity is not broken, but the AM, message server and router trace logs are not being written into since the database failover test.
Want to understand if the ORA-03114 error in case of a Oracle PDB node failover test when using TNS entry as DB connection string is expected.
If so, the only fix for this is to recycle the OFSAA services?
In this case the RAC format database has a listener running (on one of the underlying RAC hosts) - and using the same listener in the TNS file, on Database Configuration screen on OFSAA UI and also on Weblogic console for data sources configuration. Depending on the underlying host where the pluggable database listener is running that host is being connected to.
Our objective is to avoid a recycle of the AM or Router process to fix the 'connectivity to Oracle lost' error which breaks the 'Batch Monitoring Screen' on OFSAA UI. If every time the app services need to be recycled to resume connectivity, it is not really effective.
Need to confirm if the OFSAA application supports this functionality of resuming the connection to database after a local node failover is done at the database level.
Solution
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
Goal |
Solution |