NPAC-LSMS Download Procedure

Use the following procedure to perform a download of files from an NPAC to the LSMS. The example output shown in the procedure is for Time Range BDD files that include Number Pooling Efficient Data Representation (EDR). File formats for other download types vary, as described in File Naming Conventions. For more information about EDR, refer to the Database Administrator's Guide.
Note: Before you start this procedure, it is recommended that you contact the My Oracle Support (MOS). If you encounter any problems in the procedure, you must call the My Oracle Support (MOS).
CAUTION: The following procedure requires the connection between the LSMS and each regional NPAC that needs to have files downloaded be aborted (when you stop the regional agent in step 26) before the NPAC builds the files to be sent to the LSMS. The connection must be aborted so that data can be properly resynchronized after the download of files completes. Therefore, the normal transmission of NPAC data from the LSMS to the connected NEs will temporarily be precluded during this procedure. It is recommended that you contact the My Oracle Support (MOS) before performing this procedure.
Note: If an automatic or manual switchover occurs while files are being downloaded from the NPAC or between the time files are downloaded from the NPAC and the time they are imported into the LSMS database, perform the appropriate procedure described in “Copying Files to Other Server If Switchover Occurs”.
  1. Ensure that you have the necessary information, as described in “Prerequisite Information”.
  2. Log in to the LSMS active server as lsmsadm.
  3. Change to the directory that contains the current LSMS version:

    $ cd /var/TKLC/lsms/free/data/npacftp/<region>

  4. Verify that the correct directory was accessed by entering the following command:

    $ pwd

    The correct output is:

    /var/TKLC/lsms/free/data/npacftp/<region>

  5. Determine whether any files are currently contained in this directory:

    $ ls -l

  6. If the output shows any files, delete them by entering the following command:

    $ rm *
    Note: Though the steps in this procedure refer to the use of FTP, you may use SFTP instead.

  7. Use FTP to connect to the NPAC by entering the following command, where <NPAC_IP_address> is the decimal version of the NPAC’s IP address, recorded on your worksheet, as described in “Prerequisite Information”:

    $ ftp <NPAC_IP_address>

    An example command line follows:

    $ ftp 208.143.38.10

  8. When prompted, enter your NPAC login name and password, recorded on your worksheet, as described in “Prerequisite Information”.
  9. Change to the NPAC’s FTP directory by entering the following command, where <NPAC_FTP_directory> is the regional directory as recorded on the your worksheet that corresponds to the region selected in 3:

    ftp> cd <NPAC_FTP_directory>

  10. Display the contents of the NPAC’s FTP directory by entering the following command:

    ftp> ls
    • Output similar to the following appears.
      200 PORT command successful.
150 Opening ASCII mode data connection for file list.
000000-999999.07-11-2004023849.07-10-2004023849.07-11-2004023849
0000000-9999990.07-11-2004023849.07-10-2004023849.07-11-2004023849
LRN.07-11-2004023849.07-10-2004023849.07-11-2004023849
NPANXX.07-11-2004023849.07-10-2004023849.07-11-2004023849
NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849
SPID.07-11-2000023849
226 Transfer complete.
70 bytes received in 0.026 seconds (2.6 Kbytes/s)
    • If you are converting a regional database to support EDR, output similar to the following appears:
      200 PORT command successful.
