Database Connectivity and Generic DB Errors

The following table lists the commonly encountered codes and messages and their workarounds.

Table 1. Database Connectivity and Generic DB Errors related codes and messages
Code Description Action required
Db2 related codes and messages

TCS0006E: Db2-error for '...', Return Code=..., Reason Code=0x..., (Refer to Db2 UDB, Messages & Codes).

An error has occurred when accessing a Db2 system.

This error may happen if the attempt to connect to a Db2 system fails.

The error also occurs when it is not possible to read Active Log records.

 Check the availability of the Db2 and the security definitions.

TCS0008E: DSNJSLR ... error, Return Code=..., Reason Code=0x..., (Refer to Db2 UDB, Messages & Codes).

An error has occurred when accessing a Db2 system.

The error happens when archive log records cannot be processed.

00D10012
No file has been assigned to the process or the file cannot be opened. Check the file specifications.
00D10010
The RBA values are invalid. They do not correspond to the log record range. Correct the RBA values.
00D10050
A BSDS file instead of a log file has been specified. Correct the definitions.
00D10021
A gap has been detected in the archive records. This results in lost log records.
00D10022
A gap has been detected in the archive records. This results in lost log records. The specified End-RBA is less than the next available log record after the gap.
00D10024
An error occurred when reading the log records. The RBA of the previous record is higher than the RBA of the current record.
00D10026
An RBA has been specified that does not exist in the BSDS file. Correct the definition.
 Additional information about the error are contained in the return or reason codes. Refer to manual 'Messages and Codes' for Db2.

TCS0009E: Db2 System not started for Db2-access: ... .

To process the log data records in near realtime requires a connection to the Db2. Db2 must be started and available. This is not the case.

 Start the specified Db2 System or activate the process option 'Wait for an active Db2' in the additional settings 'Realtime specific settings'.

TCS0040E: Start RBA ... is less than start RBA of active log: ... .

A start RBA has been specified that is lower than the first RBA in the active log. The data must be processed from the archive log.

It is possible to automatically determine the start RBA in a process.

Correct the start RBA. Use the Db2 console command '-DIS LOG' to obtain the RBA.

TCS0041E: The DML apply thread ... has no response received from the target database for ... seconds. Please check out for any possible bottlenecks on the target database.

The process is waiting for records to be successfully processed by the target database or storage system so it can proceed. This didn't happen for more than ... seconds.

 The target database or storage system needs to be checked for problems or bottlenecks. If none are found and it just needs more time to react the timeout can be increased by setting the parameter PM_I.ThreadTaskTimeout in the prolog of the process. This setting is done in milli seconds. So PM_I.ThreadTaskTimeout = 300000 would set the timeout to 300 seconds. The maximum value possible is 3600000 for a timeout of 1 hour.

TCS0042E: Input value for numeric field '... is invalid. Input value...'.

Invalid numeric values have been detected in a field of a data record. The processing terminates. This error normally happens when processing a PACKED field.
  • has an invalid sign or
  • contains invalid numeric values.

It is possible to ignore these type of errors during the process processing. This should be considered if the correctness of the input data cannot be influenced. The invalid data is then converted to NULL. To activate this processing type, select option Correction of invalid data for setting 'Extended processing settings', to log the changes use setting 'Information protocol writing', and specify a fully qualified name for the info file. This file will contain information about the invalid data together with the key of the data-record for further reference.

Check the source data for valid values.

TCS0043E: Invalid data in log record. Field name '...', value X'...'.

This error occurs when invalid data is processed for IMS log records.

 Create a process trace (with all dumps included) and forward it to the technical support of your local Rocket Software representative.

TCS0044E: z/OS Return Code. Service called '...', Return Code ... .

This error occurs during the processing of z/OS service 'CSRCESRV' to unpack data and the service returns with an error. The following are the most common return codes.

4
Length of output area too small.
8
A higher version has been used to compress the data than the one used to decompress the data.
16
An attempt has been made to decompress data that is not compressed.
 Create a process trace (with all dumps included) and forward it to the technical support of your local Rocket Software representative.

TCS0045E: The following function is not supported: '...

