Client Warnings

Warning messages appear onscreen and in the log file. If tracing is enabled, messages are also captured in the trace file. These messages are prefixed by the timestamp hh:mm:ss (where hh is hours, mm is minutes, and ss is seconds).

WARNING: AA values for DataSet name[/rectype] are no longer valid

This message, which can occur during a process command, indicates that a DMSII structural reorganization has invalidated the specified data set that uses AA values as a key. The Client automatically marks the data set as no longer trackable, unless it is re-cloned, by setting its ds_mode column to 12 in the DATASETS control table.

You can either set the data set's mode to 0 or run the next process command with the -y option to force it to be re-cloned.

WARNING: AA values for DataSet name[/rectype] are no longer valid, ds_mode set to 0 to force a re-clone

This message, which occurs during a redefine command or when running the Administrative Console's Customize command, indicates that the specified data set must be re-cloned because its AA Values are no longer valid after a DMSII reorganization.

WARNING: AA values for DataSet name[/rectype] are no longer valid after reorganization

This message, which can occur during a redefine command, indicates that a DMSII structural reorganization has invalidated the keys for the specified data set, marking the data set as needing to be re-cloned (ds_mode to 0). The specified data set uses AA values as a key.

WARNING: Adding a UNIQUEIDENTIFIER column to a table is not supported -- you need to reclone

This message appears when a redefine command encounters a new column that is being stored as a uniqueidentifier. Since all existing rows would have their own GUIDs you must re-clone this table.

WARNING: Adding AA values to a table is not supported -- you need to re-clone

This message, which can only occur during a redefine command or when running the Administrative Console's Customize command, indicates that the command detected that the table uses AA values, which were previously not used. Since we cannot assign the correct values for this column in the existing records, you must re-clone the data set.

WARNING: AFN nnn has no StateInfo updates

This message appears when an audit file that contains no quiet points is processed. This means that you either have a very long transaction or that the audit file is empty

WARNING: All database API functions disabled by 'z' option

This message occurs during a process or clone command with the -z option. The Client loads the control table entries for the selected data source, after which it connects to the host and sets a global flag that disables all relational database functions.

The -z option is a debugging tool that can indicate the non-database time required to extract data for a data set or receive updates from the Databridge Engine.

WARNING: All Engine COMMIT parameters are zero; at least one of them needs to have a positive value

WARNING: All Engine COMMIT parameters are zero; this needs to be corrected immediately as it will degrade performance immensely

These messages, which can occur at the start of a process or clone command indicates the commit parameters are all 0. This means that the Client will try override the Databridge Engine's commit parameters by setting them to 0. Commenting them out in a text configuration file sets these parameters to -1, which instructs the Client will not try to override them.

The second message occurs after an operator console command that changes a commit parameter. It indicates that the resulting commit parameters are in error, as they do not specify any situation under which the Engine should try to do a commit. Since this was caused by an operator command, the Client does not exit, but instead tells the operator that the actions taken need to be reversed.

WARNING: All members of the variable format DataSet name must be recloned, ds_mode set to 0 for rectype nnn

If the ds_options bit DSOPT_Split_Vfmt_ds (0x10000) is set or the configuration parameter split_varfmt_ds is enabled, the Databridge Client does not support the cloning of only certain record types of variable format data sets, as all the fixed part records end up in the table for type 0 records.

WARNING: All the commit parameters for the two processing periods are the same, batch job window disabled

This message indicates that the commit parameters, which can now have two Values when the parameter batch_job_period is set to define a time period during which batch jobs typically run (for example batch_job_period = 22:00, 0200). In this case The first set of parameters is used outside the batch job period window, while the second set is used during the batch period. The Client automatically switches between these two settings by looking at the DMSII timestamp values it receives in State Information records at the end of transactions. This error indicates that the two sets of parameters are identical, which defeats the whole purpose of defining a batch job period.

If you use low values for the commit parameters to minimize the lag time (for example commit_update_inc = 1 and commit_absn_inc = 1), setting them to much higher values during the batch period will improve performance.

WARNING: Archive file was created by a newer version of the program, extra fields will be ignored

This message can occur during a reload command when you attempt to read an archive file that has a higher version than what the program supports. The Client just reads the number of fields it knows about and ignores the rest. You can use the -V option to write the archive files in formats compatible with older Clients. For a list of versions, see dbutility Command-Line Options in the Databridge Client Administrator's Guide.

WARNING: Attempt to clear duplicate records for table 'name' failed

During the data extraction, it is possible to get duplicate records. When a record is moved, it appears more than once in the data set. If the ds_options bit DSOPT_Clrdup_Recs (0x8000) is set in the DATASETS table entry for the data set, the Client remedies this by running the script script.clrduprecs.tabname. This script deletes all records that appear multiple times in the table. The fixup phase involves the processing of audit files that span the times during which the data extraction was done for the data set. It reinstates the correct copy of these records. If the script fails, this error results. See the SQL errors that precede this message to determine why the script failed.

Keys that allow nulls may cause problems with this script and require that you manually remove the duplicate records and recreate the index. Then, you can create the index by running the script script.index.tabname that resides in the dbscripts folder. Once the index is successfully created, set the ds_mode for the data set back to 1 and restart the Client.

WARNING: Attempt to drop procedure U_name failed

This message, which only occurs during a configure or dropall command, indicates that the Client was unable to drop the specified stored procedure (U_name, where name refers to a control table name). Refer to the database API error messages that precede this message to determine the cause of this error. This error will occur if your userid has inadequate privileges for dropping a stored procedure. Starting with version 6.5, the Databridge Client no longer uses stored procedures to update control tables, it uses the actual SQL statement in conjunction with host variables instead. Therefore you should not see this error, except after an upgrade from version 6.5 or older Clients.

WARNING: Attempt to modify record in table 'name' after failed insert was unsuccessful, changing it to a delete/insert (AFN=afn, ABSN=absn, SEG=seg, INX=inx) - Keys: colname = value, ...

This message, which can occur during a process or clone command, indicates that the recovery for a failed insert failed. Normally, the Client tries to recover by doing an update instead of an insert. When the update fails, the Client tries to recover by doing a delete/insert operation. If the specified table is an OCCURS table, all of the rows for the given record are deleted and reinserted. Under normal circumstances, the Client should recover from this situation. This warning indicates that the table likely has missing rows or extra rows, either of which are causing the update to fail.

WARNING: Attempt to propagate global stateinfo for DataSets failed

This message can occur during a process or a clone command after an audit file switch, or when the Client shuts down at the end of the command. It indicates that the attempt to propagate the global State Information to data sets with their in_sync columns set to 1 failed.

WARNING: Attempt to run back-to-back redefine commands; control tables will be reloaded from the backup file

This message indicates that you are running back-to-back redefine commands, which can result in incorrect redefine scripts being generated. To prevent this from happening the Client reloads the control tables from the unload file created by the first redefine command, thus eliminating the possibility of creating bad reorg scripts.

WARNING: Attempt to set MARS failed -- reverting to single thread operations

When multi-threaded updates are enabled, the SQL Server Client enables MARS (Multiple Active Result Sets), a Microsoft ODBC extension option. MARS allows multiple queries that get results to be executed simultaneously. This is done by a SQLSetConnectAttr ODBC call. If this ODBC call gets an IM006 error indicating that the operation failed, this warning is issued and multi-threaded updates are disabled. Make sure that you are not using an old SQL Server ODBC driver. We recommend using ODBC driver 17.4 or newer.

WARNING: Attempt to set parameter param_name to value1 rejected by DBEngine; using value2 instead

This message indicates that Databridge Engine did not set a parameter value as specified by the Client because it was not within the configured allowable range. To change the configured allowable range, contact the administrator for the Databridge host software on the mainframe.

WARNING: Attempt to update {dms_scale | dms_signed} ignored, this is only valid for an ALPHA item being cloned as a NUMBER

When cloning an ALPHA item as a number, you can set the dms_scale and dms_signed columns in DMS_ITEMS to indicate that the item has a scale and/or is signed. This error indicates that the attempt to perform these updates from the Console failed. Look for the corresponding SQL error in the Client log file to determine why the operation failed.

WARNING: Attempt to update stateinfo for DataSets in tracking mode failed

The attempt to update the State Information in the DATASETS table from the Administrative Console failed. See the SQL errors that precede this message to determine why the operation failed.

WARNING: Bad DMS Timestamp 0xhhhhhhhh received, Timestamp set to NULL

This message can occur during a process or clone command when processing a State Information record that has a bad time stamp. This indicates an internal error from which the program recovers by setting the timestamp to NULL to prevent a SQL error.

WARNING: Bad DMS Timestamp 0xhhhhhhhhhhhh received for item 'name' in table 'name', {record will be discarded | date set to NULL} - Keys: colname = value

