Error Messages

Error messages generally appear both on-screen and in the log file, unless noted. These messages are prefixed by the timestamp hh:mm:ss, where hh is hours, mm is minutes, and ss is seconds. For messages that appear only in the log, see Appendix B, Log Messages.

Note: Frequently one primary problem causes several secondary problems and results in many error messages. Try to find the earliest error message and solve that problem first before proceeding. In many cases, solving this one problem resolves the other problems without any additional work.

The following table lists possible error messages and provides descriptions/solutions for each of them. Many of the messages in this table are preceded by relational database messages. When that is the case, use your relational database documentation to look up the message. The messages are listed in alphabetical order. However, because error messages you receive contain actual names rather than variable names, you may not find error messages exactly where you expect them to be. In addition, some messages that are common to more than one section are listed under section_name. If you cannot find a particular message listed under the correction section, it may be listed under section_name.

AA value of LINK_AI image does not match that of previous CREATE image for DataSet name[/rectype]

This message, which can occur during a process or clone command, indicates that the AA value in the after image of a DMSII link does not match the AA value of the previous CREATE image for the specified data set record. This situation, which should never occur under normal circumstances, indicates a DATABridge Engine error.

Ambiguous command cmd, matches both cmd1 and cmd2 commands

In response to console input, this message indicates that the text of the command cmd the operator typed matches more than one command. Make sure you type enough characters to make the command unique.

Archive contains a malformed record: record_text

This message can occur during a reload command if the input scanner does not find the record to be in the expected format. If you edited the unload file created by the unload command you are likely to get this message or any of the other reload command error messages. The second line of the message is the record that the program is having a problem with.

Archive file "name" contains no data or cannot be read

This message can occur during a reload command, if an unexpected end of file situation occurs. A possible reason for this would be if the unload command that created the file did not complete the command successfully.

Archive file does not start with a version record of the form "V,version"

This message can occur during a reload command, if the file specified on the command line is not a control table unload file. The first record of this file is always "V,version" where version is the version of the client control tables.

Attempt to clear DTOPT_Nulls_Allowed option for key items failed

The Client does not normally allow keys to have the NULL attribute. This would invalidate the SQL that is used to perform update and delete operations, where the WHERE clauses tests the key items for equality. If the items are NULL, you cannot test them for equality. The client attempts to reset the bit that indicates the item allows nulls. This message is displayed in the unlikely situation where the update statement fails.

Attempt to connect to a NULL data_source; add datasource specification to configuration file

This message indicates that there is no data source specified in the [signon] section of a client that uses ODBC or CLI. You must specify a data source so that the client can connect to the database using ODBC or CLI.

Attempt to delete record from table 'name' during a modify was unsuccessful (AFN=afn, ABSN=absn, SEG=seg, INX=inx) - Keys: columnname = value, …

This message can occur when processing a MODIFY record during change tracking. It indicates that, while handling this request as a delete/insert, the Client encountered an error during the delete operation. See the database API error that precedes this message to determine the reason why the delete statement failed.

Attempt to delete record from table 'name' during a two step modify was unsuccessful (AFN=afn, ABSN=absn, SEG=seg, INX=inx) - Keys: columnname = value, …

This message, which can occur during a process or clone command, indicates that the Client was unable to delete the record from the specified table during a two step modify, which is invoked when the value of the depends item for an item with an OCCURS DEPENDING ON clause changes. If the value of this item decreases, the Client updates the rows that remain in the OCCURS table and deletes the rows that are no longer present. This error appears if the delete operation fails and may appear after other related error messages that need to be fixed first.

Attempt to delete record from table 'name' was unsuccessful (AFN=afn, ABSN=absn, SEG=seg, INX=inx) - Keys: columnname = value, …

This message, which can occur during a process or clone command, indicates that the Client was unable to delete the record from the specified table. This message may appear after other related error messages that need to be fixed first.

Attempt to delete records from table 'name' after a failed insert was unsuccessful (AFN=afn, ABSN=absn, SEG=seg, INX=inx) - Keys: columnname = value, …

This message, which can occur during a process or clone command, indicates that the Client was unable to delete the records from the specified OCCURS table. Only when a delete/insert operation involves an OCCURS table does the Client delete and reinsert all of the entries for a given key. This message may appear after other related messages that need to be fixed first.

Attempt to delete record[s] from table 'name' during a modify was unsuccessful (AFN=afn, ABSN=absn, SEG=seg, INX=inx) - Keys: columnname = value, ...

This message, which can occur during a process or clone command, indicates that the Client was unable to update a record, because it did not exist in the database. When this happens, the insert statement fails; the Client attempts to delete the record and re-insert it, but that also fails and results in this error. This message rarely occurs.

Attempt to drop history table 'name' while "inhibit_drop_history" option is enabled

This message, which can occur during a process or clone command, indicates that the Client attempted to delete a history table while the inhibit_drop_history parameter was set to True. This parameter is designed to safeguard against accidentally dropping history tables.

Attempt to drop index 'name' on table 'name' failed

This message can occur during a process or clone command when a table that has data that needs to be preserved is recloned. When the records need to be preserved in a nonstandard manner, the program drops the index of the table and runs a cleanup script to delete unwanted records instead of dropping the table and recreating it. The most common source of this error is that the table in question does not have an index, possibly because the index creation during the original clone failed. The program traps this error and continues execution after printing a WARNING. Any other type of index error results in this message.

Attempt to drop table 'name' and its procedures failed

This message occurs when an error occurs while the Client attempts to drop a table and its associated stored procedures. In this case, do the following:

Check the relational database message that precedes this error message (on the screen or in the log file).
Use SQL statements to drop the specified table and its associated stored procedures (i_name, d_name, u_name).

Attempt to insert record after failed update was unsuccessful

This message, which can occur during a process or a clone command, indicates that the program was unsuccessful in performing an update because the target record does not exist. The program then tried to do an insert, which also failed because a duplicate was found. If this error occurs, contact Attachmate Technical Support.

Attempt to insert record in table 'name' during a two step modify was unsuccessful

This message can occur during a process or clone command and indicates that the Client could not insert the record into the specified table during the two-step modify. A two‑step modify is used when the value of the depends item changes for an item with an OCCURS DEPENDING on clause. If the value of this item increases, the Client updates the rows that were present in the OCCURS table and inserts the remaining rows. This error appears if the insert operation fails. This message may appear after other related error messages that need to be fixed first.

Attempt to insert record in table 'name' was unsuccessful

This message can occur during a process or clone command and indicates that the Client could not insert the record into the specified table. This error does not apply when the Client encounters a duplicate record while executing the insert SQL statement, because the Client automatically recovers in that situation.

Attempt to insert record into table 'name' was unsuccessful - Keys: columnname = value, ...

This message can occur when a data set is cloned without using the bulk loader. It indicates that an error occurred when the Client tried to insert the record into the table. Refer to the database API error messages for details on why the insert failed.

Attempt to insert record into table 'name' was unsuccessful (AFN=afn, ABSN=absn, SEG=seg, INX=inx) - Keys: columnname = value, ...

This message, which can occur during a process or clone command, indicates that the Client was unable to insert the given record into the table. The Client always attempts to recover from a failed insert that is caused by the record already being in the database. If we get a different error, then this message is displayed and the client stops. Refer to the database API error messages for details on why the insert failed.

Attempt to mark record as deleted in table 'name' failed (AFN=afn, ABSN=absn, SEG=seg, INX=inx) - Keys: columnname = value, ...

This message indicates that the process or clone command (used in conjunction with the delete record preservation feature) was unable to update a record and set the appropriate column to indicate that it has been deleted. Refer to the SQL error messages for clues about why this error occurred.

Attempt to reclone DataSet name[/rectype] without recloning DataSet name1 [/rectype1]

The clone command is attempting to reclone the specified data set and the following conditions exist:

The configuration file parameter automate_virtuals is set to True.
The specified data set is the primary source for a virtual data set that gets its input from more than one DMSII data set.
The data set that is the secondary source of data has been cloned previously and is not specified on the command line.

Recloning is only allowed for the data set that is the secondary source of the data. For example, assume SV-HISTORY and SAVINGS both provide data for the virtual data set SV‑HISTORY-REMAP, and SV-HISTORY is the primary source of data for SV-HISTORY-REMAP that must be cloned first. An attempt to reclone SV‑HISTORY without recloning SAVINGS results in this error. If you want to reclone SV‑HISTORY, you must also reclone SAVINGS. If you specify them both on the command line, the program performs operations in the right order. However, you can reclone SAVINGS without recloning SV-HISTORY.

Attempt to recreate index for table 'name' failed

This message indicates the Client was unable to recreate the index for the specified table name during the drop or dropall command involving a data source that contains tables with records that need to be preserved.

Attempt to run user stored procedure '{m_tablename | r_tablename}' failed

This message, which only applies to MISER databases, can occur during a process or clone command and indicates that an error occurred while running the stored procedure. This message may appear after other related error messages that need to be fixed first.

Attempt to treat duplicate insert record as an update for table 'name' failed (AFN=afn, ABSN=absn, SEG=seg, INX=inx) - Keys: columnname = value, ...

The Client traps all duplicate record errors that occur during the execution of insert SQL statements. It then changes the insert statements into update statements and re-executes them. If the resulting update statement fails, this error message is displayed because it cannot find the target record to change. If this error occurs, contact Technical Support.

Attempt to update table 'name' was unsuccessful (AFN=afn, ABSN=absn, SEG=seg, INX=inx) - Keys: columnname = value, ...

This message, which can occur during a process or clone command, indicates that the Client could not update the specified table. This message may appear after other related error messages that need to be fixed first. This error does not apply to situations where the Client encounters an update with no matching rows; the Client automatically recovers from that situation.

Bad bit (0xhhhhhhhh) in {DataItem | DataSet | DataSource | DataTable | DMSItem } column mask

This message occurs when DBClntCfgServer attempts to update an Client Control Table entry and gets an invalid bit mask. This is an internal error in the Client Console or the Configurator. Contact Attachmate Technical Support.

Bad {index | table} suffix value nn specified for table 'name' in DATATABLES

This message occurs during a generate command if the index_suffix or create_suffix column of the corresponding DATATABLES entry has a value that is out range or there is no [n] specification in the configuration file parameters create_table_suffix and create_index_suffix.

BCP format file entry for item 'name' (dms_item_type = tt) cannot be generated

This message occurs during the generate command if the dms_item_type column of the corresponding DATAITEMS entry is illegal. This is an indication that the entry in question is corrupt. Make sure this is not the result of one of your user scripts. For details on the dms_item_type column, refer to DMS_ITEMS Client Control Table.

Binding of variables failed for SQL statement sql_stmt

This message is only applicable when using host variables, such as setting the configuration parameter aux_stmts to a nonzero value. The error indicates that an internal error occurred while binding program variables to various columns of an SQL statement. In this mode, all SQL statements that call stored procedures use bound variables. Before the SQL statements are actually executed, the vaues are copied into these variables by the program. This technique allows the SQL statement to be re-executed using different data as the SQL remains constant; only the content of the host variables changes.

Bulk copy record count (mmm) and actual record count (nnn) differ for table 'name'

This message, which is only displayed if the configuration parameter verify_bulk_load is set to 2, indicates that there is a mismatch between the number of rows in the table and the number of rows that the client loaded. Look at the bulk loader log file and the discards directory where you will undoubtedly find a discard file for the given table. If the parameter verify_bulk_load is set to 2, this situation causes the client to abend. However, if it set to 1, you only get a similar warning and the client ignores the error.

Bulk load failure for dataset name[/rectype]

This message indicates that there was a problem loading the extract records to the corresponding database tables using the bulk loader. The first place you should look is the bulk loader log files in the working directory. This will usually indicate what the problem is. The most common problems are:

The maximum error threshold was exceeded causing the bulk load to abort the operation.
The database’s bin directory is not in the PATH causing the attempt to run the bulk loader to fail.
The database or table space is out of space.

Cannot access DATABridge control tables -Make sure that a 'configure' command was executed previously

This message can occur for any Client command except dbutility configure. It can indicate either of the following:

You did not run the dbutility configure command and therefore the client control tables were not created.
(more common) You are trying to execute a dbutility command with a relational database user ID that is different from the one that originally created the client control tables. In this case, use a relational database query tool to sign on to relational database with the same user ID that dbutility is using. Then, enter the following:

