PIN_ERR_STREAM_EOF Returned When Executing PCM_OP_WRITE_FLDS or PCM_OP_CREATE_OBJ With Big Input Flist
(Doc ID 3044057.1)
Last updated on SEPTEMBER 02, 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
Given Oracle Communications Billing and Revenue Management(BRM) 15.0 atypical implementation which is used only for billing of some rented equipment, for which pricing and rating is done outside BRM in another custom app. Custom events that are later used for billing, are created in BRM via custom opcode execution .
To be noted customer is currently running BRM 7.5 PS12 in their production env, and project to upgrade to 15.0 is ongoing.
So they configured a BRM 15.0 env as following: fresh installation of BRM 15.0; only database(DB) schema upgrade scripts were run as following: 7.5 -> 12ps8 -> 15
DB snapshot taken from PROD env on 28-apr-2024 was used in the above upgrade.
In such upgraded env, one is running PCM_OP_WRITE_FLDS to update one instance of custom class /profile/tenancy, and passing 7 instances of custom ARRAY called CUS_FLD_TENANCY.
To be noted that class /profile/tenancy is having more than 200 fields, while only CUS_FLD_TENANCY ARRAY has 120 fields.
The problem is that when executing PCM_OP_WRITE_FLDS with 7 instances of CUS_FLD_TENANCY ARRAY in input flist, following errors are logged in cm.pinlog:
To be noted that the same identical scenario is running ok in BRM 7.5 PS12 environment. Also, if passing only 6 instances (or less) of custom ARRAY CUS_FLD_TENANCY in input flist, opcode execution is without error.
Similar error is logged when executing PCM_OP_CREATE_OBJ to create new object for the custom class.
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 |