Paradyne 6800 manual Cleaning Up the Database

Performing Migration

•ATR Phone Directories

•Historic Alerts

•Network Summary Categories and Labels

•Trouble Tickets

•Port Configuration

NOTE

User-specified information associated with the unnamed site will not be migrated from Release 2 to Release 4.2. The user must re-enter any such information after the migration is complete.

The following databases will not be migrated:

•The active alerts database will not be migrated because the Release 4.2 NMS generates up-to-date active alert data at system start-up

•Routines

•Network Control Task scheduled items

•Network Control Task results queue

•Alert Driven Routines

•Reports/Trouble Tickets customized with 4GL or SQL

Cleaning Up the Database

Since the databases not migrated were drastically redesigned in Release 3.1, the customer should print a hard copy of routines and scheduled items to assist in recreating these items, if necessary. For scheduled items, perform the List Schedule Items (lssi) command to assist in rebuilding them. For facility profiles, facility types and ACCULINK validation, perform the List Facility Profile (lsfp) command. For Trouble/Inventory Reports and Trouble Tickets that have been customized, back up the files and copy them to a removable medium.

Backing Up the Database

The data to be migrated to the Release 4.2 6800 Series NMS is downloaded to a cartridge tape using the backup utility provided on a Release 4.2 migration diskette. The data is then uploaded to Release 4.2 via a cartridge tape and the migration utility of Release 4.2. Data transfer is nondestructive; no data on the source NMS is modified or deleted.

Use the following procedure to backup the Release 2 database:

1.TYPE: cd /usr/nms/adm

PRESS: Enter

2.Insert the Release 4 migration floppy disk into the Release 2 host processor.

6800-A2-GN22-30 January 1997 7-17