For Microsoft SQL Server:
select name, uid from sysobjects where type = 'U'

For Oracle:
select table_name from user_tables

The resulting display includes the name of all of the user tables owned by the user ID. If all of the client control tables do not appear, the problem is in the user ID you were using. For more information, see the DATABridge Installation Guide.

Cannot access user# for user userid

When you sign on to the relational database, the Client reads the Oracle table sys.user$ or the Microsoft SQL Server table sysusers to find the user index for your user ID. The user index is important because the relational database uses the user index (numeric) rather than the user ID (character string) to mark table ownership.

When this error occurs, it is typically preceded by messages that helps to illustrate what went wrong. If this error persists, contact your relational database administrator.

Cannot {allocate | expand} storage to hold table names for other DataSources

This message can occur during a dbutility define or redefine command. It indicates that there is not enough memory on the system to allocate or expand the memory for the table that is used to hold table names for other data sources.

Cannot find entry point "EBCDIC_to_ASCII" in extended translation {DLL _| shared library} "filename"

The attempt to locate the entry point EBCDIC_to_ASCII in the data translation DLL failed. Make sure that there is not another DLL with the same name that Windows is finding instead. The best way to avoid this problem is to put the DLL in the DATABridge program directory and setup the PATH environment variable to include this directory. If you execute the dbutility program out of this directory, and the DLL is also present in that directory, you should not run into this problem.

Cannot open lock file for data source name, errno = number (errortext)

This message indicates that the Client cannot open the lock file used to implement a file lock for the data source. A common cause of this error is that the locks directory does not exist. If you did not use migrate to do the update, you must create the Client working directory and the locks sub-directory in order to be able to run the client. For more information, see the DATABridge Installation Guide.

Cannot open trace file "name", errno = nnn (errortext)

This message occurs when you run the Client with the -t option (dbutility) or enable tracing from the Client Console. The error indicates that the Client cannot open the file. To resolve this problem, rename or delete your log file and make sure that you have enough disk space. The error text is provided in addition to the operating system error.

Cannot run a cmd_name command while the data source is locked

This message indicates that a DATABridge run has the data source locked. When a run hangs, you must cancel the run to release the lock file. The process_id of the run that locked the file and the command it is executing is provided in the lock file source_database.lock (where source is the name of the data source and database is the name of the relational database). This file is located in the locks subdirectory of the Client working directory. (The –u option only resolves this type of situation in DATABridge 6.0 and earlier.)

Clean up of table 'name' failed

The Client was unable to delete selective entries from the specified table during the drop or dropall command. The Client typically drops tables. However, if tables contain non-DMSII data or are populated from more than one data source, the Client uses the cleanup scripts to delete the records in question. Look at the relational database message that precedes this error for more information.

Client aborting rpc_description call

This message is preceded by other messages such as relational database API errors. The rpc_description indicates the specific operation (such as connect, initialize, switchaudit) that was in progress when the Client error occurred. This message indicates that a fatal error occurred while processing the given Server Accessory API call.

Client Control Table version mismatch (found number, expected number) - Run the "dbfixup" program to correct this situation

This message indicates that the client control tables have the wrong version. You must run the dbfixup program to correct this error. This message typically occurs if you upgrade from an earlier version of the Client and do not run the dbfixup program before you run the Client.

Client/host interface level mismatch: client = ver1, host = ver2

This message can occur when the Client connects to the Server Accessory, if the version of the Server Accessory is too old to be compatible with the Client. Specifically, this message indicates that the Server Accessory returned an illegal value for the negotiated protocol level.

Close failed for binary configuration file "name", errno = number (errortext)

This is an indication that there was a problem writing the binary configuration file to disk. The errortext explains the cause of the failure. The most common cause is that the config directory has not been created.

Close failed for bulk load temporary file for table 'name', errno = number (errortext)

This message, which applies to only Windows, can occur during a clone or process command. It occurs when the Client closes the temporary file before starting the command file to run the bulk loader. The system error included in the message should explain why the error occurred. The most likely cause is a lack of disk space.

Close failed for Null Record file, errno = number (errortext)

An error occurred while closing the NULL record file during a define or redefine command. The most likely problem is a lack of disk space. The system error included in the message should explain why the error occurred.

Close failed for text configuration file "name", errno=number (errortext)

This is an indication that there was a problem writing the text configuration file disk. The errortext usually indicates the cause for the failure. The most common cause is that the config directory has not been created.

Command aborted due to error in cross checking DMSII Links

The define or redefine command is being aborted because dbutility encountered errors when checking the integrity of DMSII links. This message is preceded by one or more error messages indicating which tables have links to nonexistent or inactive tables.

command_name command failed to complete

This message indicates that the Client command could not complete successfully, where command_name is a client command such a process, clone or redefine. Typically, this message is preceded by an explanatory error.

COMMIT ABSN command requires a numeric argument

This message is a result of an invalid user input for a dbutility console COMMIT ABSN command. For details, see Controlling and Monitoring dbutility.

COMMIT ABSN value out of range

This message is a result of an invalid user input for a dbutility console COMMIT ABSN command. For details, see Controlling and Monitoring dbutility.

COMMIT command must be followed by {Absn <n> | Update <n> | TIme <n> | TRans <n> | Stats}

This message is a result of an invalid user input for a dbutility console COMMIT command. For details, see Controlling and Monitoring dbutility.

COMMIT TIME command requires a numeric argument

This message is a result of an invalid user input for a dbutility console COMMIT TIME command. For details, see Controlling and Monitoring dbutility.

COMMIT TIME value out of range

This message is a result of an invalid user input for a dbutility console COMMIT TIME command. For details, see Controlling and Monitoring dbutility.

COMMIT TRANS command requires a numeric argument

This message is a result of an invalid user input for a dbutility console COMMIT TRANS command. For details, see Controlling and Monitoring dbutility.

COMMIT TRANS value out of range

This message is a result of an invalid user input for a dbutility console COMMIT TRANS command. For details, see Controlling and Monitoring dbutility.

COMMIT UPDATES command requires a decimal argument

This message is a result of an invalid user input for a dbutility console COMMIT UPDATES command. For details, see Controlling and Monitoring dbutility.

COMMIT UPDATES value out of range

This message is a result of an invalid user input for a dbutility console COMMIT UPDATES command. For details, see Controlling and Monitoring dbutility.

Configuration file "name" contains no valid information

This message indicates that the specified configuration file contains no data or valid information (for example, there are no section headers in the file).

Configuration file [name] section: error_message - Input Line: input_text

This message is associated with a large number of errors that can appear when processing a text-based configuration file. If you use binary configuration files, these messages are confined to the import command.

[name] section is the relevant section in the configuration file. input_text is the actual line of text in which the error occurs. For information about configuration file syntax, see Appendix D, Client Configuration File Reference.

Configuration file contains invalid line: input_text

This message typically appears when you have omitted the semicolon (;) from a comment line that precedes the first section header in the configuration file.

Configured numeric date format (number) for item 'name' in table 'name' is not supported, record will be {discarded | date set to NULL}

-Keys: columnname = value

This message can occur during a process or a clone command when processing a data item whose sql_type column contains a value of 13 (numeric_date). The configuration file parameter numeric_date_format is used to define the format for numeric dates. This error indicates that the format specified in the configuration file is not supported. See Cloning a Numeric Field as a Date.

CreateFile failed for 'Console_Reader_Thread'

(Windows only) This message is an internal error, which indicates that the console thread’s attempt to read input from the keyboard failed. As a result, the console is inoperative. Except for this, the run proceeds as if the console were not enabled.

CreateMutex failed for 'name', errno = number (errortext)

(Windows only) This message, which can occur during a process or clone command, indicates that a Windows internal error has occurred while attempting to create a mutex resource. If this error occurs, contact Technical Support.

CreateSemaphore failed for 'name', errno = number (errortext)

(Windows only) This message, which can occur during a process or clone command, indicates that a Windows internal error occurred while attempting to create a semaphore resource used by the table creation thread. If this error occurs, contact Attachmate Technical Support.

CreateThread failed for 'name', errno = number (errortext)

(Windows only) This message, which can occur during a dbutility process or clone command and indicates that a internal system error occurred while attempting to create a thread (bcp_launcher, index_creator or console thread). If this error occurs, contact Technical Support.

Creation of control table 'name' failed

This message can occur during a dbutility configure command or when the control tables are created by the Console or the Client Configurator. It indicates that an error occurred while creating the specified Client control table. See the relational database API message that precedes this message (on the screen or in the log file) for more information.

This message can also occur during a drop command involving a multisourced data source, where the table is cleaned after the index is dropped and subsequently re-created.

Creation of history table 'name' failed

This message, which can occur during a reorg command, indicates that the command was unable to create the given history table. The configuration file parameter enable_dynamic_hist allow the Client to dynamically create history table without having to reclone the data set in question. See the database API error messages that precede this error message to determine why the creation of the table failed.

Creation of keys failed for primary table 'name'

This message can occur during a define or redefine command. It indicates that an error occurred whiel the Client attempted to define the keys for a primary table. this message is preceded by another error message that explains the actual cause.

Creation of keys for OCCURS failed for table 'name'

This message, which can occur during a dbutility define or redefine command, indicates that an error occurred while trying to insert the keys for an OCCURS table into the DATAITEMS Client control table. See the relational database API message that precedes this message (on the screen or in the log file) for more information.

Creation of keys within split failed for table 'name'

This message can occur during a dbutility define or redefine command. It indicates the following:

A DMSII data set has more columns than the relational database limit, and therefore, must be split into two or more relational database tables.
An error occurred while creating the keys for a secondary table.

See the relational database API message that precedes this message (on the screen or in the log file) for more information. See also Oracle Call Interface (OCI) Errors or Microsoft SQL Server ODBC Errors.

Creation of stored procedure failed for control table name

Unless the configuration parameter use_ctrl_tab_sp is set to False, all Clients extend the use of host variables to updating the various control tables. Before the Client performs an update for a control table, it makes sure that the stored procedure U_tabname exists and creates it if it doesn't. If the Client is unable to create U_tabname, this message appears and the Client reverts to using regular SQL for control table updates.

Creation of table 'name' and its procedures failed

This message can occur during the cloning of a data set using a process or clone command if the Client is attempts and is unable to create a table and its stored procedures. See the relational database message that precedes this error for more information about what went wrong.

Critical columns missing from table 'name', cannot create cleanup script

This message indicates that the generate command could not find some of the columns that are created by setting the external_columns column of the DATASETS Client control table to a nonzero value. The most common cause of this message is that the external_columns column was assigned a value without running a define or a redefine command, or that the active column for the item in question was set to zero in DATAITEMS. It is recommended that you use user scripts to perform all such actions that the redefine command runs and that you never change the value of the active column in DATAITEMS.

Data source does not support transactions (SQL_TXN_CAPABLE = NONE)

This message, which is applicable to ODBC and CLI clients, indicates that the database does support transactions. You cannot run the DATABridge Client with a database that does not support transactions. This error indicates that your relational database is not properly set up.

Database {name | NULL} failed to open [twice]

The requested relational database failed to open. (If you do not specify a database name and you are connecting to the default database, the Client displays "NULL" as the database name.)

In this case, check the following:

Is the relational database server running?
Did you enter the correct relational database server name?
Did you enter the correct relational database name?
Did you use the correct user ID for the relational database?
Did you use the correct password?
Check your settings for environment variables, dbridge.cfg configuration file, and command line options.

The Client establishes two connections with the relational database server. This error indicates a failure on the second connection when the word twice is present.

Note: The Client establishes two connections to the relational database server because the DDL (Data Definition Language, subset of SQL) statements for creating and dropping a table force a commit. Therefore, it is impossible to execute a DDL statement during a transaction without causing a commit to occur when the DDL is executed. Having an alternate connection allows the Client to execute the DDL.

Database password cannot be decoded

This message can occur when the Client reads a text-based configuration that contains an encoded password that is corrupt. This error happens most often when the file has been edited. To resolve the problem, replace any passwords and then use dbpwenc or the export command to encode them.

DATABridge call failed for rpc_description (Transport or RPC error)