150 Opening ASCII mode data connection for file list.
0000000-9999990.07-11-2004023849.07-10-2004023849.07-11-2004023849
NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849
226 Transfer complete.
20 bytes received in 0.026 seconds (2.6 Kbytes/s)

  11. Change to noninteractive mode by entering the following command:

    ftp> prompt

    Output similar to the following appears: 

    Interactive mode off

  12. Transfer the files you need as follows:

    • If you are downloading files from the NPAC after a site failure, enter the following command to transfer all the files in the NPAC’s FTP directory <NPAC_FTP_directory> to the LSMS’s regional directory /var/TKLC/lsms/free/data/npacftp/<region>:

      ftp> mget *

    • If you are reversing an NPA split, enter commands similar to the following commands (these commands use the values from the example) to transfer the subscription files and NPB files for the old NPANXX and the erroneous new NPANXX from the NPAC’s FTP directory <NPAC_FTP_directory> to the LSMS’s regional directory /var/TKLC/lsms/free/data/npacftp/<region>:

      ftp> mget 909860*

      ftp> mget 123860*

      ftp> mget 124860*

    • If you are converting a regional database to support EDR, enter the following commands to transfer the EDR files from the NPAC’s FTP directory <NPAC_FTP_directory> to the LSMS’s regional directory /var/TKLC/lsms/free/data/npacftp/<region>:

      ftp> mget 0000000-9999999*

      ftp> mget NPANXXX*

  13. Output similar to the following appears (the example shows only Time Range BDD files for downloading):

    200 PORT command successful.
150 Opening BINARY mode data connection for 000000-999999.07-11-2004023849.07-10-2004023849.07-11-2004023849 (17979 bytes).
###
226 Transfer complete.
local: 000000-999999.07-11-2004023849.07-10-2004023849.07-11-2004023849 
remote: 000000-999999.07-11-2004023849.07-10-2004023849.07-11-2004023849
17979 bytes received in 0.18 seconds (le+02 Kbytes/s)
200 PORT command successful.
150 Opening BINARY mode data connection for 
0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849 
(17979 bytes).
###
226 Transfer complete.
local: 0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849 
remote: 0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849
17979 bytes received in 0.18 seconds (le+02 Kbytes/s)
200 PORT command successful.
150 Opening BINARY mode data connection for LRN.07-10-2000023849 
(17979 bytes).
###
226 Transfer complete.
local: LRN.07-11-2004023849.07-10-2004023849.07-11-2004023849 
remote: LRN.07-11-2004023849.07-10-2004023849.07-11-2004023849
17979 bytes received in 0.18 seconds (le+02 Kbytes/s)
200 PORT command successful.
150 Opening BINARY mode data connection for NPANXX.07-11-2004023849.07-10-2004023849.07-11-2004023849 (124831 bytes).
################
226 Transfer complete.
local: NPANXX.07-11-2004023849.07-10-2004023849.07-11-2004023849 
remote: NPANXX.07-11-2004023849.07-10-2004023849.07-11-2004023849
124831 bytes received in 1 seconds (1.2e+02 Kbytes/s)
200 PORT command successful.
150 Opening BINARY mode data connection for NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849 (124831 bytes).
################
226 Transfer complete.
local: NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849 
remote: NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849
124831 bytes received in 1 seconds (1.2e+02 Kbytes/s)
200 PORT command successful.
150 Opening BINARY mode data connection for SPID.07-10-2004023849 (479 bytes).
#
226 Transfer complete.
local: SPID.07-10-2004023849 remote: 07-10-2004023849
479 bytes received in 0.018 seconds (27 Kbytes/s)

  14. Exit FTP by entering the following command:

    ftp> quit

  15. Ensure that the files just downloaded have appropriate permissions for all users by entering the following command:

    $ chmod 655 *

  16. Enter the following command to verify that all the files in 12 transferred and that they now have read-write permission:

    $ ls -l

    Output similar to the following appears (the example shows only Time Range BDD files for downloading): 

    total 3188358