An attempt has been made to perform a function that is not supported. The required action depends upon the message. The following contains a list of messages that can be influenced by the user.

LRHLL0=0 encountered
During read of Db2 log data a record with invalid length zero was encountered. Please check whether the APAR UK62469 was applied.
No structure cache for bulk transfer operation
There was a setting of 0 (zero) in the structure cache value. This is not allowed for bulk transfer. Adapt the value for 'Cache size' in category 'structures' of the process maintenance.
Batch Compare Record too long
The size of a data record exceeds the maximum size Adapt the value for 'Maximum RECORD/BLOCK size' is setting 'sizes'.
No ADABAS Descriptor for Batch Compare
A Batch Compare should be performed for an ADABAS file but no descriptor has been specified. Specify a unique, ascending descriptor for the file that must not contain NULL values.
ADABAS Descriptor with NULL-Value
A descriptor has been specified for an ADABAS file that contains NULL values. Specify a unique, ascending descriptor for the file that must not contain NULL values.
ADABAS Descriptor too long
An ADABAS descriptor has been specified that exceeds the maximum length of 500. Specify another descriptor.
Non CICS-Log
A file has been specified as a CICS Log. However the file is not a CICS log. Specify the correct file
CICS System Log
An attempt has been made to process a CICS System Log for the CICS Journal processing. Specify the correct file.
Unsupported Version of CICS
A CICS Journal has been specified that has been created by a CICS version that is not supported. Supported are files from CICS TS as of version 1.3 for z/OS and CICS 2.3 and CICS TS 1.1.x for z/VSE.
Non asc. TS: ...
Non ascending timestamps have been found when processing a CICS Journal file. Processing is terminated.
No Start of Task rec. found for Task(...)
A task end has been found in a CICS Journal without a preceding task start.
Input Type not supported
An invalid input type has been specified. Use the process wizard to specify a valid input type.
Input DataSourceType not supported
An invalid input data type has been specified. Use the process wizard to specify a valid input type.
Input Stage invalid
A file in the internal format has been processed that contains an invalid header. Check that the specified source file has been saved into the internal format. If possible select another file.
Input Subsystem not supported
A file in the internal format has been processed that contains an invalid header. Check that the specified source file has been saved into the internal format. If possible select another file.
Db2 RBA gap from restart RBA(...) to logical RBA(...)
A gap has been detected when processing Db2 RBA's. Processing terminates because data can be lost.
Restartable sender is pool process, but receiver process is not LUW managed
A sending process has option 'Restart after connection loss' active. A processing is only possible when the receiving process is able to write restart information. This requires an active LUW Manager. Activate the LUW Manager in the receiving process.
Db2 RBA gap from restart RBA(...) to current RBA(...)
A gap has been detected when processing Db2 RBA's. Processing terminates because data can be lost.
UPDATE Logrec for Non DATA CAPTURE Table DbSpaceNo(...) TableId(...)
A Db2 table without the DATACAPTURE attribute has been selected for processing. Changes to this table cannot be processed. Specify the DATACAPTURE attribute for this table.
POOL Output for external process
An external process has been started with data input type of 'CDC_Pool'. The process must be started under the control of a Agent.
Non-Query type SQL Statement
A statement has been specified for a BULK transfer that did not create columns. Correct the statement. Only SELECT statements can be used as a data source.
Too many fields in SQL Statement: Number of fields (...), maximum supported (255)
A SQL statement has been specified for a BULK transfer that contains more than 255 fields. Change the statement to contain less than 255 fields.
Too many IDMS areas
The maximum number of IDMS areas has been exceeded. A maximum of 100 areas can be processed.
IMS: No corresponding GHx call for Command...
During the processing of a pool DELE or REPL commands with no preceding 'Get Hold' have been found. Create an exit trace and try to reproduce the situation.
More than ... Parent-Segments defined in...
Too many parent segments have been defined. The maximum depth that can be processed is 256.
Db2 Logrecs to Stage 2+ without PM_I.Db2xxx_SELECTION
A process is attempting to perform the transformation of Db2 log records to stage 2 or stage 3 however no selection of tables has been specified. Use the process wizard and specify Db2 tables for selection.
Db2 Logrecs without Agent-Link
A process has been started that must connect to a Agent. Either start the process under the control of a Agent or use parameter Agent= for an external process.
ScheduleProcess but no Agent
A process should start another process when an event occurs or when a file is closed. The process however does not run under the control of a Agent. Either start the process under the control of a Agent or use parameter Agent= for an external process.
DATACOM BatchCompare without key name
A process must perform a Batch Compare for a DATACOM table. The process is missing the mandatory key. Specify an ascending key that must not contain NULL values.
MS SQL Server loader and output CCSID 1208
A process has been started that creates a file for the SQL-Server Loader. Output code page 1208 (UTF-8) has been specified. The loader of the MS-SQL Server does not support characters in a representation of multi byte code pages. Change the output code page to 1200 (UNICODE little endian) or specify a local code page.
Uneven number of characters in MS SQL loader ROW/LINE delimiter string
An odd number of characters has been specified as delimiters for the SQL Loader. This is not valid because the first half of the character string is used as a field- and the second half is used as a row delimiter. Specify an even number of characters as delimiters.
Too many sub tables
The number of nested tables has been exceeded. Up to 50 nested tables can be processed.
Primary key too long
The maximum length of the key value has been exceeded. Only keys up to a length of 500 can be processed.
Too many key fields
The maximum number of key columns has been exceeded. Only tables with up to 50 key fields can be processed.
Too many defined DATACOM elements
The maximum number of DATACOM elements have been exceeded. A maximum of 100 elements can be processed.
Nested record types
Multiple nested record types have been detected. This processing is not supported. Change the structure file so that record types are not nested,
Nested REDEFINE
Nested redefined fields have been detected. This processing is not supported. Change the structure file so that redefined fields are not nested.
Isolated REDEFINE=
During the processing of a structure file key word REDEFINE= (indicates the end of redefined fields) has been detected but no start of the redefined fields was available. Correct the structure definition
Decompression of Db2 non-Data Capture Table(...)
A Db2 table without the DATACAPTURE attribute has been selected for processing. Changes applied to this table cannot be processed. Specify the DATACAPTURE attribute for this table.
IDMS_KEY_CONNECT_NAME not defined
To resolve a OWNER-MEMBER relation and to determine the OWNER DBKEY a connection type must be specified (ODBC, DRDA, ORACLE) to perform an access to the relational OWNER table. Specify the connection type.
IDMS_KEY_CONNECT_TYPE not valid
To resolve a OWNER-MEMBER relation and to determine the OWNER DBKEY a connection type must be specified (ODBC, DRDA, ORACLE) to perform an access to the relational OWNER table. Specify the connection type.
Field count mismatch for SQL Bulk in CDS(...)
The CDS reference in exit CDC_ExitDBControl does not have the same number of fields as the SELECT statement. Either recreate the structure file or correct the SELECT statement to match the structure file.
Field type mismatch for SQL Bulk in Field(...)
The structure file referenced in exit CDC_ExitDBControl has a different data type for the field as the SELECT statement. Either recreate the structure file or correct the SELECT statement to match the structure file.
Field length mismatch for SQL Bulk in Field(...)
The structure file referenced in exit CDC_ExitDBControl has a different data type for the field as the SELECT statement. Either recreate the structure file or correct the SELECT statement to match the structure file.
 For all other messages create a process trace (all dumps included) and forward it to your local support.

