Reference to uninitialized composite

Question

Lately we experience intermittent problems deleting data from tables with TAPI/TAPI triggers and CAPI packages (Headstart 6i). When deleting a relatively large number of rows, in this case 900, we get an ORA-06530 error which seems to be caused by the TAPI del procedure. Below is an example of the delete statement and subsequent error.
If we limit the number of rows to be deleted at once to e.g. 100 the problem disappears !
Has anyone experienced a similar problem and does somebody know what the cause and solution is ?
Thank you, Marcel.
delete from gns_demand_values
where cde_id in (select id from gns_customer_demand_structures where cdn_id=38);
delete from gns_demand_values
ERROR at line 1:
ORA-20999:
ORA-06512: at "HST65.CG$ERRORS", line 562
ORA-06512: at "GNS_OWN.CG$GNS_DEMAND_VALUES", line 1007
ORA-06530: Reference to uninitialized composite
ORA-06512: at "GNS_OWN.CG$BDR_GNS_DEMAND_VALUES", line 55
ORA-04088: error during execution of trigger 'GNS_OWN.CG$BDR_GNS_DEMAND_VALUES'
SQL> @messages
Error QMS-00100: Unhandled Exception ORA-06530: Reference to uninitialized composite in PL/SQL Program Unit cg$GNS_DEMAND_VALUES.del.others
Contact Helpdesk
PL/SQL procedure successfully completed.

Answer 1

CDM RuleFrame is optimized for very fast interactive processing. There are a number of known issues related to performance of the CAPI during batch operations. In the Headstart User Guide, in the Business Logic Layer section, we have documented a number of strategies to address this problem. It sounds like you are probably running into some kind of stack overflow. That would explain why both limiting the number of rows processed and disabling the rules in question both resolve the problem.
Regards,
Lauri