This message is preceded by a SOCKETS ERROR or other message that occurs during the processing of a remote procedure call. rpc_description indicates the specific operation that was in progress when the Client error occurred (for example, connect, primary_set, set_option, data sets, initialize, switchaudit). This message can occur in any command that establishes communications with the DATABridge Server.

DATABridge control tables are not empty, use dropall command first - To bypass this check, use the 'u' option for the configure command

This message indicates that you are attempting to run a dbutility configure command that overwrites the existing client control tables. This message is intended as a safeguard so that you do not accidentally overwrite the existing client control tables. To overwrite the existing client control tables, see the -u option in dbutility Command-Line Options.

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

This message indicates that you are attempting to run the dbutility configure command under a different user ID than the one that originally created the client control tables. This message is intended as a safeguard so that you do not inadvertently create a parallel set of client control tables when you don’t intend to.

If you do want to create a new set of client control tables (for example, for testing purposes), run the dbutility configure command with the -u option. The -u option is explained in dbutility Command-Line Options.

DataSet List specification is not allowed for a DataSource that is not defined

This message occurs during a reload command when you specify a list of data sets to reload for a data source that is not found in the client control tables. The partial reload of only a few specific data sets is only supported if the data source exists and contains entries for the specified data sets.

DataSet List specification not allowed when loading all DataSources

This message occurs during a reload command when you specify a data source name of _all and a list of data sets to reload. The partial reload of only a few specific data sets is only supported if the data source is explicitly named, it exists and it contains entries for the specified data sets.

ERROR: DataSet name[/rectype] does not have history tables; DSOPT_HistoryOnly bit must be 0 in ds_options

This message, which can occur during a define or redefine command, indicates that the ds_options column of the DATASETS table entry for the data set is incorrect. The DSOPT_HistoryOnly bit can only be set when the DSOPT_Save_Updates (8) bit is also set. This is an indication that your user scripts are incorrect.

DataSet name[/rectype] failed reorganization, correct the error or reclone – mode dd

This message can occur at the start of a process or clone command if the Client finds a data set whose mode is 33. This situation can occur if you attempt to run a process or clone command after running a reorg command where the reorganization of a table fails for the data set in question.

To resolve this problem, do one of the following:

Set the ds_mode to 0 and reclone the data set.
Fix the reorganization script and rerun the reorg command after you set the ds_mode to 31 for the data set in question.

DataSet name[/rectype] has an invalid mode dd

This message occurs during a process command (at data set selection time), if the ds_mode column of the Client control table contains an illegal value dd. Use a relational database query tool to enter a valid dd value. For a list of valid values, see DATASETS Client Control Table.

DataSet name[/rectype] has an invalid value (dd) in the status_bits field

This message occurs at the start of a process or a clone command (at data set selection time), if the status_bits column of DATASETS Client control table contains an illegal value dd. Use a relational database query tool to enter a valid dd value. For a list of valid values, see DATASETS Client Control Table.

DataSet name[/rectype] has been reorganized (mode = dd); you must first run a reorg command

This message can occur at the start of a process or clone command (at data set selection time), if the Client finds a data set whose mode is 31 or 34. This situation can occur if you attempt to run a process or clone command after running a redefine command that needs to be followed by a reorg command.

After you inspect the reorg scripts to make sure that the actions they are about to perform are reasonable, run a reorg command. Reorg scripts ALTER tables, which is nearly impossible to reverse.

DataSet name[/rectype] has been reorganized; you must first run a redefine command

This message can occur during a process or clone command (at data set selection time), if the DBSelect RPC call returns a status indicating that the data set has been reorganized. This situation can occur if you attempt to clone a data set that was defined before the data set was reorganized in DMSII. Simply run a redefine command and (if necessary) a generate command before attempting the clone again.

DataSet name's {real_ds_num | virtual_ds_num} column points to an inactive or non-existent structure number

This message only applies when the automate_virtuals parameter is set to True. It indicates that the real_ds_num or virtual_ds_num column for the specified data set points to an inactive or non-existent structure. The proper handling of virtual data sets that get input from more than one real data set requires that all data sets involved have their active columns set to 1. Use a relational database query tool to correct this situation.

DataSource name already defined, use redefine command instead - To bypass this check, use the 'u' option for the define command

This message occurs if you attempt to run a define command for a data source that is already defined. It is a protection against inadvertently running a define command when you meant to run a redefine command. If you intended to use a define command, use the ‑u option on the command line. Before running a redefine command, it is always a good idea to create a backup for the data source using an unload command.

Day of year value val out of range for item 'name' in table 'name'. {record will be discarded | date set to NULL} - Keys:columnname = value,...

This message can occur during a process or clone command. It indicates that the specified day value is incorrect in a MISER or LINC database date or in a Julian date. In the case of LINC or Miser dates, this should never happen. If it does, contact Technical Support. In the case of a Julian date, the value in the DMSII database is in error (for example 400).

This is not a fatal error. The date is stored as NULL or if the item is a key, the record is discarded.

Definition of data items for table 'name' failed

This message can occur during a dbutility define or redefine command. It indicates that a failure occurred while defining the data item for the specified table. For more information on the cause, refer to the messages that preceded this one onscreen or in the log file.

Delete of control_tablename entries for datasource failed

This message can occur during a dbutility define, redefine, drop, or dropall command. It indicates that the records in the given Client control table could not be deleted. See the relational database API message that precedes this message (on the screen or in the log file) for more information.

Deletion of records from client control tables failed for DataSource name

This message can occur during the define command and is always preceded by more specific error messages. It indicates that the define command could not delete the entries that existed in the client control tables. See the database API message that preceded this message for more information.

DeSelect for DataSet name[/rectype] ignored, it has no stridx assigned

This message can occur during a process or clone command if the program encounters an internal error when attempting to deselect a data set. This operation is used when the AA values of a data set are invalidated by a DMSII garbage collection reorganization. When a search of the table that contains the selected data sets fails to yield a valid structure index for the data set to be selected, this message is displayed.

DMSII date contains an illegal numeric value val for item 'name' in table 'name', {record will be discarded | date set to NULL} - Keys: columnname = value, ...

This message indicates that dbutility encountered an illegal numeric value while processing the item which is being interpreted as a DMSII date. This error message applies to both numeric and alpha dates. It can be caused by a number that is longer than 8 digits; a value that contains illegal digits; an incorrect value in the dms_subtype column; or bad DMSII data. This is not a fatal error. The date is stored as NULL or, if the item is a key, the record is discarded.

DMSII date/time contains an illegal time value tval for item 'name' in table 'name', {record will be discarded | date set to NULL} - Keys: columnname = value, ...

This message indicates that dbutility encountered an illegal numeric value while processing the item which is being interpreted as a DMSII date/time. This error message applies to both numeric and alpha dates. It can be caused by a number that is longer than 14 digits; a value that contains illegal digits; an incorrect value in the dms_subtype column; or bad DMSII data. This is not a fatal error. The date/time is stored as NULL or, if the item is a key, the record is discarded.

Drop of control table 'name' failed

This message can appear during dbutility configure, process, clone, drop, or dropall commands. It indicates that the drop of the specified Client control table, data table, or data table’s associated stored procedures has failed. See the relational database API message that precedes this message (on the screen or in the log file) for more information.

Drop of stored procedure x_name failed

This message, which only applies to the Client for Informix, indicates that the stored procedure in question could not be dropped.

Drop of table 'name' failed

This message can appear during a drop, or a dropall command. It indicates that the drop of the specified data table, or data table’s associated stored procedures, has failed. See the relational database API message that precedes this message (on the screen or in the log file) for more information. See also Oracle Call Interface (OCI) Errors or Microsoft SQL Server ODBC Errors.

Embedded DataSet name[/rectype] cannot be selected because its parent structure is not active

This message, which can occur during a process or clone command, indicates that the Client encountered an embedded data set whose parent structure is not selected. Set the active column of the parent structure to 1 in the DATASETS Client control table.

Engine did not send BI/AI pair for update to DataSet name[/rectype] which allows key changes - Clear bit 0xhh in ds_options of DATASETS entry if you wish to ignore this error

This message, which is only applicable when using DATABridge Engine 6.1 and later, indicates that the DATABridge Engine did not send updates as BI/AI pairs as the Client requested. Clear the bit, which is displayed as a hexadecimal mask.

Caution: Clearing this bit is inadvisable if the key changes are actually taking place.

Expected LINK_AI record for DataSet name[/rectype] not received from Server

This message indicates that a DATABridge Engine error occurred during the data extraction of a data set that has DMSII links. The data extraction for such data sets consists of CREATE images followed by LINK_AI records. The Client combines these before writing the resulting record to the bulk loader file (or pipe, on UNIX). If a CREATE record is followed by another CREATE record this error is issued. Contact Attachmate Support in the unlikely event that you get this error.

Fetch of DATATABLES failed

This message can occur during a define or redefine command. It indicates that the FETCH of the external table names following the SQL select statement for the DATATABLES Client control table failed. For details, see the relational database API message that precedes this message (onscreen or in the log file).

fgets failed for console input, errno = number (errortext)

The dbutility console reads the keyboard to get console command. If you run dbutility as a background run, an attempt to read from the keyboard will result in this error and cause the console thread to terminate. On UNIX, you can use a couple of the kill signals to communicate with the back ground. For more information, see Controlling and Monitoring dbutility.

File "name" specified in -f option does not exist

This message, which is confined to dbutility, indicates the argument of the –f option is not a valid filename. If you just specify a file name, the program looks for the file in the config directory. If you want to point to a file in any other place you need to specify the fully qualified name of the file.

fseek failed for Null record file, errno = number (errortext)

This error can occur when reading or write the NULL record files. If the error occurs during a process or clone when trying to read the file, you can try running a redefine command with a -R option to rebuild the file. If you get this error during a define or a redefine command, the only recourse you have is to set the read_null_records parameter to False.

Generation of AA item 'name' in DATAITEMS table for 'tabname' failed

This message can occur during a dbutility define or redefine command. It indicates that the specified item could not be placed in the DATAITEMS table. The AA Value is the offset of the record in the DMSII data set (that is, its absolute address). The column, which is named my_aa, contains the AA Value of the record. For more information about the cause of the failure, see the relational database message that precedes this error.

Generation of Client Control Table version entry in DATASOURCES failed

This message can occur during a dbutility configure command or when the control tabels are created by the Console or the Client Configurator. It indicates that the Client cannot generate the DATASOURCES table entry to hold the version of the client control tables. For details about this problem, see the relational database message that precedes this error. One possible cause is that the userid does not have the required privileges.

Generation of common scripts failed

This message applies to the DATABridge Client for Oracle only. It can occur during a generate command, and it indicates that an error occurred while running one of the three common scripts that create or replace stored procedures used by the scripts the program uses to create or drop tables and stored procedures. The stored procedures are named exec_DDL, drop_proc, and drop_table. Try dropping these procedures using SQL*Plus and then rerun the generate command. The OCI messages that precede this error should provide further information as to why this error occurred. The most likely cause for this error is that you do not have the appropriate privileges to perform this operation.

Generation of DATASOURCES entry for DataSource name failed

This message can occur during a define or a redefine command. It indicates that the Client could not insert a record into the DATASOURCES Client control table. For more information about the cause of the failure, see the relational database message that precedes this message (onscreen or in the log file). See also Oracle Call Interface (OCI) Errors or Microsoft SQL Server ODBC Errors.

Generation of DATATABLES entry for table name failed

This message can occur during the dbutility define or redefine command. It indicates that the Client could not insert a record describing the specified table into the DATATABLES table. For more information about the cause of the failure, see the relational database message that precedes this message (onscreen or in the log file). See also Oracle Call Interface (OCI) Errors or Microsoft SQL Server ODBC Errors.

Generation of entry into DATASETS table for DataSet name[/rectype] failed

This message can occur during the dbutility define or redefine command. It indicates that an error occurrCall Interface (OCI) Errors. For Microsoft SQL Server, see Med while inserting an entry into the Client control table DATASETS for the specified data set name. For more information about the cause of the failure, see the relational database message that precedes this message (onscreen or in the log file). See also Oracle Call Interface (OCI) Errors or Microsoft SQL Server ODBC Errors.

