NDS records processing is activated by the database polling composite GetNDSRecordsOUCCBUtilitiesEBF (see the Processing Details section above) which periodically checks the status field of the activation record in the OUCCB_NDS_PROCESS_ACTIVATION table.

The Ready status triggers the start of the polling process. Immediately after the composite starts, the status is changed to Processing. After the polling process completes successfully, it changes the status back to Ready.

If any error occurs, regular error handling actions are performed, and the administrator is notified. The status of the activation record is not changed back to Ready and remains as Processing. This is done to prevent possible duplicating of error notifications.

When any error report from the polling process is detected, it is recommended that you review the activation record status. After fixing the issue, revert the status back to Ready.

During bulk NDS records processing, the polling composite may take a significant amount of time to finish. If the SOA server goes down unexpectedly or the composite was stopped from the Enterprise Manager console before the polling composite completed processing, the process may not complete the normal status reset and the status will be stuck in Processing. In this case, the administrator needs to manually revert the status manually back to Ready.

When processing an error, a standard error message is created (message number 9805, category number 11011). This message contains one parameter - faulted BPEL process ID. This information is inserted into CI_NT_DWN_EXC, CI_NT_DWN_EXP tables and is displayed in Oracle Utilities Customer Care and Billing via the NDS record user interface.