Error While Deleting Schedule Object In Secondary Schema
(Doc ID 1359175.1)
Last updated on MARCH 25, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
We are getting errors while deleting the schedule object in secondary schema from primary schema. When attaching the device to an account in secondary schema and try to delete that schedule object, it's failing while deleting that schedule object.
Steps to reproduce :
1. Attach a device to an account in secondary schema
2. Create a schedule object for that device while the device status moved from available to allocated
3. Delete that schedule object by calling the OOB opcode PCM_OP_ACT_SCHEDULE_DELETE
Errors in the cm.pinlog:
CM FM->DM opcode PCM_OP_READ_OBJ, opflags=0x0
# number of field entries allocated 20, used 1
0 PIN_FLD_POID POID  <POID> /schedule/device/vf 9840090 0
D Fri Jul 08 02:57:16 2016 XXXXX cm:8900 cm_child.c(115):4829 1:XXXXX:testnap:8897:1:120001:1303734927:1
opcode db: 1(<OPCODE1>), context db: 2(<OPCODE2>), trans_state: 2, opcode: 3
E Fri Jul 08 02:57:16 2016 brmmlapp2 cm:8900 cm_child.c(115):4872 1:XXXXX:testnap:8897:1:120001:1303734927:1
bad cm_change_dm_connection, new db=1(<OPCODE1>), current db=2(<OPCODE2>), err=37(PIN_ERR_TRANS_ALREADY_OPEN), errno=11(Resource temporarily unavailable)
E Fri Jul 08 02:57:16 2016 XXXXX cm:8900 fm_act_schedule_delete.c:290 1:XXXXX:testnap:8897:1:120001:1303734927:1
<location=PIN_ERRLOC_FLIST:6 class=PIN_ERRCLASS_SYSTEM_DETERMINATE:1 errno=PIN_ERR_TRANS_ALREADY_OPEN:37>
<field num=PIN_FLD_POID:7,16 recid=0 reserved=0 reserved2=0 time(sec:usec)=0:0>
<facility=0 msg_id=0 version=0>
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