Generation of entry into DATASETS table for Global_DataSet failed

This message, which can occur during a define or redefine command. It indicates that an error occurred while inserting an entry for Global_DataSet into the DATASETS Client control table. This entry is used for holding the global stateinfo during update processing when the optimize_stateinfo and/or the use_globalstateinfo configuration parameters are enabled. For more information about the cause of the failure, see the relational database message that precedes this message (onscreen or in the log file). See also Oracle Call Interface (OCI) Errors or Microsoft SQL Server ODBC Errors.

Generation of external column item 'name' in DATAITEMS table for 'tabname' failed

This message, which can occur during a define or a redefine command, indicates that the Client could not generate the external column item in the specified table. For details, see the relational database message that precedes this message (onscreen or in the log file).

Generation of item name in DMS_ITEMS table for DataSet name[/rectype] failed

This message can occur during the dbutility define or redefine command. It indicates that an error occurred while inserting an entry into the Client control table DMS_ITEMS for the specified item and data set. See the relational database API message that precedes this message (on the screen or in the log file) for more information. See also Oracle Call Interface (OCI) Errors or Microsoft SQL Server ODBC Errors.

Generation of KEY item 'name' in DATAITEMS table for 'tabname' failed

This message, which can occur during a define or a redefine command, indicates that the Client could not insert a record describing the specified key into the DATAITEMS table. See the relational database API message that precedes this message (on the screen or in the log file) for more information.

History table definition failed for DataSet name[/rectype]

The define or redefine command could not create the history table for the specified data set. See the relational database message that precedes this error for more information about what went wrong.

History table 'name' does not include a timestamp [or an identity] column

In order to use history tables, the table must have a timestamp column to determine the order in which to apply the changes. In the case of the DATABridge Client for Microsoft SQL Server, an identity column is equally well suited for this purpose. If the Client finds no such column during a generate command, it displays this error, which causes the generate command to fail. Make sure that you have not set active=0 in DATAITEMS for the columns that the define command automatically creates for history tables.

History table 'name' does not include an 'update_type' column

In order to use history tables, the table must have an update type column, which specifies the type of update involved (insert, delete, or update). If the Client finds no such column during a generate command, it displays this error, which causes the generate command to fail. Make sure that you have not set active=0 in DATAITEMS for the columns that the define command automatically creates for history tables.

Host password cannot be decoded

This message can occur when the Client reads a text configuration that contains an encoded password that is corrupted, most typically because the file was edited. If this is a text file, replace the password and use dbpwenc or the export command to encode it.

Illegal argument for 'g' option

This option is used to pass information from the Client service (or daemon, on UNIX) to the spawned run. It isn't applicable to dbutility. Call Attachmate Technical Support.

Illegal concatenation for items 'name1' and 'name2', resulting column is too large

The Client merges two neighboring items of like type to form a bigger item when the di_options bit DIOPT_MergeNeighbors (0x1000000) is set in the DMS_ITEMS table entry for the first item. This feature is only supported for items of type ALPHA or unsigned NUMBER. This error indicates that concatenation is illegal because the resulting column would exceed the maximum length for the corresponding data type.

Illegal date value val for item 'name' in table 'name', day set to newday
-Keys: columnname = value,...

This message only occurs when the correct_bad_days parameter is enabled. It indicates that the DMSII date item contains invalid day values, which the Client is changing to make the date valid. For more information on dates, see Cloning DMSII Dates, Times, and Date/Times.

Illegal date value val for item 'name' in table 'name', {record will be discarded | date set to NULL}
-Keys: columnname = value, ...

This message can occur during the dbutility process and clone commands. It indicates that the date extracted from the DMSII data is in error. The most likely causes of this error is bad DMSII data or an incorrect value in the dms_subtype column. This is not a fatal error. The date is stored as NULL or, if the item is a key, the record is discarded.

Illegal date value val for item 'name' in table 'name', value of year out of range, {record will be discarded | date set to NULL} - Keys: columnname = value, ...

This message can occur during a process or a clone command. It indicates that the year portion of the date is invalid for the relational database data type. The year portion of an item with a SQL type of smalldatetime is limited to the range 1900–2079. Similarly, the year portion of an item of SQL type of datetime is limited to the range 1753–9999. If you are dealing with a SQL type of smalldatetime consider changing it to datetime instead. The program recognizes a MISER date of 99999 as a special date used by MISER systems and stores it as 6/6/2079 when the SQL type is smalldatetime and 12/31/9999 when the SQL type is datetime. This is not a fatal error. The date is stored as NULL or, if the item is a key, the record is discarded.

For more information on dates, see Cloning DMSII Dates, Times, and Date/Times.

Illegal dms_subtype value number for item 'name' in table 'name', {record will be discarded | date set to NULL} - Keys: columnname = value, ...

This message indicates that a member of a DMSII date GROUP has a dms_subtype value that is not 1, 2, 3, or 4. Note that the only acceptable DMSII GROUPs are those with 2 or 3 numeric items. DMSII date groups are setup by setting the DIOPT_Clone_as_Date (2) option in the di_options column of the DMS_ITEMS entry for the group, followed by the setting of the dms_subtype columns for the members of the group.

For more information on dates, see Cloning DMSII Dates, Times, and Date/Times.

Illegal hex character 'char' found in encoded string

This message can occur when the Client tries to decode passwords when reading the configuration file at the start of a run. Passwords are always encoded in binary configuration files. Password encoding is optional in text-based configuration files and can be done with the export command or the dbpwenc utility.

Illegal month name mmm for item 'name' in table 'name', {record will be discarded | date set to NULL} - Keys: columnname = value, ...

This message indicates that dbutility encountered an illegal month name while processing a DMSII ALPHA date. If the month names are not in English, you need to use the months specification in the configuration file. This is not a fatal error. The date is stored as NULL or, if the item is a key, the record is discarded after it is written to the corresponding file in the discards subdirectory.

Illegal numeric data (value) for field name[number] in archive file

This error can occur during a reload command. If you did not modify the file, report the error to Attachmate Technical Support.

Illegal [numeric] time value number for item 'name' in table 'name', {record will be discarded | date set to NULL} - Keys: columnname = value, ...

This message indicates that dbutility encountered an illegal numeric time value while processing the item which is being interpreted as a DMSII time. The most likely cause of this error is bad DMSII data. This is not a fatal error. The date is stored as NULL or, if the item is a key, the record is discarded.

Illegal numeric value specified for {count | length}

This error can occur during a tcptest command if an illegal numeric value is specified for the count or length parameter of the command. A value that causes the count to go negative also results in this error. Do not use extremely large values for the count, as this would make the test run for a very long time using up a lot of mainframe CPU time.

Illegal numeric value specified for 'F' option argument

The argument of the /F option for the Client is an audit file number, which must be in the range of 1 to 9999.

Illegal numeric value specified for port

This message can occur during the scanning of the port number from the command line argument for a define command. It indicates that the specified port number is not syntactically correct.

For example, dbutility define cin.aa.atmate.com 12,5 would generate this message because it is not a syntactically correct number. An example of correct syntax is the following:

dbutility define cin.aa.attachmate.com 1255

Illegal numeric value specified for -t option argument

This message can occur during the scanning of the -t command line option, which has a numeric argument. It indicates that the specified argument is not syntactically correct. For a list of valid numeric arguments for the -t option, see Enabling a Trace.

Illegal numeric value specified for 'V' option argument

The -V option is used with the dbutility unload command to specify the control table version. For a list of legal values, see dbutility Command-Line Options.

When you upgrade, the dbfixup program creates control tables that are readable by the client from which you are upgrading. This allows you to safely reload these control tables and use the previous version if you experience a problem.

Illegal string

This message can occur during any dbutility command that has an argument that is a quoted string. It indicates that an illegal string was entered into the configuration file. This message is always followed by a second error message that lists the input record.

In the case of Windows, the most common cause of this error involves the use of back slashes in file names. You must enter a back slash as two back slashes because the first is interpreted as a force character. Failure to do this results in this error.

Illegal update type dd number for table 'name'

This message applies to the DATABridge Client for Oracle only, and it applies only when the aux_stmts parameter is set to a nonzero value. This message can occur during the process or clone command, and it is an internal error that indicates that the section of code that generates the SQL statement for an update encountered an undefined update type.

Improper section header in configuration file line: input_text

This message, which can occur when text-based configuration file are being processed, indicates that section header is not defined or is not formatted using the following syntax:

[SectionHeaderName]

Incomplete script file "name", missing '/***/'

This message can occur during a process or a clone operation. It indicates that a script file was not created correctly or is corrupt. First, check that an error did not occur during dbutility generate operations. If the script file is corrupt, run the generate command again to create a new script file.

This error can also occur when running a user script in a define, redefine, process, or clone command. If the error involves a user script, remember that all SQL statements, except the last one, must be followed by the script delimiter. The script delimiter must be in a separate record and must not contain any leading or trailing blanks. An improper delimiter results in an error. For this reason it is recommended that you use the runscript command, whenever possible, to test the scripts.

Index creation failed for control table name

This message can occur during a dbutility configure command or when the control tables are created by the Console or the Client Configurator. It indicates that an error occurred while creating the index for the specified Client control table. See the relational database message that precedes this message (on the screen or in the log file) for more information.

Index creation failed for history table 'name'

This message, which can occur during a reorg command, indicates that the command was unable to create the index for the given history table. See the database API error messages that precede this error message to determine why the creation of the index for this empty table failed.

Index creation failed for table 'name'

This message, which can occur during a reorg command, indicates that the command was unable to re-create the index for the given table. The reorg command typically will drop the index for a table before altering it, when a column that is a member of the index is involved in the alter command. The command also drops and recreates the index for table whose index type is changed (for example, a unique index is changed to a primary key). See the database API error messages that precede this error message to determine why the creation of the index for this empty table failed.

Index thread failure, creating index directly

This message, which is limited to UNIX clients, indicates that the attempt to create the index thread failed. When this occurs, the main thread creates the index (as if the parameter spawn_index_creation was set to false). If this error persists, refer to the thread creation error to determine why it is failing.

Insufficient memory for allocating DataSets

This message indicates that there is not enough available memory to allocate data sets. This message can occur during a process or clone command. In this case, quit all other applications and try again.

Internal error, undefined column type number for columnname encountered in Process_Archive_Record()

This message indicates an internal error in the reload command. Contact Attachmate Technical Support unless you modified the archive file.

Invalid boolean argument specified for {sched | verbose} command

The command entered in the command-line console contains an invalid Boolean argument. A Boolean argument is of the form {yes | no} or {true | false}. This applies to the sched and verbose commands.

Invalid concatenation for item 'col_name' in table 'tabname'

The client only supports concatenation of two ALPHA items or two unsigned NUMBERS. You can also use a NUMERIC item that is cloned as ALPHA in place of an ALPHA item or an ALPHA item that is cloned as a NUMBER in place of a numeric item. Any other combination results in this error message being displayed by the define and redefine commands.

Invalid database update type number received

This message can occur during a process or a clone command. It indicates that the DATABridge host software returned an undefined update type (for example, an update type that is not CREATE, DELETE, MODIFY, STATE, MODIFY_BI, MODIFY_ALL, or DOC). To get more information on this message, you must get a trace of DBServer communications (-t 0x45) and send the trace to Attachmate Technical Support.

Note: An alternative is to turn off cloning (set active column to 0) for the offending data set.

Invalid length specification for datatype 'name' in external column 'colname'

This message, which occurs when text-based configuration files are being processed, indicates that the sql_length specification in the given external_column parameter is invalid for the corresponding data type.

Invalid SQL type 'name' for external column 'colname'

This message, which occurs when text-based configuration files are being processed, indicates that the sql_type parameter in the given external_column specification is invalid.

Invalid stop_time or end_stop_time value dddd, dddd, values set to 0

This message can occur during a dbutility process or clone command if the controlled_execution configuration parameter is enabled. It indicates that the program detected an error in the values of the stop_time and end_stop_time columns it read from the DATASOURCES client control table. These values are integers that represent a time of a day using 24-hour time (hh:mm format). If the value hh is not in the range 0:24 and mm is not in the range 0:59, both entries are set to 0 and this error appears.

Invalid structure index number received

