Costing Terminated with Signal 10 or Signal 11
(Doc ID 2634312.1)
Last updated on JULY 17, 2024
Applies to:
Oracle Payroll - Version 12.2 HRMS RUP13 and laterInformation in this document applies to any platform.
Symptoms
Problem Statement:
Costing fails with the error below. (Request log with GMFZT logging enabled)
c7264 i/p id = XXX, RR id = XXX, keyflex_id -XXX.000000, b/c B, value XXX, <===== Negative ID
d/c D, aa_id XXX
....
d/c D, aa_id XXX
....
In { pycosdcomb
stat_low = 8A
stat_high = 0
emsg:was terminated by signal 10
/.../fs2/EBSapps/appl/pay/12.0.0/bin/PYUGEN
Program exited with status -1
looking for keyflex_id -xxxx.000000 hash value -xxx
stat_low = B
stat_high = 0
emsg:was terminated by signal 11
/xxx/fs2/EBSapps/appl/pay/12.0.0/bin/PYUGEN
Program exited with status -1
stat_low = B
stat_high = 0
emsg:was terminated by signal 11
/xxx/fs2/EBSapps/appl/pay/12.0.0/bin/PYUGEN
Program exited with status -1
Steps to Reproduce:
The issue can be reproduced at will with the following steps:
- Run Costing
- Request fails with the signal 10 or signal 11
Changes
Apply HR_PF.C RUP13 that includes the Bug:27775801 fix.
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 |
| Changes |
| Cause |
| Solution |
| References |