-rw-r-r-  1 lsmsadm  lsms 1608000001 Jul  11 02:38 000000-999999.07-11-2004023849.07-10-2004023849.07-11-2004023849
-rw-r-r-  1 lsmsadm  lsms 1608000001 Jul  11 02:38 0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849
-rw-r-r-  1 lsmsadm  lsms 780001     Jul  11 02:38 LRN.07-11-2004023849.07-10-2004023849.07-11-2004023849
-rw-r-r-  1 lsmsadm  lsms 6440001    Jul  11 02:38 NPANXX.07-11-2004023849.07-10-2004023849.07-11-2004023849
-rw-r-r-  1 lsmsadm  lsms 6440001    Jul  11 02:38 NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849
-rw-r-r-  1 lsmsadm  lsms 239990     Jul  11 02:38 SPID.07-10-2000023849
    Note: It is recommended that you create a backup of your files before proceeding to the next step. To create a backup, enter the following command:

    $ mkdir /var/TKLC/lsms/free/data/npacftp/<region>/save

  17. If you need files from another NPAC region, repeat 3 through 16.
  18. If switchover has occurred, perform the appropriate procedure described in “Copying Files to Other Server If Switchover Occurs”.
  19. Untar the BDD file (Object Range BDD file or Time Range BDD file) in the <region> folder using the following command:

    tar –zxvf filename.tar.gz

  20. Enter the following command to display the number of lines in each bulk load file.

    $ wc -l *
    Note: Record the line count values (shown in bold below) for future reference.
        1892 000000-999999.07-11-2004023849.07-10-2004023849.07-11-2004023849
      0 000000-999999.07-11-2004023849.07-10-2004023849.07-11-2004023849
    892 0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849
      0 0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849
    250 LRN.07-11-2004023849.07-10-2004023849.07-11-2004023849
      0 LRN.07-10-2004023849.07-11-2004023849
     23 NPANXX.07-10-2004023849.07-11-2004023849
      0 NPANXX.07-10-2004023849.07-11-2004023849
     12 NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849
      0 NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849
      0 SPID.07-10-2004023849

  21. BDD files received from the NPAC require conversion before they can be imported into the LSMS database.

    The conversion must be performed by entering the following command for each file:

    $ cat orig_file_from_NPAC | tr "\015" "\012" > new_file_for_import

    (The file name must be changed. Oracle recommends that you append a few characters, such as .tr, to the end of the file name. Maintaining most of the file name will make it easier to rename the files to the original file names, as instructed in 23) For example: 
    $ cat 000000-999999.07-10-2000023849 | tr "\015" "\012" > 000000-999999.07-11-2004023849.07-10-2004023849.07-11-2004023849.tr
$ cat 0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849 | tr "\015" "\012" > 0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849.tr
$ cat LRN.07-10-2000023849 | tr "\015" "\012" > LRN.07-11-2004023849.07-10-2004023849.07-11-2004023849.tr
$ cat NPANXX.07-11-2004023849.07-10-2004023849.07-11-2004023849 | tr "\015" "\012" > NPANXX.07-11-2004023849.07-10-2004023849.07-11-2004023849.tr
$ cat NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849 | tr "\015" "\012" > NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849.tr
$ cat SPID.07-10-2004023849 | tr "\015" "\012" > 
SPID.07-10-2004023849.tr

  22. After ensuring all files have been converted, delete the original files.

    $ rm orig_file_from_NPAC

    For example:

    $ rm 000000-999999.07-11-2004023849.07-10-2004023849.07-11-2004023849
$ rm 0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849
$ rm LRN.07-11-2004023849.07-10-2004023849.07-11-2004023849
$ rm NPANXX.07-11-2004023849.07-10-2004023849.07-11-2004023849
$ rm NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849
$ rm SPID.07-10-2004023849

  23. Rename each of the files that were converted in 21 back to the original NPAC file names by entering the following command for each file:

    $ mv new_file_for_import orig_filename_from_NPAC

    For example: 

    $ mv 000000-999999.07-11-2004023849.07-10-2004023849.07-11-2004023849.tr
 000000-999999.07-11-2004023849.07-10-2004023849.07-11-2004023849
$ mv 0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849.tr 0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849
$ mv LRN.07-11-2004023849.07-10-2004023849.07-11-2004023849.tr LRN.07-11-2004023849.07-10-2004023849.07-11-2004023849
$ mv NPANXX.07-11-2004023849.07-10-2004023849.07-11-2004023849.tr NPANXX.07-11-2004023849.07-10-2004023849.07-11-2004023849
$ mv NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849.tr NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849
$ mv SPID.07-10-2004023849.tr SPID.07-10-2004023849

  24. Verify that the files were properly converted by entering the following command:

    $ file *
    Properly converted files will be appended with the following information, : ASCII text, as shown in the example output below. 
    000000-999999.07-11-2004023849.07-10-2004023849.07-11-2004023849: ASCII text