This message occurs when attempting to interpret a DMSII REAL or ALPHA(6) item as a TIME(6) value and the value of the item is illegal. This can be caused by one of the following problems:

Bad DMSII data
Attempting to interpret data that is not a DMSII TIME(6) as a TIME(6)
The Client recovers by setting the value of the item to a NULL, unless it is a key, in which case the record is discarded.

WARNING: Bad DMS TIME(60) value 0xhhhhhhhhhhhh received for item 'name' in table 'name', {record will be discarded | date set to NULL} - Keys: colname = value

This message can appear during a process or clone command. It indicates that the value of a DMSII REAL or ALPHA(6) item, which is being interpreted as a TIME(60) value, is illegal. This can be caused by one of the following problems:

Bad DMSII data
Attempting to interpret data that is not a DMSII TIME(60) as a TIME(60)
The Client recovers by setting the value of the item to a NULL.

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

This message, which only appears if the configuration parameter verify_bulk_load is set to 1, indicates a mismatch between the number of rows in the table and the number of rows that the Client loaded. Check the bulk loader log file and the discards directory for a discard file for the given table. If the parameter verify_bulk_load is set to 1, the Client ignores the error. However, if it is set to 2, you get a similar error and the Client abends.

WARNING: Bulk load failure has occurred, continuing with process command

When the Client detects a bulk load failure, it adds the data set to a list of data sets that encountered bulk loader failures during the data extraction phase and then it prints this message.

When the data extraction phase ends, the Client displays a message for each data set in the list. This message is the initial indication of the failure, which is reported again when the data extraction completes. Note that if the verify_bulk_load parameter is set to 2, the Client abends as soon as it get the first bulk loader failure.

WARNING: Bulk loader discard file created for table 'name'

This message indicates that the Client detected the existence of a bulk loader discard file (sqlld.*name*.bad or bcp.*name*.bad) after the loading of the table completed. This is an indication that the bulk loader was not able to load all of the records. Look at the bulk loader discard and log files to determine why these errors occurred.

WARNING: Bulk loader thread appears to be hung; main thread waiting

(Windows only) This message indicates that the bulk loader thread could not continue after passing a temporary data file to the bulk loader. Typically, this occurs because the amount of temporary data file storage exceeds the value of max_temp_storage. This message indicates that the bulk loader thread is not finished loading the previous batch of files. If this is caused by the bulk loader simply being slow, the situation will correct itself. If the bulk loader thread is hung, look at the sql*loader or bcp log files to determine the cause.

WARNING: Cannot drop primary key or index for table 'name'

This message indicates that the Client encountered a SQL error while trying to drop an index. The index was being dropped because a bad value in the dt_options column of the DATATABLES control table caused the index type to be wrong. This error can occur if you change the index types that the Databridge Client uses by using means external to the Client (not recommended). See the SQL errors that precede this message to determine why the operation failed.

WARNING: Cannot get Oracle version

This message can occur during any Client command. It indicates that the Client was unable to read the Oracle system table that contains the product version. Contact Micro Focus Custoer Support.

WARNING: Cannot get SQL Server version

This message can occur during any Client command. It indicates that the Client was unable to read the SQL Server version using a "select @@version" SQL statement. Contact Micro Focus Customer Support.

WARNING: Cannot reorganize table 'name'

This message can occur during a redefine command or when running the Administrative Console's Customize command. . It is usually preceded by other messages that indicate why the table cannot be reorganized. In this case, the Client sets the ds_mode column to 0 in the corresponding entry in the DATASETS control table to force the data set in question to be re-cloned.

WARNING: Client operations inhibited between hh:mm and hh:mm

This message indicates that the Client cannot execute a process or clone command because a blackout period is in effect. Blackout periods are defined by the blackout_period parameter in the scheduling section of the Client configuration file.

WARNING: Clone of DataSet name[/rectype] failed during bulk load

When the data extraction phase ends, the Client displays this message for all data sets that encountered bulk loader failures. The actual failure will have already been reported as a bulk loader error. This is a done so that you don't have to look through the log file to find the data sets in question.

WARNING: Clone of DataSet name[/rectype] was not completed

When Enterprise Server encounters a situation that forces it to restart the clone using remote regions (also referred to as "indirect disk"), it aborts the clone. The Client keeps track of this fact for the affected data sets. After the data extraction phase is completed, if any of these data sets have a mode of 0 (that is, the clone was not successfully completed), the Client displays this message.

WARNING: Column name 'name' already in use, using 'name' instead

This message can occur during a define or redefine command. It indicates that a duplicate column name was changed to the specified name to make it unique.

WARNING: Command will have no effect until the next scheduled execution time

This message indicates that the user entered a SCHED command from the dbutility console while the Client was idle.

WARNING: Control tables do not exist, there is nothing to do

This message can occur during a dropall command and indicates that there is nothing to drop because the control tables do not exist.

WARNING: Data Source name has INDEPENDENTTRANS set, extract_embedded parameter ignored

This message indicates that INDEPENDENTTRANS is set to True and therefore, your setting for the extract_embedded parameter is disregarded. If INDEPENDDENTTRANS is False, and the extract_embedded parameter is True, Databridge allows the data extraction of embedded data sets, even though these data sets cannot be tracked.

WARNING: Database API functions previously disabled by 'z' option are now enabled

This message occurs when a process or a clone command is run with the -z option and indicates that the -z option is no longer in effect. This is just a reminder that the relational database did not get updated by this run.

WARNING: Database update level change ignored

This message can occur during a process or clone command and indicates that the Client ignored the change in the DMSII update level because none of the selected data sets were affected by the DMSII reorganization. You should only see this message if you are using a MISER database, in which case the miser_database parameter is set to True. We require that you run a redefine command regardless of whether the Databridge Engine thinks that no data sets are affected. The Engine does not recognize changes to a SET that the Client might be using as the source for the index. We recommend that you set the auto_redefine parameter when using the service to allow the service to automatically run a redefine command and prevent interruptions to the Databridge operations.

WARNING: Data extraction failed for DataSet name[/rectype], it will not be selected

WARNING: Data extraction failed for Virtual DataSet name; all DataSets involved with it will not be selected

The two errors can occurs at the start of the data extraction when a data set whose ds_mode value is 10 (BCP failure) is encountered. The Client treats data sets as if their active column was 0. If this is a virtual data sets, and the parameter automate_virtuals is set to True all dataset that contribute to the virtual data set are also not selected.

You need to determine why the bulk loads failed and remedy the situation, after which you can try re-cloning the affected data sets.

WARNING: DataSet name does not exist -- reload will not be performed

This message can occur during a dbutility reload command, if a list of data sets is specified on the command line and one of them is found not to exist. This message is just a reminder that the data set name in question was ignored.

WARNING: DataSet name[/rectype] allows duplicates, no updates will be allowed

This message indicates that the specified DMSII data set does not have any SETS that do not allow duplicate records and that the AA Values cannot be used as keys. The data set will be cloned; however, subsequent runs of process commands will not track changes for the data set. The only time you receive this message is when you run a generate command. The solution is to use an RSN as a key, as explained in Chapter 2 of the Databridge Client Administrator's Guide.

WARNING: DataSet name[/rectype] can be reorganized, run reorganize command: ds_mode set to 31

This message, which occurs when running a redefine command or the Administrative Console's Customize command, indicates that the Client has generated scripts to reorganize the tables for the specified data set and avoid re-cloning it.

Make sure that you examine the scripts for problems and back up your relational database before you run a reorganize command that will alter the tables.

WARNING: DataSet name[/rectype] does not have valid AA values, Include_AA option ignored

This message can occur during a define or redefine command and indicates that the Client ignores the ds_options bit DSOPT_Include_AA (0x10) because the specified data set does not have valid AA values. You should not use the ds_options bit DSOPT_Include_AA (0x10) because this bit is deprecated.

Use the ds_options bit DSOPT_Use_AA_Only (0x4000) to force the Client to use the AA Values (or RSNs) as the source for the index.

WARNING: DataSet name[/rectype] does not have valid AA values, Use_AA_Only option ignored

This message, which occurs during a define or redefine command, indicates that the Client is ignoring the ds_options bit DSOPT_Use_AA_Only (0x4000), because the specified data set does not have valid AA values.

WARNING: DataSet name[/rectype] has been added

During a process command, the Client compares the new data set list it gets from the Databridge Engine to the old data set list when a DMSII reorganization is detected. If the new data set list contains additional data sets, this message is displayed. The ensuing redefine command will pick up these data sets unless the configuration parameter suppress_new_datasets is set to True.

WARNING: DataSet name[/rectype] has been deleted

During a process command, the Client compares the new data set list it gets from the Databridge Engine to the old data set list when a DMSII reorganization is detected. If the new data set list is missing any data sets, this message is displayed.

