repdbcfg Command—Configure Multiple Mobile Databases

The repdbcfg command allows you to configure multiple Ingres mobile databases simultaneously from the operating system prompt of the host machine to which Ingres Replicator on mobile Replicator will connect.

Note: In Full Peer situations, the paths created by repdbcfg will not be sufficient to permit all changes from each mobile database to be replicated to all other mobile databases. For more information, see the Replicator User Guide.

The repdbcfg command has the following format:

repdbcfg [vnode::]dbname filename [-udba_name]

• vnode::dbname

  Specifies the name of the database to be configured.

• filename

  Specifies the name of the input file.

The input file should have the following format:

user_name [db_no] [dbname] [cdds_no] [target_type]

where:

• user_name

  Specifies the user name of the owner of the mobile database. The user_name must be unique and 32 characters or less.

• db_no

  Specifies the number of the mobile database.

  The optional db_no must be a number in the range of 1-32,767 that has not already been used in your Replicator configuration (dd_databases table). If db_no is not provided on the first line in the file, repdbcfg uses 101 as a default or the next higher number that does not exist in dd_databases. If db_no is not specified on subsequent lines, the previous value incremented by one is used.

• dbname

  Identifies the name of the mobile database. The optional dbname should be a unique database name up to 32 characters long. If it is not provided, the user_name is used as the default database name. The node name for all mobile databases is "mobile."

• cdds_no

  Specifies the number of the CDDS for the mobile database.

  The optional cdds_no should be a number in the range of 1-32,767. It should already be defined in the dd_cdds table through the CDDS Detail screen. If it is not provided on the first line, repdbcfg uses 50 as the default. If it is not provided on subsequent lines, the previous value is used.

• target_type

  Specifies the CDDS target type of the mobile database. Valid values are:

  FP – Full Peer
  PR – Protected Read-only
  UR – Unprotected Read-only

  Default: If target_type is not provided on the first line, the default is FP. If it is not provided on subsequent lines, the default is the previous value.

  For each target_type, repdbcfg creates a data propagation path, under the given or default CDDS, from the local database to the mobile database. If the target_type is FP, repdbcfg creates an additional path from the mobile database to the local database.

repdbcfg Examples

1. In this example, repdbcfg is invoked against an input file containing 26 user names:

   albert

   barbara

   charlie

   …

   zoe

   The repdbcfg utility defines 26 new full peer mobile databases, numbered 101 through 126. Connection names are in the form "mobile::charlie." Data propagation paths are added for CDDS 50 to and from the local database and each new mobile database. If the local database number is 5, the first four paths are 5-5-101, 101-101-5, 5-5-102, and 102-102-5.

2. In this example, the repdbcfg uses the input file:

   albert 201 albert 3 FP

   barbara

   charlie 301 charlie 4 PR

   daniel

   The repdbcfg utility defines four new mobile databases numbered 201, 202, 301, and 302. The first two are full peer and each has two data propagation paths for CDDS 3. The other two databases are protected read-only and each has one propagation path for CDDS 4.