000000-999999.07-11-2004023849.07-10-2004023849.07-11-2004023849: ASCII text
0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849: ASCII text
0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849: ASCII text
LRN.07-11-2004023849.07-10-2004023849.07-11-2004023849: ASCII text
LRN.07-10-2004023849.07-11-2004023849: ASCII text
NPANXX.07-10-2004023849.07-11-2004023849: ASCII text
NPANXX.07-10-2004023849.07-11-2004023849: ASCII text
NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849: ASCII text
NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849: ASCII text
SPID.07-10-2004023800: ASCII text
SPID.07-10-2004023849: ASCII text
    Note: If the files are appended with : ASCII text, with CR line terminators, then the conversion performed in 21 failed. Contact the My Oracle Support (MOS).

  25. If switchover has occurred, perform the appropriate procedure described in “Copying Files to Other Server If Switchover Occurs”.
  26. If the SWIM feature has been enabled, contact the My Oracle Support (MOS) to turn off SWIM.
  27. Perform the following substeps to prevent the NPAC database from being updated while the files are being converted and copied in subsequent steps:
    1. Halt the LSMS agent for the region:

      $ $LSMS_DIR/lsms stop <region>

    2. From the LSMS GUI menu, select Configure>LNP System>NPAC>Modify>Primary and click the Activate Region checkbox so that is empty.

      For more information about this GUI window, refer to the Configuration Guide. Having this checkbox empty prevents the sentryd utility from attempting to automatically restart the regional agent.

  28. You are now ready to run the import command.

    Note: Do not run the import command while any of the following processes are also running: backups, starting a standby node (to change its state from UNINITIALIZED "INHIBITED" to STANDBY), running the lsmsdb quickaudit command, and creating query server snapshots, all of which use temporary storage space. If you try to run the import command while any of these processes are running, you may not have enough disk space to complete the process. Since backups can be run automatically, perform the procedure described in “Checking for Running Backups” to ensure that no backups are running.

    • If you are performing this procedure as part of reversing an NPA split, converting a regional database to support EDR, importing an incremental download of files from NPAC after a site failure, or importing files for any reason other than a complete regional bulk download, go to 29.
    • If you are performing a complete regional bulk download from the NPAC, you can save a significant amount of time (which would be required to delete all existing entries in the database) by entering the following commands, where <region> is the name of the NPAC region:
      CAUTION: The following commands will delete all data in your regional database.

      Log into the active server and run both of the following commands:

      $ $LSMS_DIR/npac_db_setup remove <region>

      $ $LSMS_DIR/npac_db_setup_create <region>

  29. Import data in the downloaded files into the regional database by entering the following command:

    $ $LSMS_DIR/import [-c] <region>

    For example:

    $ $LSMS_DIR/import -c MidAtlantic

    The -c option allows the import to continue on to the next line of the file even if errors occur. Output similar to the following indicates the progress of the LSMS processing:

    Note: In these examples, … on a line by itself indicates that output occurs, but its contents are not significant to this procedure.
    Note: If you do not specify the -c option and a failure, such as a syntax error, occurs during the import process, an error message is displayed and the import utility prompts the user with the following message: Do you want to continue (Yes/No)? If n is entered, the import utility operation is aborted. If y is entered, the import utility aborts its operation for the current download file and continues importing the remaining specified download files.

    If such an error occurs, be sure to perform the substeps shown in 30.

    • Output similar to the following appears as the LSMS deletes subscription versions, NPBs, LRNs, NPANXXs, and SPIDs in the regional LSMS database, reformats the NPAC data file, and places the data from the NPAC data file into the specified regional LSMS database.
      NPAC FTP directory: /var/TKLC/lsms/free/data/npacftp/Midwest