TCS0054E: DRDA error: ...

An error occurred when accessing a Db2 data source. The message is issued for any Db2 error.

The error has been returned by Db2 and is related to the database. If the message contains a negative SQL code or a SQL state, refer to the manual 'Db2 UDB Messages and Codes'. The following list contains the most common error codes:

-104
The statement contains a syntax error. Correct the statement.
-204
The table used in the query does not exist. Either create the table or correct the query.
-551
This error code indicates a permission problem. The user does not have the correct permissions. Either grant the permissions to the user or select another user.
-560/-561
Incorrect username and/or password. Use the correct signon information.
-803
An attempt has been made to insert a record that validates constraints. This error happens when a BULK transfer is performed but the target table is not empty. Delete the table or check the keys.
-805
Plan or package not found. Perform a BIND.
 DRDA Errors are IBM Db2 return codes and reason codes, not internal errors, and may not be directly related to RDRS.

TCS0060E: Column '...' in 'Input_Source_Order_by' is not part of the result set.

A query has been executed for an ODBC, DRDA or Oracle OCI data source. The input field 'List of comma separated field names that build the key' contains a column that is not part of the query.

 Correct the query or the column name.

TCS0061E: Column '... in 'Input_Source_Order_by' not defined as 'NOT NULL'.

A query has been executed for an ODBC, DRDA or Oracle OCI data source. Input field 'List of comma separated field names that build the key' contains a column that can contain null VALUES:

 Set the column in the source database to 'NOT NULL'. It is not sufficient that the column does not contain NULL values.

