Runtime Service Type DPORTAL does not Process Records in the Table ICEPAYLOADEXT
(Doc ID 790552.1)
Last updated on MARCH 24, 2025
Applies to:
Oracle Utilities Energy Information Platform - Version 04.53.00.06.00 to DNU04.53.00.07.00Oracle Utilities Energy Information Platform - Version 04.54 to DNU04.54.03.04.00
Oracle Utilities Transaction Management - Version 04.53.00.06.00 to DNU04.53.00.07.00
Oracle Utilities Transaction Management - Version 04.54 to DNU04.54.03.04.00
Information in this document applies to any platform.
LODESTAR EIP - Version: 04.53.00.06.00 to 04.53.00.07.00
LODESTAR EIP - Version: 04.54.03.00.00 to 04.54.03.04.00
Oracle Utilities Meter Data Management - Version: 1.5.0 to 01.05.00.01.01
Oracle Utilities Meter Data Management - Version: 04.53.00.06.00 to 04.53.00.07.00
Oracle Utilities Meter Data Management - Version: 04.54.03.00.00 to 04.54.03.04.00
Oracle Utilities Transaction Management - Version: 1.5.0 to 01.05.00.01.01
Oracle Utilities Transaction Management - Version: 04.53.00.06.00 to 04.53.00.07.00
Oracle Utilities Transaction Management - Version: 04.54.03.00.00 to 04.54.03.04.00
This problem can occur on any platform.
Symptoms
When using Runtime service type as DPORTAL , it is expected that it will poll all the records from ICEPAYLOADEXT table if payload format is C and based on the payload type defined in the service properties. When the runtime service is started, zero records are locked by the Adapter and the service does not process any records.
There are no errors displayed and the records in ICEPAYLOADEXT table remains in status N where as they are expected to change to status C after successful processing of records.
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 |
| Steps to Update OJDBC Driver Version |
| References |