This message indicates a problem on the host. In this case, the DATABridge Engine is sending a DMSII structure index number that is invalid (for example, a structure index number less than 0). To get more information on this message, you must trace DBServer communications (-t 0x45) and send the trace to Attachmate Technical Support.

Invalid value nnn for dms_concat_num column in DATAITEMS for table tab_name item col_name

This message indicates that the Client detected a bad item number in the dms_concat_num column. While this error can occur during any Client command, it typically happens when loading the control tables. The most likely cause of this error is from a non-existent item number in the dms_concat_num column. Scripts do not cause this error. If the problem isn't fixed, the client will fail.

IO errors in writing dbload format file "name", errno = number (errortext)

This message applies to the Informix client. It can occur during a generate command, and it indicates that an error occurred while writing to the specified dbload format file. The system error should explain the cause of the problem.

IO errors in writing db2 load command file "name", errno = number (errortext)

This message applies to the DB2 client. It can occur during a generate command, and it indicates that an error occurred while writing to the specified DB2 loader format file. The system error should explain the cause of the problem.

IO errors in writing file "name", errno = number (errortext)

This error message, which can occur during an unload command, indicates that an error occurred while writing a record to the archive file whose name appears in the message. The system error should explain the cause of the problem.

IO errors in writing script file "name", errno = number (errortext)

This message can occur during a dbutility generate command. It indicates that an error occurred while writing to the specified script file. The errno value is provided in addition to the system error message errortext. For Windows, you can look up the errno value in the header files for the Microsoft C++ library routines. The system error should explain the cause of the problem.

IO errors in writing sqlldr format file "name", errno = number (errortext)

This message applies to Oracle. It can occur during a generate command, and it indicates that an error occurred while writing to the specified sqlldr format file. On Windows, you can look up the errno value in the header files for the Microsoft C++ library routines. The system error should explain the cause of the problem.

'name' is an invalid SQL type for column name

The SQL type you specified for the column in an external_column parameter specification is invalid for the given column type.

It is illegal to change the keys data set when it is using a DMSII SET for the index

The Client Configurator currently does not support changing the values of item_key in DMS_ITEMS for data sets that are using a DMSII SET as the source for the index.

Item 'name' (dms_subtype = number) cannot be cloned

This message, which typically should not occur, is an indication that thespecified dms_item_type column contains a value that the program cannot deal with. If you happen to have a DATAITEMS entry whose type is GROUP (29), attempting to set the active column to 1 results in this error unless the sql_type of the item is set to date.

Item 'name' in table 'name' cannot be cloned as three booleans

The program clones DMSII NUMBER(1) items as a field of three Booleans when the DIOPT_Clone_as_Tribit bit (16) in the di_options column of DMS_ITEMS is enabled. If you try to use this option with a DMSII NUMBER whose length is not 1 you get this error.

Item name in control table name has an illegal sql_type of nnn

This message, which is not likely to be seen, indicates that when attempting to the host variable for updating a control table a column with an invalid SQL data type code was encountered.

Item name in DataSet name[/rectype] points to a non existent or inactive DataSet (strnum = nnn)

This message only applies when the configuration file parameter enable_dms_links is enabled. It indicates that the specified item points to a non-existent or inactive data set. This situation is clearly an error, as the link must point to a valid table. You must either set the active column to 0 in the DMS_ITEMS table for the link in question, or set the active column to 1 in the DATASETS table for the target data set of the link.

Item 'name' in table 'name' cannot be cloned as TIME data type, {record will be discarded | date set to NULL}

- Keys: columnname = value, ...

This message occurs if you try to clone a DMSII TIME(12) or TIME(14), represented by a dms_subtype value of 4, as a SQL Server 2008 TIME data type. Use a numeric time instead, as this is not supported.

Item 'name' in table 'name' contains an illegal numeric value val, {record will be discarded | date set to NULL}
- Keys: columnname = value, ...

This message indicates that the Client encountered an invalid number. The program recognizes numbers that have all their digits set to 0xF to be NULLS; any other number that has a value that is not 0–9 in any digit position except for the sign is treated as bad. A bad number is stored as NULL unless the item is a key, in which case the record is discarded. Note that if the DAOPT_Allow_Nulls bit (1) in the da_options column of DATAITEMS is not set, the number is stored as either all high values or all low values depending on the setting of the configuration parameter null_digit_value.

Item 'name' in table 'name' contains an invalid time value hh:mm:ss, {record will be discarded | date set to NULL}

- Keys: columnname = value, ...

This message indicates that the Client detected an invalid time value while processing a DMSII item as a time value. This error can occur when the DMSII data is bad or when the item is not an actual DMSII time. See DMSII Times for details on interpreting DMSII items as time values.

Item 'name' in table 'name' which is a member of date group is not an integer value, {record will be discarded | date set to NULL}
- Keys: columnname = value, ...

This message appears when you have defined sql_type to a date data type and dms_subtype to 1, 2, 3, or 4, but there is a non--numeric member in the DMSII GROUP. The DMSII date GROUP can contain only numeric fields that must be appropriately identified as year, month, and day. For more information on setting the dms_subtype column for dates, see Cloning DMSII Dates, Times, and Date/Times.

Item 'name' in table 'name' has an illegal {dms_item_type | dms_subtype} value of nnn

This message, which can occur during a createscripts command indicates that the item in question is in error. This is the result of bad user scripts. You need to fix this before proceeding any further, as it will cause the Client to fail.

Item 'name' in table 'name' points to non-existent DMS item numbered nnn

This message, which can occur during a createscripts command indicates that the item in question is in error. This is the result of bad user scripts. The most likely cause of this error is that the item number in the dms_concat_num column does not exist. You need to fix this before proceeding any further, as it will cause the client to fail.

Last Database Error = number

This message is printed when a SQL error occurs while processing updates. (If logging is enabled, this message is logged rather than printed.) This message is followed by the actual SQL statement that provoked the error.

Load of DATABridge control tables failed

This message can occur during any Client command except for dbutility configure, refresh, runscript, and tcptest. It indicates that an error occurred while reading the client control tables. See the relational database API message that precedes this message (on the screen or in the log file) for more information. See also Oracle Call Interface (OCI) Errors or Microsoft SQL Server ODBC Errors.

Loading table 'name' using bcp - see file "bcp.tablename.log" for more information

This message applies to the Client for Microsoft SQL Server, and can occur during cloning of a data set via the dbutility process or clone command. A possible cause of this error is that the database is out of disk space. Make sure that you check the specified log file for possible errors.

Loading table 'name' using dbload- see file "dbload.tablename.log" for more information

This message applies to the Client for Informix, and it can occur during cloning of a data set using a process or clone command. A possible cause of this error is that the database is out of disk space. Make sure that you check the specified log file for possible errors.

Loading table 'name' using db2cmd- see file "dbload.tablename.log" for more information

This message applies to the Client for DB2, and it can occur during cloning of a data set using a process or clone command. A possible cause of this error is that the database is out of disk space. Make sure that you check the specified log file for possible errors.

Loading table 'name' using sql*loader - see file "sqlld.tablename.log" for more information

This message applies to the Client for Oracle, and it can occur during cloning of a data set via the dbutility process or clone command. A possible cause of this error is that the database is out of disk space. Make sure that you check the specified log file for possible errors.

Log file prefix is too long, maximum allowable length is 20, value truncated

You can specify a prefix for the Client log files in the Client configuration file, however this prefix is limited to 20 characters. If you use a longer prefix, you get this error. The default prefix is “db”. We recommend using the data source name as the prefix, when you have more than one data source.

Logswitch command failed

The log switch command, which can be issued from the Console, closes the current log file and open a new one with a different name. See the error messages that precede this message in the log file to see why the command failed.

Merge of neighboring items only valid for ALPHA and unsigned NUMBER- unable to merge items name1 & name2

The Client merges two neighboring items of like type to form a bigger item when the di_options bit DIOPT_MergeNeighbors (0x1000000) is set in the DMS_ITEMS table entry for the first item. This feature is only supported for items of type ALPHA or unsigned NUMBER. If you try to merge in other type of items you get this error.

Mismatched AFN values for reorganized DataSets: 'name1' AFN = afn1 and 'name2' AFN = afn2

This message, which can occur during a redefine command, indicates that not all the data sets to be reorganized have the same AFN value in their stateinfo. Most likely, the value of the active column changed for one of the data sets. You may be able to get around this problem by setting the open_audit_file parameter to No.

Missing length specification for SQL type sql_type (nn) in external column 'colname'

This error, which can occur during text-based configuration file processing, indicates that the sql_length specification for the given external_column parameter is invalid.

name command can only be followed by an optional alphanumeric argument

This message is a response to bad input from the dbutility command-line console Quit command. For example,QUIT 12:30 was entered instead of QUIT AT 12:30.

name command requires a boolean argument

This message is a response to bad input from the dbutility command-ine console,which only accepts a Boolean argument.

name command requires a decimal numeric argument

This message is a response to bad input from the dbutility command-line console, which requires a numeric argument to be a decimal number.

name command requires a valid argument

This message is a response to bad input from the dbutility command-line console, which requires an argument.

name command requires a valid numeric argument

This message is a response to bad input from the dbutility command-line console that only accepts a numeric argument that could be a decimal or a hexadecimal number. Hexadecimal numbers must be prefixed by “0x”.

name command requires a valid string argument

This message is a response to bad input from the dbutility command-line console that requires a text argument.

No active structures were found

This message can occur during a dbutility process or clone command. It indicates that no data sets are selected for cloning or updating. In other words, the active columns in the DATASETS client control table are set to 0 (cloning off). This situation could occur when you use a SQL statement to change the value for the active column, but you do not use a WHERE clause.

No configuration file name specified as an argument to the 'f' option

This message indicates that the -f option is not followed by a file specification. You cannot specify a null configuration file by omitting the parameter for the -f option.

No usable link data found in LINK_AI record received from server, record ignored

This error indicates that the Client was unable to find any matching columns in the data tables for a link after image record. Make sure that you did not set active=0 for any such columns as this makes it impossible to use links.

Non-link item 'name' in table 'tabname' cannot follow link items, command aborted

When using DMSII links, the Client requires that all links be placed at the end of the table. Adding non-DMSII columns to the end of the table results in this error. To rectify this problem, you need to change the value of the item_number columns of the links in DATAITEMS so that they land after all non-link items.

Null Record file does not contain an entry for DataSet name[/rectype]

This message, which can occur during a process or clone command, indicates that the null record entry for the specified data set is missing from the file. The most common cause of this error is enabling the configuration parameter read_null_records for a data source that was already replicated. To rectify this problem, run a redefine command with the -R option to rebuild the null record file.

Null Record file "datasource_NullRec.dat" is corrupt

This message, which can occur during the define and redefine commands, indicates that the specified file is corrupt because the Client could not locate a record that is supposed to be in the file. To rectify this problem, re-run the redefine command with the -R option to rebuild the null record file.

Open failed for archive file "name", errno = number (errortext)

This error, which can occur during a Client reload command or a DBClntCfgServer configure command, indicates that the program got a system error when trying got open the archive file.

Open failed for bcp format file "name", errno = number (errortext)

This message applies to the Client for Microsoft SQL Server. It can occur during a generate command, and it indicates that the Client cannot create the specified bcp format file. The included system error should explain the cause of the problem.

Open failed for binary configuration file "name", errno = number (errortext)

This is an indication that the Client could not open the specified binary configuration file. The Client expects to find the file dbridge.cfg in the config subdirectory. Using a file of a different name is not supported for binary files when using the service.

Open failed for data file "name", errno = number (errortext)

This message can occur during a process or clone command. It indicates that the Client cannot create the specified data file used for holding bulk loader data. The included system error should explain the cause of the problem.

Open failed for dbload format file "name", errno = number (errortext)

This message applies to the Client for Informix. It can occur during a generate command, and it indicates that the Client cannot open the specified file for write. The included system error should explain the cause of the problem.

Open failed for db2 load command file "name", errno = number (errortext)

This message applies to the Client for DB2. It can occur during a generate command, and it indicates that the Client cannot open the specified file for write. The included system error should explain the cause of the problem.

Open failed for discard file "name" for table 'name', errno = number (errortext)

