Replication Extract LEX messages

LEX0001 Invalid parameters passed to Sybase Log Extract.

Invalid parameters passed to the Sybase Log Extract.

This is a Sybase Log Extract initialization error. The text of this message can vary. (See “What you need to know” for information.)

Contact Sybase Technical Support for assistance.

LEX0002 Unable to load initialization module: module.

Sybase Log Extract is unable to load one or more initialization routines into memory.

See the job log for additional system error messages that describe the exact cause of the error.

LEX0003 Unable to obtain virtual storage in module: module.

The named module is unable to acquire necessary virtual storage.

Increase the region size and restart the Replication Agent started task. If the error persists, set the Replication Agent max_messages configuration parameter to a lower value to reduce the amount of storage dedicated to the Log Transfer Manager's LTL queue. If the error persists, call Technical Support.

LEX0004 LOAD Failed for module.

Sybase Log Extract is unable to link to or load the named module using LOAD. Sybase Log Extract uses LOAD program from the library specified in the STEPLIB JCL statement.

Verify that the STEPLIB contains the correct load library names.

See the Replication Agent for DB2 Installation Guide for MVS for more information.

If the STEPLIB contains the correct library names, see the job log for system error messages that describe the exact cause of the error. Also see the job log for additional system error messages that may describe the exact cause of the error.

LEX0005 DB2 SSID subsystem_id is not defined in the Sybase configuration file.

Sybase Log Extract cannot connect to the named DB2 subsystem because the subsystem is not defined with the Log_Identifier configuration parameter.

This is a DB2 connection error. The text of this message can vary. (See “What you need to know” for information.)

The configuration file must contain an entry for the subsystem specified by subsystem_id in the message.

To add an SSID entry to configuration file see the Replication Agent for DB2 Installation Guide for MVS.

LEX0006 The Sybase Log Extract requires APF.

The Sybase Log Extract modules must execute in an authorized library.

See Chapter 5, “Installing Replication Agent,” in the Replication Agent for DB2 Installation Guide for MVS, for information about APF authorization.

LEX0007 The Sybase LTMEXT Log Extract is exiting successfully.

The Sybase Log Extract has shut down normally.

No user action is necessary.

LEX0008 DB2 subsystem subsystem_id is not operational.

Sybase Log Extract cannot connect to the named DB2 subsystem using CONNECT because the subsystem is not running.

Start the DB2 subsystem and then restart the Replication Agent started task.

LEX0009 Plan name was not found in this DB2 subsystem.

Sybase Log Extract is unable to open a thread to DB2 using OPEN because the named plan is not bound on the DB2 subsystem. Sybase Log Extract retrieves its plan name from the DB2Plan configuration parameter.

Verify that the correct plan name is specified in the DB2Plan parameter. To specify the DB2Plan parameter, see the Replication Agent for DB2 Installation Guide for MVS.

If the correct plan is specified, verify that the plan is bound on this DB2 subsystem. See the section about binding the SYBASE plan in the Replication Agent for DB2 Installation Guide for MVS for more information.

LEX0010 User user is not authorized to execute plan: plan.

Sybase Log Extract is unable to open a thread to DB2 using OPEN because the authorization ID associated with the Replication Agent started task does not have EXECUTE authority on the named plan.

Grant the user ID EXECUTE authority on the named plan.

LEX0011 Release level mismatch between DB2 and call attachment code.

Sybase Log Extract is unable to connect to DB2 using CONNECT because the Call Attachment Facility is not at the same release level as the DB2 subsystem. Sybase Log Extract used LOAD to load the Call Attach Facility from the library specified in the STEPLIBS JCL statement.

Verify that the STEPLIB or JOBLIB statement contains the correct DB2 load library names. See the Replication Agent for DB2 Installation Guide for MVS for more information.

LEX0012 DB2 connection failure - reason code = reason_code.

Sybase Log Extract lost its connection to DB2, which may be the result of a DB2 failure. The reason code is a DB2 reason code.

See the IBM DB2 Messages and Codes manual for a detailed explanation of this error code.