WARNING: DataSet name[/rectype] has been initialized

This message can occur during a process or clone command and indicates that the specified data set has been initialized in the DMSII database (that is, all records deleted from it).

WARNING: DataSet name[/rectype] has been reorganized

This message can occur during a process or clone command if the Databridge Engine detects a structural reorganization or a change in item counts (for example, a filler substitution). For every data set affected by the reorganization, the Databridge Engine sends the Client a State Information record whose ds_mode field has a value of 3. The Client sets the bit DS_Needs_Redefining (8) in the status_bits column of the corresponding DATASETS entry and displays this message.

WARNING: DataSet name[/rectype] has been reorganized, you must first execute a redefine command

This message can appear during a process or clone command if you try to select a data set whose format level is not current. The Client sets the bit DS_Needs_Redefining (8) in the status_bits column of the DATASETS entry for the data set. It also sets a flag that causes the Client to exit with an exit status value of 2 immediately after all the data sets have been selected. It does not stop immediately so that it can catch all such data sets before you run a redefine command. The redefine command will most likely require that run a reorganize or generate command before resuming operations.

WARNING: DataSet name[/rectype] has been reorganized (fmtlevel: mmm -> nnn)

During a process command, the Client compares the new data set list it gets from the Databridge Engine to the old data set list when a DMSII reorganization is detected. This message only appears when the Databridge Engine fails to detect the fact that a data set has been reorganized. The Client handles the reorganized data set accordingly.

WARNING: DataSet name[/rectype] has ds_mode=0, run a reorganize (or generate) command before re-cloning it

This message, which occurs when running a redefine command or the Administrative Console's Customize command, indicates that the specified data set will be re-cloned and program scripts must be generated (that is, via the generate command). If other data sets are involved, the generate command is automatically invoked when you run a reorganize command. If you do not run a reorg command, you must execute a generate command before you re-clone the data set.

WARNING: DataSet name[/rectype] has ds_mode=mm, mode set to 0

This message occurs during a redefine command or when running the Administrative Console's Customize command. It indicates that a data set has an invalid ds_mode and will be re-cloned as a result. Note that, a ds_mode value of 10 is used by the Client to indicate bulk loader failure.

WARNING: DataSet name[/rectype] has embedded datasets, AA values will be used as keys

This message can occur during a define or redefine command. It indicates that the Client will use AA values (or RSNs) as the keys for the specified data set.

WARNING: DataSet name[/rectype] has invalid AA_Values, it will not be selected

This message, which occurs during a process or clone command when data sets are selected, indicates that the Client encountered a data set whose ds_mode is 12 and whose active column is 1. The ds_mode value of 12 indicates that the AA values for the data set are no longer valid. The Client treats this type of data set as if its active column was 0 until it is re-cloned. To force a re-clone, you must set ds_mode to 0 using the Databridge Administrative Console or the relational database SQL query tool, or run the process command with the -y option.

WARNING: DataSet name[/rectype] has no active tables; active column set to 0

This message, which can occur during a process or clone command, indicates that the active columns have been set to 0 in all tables associated with the specified data set. In this case, the Client automatically sets the data set's active column to 0, as there are no tables to populate.

WARNING: DataSet name[/rectype] has no index, it will not be selected

This message can occur during a process or clone command and indicates that the specified data set will not be selected because its ds_mode had a value of 11, which indicates that it has no index and therefore cannot be tracked.

WARNING: DataSet name[/rectype] has no unique keys, AA values will be used as keys

This message can occur during a define or redefine command. It indicates that the Client will use AA values (or RSNs) as the keys for the specified data set.

WARNING: DataSet name[/rectype] has no unique keys and AA values are not usable as keys - Change tracking is not possible unless a composite key is created

This message can occur during a define or redefine command. It indicates that the specified data set has no index and that AA values cannot be used as the keys. Your only recourse is to create a composite key or possibly enable RSNs for the data set in DMSII (EXTENDED attribute).

WARNING: DataSet name1[/rectype] is a remap of DataSet name2[/rectype], active column set to 0

The term remap is a DMSII term that is roughly equivalent to the term view in a relational database. In DMSII, a data set can have one or more remaps. The original data set is referred to as the base structure. It is also possible to have a remap for a variable-format data set.

Note

/rectype only appears for variable-format data set records that have a non-zero record type (that is, contain a variable part). By default, the Client only clones the base data set and sets the active column to 0 for all remaps.

If you want to use a remap instead of the base structure, you can do so by changing the values in the active columns in the DATASETS table for the data sets in question.

WARNING: DataSet name[/rectype] is embedded and INDEPENDENTTRANS is reset - Change tracking is not possible

When INDEPENDENTTRANS is set to FALSE in the DASDL, the parent-child relationship for embedded data sets is lost, and it's impossible to track changes for these data sets. You can clone them if you set the configuration parameter extract_embedded to True.

WARNING: DataSet name[/rectype] is not the first remap of structure #strnum, active column set to 0

This warning, which can occur during a define or redefine command, indicates that the search for the base structure of a remap was unsuccessful, but we found more than one remap of the base structure and are using the first remap as a substitute for the base structure. If this is not what you want, you can rectify the situation by changing the active columns of the remaps of the base structure so that the Client picks the one you want.

WARNING: DataSet name[/rectype] must be recloned, run reorganize (or generate) command: ds_mode set to 0

This message occurs during a redefine command or when running the Administrative Console's Customize command. It indicates that the data set in question must be re-cloned because the layout changes cannot be applied using alter commands. To resolve the issue, the scripts for the table need to be recreated by running either a reorganized or a generate command. (The reorganize command executes a generate command.)

WARNING: DataSet name[/rectype] record size sent by the Databridge Engine is too short, length changed from 0xhhhhhh to 0xhhhhhh)

The Client computes the sizes of data set records and compares its result to those passed to it by the Databridge Engine in the recsz_bytes column of the DATASETS table. If the resulting length is larger than the one provided by the Databridge Engine the Client uses the computed value and issues this warning to make it known that the Engine is sending the wrong length. Notify Micro Focus Customer Support if you ever get this message.

WARNING: DataSet name[/rectype] which contains embedded DataSets does not have valid AA values

This message, which can occur during a define or redefine command, indicates that the specified data set contains embedded data sets but no valid AA values.

WARNING: DataSet name[/rectype] which contains links does not have valid AA values

This message can occur during a define or redefine command and indicates that the specified data set contains link items but no valid AA values. These types of links cannot be supported.

WARNING: DataSet name[/rectype] will be recloned because DataSet name1[/rectype1] is being recloned

The process command will re-clone the specified data set because the following conditions exist:

The configuration parameter automate_virtuals is set to True.
The specified data set is the secondary source for a virtual data set that gets its input from more than one DMSII data set. This data set was cloned previously but does not have a ds_mode value of 0.
The data set that is the primary source for the virtual data set has a ds_mode of 0 (it is being re-cloned).

For example, assume that SV-HISTORY and SAVINGS both provide data for the virtual data set SV-HISTORY-REMAP, and SV-HISTORY is the primary source. When the process command finds that SV-HISTORY is being re-cloned, it ensures that SAVINGS is also re-cloned. Unlike the clone command, which produces an error in this case, the process command simply re-clones the specified data set after issuing this warning.

WARNING: DataSet name[/rectype] will be treated as if its active column was 0 - execute a redefine command to remove its definitions from the client control tables

This message is displayed during a process or clone command when the Client selects the data set and gets an invalid structure number error from the Databridge Engine. This can happen at sites that create new data set structures that replace old ones with the same name. To avoid this problem, run a redefine command followed by a generate command to get the new structure defined. Then, re-clone the data set in question. To avoid re-cloning, you must record the old State Information and reinstate it to get the program to produce exactly the same layout for the tables.

WARNING: DBEnterprise audit files origin changed from AF_origin1 to AF_origin2

The Client displays this message when the audit file origin for Databridge Enterprise Server changes. This message is not displayed if the previous value of the audit file origin is unknown (255).

WARNING: DBEnterprise audit files origin is AF_origin

The Client displays this message when the audit file origin for Enterprise Server changes from unknown (255) to a value different than that specified by the configuration parameter dbe_dflt_origin. For example, the parameter is set to DirectDisk, but the new value is IndirectDisk.

WARNING: Deleting column 'name', which is a key, requires recloning DataSet name[/rectype]

This message, which can occur during a redefine command, indicates that a column that used to be a key is no longer is present. When this happens the Client will want to re-clone the data set, as failure to do so could result in duplicate records. One such example would be the deletion of an external column of type deleted_record.

WARNING: "discard_data_errors" parameter overrides "alpha_error_cutoff" parameter