TCS0104E: Db2 z/VSE Logfile(...): The log block number (...) is not by 1 higher than the last number processed (...).

Processing of a Db2 log file. The logical block number of the next block is not exactly 1 higher than the block number of the currently processed block.

This error can happen if log files are not processed in the correct sequence.

 Make sure that archive logs are consistently processed in ascending sequence.

TCS0106E: Db2_Error: ...

An error occurred when accessing a Db2 data source. This message is issued for every Db2 error.

The error has been returned by the Db2 driver and is related to the database. If the message text contains a negative SQL Code or a SQL State refer to manual 'Db2 UDB Messages and Codes'. The following list contains the most common codes:

-104
The statement contains a syntax error. Correct the statement.
-204
The table referred to in the query does not exist. Either create the table or modify the query
-551
Authorization problem. The user who is signed on does not have the necessary permissions. Grant the user or use another user that has the correct permissions.
-560/-561
The user name and/or the password is incorrect. Use the correct sign on information.
-803
An attempt has been made to insert a data row that violated a unique constraint. This error may happen when rows already exist in a table prior to a BULK-Transfer. Delete the table or check the key values.
-805
The plan or package could not be found. Bind the required components.
 Db2 Errors are not internal errors, and may not be directly related to RDRS.

TCS0109E: Db2 Before or After Images for table '...' with no active 'DATACAPTURE' attribute.

A Db2 table has been selected for processing, however this table does not have the DATACAPTURE attribute. Changes applied to this table cannot be processed.

 Assign the DATACAPTURE attribute to this table.

TCS0118E: The processed length ...of the log image does not fit the length ... of the log image. System information ...

This error may occur when Db2 log files for z/VSE (SQL/DS) are processed. The field length of fields in the log file is not identical to the defined field lengths in the structure file.

As an example, this error can happen when fields are deleted in a structure file and these field cannot have NULL values. The error also may happen if the layout of the table has changed but these changes are not reflected in the structure file.

 Reimport the structure file.

TCS0119E: Db2 z/VSE Logfile(...): The file does not contain a 'LOGCID'-Header.

The log file that is processed does not have a valid start record. The reason for the error can be:
  • a file with a wrong format has been specified,
  • a file has not been transferred in a binary format.
 Check the specified file. If the file has been transferred from the mainframe to the workstation a BINARY transfer with no conversion must be performed.

TCS0140E: Db2 UDB error: ...

An error occurred when accessing a Db2 UDB. This message will be issued for every Db2 UDB error.

The error has been returned by Db2 UDB and is related to the database. If the message text contains a negative SQL Code or a SQL State refer to manual 'Db2 UDB Messages and Codes'. The following list contains the most common codes:

-104
The statement contains a syntax error. Correct the syntax.
-204
The table referred to in the query does not exist. Create the table or correct the query.
-551
The error code indicates a security problem. The signed on user does not have sufficient permissions. Grant the permissions to the user or select another user.
-560/-561
Username and/or password is incorrect. Use the correct sign on information.
-803
An attempt has been made to insert a data row that violated a unique constraint. This error may happen when rows already exist in a table prior to a BULK-Transfer. Delete the table or check the keys.
-805
Plan or package could not be found. Bind the plan.
 Db2 Errors are IBM Db2 return codes and reason codes, not internal errors, and may not be directly related to RDRS.