LEX0013 Missing log data detected, log processing terminated.

Sybase Log Extract terminated because it detected a gap in the DB2 log.

If you cannot resolve the problem, contact Sybase Technical Support.

LEX0014 SQL error detected in module module.

Sybase Log Extract encountered a SQL error. The SQLCODE that was returned and a description of the error follows this message.

See the IBM DB2 Messages and Codes manual for additional information regarding the SQLCODE and any action you should take to correct the problem.

LEX0015 User lacks read authority on active log dataset. Return code = return_code, reason code = reason_code.

The user ID associated with the Replication Agent started task must have READ authority on the DB2 active log data sets. The return and reason codes shown are source address field (SAF) error codes.

Use your installation security package (such as RACF) to grant READ access over your DB2 active log data sets to the user ID associated with the Replication Agent started task.

LEX0016 Replication stopped for table table_namelog

LRSN: lrsn

member: member

URID: urid

return code=return_code

Sybase Log Extract encountered an error while processing a DB2 log record that describes a change to the identified table. Replication of this table stops. The log LRSN indicates the LRSN of the log record that caused the error.

Possible return codes and their meanings include the following:

4--The table is not defined on this DB2 subsystem. The log LRSN, URID, and member have no meaning for this error. The name of the table as specified in the LTMOBJECTS table is probably incorrect.

8--Sybase Log Extract is unable to expand DB2 compressed log data.

12--The DATA CAPTURE CHANGES clause is not activated for this table.

16--An error is encountered while column data is being converted from its internal DB2 format.

Do one of the following, depending on the return code you received:

4--Use LTMCSET (the Replication Agent interface panels) to delete the invalid row from the LTMOBJECTS table and to insert a new row with the correct table creator and name (see Chapter 4, “Managing Replication Agent”). Restart the Replication Agent started task.

8--Rematerialize the replicated tables before replication of the affected table can be restarted.

12--Rematerialize the replicated tables before restarting replication of the affected table.

16--Contact Sybase Technical Support.

After you correct the error or re-materialize the replicated table in error, reset the ERROR_CODE column of the LTMOBJECTS table to 0 to restart replication of the affected table.

LEX0017 Log sequence error detected at RBA rba. Recovery processing in progress.

A log data sequence error is detected while the DB2 log is read. A gap exists in the DB2 log. Some data is missing from the first copy of the DB2 log. Sybase Log Extract terminates.

Each Control Interval (CI) of the DB2 log contains control information, which includes the RBA of the CI. Sybase Log Extract uses this control information to verify that log records are being processed in the correct order. The log CI returned by a READ request contained an unexpected log RBA. This message does not indicate that an error occurred. It issues under any of the following conditions:

The ARCHIVE LOG command issues, which results in the truncation of the log data set that Sybase Log Extract is processing. Sybase Log Extract recovers by switching to the next active log data set.

DB2 overwrites the active log that Sybase Log Extract is processing. Sybase Log Extract repositions itself within the appropriate archive log data set and continues processing.

No user action is necessary.

LEX0018 subsystem_id. invalid Poll_Interval, format must be HH.MM.SS.TH.

An invalid value is specified on the Poll_Interval configuration parameter. Sybase Log Extract terminates.

Edit the configuration file. See the section about editing the file in the Replication Agent for DB2 Installation Guide for MVS for more information.

LEX0019 subsystem_id. invalid Poll_Interval value must be between 00 and 60.

An invalid value is specified for the minutes or seconds portion of the Poll_Interval configuration, which must be a number between 00 and 60. Sybase Log Extract terminates.

This is a configuration error. The text of this message can vary. (See “What you need to know” for information.)

Edit the configuration file. See the section about editing the file in the Replication Agent for DB2 Installation Guide for MVS for more information.

LEX0020 subsystem_id. CI_Max must be numeric.

An invalid value is specified with the CI_Max configuration parameter. The CI_Max value must be a number from 0 through 999. Sybase Log Extract terminates.

This is a configuration file error. The text of this message can vary. (See “What you need to know” for information.)

