DSMSERV INSERTDB (Move a server database into an empty database)
Use the DSMSERV INSERTDB utility to move a server database into a new database. The database can be extracted from the original server and inserted into a new database on the new server by using a network connection between the two servers. The database can also be inserted from media that contains the extracted database.
Before you use the DSMSERV INSERTDB utility, complete the planning and preparation tasks, such as backing up the database and saving configuration information. Ensure that you meet all requirements before you move the server database.
Requirements for insertion by using media
- The manifest file from the DSMUPGRD EXTRACTDB operation must be available.
- If the manifest file does not contain device configuration information,
or if you are specifying the CONFIGINFO=DEVCONFIG parameter,
both of the following statements must be true:
- The server options file must contain an entry for the device configuration file.
- The device configuration file must have information about the device class that is specified in the manifest file.
- The media that contains the extracted database must be available to the version 8 server. Also, the permissions must be set to grant access to the media for the user ID that owns the version 8 server instance.
Syntax
Parameters

-u
user_name
Specifies a user name to switch to before initializing the server. This parameter is
optional.
-i
instance_dir
Specifies an instance directory to use. This directory becomes the current working directory of
the server. This parameter is optional.
-k key_name
Specifies the name of the Windows registry
key from which to retrieve information about the server. This parameter
is optional. The default is SERVER1.- -o options_file
- Specifies an options file to use. This parameter is optional.
- -noexpire
- Specifies that expiration processing is suppressed when starting. This parameter is optional.
- -quiet
- Specifies that messages to the console are suppressed. This parameter is optional.
- DEVclass
- Specifies a sequential-access device class. You can specify any device class except for the DISK
device class. The definition for the device class must exist in either the manifest file or the
device configuration file.This parameter is optional and is used only when the database that you want to insert into the empty version 8 database was extracted to media. If the database is on media and you do not specify a device class, the device class that is identified in the manifest file is used.Restriction: You cannot use a device class with a device type of NAS or CENTERA.
- MANifest
- Specifies the location of the manifest file. Use a fully qualified file name, or place in a
local directory. For example: ./manifest.txt
This parameter is required when the database that you want to insert into the empty version 8 database was extracted to media.
- CONFiginfo
- Specifies the source of the device configuration information that
is used by the DSMSERV INSERTDB operation. The
default value for this parameter is MANIFEST.
Possible values are as follows:
- MANifest
- Specifies that device configuration information is read from the manifest file. If the manifest file does not have device configuration information, the device configuration file is used instead.
- DEVConfig
- Specifies that device configuration information is read from the device configuration file.
- SESSWait
- Specifies the number of minutes that the version 8 server waits to be contacted by the original
server. The default value is 60 minutes.
Use this parameter only if the data that is inserted into the empty version 8 database is transmitted from the source server with a network connection.
- PREview
- Specifies whether to preview the insertion operation. This parameter
is optional. The default value is NO.
Use the PREVIEW=YES parameter to test a database. When you use this parameter, the operation includes all steps of the process, except for the actual insertion of data into the new database. When you preview the insertion operation, you can quickly verify that the source database is readable. You can also identify any data constraint violations that might prevent an upgraded database from being put into production.