This error, which can occur during a process or clone command, indicates that the program got a system error when trying to open the discard file. The discard file is created when the data set is cloned; from thereon it is always opened in append mode. You must delete the contents of this file when you no longer need it.

Open failed for global configuration file "/etc/Attachmate/DATABridge/6.1/globalprofile.ini"

In order to be able to run UNIX clients You must first create the file /etc/Attachmate/DATABridge/6.1/globalprofile.ini with the correct information. This file serves the same purpose as the Windows registry for the Client. It defines the directories where the software was installed and the global working directory where the client lock files are created in the locks subdirectory. This file also defines the userid under which the daemon is to be run. If you do not create this file, the Client will display this error and exit.

Open failed for Null Record file "name" failed, errno = number (errortext)

This message indicates that the Client failed to open the file datasource_NullRec.dat. The most common cause of this error is enabling the configuration parameter read_null_records for a data source that was already replicated. To rectify this problem, run a redefine command with the -R option to rebuild the null record file.

Open failed for pipe for shell "filename", errno = number (errortext)

This message, which applies to UNIX, can occur during a process or clone command. It indicates that the program could not open the shell script file which launches the SQL*Loader. The included system error should explain the cause of the problem.

Open failed for script file "name", errno = number (errortext)

Example: "Open failed for script file "name", errno=2, (No such file or directory)"

This message can occur during a process, clone, generate, refresh, runscript or createscripts command. It indicates that the Client cannot find or open the specified script file. This error typically occurs if the dbscripts sub-directory does not contain the scripts or the user_scripts_dir parameter is not properly set up. Make sure that your scripts are in the directories where they are expected to be (dbscripts, scripts or the client working directory) for this data source and that you have not inadvertently deleted any script files. If you ran a createscripts command before the error occurred, the user_script_dir parameter may be pointing to a non-existent directory.

Open failed for sqlldr control file "name", errno = number (errortext)

This message applies to the Client for Oracle. It can occur during a generate command, and it indicates that the Client cannot open the specified script file. The system error message that is included in this message should give you a handle on why this error occurred.

Open failed for text configuration file"name", errno = number (errortext)

This is an indication that the Client could not open the specified text configuration file. If you specified it through the use of the -f option, make sure that you typed the name correctly. The Client expects to find the text-based configuration file dbridge.cfg in the config subdirectory. Unless you use the -f option, the import command expects to find the dbridge.ini file in the config directory.

Open_Stmt failed for thread[nn]

This error, which is limited to multi-threaded updates, is usually caused by an SQL error while creating the STMT. STMT executes pre-parsed SQL using host variables to pass the data. It could also be the result of memory allocation error. See the preceding error message for details about the problem.

Optimized update failure initiated rollback failed -- program exiting

This error, which is limited to multi-threaded updates, indicates that the program initiated rollback failed. The program treats a COMMIT request by the DATABridge Engine as aROLLBACK request and reruns the transaction group with update optimization off. This is done in order to correct a situation that could otherwise result in missing updates.

We recommend that you do not use update optimization and multi-threaded updates at the same time. If you are worried about performance, flatten the OCCURS clauses instead.

Parser table in error

This is an internal error indicating that the parser table for the Windows console command is in error. Contact Attachmate Technical Support if you get this error.

Partial load failed for table 'name' using bcp - see file "bcp.tablename.log" for more information

This message applies to Microsoft SQL Server. It can occur when the bcp utility stops processing during a segmented load of a table. The amount of the segmented load is determined by your setting for max_temp_storage.

Partial load failed for table 'name' using sql*loader - see file "sqlld.tablename.log" for more information

This message applies to Oracle (Windows). It can occur when SQL*Loader stops processing during a segmented load of a table. The amount of the segmented load is determined by your setting for max_temp_storage.

Pass1 of two pass modify failed (return code = ddd)

This message, which can occur during a process or clone command, indicates that an error occurred while processing an update for an item with an OCCURS DEPENDING ON clause. The value of the item pointed to by the OCCURS DEPENDING ON changed. The Client updates the rows that remain in the table and then inserts new rows or deletes rows that no longer exist from the OCCURS table. The following values indicate the status of updating the tables, and the Client handles them appropriately:

6 - rows to insert
7 - rows to delete
8 - one of the updates found no matching rows

If any other value is returned, it is probably an internal error or some other error that caused the Client to return an unexpected status. Contact Attachmate Technical Support if this error is not caused by another error during the process of updating the table.

Prepare failed for SQL statement: sql_stmt

This message can occur during a process or clone command. It indicates that an error occurred while parsing a SQL statement used to call stored procedures for updating data or control tables. See the relational database API message that precedes this message (on the screen or in the log file) for more information. See also Oracle Call Interface (OCI) Errors or Microsoft SQL Server ODBC Errors.

Processing of configuration file "name" failed

This message occurs any time the Client finds an error in the text-based configuration file that causes it to terminate.

Program terminating, due to bulk loader failure

This message can occur during a process or clone command. It indicates that there was a bulk loader failure during data extraction and that the Client is terminating.

Program terminating, error occurred in a worker thread

This message indicates that a fatal error occurred in an Update Worker thread causing the program to terminate. This message is displayed but the main thread once it realized that such an error has occurred. To determine what's causing the problem in the Update Worker thread, see the additional error messages.

pthread_create failed for 'name', error = number (errortext)

(UNIX) This error indicates that the system could not create the specified thread. The Index Creator Thread creates indexes for tables whose data extraction completes successfully. The Watchdog Thread performs periodic checks for things such as lack of response from the server. When using multi-threaded updates, several Update Worker Threads are responsible for executing SQL.

This is an internal occur that should never occur. It is an indication that the system might be low on resources.

pthread_mutex_init failed for 'name', errno = errno (errortext)

(UNIX) This error is indicates that the initialization of a mutex in question failed. It is an internal occur that should never occur.

quit after command requires an audit file number in the range 0 to 9999

This message can occur during a process or clone command and indicates that the AFN for the QUIT command is invalid.

quit command not in the form: "QUIT {AT hh:mm | AFTER nnnn}"

This message indicates that there is a syntax error in the dbutility console QUIT command issued by the operator.

rc = status for SQL_stmt at line# of dbbd.c

Any ODBC operation whose return status is not one SQL_SUCESS, SQL_SUCCESS_WITH_INFO, SQL_ERROR or SQL_NO_DATA_FOUND will result in this message being displayed. The line# in dbdb.c is provided to help determine which SQL statement got this unexpected result.

Read failed for Null Record file, errno = number (errortext)

This message, which can occur during a process, clone, or redefine command, indicates that an I/O error occurred while reading the null record file. To rectify this problem, try running a redefine command with the -R option to rebuild the null record file.

Read failed for trace descriptor file "name", errno = number (errortext)

The trace descriptor file trace.cfg is a tiny binary file used by the client to keep track of the trace file name. If the error persists simply delete this file and let the client create a new one. The most like source of this error is file ownership conflicts between the command-line client and the service. See the system error in this message for more information about why this error occurred.

ReadFile failed for console, error = number

This message indicates that the Console thread for the Windows Client received a read error while reading keyboard input. You typically get this error message when the Client is terminated by pressing Ctrl+C.

Real data set link for data set name[/rectype] is NULL, make sure that automate_virtuals is true

In a MISER database, user scripts create a pointer that links the virtual data sets and the real data sets from which they are derived using the virtual_ds_num, real_ds_num and real_ds_rectype columns in the DATASETS client control table. If the configuration parameter automate_virtuals is not enabled, this pointer is not set up and executing a createscripts command returns this message.

Received invalid structure index for DataSet name[/rectype]

This message can occur during a process or clone command. It indicates that the DATABridge Server returned a negative structure index in the response packet for a DB_Select RPC call. When this occurs, set the active column to 0 in the DATASETS table for the specified data set and try again. If this error continues, contact Attachmate Technical Support.

Refresh of stored procedures failed for DataSet name[/rectype]

This message, which can occur during a reorg command, indicates that the Client was unable to drop and recreate the three stored update procedures that are associated with the tables for the data set. See the preceding SQL error to figure out what causes the error.

ReleaseSemaphore failed for 'name', error = number (errortext)

This message, which can occur during a process or clone command for Windows Clients, indicates that an error occurred while attempting to post the semaphore (either the bcp_work_semaphore or the index_work_semaphore, which pass work items to the corresponding threads during the data extraction phase). This is a system error which should not occur under normal circumstances. Reboot Windows.

Resequencing DATAITEMS table entries for item 'name' of table 'tabname'

The define and redefine commands resequence DMSII links to always appear at the end of data tables. This happens because, during data extraction, data for the links is received as a separate record and must be added to the previous record that contained the data part of the data set record. This message indicates that a SQL error occurred during the resequencing. See the relational database API message that precedes this message (onscreen or in the log file) for more information.

RPC PROTOCOL ERROR: Type = responsetype StrNum=number

This message can occur during any Client command that involves communications with DBServer Accessory or Enterprise Server. It indicates that an RPC protocol error occurred while trying to read a response packet to an RPC. In this case, try again. If this error occurs persistently and is reproducible, contact Attachmate Technical Support.

RPC response length of dddddd (0xhhhhhhhh) is too large

This message, which is very unlikely to occur, indicates that an RPC response packet has a bad length word. All RPC responses are preceded by a 4-byte length. This error indicates that the message is too long to be valid. In the unlikely event that you get this error, simply you restart the client. If you still get the error, call Attachmate Support.

Script generation failed

This message can occur during a dbutility generate command. It indicates that the scripts could not be generated. Typically, this message is preceded by other more explanatory messages.

Scripts for DataSet name[/rectype] are not current; you must first run a generate command

This message, which can occur at the start of a process or clone command, indicates that the program believes that you need to run a generate command. The DS_Needs_Generating bit of the status_bits column of the DATASETS entry is used to keep track of this. As stated, run a generate command before going any further.

Select of DATATABLES failed

This message can occur during a define or redefine command. It indicates that the SQL SELECT statement used to get the external table names from the client control table DATATABLES failed. See the relational database API message that precedes this message (on the screen or in the log file) for more information. See also Oracle Call Interface (OCI) Errors or Microsoft SQL Server ODBC Errors.

sem_init failed for 'name', errno=number (errortext)

(UNIX) This error is indicates that the initialization of a semaphore failed. The Client uses several semaphores to synchronize activities between the various threads. This is an internal occur that should never occur, unless the system is low on resources.

Send_DS_Added_Msg() failed

This is an internal error that indicates that the Client was unable to send an IPC message to the Console. The most common cause of the error would be a network error.

Send_DS_Deleted_Msg() failed

This is an internal error that indicates that the Client was unable to send anIPC message to the Console. The most common cause of the error would be a network error.

Send_DS_Mode_Chg_Msg() failed

This is an internal error that indicates that the Client was unable to send a IPC message to the Console. The most common cause of the error would be a network error.

Send_IPC_Message() failed

This is an internal error that indicates that the Client was unable to send and IPC message to the Console. The most common cause of the error would be a network error.

Send_IPC_Response() failed

This is an internal error that indicates that the Client was unable to send and IPC message to the Console. The most common cause of the error would be a network error.

Set of DATEFORMAT failed

This message applies to the Client for Microsoft SQL Server. It indicates that the attempt to override the database server default date format was not successful. See the DBLIB message that precedes this message (onscreen or in the log file) for more information.

Set of nocount off failed

This message applies to the Client for Microsoft SQL Server. It can occur when you first start the Client and it indicates that the attempt to enable row counts by execution the SQL statement “SET NOCOUNT OFF” failed. See the ODBC message that precedes this message (on the screen or in the log file) for more information. See also Microsoft SQL Server ODBC Errors.

Source record missing in unload file "name"

This message, which can occur during a DBClntCfgServer configure command, indicates that the unload file that is being used to hold the backup copy of the client control tables does not have a source record ( S, …) immediately following the version record (V, …). It is an indication that the unload file is corrupt. If you haven't modified this file, contact Attachmate Technical support.

sp_recompile failed for table 'name'

This message applies to Microsoft SQL Server. It can occur during a process or clone command after an index for a table is created. The sp_recompile stored procedure informs the relational database that all the procedures associated with the table should be recompiled at the next execution. This ensures that the query plans associated with the tables use the index that was just created.

SQL*Loader control file entry for item 'name' (dms_type = tt) cannot be generated