Edit the configuration file. See the section about editing the configuration file in "Configuring Sybase Log Extract" in the Replication Agent for DB2 Installation Guide for MVS for more information.

LEX0021 subsystem_id. GenID must be an integer from 0 to 65535.

An invalid value was specified for the GenID configuration parameter. The GenID value must be a number from 0 to 65535. Sybase Log Extract terminates.

This is configuration file error. The text of this message can vary. (See “What you need to know” for information.)

See the Replication Agent for DB2 Installation Guide for MVS for more information.

LEX0022 subsystem_id. SetTruncPoint must be an integer from 0 to 99999.

An invalid value is specified for the SetTruncPoint configuration parameter. The SetTruncPoint value must be a number from 0 to 99999. Sybase Log Extract terminates.

This is a configuration file error. The text of this message can vary. (See “What you need to know” for information.)

See the Replication Agent for DB2 Installation Guide for MVS for more information.

LEX0023 DB2 log extract initialization in progress.

Sybase Log Extract is attached and began initialization processing. Message LEX0040 issues when initialization completes and Sybase Log Extract begins extracting data from the DB2 logs.

No user action is necessary.

LEX0024 connection established to DB2 subsystem subsystem.

Sybase Log Extract successfully connected to the named DB2 subsystem.

No user action is necessary.

LEX0025 Log processing to begin at log RBA rba.

Sybase Log Extract begins scanning the log for changes to those tables marked for replication at the indicated log RBA or position within the DB2 log.

No user action is necessary.

LEX0026 Sybase Log Extract terminating with return code return_code.

The Sybase Log Extract subtask is terminating. If the return code shown has a non-zero value, then Sybase Log Extract terminates due to errors. Additional messages describing the cause of the error precede this message. Return code 0 indicates that Sybase Log Extract is terminating normally at the request of the operator or Replication Agent.

No user action is necessary unless you receive a non-zero return code. If you do, see the additional messages.

LEX0027 Sybase Log Extract unable to retrieve DB2 high written RBA.

Sybase Log Extract is unable to determine the end of the current active log. This information is needed to ensure that Sybase Log Extract does not read past the end of the current active log data set.

If you cannot resolve the problem, contact Sybase Technical Support.

LEX0028 Definition of table table not found.

The named table is not defined on this DB2 subsystem. The name of the table specified in the LTMOBJECTS table is probably incorrect. If you are running Sybase Log Extract with the Replication_LogExtractError=TERM option, Sybase Log Extract terminates.

Delete the invalid row from the LTMOBJECTS table and to insert a new row with the correct table creator and name (see Chapter 4, “Managing Replication Agent”). Restart the Replication Agent started task.

LEX0029 Unsupported release of DB2, Sybase Log Extract terminating.

Sybase Log Extract connected to a DB2 subsystem version 5.x or earlier, which is not supported. Sybase Log Extract supports only DB2 version 6.1 or later. Sybase Log Extract terminates.

No user action is necessary.

LEX0030 Log record sequence error detected.

URID: urid

LOGRBA: rba

LRSN: lrsn

member: member

Sybase Log Extract encountered a log record that is out of sequence.

If you cannot resolve the problem, contact Sybase Technical Support.

LEX0031 Capture data changes not active, unable to format log record.

Table table

RBA: rba log

LRSN: lrsn

member: member

The named table does not have the DB2 DATA CAPTURE CHANGES attribute activated. Sybase Log Extract cannot replicate changes made to a DB2 table without DATA CAPTURE CHANGES.

Do the following:

Use the DB2 ALTER TABLE statement to turn on the DATA CAPTURE CHANGES attribute. For more information about ALTER TABLE, see the IBM DB2 SQL Reference.

Rematerialize the affected replicated tables.

Update the LTMOBJECTS row that describes the named table. You must reset the ERROR_CODE column of the LTMOBJECTS table to 0.

Restart replication of the affected table.

LEX0032 Error attempting to expand compressed data at RBA rba

