This chapter contains a list of the messages issued by DB2 replication for the Capture and Apply programs on all of the database management systems except DB2 for AS/400. The messages issued by DB2 replication for AS/400 are located in Replication messages for AS/400. The Replication Administration messages (DBA6001-DBA6110) are listed in the DB2 Message Reference.
The replication messages have the following prefixes:
Unless otherwise stated, all error codes described in error messages are internal error codes used by IBM Software Support. Also, unless otherwise stated, error messages are issued with a return code of 8.
You can also obtain explanations for messages by typing the following command at a DB2 command prompt:
db2 message_number
When you get a Capture program error, verify that your DB2 maintenance is at the most current level. The Capture program is an application program that uses DB2 APIs. Many Capture program errors are due to DB2 maintenance that is not current.
When you start DB2 with the cold start option, you must also start the Capture program with the cold start option.
| Note: | For SQL errors, see the DB2 Message Reference for your platform. |
| ASN0000S | An internal error occurred for message number "<number>". The error code is "<error_code>". The return code is "<return_code>". |
Explanation: The message file for the Capture program was installed incorrectly, or the language environment variables are not set correctly. This message is displayed because no other Capture program message could be formatted.
User Response: Refer to the installation and configuration information in this book pertaining to your platform. Make sure that the message file is installed in the correct directory, and the language environment variables are set correctly. If the language environment variables are set correctly, contact IBM Software Support.
| ASN0001E | The Capture program encountered an SQL error. |
Parameters:
Explanation: A nonzero SQLCODE was returned when the Capture program issued an EXEC SQL statement.
User Response: See the messages and codes publication of the DB2 database manager on your platform for information about SQL return codes that use SQLERRML and SQLERRMC as substitution fields. Contact your DBA for more information.
| ASN0002E | The Capture program could not connect to DB2. |
Parameters:
Explanation: An error occurred when the Capture program issued:
User Response: See DB2 codes in the messages and codes publication of the DB2 database manager on your platform for the appropriate reason code.
For DB2 for OS/390 errors, see the section in the administration guide that describes the Call Attachment Facility. Contact your DBA for questions and diagnosis.
If you are running Capture under DB2 UDB for UNIX or under DataJoiner for UNIX, ensure that the LIBPATH environment variable is set to the same environment in which the Capture program starts. See Starting Capture for UNIX platforms for more information.
| ASN0003E | The Capture program could not open the plan. |
Parameters:
Explanation: An error occurred when the Capture program tried to open the plan, ASNLPLAN.
User Response: See the DB2 Codes section in the messages and codes publication of the DB2 database manager on your platform to find the appropriate reason code. See the section in the administration guide that describes the Call Attachment Facility.
| ASN0004E | The Capture program could not start the trace. |
Parameters:
Explanation: An error occurred when the START TRACE DB2 command was issued, or when Capture program read the DB2 log.
User Response: See the DB2 Codes section of in the messages and codes publication of the DB2 database manager on your platform to find the appropriate reason code. For more information, see either of the following sections in the administration guide: the Call Attachment Facility (CAF) for START TRACE DB2 errors, or the Instrumentation Facility Interface (IFI) for DB2 log read errors, or contact your DBA. If the CAF or the IFI returned a message, it is also printed on the system display console.
| ASN0005E | The Capture program encountered an error while reading the DB2 log. |
Parameters:
Explanation: An error occurred when the Capture program read the DB2 log. There might be an SQL error.
For Capture program for OS/390, an MVS system dump is generated for this message that is contained in MVS dump data set SYS1.DUMP.
For DB2 DataPropagator, the "<return_code>" value is for the Asynchronous Read Log API.
For Capture for VSE, the "<return code>" is for the VSE/VSAM GET macro.
For Capture for VM, the "<return code>" is for Diagnose X'A4'.
User Response: See the DB2 Codes section in the messages and codes publication of the DB2 database manager on your platform for the appropriate reason code.
For Capture program for OS/390, see the Instrumentation Facility Interface (IFI) section in the administration guide publication of the DB2 database manager on your platform or contact your DBA.
For Capture for VSE, see the VSE/VSAM Commands and Macros, VSE/ESA System Macro Reference, and VSE/ESA V2R3 Messages and Codes manuals for more information.
For VM/ESA, see the VM/ESA Programming Services for more information.
For Capture on UNIX, Windows, and OS/2, see the active and archived database logs section in the DB2 UDB Administration Guide or contact IBM Software Support.
| ASN0006E | The Capture program encountered an unexpected log error of unknown log variation. The routine name is "<routine>". |
Explanation: An unexpected log error not reported by either:
occurred while the Capture program was processing the DB2 log records. The Capture program could not determine the type of SQL update associated with the log record.
For Capture program for OS/390, an MVS system dump is generated for this message that is contained in MVS dump data set SYS1.DUMP.
User Response: Contact IBM Software Support.
| ASN0007E | The Capture program encountered an unexpected log error of unimplemented data type. The routine name is "<routine>". |
Explanation: An unexpected log error not reported by either:
occurred while the Capture program was processing the DB2 log records. The Capture program could not determine the type of SQL update associated with the log record.
For Capture program for OS/390, an MVS system dump is generated for this message that is contained in MVS dump data set SYS1.DUMP.
User Response: Contact IBM Software Support.
| ASN0008I | The Capture program was stopped. |
Explanation: The IBM Replication administrator stopped the Capture program using one of the valid methods.
Explanation: This message is for your information only.
User Response: No action is required.
| ASN0009E | The table was created without the DATA CAPTURE CHANGES (DCC) attribute. |
Parameters:
Explanation: The source table was defined without the DCC attribute and the Capture program tried to capture changes for the replication source.
User Response:
| ASN0010E | The Capture program cannot obtain enough storage. |
Parameters:
Explanation: The Capture program cannot continue processing because not enough free storage is available. Usually 2MB is enough storage.
User Response: For Capture program for OS/390, ensure that the REGION parameter has enough storage allocated to run your job. If necessary, contact your OS/390 system programmer to determine the method for requesting sufficient storage.
For Capture for VM, a request to obtain virtual storage could not be satisfied. You might need to increase the size of the virtual machine in which Capture program runs.
For Capture for VSE, all available GETVIS storage has been exhausted. You might need to restart the Capture program after allocating a larger partition.
If you believe enough storage has been allocated, contact IBM Software Support.
| ASN0011E | The DB2 compression dictionary is not available or the IFCID 306 buffer is invalid. |
Parameters:
Explanation: In the case of the DB2 compression dictionary not being available, the Capture program attempted to read log records for an old compression dictionary. DB2 for OS/390 only retains one version of the compression dictionary in memory. DB2 can only decompress log records for a compressed table if the compression dictionary used to compress the log records is still the current compression dictionary.
In the case of the IFCID 306 buffer not being valid, the control information is missing from the buffer.
For Capture program for OS/390, an MVS system dump is generated for this message that is contained in MVS dump data set SYS1.DUMP.
User Response: For the DB2 compression dictionary error, to avoid an unwanted cold start of the Capture program, you must capture all log records for a compressed table before creating a new version of the compression dictionary. Use the KEEPDICTIONARY option to retain the current version of the compression dictionary during routine REORG processing.
When you want a new compression dictionary for the table, you must synchronize running the REORG utility with running your updated applications and the Capture program as follows:
For the IFCID 306 buffer error, ensure that all DB2 maintenance is current.
If you believe neither of these problems is the case, contact IBM Software Support. Maintenance could be the problem.
| ASN0013E | The Capture program required a column that was not defined in the change data (CD) table. |
Parameters:
Explanation: The user did not define a required column in the change data table.
User Response: Ensure that the change data table definition is correct. Refer to Change data table for more information.
| ASN0014E | The processing of the Capture program has fallen below a minimum level. The log record lags current time by "<number>" seconds. The routine name is "<routine>". |
Explanation: The Capture program terminated because a high DB2 transaction rate caused the Capture program to run slower than the defined minimum level.
User Response: Refer to the Capture and Apply chapter for your platform for more information on the lag limit. Then you can:
| ASN0015E | The Capture program encountered a storage allocation error. |
Parameters:
Explanation: A storage allocation error was detected; sufficient storage is not available. The Capture program might have been installed improperly.
For the Capture program on AIX, you might not have set the soft links for the component files to the shared directory.
User Response: Determine why storage could not be allocated by looking at the operating system and application task status. Contact your system programmer to determine the method of requesting the storage listed in the error message. Also verify that all C libraries are at the current maintenance level. If you believe enough storage space has been allocated, contact IBM Software Support.
For Capture for AIX, determine whether you have set the soft links for the component files.
For Capture for VM, a request to obtain virtual storage could not be satisfied. You might need to increase the size of the virtual machine in which Capture program runs.
For Capture for VSE, all available GETVIS storage has been exhausted. You might need to restart the Capture program after allocating a larger partition.
For Capture for OS/390 consult the program directory for instructions and verification of the appropriate C library level.
| ASN0016E | The Capture program could not begin capturing changes because there was no eligible replication source. |
Parameters:
Explanation: The replication source information in the register table has not been defined.
The Capture program started but could not find source tables that were:
User Response: Ensure that the register table is defined properly. For more information about the register table, see Register table. Verify that replication sources have been defined.
| ASN0017E | The Capture program encountered a severe internal error and could not issue the correct error message. The routine name is "<routine>"; the return code is "<return_code>"; the error message number is "<error_message_num>". |
Explanation: The Capture program could not retrieve the message from the Capture program error messages file.
User Response: Edit the Capture program error messages file. Locate the ASNnnnn error message number to determine which error message should have been issued. See the information about the error message in this chapter to determine how to resolve the error. Consult the installation instructions for your platform.
| ASN0018W | The Capture program did not process updates made to the register table rows. The routine name is "<routine>"; the table name is "<table_name>". |
Explanation: The user changed a replication source definition while the Capture program was running and then issued a REINIT command. The register table, which contains a row for each replication source, might not match the other replication source control tables.
User Response:
| ASN0019E | The Capture program libraries are not authorized for the Authorized Program Facility (APF). |
Explanation: The Capture program cannot process the STOP, SUSPEND, RESUME, or REINIT commands because the STEPLIB libraries are not authorized for APF.
User Response: Authorize the Capture link library for APF.
| ASN0020I | Netview Generic Alerts Interface failure. The Netview return code is "<return_code>". |
Explanation: The Network Major Vector Transport (NMVT) could not be sent to Netview by the program because the program interface failed. This is a secondary informational message.
User Response: See the Netview programming documentation for a description of the return code to determine the interface error. The Capture program alerts will not be received by the System Services Control Point (SSCP) until the error is corrected.
| ASN0021I | Netview Program to Program Interface unavailable. The Netview return code is "<return_code>". |
Explanation: Netview is unavailable. This is a secondary informational message.
User Response: See the Netview programming documentation for a description of the return code to determine the Netview problem. For example, the subsystem might not have been started.
| ASN0022E | DB2 release "<release>" is not supported. The routine name is "<routine>". |
Explanation: The Capture program does not support this release of DB2.
User Response: Run the Capture program with the appropriate release of DB2.
| ASN0023I | The Capture program successfully reinitialized the register table. The table name is "<table_name>"; the routine name is "<routine_name>". |
Explanation: A REINIT command was issued and the updates were successfully made to the Capture program internal control information. This message is for your information only.
User Response: No action is required.
| ASN0024I | The Capture program did not need to reinitialize the register table. Table "<table_name>"did not change. |
Explanation: The REINIT command was issued. No updates were made to the register table since initialization or the last REINIT. This message is for your information only.
User Response: No action is required.
| ASN0025I | The Capture program reinitialized the register table. Table "<table_name>" has "<number>" potentially bad row(s). |
Explanation: This message accompanies ASN0018W. Reinitialization was performed as requested despite potential problems reported in ASN0018W.
User Response: See ASN0018W.
| ASN0026W | The Capture program could not allocate the trace buffer. The routine name is "<routine>"; the storage required is <required_storage>". |
Explanation: A storage allocation error was detected; not enough storage is allocated for the trace buffer. The trace buffer is an information-only feature of the Capture program and the allocated storage is not required for the Capture program to run.
User Response: Contact your system programmer to determine the method of requesting the storage listed in the error message.
For Capture for VM, a request to obtain virtual storage could not be satisfied. You might need to increase the size of the virtual machine in which the Capture program runs.
For Capture for VSE, all available GETVIS storage has been exhausted. You might need to restart the Capture program after allocating a larger partition.
| ASN0027W | The Capture program is already active. |
Explanation: You tried to start more than one the Capture program per DB2 subsystem or database.
For VSE/ESA, Capture for VSE generates a unique lock name for each database. This lock name is already in use, indicating that Capture for VSE is already active for the database.
For VM/ESA, Capture for VM has determined that the resource ID used as a lock is already in use. The resource ID is specified on the ENQ_NAME parameter of the CAPTURE ASNPARMS file.
User Response: For DB2 for OS/390 subsystems, either run only one instance of the Capture program for all subsystems that are members of a data-sharing group, or run only one instance of the Capture program on any stand-alone system. Display the ENQ resource to determine the unique resource name violation.
For other DB2 database platforms, run only one Capture program per database.
For Capture for VM, you can change the ENQ_NAME parameter in the CAPTURE ASNPARMS to ensure unique values for each Capture program if you want to run Capture for VM for more than one DB2 database on a system.
| ASN0028I | The Capture program is suspended by operator command. |
Explanation: The IBM Replication administrator suspended the Capture program, and the program has entered a wait state. This message is for your information only.
User Response: No action is required.
| ASN0029I | The Capture program is resumed by operator command. |
Explanation: The IBM Replication administrator resumed the Capture program from a suspended state and the Capture program has continued running. This message is for your information only.
User Response: No action is required.
| ASN0030I | The Capture program command entered by the operator was unrecognized. |
Explanation: The IBM Replication administrator entered a command not recognized by the Capture program. The only valid commands are:
There are no parameters allowed for these commands.
User Response: Use only valid Capture program commands.
| ASN0031E | The Capture program tuning parameters table can have only one row. The routine name is "<routine>"; the table name is "<table_name>". |
Explanation: The tuning parameters table was not defined correctly or has been updated with invalid rows.
User Response: Refer to Tuning parameters table to determine the correct format of this table. Remove any invalid rows.
| ASN0033E | The Capture program could not reinitialize the register table. The table name is "<table_name>". |
Explanation: The IBM Replication administrator tried to reinitialize the Capture program, but there was an error in the register table. A user might have tried to update a replication source while the Capture program was running or suspended, and the register table might not match the other control tables.
User Response: This is a secondary message. See any preceding messages for more information about the error. See the Capture and Apply chapter for your platform for more information about reinitializing the Capture program, and Register table for information about the register table.
| ASN0034E | An incorrect value was supplied for column "<column>"of the Capture program tuning parameters table. The routine name is "<routine>"; the table name is "<table_name>". |
Explanation: The tuning parameters table does not have the correct values. Values might be out of range.
User Response: Check the lag limit, retention period, and commit frequency. Refer to Tuning parameters table, or to the Capture and Apply chapter for your platform for more information.
| ASN0035W | Some rows were found in the register table with an unsupported architectural level. The routine name is "<routine>"; the table name is "<table_name>". |
Explanation: The register table version does not match the current version of the Capture program. The current version of the DB2 Control Center is not compatible with the version of the Capture program that you are running.
User Response: Refer to Register table to check the required value for the ARCH_LEVEL column in the register table. Verify that the value in the register table at the source server is correct. If not, use compatible versions of the DB2 Control Center and the Capture program.
| ASN0036E | DB2 was terminated abnormally. The routine name is "<routine>". |
Explanation: DB2 was terminated while the Capture program was still active.
For OS/390, VSE/ESA, or VM/ESA, DB2 was terminated while Capture program was active and the user did not specify the NOTERM invocation parameter.
User Response: Start DB2 and start the Capture program.
| ASN0037W | DB2 was terminated in QUIESCE mode. The routine name is "<routine>". |
Explanation: DB2 was terminated while the Capture program was still active.
User Response: Start DB2 and start the Capture program.
| ASN0038E | The disconnect to DB2 failed. The routine name is "<routine>"; the return code is "<return_code>"; the reason code is "<reason_code>". |
Explanation: DB2 was stopped in QUIESCE mode, but the user wanted to leave the Capture program running. While terminating the connection to DB2, the Capture program received an error returned code from the Call Attachment Facility (CAF).
User Response: Restart the Capture program.
| ASN0040E | An error was returned from the FORK function of "<platform>". The error is "<error_text>". |
Explanation: An AIX FORK function returned a negative value. "<Error_text>"describes the error.
User Response: See AIX Calls and Subroutines Reference for information about FORK functions, use the provided error text to determine the error, or contact IBM Software Support.
| ASN0041E | An error was returned while getting the instance name. The reason code is "<reason_code>". |
Explanation: The SQLEGINS API of DB2 Universal Database returned an error.
User Response: See the DB2 Universal Database API Reference for information about the SQLEGINS API to determine the error, or contact IBM Software Support.
| ASN0042E | An error was returned from the EXECLP function. The error is "<error_text>". |
Explanation: The AIX EXECLP function returned a negative value. "<Error_text>" describes the error.
User Response: See the AIX Calls and Subroutines Reference for information about the EXECLP function, or contact IBM Software Support.
| ASN0043E | A child process of ASNLMAIN died. |
Explanation: The child process created by ASNLMAIN terminated. Possible causes include:
User Response: Check the system processes for conflicts, or contact your AIX system programmer.
| ASN0044E | The child process has not called the dummy process after an extended wait. |
Explanation: The child process was unable to call the dummy routine ASNLPVRF. The installation soft links might not have been set.
User Response: Verify whether the installation soft links have been set, check the system for problems, or contact IBM Software Support.
| ASN0045E | An error was returned from the MSGRCV function. The error is "<error_text>". |
Explanation: The function MSGRCV returned an error. "<Error_text>" describes the error. This error can be caused by ASNCMD sending a message that ASNCCP could not process.
User Response: Use the provided error text to determine the error, or contact IBM Software Support.
| ASN0046E | An error was returned from the MSGGET function. The error is "<error_text>". |
Explanation: The function MSGGET returned an error. "<Error_text>" describes the error. This error occurs during message handling. This error can be caused by an ASNCMD process failure.
User Response: Use the provided error text to determine the error, or contact IBM Software Support.
| ASN0047E | An error was returned from the FTOK function of "<platform>". The error is "<error_text>". |
Explanation: The AIX function FTOK returned an error. "<Error_text>" describes the error.
User Response: See AIX Calls and Subroutines Reference for information about the FTOK function, use the provided error text to determine the error, or contact IBM Software Support.
| ASN0048E | The Capture program could not open the log file. The error is "<error_text>. The error code is "<error_code>". |
Explanation: The Capture program could not open the log file. Some possible reasons are:
User Response: Contact your system programmer to determine the error, or contact IBM Software Support.
| ASN0050E | The Capture program encountered an error while writing to the error message file. |
Explanation: An I/O error occurred while writing to the Capture program log file.
User Response: Check the trace table for error messages.
| ASN0053E | An error was returned by the Asynchronous Read Log API (SQLURLOG). |
Parameters:
Explanation: The Asynchronous Read Log API returned an SQLCODE in the SQL error message that preceded this message. The information in this message provides additional information about the SQL error.
User Response: See message ASN0001E for information about SQLCODEs.
| ASN0054E | The Capture program did not recognize the invocation parameter. |
Explanation: An invalid invocation parameter was entered with the ASNCCP command.
User Response: Enter a valid invocation parameter.
See the Capture and Apply chapter for your platform for information about valid invocation parameters.
| ASN0055E | The Capture program encountered an SQLTYPE that is not supported in the origin table. |
Parameters:
Explanation: The Capture program encountered an invalid SQL type. A table might have been defined as a replication source outside the DB2 Control Center that contains unsupported SQL types (for example, binary data types with precision).
User Response: Delete the replication source and use the DB2 Control Center to define replication sources to ensure that only valid types are defined. Or, when manually defining the replication source, ensure that the table contains only supported SQL types. See the messages and codes publication of the DB2 database manager on your platform to determine the invalid SQLTYPE.
| ASN0056E | ASN.IBMSNAP_UOW table does not exist. |
Explanation: The unit-of-work (UOW) table or the source server database might have been dropped.
User Response: Contact IBM Software Support.
| ASN0100I | The Capture program initialization is successful. |
Explanation: This message is for your information only.
User Response: No action is required.
| ASN0101W | The Capture program warm start failed because existing data is too old; a cold start will be attempted. |
Explanation: The data in the change data tables is older than the value "<current_timestamp_lag_limit>". A cold start will be performed.
User Response: See Starting or restarting the Capture program for more information about warm and cold starts to determine why the Capture program could not warm start.
| ASN0102W | The Capture program will switch to cold start because the warm start information is insufficient. |
Explanation: A problem occurred during the retrieval of the warm start information. The warm start table data was invalid. A cold start will be performed.
For DB2 Universal Database, an Asynchronous Read Log API error occurred while reading the log during warm start. For OS/390, an Instrumentation Facility Information (IFI) error occurred while reading the log during warm start.
User Response: See Starting or restarting the Capture program for more information about warm and cold starts to determine why the Capture program could not warm start.
| ASN0103I | The Capture program started with: "<server_name>". |
Parameters:
Explanation: This is an informational message that displays the DB2 server name and the Capture program start up options.
For Capture for VSE and VM, the ENQ_NAME shows the name on which Capture program locks to make sure that there is only one Capture program running for any DB2 database. The lock name can be specified for VM/ESA by changing the ENQ_NAME parameter value in the CAPTURE ASNPARMS file.
User Response: No action is required.
| ASN0104I | Change capture started for owner "<owner>", the table name is "<copy_table>" at log sequence number (LSN) "<log_sequence_number>". |
Explanation: The Capture program was started for the table owner and table name at the specified log sequence number (LSN). This message is issued for each origin table for which the Capture program captures changes. This message is for your information only.
User Response: No action is required.
| ASN0105I | Data that has been copied was pruned from the change data table and the unit-of-work table. |
Explanation: This message is for your information only.
User Response: No action is required.
| ASN0106I | The Capture program is waiting for DB2 to come up. |
Explanation: When the Capture program is initially brought up, if DB2 is not up at that time, the Capture program waits until DB2 is up. After DB2 is up, the Capture program makes the connection and begins to capture changes.
If the NOTERM option is specified in the Capture invocation parameters, and DB2 comes down smoothly, the Capture program waits for it to come back up.
User Response: No action is required.
| ASN0110E | Capture for OS/390 Storage Dump. The Control Address is "<address>". |
Explanation: An MVS system dump was generated for a severe error message. The dump is contained in dump data set SYS1.DUMP. An IPCS readable system dump contains more diagnostic information than the Capture program trace and can be used by IBM to diagnose system problems.
User Response: No action is required.
| ASN0115I | The warm start control information was not supplied. The routine name is "<routine>"; the table name is "<table_name>". |
Explanation: The warm start table is missing or corrupted. This table provides a faster warm start. The Capture program will warm start.
User Response: No action is required.
| ASN0116I | The Capture program did not reinitialize the tuning parameters table. The routine name is "<routine>"; the table name is "<table_name>". |
Explanation: The REINIT command was issued, but tuning parameter information from the tuning parameters table was not available. The previous tuning parameter values were retained.
User Response: No action is required.
| ASN0117W | Warm start control information was not saved. The routine name is "<routine>"; the table name is "<table_name>". |
Explanation: An error occurred that prevented warm start information from being saved in the warm start table. Warm start will take longer because other tables will be used.
User Response: No action is required.
| ASN0121E | The Capture program warm start failed because existing data is too old. The Capture program will terminate. |
Explanation: The time of the warm start information exceeded the lag limit.
User Response: No response required; the Capture program will terminate because WARMNS was specified.
| ASN0122E | An error occurred while reading the warm start information or DB2 log. The Capture program will terminate. |
Explanation: A problem occurred while retrieving the warm start information. The warm start table data was invalid or for OS/390, an Instrumentation Facility Interface (IFI) error occurred while reading the log during warm start. When the error is resolved, you can restart using the warm start option.
User Response: No response required; the Capture program will terminate because WARMNS was specified.
| ASN0123I | The highest log sequence number of a successfully captured log record is "<log_sequence_number>". |
Explanation: The Capture program saved the highest log sequence number (LSN) in the warm start table. This is the point at which the Capture program finished successfully processing the log data.
User Response: No response required; the Capture program will terminate.
| ASN0124I | The prune command was accepted; the pruning action is queued. |
Explanation: The IBM Replication administrator entered the PRUNE command and the Capture program has queued the request. The Capture program will prune the change data (CD) table and the unit-of-work (UOW) table.
User Response: No response required.
| ASN0125I | The current log sequence number of successfully processed log records is "<log_sequence_number>". The log timestamp is "<timestamp>". |
Explanation: Capture program is processing the DB2 log at the log sequence number provided.
User Response: No action is required.
| ASN0126E | The Capture program encountered a syntax error. The Capture program will terminate. |
Explanation: The Capture program encountered the wrong combination of invocation parameters.
User Response: Check the Capture and Apply chapter for your platform for more information about the START command.
| ASN0130I | The user requested that the Capture program start reading from the end of the DB2 log. |
Explanation: The user specified the WRMSKPM parameter when invoking the Capture program.
User Response: No action is required.
| ASN0133I | The Capture program reached the end of the mobile transactions. |
Explanation: This message is for your information only.
User Response: No action is required.
| ASN0135E | The trial period for the Capture program has expired. |
Explanation: The trial period for the DB2 DataPropagator product has ended. You can no longer use this product until you order and install the DataPropagator licensed feature of DB2 for OS/390.
User Response: Contact the person responsible for ordering the DB2 DataPropagator product. Note that even though the error message ASN0017E is also issued, you should not follow the suggested action for that message.
| ASN0136I | The trial version of Capture will end in nn days. |
Explanation: You are using the trial version of DB2 DataPropagator. After nn days have passed, you will no longer be able to use DB2 DataPropagator unless you install the DataPropagator licensed feature of DB2 for OS/390.
User Response: None; however you might want to contact the person responsible for ordering the DB2 DataPropagator product.
| ASN0137E | The product registration module has unexpected content. |
Explanation: The content of the registration module (ASNLPR61) for the DB2 DataPropagator feature is not as expected for this version of the DB2 DataPropagator product. No further use of the product is possible until you provide the correct registration module.
User Response: Verify that the DB2 DataPropagator feature was installed without errors. If errors occurred, correct them and try again.
If the DB2 DataPropagator feature installed without error and you are correctly accessing the feature-registration module (ASNLPR61), contact IBM Software Support.
| ASN0138E | The product trial module has unexpected content. |
Explanation: The content of the DB2 DataPropagator trial module is not as expected for this version of the DB2 DataPropagator product. No further use of the product is possible until you provide the correct trial module.
User Response: Verify that the DB2 DataPropagator feature was installed without errors. If errors occurred, correct them and try again.
If the DB2 DataPropagator feature installed without error and you are correctly accessing it, contact IBM Software Support.
| ASN0139E | The Capture program could not open the trace file. The error is "<error_code>". |
Explanation: The user specified the TRCFILE option, but the Capture program could not open the trace file. Possible reasons are:
User Response: Contact your system programmer, or IBM Software Support.
| ASN0200E | An incorrect parameter "<parameter>" was passed to the Capture program. |
Explanation: For VM/ESA, one of the following situations caused an error:
For VSE/ESA, an invalid parameter was specified on the ASNCCP command.
User Response: Verify that the parameters supplied are valid. See the Capture and Apply chapter for your platform for more information about the ASNCCP command.
| ASN0201E | The Capture program encountered a "<platform>" error. The routine name is "<routine>"; the function name is "<function>"; the return code is "<return_code>". |
Explanation: On VM:
On VSE:
User Response: Correct the error as described in the platform documentation. On VM:
On VSE:
| ASN0202E | The USERID parameter was not specified. |
Explanation: The USERID parameter is required in the PARM= field on the EXEC job control statement that is passed to the Capture program.
User Response: Add the USERID= parameter, specifying the user ID and password in the PARM= field, and resubmit the job.
| ASN0203I | Linking to "<diskname>" minidisk"<diskowner>"as "<vdev>". |
Explanation: The Capture program is about to issue an internal CP link command to the specified database minidisk.
User Response: If prompted, enter the minidisk password.
| ASN1000S | An internal error occurred for message number "<number>". Its substitution fields are "<substitution_field_1>", "<substitution_field_2>", "<substitution_field_3>", "<substitution_field_4>", "<substitution_field_5>", "<substitution_field_6>", and "<substitution_field_7>". The error code is "<error_code>". The return code is "<return_code>". |
Explanation: The message file for the Apply program was installed incorrectly, or the language environment variables are not set correctly. This message is displayed because no other Apply message could be formatted.
User Response: Refer to the installation and configuration information in this book pertaining to your platform. Make sure that the message file is installed in the correct directory, and the language environment variables are set correctly. If the language environment variables are set correctly, contact IBM Software Support.
| ASN1001E | The Apply program encountered an SQL error. |
Parameters:
Explanation: An error occurred during the execution of an SQL statement.
User Response: Refer to your database message reference for an explanation of the SQL error code.
| ASN1002E | The "<table_name>" could not be locked. ERRCODE is "<error_code>", SQLSTATE is "<sqlstate>", SQLCODE is "<sqlcode>", SQLERRM is "<sqlerrm>", SQLERRP is "<sqlerrp>", server name is "<server_name>", table name is "<table_name>" |
Explanation: The Apply program could not lock the table.
User Response: Refer to your database message reference.
| ASN1003E | The Apply program could not connect to the server "<server>". |
Parameters:
Explanation: The Apply program attempted to connect to the database and received a failing return code. There are many reasons why the Apply program could not connect to the database. For example, the Apply program would receive a failing return code if the database was down or too many users were accessing it.
User Response: Look up the SQLCODE in the DB2 messages and codes manual to determine why the connection failed. See Setting up end-user authentication at the source server for more information.
Refer to your database message reference for an explanation of the SQL error code.
| ASN1004I | The trial version of Apply will end in nn days. |
Explanation: You are using the trial version of DB2 DataPropagator. After nn days have passed, you will no longer be able to use DB2 DataPropagator unless you install the DataPropagator licensed feature of DB2 for OS/390.
User Response: None; however you might want to contact the person responsible for ordering the DB2 DataPropagator product.
| ASN1005E | The trial period for the Apply program has expired. |
Explanation: The trial period for the DB2 DataPropagator product has ended. You can no longer use this product until you order and install the DataPropagator licensed feature of DB2 for OS/390.
User Response: Contact the person responsible for ordering the DB2 DataPropagator product.
| ASN1006E | The product registration module has unexpected content. |
Explanation: The content of the registration module (ASNAPR61) for the DB2 DataPropagator feature is not as expected for this version of the DB2 DataPropagator product. No further use of the product is possible until you provide the correct registration module.
User Response: Verify that the DB2 DataPropagator feature was installed without errors. If errors occurred, correct them and try again.
If the DB2 DataPropagator feature installed without error and you are correctly accessing the feature-registration module (ASNAPR61), contact IBM Software Support for assistance.
| ASN1007E | The product trial module has unexpected content. |
Explanation: The content of the DB2 DataPropagator trial module is not as expected for this version of the DB2 DataPropagator product. No further use of the product is possible until you provide the correct trial module.
User Response: Verify that the DB2 DataPropagator feature was installed without errors. If errors occurred, correct them and try again.
If the DB2 DataPropagator feature installed without error and you are correctly accessing it, contact IBM Software Support for assistance.
| ASN1008E | The subscription set with Apply qualifier "<qualifier>" and set name "<set_name>" is not defined correctly. ERRCODE is <error_code>". |
Explanation: The subscription set is not defined correctly.
User Response: Make sure that the WHOS_ON_FIRST column in the subscription set table is specified correctly.
| ASN1009E | There is no subscription set defined for Apply qualifier "<qualifier>". |
Explanation: There is no subscription set defined for Apply qualifier "<qualifier>".
User Response: Define at least one subscription set for Apply qualifier "<qualifier>".
| ASN1010E | The Apply program could not insert row "<row>" into the audit trail table due to the following error: "<error_code>". |
Explanation: This is an SQL return code indicating that the audit trail table was not set up with the same structure as the table in Apply trail table.
User Response: Refer to Apply trail table and your database SQL manual.
| ASN1011E | The copy request has incompatible source and target attributes. The error code is "<error_code>". |
Explanation: This is an SQL error code indicating that the attributes of the target table must be compatible with the attributes of the source table.
User Response: Refer to the SOURCE_STRUCTURE column in the register table for the compatibility of the source and target attributes.
| ASN1012E | The source table structure is invalid. The error code is "<error_code>". |
Explanation: This is an SQL return code indicating that the source table structure in the register table was not set up according to the SOURCE_STRUCTURE column in the register table.
User Response: Refer to Register table, the SOURCE_STRUCTURE column in the register table for valid source table structures.
| ASN1013E | The target table structure is invalid. The error code is "<error_code>". |
Explanation: The target table structure in the subscription-targets-member table was not valid.
User Response: Refer to Subscription-targets-member table for valid target table structure.
| ASN1014E | The Apply program could not find a source for the copy request because it could not find the change data table. The error code is "<error_code>". |
Explanation: The change data table was not defined in the register table because either the Apply program did not find the change data table name in the register table or the source table was not registered correctly.
User Response: Refer to Register table and verify that the change data table is correctly defined in the register table (CD_OWNER, CD_TABLE).
| ASN1015I | The Apply program is waiting for the Capture program at server "<server_name>" to advance the global SYNCHTIME. Verify that the Capture program is running. |
Explanation: This message is for your information only.
User Response: Verify that the Capture program is running.
| ASN1016I | Refresh copying has been disabled. The error code is "<error_code>". |
Explanation: While attempting to perform a full refresh, the Apply program encountered a DISABLE_REFRESH column in the register table which was set on.
User Response: Either turn off the DISABLE_REFRESH column or bypass the Apply program and perform a manual refresh.
| ASN1017E | Apply could not find any target column names. The error code is "<error_code>". |
Explanation: The Apply program could not find any columns in the subscription columns table.
User Response: Redefine the subscription set and subscription-set members (see Setting up your replication environment for instructions).
| ASN1018I | The Apply program is processing subscription set "<set_name>"("<whos_on_first>"). ("<set_number>" of "<total_sets>"). |
Explanation: This message is for your information only.
User Response: No action is required.
| ASN1019E | The target table does not have any key columns. The error code is "<error_code>". |
Explanation: The Apply program could not find key column names in one of the columns requiring a primary key.
User Response: Redefine the subscription set and the subscription-set members (see Setting up your replication environment for instructions).
| ASN1020S | The Apply program could not reserve a storage block. The error code is "<error_code>". |
Explanation: The Apply program could not obtain the required (memory) storage.
User Response: Contact IBM Software Support.
| ASN1021S | The Apply program could not read the work file. The error code is "<error_code>". |
Explanation: The Apply program could not read the work file due to a system error.
User Response: Determine if the problem is caused by lack of space and contact your system administrator to obtain what is needed.
| ASN1022S | The Apply program could not write into the work file. The error code is "<error_code>". |
Explanation: Either the user does not have the proper access authority for one or all of the files or not enough space is left after writing to the target file.
User Response: Determine whether the problem is caused by a lack of access authority or a lack of space and contact your system administrator to obtain what is needed.
| ASN1023S | The Apply program could not open the work file. The error code is "<error_code>". |
Explanation: The Apply program could not open the work file.
User Response: Contact IBM Software Support.
| ASN1024S | The Apply program could not close the work file. The error code is "<error_code>". |
Explanation: The Apply program could not close the work file.
User Response: Contact IBM Software Support.
| ASN1025I | The Apply program completed processing for subscription set "<set_name>"("<whos_on_first>"). The return code is "<return_code>". |
Explanation: This message is for your information only.
User Response: No action is required.
| ASN1026I | The Apply program encountered an error while trying to bind. SQLSTATE is "<sqlstate>", SQLCODE is "<sqlcode>". |
Explanation: An error occurred during the execution of bind.
User Response: Refer to your database message reference.
| ASN1029E | The SQL statement could not execute. The error code is "<error_code>". |
Explanation: The execution of the SQL statement specified by the user was not successful.
User Response: Refer to SQLSTATE, SQLCODE, SQLERRO, and SQLERRM in the apply trail table and in your database SQL manual for detailed information.
| ASN1030S | The Apply program encountered an OS/2 error. The error code is "<error_code>"; the return code is "<return_code>". |
Explanation: The execution of an OS/2 API failed.
User Response: For more information on the return code, refer to the OS/2 WARP Control Program Programming Reference.
| ASN1031E | The SQL statement is empty. The error code is "<error_code>". |
Explanation: The SQL statement is an empty string.
User Response: Specify the SQL statement to be executed.
| ASN1032S | The Apply program log file could not be opened. The error code is "<error_code>"; the return code is "<return_code>". |
Explanation: The Apply program could not open the log file.
User Response: For more information on the return code, refer to the manual that describes problem determination for your particular platform.
| ASN1033E | The Apply program could not write to the Apply log file. The error code is "<error_code>"; the return code is "<return_code>". |
Explanation: The Apply program could not write to the log file.
User Response: For more information on the return code, refer to the manual that describes problem determination for your particular platform.
| ASN1035E | The Apply program could not access the subscription columns table. |
Parameters:
Explanation: An error occurred during the execution of an SQL statement.
User Response: Refer to your database message reference for SQL.
| ASN1036E | The column type "<col_type>" for expression "<expression>" is invalid. The error code is "<error_code>". |
Explanation: The value for the COL_TYPE column in the subscription columns table is invalid.
User Response: Change the value to A, B, C, D, F, L, or R.
| ASN1037E | The Apply program could not obtain the date and time. The error code is "<error_code>"; the return code is "<return_code>". |
Explanation: The OS/2 API DosGetDateTime failed.
User Response: For more information on the return code, refer to the OS/2 WARP Control Program Programming Reference.
| ASN1038E | No column names or expressions were specified in the subscription columns table. |
Explanation: Column names or expressions for a copy statement must be specified.
User Response: Refer to Setting up your replication environment for more information about requirements for subscription definitions.
| ASN1039S | The Apply program plan, "<plan_name>", could not be opened. |
Parameters:
Explanation: The Apply program plan could not be opened.
User Response: Refer to the Apply for OS/390 Program Directory.
| ASN1040S | The Apply program encountered an OS/390 error. The error code is "<error_code>"; the return code is "<return_code>". |
Explanation: Execution of an OS/390 system operation failed.
User Response: Refer to your OS/390 system library information.
| ASN1041I | The Apply program was started using subsystem name: "<subsystem>". |
Explanation: This is not an error message, however, you should make sure that the displayed subsystem name is valid.
User Response: Verify that the subsystem name is valid.
| ASN1042W | There are too many invocation parameters. |
Explanation: The number of parameters you specified when you invoked the Apply program exceeds the maximum allowed.
User Response: Refer to the Capture and Apply chapter for your platform for information on the appropriate number of invocation parameters.
| ASN1043E | There is already one Apply instance running with this Apply program qualifier "<qualifier>". The error code is "<error_code>"; the reason code is "<reason_code>". |
Explanation: Verification attempt failed.
User Response: Make sure that only one instance of the Apply program is running under this user ID on this subsystem or database.
| ASN1044I | The Apply program will become inactive for "<number>" minutes and "<number>" seconds. |
Explanation: This message is for your information only.
User Response: No action is required.
| ASN1045I | The Apply program was started using database "<database>". |
Explanation: This message is for your information only.
User Response: No action is required unless this is not the intended database.
| ASN1046S | The Apply program libraries are not authorized for the Authorized Program Facility (APF). |
Explanation: The Apply program libraries must be APF authorized.
User Response: Authorize the Apply program libraries.
| ASN1048E | The execution of a copy statement failed. See the Apply trail table for full details: "<text>" |
Explanation: A copy statement could not execute. In the message, "<text>" identifies the "<copy_server>", "<copy_owner, copy_table, stmt_number>", and "<cntl_server>".
User Response: Check the APPERRM fields in the audit trail table to determine why the copy statement failed.
| ASN1049S | The Apply program encountered a system error. The error code is "<error_code>". The return code is "<return_code>". |
Explanation: Execution of a system operation failed.
User Response: Refer to the system library information for your platform.
| ASN1050E | The Apply program encountered an invalid operation while updating the target table. The error code is "<error_code>". The invalid operation to be applied is "<operation>". |
Explanation: The operation field of a row fetched from the source table is not valid.
User Response: Contact IBM Software Support.
| ASN1051E | The Apply program detected a gap between the source "<source>" table and the target table. The error code is "<error_code>". |
Explanation: The Apply program has detected that the Capture program lost change data before the Apply program could copy it. For example, the Capture program might have been cold started.
User Response: Check the control tables to determine why the gap is present. Take proper action to preserve data integrity before you reset the control table information to execute the definition again.
| ASN1052E | The Apply program could not find the ASNLOAD program. |
Explanation: The Apply program cannot find the ASNLOAD program in the current directory.
User Response: Make sure that ASNLOAD is in the directory from which you are invoking the Apply program.
| ASN1053E | The execution of the ASNLOAD program failed. The return code is "<return_code>". |
Explanation: The ASNLOAD program detected an error.
User Response: Refer to the messages files generated by the EXPORT and IMPORT utilities. (Note that these files names are different for Apply for OS/2 and Apply for AIX.)
| ASN1054S | The Apply program could not find the registration information for source owner "<src_ownr>", source table "<src_tbl>", and source view qualifier "<src_view_qual>". |
Explanation: The source table registration is incorrect or incomplete.
User Response: Drop the registration and redo it. Also make sure that the registration information is in both the register table and the pruning control table.
| ASN1055S | The Apply program could not find the prune control information for source owner "<src_ownr>", source table "<src_tbl>", source view qualifier "<src_view_qual>", target owner "<tgt_ownr>", and target table "<tgt_tbl>". |
Explanation: The source table registration is incorrect.
User Response: Drop the subscription and redo it.
| ASN1056E | The Apply program could not connect to the server due to lack of user ID/password. The error code is "<error_code>". |
Explanation: The Apply program could not find the password and user ID to connect to the server.
User Response: Make sure that the Apply program password file exists. The Apply program password file resides in the same directory from which you start the Apply program. If you are using DB2 Universal Database Satellite Edition, make sure that the password and user ID are defined to the client systems.
| ASN1057E | The Apply program could not read the password in the Apply password file. The error code is "<error_code>". |
Explanation: The Apply program found no password.
User Response: If you want to use the AUTHENTICATION=SERVER scheme, you must provide a password, as described in the Apply program section in the Capture and Apply chapter for your platform.
| ASN1058E | The Apply program could not close the password file. The error code is "<error_code>". |
Explanation: The Apply program could not close the password file.
User Response: Contact IBM Software Support.
| ASN1059E | The Apply program detected invalid syntax for line "<line>" in the password file. The error code is "<error_code>". |
Explanation: The Apply program could not recognize a line in the password file.
User Response: Correct the syntax error in the password file. See the Apply program section in the Capture and Apply chapter for your platform.
| ASN1060E | The dynamic allocation for the temporary work file failed. The error code is "<error_code>". |
Explanation: A system error was encountered during dynamic allocation.
User Response: Contact IBM Software Support.
| ASN1061E | An invalid keyword parameter was specified. The error code is "<error_code>". |
Explanation: An invalid invocation parameter was specified and ignored by the Apply program.
User Response: Correct the invocation parameter. See the Apply program section in the Capture and Apply chapter for your platform.
| ASN1063E | A subscription set cannot have more than 200 members. The error code is "<error_code>". |
Explanation: The number of subscriptions has exceeded the maximum allowed number of 200.
User Response: Remove excess members from the subscription set.
| ASN1066S | An internal Apply program error occurred. The error code is "<error_code>". |
Explanation: An internal Apply program error occurred.
User Response: Contact IBM Software Support.
| ASN1067E | The Apply program has detected update conflicts and compensated rejected transactions. See the unit-of-work table for details. The error code is "<error_code>". |
Explanation: More than one application updated the same row in a table from different locations. Some transactions have been rejected and compensated.
User Response: Refer to Unit-of-work table for details.
| ASN1068E | The Apply program has deactivated the subscription due to an RI violation. The error code is "<error_code>". |
Explanation: A referential integrity violation was detected when copying data from the source table to a replica. The Apply program has terminated and the subscription has been deactivated.
User Response: Correct the referential integrity error and reactivate the subscription.
| ASN1069E | The Apply program has detected a referential integrity violation and compensated the rejected transactions. See the unit-of-work table for more details. The error code is "<error_code>". |
Explanation: A referential integrity violation was detected when replicating data from the replica to the user table.
User Response: See the unit-of-work table for more details.
| ASN1070E | The Apply program could not lock the target table. |
Parameters:
Explanation: The Apply program could not lock the target tables before it was to check update conflicts.
User Response: Verify that all the target tables are available before restarting Apply.
| ASN1071E | The Apply program could not reposition the work file. The error code is "<error_code>". |
Explanation: The Apply program has detected an error while reading the temporary work file.
User Response: Contact IBM Software Support.
| ASN1072E | The Apply program could not find the ASNDONE program. |
Explanation: The Apply program could not find the user exit program, ASNDONE.
User Response: Verify that the ASNDONE program is located in the correct directory.
| ASN1073E | The execution of the ASNDONE program failed. The return code is "<return_code>". |
Explanation: An error occurred while calling the user exit program, ASNDONE.
User Response: Contact IBM Software Support.
| ASN1074E | The Apply program could not find the ASNDLCOPY program. |
Explanation: The Apply program did not find the ASNDLCOPY program in the current search path.
User Response: Add the ASNDLCOPY program to the search path and run the Apply program again.
| ASN1075E | The ASNDLCOPY program failed. The return code is "<error_code>". |
Explanation: The ASNDLCOPY program detected an error.
User Response: Refer to the log file that was generated by the ASNDLCOPY program for detailed information. The name of the log file is asndlxxxx.log.
| ASN1076E | The Apply program cannot read the format of the result file that was generated by the ASNDLCOPY program. |
Explanation: The result file that was generated by the ASNDLCOPY program is not in an expected format.
User Response: If you modified the ASNDLCOPY program, check that your changes are not causing the invalid format. If your changes are not the cause of the problem, check that your machine has enough space for the result file.
| ASN1077S | The Apply program encountered an invalid DATALINK column value while updating the target table. The error code is "<error_code>". |
Explanation: The DATALINK column field of a row fetched from the source table is not valid.
User Response: Contact IBM Software Support.
| ASN1097I | The Apply program stopped due to the above error. |
Explanation: The error reported previously caused the Apply program to stop.
User Response: Fix the error reported before this message.
| ASN1100I | A user has stopped the Apply program. |
Explanation: A user issued the STOP command to stop the Apply program.
User Response: No action is required.
| ASN1109I | Not all of the Jet database changes are applied due to an RI violation. |
Explanation: There was at least one change in the row-replica target list table that violates the referential integrity (RI) of the source table.
User Response: Refer to the Microsoft Jet-specific error information and error messages tables for more details. See Error information table (Microsoft Jet specific).
| ASN1110I | The Apply program created Jet database "<db_name>". |
Explanation: The target database <db_name> was created.
User Response: No action is required.
| ASN1111I | The Apply program converted Jet Database "<db_name>" to a Design Master. |
Explanation: The database that you specified is now a Design Master from which all Microsoft Jet Replicas will be created.
User Response: No action is required.
| ASN1115I | ODBC call was successful with sqlcode "<sqlcode>", sqlstate "<sqlstate>", and message "<message>". |
Explanation: The ODBC call was successful, but a message was issued. This message is for your information only.
User Response: No action is required.
| ASN1116E | ODBC call failed. sqlcode "<sqlcode>", sqlstate "<sqlstate>", and message "<message>". |
Explanation: An error occurred during the execution of an ODBC operation against either the DB2 ODBC driver or the Microsoft Jet ODBC driver.
User Response: Refer to the appropriate ODBC reference for more information.
| ASN1130E | Execution of DAO call failed. ERRCODE "<error_code>", DAO error number "<error_number>", and DAO error message "<error_message>". |
Explanation: An error occurred during a Microsoft Data Access Object (DAO) execution.
User Response: Refer to the Microsoft DAO reference for more information.
| ASN1135E | File operation failed. File name is "<file_name>", error code is "<error_code>". |
Explanation: Open, close, read, or write operations failed.
User Response: Verify that the user has authority for the file operation. Also verify that there is enough space in the system.
| ASN1207E | The subscription for "<subscription>" was not activated. |
Explanation: The selected subscription is inactive.
User Response: Either activate the subscription or select another one.
| ASN1210E | An Apply qualifier must be specified following the keyword -q. |
Explanation: You must specify an Apply qualifier following the keyword -q.
User Response: Specify an Apply qualifier following the keyword -q.
| ASN1212E | A read-only set name "<set_name>" is found following the keyword "<keyword>". |
Explanation: A read-only set name was specified following the keyword U or D.
User Response: Specify only replica for the keywords U and D.
| ASN1221I | Set "<set_name>" has been successfully refreshed with "<number>"rows at "<time>". |
Explanation: This message is for your information only.
User Response: No action is required.
| ASN1222I | Set "<set_name>" has successfully inserted "<number>" rows, deleted "<number>" rows, updated "<number>" rows at "<time>". |
Explanation: This message is for your information only.
User Response: No action is required.
| ASN1223E | The Apply program could not copy for set "<set_name>". |
Explanation: The Apply program encountered a problem while copying.
User Response: Refer to the apply trail table to determine the cause of the error.
| ASN1242E | A SQL error occurred. ERRCODE is "<error_code>", SQLSTATE is "<sqlstate>", SQLCODE is "<sqlcode>", SQLERRM is "<sqlerrm>", SQLERRP is "<sqlerrp>", table name is "<table_name>". |
Explanation: This message is for your information only.
User Response: No action is required.
| ASN1243E | There is no eligible subscription in the ASN.IBMSNAP_SUBS_SET table. |
Explanation: Either a subscription set has not been selected or the apply qualifier is invalid.
User Response: Verify the subscription names and apply qualifier.
| ASN1244E | User has not selected any set. |
Explanation: A subscription set has not been selected from the ASNMOBIL dialog.
User Response: Select at least one subscription set from ASNMOBIL dialog.
| ASN1303E | The ASNSAT program encountered an incorrect invocation keyword. The keyword is "<keyword>". |
Explanation: An unknown keyword parameter was specified.
User Response: Specify the correct keyword parameter.
| ASN1304E | The ASNSAT program terminated due to a Capture error. |
Explanation: The Capture program returned an error.
User Response: Determine the error from the Capture log file.
| ASN1305E | The ASNSAT program terminated due to an Apply error. |
Explanation: The Apply program returned an error.
User Response: Determine the error from the Apply log file.
| ASN1309E | Cannot find default control database name. |
Explanation:
User Response: Specify the control server name following the -n keyword.
| ASN1310E | The ASNSAT program encountered a system error while attempting to invoke the Capture program. Return code is "<return_code>". |
Explanation: An operating system error occurred while calling ASNCCP.
User Response: Make sure that the Capture program is in the execution path.
| ASN1311E | The ASNSAT program encountered a system error while attempting to invoke the Apply program. Return code is "<return_code>". |
Explanation: An operating system error occurred while calling ASNAPPLY.
User Response: Make sure that the Apply program is in the execution path.
| ASN1312E | The default target server, DB2DBDFT, is not set. |
Explanation: The user did not specify the target server name, and the ASNSAT program could not determine the default database name from DB2DBDFT.
User Response: Specify the target server name following the -t keyword.
| ASN1314E | An SQL error occurred while ASNSAT was getting the default Apply qualifier. SQLSTATE is "<sqlstate>", SQLCODE is "<sqlcode>". |
Explanation: The user did not specify the Apply qualifier. The ASNSAT program encountered an error while retrieving the USER special register.
User Response: Specify the Apply qualifier following the -q keyword.
| ASN1315E | Cannot connect to database server. SQLSTATE is "<sqlstate>", SQLCODE is "<sqlcode>". |
Explanation: An error occurred while attempting to connect to the target database.
User Response: Refer to your database message reference.
| ASN1316E | ASNSAT encountered an error while trying to bind. The SQLSTATE is "<sqlstate>", SQLCODE is "<sqlcode>". |
Explanation: An error occurred while attempting to auto bind.
User Response: Make sure that the bind file exists in the sqllib\bnd directory.
| ASN1317E | An SQL error occurred while ASNSAT was getting the CD_TABLE value from ASN.IBMSNAP_REGISTER table. SQLSTATE is "<sqlstate>", SQLCODE is "<sqlcode>". |
Explanation: An SQL error occurred while selecting from the register table.
User Response: Refer to your database message reference.
| ASN1318E | An SQL error occurred while ASNSAT attempted to get the DB2 node type. SQLSTATE is "<sqlstate>", SQLCODE is "<sqlcode>". |
Explanation: An error occurred while retrieving the node type configuration parameter.
User Response: Refer to your database message reference.