Filter
Top Products
Manually Deleting CDRs 299
■ Only the record with ACTIVE_STATUS=1 is submitted. Verify that only
one entry is set to ACTIVE_STATUS=1.
■ Verify that the job_to_submit is CWE.OUTPUT.
■ Verify that the job_interval, file_name, file_path, and col_delimiter
entries are set correctly.
3 From a SQL Plus command line, login as the cwbss user.
4 Enter the following script:
set serveroutput on
begin
CWE.JOB_EXPORT;
end;
The super CDRs are exported as scheduled. Once the super CDR export is
run, the file set as the export file contains the CDR fields specified in the
job_export_fields_map table.
To kill a scheduled job, refer to Manually Dropping a Scheduled Job.l
Manually Deleting
CDRs
The billing support server deletes super CDRs stored in the
rt_super_cdr_status table (and in the rt_cdr, rt_cdr_pointer tables)
based on the configuration of the table supercdr_hold. The
supercdr_hold table determines the amount of time (days) the super
CDRs are saved in database and the total number of super CDRs for each
account_id (or URI_ID). The default holding is 30 days or 100 records for
each account_id (or URI_ID), which ever is less.
The billing support server installation procedure schedules all the
necessary Oracle jobs for the billing support server for default
configuration. If you want to use the default configuration, you do not
need to do any Oracle job scheduling such as uploading CDRs, merging
CDRs into Super CDRs, exporting Super CDRs, and deleting CDRs. If you
do not use the default configuration, you should drop the default
schedules of the Oracle jobs and submit the Oracle jobs following the
instructions in the dedicated sections of this guide.
The supercdr_hold table overrides any data deletion. If the
supercdr_hold table is configured to hold calls for a certain period of
time or up to a certain number of CDRs, the CDRs are held until those
conditions are met. To delete the CDRs immediately, disable the holding
parameters set both the HOLDING_PERIOD and NUM_LIMIT fields in