Sybase Log Extract is unable to expand DB2 compressed data contained in the indicated log record. This error occurs if Sybase Log Extract is unable to locate a usable DB2 expansion dictionary.

Rematerialize the affected replicated tables. If you cannot resolve the problem, contact Sybase Technical Support.

LEX0033 The definition of the LTMOBJECTS table is invalid.

Sybase Log Extract is unable to interpret a log record that describes a change to the LTMOBJECTS table, which indicates that the table is not defined correctly. The LTMOBJECTS table must be created using the data description language (DDL) shipped with Replication Agent. Do not edit the shipped DDL to rearrange the physical order of the columns or add or delete columns.

Using the DROP and CREATE commands, drop and re-create the LTMOBJECTS table with the correct definition before you resume replication.

LEX0034 Replication activated for table table.

Log RBA: rba log

time date time

Log LRSN: lrsn

member: member

Replication of the named table begins. Replication is dynamically activated for a table in one of two ways while Sybase Log Extract runs:

By inserting a new row into the LTMOBJECTS table using INSERT.

By resetting the ERROR_CODE column of an existing row in the LTMOBJECTS table to 0.

No user action is necessary.

LEX0035 Unable to start replication for table. The specified table does not exist.

The named table is not defined on this DB2 subsystem, which means the name of the table specified in the LTMOBJECTS table is probably incorrect. If you run Sybase Log Extract with the Replication_Error=TERM option, Sybase Log Extract terminates.

Delete the invalid row from the LTMOBJECTS table and insert a new row with the correct table creator and name (see “Managing Replication Agent”). Restart the Replication Agent started task.

LEX0036 Replication stopped for table table.

Log RBA: rba log

time date time log LRSN: member: member

Replication of the named table terminated because this table’s entry is deleted from the LTMOBJECTS table with DELETE. This message does not indicate an error condition.

No user action is necessary.

LEX0037 Qualify status for table table has been changed to qualifier_name.

Log RBA: rba log time date timelog LRSN: member: member

The qualify status is modified because Sybase Log Extract encountered a log record describing a change to the QUALIFY column of this table's LTMOBJECTS entry.

No user action is necessary.

LEX0038 Unable to change replication status of table. This table is not currently being replicated.

A change was requested to the replication status for a table that is not being replicated.

Bring Sybase Log Extract down. Check the data and indexes for the LTMOBJECTS table for accuracy. Then change the replication status.

LEX0039 Qualify status for table table has been changed to qualifier. Replicate_name is replication_name. Log RBA: rba log time date time Log LRSN: member: member

The value in the QUALIFY column of the LTMOBJECTS table has been changed. This value indicates whether the CREATOR value in the LTMOBJECTS table will pass to Replication Server.

No user action is necessary.

LEX0040 Log extract initialization complete.

Initialization of Sybase Log Extract is complete.

No user action is necessary.

LEX0041 Unable to initialize LTM communications.

Sybase Log Extract is unable to establish a communications link to LTM for MVS.

See the job log for additional messages describing the cause of the error.

LEX0042 Error detected on LTMRECV call.

Sybase Log Extract received an unexpected return code from the LTMRECV function. The return code received displays in message LEX0026.

If you cannot resolve the problem, contact Sybase Technical Support.

LEX0043 Error detected on LTMOPEN call.

Sybase Log Extract received an unexpected return code from the LTMOPEN function. The return code received displays in message LEX0026.

If you cannot resolve the problem, contact Sybase Technical Support.

LEX0044 Error detected on LTMSEND call.

Sybase Log Extract received an unexpected return code from the LTMSEND function. The return code received displays in message LEX0026.

If you cannot resolve the problem, contact Sybase Technical Support.

LEX0045 Command is not a valid command.

An invalid command is entered at the console.

See “Entering operator commands”.

LEX0046 Value command or parameter is too long.

An invalid command or parameter is entered at the console.

See “Entering operator commands”.

LEX0047 Error_code return_code detected in the replication registration entry for table table. replication will not be restarted for this table.