TCS0154E: Db2 z/OS Alert, an unexpected logrec variation '..' has been detected.

An unexpected variation has been encountered when processing Db2 z/OS log records. Currently this variation cannot be processed. The following is recommended:
  • Secure the relevant documentation (Traces, Db2 logfile, structure files or backup of metadata repository). Send the documentation to your local software support.
  • Specify PM_I.PROCESS_VARIATION=1 in the prolog section of your processing process.
 PM_I.PROCESS_VARIATION=1 in the process prolog suppresses the message and an attempt is made to process unknown variations. The purpose of the switch is to continue the replication process.

TCS0164E: Db2 z/VSE exit log reader: Processing must start with a Db2 warm or cold start.

A replication has been implemented for a Db2 Server for z/VSE. During the start of the replication the data pool is processed. The first record in the data pool was not a Db2 start record.

A Db2 Server for z/VSE replication can only be successfully restarted when the first pool record represents a Db2 start.

 Perform the following steps to resolve the problem:
  • Stop the Db2 Server for z/VSE
  • New start of the partition
  • Definition of a restart file for the pool process (i.e. SAM ESDS, VB, record length 32000)
  • Maintenance of the pool process, add the restart file as input and output
  • Start the collector, start the data pool
  • Start the Db2 Server

Because of the presence of restart files the pool process can now be restarted as often as required. It is no longer necessary to record the start of Db2 as the first record in the data pool.

TCS0270E: No information from ADABAS nucleus with Id ... since .... Please check the PLOG reader.

The specified nucleus in a group of Adabas nuclei has not returned the status since the mentioned time. Newer transactions from other nuclei are ready for processing, but they cannot be processed due to the dependency between the nuclei. Therefore the replication has to wait.

 The status of the PLOG reader of the specified Adabas nucleus should be checked. The timeout that triggers this message can be set (in seconds) with the parameter PM_I.ADABAS_NUCLEUS_CHECK.

TCS0411W: Db2 zLOAD Info: ...

The Db2 zLOAD utility has returned the above information for a successful load.

 Loading of the data was successful. No further action required.

TCS0412E The specified error occurred while loading data with the Db2 zLOAD utility.

 Loading the data was not successful. The error message names the problem. Take action as per the error message.

TCS0470E: PostgreSQL Logreader error: …

The error indicated in the message occurred while trying to read data from PostgreSQL logs.

 Please make sure that the process definition is correct and restart the task. If the behavior persists, contact the Rocket Software technical support.

TCS1002I: Db2: ... .

This message is a placeholder for all general messages related to a Db2 access. The required action depends upon the actual message.

 The errors are IBM Db2 errors, not internal errors, and may not be directly related to RDRS.

TCS1003I: Start RBA ... is higher than the highest RBA used by Db2.

A start RBA has been specified to read a Db2 log. However this RBA has not yet been reached in the system.

 Specify a valid RBA that already exists. Use the console command '-DIS LOG' to obtain the correct RBA.

TCS1004I: Db2 VM z/VSE: Waiting for Warmstart, BlockNr(...).

Option 'Wait for an active Db2' has been specified for the active log processing. The Db2 system has been shut down. This message indicates the waiting status for Db2 to come up again.

 No action required.

TCS1005I: Db2 VM z/VSE: WarmStart, BlockNr(...) at ...

Option 'Wait for an active Db2' has been specified for the Db2 active log processing. The Db2 system has been restarted. This message confirms the warm start of Db2.

 No action required.

TCS1006I: Db2 VM z/VSE: Shutdown, BlockNr(...) at ... .

The Db2 system has been shut down. This message confirms the termination of the Db2 system.

 No action required.
Oracle related codes and messages

TCS0087E: Error during ORACLE-access, ...

An error occurred when accessing an ORACLE data source. This message is used for every ORACLE error.

The error has been issued by the Oracle driver and relates to the database. The error messages can be found in manual 'Database Error Messages'. The following list contains the most common error codes:

