Troubleshooting Table

The following table lists some common problems and their solutions.



You made changes to the client control tables, such as changing the active column value, but none of your changes are taking effect.

This problem, which only occurs when using SQL*Plus in an Oracle database, is an indication that your SQL statements did not get "committed." The default mode of operations of SQL*Plus is transaction mode. SQL statements only get committed when you explicitly issue a commit or when you exit SQL*Plus. You can make the program automatically issue a commit after every SQL statement by typing set auto[commit] on.

You changed one or more table names, but the new tables are empty after you do a clone or an update.

Most likely you did not update the table_name columns in the DATAITEMS client control table.

You have the correct host name, port number, and data source name, but you still cannot connect to the host.

Make sure the domain name server is running. If the domain name server is down, change the host name in the DATASOURCES table to the IP address and try the dbutility command again.

You get a "constraint violation" error when you run the process command to update the relational database.

Most likely you have placed a constraint on one of the columns in the DATABridge data tables. When this occurs, remove the constraint and reclone the data set to get all of the records.

Important: You must not place constraints or other restrictions on any DATABridge data table. If you do, DATABridge will not work. Instead, filter rows on the host using the DBGenFormat utility.

The DATABridge Client becomes unresponsive at the following message:

Begin populating/updating database from AFN=afn, ABSN=absn, INX=inx, SEG=seg, DMSII Time=time_stamp

Check the host ODT for a waiting entry from the Server Accessory, similar to the following:

(usercode) DBSERVER/WORKER-n
NO FILE (usercode)databasename-AUDITnnnn

In this case, make the audit file available to the DBEngine. For example, if the file is on tape, copy it to the usercode indicated for the AUDITnnnn file. Once you make the audit file available, the DBEngine automatically begins processing again.

If for some reason you cannot make the audit file available, stop running the DATABridge Client by typing Ctrl+C on the client system.

You are running multiple DATABridge Clients, and all of them seem to stop processing.

Most likely, only one of the DATABridge Clients has stopped processing because of a problem, and the other DATABridge Clients have stopped not because of a processing problem, but because of a resource contention problem on the host or network.

To correct this situation, look at the ODT and at the Windows Event Viewer for messages related to the DATABridge Client. (The previous two problem descriptions in this table list possible messages.)

When you locate and respond to the message for the problem client, the other clients start processing automatically from where they left off.

You are unable to execute the dbutility program.

Make sure you have included the DATABridge Client program directory in the operating system’s PATH environment variable.

The DATABridge Client gets an index creation error for a table that uses a legitimate DMSII SET as an index.

There is no guarantee that the DBEngine will always produce tables without duplicate records at the end of the data extraction phase.

Most of the time, duplicate records occur when records are deleted and later reinserted into the data set (this sometimes occurs in environments where the DMSII applications use delete/create pairs or in compact data sets). If a record ends up in a location that is different from the original one, the DBEngine sees it twice, resulting in a duplicate record.

When this problem occurs, use the procedure described in Using SQL Query to Find Duplicate Records to query for duplicate records and remove them.

Alternatively, you can clone the data set when the database is inactive or clone the data set offline (the DATABridge Host Administrator’s Guide provides information about cloning offline).

The DATABridge Client stops at the start of the fixup phase with the following error:

Stopping: Errors occurred during data extraction

The DATABridge Client stops at this point if records were discarded. There are two types of discards:

  • Discards created by the DATABridge Client because of data errors in items used as keys.
  • Discards created by the bulk loader because of internal errors. This type of error typically does not occur. If it does occur, it indicates that the program failed to detect a data error.

    The DATABridge Client stops so that you can review these errors. You can fix the data in the discard files that the DATABridge Client creates and load the records using a relational database query tool. Alternatively, you can fix the bad data on the mainframe and let the normal update processing take care of things. If you restart the process command, the fixup phase proceeds normally.

The DATABridge Client stops at the start of the fixup phase with the following error:

Stopping: Errors occurred during index creation

The DATABridge Client stops at this point if one or more index creations fail. You need to determine why the index creation failed and remedy the situation, if possible. For example, if you did not have a large enough TEMP SEGMENT in Oracle, increase its size and execute the index creation scripts using SQL*Plus. Once the indexes are created, you can change the ds_mode of the affected data sets to 1 and resume the process command, which proceeds normally.

Tables that do not have indexes do not cause the DATABridge Client to stop at the beginning of the fixup phase. The DATABridge Client deselects such data sets before entering the fixup mode. Any subsequent process commands will not select such data sets unless you fix the problem and set their mode to 1. You can reclone such data sets at anytime.

The DATABridge Client stops at the start of the fixup phase with the following error:

Stopping: Errors occurred during data extraction and index creation

This message indicates that both of the last two conditions have occurred.