The following NPAC download file(s) are available for import:
            LRN.07-11-2004023849.07-10-2004023849.07-11-2004023849
           NPANXX.07-11-2004023849.07-10-2004023849.07-11-2004023849
        NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849             
SPID.07-10-2004023849
  000000-999999.07-11-2004023849.07-10-2004023849.07-11-2004023849     
0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849
Import LRN.07-11-2004023849.07-10-2004023849.07-11-2004023849 (Yes/No/All/Quit)?all
The following NPAC download files have been chosen to be imported:
           SPID.07-10-2004023849          
NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849 
       NPANXX.07-11-2004023849.07-10-2004023849.07-11-2004023849              
LRN.07-11-2004023849.07-10-2004023849.07-11-2004023849
  000000-999999.07-11-2004023849.07-10-2004023849.07-11-2004023849  
0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849
Do you want to continue (Yes/No)?yes
Beginning Delete Process for SPID.07-10-2004023849
Delete Process Completed for SPID.07-10-2004023849
Beginning Download Process for SPID.07-10-2004023849
1000 ServiceProvNetwork instances written to MidwestDB
2000 ServiceProvNetwork instances written to MidwestDB
2351 ServiceProvNetwork instances written to MidwestDB

Import completed successfully.
Download Process Completed for SPID.11-07-2001145342

Beginning Delete Process for NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849
Delete Process Completed for NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849

Beginning Download Process for NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849

1000 ServiceProvNPA_NXX_X instances written to MidwestDB
2000 ServiceProvNPA_NXX_X instances written to MidwestDB
3000 ServiceProvNPA_NXX_X instances written to MidwestDB
4000 ServiceProvNPA_NXX_X instances written to MidwestDB
…
30000 ServiceProvNPA_NXX_X instances written to MidwestDB
30860 ServiceProvNPA_NXX_X instances written to MidwestDB
Import completed successfully.
Download Process Completed for NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849

Beginning Delete Process for NPANXX.07-11-2004023849.07-10-2004023849.07-11-2004023849

Delete Process Completed for NPANXX.07-11-2004023849.07-10-2004023849.07-11-2004023849

Beginning Download Process for NPANXX.07-11-2004023849.07-10-2004023849.07-11-2004023849

90 ServiceProvNPA_NXX instances written to MidwestDB
1090 ServiceProvNPA_NXX instances written to MidwestDB
Import completed successfully.
Download Process Completed for NPANXX.07-11-2004023849.07-10-2004023849.07-11-2004023849

Beginning Delete Process for LRN.07-11-2004023849.07-10-2004023849.07-11-2004023849

Delete Process Completed for LRN.07-11-2004023849.07-10-2004023849.07-11-2004023849

Beginning Download Process for LRN.07-11-2004023849.07-10-2004023849.07-11-2004023849

1000 ServiceProvLRN instances written to MidwestDB
2000 ServiceProvLRN instances written to MidwestDB
3000 ServiceProvLRN instances written to MidwestDB
4000 ServiceProvLRN instances written to MidwestDB
4700 ServiceProvLRN instances written to MidwestDB
5700 ServiceProvLRN instances written to MidwestDB
Import completed successfully.
Download Process Completed for LRN.07-11-2004023849.07-10-2004023849.07-11-2004023849

Beginning Delete Process for 000000-999999.07-11-2004023849.07-10-2004023849.07-11-2004023849

Will drop instances of:
Drop instances of class `SubscriptionVersion'
DROPPING INSTANCES.
Delete Process Completed for 000000-999999.07-11-2004023849.07-10-2004023849.07-11-2004023849

Beginning Download Process for 000000-999999.07-11-2004023849.07-10-2004023849.07-11-2004023849

1000 SubscriptionVersion instances written to MidwestDB
2000 SubscriptionVersion instances written to MidwestDB
3000 SubscriptionVersion instances written to MidwestDB
4000 SubscriptionVersion instances written to MidwestDB
4500 SubscriptionVersion instances written to MidwestDB
Import completed successfully.
Download Process Completed for 000000-999999.11-07-2001145342

Beginning Delete Process for 0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849

Will drop instances of:
Drop instances of class `NumberPoolBlock'
DROPPING INSTANCES.
Delete Process Completed for 0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849