This message, which applies to the Client for Oracle, can occur during the generate command when creating the SQL*Loader control file. If an item whose dms_item_type column contains an illegal value is encountered, the program displays this error. This message originates from exactly the same conditions as the message "ERROR: Item name (dms_type = number) cannot be cloned," which can occur during a process or clone command.

SQLAllocHandle(SQL_HANDLE_ENV) failed

This error, which can occur with any ODBC or CLI clients, indicates that the ODBC SQLAllocHandle call for the environment handle failed. Check the preceding ODBC error message for more information about the reason for the failure.

Stmt allocation failed for table 'name'

This message can occur during a process or clone command, and it indicates that the Client was unable to create a stmt for processing an update to the specified table. See the database API error that precedes this message to determine the cause. The aux_stmts parameter may be set too high for your hardware configuration. Try reducing the number of the aux_stmts parameter to 10 or 20. See aux_stmts. See also Oracle Call Interface (OCI) Errors or Microsoft SQL Server ODBC Errors.

System command failed for file "name", errno = number (errortext)

This message, which only applies to Windows Clients, can occur during a dbutility process or clone command. It indicates that an error occurred while spawning a command prompt session to run the bulk loader utility (SQL*Loader for Oracle and bcp for Microsoft SQL Server). You can look up the errno value in the header files for the Microsoft C++ library routines.

System command failed for file load.tablename.cmd, errno=87 (Unknown error)

A system command failed. This error can occur when the database and server configuration values passed to the bcp utility do not match the values configured for the ODBC datasource, or when the bcp utility is not found in the path.

Table definition failed for DataSet name[/rectype]

This message can occur when you run dbutility define or redefine. It indicates that the client control tables were not populated. For details on why this occurred, see the error messages that occurred during processing of the table specified by name.

Table 'name' does not contain a res_flag column

This message, which only applies to MISER databases, indicates that a multi-input virtual data set does not have the column it requires for tracking resident history records. Make sure that you did not inadvertently set active to 0 for this column; its name usually contains the text "res_flag" and its dms_subtype value is 255.

Table name prefix for DataSource name is too long

This message is an internal error, which indicates that the tab_name_prefix value, read from the DATASOURCES client control table, is longer than 8 characters. The only way this can happen is if you alter the DATASOURCES table and increase the length of this column.

Table 'name' which has an index defined has no key items, index script generation failed

This error occurs if you disable cloning for all the key fields in the index for the specified table. When the generate command tries to generate the index creation script, it displays this message instead of generating a bad create index SQL statement.

Table 'name' which has links is not using my_aa as the primary_key

This error can occur during a process or clone command and indicates that the specified table contains link items but is not using my_aa as the key. You cannot set active=0 or item_key=0 for the my_aa column for a table that contains links.

Tables for DataSet name[/rectype] are not current; you must first run a redefine command

This message, which can occur at the start of a process or clone command, indicates that the layouts of the tables mapped from the data set are not current; therefore, they need to be updated via the redefine command. The DS_Needs_Remapping bit of the status_bits column of the DATASETS client control table keeps track of this.

Tables for DataSet name[/rectype] need to be mapped; you must first run a redefine command

This message, which can occur at the start of a process or clone command, indicates that the mapping of the data set to relational database tables was not performed; therefore, you need to run a redefine command. The DS_Needs_Mapping bit of the status_bits column of the DATASETS client control table is used to keep track of this. This situation typically occurs if you try to run a process or clone command after setting the active column to 1 for a data set that was not previously mapped.

Target DBServer has a protocol level of ll, which does not support the "tcptest" function

This message appears if you run a tcptest command with older host software. The tcptest command requires version 3.0 or newer host software, which has a protocol level of 7 or higher.

The configured number of stmts (mmm) is insufficient for nn threads

Multi-thread updates need a greater number of configured database API statements (STMT) because of the increased number of concurrently executing SQL operations. The minimum allowed value is 20+ the number of threads.

Time must be specified as 'hh:mm', legal ranges are 0 to 23 for hh and 0 to 59 for mm

This message can occur in response to a Windows console command and indicates that the time specification values are invalid.

Trace file prefix is too long, maximum allowable length is 20, value truncated

You can specify a prefix for the Client trace files in the Client configuration file, however this prefix is limited to 20 characters. If you use a longer prefix, you get this error. The default prefix is “trace”.

Tswitch command failed

The trace switch command is a dbutility console command that closes the current trace file and opens a new file. If an IO error occurs during this operation this error is displayed. See Log and Trace Files .

Unable to access registry key SOFTWARE\Attachmate\DATABridge Client\6.1

The Client needs to access the Windows Registry created by the installer in order be able to run. If you did not use the installer and tried to copy the files, you will not get very far. Do not attempt to change the registry keys created by the installer as this might result in the Client being unable to operate.

Unable to access registry key SOFTWARE\ODBC\\ODBC.INI

The Microsoft SQL Server Client gets the server name from the Windows Registry when the configuration parameter use_odbc_reg is set True. This error indicates that the client is unable to access the key in question. You should not set this parameter to True, unless your server name has dots in it. Contact customer support if you get this error.

Unable to allocate nnnn bytes of memory

This message can occur during all dbutility commands except dbutility configure. It indicates that the operating system does not have enough memory for various Client structures. The most common occurrence of this message is while loading the client control tables. If this error occurs, try again after quiting all other applications and make sure that your system meets the minimum memory requirements for the hardware and software.
Check the size of your swap file. The swap file could be too small or you could be running out of disk space on the volume where the swap file is located.
Reboot the server if all else fails.

Unable to convert DMSII type number to [a numeric] time for item 'name' in table 'name', {record will be discarded | time set to NULL}

- Keys: columnname = value, ...

This message can occur during a dbutility process or clone command when you map a DMSII ALPHA or REAL item to a relational database integer data type (or in the case of SQL Server 2008, a time data type). The dms_subtype (DMSII type number) specified must be one of the values defined in DMSII Times.

Unable to convert DMSII type number to date for item 'name' in table 'name', {record will be discarded | date set to NULL}

- Keys: columnname = value, ...

This message can occur during a dbutility process or clone command when you map a DMSII NUMBER or ALPHA item to a relational database date type. The dms_subtype (DMSII type number) specified must be one of the values defined in Cloning DMSII Dates, Times, and Date/Times.

Unable to create "name" directory, errno=number (errortext)

This message, which can occur during a dbutility configure or define command, indicates that the Client was unable to create the specified directory. (This directory includes config, logs, dbscripts, discards, and locks subdirectories.)

Unable to create archive file "name", errno = number (errortext)

This error, which can occur during an unload command, indicates that the program got a system error when trying to create the archive file.

Unable to create backup user script directory "path", errno= number (errortext)

This message, which can occur during a createscripts command, indicates that the Client was unable to create the backup user script directory. The Client tries to create the directory if it doesn't exist. This might simply be a configuration error. Check the configuration file parameter user_script_bu_dir to see if it mistyped.

Unable to create working directory "path" (errno=errno)

This message, which can occur during a dbutility configure or define command, indicates that the Client was unable to create global working directory for the client. The Client requires this directory for operations as this is the location in which locks files are created.

Unable to drop DATABridge Client control tables

This message can occur during a dbutility dropall command. It indicates that an error occurred while dropping the client control tables. In this case, check the following:

See the DBLIB message that precedes this message (on the screen or in the log file) for more information. For Oracle, see Oracle Call Interface (OCI) Errors. For Microsoft SQL Server, see Microsoft SQL Server ODBC Errors.
Look at the previous output messages to see how far the Client progressed before encountering the error.
Note: After this message appears, you cannot rerun the dbutility dropall command if some of the DATABridge control tables were dropped. You might have to use a relational database query tool to drop the remaining tables.

Unable to find control tables for DataSource name in file name

This error, which can occur during a reload command, indicates that the archive file does not contain any entries for the data source on the command line. You either mistyped the data source name on the command line, you are not using the correct archive file, or you did not back up the data source you are trying to reload.

Unable to expand config buffer

This message can occur when the Client writes the binary configuration file. The Client allocates a buffer that is big enough to hold a reasonable amount of text data. However, if the configuration file contains a lot of text data, this buffer must be resized. If the attempt to grow this buffer fails, this message occurs. For details, see “Unable to allocate nnnn bytes of memory” in the previous error messages.

Unable to find DataSource name

This message can occur during all dbutility commands except dbutility configure, define, and dropall. It indicates that you entered a data source name that is not in the DATASOURCES client control table. This can occur if the data source name is misspelled, or if you have not created the data source yet.

Unable to find matching concat data item (nnn) record for item 'name' in table 'name'

This message indicates that the dms_concat_num column in DMS_ITEMS contains an incorrect value. This value may refer to a non existent or inactive column. The user script involved is most likely the cause of the error and should be examined.

Unable to find matching data item record for DMS Item Number nnn in table 'name'

This error can occur during any Client command that loads the client control tables when the data source contains an active data set that has active item with an OCCURS DEPENDING ON clause. The loading of the client control tables dynamically sets up the links between the given item and the item on which the OCCURS clause depends. This link may go back to the primary table if the OCCURS item is in a secondary table. The dms_item_number column is used as a foreign key. If the load cannot find such an item in the DATAITEMS table this message is displayed.

The only possible cause for this error is the active column of the DMS_ITEMS table of the depends item set to 0, causing it vanish from the DATAITEMS table. To resolve this error, set the active column to 1, set the DS_Needs_Remapping bit in the ds_options column of the corresponding DATASETS client control table, and execute a redefine and a generate command.

Unable to get stmt for stored procedure '{i|u|d}_name'

This message, which can occur during a process or a clone command, indicates that the Client was unable to get a statement (OCI, ODBC or CLI) for executing the specified stored procedure. This message is typically preceded by a database API error message.

Unable to get stmt for stored procedure U_name

This message, which can occur during most commands, indicates that the Client was unable to get a statement (OCI, ODBC or CLI) for executing the specified stored procedure which updates the corresponding client control table. This message is typically preceded by a database API error message.

Unable to handle sql_type dd for external column 'name' in table 'name'

This message occurs during a process or clone command and indicates that the Client cannot handle the sql_type for the external column being added to the specified data set.

Unable to load backup copy of control tables for DataSource name

During Client Configuration operations, the initial state of the control tables is automatically saved in the unload file src_reorg_ddd.cct where src is the data source name and ddd is the update level of the database. Client Configuration operations run much like redefine commands. When the Client Configurator needs to compare the old and the new layout it reloads the old control tables from this file.

CAUTION: Deleting the unload file is not recommended until you have completed all customization tasks in the Client Configurator. The Client automatically deletes the unload file when it no longer needs it. If you run the Client Configurator multiple times before running a process command, subsequent executions will not back up the control tables. The Client Configurator needs the unload file (that is, the original backup) to determine which changes have been made.

Unable to load data source list

This message occurs during a define or redefine command indicates that the Client cannot load the data source list.

Unable to locate the extended translation {DLL | shared library} "filename"

The attempt to locate the external data translation DLL, DBEATRAN.DLL, using a LoadLibrary call failed. Windows looks for a DLL in several places, the first of which is the directory where the program being executed resides. Under normal circumstances, this is the program directory created by the install process of the Client (c:\Program Files\Attachmate\DATABridge\[version]\dbase_type). It is recommend that the DLL be copied into this directory. Windows also looks for the DLL in the current directory, the Windows system directory, the Windows directory, and the directories listed in the PATH environment variable. If the DBEATRAN DLL is in none of these places, this error message is displayed when you set the configuration parameter use_ext_translation to Yes.

On UNIX, the environment variable LD_LIBRARY_PATH must contain the directory where the shared library resides. On some 32-bit systems (for example, SHLIB_PATH for HP-UX and LIBPATH for AIX), a different environment variable is used.

Unable to open archive file 'name'

This error, which can occur during a reload command, indicates that the program got a system error when trying to open the archive file.

Unable to open discard file name for table name

Unable to read translation configuration files and initialize tables

This message, which only occurs at the start of process or clone command when using a version 6.1 or newer external translation DLL (or shared library), indicates that the translation DLL initialization was unsuccessful. In most cases,the DLL can not find the translation configuration file. The DLL expects these configuration files to be located in the config directory with the other client configuration files.