A non-zero ERROR_CODE value is detected in the LTMOBJECTS entry for the named table. Sybase Log Extract does not replicate changes made to this table. Possible ERROR_CODE values and their meanings are:

4--The table is not defined on this DB2 subsystem. The log RBA and URID have no meaning for this error. The name of the table as specified in the LTMOBJECTS table is probably incorrect.

8--Sybase Log Extract is unable to expand DB2 compressed log data.

12--The DATA CAPTURE CHANGES clause is not activated for this table.

16--An error is encountered while column data is being converted from its internal DB2 format.

Do one of the following, depending on the return code you received:

4--Use LTMCSET (in the Replication Agent interface panels) to delete the invalid row from the LTMOBJECTS table and to insert a new row with the correct table creator and name (see Chapter 4, “Managing Replication Agent”). Restart the Replication Agent started task.

8--Rematerialize the replicated tables before restarting replication of the affected table.

12--Rematerialize the replicated tables before restarting replication of the affected table.

16--Call Technical Support.

After the error is corrected or the replicated table in error is re-materialized, reset the ERROR_CODE column of the LTMOBJECTS table to 0 to restart replication of the affected table.

LEX0048 DB2 has terminated. Sybase Log Extract terminating.

The DB2 subsystem to which Sybase Log Extract connected with CONNECT terminated. Sybase Log Extract cannot run while DB2 is down. Sybase Log Extract terminates.

To restart the Replication Agent started task, restart DB2.

LEX0049 Unable to format data change log record for table table at RBA rba, LRSN: lrsn member: member.

The DB2 data row described by a data change log record cannot be formatted using the column definitions retrieved from the DB2 catalog. This occurs if a primary table is dropped and re-created and Replication Agent then runs to extract changes made to the table before it was dropped. It may also occur if user exit rearranges the column order in LE Command.

Rematerialize the replicated copy of the table. If you cannot resolve the problem, contact Sybase Technical Support.

LEX0050 Replicate name for table_name is rep_table_name. Log RBA rba log time date time LRSN: member: member.

The replication of the named table is performed using the value of the REPLICATE_NAME column in the LTMOBJECTS entry for this table.

No user action is necessary.

LEX0051 Replicate name for table table_name has been changed to new_name. Log RBA rba log time date time LRSN: lrsn member: member.

The value in the REPLICATE_NAME column of the LTMOBJECTS entry for this table is updated. The REPLICATE_NAME is modified because the Sybase Log Extract encountered a log record that describes a change to the REPLICATION_NAME column of the LTMOBJECTS entry for this table. Replication of this table continues using the updated value.

No user action is necessary.

LEX0052 Replicate name for table_name Has been changed to default to the actual table name. Log RBA rba Log time date time LRSN: lrsn member: member.

The value of the REPLICATION_NAME of the named table is updated and set to a value of blank. Sybase Log Extract continues replication of the named table using the DB2 table name.

No user action is necessary.

LEX0053 Replication bypassed for table table_name. Log RBA rba log time date time LRSN: lrsn member: member.

The replication of the named table is bypassed. Sybase Log Extract encountered a log record that would start replication; however, the record is ignored due to a previous error with the named table.

After the error is corrected, use LTMCSET (in the Replication Agent interface panels) to delete the row from the LTMOBJECTS table and to insert the row back into the LTMOBJECTS table to activate replication for the named table (see Chapter 4, “Managing Replication Agent”).

LEX0054 A row has been deleted from the LTMOBJECTS table. The row represented table_name which was not currently being replicated. Log rba rba log time date time lrsn: lrsn member: member.

A table not being replicated is deleted from the LTMOBJECTS table.

No action is necessary.

LEX0055 Unable to retrieve Data Sharing member information.

Sybase Log Extract is unable to obtain information about the data sharing environment.

If you cannot resolve the problem, contact Sybase Technical Support.

LEX0056 An error occurred while converting a Constant default value for Column: column type type. The system default has been used.

Sybase Log Extract is unable to convert a column value that was defined with a constant default.

Check the definition of the column.

