Restoring remote database schemas

After restoring the IBM i5/OS profile, restore the remote database schema.

To restore the remote database schema:

Before restoring the saved version of the WebSphere Portal profile, this script renames Integrated File System (IFS) data associated with the existing profile, and duplicates the schema data. This protects against the case where the user specifies the wrong profile name and the wrong profile is restored. To avoid unnecessarily using up storage on your system, delete the renamed and duplicated data after you have verified that the restore occurred successfully (check the log file for details on the renamed profile data).

In addition, you can specify the -x parameter to prevent the schema data for the profile from being duplicated.

  1. If WebSphere Portal is not installed on the system containing the remote schemas, copy the /QIBM/ProdData/PortalExpress/V61/Tools file from a system where WebSphere Portal is installed to a location in the IFS where the remote database schemas are located.

  2. Type STRQSH on the command line to start the QShell Interpreter.

  3. Change to the directory containing the restoreRemoteDb.sh file.

    If WebSphere Portal is not installed on the system, change to the directory where you copied the rstRmtDb.sh file.

    If WebSphere Portal is installed on the system, change to the /QIBM/ProdData/PortalExpress/V61/Tools directory.

  4. Enter the restoreRemoteDb.sh parameters command to back up your profile: Use the following parameters listed in the table with the above task; the following parameters are required:

    -schemaList (-t)

    List of schemas to restore. Schemas listed must be separated by a comma with no spaces.

    -mediaDevice (-m) and -date (-d), or -saveFileLib (-s)

    Specifies the media device where the profile is save, the date the profile was saved, or the library where the saved profile is stored

    The library name must be 10 characters are less.

    Parameter names are case-sensitive.


    Table 1. Optional parameters for use with the script restoreRemoteDb

    Parameter Description
    -help (-h)

    Displays help for the command.

    -logDir (-l)

    Specifies where to save log files for this command.

    If a log directory is not specified using this parameter, logs are created by default in /savRstWp60.

    If you specify a path using this parameter, the command will create only the last directory in the path. The other directories in the path must already exist.

    For example, if you specify -l /wcs01/logs, the /wcs01 directory must already exist.

    -noSaftyNet (-x)

    Do not duplicate existing schema data.

    By default, the command duplicates existing schema data before deleting it. This protects against the case where the user enters the wrong profile name and the wrong profile is restored. Only use this parameter if you wish to prevent this duplication from happening.

    -seqNum (-q)

    Specifies the starting sequence number of the file set you want to restore. Normally you will not need this parameter, but if you saved multiple copies of the same instance on the same day on the same tape, you may need to distinguish which save set you want. This parameter is only valid with -m option and the media device must be a tape drive.

    -verify (-v)

    Verifies the command. If this parameter is used, the command outputs what would be done according to the parameters being used, without actually performing the restore.

  5. Check the log file to verify that the script completed successfully. After verifying that the restore is complete, delete any renamed profile data.


Examples

restoreRemoteDb.sh -saveFileLib savlib1 -schemaList lib1,lib2,lib3,lib4,lib5,wcs01,wcs02,wcs03

In this example, 8 schemas are restored from library savlib1.


Parent topic:

Backing up and restoring profiles