Unable to read version record from archive file "name", errno = number (errortext)

This message can occur during a reload command if the file I/O error occurs when trying to read the first record of the file, which is always V,version. The included system error should give you more information about why this error occurred.

Unable to retrieve value for 'INSTALLDIR' from registry (result = nnn)

This error indicates that the Windows registry keys for the Client are corrupt. The Client expects to find the string INSTALLDIR (the name of the directory in which the software was installed) in HKEY_LOCAL_MACHINE\SOFTWARE\Attachmate\DATABridge Client\[version]

Unable to retrieve value for 'Server' from registry (result = nnn)

This error indicates that the SQL Server Client was unable to get the server name from the Windows Registry registry key HEY_LOCAL_MACHINE\SOFTWARE\ODBC\\ODBC.INI. (The registry key provides the SQL server name only if the configuration parameter use_odbc_reg value is True. This value should be avoided unless your server name contains periods.) If you get this error, contact Attachmate Technical Support.

Unable to retrieve value for 'WORKINGDIR' from registry (result = nnn)

This error indicates that the Windows registry keys for the Client are corrupt. The Client expects to find the string WORKINGDIR (the working directory for the service and location of the locks subdirectory) in HKEY_LOCAL_MACHINE\SOFTWARE\Attachmate\DATABridge Client\[version]. For more information about the working directory, see the DATABridge Installation Guide.

Unable to retrieve database/server names from data source

The SQL Server and Informix clients use SQLGetInfo calls to programmatically retrieve the database and server name for the ODBC data source, which eliminates the need to specify the names in the configuration files. This message indicates that there was an error while retrieving these names. Check the preceding ODBC error message for more information about the reason for the failure.

Unable to update specified external column nn

This error can only occur when processing a binary configuration file that contains external_column specifications and indicates that the Client was unable to update its internal table for external column definition. This message is usually preceded by a message that explains why the operation failed.

Undefined date format type (number) for item 'name' in table 'name', {record will be discarded | date set to NULL}
- Keys: columnname = value, ...

This message indicates an invalid value in the dms_subtype column in the DATAITEMS client control table. It can also indicate that you set dms_subtype for a DMSII NUMBER item when the item is actually a DMSII ALPHA item (or vice versa). For more information on setting the dms_subtype column for dates, see Cloning DMSII Dates, Times, and Date/Times.

Undefined section header in configuration file line: text

See Sample SQL Server Client Configuration File for valid section headers.

Unimplemented command cmd_number

This internal DBClntCfgServer error indicates that the Console or Client Configurator attempted to execute an unimplemented RPC. This can only happen if you try to run a newer version of the Console or Client Configurator with an old Client.

Unknown command: command

This message can appear when you misspell a dbutility command, or you enter a command that does not apply to dbutility.

Unknown console command; type "help" to get a list of commands

This message indicates that the operator entered an invalid console command.

Update of colname column in DATASETS table failed for name[/rectype]

This message, which can occur during a process, clone, define or redefine command, indicates that an attempt to update the specified column of the DATASETS Client control table failed. The columns in question include the following columns:

active
misc_flags
status_bits
ds_options

Check the preceding SQL error message to determine why the error occurred.

Update of DATAITEMS entries failed for table 'name' [for DataSet name[/rectype]]

This error can occur during a redefine command or when running the Client Configurator. It indicates that the update of the DATAITEMS control table failed when trying to restore customizations. See the SQL errors that precede this message to find out why this error occurred.

Update of DATAITEMS table failed for 'name' [of table 'name']

This error can occur when running the Client Configurator or when running a redefine command. If it occurs when running the Client Configurator, it indicates that DBClntCfgServer was unable to update the DATATABLES control table as per changes tade by the user. See the preceding SQL errors to determine why this error occurred.

Update of DATASETS table failed for Global_DataSet

This message can occur during a redefine, clone, or process command. It indicates that an error occurred when updating the DATASETS client control table for the Global_DataSet. See preceding API error messages (onscreen or in the log file) to determine the reason for this error.

Update of DATASETS table failed for name[/rectype]

This message can occur during a process or clone command when the DATASETS client control table is updated for a given data set (the /rectype is added for variable-format data sets except type 0 records). This error can occur when the stateinfo is being updated and the optimize_stateinfo parameter is disabled. It can also appear during the cloning of a data set when the stateinfo is changed multiple times and at the end of a process command when the global stateinfo is being propagated to all data sets whose in_sync column has a value of 1. This message can occur when running the Client Configurator. See the database API messages that precede this error for more information.

Update of DATASOURCES table failed for name

This message can occur whenever the DATASOURCES client control table is updated for a given data source. This can happen at the beginning and end of a process or clone command when the status_bits column is updated. See the database API messages that precede this error for more information.

Update of DATATABLES and DATAITEMS tables to preserve pass2 changes failed for DataSet name[/rectype]

This message, which can occur during a redefine command or when running the Client Configurator, indicates that the Client could not update the DATATABLES and DATAITEMS entries while attempting to preserve changes. Check the SQL error message that precedes this message as to why this error occurred.

Update of DATATABLES failed for table 'name' [for DataSet name[/rectype]]

This message, which can occur during most commands, indicates that the Client could not update the DATATABLES entry for the specified table. Check the SQL error message that precedes this message as to why this error occurred.

Update of DATATABLES statistics failed for table 'name'

The Client maintains update statistics for data tables. These statistics are periodically written to the DATATABLES client control tables so the statistics are available to future runs. This error indicates that the watch timer thread was unable to perform the updates needed to do this. Check the SQL error message that precedes this message for clues about why this error occurred.

Update of DMS_ITEMS table failed for item name for DataSet name[/rectype]

This message, which can occur during a redefine command or when running the Client Configurator, indicates that the Client could not update the DMS_ITEMS entries. Check the SQL error message that precedes this message for clues about why this error occurred.

Update of DMS_ITEMS table failed for name (item_number nnn in DataSet name[/rectype])

This message indicates that the DBClntCfgServer was unable to update the DMS_ITEMS control table when processing an update request from the Client Configurator. Check the SQL error message that precedes this message as to why this error occurred.

Update of DMS_ITEMS table to preserve pass1 changes failed for dataset name[/rectype]

This message, which can occur during a redefine command or when running the Client Configurator, indicates that the Client could not update the DMS_ITEMS entries while preserving previous customizations. Check the SQL error message that precedes this message as to why this error occurred.

Update of ds_mode and status_bits columns in DATASETS table failed for name[/rectype]

This message can occur during the second pass of a redefine command when processing a data set whose status_bits field had the DS_Needs_Remapping bit set. The program attempts to set the DS_Needs_Mapping and the DS_Needs_Generating bits before starting the mapping process. If the update SQL statement gets an error, this message is displayed. See the database API messages that precede this error for more information.

Update of set_name and ds_options columns in DATASETS table failed for name[/rectype]

This message can occur during a define or redefine command when processing a data set who ds_options bit DSOPT_Use_AA_Only (0x4000) is set and the data set has valid AA Values (or RSNs). The command attempt to set the set_name of the data set to aa_set_tabname while updating the ds_options column. This message indicates that this update failed. See the database API messages that precede this error for more information.

Update statistics failed for table 'name'

This message applies to the Client for Microsoft SQL Server. It can occur during a process or clone command after an index for a table is created. The update statistics SQL Server command causes the software to update the statistics on the current table. This message indicates that the update statistics command has failed.

Update Worker Thread[nn]: Illegal response type rr encountered

This is an internal error that can only occur when using multi-threaded updates it indicates that an Update Worker encountered a dms buffer whose record type field is illegal. The only record types that are expected by the Update Worker are CREATE, DELETE, MODIFY, MODIFY_AI or LINK_AI any other record types are handled in the main thread. Report this error to Attachmate Support.

Update Worker Thread[nn]: Read_CB_CREATE() failed

This message, which can only occur during a process or clone command when using multi-threaded updates, indicates that the update worker got a fatal error while processing a DMSII CREATE record (that is, a relational database INSERT).

Update Worker Thread[nn]: Read_CB_DELETE() failed

This message, which can only occur during a process or clone command when using multi-threaded updates, indicates that the update worker got a fatal error while processing a DMSII DELETE record.

Update Worker Thread[nn]: Read_CB_LINKS() failed

This message, which can only occur during a process or clone command when using multi-threaded updates, indicates that the update worker got a fatal error while processing a DMSII LINK record.

ERROR: Update Worker Thread[nn]: Read_CB_MODIFY() failed

This message, which can only occur during a process or clone command when using multi-threaded updates, indicates that the update worker got a fatal error while processing a DMSII MODIFY record (that is, a relational database UPDATE).

User columns of dms_subtype n1 and n2 are mutually exclusive

Two of the user columns you specified are mutually exclusive. For example 1 (update_type) and 11 (expanded update_type) or 10 (deleted_record) and 11 (expanded update_type). See Numeric Date and Time in Non-Contiguous Columns.

User DataSet {define | layout} script "filename" failed

This message can appear during a define or redefine command. It indicates that the specified script failed. Check API or SQL errors that precede this message to see why the script failed. If you cannot figure out why it is failing, use the -t 0x800 option for the command or use the runscript command to test the script.

User DataSets global layout script "filename" failed

This message can appear during a define or redefine command. It indicates that specified script failed. Check API or SQL errors that precede this message to see why the script failed.

User DataTables global define script "filename" failed

This message can appear during a define or a redefine command and indicates that the specified script failed. Check API or SQL errors that precede this message to see why the script failed. This message may appear after other related error messages that need to be fixed first.

User script "filename" failed

This message can appear during a runscript command and indicates that the specified script failed. Check API or SQL errors that precede this message to see why the script failed.

User table creation script "filename" failed

This message can appear during a process or clone command and indicates that specified data table creation script failed. Check API or SQL errors that precede this message to see why the script failed.

Value out of range for 'F' option argument

The F option is used to pass dbutility an AFN after which it stops. If you use a value that is not in the range 1 to 9999 this error is displayed.

Value out of range for 'V' option argument -- using nn instead

The V option is used to pass dbutility a control table version to use in the unload command. The value being passed must be greater than 0 and less than or equal to the present version of the client control tables. For 6.1 clients, the client control table version is 24; for 6.0 clients, the version is 23.

Virtual data set link for data set name[/rectype] is NULL, make sure that automate_virtuals is true

Work_desc pool empty

This error, which only occurs with multi-threaded updates, indicates that there is a bug in the Client. The work descriptors are tiny records that are used to queue the same dms buffer on multiple update worker work queues. Running out of these structures is an indication that Client is failing to return some of these top the pool when they are no longer needed.

WORKINGDIR not followed by = sign in file "/etc/Attachmate/DATABridge/6.1/globalprofile.ini"

This message, which is limited to UNIX clients, indicates that the specified line in the global profile file is incorrect. The Client expects this file to conform to the standard INI file format. You will not be able to run the Client without this file, which substitutes for Windows registry entries for the Client.

Write failed for binary configuration file "name", errno = number (errortext)

This message can occur during a dbutility import command or when DBClntCfgServer updates a client configuration file. It indicates that an I/O error occurred while writing to the specified binary configuration file. The system error included in this message should explain why this error occurred.

Write failed for bulk load file for table 'name', errno = number (errortext), Record: recordtext

This message applies only to Windows. This message can occur during a process or clone command and indicates that an I/O error occurred while writing to the specified temporary data file. This message typically occurs when you run out of disk space (resulting in the errortext "Out of Disk Space"). The system error included in this message should explain why this error occurred.

Write failed for discard file for table 'name', errno = number (errortext)

This message, which can occur during a process or a clone command, indicates that an error occurred while writing a record to a discard file whose name appears in the message. The system error included in this message should explain why this error occurred.

Write failed for Null Record file, errno = number (errortext)

This message, which can occur during a define or redefine command, indicates that an I/O error occurred while writing to the null record file. The system error included in this message should explain why this error occurred.

Write failed for pipe for table 'name', errno = number (errortext), Record: recordtext

This message, which is limited to UNIX, can occur during a process or a clone command when the main process is writing data to a UNIX pipe used to pass data records to the bulk loader process that runs the Oracle SQL*Loader utility. errortext provides information as to why the error occurred.