This message can appear during any Client command, it indicates that configuration file specifies two mutually exclusive configuration parameter settings. The discard_data_errors parameter forces the alpha_error_cutoff parameter to be set to 0, indicating that even if one character is in error, the Client should treat the data as bad and discard the record.

WARNING: DMSII reorganization has occurred; AA values for DataSet name[/rectype] no longer valid - {add the -y option to the process command or set ds_mode to 0 to force a reclone}

This message indicates that a DMSII garbage collection reorganization has invalidated the keys of the specified data set that uses AA values as keys. You must re-clone the affected data set. The Databridge Client sets the ds_mode column of such a data set to 12.

The Client deselects the specified data set and continues the command. The next time you run a process command, the Client will not select data sets whose mode is 12. You can force a re-clone by specifying the -y switch for the next process command. Do not set ds_mode to 2 unless you create a composite key instead of using the column my_aa. See "Changing an Index from AA Values to a Composite Key" in Chapter 4 of the Databridge Client Administrator's Guide.

WARNING: DTOPT_Preserve_Deletes bit erroneously set for table 'name' -- option reset.

This message indicates that the program encountered a table whose dt_options bit DTOPT_Preserve_Deletes (0x80) is set even though there are no user columns that are required to implement deleted record preservation. Make sure that this bit is not set in the DATATABLES control table.

WARNING: DTOPT_PrimaryKey option does not match index type for table 'name'; attempting to recover

This error message can occur during a reorganize command when the Client tries to drop an index. If the dt_options bit for the table is wrong, the Client realizes this and recovers by using the right SQL to drop the index.

WARNING: Duplicate deleted record for table 'name'; use delete sequence number to avoid slowing the program down

This message can occur when you are preserving deleted records using the deleted_record column. Since the current value of time is used as the value in this column, when more than one deletion of the same record is seen by the Client within the same second, a duplicate record is created. The Client inefficiently sleeps for a second waiting for the value of time to change. To avoid this situation, add the delete_seqno column, which eliminates such duplicates.

This situation should not occur, unless you have programs that do updates by doing delete/insert operations rather than actual updates. We therefore recommend that you always add the sequence number column when preserving deleted records.

WARNING: Duplicate record encountered during a two step modify for table 'name' which has unique keys - Program automatically recovers from this error by doing a delete/insert instead (AFN=afn, ABSN=absn, SEQ=seg, INX=inx)- Keys: colname = value, ...

This warning, which can occur during a process or clone command, indicates that the Client was unable to update a record in the specified table during a two-step modify. A two-step modify occurs when a change occurs to the value of the depends item for an item with an OCCURS DEPENDING ON clause. The Client first updates the rows that remain in the OCCURS table and later deletes the rows that are no longer present, or adds rows that were inserted. This warning appears if the update for one of the rows fails because the target row is not in the table. The Client recovers by deleting all of the rows in the OCCURS table for the given key and inserting all of the rows that are present in the after image. This only happens when the OCCURS table is corrupt.

WARNING: Duplicate record encountered for table 'name' which has unique keys - Program automatically recovers from this error by doing an update instead (AFN=afn, ABSN=absn, SEQ=seg, INX=inx) - Keys: colname = value, ...

This message can occur during the fixup phase of a process or clone command if the -v option is enabled. It is unconditionally displayed if this situation occurs during the update phase as this is not expected behavior. The Client attempts to deal with this situation by changing the failed insert into an update instead.

WARNING: Duplicate record encountered for table 'name' which has unique keys - Program automatically recovers from this error by doing a delete/insert instead (AFN=afn, ABSN=absn, SEQ=seg, INX=inx) - Keys: colname = value, ...

This message can occur during when an update finds no rows to update and the subsequent insert get a duplicate message error. As a last ditch effort the Client tries to delete the record and reinsert it. Sometimes the presence of triggers can adversely affect the row count, which is about the only way to explain how this situation could ever occur. If the delete/insert works, the Client continues processing updates, thus avoiding an unnecessary stop.

WARNING: End_Split_Table bit in di_options2 for item name in DataSet name[/rectype] has no matching item with the Split_Table bit set; the bit will be ignored

The bits DIOPT_Split_Table (4) and DIOPT_End_Split_Table (8) in the DMS_ITEMS di_options2 column allow you to move a block of DMS items to a new table and return back to adding items to the original table. The current implementation does not allow consecutive DIOPT_Split_Table bit settings, as we only remember the last point where the table was split. This warning indicates that you have a spurious DIOPT_End_Split_Table bit set due to a bad user script.

WARNING: Error in creating index for FileXtract table 'name' was ignored

Unlike DMSII data sets, FileXtract tables do not require an index for data tracking. The only type of update that is performed is an insert. Under these conditions, the Client does not object to the lack of an index. This message simply documents the fact that there was no index created.

WARNING: Error in creating index for table 'name'

This message indicates that an error occurred when creating an index for the specified table. This can happen if:

You have a very large table and your log space is too small.
You created an invalid composite key

When this error occurs and the DATASETS ds_options bit DSOPT_ClrDuprecs (0x8000) is set to 1, the Client runs the script script.clrduprecs.*name*. If this script runs successfully, the index is re-created. If the bit is not set or the index creation fails after the script runs, the Client sets ds_mode to 11 to indicate that the data set has at least one table that does not have an index. This puts the data set temporarily out of commission until you fix the problem. To create the index for the specified table, issue a runscript command for script.index.*tablename*.

WARNING: Error in dropping DataSource name

An error occurred during a dbutility dropall command. Check the previous error messages (on screen or in log file) for details on what went wrong. If you attempted a dropall command and the scripts for the specified data source could not be found, you probably did not point your current directory to the proper place. If this is the case, change to the proper directory and repeat the dropall command.

This error does not stop the execution of the dropall command. Instead, the Client informs you via this message and then proceeds to the next data source. When the dbutility dropall command is finished with all of the data sources, it leaves the control tables. This allows you to fix the problem (for example, the scripts are in a different directory). You can then rerun the dropall command.

WARNING: Error in initializing table 'name'

The specified table was not dropped and recreated successfully. Check the error messages that appear prior to this one for more details.

WARNING: Error in reading Null Record file "datasource_NullRec.dat"

This message can occur during a process or clone command and indicates that the Client encountered and error while reading the specified file. Check the error messages that precede this message to see why this file could not be read.

WARNING: Error in reading value in BI for depends item 'name' in table 'name', using maximum of nnnn instead

This warning, which can occur during a process or a clone command, indicates that the Client detected a data error while retrieving the value of the depends item from the before-image of the record. A depends item is an item pointed to by an OCCURS DEPENDING ON clause, which is in the form "OCCURS N TIMES DEPENDING ON item_name." The Client also tests the value of the depends item to make sure it does not exceed the maximum specified in the OCCURS DEPENDING ON clause.

WARNING: Error in reading value of depends item 'name' in table 'name', using maximum of nnnn instead

This warning, which can occur during a process or a clone command, indicates that the Client detected a data error while retrieving the value of the depends item from the after-image.

WARNING: Filter for table 'name', which is not an OCCURS table, will be ignored

This message is an internal error that only occurs when there is an OCCURS table filter file dbfilter.cfg present in the config subdirectory for the data source. It indicates the filter references a table that is not an OCCURS table. The most likely cause of this error is that the filter and the control table are not in sync. Try recreating the filter by either running the makefilter utility's import command or run a redefine command with the -R option (Redefine All) to try to remedy this situation. This situation should never occur, as whenever you run a redefine command or you run the Administrative Console's Customize command makefilter is automatically launched. However, you need to pay attention to the cases where the program is unable to compile the filter due to errors in the filter's source file. Look in the makefilter log file to determine why the compile failed.

WARNING: fixed_delay scheduling overrides daily scheduling

See sched_delay_secs under Scheduling Parameters in Appendix C of the Databridge Client Administrator's Guide.

WARNING: Group name cannot be collapsed, as it contains an item with an OCCURS clause

A groups of unsigned NUMBER or ALPHA items can be collapsed into a single item whose length is the same as that of the GROUP. This operation works like a REDEFINE in GenFormat and it provides a simple way of dealing with dates that are represented as a DMSII GROUP. This operation is only allowed for GROUPs that do not contain items with OCCURS clauses. Attempting to collapse such a GROUP results in this WARNING.

WARNING: Group name cannot be collapsed; item name is not an {ALPHA item | unsigned NUMBER} [like the items that precede it]

A groups of unsigned NUMBER or ALPHA items can be collapsed into a single item whose length is the same as that of the GROUP. This operation works like a REDEFINE in GenFormat and it provide a simple way of dealing with dates that are represented as a DMSII GROUP. Attempting to collapse a GROUP whose items do not meet the above restrictions results in this WARNING.

WARNING: Illegal split offset for item 'name' in table 'name' will not be performed

