OFSAA 6.0 Allocation Batch Displays Hanging Ongoing Status When Allocation Fails With ORA- Error
(Doc ID 1558429.1)
Last updated on APRIL 30, 2019
Applies to:
Oracle Financial Services Profitability Management - Version 6.0.3 to 6.1.0.1 [Release 6]Information in this document applies to any platform.
Oracle Financial Services Analytical Applications Infrastructure (OFSAAI) - Version 7.3
Oracle Financial Services Analytical Applications (OFSAA) - Version 6.x
Symptoms
On Oracle Financial Services Profitability Management (PFT) 6.0.3, the PFT engine fails to send proper failure messages for ORA- errors to the ICC batch engine. The batch remains hanging in Ongoing status.
ERROR
Batch continues in 'Ongoing' status even though it has failed with ORA- errors:
PRTCPT_ACCT_COST.BOOK_CODE_ID
Invalid Debit.
Page: 1
(203105) Oracle drv_oci error:
"OCI Function: [4] - oexec(), oexn()"
"SQL Function: [0] - SQL function not found!"
"Oracle Error: ORA-00903: invalid table name"
"Driver Function: drv_oci::Execute()"
"SQL Statement: TRUNCATE TABLE "
(203105) Oracle drv_oci error:
"OCI Function: [4] - oexec(), oexn()"
The issue can be reproduced at will with the following steps:
1. Create allocation which will fail with ORA- errors.
2. Run allocation and check batch status in batch monitor and check FSI_MESSAGE_LOG and debug log file for errors.
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 |
| References |