The repcat command creates and populates the Ingres Replicator catalog tables and creates Ingres Replicator database events. You must run repcat before starting the Replicator Manager for the first time.
The repcat command must be run before you can move the Ingres Replicator configuration from a configuration database to the other participating databases. The repcat command must be run on every Replicator database containing Full Peer or Protected Read-only CDDSs. You do not need to run repcat on databases with only Unprotected Read-only CDDSs.
Note: You can run repcat from a single location by specifying the virtual node name (vnode).
The repcat command has the following format:
repcat [+w|-w] [-udba_name] [vnode::]dbname
Indicates whether to wait for an exclusive lock on the database.
Default: w (do not wait)
Specifies the effective user for the session. You must run repcat as the owner of the database.
Identifies the name of the database, and if required, the vnode, as described in Standard Flags and Parameters.
This command creates and loads Replicator catalogs for the europe database:
repcat europe
This command creates and loads Replicator catalogs for database hq on vnode nyc, with the Replicator database administrator as user:
repcat –urep_dba nyc::hq