This message is a result of a bad user script that attempt to split an item by specifying a bad offset. You will not see this error when using the Administrative Console's Customize command as it will not allow you to specify an illegal offset.

WARNING: Index column 'name' in table 'name' has NULL attribute, this may cause updates to fail

This message indicates that the index includes a column that allows nulls. If you try to create a Primary Key constraint, it will fail. However, if you create an index, it will appear to work.

WARNING: Index for tables in data set name[/rectype] contains a date that allows nulls; you will need to run a redefine command

This message, which is limited to MISER databases, indicates that the Client encountered an unregistered MISER date column that allows nulls. Running a redefine command will correct this problem.

WARNING: Index 'name' for table 'name' has too many keys -- command terminated

This message, which can occur during a define or generate command, indicates that the Client cannot use the selected DMSII SET as a source for an index, as the number of key would exceed the limit of the corresponding relational database. You need to either force the Client to use AA Values (or RSNs) or create a composite key

WARNING: Index name 'name' already in use by another DataSource, using 'name1'instead

This message, which occurs during a define or redefine command, indicates that an index name that was not unique across data sources was renamed. The new index names are constructed by appending the smallest possible integer (for example, 1, 2, 3,...) to the name to make it unique. If this causes the name to become too long, the last few characters of the index name are changed to digits.

WARNING: Index name 'name' already in use, using 'name1' instead

This message, which occurs during a define or redefine command, indicates that an index name that was not unique was renamed. For example, this message can occur when the index name gets truncated, therefore making it indistinguishable from another index name.

The new index names are constructed by appending the smallest possible integer (for example, 1, 2, 3,...) to the name to make it unique. If this causes the name to become too long, the last few characters of the index name are changed to digits.

WARNING: Insert for filtered secondary table 'name' failed, changing it to a delete/insert (AFN=afn, ABSN=absn, SEG=seg, INX=inx)- Keys: colname = value, ...

This message is the standard error recovery indication from an exception that occurs during the processing of an insert for an OCCURS table that has a filter. It indicates that the data in the table is corrupted, this can occur during the fixup phase, at which time this message is not displayed unless the -v option is enabled.

WARNING: IO error writing to trace file "trace_filename", file closed; errno=number (errortext)

This message can appear during any Client command when the -t option is enabled. It indicates that there was an I/O error writing to the specified trace file. The errortext which is generated by the system should explain why the error occurred.

WARNING: IPC connection to service lost, terminating command

This message, which can occur when using the service, indicates that the Client has lost its IPC connection to the service and is therefore shutting down. This normally indicates that the service (or daemon) has crashed or was stopped.

