Creating a Second Set of Tables

Occasionally, sites create a test environment that includes a second set of client control tables. Even though the second set of tables may coexist with the production environment, this type of test environment can negatively impact the performance of your production database and is not recommended.

Creating a second set of client control tables in the same relational database requires a separate database user ID. You must keep the working directories for the two user IDs separate. Because table name duplications are allowed when using different user IDs, this can lead to script files with the same names. If you create a set of client control tables by running a configure command under the user ID "usera", those tables will be owned by usera (for example, USERA.DATASOURCES). If you later attempt to use the user ID "userb" to run a configure command, the following message appears:

ERROR: DATABridge control tables exist under another user, command aborted - To bypass this test use the 'u' option for the configure command

At this point, you can run a configure command, as follows:

dbutility -u configure

The DATABridge Client creates a new set of client control tables owned by userb (for example, USERB.DATASOURCES). From here on, the usera and userb tables are treated independently of each other.

The -u option is also explained in dbutility Command-Line Options.