LEX0057 Switch to log log data set name. Begin RBA: rba processing type record from member: member Log RBA: rba Log LRSN: lrsn.

Sybase Log Extract completed reading a DB2 log and started reading a different log.

No action is necessary.

LEX0058 IFI start call failed.

Sybase Log Extract was unable to obtain the high LRSN value because the ID running Replication Agent does not have permission to execute DB2 MONITOR2 and TRACE commands.

This is a Sybase Log Extract log reader error. The text of this message can vary. (See “What you need to know” for information.)

Grant MONITOR2 and TRACE permission on DB2 to the LTMADMIN user ID.

LEX0059 Fetch for high LRSN failed.

Sybase Log Extract was unable to obtain the high LRSN value because the ID running Replication Agent does not have permission to execute DB2 MONITOR2 and TRACE commands.

This is a Sybase Log Extract log reader error. The text of this message can vary. (See “What you need to know” for information.)

Grant MONITOR2 and TRACE permission on DB2 to the LTMADMIN user.

See Chapter 5, "Installing Replication Agent," in the Replication Agent for DB2 Installation Guide for MVS, for instructions on granting these permissions.

LEX0060 Variable text.

Sybase Log Extract encountered a problem reading the log.

This is a Sybase Log Extract log reader error. The text of this message can vary. (See “What you need to know” for information.)

Contact Sybase Technical Support.

LEX0061 Display group IFI call failed call attach error

A DB2 Display Group command was issued, but failed due to the call attach error that is displayed.

See the IBM DB2 Messages and Codes manual for additional information regarding this error and any action you should take to correct the problem. After the problem is corrected, shut down Sybase Log Extract and then restart.

LEX0062 QID: qid

This message displays during startup and shutdown of Sybase Log Extract.

No user action is necessary.

LEX0063 Tablespace table is a DB2 V5+ large object. This version of Sybase Log Extract does not support such objects. Data changes from this object may not be replicated accurately.

Sybase Log Extract does not support DB2 version 5 large objects in this version. Data for this table may not be replicated accurately.

No user action is necessary.

LEX0064 Error in reading the log not due to encountering the end of the log.

Sybase Log Extract cannot read the log file.

Contact Sybase Technical Support.

LEX0065 A connection could not be established to the subsystem DB2 subsystem.

The DB2 subsystem is not operating, or the Replication Agent is not configured to connect properly to the DB2 subsystem.

Verify that the configuration and authorization are correct and that the DB2 system is operational.

Contact Sybase Technical Support.

LEX0066 Incorrect number of buffers specified.

The Buffers configuration parameter must have a value from 1 to 50.

Change the Buffers configuration parameter to have a value between 1 and 50.

LEX0067 Table name %0s not found in repdefs.”

A table was specified in the LTMOBJECTS system table but was not found in the Replication definitions.

Add a replication definition and modify the LTMOBJECTS table error code to enable replication.

LEX0068 Replication %0s for table %1s.%2s.”

Replication has stopped or started for the table described in message parameters 1 and 2.

If replication on the table has stopped, check other Rep Agent messages to determine why.

LEX0069 Column %0s changed to %1s”

A character column has changed in the LTMOBJECTS table.

If the Rep Agent changed this column, check other Rep Agent messages to determine why.

LEX0070 Column %0s changed to %1h”

The ERROR_CODE column has changed in the LTMOBJECTS table.

If the Rep Agent changed this column, check other Rep Agent messages to determine the cause of the error. Then take appropriate action.

71=LEX_071,” Log RBA: %0x Log Time: %1x-%2x-%3x %4x.%5x.%6x”

Informational only.

No action required.

72=LEX_072,” Log LSRN: %0x Member: %1s”

Informational only.

No action required.

73=LEX_073,”LEX0073 DB2 Authorization Error rc=%0p reason=%1p. Check user priv

Log Extract is missing a DB2 privilege.

Check user privileges.

74=LEX_074,”LEX0074 ECSA memory allocated,(SP,231), pointer=0%0p length=%1p.”

Informational only.

No action required.