Beginning Download Process for 0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849

1000 NumberPoolBlock instances written to MidwestDB
2000 NumberPoolBlock instances written to MidwestDB
Import completed successfully.
Download Process Completed for 0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849
Script completed.
    • If you are reversing an NPA split, in this step the LSMS deletes all subscription versions and NPBs for the old NPA-NXX and the erroneous new NPA-NXX in the regional LSMS database, reformats the NPAC data file, and places the data from the NPAC data file into the specified regional LSMS database. (Example output is not shown.)
    • If you are converting a regional database to support EDR, in this step the LSMS formats the NPAC data file, and places the data from the NPAC data file into the specified regional LSMS database. (Example output is not shown.)
  30. If you specified the -c option or you answered Y when prompted for any failure, such as syntax error, that occurred during the import process in 29, perform the one of the following sets of substeps:

    CAUTION: This step requires a working knowledge of the vi editor and detailed understanding of the contents of the files downloaded from the NPAC. It is recommended that the My Oracle Support (MOS) be contacted prior to performing this step.

    If you answered Y when prompted for any failure during the import process in 29, perform these substeps:

    1. Examine and correct the files that were not successfully imported by entering the following command:
      $ vi /var/TKLC/lsms/free/data/npacftp/<region>/<downloaded file>

      For example:

      $ vi /var/TKLC/lsms/free/data/npacftp/Midwest/SPID.07-10-2000023849

    2. Delete the ^D characters added at the end of the file by the vi editor by pressing the Shift and G keys at the same time to go to the end of the file, and then typing dd to remove the last line.
    3. For each file corrected by 30 a and b, enter the following command to import the corrected file into the regional database:
      $ $LSMS_DIR/import <region> <bulk load file>
    4. Go to step 31.

    If you specified the -c option in 29, perform these substeps:

    1. Examine and correct the files that were not successfully imported by entering the following command:
      $ vi /var/TKLC/lsms/free/data/npacftp/<region>/<downloaded file>

      For example:

      $ vi /var/TKLC/lsms/free/data/npacftp/Midwest/SPID.07-10-2000023849_FAILED

    2. Correct the file as desired, and then import the file into the database by entering the following command, where <region> is the name of the NPAC region, <instance> is the type of instance to be imported into the database, and <filename> is the name of the file to be imported:
      $ $LSMS_TOOLS_DIR/npacimport -r <region> -i <instance> -y <filename>
  31. If you are reversing an NPA split, go to step 34.

    Otherwise, perform the following substeps:
    NPAC Bulk Load Files and LSMS Database Object Classes

    NPAC Bulk Load File

    LSMS Database Object Class

    000000-999999.07-11-2004023849.07-10-2004023849.07-11-2004023849

    SubscriptionVersion

    0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849

    NumberPoolBlock

    LRN.07-11-2004023849.07-10-2004023849.07-11-2004023849

    ServiceProvLRN

    NPANXX.07-11-2004023849.07-10-2004023849.07-11-2004023849

    ServiceProvNPA_NXX

    NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849

    ServiceProvNPA_NXX_X

    SPID.07-11-2004023849

    ServiceProvNetwork
    These substeps compare the number of instances of each object type (shown in bold in the following examples) contained in the NPAC files and in the LSMS database.

    1. Enter the following command to display the number of lines in each bulk load file:

      $ wc -l *

      Output similar to the following appears:

      • If you are downloading files from the NPAC after a site failure or during migration, output similar to the following appears. This output includes lines (shown in bold) used for Efficient Data Representation (EDR). If an NPAC does not support EDR, or if you do not have the EDR feature installed, lines similar to those shown in bold will not appear. 
             1892
  000000-999999.07-11-2004023849.07-10-2004023849.07-11-2004023849    
     892  0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849         250
  LRN.07-11-2004023849.07-10-2004023849.07-11-2004023849           23
  NPANXX.07-11-2004023849.07-10-2004023849.07-11-2004023849
      12  NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849        5
  SPID.07-10-2004023849
      • If you are converting a regional database to support EDR, output similar to the following output appears. 
         892
  0000000-9999999.07-11-2004023849.07-10-2004023849.07-11-2004023849  12
  NPANXXX.07-11-2004023849.07-10-2004023849.07-11-2004023849

    2. Enter the following command to display the total number of instances of each class in the regional database:

      $ lsmsdb -c counts -d <dbname>

      Output similar to the following appears:

      $ lsmsdb -c counts -d MidwestDB 892
 ........... MidwestDB.NumberPoolBlock 250
 ........... MidwestDB.ServiceProvLRN 23
 ............ MidwestDB.ServiceProvNPA_NXX 12
 ............ MidwestDB.ServiceProvNPA_NXX_X 5
 ............. MidwestDB.ServiceProvNetwork 1,892
 ......... MidwestDB.SubscriptionVersion