WARNING: Item 'name'in table 'name' contains an illegal character in data [, record will be discarded - Keys: colname = value...

This message, which is only applicable when using the translation DLL, indicates that the DLL detected an illegal character (such as an EBCDIC character that translates to a value that is reserved for the starting bytes of a DBCS character, which is encountered when not in double byte mode).

WARNING: Item 'name' in table 'name' contains an illegal digit 0xdigit, {number set to NULL value | record will be discarded} - Keys: colname = value,...

This message can appear during a process or clone command. It indicates that the program encountered a value other than 0–9 (excluding the sign digit of a signed numbers).

WARNING: Item 'name' in table 'name' does not contain a valid GUID, value set to NULL

This message, which is limited to the SQL Server Client, when storing an ALPHA(36) item as a uniqueidentifier data type, indicates that the data is not a valid GUID and will therefore be set to NULL to avoid causing a SQL error.

WARNING: Item 'name' in table 'name' has 8-bit characters in data[,{ column set to NULL | record will be discarded} ] - Keys: colname = value, ...

This message can appear during a process or clone command. It indicates that the Client has changed all 8-bit characters to question marks.

WARNING: Item 'name' in table 'name' has control characters in data[; too many errors column set to NULL] - Keys: colname = value, ...

This message can appear during a process or clone command. It indicates that the Client has changed all control characters to question marks.

WARNING: Item 'name' in table 'name' has control characters in data, record will be discarded - Keys: keyname = value, ...

This message can appear during a process or clone command, and it indicates that the Client encountered illegal control characters in the data.

WARNING: Item 'name' in table 'name' split into multiple columns

This message, which occurs during a define or redefine command, can occur if a DMSII ALPHA item is too big for the relational database to handle and the bit DIOPT_Split_Item (4) is set in the di_options column of the corresponding DMS_ITEMS table. When this happens, the item is stored in multiple columns. If the bit is not set, the item is truncated instead.

WARNING: Item 'name' in table 'name' was truncated to ddd characters

This message, which occurs during a define or redefine command, can appear if a DMSII ALPHA item is too big for the relational database to handle and the bit DIOPT_Split_Item (4) is not set in the di_options column of the corresponding DMS_ITEMS table. When this happens, ALPHA items that are too large are truncated.

WARNING: Key_Item 'name' in table 'name' contains an illegal character in data, record will be discarded - Keys: colname = value,...

This message indicates that the translation DLL detected illegal characters (such as an EBCDIC character that translates to a value that is reserved for the starting bytes of a DBCS character.

WARNING: Key_Item 'name' in table 'name' contains an illegal digit 0xdigit, record will be discarded - Keys: colname = value,...

The record is written to the discard file and is otherwise ignored. For more information on discard files, see Special Handling of Key Items in Discard Files in the Databridge Client Administrator's Guide.

WARNING: Key_Item 'name' in table 'name' has 8-bit characters in alpha data, record will be discarded - Keys: colname = value,...

The record is written to the discard file and otherwise ignored. For more information on discard files, see Special Handling of Key Items in Discard Files in the Databridge Client Administrator's Guide.

WARNING: Key_Item 'name' in table 'name' has control characters in data, record will be discarded - Keys: colname = value,...

The record is written to the discard file and otherwise ignored. For more information on discard files, see Special Handling of Key Items in Discard Files.

WARNING: Key_Item 'name' in table 'name' is NULL, item will be treated as blank - Keys: colname = value, ...

This message can appear during a process or clone command when the value of a key item of type ALPHA is NULL. If the bit DSOPT_Keep_Null_Alpha_Keys (128) of the ds_options column of the corresponding DATASETS entry is set, the Client treats the NULL value as blanks instead of discarding the record. This warning is just a reminder that a NULL key was changed to blanks. This action can sometimes lead to duplicate records.

WARNING: Key_Item 'name' in table 'name' is NULL, record will be discarded - Keys: colname = value, ...

This message can appear during a process or clone command when the value of a key item is NULL. The program typically treats a NULL key as a non-fatal error; the record is written to the discard file and otherwise ignored. You are given the option to make the program treat NULL ALPHA keys as blanks instead of NULL. To do this, the bitDSOPT_Keep_Null_Alpha_Keys (128) of the ds_options column of the corresponding DATASETS entry must be set using user scripts.

WARNING: Link 'item_name' values for DataSet name[/rectype] no longer valid

This message can occur during a process or clone command and indicates that the link items for the specified data set are invalid because the target data set’s AA values were invalidated by a DMSII garbage collection or structural reorganization. You must re-clone both data sets.

WARNING: Main thread stuck waiting for updaters to complete after COMMIT for (elapsed time sss, n_active_threads = nn)

This message indicates that the timer thread detected that the main thread is stuck waiting for the updater threads to complete their work, before it can issue a commit. This situation is most likely the result of a stuck query, which could be caused by either a table being locked by a user or one of the updater threads being stuck executing a query.

WARNING: Malformed AF_header DOC record ignored

Databridge Engine and Enterprise Server use this type of DOC record to pass information about an audit file to the Client when they start processing updates from the given audit file. This message indicates that the record that has been sent is malformed. This is an internal error that should never occur. If you see this error, contact Micro Focus Customer Support.

WARNING: Maximum bcp failure threshold exceeded, aborting clone

The 7.0 client keep track of the number of tables that had bcp failure during data extraction, if this exceed the value of the configuration parameter max_bcp_failures the Client aborts the clone to avoid wasting mainframe resources.

WARNING: Maximum discards threshold reached, aborting clone

This message indicates that the Client has exceeded the limit on the maximum number of total discard records that was specified in the configuration file using the first value of the parameter max_discards. This has happened during data extraction and the clone will be aborted.

WARNING: Maximum discards threshold reached, {DBClient | dbutility} will stop at the next quiet point

This message indicates that the Client has exceeded the limit on the maximum number of total discard records that was specified in the configuration file using the first value of the parameter max_discards. This has happened during the change tracking phase and the Client will stop at the next quiet point.

WARNING: Maximum discard threshold reached for table 'name' additional discards will not be archived

This message indicates that the Client has exceeded the limit on the maximum number of discard records for the given table that was specified in the configuration file using the second value of the parameter max_discards. This situation results in the Client ignoring the record without writing to the discard file, as doing so could result in a huge discard file that would slow the Client down considerably, as a result of continuously appending a record to the discard file and closing the file.

WARNING: Miser database requires "param name" to be set to value; parameter set to value

This message indicates that the specified configuration parameter (miser_database=True), which is required for a MISER database, has the wrong value. You must correct the value of the parameter param_name in the configuration by using the value specified in the message. These parameters include automate_virtuals (True), flatten_all_occurs (True), use_nullable_dates (True) and default_date_format (1)

WARNING: More than one nullable date found in index for table 'name', updates will fail if column name is NULL

This message occurs when using a MISER database with the SQL Server Client and you have more than one MISER date being used as a key. The only solution is to use an RSN as the index instead of the SET.

WARNING: Multisource DataSet name[/rectype] must be recloned, run reorganize command: ds_mode set to 34

This message occurs during a redefine command when a multisource data source is reorganized. It indicates that the specified data source must be re-cloned. You may need to wait until other data sources are caught up with the reorg before doing this. However, the reorganize command can determine if the data source can be re-cloned.

WARNING: Multisource DataSet name[/rectype] processing stopped until other sources are reorganized – mode 35

This message, which can occur during a process or clone command involving a multi-sourced data sets, indicates that the data set has a mode of 35. This means that the source is waiting for all other data sources to be reorganized.

WARNING: Multi-threaded updates need at least 2 DMSII buffers per thread to be effective

This message, which only occurs when processing a text-based configuration file, indicates that the number of DMSII buffers must be increased to support multi-threaded updates.

WARNING: Name 'name' is an SQL reserved word, using 'newname' instead

This message can occur during a define or redefine command. It indicates that a table, column, or index name is a SQL reserved word (for example, order or update) and that the specified new name is being used in its place. The newname is the original name with a suffix of _x.

If using the SQL Server Client and the object in question is a table, you can force the Client to use this name by setting the configuration parameter bracket_tabnames to True.

WARNING: No data received from {DBServer | DBEnterprise Server} for number minutes

If the Client waits for TCP/IP input from the Databridge server past a certain threshold, the watchdog timer thread returns this message. The initial threshold is 5 minutes.

WARNING: No DataSources found in client control tables

This message which can occur during an unload command, when a data source name of _all is specified. It indicates that the dbutility program did not find any data sources to unload.

WARNING: No items except keys were active in occurs table 'name', active column set to 0

This message can occur during a generate command. It indicates that the Client disabled cloning of the specified secondary table because it contained nothing but keys.

WARNING: No items were active in table 'name', active column set to 0

This message can occur during a generate command. It indicates that there are no data items to be cloned for the specified table. This message can occur in the following circumstances:

When you set all of the active columns in the DATAITEMS table to 0. Unless you intended for all the active columns to be set to 0, reset the active columns and run the process again.

When you change a table name in the DATATABLES Client control table but fail to make the same change in the DATAITEMS table.

WARNING: No updates received from {DBServer | DBEnterprise Server} for number minutes

If the Client is using DBWait and it uses a non-zero value for the second parameter of max_wait_secs, you end up with frequent data on the line which acts pretty much like a heartbeat. However, this makes the "No data received from {DBServer | DBEnterprise Server} for *number* minutes" message disappear. We added this message so that the watchdog timer can issue warnings about the lack of updates, which could be indicative of a problem with MCP. The initial threshold is 5 minutes. This message is reissued after 15 minutes and then 30 minutes of inactivity, and every 30 minutes thereafter.

WARNING: No value specified for "max_temp_storage" in config file, the default value will be used

(Windows only) This message appears only when you explicitly set max_temp_storage to 0. To correct this error, change the max_temp_storage back to the default setting.

WARNING: None of the commit parameters are set, batch job window disabled

When the batch_job_period parameter is enabled by setting to a time period where the start and end time are different, you must provide to set of commit parameters that the client will use during the two periods. If none of the commit parameters are set, you get this message. When you set this parameter, you will see this warning because the client will ignore the batch_job_period parameter.

WARNING: One or more data sets will be recloned

This message, which can occur during a redefine command or when running the Administrative Console's Customize command, is designed to alert the user that there is a pending re-clone, which might not be desirable.

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

This message can occur during a process or clone command when the check_user_scripts parameter is enabled.

WARNING: Overflow error in translation DLL for Item 'name 'in table 'name', record will be discarded - Keys: colname = value, ...

This message can appear during a process or clone command. It indicates that the character translation DLL called by the Client returned an overflow error status.

WARNING: Overflow error in translation DLL for Key_Item 'name' in table 'name', record will be discarded - Keys: colname = value, ...

This message, which can appear during a process or clone command, indicates that the character translation DLL called by Client returned an overflow error status while translating the data for an item that is a key. This is not a fatal error; the record is written to the discard file and otherwise ignored. See Special Handling of Key Items in Discard Files.

WARNING: Parameter "max_retry_secs" must not exceed the 2'nd value of "max_wait_secs"; parameter set to nn

When you specify a second value for the parameter max_wait_secs, this value is used in the request sent to the Databridge Engine. The value of the parameter max_retry_secs needs to be smaller than this value for this to make sense. If the value of max_retry_secs is greater than the second value of the parameter max_wait_secs the Client forces the value of max_retry_secs to be ½ the value of the second part of max_wait_secs.

WARNING: Parameter use_ctrl_tab_sp requires that aux_stmts be greater than 0 - use_ctrl_tab_sp parameter disabled.

This warning indicates that the parameter aux_stmts is zero; the parameter use_ctrl_tab_sp cannot be set to True if there are no database API stmt structures required to support the host variables. When the parameter use_ctrl_tab_sp is True (default), all of the control tables updates use host variables. We recommend that you do not change the value of the deprecated parameter use_ctrl_tab_sp.

WARNING: Parameter "use_global_stateinfo" requires that "optimize_stateinfo" be enabled - "optimize_stateinfo" parameter enabled.

This message appears during any Client command if you disable the deprecated parameter optimize_stateinfo without disabling the deprecated parameter use_global_stateinfo. For more information, see preserve_deletes under Process and Clone Command Parameters in the Databridge Client Administrator's Guide. For optimal efficiency of the Client, avoid changing the values of deprecated parameters.

WARNING: Parameters "convert_ctrl_char" and "inhibit_ctrl_chars" are mutually exclusive

This message can occur when a text configuration file is being processed. It indicates that you need to set one of the specified parameters to False.

WARNING: Parameters use_decimal_aa and use_binary_aa are mutually exclusive

This message can occur when a text-based configuration file is being processed. It indicates that the specified parameters are mutually exclusive and that you need to set one of them to False.

WARNING: Parent_AA values for DataSet name [/rectype] no longer valid

This message can occur during a process or clone command and indicates that the Parent_AA values for the specified embedded data set are no longer valid because the DMSII database was reorganized. You must re-clone both data sets.

WARNING: Pending DMSII REORG -- client update_level = nnn

This message, which applies to a process command indicates that the Client’s update level is not the same as the DMSII update level, which is shown in the DB_Info lines in the log file at the start of the run. The Client will soon encounter a DMSII reorganization as it processes audit files.

WARNING: Performance statistics cannot be disabled when multi-threaded updates are being used, parameter set to true

When running multi-threaded updates, you must have performance statistics enabled because the Client uses the table statistics to balance the load between threads. Except for show_table_stats, statistics parameters should be left enabled.

WARNING: 'quit' command is only meaningful during process or clone commands

This message indicates that the operator issued a dbutility QUIT command. The Client only honors this command during a process or clone command.

WARNING: 'quit' command will take effect at the start of audit file processing

This message indicates that the operator issued a dbutility QUIT command during data extraction. The QUIT command is not acted on during the data extraction phase; it will be acted on at the start of audit file processing.

WARNING: Received unexpected result: seq_no = hexnumber; expected seq_no = hexnumber

This message indicates that the host sent an unexpected response to the Databridge Client. Typically, this occurs when the previously executed Databridge command had an error. Since this happens often at session startup where the expected sequence number is 1, this message is not printed when the sequence number is 1 unless the -v option is enabled. This message is displayed unconditionally for any other expected sequence number as this is a symptom of a protocol error between the Databridge server and the Client.

The Databridge Client typically recovers from this condition by discarding the unexpected message, which is left over from a previous session.

WARNING: Redefine command found nothing to do

The redefine command is driven by the bit settings of status_bits and active column in the DATASETS Client control table. This message indicates that the command found nothing in the status_bits columns that indicated that something needed to be redefined or remapped and that all the data sets that needed mapping had their active column set to 0. If you want the command to do something, except for the processing of changes caused by DMSII reorganizations, you need to set the bit DS_Needs_Remapping in the status_bits column of the data sets that you want remapped. In the case of data sets that were not previously mapped, setting the active column to 1 prior to running the redefine command is all that is needed. Alternatively, you can add the –R option to force all data sets to be redefined. If you execute the redefine command without doing these things, this message appears to remind you that nothing happened.

WARNING: Reorganize command found nothing to do -- there are no DataSets with mode 31

This message indicates that you did not need to run the reorganize command because no data sets whose mode is 31 were found. It is mainly meant to provide some feedback when the command is executed from the Administrative Console.

WARNING: Session initialization script name failed

This message indicates that the specified script failed. Check the preceding API or SQL error to see why it failed.

WARNING: Set name is not usable as an index as it has too many keys

This warning occurs if you have a DMSII SET that has more keys than the relational database allows in an index. Consider using an RSN. The limit on the number of keys in an index is 16 keys for SQL Server and 32 keys for Oracle.

WARNING: Set name of data set name[/rectype] allows key changes

This warning appears when a data set whose optimum SET has the KEYCHANGEOK attribute is encountered (during a define or redefine command) when using Databridge Engine 6.0 or earlier. It is intended to warn you of the resulting increase in TCP/IP overhead. With the older Engines, the Client requests that all MODIFY records be passed to the Client as MODIFY BI/AI pairs. With the newer Engines, this decision is made by the Engine after comparing the old and new values of the keys in the index. The Client must register the keys it uses with the Engine in order for the Engine to perform this test.

WARNING: Setting n update_threads to 1 will not improve performance, set it to 2 or higher

Using one update thread makes the program work in single-threaded mode, except that all updates are queued to the worker. There is almost no overlap in SQL execution, as the main thread only handles the updates of the DATASETS table. The Client will queue updates to the update worker and use all available DMSII buffers. Using one update thread is not likely to help performance.

WARNING: SQL operation [for table 'name'] appears to be hung (elapsed time eee, incident # nn)

This message is returned by the watchdog timer thread when the Client wait time for a SQL operation to complete reaches the primary threshold specified by the parameter sql_exec_timeout. The message is issued at increasing intervals after this point until it reaches 30 minutes, at which point it repeats every 30 minutes. This can indicate that a badly written database application program has locked the table. If this is case, determine the program and terminate it. This problem can also be caused by issuing a select statement that has no “where” clause for a very large table.

If the table name is known to the Client, it is included in the message. The value eee is expressed in the appropriate units based on its value (for example, 5 minutes or 15 seconds). The value nn is a thread specific counter that is used to make it easy to see if this is a new problem or a repeat warning for an existing hang.

WARNING: Stored procedures required for data set name[/rectype] which has a key that allows nulls; DSOPT_No_StoredProcs option will be ignored

This message, which only applies to MISER databases, indicates that you are attempting to disable the use of stored procedures for a data set that has a key that is a MISER date. This is not possible, as the stored procedures contain logic to handle the update when the key is NULL. If you set the configuration parameter use_stored_procs to False and run a redefine command (with the /R option) you will see several occurrences of this message. The Client will then ask you to run a reorganize command, which will fix things up and reset the above mentioned bit for such data sets; after that you will not see this message again.

WARNING: "-t 1" option ignored as this would create a second copy of the log file

This message indicates that for the Client to process this option, additional bits must be set in the trace mask to differentiate the resulting trace file from the log file.

WARNING: Table 'name' cannot be altered data truncation would occur

This message indicates that the size of a column has decreased as a result of a reorganization or a change in a user script. The relational database will not let you do an alter command that does something like changing a column from a NUMBER(10) to a NUMBER(8).

WARNING: Table 'name' cannot be altered, this type of alter is not supported

This message indicates that it is not possible use an alter command to fix a column whose data type has changed. You may be able to handle this manually by creating a new columns and populating the new column using the old values. The only other alternative is to re-clone.

WARNING: Table 'name' contains a column of type CLOB which requires host variables; active set to 0 for DataSet name[/rectype]

(Oracle only) This message indicates that you're updating a column whose data type requires the use of host variables. This message occurs if the Client encounters a table that contains a column of type CLOB, while aux_stmts is set to 0 or the table has the dt_options bit DTOPT_No_Aux_Stmts (8) set. You'll need to correct this before going any further.

WARNING: Table 'name' contains a column of type CLOB which requires host variables; minimize_col_updates option disabled for DataSet name[/rectype]

(Oracle only) This indicates that the Client is updating a column whose data type requires the use of host variables. The Client will issue this warning if you set the configuration parameter minimize_col_updates to True or the corresponding bit in ds_options of the DATASETS table entry is set for a column of type CLOB. In response, the Client will disable the use of host variables for this table and process the updates for this table if the aforementioned bit is zero.

WARNING: Table 'name' contains more than one nullable key that is a MISER date - updates will fail if the column col_name is null

This message, which is only applicable to MISER databases, indicates that you have more than one MISER date that allows NULLS in the index. The Client only handles one such key. To get past this error, reset the da_options bit DAOPT_Nulls_Allowed (1). However, if the date in question happens to be NULL when you attempt to update the table, the update will fail. Then, the solution is to use an RSN or a composite key as the index.

WARNING: Table name 'name' already in use by another DataSource using 'newname' instead.

This message can occur during a define or redefine command. It indicates that specified table name was already in use by another data source. The new table name is constructed by appending the smallest possible integer (for example, 1, 2, 3,...) to the name to make it unique. If this causes the name to become too long, the last few characters of the table name are changed to digits.

WARNING: Table name 'name' already in use, using 'newname' instead.

This message can occur during a define or redefine command. It indicates that a table name that was not unique was renamed. This is different from tables being renamed when they are the result of a split data set. For example this message can occur when the table name gets truncated, therefore making it indistinguishable from another table name.

The new table names are constructed by appending the smallest possible integer (for example, 1, 2, 3,...) to the name to make it unique. If this causes the name to become too long, the last few characters of the table name are changed to digits.

WARNING: Table 'name' exceeds max record size of dddd bytes; table 'name1' will be used for additional columns

This message applies to the Databridge Client for Microsoft SQL Server, and it can occur during a define or redefine command. It indicates that the specified table was split because the maximum size limit for a relational database record was reached. Keys in the primary table are replicated into the split table; the tables are not linked in any way. See Relational Database Split Tables in the Databridge Client Administrator's Guide.

WARNING: Table 'name' has more than ddd columns; table 'name1' will be used for additional columns

This message can occur during a define or redefine command. It indicates that the specified table had to be split because the maximum column limit (ddd) for the relational database was reached. The maximum number of columns in a table is 1024 for Microsoft SQL Server and 1000 for Oracle. The keys in the primary table are replicated into the split table; the tables are not linked in any way. See Relational Database Split Tables in the Databridge Client Administrator's Guide.

WARNING: Table name has no index the DataSet name[/rectype] cannot be tracked, mode set to 11

This message is returned when a table for a DMSII data source has no index. In the past, these data sets had the ds_mode set to 11 with no indication that this happened. This message rectifies this situation. You need to create a composite key to be able to track changes to this data set.

WARNING: Table name is a split table; this type of reorg is not supported

The Databridge Client issues this message when a split table is reorganized. This type of reorganization is not supported when a column are added or deleted to the split table. You must re-clone the data set.

WARNING: Table name is using a PRIMARY KEY, index column name, which is a MISER date, cannot have the NULL attribute

This message, which is only applicable to Miser database users, indicates an attempt to use a Primary Key constraint as the index for a table that has keys that are MISER date columns and allow nulls. To make the Client use a unique index instead, clear the dt_options bit DTOPT_PrimaryKey (0x800).

WARNING: Tcptest length exceeds maximum value of maxlen, using maxlen instead

This warning indicates that the tcptest length parameter specified on the command line is too large. The value of maxlen (currently 128K) is used instead.

WARNING: The clone of DataSet name[/rectype] will be deferred until the client catches up with all pending DMSII reorgs

This warning, which appears at selection time during a process or clone command, indicates that the Client has not yet caught up with outstanding DMSII reorganizations and the requested clone cannot be performed at this time. The clone will be performed as soon after the Client processes that last outstanding DMSII reorganization.

WARNING: The configured number of stmts (nn) is insufficient for n threads

When using multi-threaded updates, you need a minimum of 20 database API STMTs plus the number of threads. When not using multi-threaded updates, the minimum number of API STMTs required is 20.

WARNING: The DataSource name was recently customized, changes made since the backup unload file was created will be lost - To bypass this check, use the 'u' option for the redefine command

If you mix using the Administrative Console's Customize and Define/Redefine command you are likely to get this warning, because making layout changes using the Customize command and the redefine command are not compatible.

The redefine relies on using user scripts to restore changes, while the Customize command restore these changes from the old copy of the control tables. To allow the re-running of a redefine command after a user script is updated, the command reloads the control tables from the backup copy of the control tables and re-runs the command. If the current copy contained any changes implemented by the Customize, they would be lost under these circumstances.

To avoid this situation, refrain from using the redefine command when using Customize to make layout changes. Ideally you should always use the Customize command because it does everything the redefine command does. And unlike the redefine command, the Customize command does not have problems when it is run multiple times, because it picks up changes from that last copy of the table and only uses the backup copy to compare the old and new layout when you are done customizing.

WARNING: The filtering status of data set name[/rectype] has changed from n to m; ds_mode set to 0 to force it to be recloned

This message indicates that an OCCURS table that was not previously filtered is now filtered (0 -

1) or vice versa. Since this will change the number of records stored in the table, re-cloning is the only option.

WARNING: The "minimize_col_updates" parameter will be set to false, as it is invalid for a MISER database

When the Client loads the control tables, if the miser_database parameter is set to True, the Client disables the minimize_col_updates parameter (if set to True) and issues this warning.

WARNING: The parameter 'name' is deprecated; it will be ignored

The Client issues this message if it finds one of the following deprecated parameters in a text configuration file: auto_reclone, bcp_date_format, bcp_delim, check_key_changes, encode_passwords, and redef_all_active_ds n_bcp_threads. The Oracle Client will also issue this warning if you attempt to use the bcp_delim parameter. Also using the old parameters optimize_col_updates and enable_optimized_col will generate a similar message stating the new name of the parameter in question.

WARNING: This command will drop all Databridge tables, do you really want to do this?- To bypass this check, use the 'u' option for the dropall command

This message appears during a dropall command when you use the command without the - u option. The -u option is required as a safeguard against accidentally dropping the Databridge tables.

WARNING: Too many data errors for DataSet name[/rectype] -- additional errors will not be {displayed | logged}

This message can appear during a process or clone command. It indicates that the count of data errors for the given data set has just crossed the display or log cutoff threshold and that no more data errors will be displayed or logged for this data set. See error_display_limits.

WARNING: "trace 1" command ignored as this would create a second copy of the log file

This message appears when a dbutility console TRACE command specifies a trace mask of 1 or "verbose" is enabled. The Client won't process this option unless additional bits are set in the trace mask, resulting in a trace file that can be differentiated from the log file.

WARNING: Transaction group aborted; number SQL operations rolled back

This message, which is only written to the trace file when the trace file TR_VERBOSE bit is set in the trace mask, occurs when the Client rolls back some updates at the end of the last audit file processed. These updates are picked up when the next audit file is processed.

WARNING: Truncation error in translation DLL for [Key_] Item 'name'> in table 'name' [, record will be discarded] - Keys: colname = value,...

This message can appear during a process or clone command. It indicates that the character translation DLL called by Client returned a truncation error status. This is not a fatal error. However, when the configuration parameter discard_data_errors is set to True or the item is a key, the Client discards the record. If the item is a key, the Client also discards the record.

WARNING: Unable to clear 'changes' column in {DATASETS | DMS_ITEMS} for data source 'name'

This warning can occur when running a redefine command or when using the Client Configurator. It indicates that the Client was unable to clear the changes column for the entries in the specified table. Check the SQL error that precedes this warning to determine why the update failed. This column is used by the Administrative Console's Customize command to highlight the items that have changed.

WARNING: Unexpected held buffer for DataSet name[/rectype]; buffer discarded

This warning indicates that an internal error occurred causing a before image record to not be immediately followed by an after image record. Contact Micro Focus Customer Support if you get this error.

WARNING: Unknown translation error (0xdd) for [Key_]Item 'name' in table 'name'[, record will be discarded] - Keys: colname = value, ...

This message can appear during a process or clone command. It indicates that the character translation DLL called by the Client returned an undefined error status of 0xdd. This message is a catchall for any new error status that may be added to the data translation DLL. This is not a fatal error. However, when the configuration parameter discard_data_errors is set to True or the item is a key, the Client discards the record.

WARNING: Update for filtered secondary table 'name' failed, changing it to a delete/insert (AFN=afn, ABSN=absn, SEG=seg, INX=inx) - Keys: colname = value, ...

This message is the standard error recovery indication from an exception that occurs during the processing of an update for an OCCURS table that has a filter. It indicates that the data in the table is corrupted, this can occur during the fixup phase, at which time this message is not displayed unless the -v option is enabled.

WARNING: Update for table 'name' had no matching row, changing it to a delete/insert (AFN=afn, ABSN=absn, SEG=seg, INX=inx) - Keys: colname = value, ...

This message can appear during a process or clone command. It indicates that the executed update SQL statement for a user table resulted in a row count of zero, indicating that the update did not find any matching rows. Furthermore, the update involved an item with an OCCURS clause, so instead of just turning the update into an insert, the Client first deletes any partial data that may be in the occurs table and inserts the after image of the update.

WARNING: Update for table 'name' had no matching row, changing it to an insert (AFN=afn, ABSN=absn, SEG=seg, INX=inx) - Keys: colname = value,...

This message can appear during a process or clone command. It indicates that the execution of an update SQL statement for a user table resulted in a row count of zero, indicating that the update did not find any matching rows. The Client turns these updates into inserts and tries them again.

WARNING: User index creation script "name" failed

This message indicates that the execution of the index creation user script for the specified table (script.user_index.tablename) failed. See the preceding database API error message to determine the cause of the failure. The most likely reason is that the script is in error.

WARNING: User script directory must reside in the global working directory or the data source's working directory

When security is enabled, all user scripts must reside inside the Client working directory. You will see this warning when the user_script_dir configuration parameter is set to point to a directory that does not meet this restriction.

WARNING: User table cleanup script name failed

This message can occur during a process or clone command and indicates that the specified script failed. Cleanup scripts are used to remove records from special tables that cannot be dropped.

WARNING: Value of item 'name' in table 'name' exceeds maximum allowed, value set to NULL

This message indicates that the value of a DMS item of type REAL (n) or REAL (m,n) is too large for the Client to be able to handle. The Client uses the precision and the scale to create the corresponding relational database column, therefore attempting to use such a value could result in an SQL error.

WARNING: Value mmm for "maximum_columns" too large for {Oracle| SQL Server} Vm,Vn using nnn instead

When the Client determines which version of SQL Server or Oracle it is connected to, it checks the value of the configuration parameter maximum_columns to make sure that this value does not exceed the maximum number of column supported by the database. You will only see this error if you use a very old version of SQL Server or Oracle.

WARNING: Variable Format DataSet name[/rectype] has links -- it will not be tracked

The Databridge Client cannot track changes to variable format data sets that contain links. If the configuration parameter track_vfds_nolinks is set to False, the Client will not track any updates to these data sets. This message is a reminder about the action that the Client is taking.

WARNING: Variable Format DataSet name[/rectype] has links -- link updates will not be tracked

The Databridge Client cannot track changes to variable format data sets that contain links. If the configuration parameter track_vfds_nolinks is set to True, the Client will track non-link updates to these data sets. This message is a reminder about the action that the Client is taking.

WARNING: Virtual DataSet name has no index; all DataSets involved with it will not be selected

This message, which can occur during a process or clone command, indicates that no data sets associated with the given virtual data will be selected, because the virtual data set has no index.

WARNING: Virtual DataSet name will not be selected because its parent structure was not selected

This message can occur during a process or clone command and indicates that the virtual data set will not be selected because the data set from which it was derived was not selected.

WARNING: You are about to overwrite your input configuration file "name"> - To bypass this check, use the 'u' option for the {import_ | export} command

This message indicates that the input and output filenames are the same for an import or export command. If you want to convert a text configuration file named dbridge.cfg to a binary file, you must set the -u option in addition to specifying the input file using the -f option.

WARNING: You are attempting to run a createscripts command for a data source that was not created using the Client Configurator - The control tables need to be upgraded by running "dbscriptfixup" before you can safely do this

This message, which only occurs when you run a createscripts command, indicates that the control tables are not compatible with the Administrative Console's Customize command. You must first run the dbscriptfixup program. This program will fix the control tables and create new set of user scripts that reflect changes to be implemented. The Administrative Console's Customize command uses an additional bit in the various xx_options columns in the control tables and the xx_bmask columns to keep track of table entries that were changed during customization.

WARNING: You are attempting to run a redefine command with the parameter "use_dbconfig" set to true - The control tables need to be upgraded by running "dbscriptfixup" before you can safely do this

This warning is a reminder to run the dbscriptfixup program before using the Administrative Console's Customize command. The dbscriptfixup program fixes the control tables and creates a new set of user scripts from which you can recover a corrupted relational database. It also sets the use_dbconfig parameter in the binary configuration file to True. This parameter is required for the Administrative Console's Customize command to run. (Attempting to edit this or other parameters in the binary configuration file will only corrupt the file.)