Polycom 3725-70003-009F Manual De Usuario
Maintaining the ReadiVoice System
Proprietary & Confidential
109
6
Restore the data from the CDR backup file to the cdrcnow database by
entering (all on one line):
/rahome/dbcdr/loadtable.pl DB=cdrcnow <
entering (all on one line):
/rahome/dbcdr/loadtable.pl DB=cdrcnow <
/rahome/cdr/archives/YYYYMMDDhhmmsscdr.log
Replace YYYYMMDDhhmmsscdr.log with the name of the backup file.
7
Change directories to /rahome and enter ./rastart.
8
Log into the Administration interface and use the CDR Data pages to
verify that the records you wanted to restore are there (see
verify that the records you wanted to restore are there (see
Purging Subscriber Records Flagged for Deletion
When you change a subscriber’s status to deleted, either in the Provisioning
interface or with a stored procedure call, the ReadiVoice system doesn’t
actually delete the subscriber from the database; it merely flags the record for
deletion. To actually delete such records from the database, you must run the
interface or with a stored procedure call, the ReadiVoice system doesn’t
actually delete the subscriber from the database; it merely flags the record for
deletion. To actually delete such records from the database, you must run the
subDelete.pl script.
To permanently and irrevocably delete all subscriber records flagged for
deletion:
deletion:
1
Open a Telnet session to the CACS as user cnow.
2
Change to the /rahome/database/scripts directory.
3
Type ./subDelete.pl and press
ENTER
.
All subscriber records flagged for deletion are permanently deleted from
the database.
the database.
Caution!
The subDelete.pl script immediately and permanently deletes all subscriber
records whose status is set to 2 (deleted) in the database. This script does not
create a backup of the deleted records. Be sure you really want to delete these
subscribers. Be sure your provisioning procedures are appropriate (that is, the
guidelines for setting a subscriber’s status to deleted take into account the use of
this script).
records whose status is set to 2 (deleted) in the database. This script does not
create a backup of the deleted records. Be sure you really want to delete these
subscribers. Be sure your provisioning procedures are appropriate (that is, the
guidelines for setting a subscriber’s status to deleted take into account the use of
this script).
Caution!
You can schedule this script as a cron task. But, remember that purged subscriber
records, unlike purged CDRs, can’t be recovered. Therefore, approach the
automatic deletion of subscriber records with caution.
records, unlike purged CDRs, can’t be recovered. Therefore, approach the
automatic deletion of subscriber records with caution.