Conversion Manager Does Not Convert Extension Date Field To Unix Timestamp
(Doc ID 3035935.1)
Last updated on JULY 19, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 15.0.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
Having a promotion extension array which contains a date field. Sometimes observed the conversion from datetime to Unix Timestamp is not successful in all cases.
During testing and subsequent observations, identified the following unexpected behavior:
1. Conversion Phase: During the import process this field is supposed to be converted from datetime to Unix Timestamp from the pin_cmt utility. Sometimes the conversion is not successful and the utility writes a .dat file with most of dates for this field correctly transformed, and a minor subset of them left as datetime. No error is shown during this phase.
2. Import Phase: This is when an SQL Loader error is encountered, because the control file expects an integer for this field, but in some cases it receives datetime values.
ERROR :
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 |