#

    3. Verify that the numbers of instances indicated in the output of 31 b (shown in bold in the example) match the numbers included in the output of 31 a (shown in bold in that example). If they do not match, repeat 28 through 30
  32. If you are converting a regional database to support EDR, go to 34.

    Otherwise, perform the following command to change the Last Change Time (LCT) of the regional database to match the timestamp embedded in the file name of the files obtained in 16.

    $ chglct -r <region> -s <YYYYMMDDhhmmss>

    Where <region> is the name of the NPAC for which you are performing the download and <YYYYMMDDhhmmss> is the timestamp embedded in the file name as shown in the files displayed in 16. For more information about the chglct command, see “chglct”.

  33. Once you have verified that the region has received a "Recovery Complete" message from the NPAC, you may remove the "import" files from the system by repeating 2 through 6 of this procedure.
  34. Restart the LSMS agent for the region by doing the following:

    From the LSMS GUI menu, select Configure > LNP System > NPAC > Modify > Primary and click the Activate Region checkbox so that is checked. For more information about this GUI window, refer to the Configuration Guide. Having this checkbox checked enables the sentryd utility to automatically attempt to restart the regional agent.

  35. If the SWIM feature was turned off in 26, contact the NPAC to have the SWIM list cleared for all imported regions, then contact the My Oracle Support (MOS) to reactivate SWIM.
  36. If imports were performed for all active regions, go to 37 Otherwise, contact the My Oracle Support (MOS) to determine if time range resynchronizations are needed for regions that were not imported due to SWIM having been turned off temporarily.

    If necessary, the My Oracle Support (MOS) will help the customer reassociate LSMS with the NPAC and perform manual time range resynchronizations.

  37. Restart the LSMS GUI for the region.
  38. Repeat steps 21 through 37 for each NPAC region for which you have downloaded files.
  39. For each network element supported by the LSMS, resynchronize the data that corresponds to the data downloaded from the NPAC, using one of the procedures described in LNP Database Synchronization User's Guide. For example:

    • If you downloaded from the NPAC after a site failure or during migration, perform a time range audit or a bulk download to each supported network element (refer to “Auditing and Reconciling Network Elements from the LSMS” or “Managing Bulk Load from the LSMS”).
    • If you have reversed an NPA split, perform an audit and reconcile procedure for subscription versions and NPBs in both the old NPA-NXX and the erroneous new NPA-NXX to each supported network element (refer to “Auditing and Reconciling Network Elements from the LSMS”).
    • If you have converted a regional database to support EDR, perform an audit and reconcile procedure for all NPBs to each supported network element (refer to “Auditing and Reconciling Network Elements from the LSMS”).

Parent topic: Downloading Files from an NPAC to the LSMS