ORA-00900
Invalid SQL statement. Correct the SQL statement.
ORA-00942
Table or View not found. Create the table or correct the query.
ORA-01031
Insufficient permissions. Grant the required permissions to the user or choose another username.
ORA-01017
Invalid username/Invalid password. Use the correct sign on information.
ORA-00001
Unique constraint (xxx) violated. Make sure the table is empty or correct the key.
ORA-12154
TNS:could not resolve service name. Check that the specified NetService-Name exists in file TNSNAMES.ORA.
ORA-12541
TNS: No listener. The listener on the target system cannot be reached or must be started.
 ORACLE Errors are not internal errors, and may not be directly related to RDRS.

TCS0088E: ORACLE DB Version ... is not supported.

An attempt has been made to connect to an ORACLE database of version 8 or to establish a connection to ORACLE using libraries that relate to version 8 or an earlier version. This is not supported. At least version 9i of Oracle is required.

 Use a current Oracle version.

TCS0089E: ORACLE OCI Version ... is less than DB Version ... .

An attempt has been made to connect to an Oracle database using libraries of a different version. This is not supported. However it is possible to use a version 10g client to access an Oracle database of version 11.

 Use the library version that matches the database.

TCS0141E: ORACLE: Processing (...) of OBJ ... without 'Minimum Supplemental Logging' not possible. ...

The processing of an ORACLE object is not possible without 'Minimum Supplemental Logging'.

 To activate the feature use command 'ALTER DATABASE ADD SUPPLEMENTAL LOG DATA' and repeat the attempt.

TCS0480E: OCILIB …

The error indicated in the message occurred while accessing an Oracle database using the OCILIB library.

 Consult the OCILIB documentation for more details on the error.
ODBC/JDBC/SQL related codes and messages

TCS0049E: ODBC error: ... An error has occurred when accessing an ODBC data source. This message applies to all ODBC errors. No specific explanation is available. The error was caused by the ODBC for a certain database and is related to this database. The message contains the original error message of the ODBC driver. The required action depends upon the message

An error has occurred when accessing an ODBC data source. This message applies to all ODBC errors. No specific explanation is available.

The error was caused by the ODBC for a certain database and is related to this database.

 The message contains the original error message of the ODBC driver. The required action depends upon the message.

TCS0200E SQL error for lookup processing: ...

An error occurred during the processing of a Lookup function. The error is part of the message and has been issued by the database management system that was the target for the Lookup function.

 The required action depends upon the actual error message.

TCS0241E: IBM Db2 client error.

An error occurred when accessing the IBM Db2 client.

 The action depends on the message returned.

TCS0263E: JDBC error: …

The error indicated in the message occurred during the JDBC processing.

 Consult the JDBC documentation for a description of the error.
Other databases related codes and messages

TCS0255E: MariaDB error: …

The error indicated in the message occurred during the MariaDB processing.

 Consult the MariaDB documentation for a description of the error.

TCS0256E: PostgreSQL libpq …

The error indicated in the message occurred during the PostgreSQL processing.

 Consult the PostgreSQL documentation for a description of the error.

TCS0257E: Teradata CLIv2: …

The error indicated in the message occurred during the Teradata processing.

 Consult the Teradata documentation for a description of the error.

TCS0258E: MySQL error: …

The error indicated in the message occurred during the MySQL processing.

 Consult the MySQL documentation for a description of the error.

TCS0265E: Cloud Spanner error: …

The error indicated in the message occurred during the Cloud Spanner processing.

 Consult the Cloud Spanner documentation for a description of the error.

TCS0266E: BigQuery error: …

The error indicated in the message occurred during the BigQuery processing.

 Consult the BigQuery documentation for a description of the error.

TCS0271E: MSSQL error '...'

The error referred to in the message occurred during an access to MS SQL.

 Refer to the corresponding documentation for MS SQL.

TCS0291E: Snowflake-Error …

During processing Snowflake operations an error occurred, more information, if available, is in the trace-log.

 Restart the task. If the problem happens again, please contact Rocket Software Support.

TCS0294E: Spark-Iceberg-Error …

During processing Spark-Iceberg operations an error occurred, more information, if available, is in the trace-log.

 Restart the task. If the problem happens again, please contact Rocket Software Support.