"not valid segment" Core Dump when Running Pin_ledger_report -export -regenerate
(Doc ID 2000709.1)
Last updated on MARCH 13, 2019
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.4.0.1.0 and laterInformation in this document applies to any platform.
Symptoms
On : 7.4.0.20.0 version, General Ledger (GL)
ACTUAL BEHAVIOR
---------------
The ledger report core dumps after a period of time when using the regenerate option.
In cm.pinlog, we see:
EXPECTED BEHAVIOR
-----------------------
pin_ledger_report should not core dump.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) Run ledger as normal on first of month.
2) Update some of the values in the pin_glid file
3) Reload the pin_glid file
4) Remove segment from system and add new segment
5) Restart system
6) Run SQL statement to get the poid of last run of the ledger (as completed in step 1). You can use developer's center as well.
7) Run the ledger again in regenerate mode (pin_ledger_report -mode export -regenerate 0.0.0.1-poidval)
Changes
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 |