ASN2000-2999

ASN Message ID Message Explanation User Response

ASN2000I

 The action action_name started at time_stamp. The Q Capture server is capture_server , and the Q Capture schema is capture_schema.

This message is for your information only.

This message is for your information only. No action is required.

ASN2001I

 The action action_name started at time_stamp. The Q Apply server is apply_server, and the Q Apply schema is apply_schema.

See message text.

This message is for your information only. No action is required.

ASN2002I

 The action action_name started at time_stamp. The publication name is pub_name, the Q Capture server is capture_server, the Q Capture schema is capture_schema, and the source table, view, or nickname is table_name.

See message text.

This message is for your information only. No action is required.

ASN2003I

 The action action_name started at time_stamp. Q subscription name: name. Q Capture server: capture_server. Q Capture schema: capture_schema. Q Apply server: apply_server. Q Apply schema: apply_schema. The source table is table_name. The target table or stored procedure is table_name.

See message text.

This message is for your information only. No action is required.

ASN2004I

 The action action_name started at time_stamp. The publishing queue map name is queue_map_name, the Q Capture server is capture_server, and the Q Capture schema is capture_schema.

See message text.

This message is for your information only. No action is required.

ASN2005I

 The action action_name started at time_stamp. The replication queue map name is queue_map_name, the Q Capture server is capture_server, the Q Capture schema is capture_schema, the Q Apply server is apply_server, and the Q Apply schema is apply_schema.

See message text.

This message is for your information only. No action is required.

ASN2006I

 The action action_name ended successfully at time_stamp for the Q Capture server capture_server and Q Capture schema capture_schema.

See message text.

This message is for your information only. No action is required.

ASN2007I

 The action action_name ended successfully at time_stamp for the Q Apply server apply_server and Q Apply schema apply_schema.

See message text.

This message is for your information only. No action is required.

ASN2008I

 The action action_name ended successfully at time_stamp for the publication name pub_name, Q Capture server capture_server, Q Capture schema capture_schema, and source table, view, or nickname table_name.

See message text.

This message is for your information only. No action is required.

ASN2009I

 The action action_name ended successfully at time_stamp for the Q subscription name name. The Q Capture server is capture_server, the Q Capture schema is capture_schema, the Q Apply server is apply_server, the Q Apply schema is apply_schema, the source table is table_name, the target table or stored procedure is table_name.

See message text.

This message is for your information only. No action is required.

ASN2010I

 The action action_name ended successfully at time_stamp for the publishing queue map name queue_map_name, Q Capture server capture_server, and Q Capture schema capture_schema.

See message text.

This message is for your information only. No action is required.

ASN2011I

 The action action_name ended successfully at time_stamp for the replication queue map name queue_map_name. The Q Capture server is capture_server and the Q Capture schema is capture_schema. The Q Apply Server is apply_server and the Q Apply schema is apply_schema.

See message text.

This message is for your information only. No action is required.

ASN2018E

 The value is missing for the input parameter input_parameter.

The value for the input parameter is mandatory but it is missing. A script is not generated.

Provide a value for the mandatory parameter and rerun the action.

ASN2019E

 The value value for input parameter input_parameter is incorrect. Reason code: reason_code.

The value provided for the input parameter is not a valid value. The following values are valid for the reason code:

0

In this context, the SUBTYPE column value must be 'U' or 'B'.

1

The SLEEP_INTERVAL column value must be greater than 0 and less than 2147483647.

2

The ALL_CHANGED_ROWS column value must be 'Y' or 'N'.

3

The BEFORE_VALUES column value must be 'Y' or 'N'.

4

The CHANGED_COLS_ONLY column value must be 'Y' or 'N'.

5

The HAS_LOADPHASE column value must be 'N' or 'E' for publications.

6

The HAS_LOADPHASE column value must be 'N', 'I', or 'E' for Q Subscription.

7

The SUPPRESS_DELETES column value must be 'Y' or 'N'.

8

The MESSAGE_FORMAT column value must be 'X' for publishing queue maps.

9

The MESSAGE_FORMAT column value must be 'C' for replication queue maps.

10

The MSG_CONTENT_TYPE column value must be 'T' or 'R' for publishing queue maps.

11

The MSG_CONTENT_TYPE column value must be 'T' for replication queue maps.

12

In the IBMQREP_SENDQUEUES table, the ERROR_ACTION value must be 'I' or 'S' for publishing queue maps or replication queue maps.

13

The ERROR_ACTION column value for Q subscriptions must be 'I' , 'S' , 'Q', or 'D'.

14

The CONFLICT_ACTION column value must be 'F' , 'I' , 'D', 'S', or 'Q' for Q subscriptions.

15

The LOADTYPE parameter must be '0', '1', '2', '3', '4', or '5.'.

16

The SOURCENODE parameter must be greater than zero.

17

The TARGETNODE parameter must be greater than zero.

18

The NUM_APPLY_AGENTS parameter must be greater than 0 and less than 100.

19

The MEMORY_LIMIT parameter must be greater than 0 and less than 100.

20

The MSG_FORMAT column value for Q subscriptions must be 'C'.

21

The valid values for the STATE parameter is 'A' only.

22

The TARGET_TYPE parameter must be '1' (user table) or '5' (stored procedure).

23

The SUBNAME parameter cannot contain the semicolon character ( ; ).

24

The SENDQ or RECVQ column value cannot contain special characters or blanks.

25

The MONITOR_INTERVAL column value must be greater than 0 and less than 2147483647.

26

The MONITOR_LIMIT column value must be greater than 0 and less than or equal to 10080.

27

The TRACE_LIMIT column value must be greater than 0 and less than 2147483647.

28

The PRUNE_INTERVAL column value must be greater than 0 and less than 3600.

29

The AUTO_STOP column value must be 'Y' or 'N'.

30

The LOG_REUSE column value must be 'Y' or 'N'.

31

The LOGSTDOUT parameter must be 'Y' or 'N'.

32

The TERM parameter must be 'Y' or 'N'.

33

The STARTMODE column value must be 'COLD', 'WARMSI' or 'WARMNS'.

34

The COMMIT_INTERVAL column value must be greater than 100 and less than 600000.

35

The SIGNAL_LIMIT column value must be greater than 0 and less than 2147483647.

36

The length of the DBSPACE name is longer than 18 characters.

37

The specified option for the lock size is not valid.

38

The number of pages specified cannot be less than 0.

39

The number of header pages cannot be less than 1 or greater than 8.

40

The specified value for percent index, percent free space for data pages, or percent free space for index pages cannot be less than 0 or greater than 99.

41

The value for the DBSPACE name is not valid.

42

The parameter loadphase must be 'N' for all target objects that are not tables.

43

Targets that are not tables (such as nicknames and stored procedures) cannot be loaded. Therefore, the parameter HAS_LOADPHASE must be 'N'.

44

The value for the input parameter PARALLEL SENDQS cannot be greater than 4 or less than 2.

45

The SYNCHINTERVAL value should be within the range of 100 to 3000.

46

The BEFORE_VALUES column value must be 'Y' for delimited messages.

Provide a valid value for the input parameter, and rerun the action.

ASN2020E

 The value of the input parameter input_parameter is too long. The length of the value value exceeds the maximum allowed limit maximum_limit.

See message text.

Specify a valid value for the input parameter.

ASN2021E

 The action ended in error. An internal error occurred. Return code return_code.

The specified action cannot be performed because of an internal or a run-time error.

Contact IBM Software Support. Report the return code that was returned in the message. Provide an Analyzer report.

ASN2022E

 The action ended in error. An SQL error was encountered. SQL message is sql_message.

An error occurred during the execution of an SQL statement.

Refer to your database message reference for SQL.

ASN2023E

 The database platform platform, version version on server server_alias is not supported.

Q Replication and event publishing are not supported on the specified platform, version, or release.

See the system requirements page on the replication technical support Web site for details about supported platforms, versions, and releases.

ASN2050E

 The receive queue queue_name specified for the replication queue map queue_map_name is already used by another replication queue map at the Q Apply server server_alias and the Q Apply schema apply_schema.

The receive queue can be used only once for one replication queue map and under a single Q Apply schema.

Provide a different receive queue name that is not being used by any other replication queue map for this Q Apply schema, and rerun the action.

ASN2051E

 Control tables already exist at the given Q Capture server for Q capture schema capture_schema.

At least one Q Capture control table already exists under the given schema at this server. No script is generated.

Rerun the 'Create Capture Control Tables' action under a different Q Capture schema.

ASN2052E

 Control tables already exist at the given Q Apply server for Q Apply schema apply_schema.

At least one Q Apply control table already exists under the given schema at the provided server. No script is generated.

Rerun the 'Create Apply Control Tables' action under a different Q Apply schema.

ASN2053E

 No control tables were found for Q Capture schema capture_schema.

No control tables exist on the Q Capture server for the specified Q Capture schema. If the action 'Drop Capture Control Tables' was issued, no script is generated to drop the control tables. If any other action, such as 'Create publication', was issued, then the control tables could not be retrieved from the database under the specified Q Capture schema and a script for the action is not generated.

Issue the action again for the appropriate Q Capture server and Q Capture schema.

ASN2054E

 No control tables were found for Q Apply schema apply_schema.

No control tables exist on the Q Apply server for the specified Q Apply schema. If the action 'Drop Apply Control Tables' was issued, no script is generated to drop the control tables. If any other action, like 'Create Q Subscription' was issued, then the control tables could not be retrieved from the database under the specified Q Apply schema and a script for the action is not generated.

Issue the action again for the appropriate Q Apply server and Q Apply schema.

ASN2055I

 The replication control table table_name was not found and was not dropped.

The 'Drop Q Capture control tables' or 'Drop Q Apply control tables' action was issued and the control table was missing. The script will not generate the appropriate DROP statement for that control table.

This message is for your information only. No action is required.

ASN2056W

 At least one row was found in the control table table_name. If you choose to drop this control table, any replication definitions stored in the table will also be dropped.

A script was generated to drop the specified control table, but that table is not empty. If you run the script, replication control information that is in the table will be deleted and your existing publications or Q subscriptions will be affected.

Determine what would happen to your publications or Q subscriptions if you dropped the control table. Run the generated script only if the result is acceptable to you.

ASN2057W

 The table space tablespace_name already exists at the given server. The control tables will be created in this table space.

The control tables are created in recommended table spaces by default if you do not override the default and specify other table spaces. In this situation, the recommended table space already exists, so the control tables will be created in an existing table space.

Modify the script to specify a different table space if you do not want to create the tables in the existing table space. No action is required if you want the control tables to be created in the existing table spaces.

ASN2058E

 The Q Capture control table table_name was not created in table space tablespace_name in database logicaldb_name because the locksize is locksize. This control table must be created in table space with locksize expected_locksize.

On the z/OS platform, some control tables require a table space with row locksize, while others require a table space with page locksize. The table space selected for the control table does not have the appropriate locksize.

Issue the 'Create the Q Capture control tables' again using table spaces with the appropriate locksize.

ASN2059E

 The Q Apply control table table_name was not created in table space tablespace_name in database logicaldb_name because the locksize is locksize. This control table must be created in table space with locksize expected_locksize.

On the z/OS platform, some control tables require a table space with row locksize, while others require a table space with page locksize. The table space selected for the control table does not have the appropriate locksize.

Issue the 'Create the Q Apply control tables' again using table spaces with the appropriate locksize.

ASN2075E

 The object object_name of type object_type exists at the specified server and under the specified Q Capture schema.

Duplicate values for the specified type are not allowed in the control tables for the same Q Capture schema. No script is generated.

Provide a different name for the object that is unique for the Q Capture schema, and rerun the action.

ASN2076E

 The send queue object sendqueue_name specified for publishing queue map queue_map_name is already used by another publishing queue map at the Q Capture server server_alias and the Q Capture schema capture_schema.

The send queue can be used only once for one publishing queue map and under a single Q Capture schema.

Provide a different send queue name that is not being used by any other publishing queue map for the Q Capture schema, and rerun the action.

ASN2077E

 The object object_name of type object_type does not exist at the server capture_server for the Q Capture schema capture_schema.

The action was invoked on a Q subscription whose catalog definitions were not found in the Q Capture control tables.

Drop the specified object from the Q Apply server, and if needed, recreate.

ASN2078E

 The object object_name of type object_type does not exist at the server apply_server for the Q Apply schema apply_schema.

The action was invoked on a Q subscription whose catalog definitions were not found in the Q Apply control tables.

Drop the specified object from the Q Capture server, and if needed, recreate.

ASN2081E

 The table table_name cannot be published. Reason code: reason_code.
The table is not supported for publication. No script is generated. The following values are valid for the reason code:
0
The provided source table is a DB2 catalog table. Publishing of changes from system catalog tables is allowed only if the Q Capture program runs on z/OS.
1
The Q Capture server is on a z/OS platform and the source table is defined with an EDITPROC option, but DB2 for z/OS is not at the correct level.
2
The Q Capture server is on a z/OS platform and the source table is defined with a Valid proc option.
3
The source table has one or more LOB columns but there is no uniqueness defined.
4
No columns in the source table were selected for publication.
5
No key columns could be derived for the published columns at the source table.
Review the reason codes in the explanation, and take the appropriate action:
0
Provide a source table other than a DB2 catalog table and rerun the action.
1
DB2 for z/OS source tables that are defined with an edit routine (EDITPROC) to provide additional data security are supported. To use these tables as sources, the DB2 subsystem that contains the tables must be at Version 8 with APAR PK13542.
2
Provide a different source table that is not defined with the Valid proc option and rerun the action.
3
Create a unique database property on any one of the source columns that is subscribed other than a LOB column, and then rerun the action.
4
Select at least one column in the source table and rerun the action.
5
Specify the key columns and rerun the action.

ASN2082E

 The column tablename-columnname of data type datatype cannot be included in the publication. Reason code: reason_code.

The provided column is not supported by publications. The following values are valid for the reason code:

0

The data type of the column is not supported for publication.

1

The maximum number of published LOB columns was exceeded for this table.

2

Columns of LOB data type cannot be part of the key definition of a table.

Review the reason codes, provide a different column name in the publication, and rerun the action.

ASN2083E

 The Q subscription name cannot be created because it already exists under the specified Q Capture or Q Apply schema.

See message text.

Provide another Q subscription name that does not already exist at the server and rerun the action.

ASN2084E

 The object objectowner.objectname of type object_type exists at the specified server and under the specified Q Apply schema.

A catalog definition already exits in the control tables for the provided object name and Q Apply instance. Duplicate values for this type are not allowed in the same Q Apply instance.

Provide a different name for the object and rerun the action.

ASN2086E

 The stored procedure storedproc_owner.storedproc_name cannot be used by the associated Q subscription. Reason code: reason_code.
The stored procedure is not valid. No script is generated. The following values are valid for reason code:
0
The stored procedure has no parameters.
1
The first parameter in the stored procedure must be 'OPERATION'.
2
The second parameter in the stored procedure must be 'SUPPRESSION_IND'.
3
The third parameter in the stored procedure must be 'SRC_COMMIT_LSN'.
4
The fourth parameter in the stored procedure must be 'SRC_TRANS_TIME'.
5
The 'INOUT' attribute value of the OPERATION parameter is not equal to 'INOUT'.
6
The 'INOUT' attribute value of the 'SUPPRESSION_IND', 'SRC_COMMIT_LSN', or 'SRC_TRANS_TIME' parameter is not equal to 'IN'.
7
The stored procedure must contain at least five parameters: four required parameters ( 'OPERATION', 'SUPPRESSION_IND', 'SRC_COMMIT_LSN', 'SRC_TRANS_TIME') and at least one additional parameter.

Review the reason codes in the explanation, provide a valid stored procedure and rerun the action.

ASN2087E

 The stored procedure parameter owner.name.parameter cannot be included in the Q subscription. Reason code: reason_code.
The stored procedure parameter is not supported by the Q subscription. No script is generated. The following values are valid for the reason code:
0
The parameter's 'INOUT' attribute value is not equal to 'IN'.
1
The parameter is a special prerequisite parameter required by the Q Apply program and this parameter should not take part in the Q subscription.
2
The parameter is a before-value parameter, and before-value parameters cannot be mapped to a source column in the Q subscription.
3
The parameter is part of the key but the corresponding before-value parameter does not appear in front of this parameter in the stored procedure definition.

Review the reason codes in the explanation. Either modify the parameter definition of the stored procedure or provide a stored procedure with supported parameters and rerun the action.

ASN2088E

 The column or stored procedure parameter targetowner.targetname.name cannot be added to the Q subscription. Reason code: reason_code.
The column or the stored procedure parameter is not supported or not valid. No script is generated. The following values are valid for the reason code:
0
The target is a stored procedure and the parameter should exist in the procedure definition before adding the parameter to the Q subscription.
1
The column is already participating in the Q subscription.
Review the reason codes in the explanation, and take the appropriate action:
0
Modify the definition of the stored procedure to include this parameter in the stored procedure and rerun the action.
1
Verify the column name and provide a different column name not already participating in the Q subscription.

ASN2100E

 The length length of the string string for parameter parameter in the database object object_name of type object_type at the server server_alias is longer than the maximum limit max_limit.

This type of database object requires a shorter string than the one that was supplied for the parameter.

Refer to the SQL reference for the appropriate database to find the valid length of the string, and provide the correct name length.

ASN2101E

 The database object object_name of type object_type already exists at server server_alias.

The database object cannot be created because there is already a database object of the same type with the same name.

Provide a name for that object that does not already exist in the database and reissue the task.

ASN2102E

 The database object object_name of type object_type does not exist at the server server_alias.

The database object does not exist in the database catalog. There is no information to retrieve for this object, and it cannot participate in the publication or Q subscription.

Ensure that you specify the correct name of an existing database object and run the task again.

ASN2104E

 The row size row_size of all columns in the database object object_name of type object_type at server server exceeds the allowed maximum limit max_limit.

The combined row size of all the columns in the specified object cannot exceed the limit. This object cannot be created or altered.

Either assign a table space with a larger page size for this object, or specify fewer columns or shorter columns for this object. Refer to the database specific SQL reference for details on the row size limits of database objects.

ASN2105E

 The number of columns num_columns in the database object object_name of type object_type at server server_alias exceeds the database limit max_limit.

The number of columns that a database object (table or index) can contain depends on the database platform, but it cannot exceed a predefined maximum number. No script is generated to create or alter the object.

Redefine the database object with the appropriate number of columns. Refer to the SQL Reference for the appropriate database to find the valid number of columns for the database object.

ASN2106E

 The page size page_size1 for the table space tablespace_name at server server_alias does not match the page size page_size2 of the table space bufferpool buffer_pool. Reason code: reason_code.
The page size for the table space must match the page size of the bufferpool that is assigned to this table space. The following values are valid for the reason code:
0
The bufferpool specified was assigned to the table space and the page size obtained from the bufferpool is not equal to the page size specified for the table.
1
Bufferpool information is not specified for the table space and so the default bufferpool is selected for this table space. But the page size of the default bufferpool does not match the page size of the table space.
Check the input and take the following actions:
  • If the bufferpool information is specified in the table space, modify the page size of the table space to match the page size of the bufferpool and rerun the action.
  • If the default bufferpool was used for the table space, modify the page size of the table space to match the page size of the default bufferpool and rerun the action.

ASN2118E

 The database object object_name of type object_type1 cannot be deleted because dependent objects of type object_type2 still exist at server server_alias.

The database object cannot be deleted because one or more objects exist at the specified server that are dependent on the existence of this object.

Check the provided object name and issue the task again.

ASN2119E

 The parameter parm_name is missing for the database object object_name of type object_type at server server_alias.

The parameter value is required for the specified object.

Check the input and provide a valid value for the required parameter.

ASN2120E

 The parameter parm_name is not supported for the database object object_name of type object_type at server server_alias.

See message text.

Check the input and ensure that no value is specified for the parameter. Refer to the database specific SQL reference for further details.

ASN2121E

 The parameter parm_name cannot be used in an update operation for the database object object_name of type object_type at server server_alias.

You cannot update the value of this parameter.

Check the input and ensure that no value is specified for the parameter.

ASN2122E

 The value value for the parameter parm_name of the database object object_name of type object_type at server server_alias contains the invalid character char.

The values for the parameter can only contain certain characters.

Remove the invalid character from the provided value. Refer to the database specific SQL reference to find out which characters are valid for the provided parameter.

ASN2123E

 The value value1 for the parameter parm1 of the database object object_name of type object_type conflicts with the value value2 for parameter parm2.

The values provided for the specified parameters cannot coexist at the server.

Modify the input to reflect a valid value combination. Refer to the database specific SQL reference to find out which value combinations are valid.

ASN2124E

 The value value for the parameter parm of the database object object_name of type object_type at server server_alias is higher than the maximum value allowed max_value.

The provided value is too high. Only values lower than or equal to the specified maximum are supported.

Check the input and provide a lower number. Refer to the database specific SQL reference for the valid range of values.

ASN2125E

 The value value for the parameter parm of the database object object_name of type object_type at server server_alias is lower than the minimum value allowed min_value.

The provided value is too small. Only values higher than or equal to the specified minimum value are supported.

Check the input and provide a higher number. Refer to the database specific SQL reference for the valid range of values.

ASN2126E

 The database object object_name1 of type object_type1 at server server_alias contains duplicate objects of type object_type2 of the name object_name2.

The duplicate objects are not allowed.

Check the input and make sure each object is provided only once.

ASN2127E

 The database object object_name of type object_type1 at server server_alias contains num_objects objects of type object_type2 but the maximum limit allowed is max_limit.

Too many objects were specified for the provided parameter.

Check the input and reduce the number of these database objects to the maximum.

ASN2128E

 The column col_name of data type datatype cannot be used in the database object object_name of type object_type at the server server_alias. Reason code: reason_code.
The column is not supported in the specified database object. The following values are valid for the reason code:
0
The data type of the column is not valid.
1
The column cannot be used in the database object.
2
The column length is too long.
3
The data type of the referencing column does not match the data type of the referenced column in a foreign key constraint.

Review the reason codes listed in the explanation. Choose another column or choose another database object for this column.

ASN2129E

 A conflict exists between property prop_name of type prop_type and another property in the database object object_name of type object_type at server server_alias.
The object was not created or updated because conflicting properties were found and they cannot coexist. The following values are valid for the reason code:
0
You are trying to create the object and you specified a property that conflicts with another property specified in the same session.
1
You are trying to update the object and you specified a property that conflicts with another property specified in the same session.
2
You are trying to update the object and you specified a property that conflicts with an existing property in the object.

If both the properties are new and are specified, then specify only one of the properties and issue the task. If one of the properties already exists in the object, then do not specify the new property in the object.

ASN2130E

 The database object object_name of type object_type cannot be created or updated because column column_name does not exist in the table table_name at server server_alias.

See message text.

Check the input and provide another name for the column that exists in the table.

ASN2131E

 The column column_name in the target table table_name cannot be used for Q Replication because the column is read-only.

See message text.

Choose another target column. Refer to the database specific SQL reference to determine which columns cannot be updated.

ASN2132E

 The Column column_name in the target table table_name is not mapped to a source column for replication. Because this column is not nullable and it does not have a default value, the Q subscription cannot be created or updated.

Any columns in a target table that do not participate in the Q subscription must be either nullable or not null with default. At least one column in the target table that you did not select for the Q subscription does not meet the criteria.
Take one of the following actions:
  • Map the specified column in the target table to a column in the source table so that the column participates in the Q subscription.
  • Enable the nullability property for the target column.
  • Specify a default value for this column.

ASN2135E

 The data type target_datatype of the target column target_colname is not compatible with the data type source_datatype of the source column source_colname.

The values of the source column cannot be applied to the target column because the data types of the columns are not compatible.

Take one of the following actions:

  • If the target exists and is a user table, change the column mapping to a different column that has a compatible data type.
  • If the target exists and is a nickname, alter the data type of the nickname column to match the source column data type.
  • If the target table does not exist, modify the data type of the target column so that it is compatible with the source column.

ASN2136W

 The attribute of the target column target_column and the attribute of the source column source_column do not match. Reason code: reason_code.
A difference between the values of the source and target column for the same attribute was detected. A script for creating or updating the Q subscription is generated. The following values are valid for the reason code:
0
The source column is nullable whereas the target column is not nullable.
1
The source column in not nullable whereas the target column is nullable.
2
The encoding schemes for the source column and the target column are different.
3
The source column has default values and the target column does not have default values.
4
The source column does not have default values and the target column has default values.

Change the column mapping or column properties if the difference can cause potential problems. If the difference is acceptable, no action is necessary.

ASN2137W

 The compatibility between the source column source_column and the target column target_column exists only for certain values of the source column. Reason code: reason_code.
The values of the source column cannot be always applied to the target column. A script to create or update the Q subscription is still generated. The following values are valid for the reason code:
0
The source column can contain null values, but the target column does not allow null values. Null values in the source column cannot be applied to the target column.
1
The source column data type is either a CHAR or a VARCHAR, whereas the target column data type is a DATE, TIME, or a TIMESTAMP. Any string values in the source column that are not a valid representation of a time, date, or timestamp cannot be applied to the target column.
2
The source column contains numbers that are outside of the range of values that the target column supports.
3
The length of the VARCHAR data type of the source column is longer than the length of the CHAR or VARCHAR data type of the target column.
Review the reason codes in the explanation, and take the appropriate action:
  • If the target table exists, change the column mapping.
  • If the target table does not exist, change the column properties.
  • Check the source and the target column. If the source column will only contain values that are allowed for the target column, no action is required.

ASN2138W

 The values of the source column source_column of data type source_datatype will potentially lose fractional digits when replicated to the target column target_column of data type target_datatype.

There can be potential loss of data between the source and the target columns because the target column data type definition indicates that the precision allowed in the column is much lower than that of the source column.
Take one of the following actions:
  • If the target table exists, change the column mapping.
  • If the target table does not exist, change the column properties.
  • Check the source and the target column. If the values will never exist in the source column or if the truncation is acceptable in the target column, no action is necessary.

ASN2139E

 The value value for the parameter parm in the database object object_name of type object_type at server server_alias is not valid because it is not equal to one of the following values: valid_values.

See message text.

Check the input and provide a value from the list of values specified.

ASN2140E

 The value value for the parameter parm1 in the database object object_name of type object_type at server server_alias is not a multiple of factor.

The values for the specified parameter in the database object must be multiples of the provided factor.

Check the input and provide a value that is a multiple of the specified factor.

ASN2141E

 The value value for the parameter parm of the database object object_name of type object_type at server server_alias is not valid.

The value for the specified parameter is not valid on the database platform.

Check the input and provide another value. Refer to the database specific SQL reference for valid values for this parameter.

ASN2142E

 The attribute parm is not valid for LOB table space tablespace_name on server server_alias.

The following attributes are not valid for a LOB table space: PCTFREE, TRACKMOD, COMPRESS, SEGSIZE.

Remove the attributes that are not valid for LOB table space (PCTFREE, TRACKMOD, COMPRESS, SEGSIZE), and rerun the action.

ASN2144E

 The table table_name at the server server_alias was not created or updated because the definition of the foreign key foreign_key is not valid. Reason code: reason_code.
No script is generated. The following values are valid for the reason code:
0
The number of referencing columns is lower than the referenced columns.
1
The number of referencing columns is higher than the number of referenced columns.

Check the input and ensure that the number of referenced columns matches the number of referencing columns.

ASN2145E

 The column name column_name for the table table_name at server server_alias was specified more than once in the same session.

See message text.

Check the input and remove the duplicate name.

ASN2146E

 The publication or Q subscription cannot be created or updated because required information is missing. Reason code: reason_code.

No script is generated. The following values are valid for the reason code:

0

The source table information is missing.

1

The target table information is missing.

2

No source columns were selected.

3

No target columns were selected.

Check the input and provide values for the specified parameters.

ASN2147E

 The publication or Q subscription cannot be updated or created because column column_name does not exist in table targetowner-targetname at server server_alias. Reason code: reason_code.

No script is generated. The following values are valid for the reason code:

0

The column does not exist in the source table.

1

An existing target table was provided but the specified column does not exist in the target table.

Check the input and select columns that exist in the source or target table.

ASN2148E

 The publication or Q subscription cannot be created or updated because column column_name in table table_name at server server_alias cannot be a replication key column. Reason code: reason_code.

No script is generated. The following values are valid for the reason code:

0

The column that is selected for the key column is not part of the list of selected source columns.

1

The column that is selected for the key column is not part of the list of selected target columns.

Check the input and choose key columns that are selected as the source or the target columns.

ASN2149E

 The target table_name of type target_type is read-only.

The specified database object cannot be a target because it cannot be updated.

Choose another database object as a replication target. Refer to the database specific SQL reference for information about which database objects can be updated.

ASN2150E

 The Q subscription cannot be created because the replication target key is missing. Reason code: reason_code.
No script is generated. The following values are valid for the reason code:
0
User input is missing for the target key.
1
The target table does not exist and the source table does not contain any unique database properties for the selected source columns.
2
Both source and target tables exist, but they do not contain any unique database properties on the selected target and source columns.

Check the input and make sure the appropriate columns are selected as part of the target key.

ASN2151E

 The source column source_column does not have a mapped target column.

The action create or update Q Subscription cannot be completed because the specified source column does not have a target column to be mapped.

Check the source column and verify that it is mapped to a valid target column and rerun the action.

ASN2152E

 The target column target_column does not have a mapped source column.

The action create or update Q subscription cannot be completed because the specified target column does not have a source column to be mapped.

Check the target column and verify that it is mapped to a valid source column and rerun the action.

ASN2153E

 The option option that was provided is not supported for the platform platform on server server.

The ASNCLP option is not supported for the server platform.

Check the syntax and provide the correct options.

ASN2154E

 The specified environmental value is not relevant in this particular context. The token token will be ignored.

See message text.

Check the syntax and provide the correct values.

ASN2155E

 The publication or replication queue map queue_map_name cannot be deleted because it is used by one or more publications or Q subscriptions, respectively. Reason code: reason_code.
The following values are valid for the reason code:
0
You are trying to delete a publishing queue map but there exist one or more publications that depend on this queue map.
1
You are trying to delete a replication queue map but there exist one or more Q subscriptions that depend on this queue map.
Review the reason codes in the explanation, and take the appropriate action:
0
If you want to delete the publications that use the publishing queue map, delete them first and then delete the publishing queue map.
1
If you want to delete the Q subscriptions that use the replication queue map, delete them first and then delete the replication queue map.

ASN2156W

 The uniqueness of the replication key values is not enforced at the source table, at the target table, or at both. Reason code: reason_code.

The following values are valid for the reason code:

0
The uniqueness of the replication key is enforced at the target table, but not at the source table.
1
The uniqueness of the replication key is enforced at the source table, but not at the target table.
2
The uniqueness of the replication key values is not enforced at both the source and target tables.

Review the reason codes in the explanation, and take the appropriate action:

0
Make sure that the application on the source table only generates unique values for the source columns that are mapped to the replication target key columns.
1
Make sure that the application on the target table only generates unique values for the target columns that were selected as replication target key columns.
2
Take the actions that are described for reason codes 0 and 1.

ASN2157I

 No script was generated because no action was required.

The action is not required because the objects in the database already reflect the required state.

This message is for your information only. No action is required.

ASN2158E

 No objects of type object_type were found for the provided query query. The command will be ignored.

In the command line interface, you specified a query to retrieve multiple objects that all participate in an action (such as Create Publication or Create Q Subscription). The query did not return any objects. No script is generated for the create, update, or delete action.

Redefine the query so that it can return at least one object of the specified type and reissue the command.

ASN2159E

 The value value provided for the option option cannot be used in conjunction with token.

In the ASNCLP program, some parameters are not supported in certain scenarios. For example, if the subscription specifies to create a new target table, then the TYPE value cannot be STOREDPROC because there is no support for creating stored procedures.

No script is generated.

Refer to the ASNCLP documentation for a list of valid combinations for the keywords.

ASN2160E

 The object object of type type cannot be created at server server because the logical database was not specified.

The logical database must be specified in order to create the specified object type on a z/OS platform.

Specify a value for the logical database and rerun the action.

ASN2161E

 The table table_name at server server cannot be created or updated because the column column_name is not valid. Reason code: reason_code.
The following values are valid for the reason code:
0
The GRAPHIC data type is not supported for ASCII or EBCDIC table spaces.
1
The column encoding scheme "FOR MIXED DATA" is not supported for ASCII or EBCDIC table spaces.
2
The GRAPHIC data type is not supported at the specified server.

Specify a UNICODE table space for this table and rerun the action.

ASN2162W

 The uniqueness of the columns of the unique constraint or index name in the target table table_name at server server is not enforced in the source table table_name at server server.

If uniqueness for one or more of the replicated columns is enforced at the target table but not at the source table, then the source column value combinations that violate this uniqueness cannot be replicated to the target. Data in the source table cannot be applied to the target table.

If all unique database constraints or indexes at the target table cannot be violated by column value combinations from the source table, no action is necessary. Otherwise, do not run the script that was generated. Instead, reconsider dropping the unique constraint or index at the target table and run the action again.

ASN2163E

 A script to create or update the Q subscription was not generated. The source table is table_name. The target table is table_name. Reason code: reason_code.
The following values are valid for the reason code:
0
The target table does not exist and the source table does not have a unique key to be used for new target table.
1
The reason differs depending on the target type:
Target tables
The target table exists and neither the target table nor the source table has a unique index or primary key.
Stored procedure targets
The stored procedure does not have the correct number of parameters for the key columns. Two stored procedure parameters are required for each key column at the source: one for the before value of the key and one for the after value. The parameter for the before value must come before the parameter for the after value. The before-value parameter must begin with an X.
2
An automatic index could not be derived for the target table.

Review the reason codes in the explanation. Modify the source table definition, the target table or stored procedure definition, or both. Reissue the action.

ASN2164E

 The column tablename.columnname of data type datatype cannot be included in the Q subscription. Reason code: reason_code.
The following values are valid for the reason code:
0
The data type of the column is not supported for Q subscription.
1
The maximum number of subscribed LOB columns was exceeded for this table.
2
The target is a federated server and write access to a LOB data type for the federated data source is not permitted.

Review the reason codes, provide a different column name in the Q subscription, and rerun the action.

ASN2165E

 The properties of the queue map queue_map_name cannot be updated because its associated source|target database or subsystem name was not added to the Replication Center object tree.

Before you can change the properties of a publishing or replication queue map, you must add both the source and target servers that are specified for the queue map to the Replication Center.

Use the Add Q Capture Server or Add Q Apply Server wizards to add the missing server to the Q Capture Servers or Q Apply Servers folder in the object tree.

ASN2200E

 The Q Apply schema apply_schema or the Q Capture schema capture_schema for server server could not be used for multidirectional replication.

On each server that participates in multidirectional replication, the Q Apply and Q Capture control tables must have the same schema.

Make sure that the Q Apply control tables and the Q Capture control tables have the same schema name and that they exist on the same server that you are using for multidirectional replication.

ASN2201E

 In the IBMQREP_SUBS table for Q Capture schema schema_name, the values in the SOURCE_NODE column are not equal to each other.

There are one or more Q subscriptions in the Q Capture control tables for the given schema that contain different values for the SOURCE_NODE field. In multidirectional replication, the rows in the SOURCE_NODE column must contain the same value.

The report log generated by ASNCLP contains details about the Q subscription that failed.

Verify that all the SOURCE_NODE values for the Q subscriptions are the same in the IBMQREP_SUBS table.

ASN2202E

 One or more Q subscriptions (SUBTYPE subtype) cannot be created because one or more reported errors were not corrected.

The Q subscriptions cannot be created for multidirectional replication because they are not valid. Refer to the error message given for each Q subscription.

Fix the invalid Q subscriptions and try creating them again.

ASN2203E

 The Q subscription name name is not unique for the Q Capture schema capture_schema on server server for multidirectional replication.

The same name must not be provided for multiple Q subscriptions when setting up a multidirectional replication configuration. For each instance of the Q Capture program, all Q subscription names must be unique. Because the name of the Q subscription is stored at both the source and target server, be sure that the name is compatible with the code pages for both the source and target servers.

Make sure that each Q subscription name is unique.

ASN2204E

 The table table_name is on server server, but the Q Apply and Q Capture schemas schema were not found on that server.

The Q Capture and Q Apply control tables with the given schema were not found on the same server as the table that you are replicating. In multidirectional replication, the Q Capture and Q Apply control tables must be on the same server as the replicated table and they must use the same schema name.

Ensure that the table and the Q Apply and Q Capture control tables that it uses for multidirectional replication are on the same server.

ASN2205W

 Q subscription namefor Q Apply schema apply_schema on Q Apply server server is not valid and was not created as part of the mass operation.

When creating multiple Q subscriptions at one time for unidirectional replication, if one or more of the Q subscriptions are not valid they are not created; however, the rest of the Q subscriptions are created if they are valid.

Correct the Q subscriptions that were not valid and then create them.

ASN2206E

 The connection information provided for Q Apply schema and Q Capture schema source_schema on server server to Q Apply schema and Q Capture schema target_schema on server server points to itself.

In multidirectional replication, the Q Apply schema and the Q Capture schema at the Q Apply server (source) cannot also be used as the Q Capture server (target).

Make sure that the schema name and server for the Q Apply and Q Capture tables at the Q Apply server are different from the schema name and server for the Q Apply and Q Capture tables at the Q Capture server.

ASN2207E

 The replication queue map queue_map_name is not valid for setting up a connection from the source Q Apply and Q Capture schema source_schema on the Q Capture server server to the target Q Apply and Q Capture schema target_schema on the Q Apply server server.

This replication queue map does not match the specified schemas that are used for multidirectional replication.

Ensure that the replication queue map maps from the specified Q Capture control tables to the specified Q Apply control tables.

ASN2208E

 Connection information was not provided for the SUBGROUP subgroup.

The Q subscription group must have all required information defined before it can proceed with any CREATE, ALTER. or DELETE operations.

Ensure that all of the replication queue maps are provided between the source and target tables.

ASN2209E

 The connection information exists for SUBGROUP subgroup and it cannot be overwritten.

Once you define connection information for a Q subscription group, you cannot change it.

Do not give connection information for a Q subscription group more than once.

ASN2210E

 A Q subscription with the SUBGROUP name subgroup does not exist on the Q Capture server server using Q Apply and Q Capture schema schema.

The Q subscription group information could not be found.

Make sure that there is at least one Q subscription on the Q Capture schema for the SUBGROUP name.

ASN2211E

 No Q subscriptions exist for the reference table table_name for the SUBGROUP subgroup using Q Apply and Q Capture schema schema on server server.

See message text.

Make sure that there is a Q subscription of SUBTYPE 'P' (peer-to-peer) or 'B' (bidirectional) on the Q Capture schema that uses the given reference table as a source.

ASN2212E

 An internal inconsistency was detected. Reason code: reason_code
The Q subscription group must be synchronized with the persistent information on the database before being used. The following values are valid for the reason code:
0
The Q subscription group already exists but it was not synchronized, or it is not in a synchronized state.
1
Connection information between the nodes was missing.

Contact IBM Software Support. Provide an Analyzer report.

ASN2213E

 Replication queue map queue_map_name was specified with duplicate source and target information: Q Apply schema apply_schema on Q Apply server apply_server, and Q Capture schema capture_schema on Q Capture server capture_server.

A replication queue map with duplicate source and target information was specified. Replication queue maps must be unique between the connections they form. For example, the first connection is arbitrary. The second connection must share one end with either end of the first connection. The third connection must share one end with one of the three points formed by the previous two connections.

Make sure that the replication queue map specified is unique to the Q Apply server and the Q Capture server.

ASN2214E

 Replication queue map queue_map_name between Q Apply schema apply_schema on Q Apply server apply_server and Q Capture schema capture_schema on Q Capture server capture_server does not connect to any of the replication queue maps previously specified in the connection information.

The replication queue maps must be connected to each other. Each replication queue map must share a Q Capture or Q Apply schema with any of the previously specified replication queue maps.

Specify the replication queue map such that it shares a Q Capture or Q Apply schema with any of the previously specified replication queue maps.

ASN2215E

 The maximum number of Q Apply and Q Capture schema pairs allowed for a peer-to-peer Q subscription group was exceeded. The maximum number of pairs allowed is max_limit.

See message text.

Reduce the number for Q Apply and Q Capture schema pairs used in this configuration for peer-to-peer replication.

ASN2216E

 Q subscriptions of SUBTYPE subtype can be assigned only to a Q subscription group with other Q subscriptions of the same SUBTYPE.

Q subscriptions of SUBTYPE 'P' (peer-to-peer) cannot be added to a bidirectional replication configuration, and Q subscriptions of SUBTYPE 'B' (bidirectional) cannot be added to a peer-to-peer replication configuration.

When adding Q subscriptions to a SUBGROUP, ensure that the Q subscriptions have the same SUBTYPE as others in the SUBGROUP.

ASN2217E

 The pair of Q Apply and Q Capture schemas from which each Q subscription originates was not specified. The attributes for the two Q subscriptions cannot be updated for bidirectional replication.

When setting up bidirectional replication, you can specify different attributes for each of the two Q subscriptions. To do so, you must specify from which Q Apply and Q Capture schema each Q subscription originates.

To assign attributes to a Q subscription when setting up bidirectional replication, specify the Q Apply and Q Capture schema pair from which the Q subscription originates.

ASN2218E

 An internal inconsistency was detected. Reason code: reason_code.
The Q subscriptions are not synchronized with the persistent information on the database to perform an UPDATE or DELETE operation. The following value is valid for the reason code:
0
The SUBGROUP already exists but was not synchronized, or it is not in a synchronized state.

Contact IBM Software Support. Provide an Analyzer report.

ASN2219E

 The number of Q Apply and Q Capture schema pairs schema has exceeded the number allowed for SUBGROUP subgroup with Q subscriptions of SUBTYPE subtype.

The Q subscription group configuration limits the number of Q Apply and Q Capture schema pairs. Bidirectional replication allows only two Q Apply and Q Capture schema pairs per SUBGROUP.

Make sure that the number of Q Apply and Q Capture schema pairs is less than or equal to the maximum allowed for that SUBTYPE.

ASN2220E

 There are not enough Q Apply and Q Capture schema pairs schema for SUBGROUP subgroup with Q subscriptions of SUBTYPE subtype. The minimum number of pairs required is number.

See message text.

Make sure that the number of Q Apply and Q Capture schema pairs is equal to the minimum allowed for that type of Q subscription.

ASN2221E

 The connection information is not valid for this SUBGROUP subgroup for SUBTYPE subtype.

Bidirectional and peer-to-peer replication require that all servers are connected to each other.

Validate the connection information provided for this SUBGROUP and SUBTYPE and fix any problems that prevent all servers from connecting to each other. Then recreate the Q subscriptions.

ASN2222E

 The number number of attribute type object_type on table table_name on server server does not match the number number of object type object_type on table table_name on server server.

The number of columns, unique indexes, primary keys, foreign keys, unique keys, and check constraints must be the same for the source and the target tables that participate in multidirectional replication configurations.

Either change the definition of the specified attribute in the source or the target table so that the number of attributes match, or choose a different combination of source and target tables.

ASN2224E

 The object object of type object_type on table table_name on server server does not match an object on table table_name on server server.

The attribute must be the same for the source and the target tables that participate in multidirectional replication configurations.

Either change the definition of the specified attribute in the source or the target table so that it matches the attribute on the other table, or choose a different combination of source and target tables.

ASN2225E

 ASNCLP: More than one SET SUBGROUP statement was found in the script for creating, updating, or deleting a SUBGROUP.

Only one SUBGROUP can be specified per script. The ASNCLP program cannot work with more than one subgroup in a session. The SUBGROUP was not created, updated, or deleted.

Ensure that you specify only one SET SUBGROUP statement per script and run the script again.

ASN2226E

 ASNCLP: The Q subscription SUBTYPE subtype does not match the SUBTYPE of other Q subscriptions in a Q subscription group.

The information specified in a create subscription command was inconsistent with other create subscription commands belonging to this multidirectional replication configuration. Different types of Q subscriptions were detected for the Q subscription group. Only one SUBGROUP can be specified, and the SUBGROUP must have Q subscriptions of one SUBTYPE. No Q subscriptions were created.

Ensure that you specify either SUBTYPE 'P' or 'B' under a specific SUBGROUP. Do not mix types of Q subscriptions in one Q subscription group. Rerun the create subscription command.

ASN2227E

 ASNCLP: The number of set connection statements is not sufficient for the number of set schema statements.

In a multidirectional replication configuration, for every n nodes you need n*(n-1) connections. For example, if there are 3 nodes, you need 3*(3-1)=6 connections.

Ensure that the set connection statement and the set schema statement conform to the rules.

ASN2228E

 ASNCLP: Q subscriptions for the SUBGROUP subgroup already exist on the specified servers.

While trying to create more Q subscriptions, you provided SUBGROUP information instead of providing referential information to that SUBGROUP.

Provide a reference to the SUBGROUP rather than defining the SUBGROUP again.

ASN2229I

 The action action_name started at time_stamp. The Q Apply server is apply_server, the Q Apply schema is apply_schema, and the remote server name is remote_servername.

The action started successfully at the Q Apply server.

This message is for your information. No action is required.

ASN2230I

 The action of creating a Q subscription started at time_stamp . Q subscription name: name. Q Capture server: capture_server. Q Capture schema: capture_schema. Q Apply Server: apply_server. Remote server name: remote_servername. Q Apply Schema: apply_schema. The source table is table_name. The target table or stored procedure is table_name.

The Q subscription is starting to be created.

This message is for your information. No action is required.

ASN2231E

 The database object object_name of type object_type does not exist at the data source datasource that was defined through the remote server remote_server.

The database object does not exist in the database catalog at the data source that you specified. Because no information can be retrieved for this object, this object cannot participate in the Q subscription.

Ensure that you specify the correct name of an existing database object and run the task again.

ASN2232E

 The database object object_name of type object_type already exists at the data source datasource, which is defined through the remote server remote_server.

The database object cannot be created because another object already exists that has the same name at the specified data source.

Provide a name for that object that does not already exist in the database, and run the task again.

ASN2233E

 The data source datasource_name that was defined by using the remote server remote_servername is not supported as a Q Replication target.

Only a subset of the data source platforms are supported as targets in Q Replication.

Provide a remote server name that is defined on a supported target and run the task again.

ASN2234W

 The length length1 of the source column source_colname is greater than the length length2 of the target column target_colname. The source data applied to the target might get truncated.

If the actual value of the source column cannot be stored in the target column completely, the data that is applied to the target might get truncated. As long as the actual values from the source are not larger as the target column definition, no data is modified.

No action is needed if truncation is acceptable or if the source column values are always small enough to be applied to the target column. If truncation is not acceptable, then do not select this column to be part of the Q subscription.

ASN2235E

 The name of the target nickname owner.name conflicts with another database object of type object_name.

For federated targets, the replication administration tools always create a new target nickname, which cannot have the same name as a table, view, or other nickname that exists on that system. The name that you provided already exists.

Provide a name for the nickname that is not the same name as a table, view, or other nickname that already exists on that system.

ASN2236W

 The target table schema.tablename of the target nickname schema.nickname has a foreign key defined on it. The nickname does not have the foreign key defined on it but needs to.

Any referential constraints that are defined on the source table are not automatically carried over to the nickname. You need to issue an alter statement to carry the constraints over to the nickname so that the information is in the DB2 catalog tables.

If both the parent and the child tables are participating in the Q subscription, the Q Apply program relies on the information that is stored in the DB2 catalog tables about the referential integrity constraints in order to apply changes to the parent and the child target tables in the correct sequence. If the referential constraint information in not carried over to the nicknames, the Q Apply program might encounter an error while loading the nicknames if the data violates the referential integrity rules.

Issue the ALTER NICKNAME statement if the parent data source tables are also participating in the Q subscriptions.

ASN2237E

 The table object cannot be created at server server because you did not specify the table space.

The replication administration tools require for all z/OS tables to be created using an explicit table space assignment.

Assign a table space to the z/OS table.

ASN2238W

 Transaction mode processing is not supported when you are replicating data from a non-DB2 relational server. In this situation, NULL is the only valid value for the COMMIT_COUNT attribute of the subscription set. The COMMIT_COUNT commitcount_value that you specified will be ignored.

When the source of a subscription set is a non-DB2 relational server, the Apply program uses table mode processing. For table mode processing, the Apply program fetches answer sets for the subscription-set members one member at a time, until all data has been processed. At the end of the data processing for the whole set, the Apply program issues a single commit. The COMMIT_COUNT of NULL is used to tell the Apply program to use table mode processing. The COMMIT_COUNT that you specified is not NULL. Therefore the COMMIT_COUNT is invalid and is ignored.

This message is for your information only. No action is required.

ASN2239I

 The action action_name ended successfully at time_stamp for the Q Apply server apply_server, the Q Apply schema apply_schema and the remote server name remote_servername.

The action ended successfully at the Q Apply server.

This message is for your information only. No action is required.

ASN2240I

 The Q subscription was finished being created at time_stamp for the Q subscription name name The Q Capture server is capture_server, the Q Capture schema is capture_schema, the Q Apply server is apply_server, the Q Apply schema is apply_schema, the remote server is remote_servername, the source table is table_name and the target table or stored procedure is table_name.

The Q subscription was successfully created.

This message is for your information. No action is required.

ASN2241I

 The Q subscription was finished being dropped at time_stamp for the Q subscription name name. The Q Capture server is capture_server, the Q Capture schema is capture_schema, the Q Apply server is apply_server, the Q Apply schema is apply_schema, the remote server is remote_servername, the source table is table_name and the target table or stored procedure is table_name.

The Q subscription was successfully dropped.

This message is for your information. No action is required.

ASN2251E

 The template template_name cannot be dropped because it is being used by one or more monitor suspensions.

At least one row exists in the IBMSNAP_MONSUSPENDS table that refers to the provided template name.

Drop all the suspensions that use this template and then drop the template.

ASN2252W

 The monitor program will be suspended for the entire period between the start date start_date and end date end_date because a template is not provided.

Please see message text.

If you intend to suspend the monitor program for the entire period then no action is necessary. However, if you intend to suspend the monitor program for a certain duration on certain days between the start date and end date then you need to provide a template that is defined using these attributes.

ASN2253E

 The Replication Alert Monitor control tables on server server_name are at a Version 8 architecture level. They must be migrated to a Version 9 architecture level before the suspension function can be used.

Monitor suspension templates and suspensions can only be created if the Monitor control tables have been migrated to a level that supports this function. No script is generated.

Run the migration program to upgrade the control table's architecture level and create the set of new control tables before invoking the action.

ASN2254E

 The template template_name cannot be created as another template with the same name already exists at the server server_name.

A row already exists in the IBMSNAP_TEMPLATES table with the same value in the TEMPLATE_NAME column as the provided template name. No script is generated.

Provide a valid name for the template and reissue the command.

ASN2255E

 The suspension suspension_name cannot be created because another suspension with the same name already exists at the server server_name.

At least one row exists in the IBMSNAP_SUSPENDS table that has the same value in the SUSPENSION_NAME column as the provided suspension name. No script is generated.

Provide a valid value for the suspension name and reissue the command.

ASN2256E

 The value for the end date end_date is not valid because it is earlier than the start date start_date.

The end date value must be greater than the starting date value for the monitor program to suspend during that period.

Provide a valid value for the end date and reissue the command.

ASN2257E

 The value for the start date start_date is not valid because it is in the past.

The start date value must represent a date value in the future in order to indicate to the monitor program when to start suspending.

Provide a valid value for the start date and reissue the command.

ASN2258E

 The value value provided for the input parameter START DATE or END DATE is out of range.

The START DATE and END DATE input parameters require a value that is within the allowed range of the DB2 TIMESTAMP data type.

Make sure that the specified value is within the allowed range. Refer to the DB2 SQL Reference for acceptable values for the TIMESTAMP data type.

ASN2259E

 The value value specified for the input parameter parameter is incorrect. reason_text

A value specified as an input parameter to the CREATE TEMPLATE or ALTER TEMPLATE command is either incorrect or outside of the required value range.

Please specify a correct value for the input value based on the reason_text.

ASN2261E

 An operating system error occurred while executing the command command_name on the host host_name by the stored procedure schema_name in database database_name. The operating system error message is message.

The operating system could not execute the command.

Ensure that the fenced user of the database manager instance of the specified database can execute the provided command.

ASN2262E

 The requested action failed because the name name that was provided for the WebSphere MQ queue manager is not valid or known at the host system host_name. The WebSphere MQ error code is error_code.

The replication administration tool must be able to connect to the specified queue manager to perform the requested action. The queue manager name that was specified does not match any existing queue managers on the host system.

Make sure that the queue manager exists on the host system and check the queue manager name. WebSphere MQ object names are case-sensitive.

ASN2263E

 The requested action failed because the WebSphere MQ queue manager host_name-queue_manager_name is not available for connection. The WebSphere MQ error code is error_code.

The replication administration tool must be able to connect to the specified queue manager to perform the requested action. The queue manager might not be running. Other possible causes can be found in the error code that was returned by WebSphere MQ.

Start the queue manager if it is not running, for example by using the strmqm command.

ASN2264E

 The requested action failed because the command server for the WebSphere MQ queue manager host_name-queue_manager_name is not running. The WebSphere MQ error code is error_code.

The replication administration tool must be able to connect to the specified queue manager to perform the requested action. The command server must be running to issue commands to the queue manager and transmit responses back to the sender.

Start the command server, for example by using the strmqcsv command.

ASN2265E

 The stored procedure schema_name in subsystem subsystem_name is not authorized to access the WebSphere MQ queue manager host_name-queue_manager_name.

The effective user of the stored procedure does not have sufficient authority to connect to the queue manager.

Ensure that the subsystem user, stored procedure definer, or the DB2 user has the authority to access WebSphere MQ.

ASN2266E

 An error occurred while accessing the WebSphere MQ queue manager host_name-queue_manager_name. The WebSphere MQ reason code is reason_code.

A problem occurred while accessing the queue manager.

Respond according to the reason code.

ASN2267E

 A WebSphere MQ queue with the specified name queue_name does not exist in the queue manager host_name-queue_manager_name. The WebSphere MQ error code is error_code.

A queue with the specified name cannot be found at the specified queue manager. The queue name that was specified might be incorrect.

Check the queue name for misspellings and ensure that the queue exists in the queue manager (for example using the DISPLAY QUEUE command).

ASN2268E

 The action action failed on WebSphere MQ queue host_name-queue_manager_name-queue_name. The WebSphere MQ reason code is reason_code.

A problem occurred while putting a test message on a queue or getting a message from a queue.

Respond according to the reason code.

ASN2270E

 The stored procedure schema_stored_procedure_name in database database_name is not authorized to access the WebSphere MQ queue manager queue_manager_name because the operating system user ID user_ID, which is the DB2 fenced user of the instance that contains this database, is not a member of the operating system group for WebSphere MQ applications (usually mqm) at the host host_name.

The fenced user of the database instance does not have the authority to access the WebSphere MQ environment or the specified queue manager.

Ensure that the fenced user ID of the database instance is part of the operating system group assigned to WebSphere MQ (usually mqm).

ASN2271W

 The WebSphere MQ queue manager host_name-queue_manager_name has the version version_number that is older than the minimum supported version version_number.

Q Replication and event publishing require a minimum version level of WebSphere MQ.

Check the installation for the correct version, or install an WebSphere MQ server at the minimum version level.

ASN2272W

 The WebSphere MQ queue host_name-queue_manager_name-queue_name has an invalid definition and cannot be opened. The WebSphere MQ error code is error_code.

The specified queue is defined incorrectly.

Fix the problem indicated by the reason code, and then retry the action.

ASN2273W

 The WebSphere MQ base queue (BASE_Q) queue_name1 that is referenced by the alias queue host_name-queue_manager_name-queue_name2 does not exist.

The WebSphere MQ alias queue definition is inconsistent. Any alias queue used by Q Replication or event publishing must be defined with an existing base queue.

Check the parameter BASE_Q of the alias queue for misspellings, and check if the specified queue exists. If necessary, update the BASE_Q parameter of the alias queue, or create a base queue with the specified name. Ensure that the base queue has the correct type and parameters as required by Q Replication.

ASN2274W

 The WebSphere MQ transmission queue queue_name for the remote queue host_name-queue_manager_name-queue_name does not exist.

When a remote queue such as the Q Capture send queue or Q Apply administration queue is created, you use the XMITQ attribute to specify the transmission queue that is used. No transmission queue exists with the name that was specified with the attribute XMITQ for the specified remote queue in the same queue manager.

Check the attribute XMITQ of the specified remote queue for misspellings, or create a transmission queue for the specified remote queue.

ASN2275W

 The maximum message size (MAXMSGL) size1 of the WebSphere MQ queue host_name-queue_manager_name-queue_name is greater than the maximum message size (MAXMSGL) size2 of its queue manager host_name-queue_manager_name.

The maximum message size (MAXMSGL) of the specified queue must be less than or equal to the maximum message size (MAXMSGL) of the queue manager.

Reduce the maximum message size of the queue or increase the maximum message size of the queue manager.

ASN2276W

 The maximum message size (MAXMSGL) size of the WebSphere MQ queue host_name-queue_manager_name-queue_name that is used as the send queue is greater than the maximum message size (MAXMSGL) size of the receive queue host_name-queue_manager_name-queue_name.

The maximum message size (MAXMSGL) of the send queue must be less than or equal to the maximum message size (MAXMSGL) of the receive queue.

Reduce the maximum message size of the send queue or increase the maximum message size of the receive queue.

ASN2277W

 The WebSphere MQ queue host_name-queue_manager_name-queue_name cannot be used as a Q_replication_queue_type because it is neither a local queue nor an alias queue that references a local queue.

The Q Capture administration queue and restart queue must be local queues or alias queues that reference a local queue.

Specify a local queue or an alias queue that references a local queue.

ASN2278W

 The WebSphere MQ queue host_name-queue_manager_name-queue_name cannot be used as a send queue because it is not a local queue, a remote queue, or an alias queue that directly or indirectly references a local or remote queue.

When you create or change a replication queue map, the send queue that you specify must be a local queue, remote queue, or an alias queue that references a local or remote queue.

Specify a queue of a correct type.

ASN2279W

 The maximum message size (max_message_size) size of the queue map queue_map_name is greater than the maximum message size (MAXMSGL) size of the WebSphere MQ queue host_name-queue_manager_name-queue_name that is used as the send queue.

The max_message_size attribute of the queue map, which specifies the maximum size of the buffer that is used for sending messages over a send queue, must not be larger than the WebSphere MQ maximum message length (MAXMSGL) attribute that is defined for the queue.

Use the Replication Center or ASNCLP command-line program to decrease the max_message_size value for the queue map or increase the MAXMSGL attribute of the queue.

ASN2280W

 The maximum message size (max_message_size) size1 of the replication queue map replication_queue_map_name is greater than the maximum message size (MAXMSGL) size2 of the WebSphere MQ queue host_name-queue_manager_name-queue_name that is used as the send queue.

The maximum message size of the replication queue map must be less than or equal to the maximum message size of the specified send queue.

Reduce the max_message_size value of the replication queue map or increase the MAXMSGL value of the queue.

ASN2281W

 The WebSphere MQ queue host_name-queue_manager_name-queue_name cannot be used as a Q_replication_queue_type. Although the Q Capture and Q Apply programs use the same queue manager, the specified queue is neither a local queue nor an alias queue that directly or indirectly references a local queue.

When the Q Capture and Q Apply programs use the same queue manager, the send queue, receive queue, and administration queue that you specify for a replication queue map must be local queues or alias queues that directly or indirectly reference local queues.

Specify a queue of a correct type.

ASN2282W

 Although the Q Capture and Q Apply programs use the same queue manager host_name-queue_manager_name, the queue queue1 that is used as a Q_replication_queue_type1 and the queue queue2 that is used as a Q_replication_queue_type2 are not identical or are not alias queues that refer to the same local queue.

When the Q Capture and Q Apply programs use the same queue manager, the send queue and receive queue must be either the same local queue or alias queues that refer to the same local queue. The same holds true for the Q Capture and Q Apply administration queues.

Choose one queue for both purposes.

ASN2283W

 The WebSphere MQ queue host_name-queue_manager_name-queue_name cannot be used as a receive queue in the replication queue map replication_queue_map_name. Although the Q Capture and Q Apply programs use different queue managers, the specified queue is neither a local queue nor an alias queue referencing a local queue directly or indirectly.

When Q Capture and Q Apply use different queue managers, the receive queue must be local queues or alias queues referencing a local queue directly or indirectly.

Specify a queue of a correct type.

ASN2284W

 The WebSphere MQ queue host_name-queue_manager_name-queue_name cannot be used as Q_replication_queue_type in the replication queue map replication_queue_map_name. Although the Q Capture and Q Apply programs use different queue managers, the specified queue is neither a remote queue nor an alias queue that directly or indirectly references a remote queue.

When Q Capture and Q Apply use different queue managers, the send queue and Q Apply administration queue must be remote queues or alias queues that directly or indirectly reference remote queues.

Specify a queue of a correct type.

ASN2285W

 The WebSphere MQ model queue queue_name does not exist in queue manager host_name-queue_manager_name, although the Q subscription specifies a load phase.

For a Q subscription that uses a load phase, a model queue needs to exist in the queue manager that the Q Apply program uses so that the Q Apply program can create a spill queue dynamically. By default, Q Apply expects the model queue to be named IBMQREP.SPILL.MODELQ.

Check the name of the model queue for misspellings, create a new model queue, or specify no load phase for the Q subscription.

The following attributes are mandatory for the model queue:

  • Message delivery sequence (MSGDLVSQ): FIFO
  • Maximum queue depth (MAXDEPTH): 500000 or higher
  • Maximum message size (MAXMSGL): 100000 or higher
  • Definition type (DEFTYPE): PERMDYN

ASN2286W

 The value value1 of the parameter parameter_name of the WebSphere MQ model queue host_name-queue_manager_name-queue_name is incorrect or too low. The required value is value2.

The model queue that is used to create spill queues for the Q Apply program needs to have the following parameter values:

  • Message delivery sequence (MSGDLVSQ): FIFO
  • Maximum queue depth (MAXDEPTH): 500000 or higher
  • Maximum message size (MAXMSGL): 100000 or higher
  • Definition type (DEFTYPE): PERMDYN

Update the model queue parameter values, or specify a model queue that has the correct parameter values.

ASN2287W

 The WebSphere MQ queue host_name-queue_manager_name-queue_name cannot be used as Q_replication_queue_type because the value value1 of the attribute parameter_name does not match the required value value2.

The specified WebSphere queue attribute is not valid for the specified purpose.

Choose a different queue or update the attribute to the required value.

ASN2288W

 The test message put on WebSphere MQ queue host_name1-queue_manager_name1-queue_name1 did not arrive at the queue host_name2-queue_manager_name2-queue_name2.

The message flow between the first and the second queue does not work properly.

Test messages can only be delivered successfully if the Q Capture and Q Apply programs are not running. Ensure that the Q Capture and Q Apply programs are stopped. Check the WebSphere MQ setup for error messages and test the message flow by using the programs that are provided by WebSphere MQ (amqsput, amqsget, amqsbcg, amqsbr).

ASN2289W

 The test message put on WebSphere MQ queue host1_queue_manager1_queue1 was received at the queue host2_queue_manager2_queue2, but the content has been distorted.

The message flow between the first and the second queue does not work properly. Messages can be transmitted, but their contents are being distorted.

Check the code pages of the source and target queue managers, and use the WebSphere MQ tools to check for configuration faults that can lead to the distortion of messages between the two queues.

ASN2290I

 The test message put on WebSphere MQ queue host_name1-queue_manager_name1-queue_name1 was received at the queue host_name2-queue_manager_name2-queue_name2 used as Q_replication_queue_type.

The test message confirms that the message flow between the two queues is functioning properly.

This message is for your information only. No action is required.

ASN2291I

 number tests failed.

The WebSphere MQ environment for the current object was validated by several checks, and problems were found.

For any tests that failed, examine the corresponding messages and correct the problem.

ASN2293E

 The OPERATOR CONSOLE option is not valid for the Replication Alert Monitor with monitor qualifier monitor_qualifier and monitor server server_name because the monitoring server is on Linux, UNIX, or Windows and not on z/OS.

The OPERATOR CONSOLE option is used to send alerts to the z/OS console. This option is not valid for Linux, UNIX, or Windows operating systems.

Send alerts to a contact or contact group for this monitor.

ASN2294E

 The replication action action_name ended in error. The architecture level arch_level of the Q Capture server server for the Q Capture schema Q_capture_schema is not compatible with the Version 9 DB2 database for Linux, UNIX, or Windows where the Q Capture control tables are defined.

In order to capture data and schema changes made to a Version 9 DB2 database on Linux, UNIX and Windows platforms, a Version 9 Q Capture server is required. Version 9 Q Capture server refers to both the architecture level of the control tables and the version of the Q Capture program instance running on the server. But based on the value of the architecture level obtained from the IBMQREP_CAPPARMS table, the control table structure is at a level prior to Version 9. This indicates there are inconsistencies in the data stored in the control tables or the control tables have not been migrated.

Migrate your existing Q Capture control server to the current architecture level.

ASN2296E

 The table schema_name cannot be used as a CCD table because it does not have the correct column structure. The column column_name is missing or has an invalid definition.
CCD tables must have the following four columns:
  • IBMSNAP_INTENTSEQ
  • IBMSNAP_OPERATION
  • IBMSNAP_COMMITSEQ
  • IBMSNAP_LOGMARKER

Choose an existing table with the correct CCD columns, or use the Replication Center or ASNCLP program to create a new CCD table.

ASN2297E

 The table schema_name cannot be used as a user table because it has a CCD column structure. The column column_name indicates a CCD table structure.

CCD tables cannot be used as user table targets for Q subscriptions.

Choose a different existing table that does not contain any CCD columns, or use the Replication Center or ASNCLP program to create a new target table.

ASN2298E

 The operation operation cannot be completed because the architecture level arch_level of the schema schema for the program program_name is older than the required architecture level arch_level.

The specified operation requires a higher architecture level.

Check if the provided schema is correctly specified for the requested operation. If not, choose another, appropriate schema for the provided program.

ASN2299E

 The CCD table schema.name cannot be populated by Q Apply schema Q_apply_schema because the Q subscription Q_subscription_name in this schema already uses the CCD table as a target.

CCD tables populated by Q Apply can be the target of only one Q subscription.

Remove all but one Q subscription with the CCD table as a target.

ASN2300E

 The CCD option option cannot be specified together with the value value for the Q subscription attribute attribute_name. Valid attribute values are value_list.

The command attempts to create a Q subscription with a target table type of CCD and some of the specified parameter values are not compatible with this type of target.

Specify a valid value for the Q subscription attribute.

ASN2301E

 The Q subscription receive_queue_Q_subscription_name cannot be used to populate the SQL registration of the CCD table schema_name because the value value1 of the attribute attribute_name of the Q subscription does not match the value value2 of the SQL registration.

The attributes for "complete" and "condensed" have to match between the Q subscription and the SQL registration.

Update the attributes of the existing Q subscription or SQL registration.

ASN2302E

 The configuration of the Q Apply schema Q_apply_schema cannot be changed to populate registrations in the SQL Capture schema capture_schema because Q Apply is currently configured to populate registrations in the SQL Capture schema capture_schema.

A Q Apply program (which is identified by a Q Apply schema) can only send changes to CCD tables that are registered in a single SQL Capture schema. The specified Q Apply schema is already being used to send changes to CCD tables in a SQL Capture schema. If you want to use the specified Q Apply schema for CCD tables in a different SQL Capture schema, change the SQL_CAP_SCHEMA value in the IBMQREP_APPLYPARMS table for the specified Q Apply program.

Check the Q Apply schema for misspellings, check the configured SQL Capture schema in the Q Apply schema, or update the Q Apply schema. To update the schema, use the ALTER APPLY CONFIGURATION command in the ASNCLP command-line program or the Change Saved Parameters window for the Q Apply program in the Replication Center.

ASN2303W

 The configuration of the Q Apply schema Q_apply_schema is being changed from populating registrations in the SQL Capture schema capture_schema to populate registrations in the SQL Capture schema capture_schema. Existing, inactive Q subscriptions populating CCD target tables may become invalid.

Q Apply has already been configured to use a different SQL capture schema. The update will overwrite the existing value and invalidate any existing Q Subscriptions with CCD targets.

No action is necessary if the existing Q subscriptions can be invalidated. Otherwise, choose a different Q Apply schema.

ASN2304E

 The configuration of the Q Apply schema Q_apply_schema cannot be changed from populating registrations in the SQL Capture schema capture_schema to populate registrations in the SQL Capture schema capture_schema. There are active Q Subscriptions populating CCD target tables in this Q Apply schema.

Q Apply has already been configured to use a different SQL capture schema. The update will overwrite the existing value and invalidate any existing Q Subscriptions with CCD targets.

Deactivate the Q Subscriptions, or use a different Q Apply schema.

ASN2305E

 The Q Apply schema Q_apply_schema does not contain a Q subscription that uses the provided CCD table schema_name as a target table.

A Q subscription must exist for this CCD table before it can be registered as a source populated by Q Replication.

Check the table name for misspellings, and verify that the provided table is a target table for a Q Subscription in the provided Q Apply schema.

ASN2306E

 The subscription member cannot be added to the subscription set because the existing members in this set are using registrations that are not populated by a Q Apply schema, and the new member is using a registration that is populated by the Q Apply schema Q_apply_schema.

A subscription set can only contain member with registrations that are populated by a Q Apply schema, or members with registrations that are not populated by a Q Apply schema.

Choose another subscription set that is empty or that contains compatible members.

ASN2307E

 The subscription member cannot be added to the subscription set because the existing members in this set are using registrations that are populated by the Q Apply schema Q_apply_schema, and the new member is using a registration that is not populated by a Q Apply schema.

A subscription set can only contain member with registrations that are populated by a Q Apply schema, or members with registrations that are not populated by a Q Apply schema.

Choose another subscription set that is empty or that contains compatible members.

ASN2308E

 The subscription member cannot be added to the subscription set because the existing members in this set are using registrations which are populated by the Q Apply schema schema, and the new member is using a registration that is populated by the Q Apply schema Q_apply_schema.

A subscription set can only contain member with registrations that are populated by a Q Apply schema if the Q Apply schema and the receive queue are the same for all registrations of the members.

Choose another subscription set that is empty or that contains compatible members.

ASN2309E

 The subscription member cannot be added to the subscription set because the existing members in this set are using registrations that are populated by the Q Apply schema Q_apply_schema using the receive queue receive_queue_name, and the new member is using a registration that is populated using the receive queue receive_queue_name.

A subscription set can only contain member with registrations that are populated by a Q Apply schema if the Q Apply schema and the receive queue are the same for all registrations of the members.

Choose another subscription set that is empty or that contains compatible members.

ASN2310W

 The SQL registration for the CCD table schema_name in the SQL Capture schema capture_schema will become unpopulated.

If the Q subscription populating a CCD table registration in a SQL Capture schema is dropped, the registration will no longer receive updates from Q Apply.

No action is required.

ASN2311I

 The table table_owner.table_name has an edit routine (EDITPROC) defined on it. Replication requires DB2 Version 8 APAR PK13542 or later to correctly handle the data in such tables.

Replication supports tables with EDITPROC definitions, but the DB2 subsystem that contains the tables must be upgraded to the specified APAR. With the APAR, DB2 invokes the edit routine to transform the row back to its original state before giving the data to the replication log reader program.

Upgrade the database manager instance that contains the table to the specified APAR.

ASN2312E

 The target type of type does not support before-image columns.

The only valid target type for before-image columns is CCD.

Change the target type for the Q subscription to CCD.

ASN2313E

 The before-image column prefix prefix is invalid because its length length is not within the allowed range of 1 to 4 characters.

The prefix that is used to identify values in a before-image column must be at least 1 and at most 4 characters long.

Change the length of the prefix to a value that is within the required range.

ASN2314E

 The before-image column prefix prefix is invalid because it contains the character character, which is not supported.

The before-image column prefix can only contain alphabetical characters that the database allows at the start of column names and within column names.

Replace or remove invalid characters from the prefix.

ASN2315E

 The before-image column column1 does not exist for the column column2.

The Q subscription was set up so that the column from the source table has a corresponding before-image column in the target table. Before-image column names are generated by adding a before-image prefix to the name of the target column that maps to the source column. No column could be found in the target table with this generated name.

Verify that the target table contains a column with this generated name. If not, change the Q subscription to update the before-image prefix value and regenerate the script. If the before-image is not needed, remove it from the target column specification.

ASN2316E

 The target column column_name cannot be selected for before-images because the data type data_type of the column does not support before images.

Q Replication supports before-image columns for all data types except for large object (LOB) data types.

Remove this column from the before-image column selection.

ASN2317E

 The column column_name cannot be selected for a before-image column because the length length of the combined column name and before-image prefix combined_name exceeds the limit of the database database_alias.

The combined length of the column name and before-image prefix must be within the database limits for column-name length.

Shorten the before-image prefix.

ASN2318E

 The column column_name1 cannot be selected as a replication target column because it is used to hold the before-image values of column column_name2.

Before-image columns cannot be target columns for replication.

Either change the value of the before-image column prefix or select a different before-image column for the specified after-image column.

ASN2319W

 The before-image columns in the target table table_owner.table_name do not have the same before-image prefix. You will not be able to register this table with the SQL Replication Apply program for a three-tier distribution.

Before-image columns in a CCD table that is used as the middle tier in three-tier replication must use the same single character for the before-image prefix. The before-image columns in the specified table do not have the same prefix. The table cannot be used in a three-tier architecture.

Modify the before-image prefix if you intend to use this table in three-tier replication architecture.

ASN2320E

 The column column_name1 requested to be a before-image column for the column column_name2 does not exist in the target table.

To be used as a before-image column, a column must first exist in the target table.

Specify a column name that exists in the target table.

ASN2321E

 The column column_name1 with data typedata_type cannot be used as a before-image column for columncolumn_name2 with data type data_type because their data types are not compatible.

The data types for an after-image column and its corresponding before-image column must be compatible.

Make sure that you specify the correct column names.

ASN2322E

 The table table_owner.table_name cannot be registered as an external CCD table because the before-image columns do not have the same prefix.

The before-image columns in a CCD table must share a common prefix in order to register the table as an external CCD. The before-image columns in the specified table do not share a common prefix.

To use this CCD table as a SQL Replication source, redefine the Q subscription so that the before-image columns for the table share a common prefix, then perform the action again.

ASN2323E

 Before values cannot be sent for the column column_name in the table table_owner.table_name because the column is not part of the publication.

You have requested that the Q Capture program send before values for the specified column, but this column was not included in the publication.

Either select the column to be part of the publication or do not request before values for the column.

ASN2324I

 The default before-image prefix, X, resulted in conflicting column names in the target table table_owner.table_name. A different before-image prefix, prefix, will be used to generate unique before-image column names.

The columns in the table should be unique. However, the default before-image prefix resulted in conflicting names. The specified prefix will be used instead.

This message is for your information only. No action is required.

ASN2325E

 The Q Apply schema schema cannot be used to populate CCD tables that are registered for SQL Replication because the SQL Capture schema has not been specified.

You must first configure the Q Apply program to use a specific SQL Capture schema for the CCD tables that it populates before you register the tables as sources for SQL Replication.

Update the Q Apply schema using the ALTER CONFIGURATION APPLY command in the ASNCLP command-line program, or by using the Change Saved Parameters window for the Q Apply program in the Replication Center.

ASN2326E

 The SQL registration for the CCD target table table_owner.table_name of the Q subscription receive_queue_name.q_subscription_name cannot be created because this Q subscription uses the Q Capture schema schema and the Q Apply schema schema. These schemas are different from the Q Capture schema schema and the Q Apply schema schema that are used by other Q subscriptions that were selected.

Only Q subscriptions that are replicated from the same Q Capture schema to the same Q Apply schema can be registered at the same time.

Exclude the specified Q subscription from the group of Q subscriptions that you are registering.

ASN2327E

 The existing SQL registration of the CCD table table_owner.table_name in the SQL Capture schema schema cannot be modified to be used by the Q Apply program because the value value1 for the property property1 in this registration conflicts with the value value2 for the property property2 in the Q subscription receive_queue_name.q_subscription_name.

The SQL registration and Q subscription need to have the same values for the CCD table properties CONDENSED and COMPLETE. The values can be either ON or OFF. The matching properties are required in order to change an existing registration to be used by the Q Apply program.

Change the Q subscription so that the CCD table properties CONDENSED and COMPLETE match the properties of the SQL registration.

ASN2328E

 The Capture schema schema does not exist at the database database_alias.

The specified Capture schema could not be found at this database.

Check the name for misspellings and correct the name of the Capture schema.

ASN2329E

 The Capture schema schema has an architecture level of level1 that is older than the required architecture level level2.

The Capture schema is too old.

Choose a different Capture schema, or migrate the Capture schema to the required architecture level.

ASN2330E

 The Capture schema schema is defined in the federated database database_name and cannot be used to register CCD tables that are targets for Q Replication.

The Capture schema was set up for federated data sources and cannot be used for DB2 sources.

Choose another Capture schema that is not set up for federated data sources.

ASN2331E

 The Capture schema schema that is managed by the Q Apply schema schema cannot be modified to the new schema schema2 because an active Q subscription, receive_queue_name.q_subscription_name, is managing the SQL registration for the target CCD table table_owner.table_name in the existing schema.

If the Capture schema were changed, it would invalidate the active Q subscription.

Deactivate the Q subscription and retry the action.

ASN2332W

 The Capture schema schema that is managed by the Q Apply schema schema will be modified to the new schema schema2. The existing and inactive Q subscription receive_queue_name.q_subscription_name may become invalid.

The requested update of the Capture schema could invalidate Q subscriptions.

No user action is necessary.

ASN2333E

 The length length1 of the value schema for the Capture schema is higher than the maximum supported length length2.

The specified Capture schema has an invalid length.

Reduce the length of the Capture schema and rerun the action.

ASN2334W

 The SQL registration for the CCD table table_owner.table_name will be modified so that it will not longer be populated by the Q subscription receive_queue_name.q_subscription_name.

A SQL registration can receive updates only from one Q subscription. If another Q subscription is selected to send updates, the previous one will no longer be able to update the target as well.

Choose one of the following options:

  • If you would like the SQL registration to be populated by the specified Q subscription, then no action is necessary. You can execute the generated script.
  • If you would like to continue using the original Q subscription to populate the SQL registration, then do not execute the generated script and cancel the action.

ASN2335E

 The SQL registration for the CCD table table_owner.table_name cannot be found in the SQL Capture schema schema at the database database_alias.

The SQL Capture schema at this database does not contain the specified SQL registration.

Check the name of the CCD table for which the registration was specified, and retry the action.

ASN2336E

 A SQL registration for the CCD tabletable_owner.table_name already exists in the SQL Capture schema schema at the database database_alias .

A SQL registration was specified but another registration already exists with the same name in the SQL Capture schema on this database.

Check the name of the CCD table for which the registration was specified, and retry the action.

ASN2337W

 The SQL registration for the CCD table table_owner.table_name will become unpopulated when the Q subscription is dropped.

When the Q subscription that is populating this CCD table is dropped, the SQL registration of the CCD table will no longer receive data from the source.

No user action necessary.

ASN2338W

 The SQL registration for the CCD table table_owner.table_name will be dropped. Ensure that the SQL subscription-set member for the target table table_owner.table_name at the SQL Apply control server database_alias in the SQL subscription set set_name that uses the Apply qualifier apply_qualifier has been deactivated.

When this SQL registration is dropped, the subscription-set member that receives data from the registration should be inactive to avoid data loss.

Check if the specified member has been deactivated.

ASN2339W

 The SQL registration for the CCD table table_owner.table_name will be updated to be populated by the Q subscription receive_queue_name.q_subscription_name. Ensure that the subscription-set member for the target table table_owner.table_name at the SQL Apply control server database_alias in the SQL subscription set set_name that uses the Apply qualifier apply_qualifier has been deactivated.

When the SQL registration is updated, the subscription-set member that receives data from the registration should be inactive to avoid data loss.

Check if the specified member has been deactivated.

ASN2340E

 The subscription-set member cannot be added to the subscription set because the existing members in this set are using source registrations that are not populated by a Q Apply program, and the new member is using a source registration that is populated by the Q Apply schema schema.

A subscription set can only contain members with source registrations that are populated by one Q Apply program using the same receive queue, or that are not populated by Q Apply.

Choose another subscription set that is empty or contains compatible members.

ASN2341E

 The subscription-set member cannot be added to the subscription set because the existing members in this set are using source registrations that are populated by Q Apply schema schema and the new member is using a source registrations this is not populated by a Q Apply program.

A subscription set can only contain members with source registrations that are populated by one Q Apply program using the same receive queue, or that are not populated by Q Apply.

Choose another subscription set that is empty or contains compatible members.

ASN2342E

 The subscription-set member cannot be added to the subscription set because the existing members in this set are using source registrations that are populated by Q Apply schema schema using the receive queue receive_queue, and the new member is using a source registration this is populated by Q Apply schema schema2 using the receive queue receive_queue.

A subscription set can only contain members with source registrations that are populated by one Q Apply program from the same receive queue.

Choose another subscription set that is empty or contains compatible members.

ASN2343E

 The SQL registration for the target CCD table_owner.table_name cannot be modified to be managed by the Q Apply program because the value value of the property property is unsupported.

Q Apply can only manage specific SQL registrations. The documentation provides details.

Update the SQL registrations, or choose a different SQL registration in a different SQL Capture schema.

ASN2344I

 The target CCD table_owner.table_name for this Q subscription has an existing SQL registration in the SQL Capture schema schema, and the Q Apply program is configured to manage SQL registrations in this schema. If this Q subscription becomes active, the Q Apply program will manage the target CCD table as a source for SQL Replication.

The target CCD is already registered and Q Apply has been configured correctly, so the target CCD will automatically become a source for SQL Replication.

This message is for your information only. No action is required.

ASN2345E

 The resulting data type data_type1 of the expression expression is not compatible with the data type data_type2 of the mapped target column column_name.

In order to replicate an expression to a target column, the Q Apply program requires the resulting data type of the expression to match the data type of the target column. The data types of the expression and the target column to which it is mapped do not match.

Modify your expression so that its resulting data type matches the data type of the specified target column, or choose another column in the target that has the same data type as the expression.

ASN2346E

 The column column_name that is specified in the expression expression does not exist in the source table table_owner.table_name.

A column must exist in the source table to be part of an expression, and the specified column could not be found.

Specify a different column that exists in the source table or remove the column from the expression.

ASN2347E

 The expression expression cannot be mapped to the target column column_name because the expression can have a null value and the target column is defined with a NOT NULL attribute.

The null characteristics of the expression and the target column must match. None of the source columns chosen in the expression is defined with a NOT NULL attribute, so the resulting value of the expression can be null. The target column is defined as NOT NULL.

Include at least one source column that is defined as NOT NULL in the expression, or map the expression to another column in the target that can hold null values.

ASN2348E

 The column column_name in the target table table_owner.table_name cannot be directly mapped to a source column because the specified target column already maps to an expression expression.

A target column cannot be mapped to both a source column and an expression.

Choose a different target column for the mapping.

ASN2349E

 The column column_name in the target table table_owner.table_name cannot be mapped to an expression expression because the target column is already mapped directly to a source column column_name.

A target column cannot be mapped to both an expression and a source column.

Choose a different target column for the mapping.

ASN2350E

 The Replication administration tool is running at a DB2 Version 8 level. The tool cannot be used to administer a DB2 Version 9 server for Q Replication.

You cannot use a pre-Version 9 Replication administration tool to administer a DB2 Version 9 server because of the changes in the structure of the replication control tables and the replication architecture level.

Migrate the DB2 client where the replication administration tool is running to Version 9.

ASN2351E

 The CCD table schema.name cannot be defined as condensed because the database object name of type typename enforces uniqueness of the columns column_names, which are not part of the replication key.

The Apply program will fail when trying to apply changes to the target table if this table contains a primary key, unique constraint, or unique index that enforces the uniqueness of columns that are not part of the replication key. This is usually the case if there is a second unique constraint or index defined on this table. Note: You can have secondary unique indexes on CCD columns, for example, IBMSNAP_INTENTSEQ and IBMSNAP_COMMITSEQ.

Remove the unique constraint or index, or consider generating a new CCD target table.

ASN2353E

 On z/OS, you cannot use the Replication Center to perform operational tasks on replication and event publishing programs such as starting, stopping, or reinitializing.

The Replication Center function to run commands that operate on replication or publishing programs on z/OS has been deprecated.

To start the programs, use JCL or a started task. To issue commands to running replication or publishing programs such as stop or reinitialize, use the MODIFY command.

ASN2354E

 You cannot use the Replication Center on z/OS to perform operational tasks such as starting, stopping, or reinitializing replication and event publishing programs.

The Replication Center function to run commands that operate on replication or publishing programs on z/OS has been deprecated.

To start the programs, use JCL or a started task. To issue commands to running replication or publishing programs such as stop or reinitialize, use the MODIFY command.

ASN2355E

 The command command cannot be used with a Classic replication source.

A Classic replication server was set as the capture server in a prior SET SERVER CAPTURE command. The specified command is not valid for Classic replication sources. The following commands are valid for a Classic source:

  • CREATE REPLQMAP
  • ALTER REPLQMAP
  • DROP REPLQMAP
  • CREATE QSUB
  • ALTER QSUB
  • DROP QSUB
  • LOADDONE
  • START QSUB
  • STOP QSUB
  • LIST
  • ALTER CAPPARMS

Take one of the following actions:

  • Issue the environment command SET SERVER CAPTURE to set the Capture server to another server where the command is supported.
  • Use one of the supported commands for Classic sources.

ASN2356W

 A default schema of ASN is assigned because the capture server is a Classic replication server. The schema that was provided is not used.

A Classic replication server was set as the capture server in a prior SET SERVER CAPTURE command. Only one set of Classic capture control tables exists on the server. These tables have a schema of ASN and the ASNCLP program always uses a default schema of ASN.

This message is for your information only. No action is necessary.

ASN2357E

 The option option cannot be used with a Classic replication source.

A Classic replication server was set as the capture server in a prior SET SERVER CAPTURE command. The specified option is not valid for Classic sources. The following options are not supported:

  • SUPPRESS DELETES
  • SEARCH CONDITION
  • TRGCOLS EXCLUDE (for new targets)
  • LOAD TYPE with values 1, 2, or 3

Take one of the following actions:

  • Issue the environment command SET SERVER CAPTURE to set the Capture server to another server where the option is supported.
  • Specify a different option for Classic sources. For LOAD TYPE, the supported options are 0 (no load) or 4 (load from Classic source).

ASN2358E

 The configuration file file_name does not exist at the specified location. Please check the directory name, file name, and permissions on the file.

The ASNCLP program did not find the specified configuration file by using the path and file name that was provided in the file_name parameter.

Ensure that the path and file name are correct. Also, check whether the permissions on the file are set correctly to allow the ASNCLP program to read the file.

ASN2359E

 The command to create Q subscriptions did not complete successfully. These number Q subscriptions were defined on the Classic server but not on the Q Apply server: Q_subscription_list1. These number Q subscriptions were not defined on either server: Q_subscription_list2. These number Q subscriptions were defined on both servers: Q_subscription_list3.

An error occurred during processing of the CREATE QSUB command. Some of the Q subscriptions were defined on the Classic server only, and some were not defined on either server. The Q subscriptions that are defined on only one server are incomplete and must be deleted.

Follow these steps:

  • Use the DROP QSUB command in the ASNCLP program to delete the subscriptions that are defined on the Classic server only.
  • Use the CREATE QSUB command to create the Q subscriptions that were not defined on either server.

The Q subscriptions that were defined on both servers are complete and no further action is required.

ASN2360E

 The command to delete one or more Q subscriptions did not complete successfully. These number Q subscriptions were deleted on the Classic server but not on the Q Apply server: Q_subscription_list1. These number Q subscriptions were not deleted from either server: Q_subscription_list2. These number Q subscriptions were deleted from both servers: Q_subscription_list3.

An error occurred during processing of the DROP QSUB command. Some of the Q subscriptions were deleted only on the Classic server and some were not deleted at either server. The Q subscriptions that were deleted only on the Classic server still exist on the Q Apply server and must be dropped manually.

Use the DROP QSUB command in the ASNCLP program to delete the Q subscriptions that were only deleted on the Classic server and the Q subscriptions that were not deleted on either server.

ASN2361E

 The Q subscription cannot be created because only a subset of the columns from the source table table_owner.table_name were selected to take part in replication and the source server is a Classic replication server.

For Classic replication, all columns in the source table must be selected for replication.

Specify all columns in the source table to take part in the Q subscription and issue the CREATE QSUB command again.

ASN2362E

 The action action_name ended in error because the architecture level of the Q Apply control tables under the schema schema is at pre-Version 9 and the source is a Classic replication server.

The Q Apply control tables need to be at a Version 9 architecture level in order to use a Classic replication server as a source. The specified Q Apply schema is at pre-V9 architecture level.

Take one of the following actions:

  • Migrate the Q Apply control tables to Version 9.
  • Create a new set of Q Apply control tables with Version 9 architecture.

ASN2363E

 The action action_name ended in error because capture control tables were not found on the Classic replication server.

The control tables need to exist prior to performing the specified action but were not found. The control tables are created when the Classic replication product is installed.

See IBM Knowledge Center for details on how to configure a Classic replication server, and complete the steps before defining or using any replication objects.

ASN2364E

 The action action_name ended in error because the IBMQREP_CAPPARMS table is empty.

The ASNCLP program requires a row in the IBMQREP_CAPPARMS control table before it can define objects for replication. No row was found in the table.

Please run the ASNCLP command ALTER CAPPARMS to populate the table with a row prior to performing this action.

ASN2365I

 The Q Apply schema has Q subscriptions or replication queue maps for which the source is a Classic replication server. These definitions are not displayed in the list shown here.

Q subscriptions or replication queue maps for which the source is a Classic replication server are not displayed by the Replication Center.

This message is for your information only. No action is required.

ASN2366E

 The SET command command_name cannot be used with an Oracle source server.

The specified command is not supported for Oracle sources.

Specify an ASNCLP command that is supported with Oracle sources.

ASN2367E

 The command could not be processed. Oracle servers are not supported as replication targets unless an intermediate federated server is installed and configured.

To replicate data to an Oracle target, you must configure a Q Apply program to run within a DB2 federated instance, which requires InfoSphere Federation Server.

Install and configure InfoSphere Federation Server and then use the SET SERVER command to specify a Q Apply server that is on a federated database manager instance.

ASN2368E

 The CREATE QSUB command does not support the values B or P for the SUBTYPE keyword if the source is Oracle. Bidirectional (type B) and peer-to-peer (type P) replication are not supported for native Oracle sources. The only allowed Q subscription type is unidirectional (type U). For the SUBTYPE keyword, specify the value U and reissue the command.

ASN2369E

 The load type option option cannot be used with an Oracle source. An Oracle server was specified as the Q Capture server in a prior SET SERVER command. For Oracle servers, the values 1, 2, 3, and 4 are not supported for the LOAD TYPE keyword. Take one of the following actions:
  • Issue the SET SERVER command and specify another Q Capture server where this option is supported.
  • For an Oracle source, specify the values 0 (no load) or 5 (Oracle load) for the LOAD TYPE keyword.

ASN2370E

 The action action ended in error because the architecture level of the Q Apply control tables is level and the source is an Oracle server. The Q Apply control tables need to be at a architecture level of 0905 (Version 9.5) or above to use an Oracle server as a source. The specified Q Apply schema is at a previous architecture level. Take one of the following actions:
  • Migrate the Q Apply control tables to the required architecture level.
  • Create a new set of Q Apply control tables under the required architecture level and use that schema for the specified action.

ASN2371E

 The table table_name cannot be used as a Q Replication source because table-level supplemental logging is not set.

Table-level supplemental logging should be set to ON so that Oracle maintains the required log data for replication.

Issue the ALTER command to alter the source table to enable table-level supplemental logging.

ASN2372E

 The database database_name cannot be used as a Q Replication source because database-wide supplemental logging is not enabled.

The Q Capture program uses Oracle LogMiner, which requires minimal supplemental logging to be enabled. This function logs the minimal amount of information needed for Oracle LogMiner to identify, group, and merge the redo operations from DML changes. Minimal supplemental logging ensures that Oracle LogMiner and Q Capture have sufficient information to support chained rows and various storage arrangements, such as cluster tables.

Issue the ALTER command to alter the database to enable database-wide minimal supplemental logging.

ASN2373E

 The database that was specified as a Q Capture server cannot be used as a source. Q Replication supports only Oracle version 10g and above.

To replicate data from an Oracle source, you must specify a source database that is at Oracle version 10g or later as a Q Capture server.

Specify a database that is at a supported level and retry the command.

ASN2375E

 The XML keyword was provided in the CREATE PUB command, but the publishing queue map that was specified for the publication uses a DELIMITED message format.

The message format must match between the publication and the publishing queue map that it uses.

Take one of the following actions:

  • If you want a publication with XML message format, specify a publishing queue map that uses XML format.
  • If you want a publication with DELIMITED message format, change the message format for the publication to DELIMITED.

ASN2376E

 The publishing queue map queue_map_name cannot be promoted because it does not exist within the specified Q Capture schema on the specified Q Capture server. Before you can promote an object, the object must exist within the schema that you specify. A publishing queue map with the specified name does not exist within this schema. Make sure that the correct publishing queue map, schema, and server are specified and issue the command again.

ASN2377E

 The publication publication_name cannot be promoted because it does not exist within the specified Q Capture schema on the specified Q Capture server. Before you can promote an object, the object must exist within the schema that you specify. A publication with the specified name does not exist within this schema. Make sure that the correct publication, schema, and server are specified and issue the command again.

ASN2378E

 The replication queue map queue_map_name cannot be promoted because it does not exist within the Q Capture schema Q_Capture_schema on the specified Q Capture server or within the Q Apply schema Q_Apply_schema on the specified Q Apply server. Before you can promote a replication queue map, the queue map must exist within the Q Capture and Q Apply schemas that you specify. A replication queue map with the specified name does not exist within these schemas. Make sure that the correct replication queue map, schema, and server are specified and issue the command again.

ASN2379E

 The command is not supported because the target database is accessed through a federated server. The specified command is not supported for federated targets. Specify a server where the command is supported.

ASN2380I

 The operation operation for program program_name has started for schema or qualifier name on database or subsystem name at host host_name at timestamp. The requested operation was initiated. This message is for your information only. No action is required.

ASN2381I

 The operation operation ended successfully at timestamp timestamp.

A replication or event publishing program successfully carried out the described operation.

This message is for your information only. No action is required.

ASN2383I

 The program status is status. Additional information: information. This message describes the status of a replication or event publishing program. This message is for your information only. No action is required.

ASN2384E

 The operation operation ended in error because the programprogram_name is not active. The program that was prompted to carry out the described operation was not running, so the operation could not be executed. Start the program, and then request the operation again.

ASN2385I

 The detailed status of the active program is detailed_status.

The requested status information describes the current state of the program in detail.

This message is for your information only. No action is required.

ASN2386I

 The program parameter parameter has a value of value and was defined by origin. The message reflects the parameter value that the program is currently using. This value might differ from the value that is saved in the control tables. When a program stops and restarts, it uses saved values unless you override the saved values at startup or while the program is running. This message is for your information only. No action is required.

ASN2387E

 The operation operation cannot be executed because the access method method is not available on the database or subsystem name at host host. Reason: reason. Suggested action: action. Perform the suggested action to enable this access method for future use.

The requested operation requires the stated access method to be available.

Perform the suggested action and retry the operation.

ASN2388E

 The operation was terminated at timestamp because the timeout of number seconds was exceeded. A replication or event publishing program could not carry out the requested operation within the specified time. Check the status of the program and retry the operation.

ASN2389E

 The operation operation cannot be executed because a prerequisite setup step is missing on the database or subsystem name at host host. Reason: reason. Suggested action: action. Perform the suggested action to enable this operation for future use. The requested operation requires a prerequisite setup step to be completed. Perform the suggested action to complete the prerequisite setup step and retry the operation.

ASN2390E

 An error occurred during communication with the active program program_name. Error message: message. Response: response.

An internal error occurred during communication with the replication program.

Verify your replication setup, and then retry the action.

ASN2391E

 The operation operation for the program program_name is not supported for database_type databases.

Some operations by replication programs are not supported on some database types.

Specify only those operations that are supported with this database type.

ASN2392W

 The database manager instance could not be determined. The instance name of instance_name is used as a default to perform the requested operation on the database database_name. To support other instance names for this operation, perform the suggested action action.

The database manager instance name is required to perform the operation, but the instance name cannot be determined. A default instance name is used.

If the name of the database manager instance is the same as the default, no action is necessary. Otherwise perform the suggested action.

ASN2394W

 The recommended access method method is not available to perform the operation operation on the database or subsystem name at host host_name. Reason: reason. Suggested action action. Perform the suggested action in order to make the recommended access method available for future use. A recommended method of accessing the database or subsystem was not available. An alternative method will be tried to perform the requested operation. Perform the suggested action and retry the operation.

ASN2395E

 The program program_name could not be started because an instance of this program with the same schema or qualifier is already running on the database or subsystem name. Only one program instance with a given schema or qualifier can run within a database. Either stop the running program that has the same schema or qualifier, or drop and recreate the schema or qualifier for the second program.

ASN2396E

 The operation operation ended in error because the program returned one or more error messages: error_messages.

The program received the request to perform an operation, but returned an error.

Check the error message, correct the problem, and retry the operation.

ASN2397E

 The replication queue map cannot be created because the MAXAGENTS_CORRELID value (number_agents) is greater than the NUM_APPLY_AGENTS value (total_agents). The total number of apply agents is specified by the NUM_APPLY_AGENTS value in the IBMQREP_RECVQUEUES table for a receive queue and replication queue map. The MAXAGENTS_CORRELID value specifies the number of transactions to apply in parallel from the same job name. This setting allows the Q Apply program to limit parallelism during batch workloads to prevent lock contention. Set the MAXAGENTS_CORRELID value to be lower than the NUM_APPLY_AGENTS value.

ASN2398E

 The replication queue map could not be updated because the MAXAGENTS_CORRELID value (number_agents) is greater than the NUM_APPLY_AGENTS value (total_agents). The total number of apply agents is specified by the NUM_APPLY_AGENTS value in the IBMQREP_RECVQUEUES table for a receive queue and replication queue map. The MAXAGENTS_CORRELID value specifies the number of transactions to apply in parallel from the same job name. This setting allows the Q Apply program to limit parallelism during batch workloads to prevent lock contention. Set the MAXAGENTS_CORRELID value lower than the NUM_APPLY_AGENTS value.

ASN2399E

 The table capture_schema.IBMQREP_IGNTRAN table does not have a row. Your configuration requires that a row exists and that the row contains the authorization ID for the Q Apply program. You are using the peer-to-peer configuration with value-based conflict detection. This configuration requires that the IBMQREP_IGNTRAN table be populated with the authorization ID of the Q Apply program so that the Q Capture program can ignore the transactions and avoid recursion. Specify the ALTER SERVER ADD IGNORE TRANSACTIONS command.

ASN2400I

 A row with the specified information already exists in the capture_schema.IBMQREP_IGNTRAN table. An SQL script to insert the ignore-transactions specification is not generated.

The command did not generate a SQL script because a row already exists.

This message is for your information only. No action is required.

ASN2401I

 A row with the specified information does not exist in the capture_schema.IBMQREP_IGNTRAN table. An SQL script to delete the ignore-transactions specification is not generated.

The command did not generate a SQL script because a row does not exist in the IBMQREP_IGNTRAN table.

This message is for your information only. No action is required.

ASN2402E

 The command command is only supported for Q Replication and event publishing.

The specified command is not applicable to SQL Replication.

Specify the environment by using the ASNCLP SESSION SET TO Q REPLICATION command before using this command.

ASN2403E

 The specified source table owner.table_name does not have any subscriptions or publications in the capture schema capture_schema. The ALTER ADD COLUMN command did not add a signal into the IBMQREP_SIGNAL table.

The command failed because subscriptions or publications for the specified source table do not exist.

Check the source table name and reissue the command.

ASN2404E

 The column column_name is already subscribed for the subscription or publication sub_name for the provided source table owner.table_name. Because the column is already subscribed for the subscription or publication, the column cannot be added. If the wrong table or column name was specified, correct the statement and reissue the command. Otherwise, no action is required.

ASN2405W

 The referential integrity constraints constraint_name do not match for the source table owner.src_table_name and target table owner.tgt_table_name. The referential integrity constraints for the source and target tables for bidirectional and peer-to-peer subscriptions must exactly match. Because the constraints do not match for the source and target tables, you might have experience problems with the Q Apply program. If the mismatched constraints will not cause problems while running the Q Apply program, no action is necessary. Otherwise, ensure that the referential integrity constraints on the source and target tables match before running the replication programs.

ASN2406W

 The check constraints constraint_name do not match for the source table owner.src_table_name and target table owner.tgt_table_name. The check constraints for the source and target tables for bidirectional and peer-to-peer subscriptions must exactly match. Because the constraints do not match for the source and target tables, you might experience problems with the Q Apply program. If the mismatched constraints will not cause problems while running the Q Apply program, no action is necessary. Otherwise, ensure that the check constraints on the source and target tables match before running the replication programs. Scripts were generated because you set enforcement of constraints matching to 'no.'

ASN2407W

 The unique constraints constraint_name do not match for the source table owner.src_table_name and target table owner.tgt_table_name. The unique constraints for the source and target tables for bidirectional and peer-to-peer subscriptions must exactly match. Because the constraints do not match for the source and target tables, you might have experience problems with the Q Apply program. If the mismatched constraints will not cause problems while running the Q Apply program, no action is necessary. Otherwise, ensure that the unique constraints on the source and target tables match before running the replication programs.

ASN2408W

 The target member target_owner-target_table in the subscription set subs_set_name is an external consistent-change data (CCD) table. This table type does not require a join of the changed-data (CD) and unit-of-work (UOW) tables to populate the LOGMARKER column. You specified a non-zero commit count value for the subscription set. If you use this CCD table as a source in a three-tier distribution and the block factor is non-zero, data loss problems might result while running the Apply program.

Because the CCD target type is '9,' the Apply program will not perform a join of the CD and UOW tables to get a value for the LOGMARKER column. You specified a non-zero value for the commit count when you created the subscription set. If this CCD table is used as a source in the second tier, you should specify zero for the blocking factor or MAX_SYNCH_MINUTES column in the IBMSNAP_SUBS_SET table for the subscription set.

Specify zero for the blocking factor or the MAX_SYNCH_MINUTES column in the IBMSNAP_SUBS_SET table.

ASN2410E

 The keyword GENERATE SQL FOR EXISTING is not supported in SQL Replication.

The GENERATE SQL FOR EXISTING option causes the SET RUN SCRIPT command to ignore certain errors when generating SQL script. This option is supported only in Q Replication. However, the current session is SQL Replication.

Remove the GENERATE SQL FOR EXISTING keyword from the input file.

ASN2411W

 The object object_name of type object_type already exists under the specified Q Capture schema. A script to create the object has been generated regardless, because the option to ignore errors while generating the script was chosen.

Data already exists in the Q Capture control tables for the publication or publication queue map with this name. The SQL for creating the object has been generated regardless, because the GENERATE SQL FOR EXISTING YES option was set in the SET RUN SCRIPT LATER command. Running this generated SQL against the given control tables will cause SQL errors.

No action is needed.

ASN2412W

 The object object_name of type object_type already exists under the specified Q Capture schema and Q Apply schema. A script to create the object has been generated regardless, because the option to ignore errors while generating the script was chosen.

Data already exists in the control tables for Q Capture or Q Apply for the subscription or replication queue map with this name. The SQL for creating the object has been generated regardless, because the GENERATE SQL FOR EXISTING YES option was set in the SET RUN SCRIPT LATER command. Running this generated SQL against the given control tables will cause SQL errors.

No action is needed.

ASN2413W

 The database object object_name of type object_type already exists at the server server_alias. A script to create the object has been generated regardless, because the option to ignore errors while generating the script was chosen.

The table, tablespace, or index already exists in the database. The SQL to create this object has been generated regardless, because the GENERATE SQL FOR EXISTING YES option was set in the SET RUN SCRIPT LATER command. Running this generated SQL against the given database will cause SQL errors.

No action is needed.

ASN2414W

 The value of the parameter_name parameter of the WebSphere MQ model queue host_name-queue_manager_name-queue_name is too low. The value is set to value1 but the required value must be at least value2.

The model queue for the spill queue for the Q Apply program needs to have the following parameter values:

  • Maximum queue depth (MAXDEPTH): 500000 or higher
  • Maximum message size (MAXMSGL): 100000 or higher

Update the model queue parameter values, or specify a model queue that has the correct parameter values.

ASN2415E

 The load type load_type is not valid for the Q subscription name because the same target table table_owner.table_name is participating in another Q subscription name that has a conflicting load type of load_type. Either the wrong target table name was specified for the Q subscription, or the specified load type is incorrect. Target tables that are populated from multiple source tables (this process is often called data consolidation) require certain load types. If the target table name is correct, then at least one existing Q subscription has a load type that replaces all contents in the table (type 4 or 5). If two or more Q subscriptions were to replace data in the target table, a loss of data could occur. Take one of the following actions:
  • Correct the target table name if the wrong one was specified.
  • Change the selection of the load type to use select and load with insert (104) or select and import with insert (105).

ASN2416E

 The load type load_type is supported only for Q subscriptions where the Q Capture server is a Classic server. The command failed. Load types 4 (Select and load with replace), 104 (Select and load with insert), 5 (Select and import with replace), and 105 (Select and import with insert) are only supported where the source is a Classic server. Choose a different load option and rerun the command.

ASN2417E

 Use the replication administration tools to start the Q subscription name.

The target table that was specified for the Q subscription is the same as the target table for one or more other Q subscriptions. The Q Apply program does not start these Q subscriptions automatically because one of them has a load type (4 or 5) that replaces all data in the target table. The Q subscription must be started before the other Q subscriptions that specify the same target table to ensure no loss of data.

The Q subscription is using one of the following load types:

104

Select and load with insert

5

Select and import with replace

105

Select and import with insert

The Q subscriptions need to be started in a particular order so there is no loss of data. The option to manually start the Q subscription was specified for this Q subscription.

Use the Q Replication Dashboard, ASNCLP command-line program, or Replication Center to start the Q subscription. For details see, "Starting Q subscriptions."

ASN2418E

 The load type load_type is not valid when HAS LOAD PHASE is set to value. The HAS LOAD PHASE value was specified as N, indicating that the target table is not loaded. However, a load type value greater than 0 was specified. Take one of the following actions:
  • If you want Q Apply to load the target table, pick a HAS LOAD PHASE value of I.
  • If you do not want Q Apply to load the target table, keep the HAS LOAD PHASE value as N and remove the LOAD TYPE option from the CREATE QSUB command.

ASN2419E

 An unexpected value value was found in column column_name of replication control table table_name. The specified control table contains at least one value that prevents processing of the current action. The table might have been updated with SQL that was not generated by the Replication Center or ASNCLP. Use one of the replication administration tools to drop and recreate the object with the unexpected value. For example, if the object is a Q subscription, drop and recreate it.

ASN2420I

 The replication key was defined to include all of the selected target columns because no primary key, unique constraint, or index was found on both the source and the target table within the range of the replicated columns.

If no primary key, unique constraint, or index are found on the source or target, the administration tool automatically specifies all valid replicated columns as key columns for replication. Some subscribed columns, such as LOB columns, cannot be used as keys.

This message is for your information only. No action is required.

ASN2421W

 The column column_name is automatically excluded from the Q subscription.

Columns defined as ROWID and GENERATED ALWAYS are excluded automatically from bidirectional and peer-to-peer Q subscriptions.

This message is for your information only. No action is required.

ASN2422E

 The source|target database or subsystem that was provided in the SET SERVER command for the Q subscription does not match the source|target database or subsystem that is associated with the replication queue map queue_map_name for the Q subscription.

The source and target servers that are specified for a Q subscription must be the same as the source and target servers for the queue map that used to define the Q subscription.

To determine the name of the server that was specified for the queue map, use the Replication Center or view the CAPTURE_SERVER column in the IBMQREP_RECVQUEUES table or the APPLY_SERVER column in the IBMQREP_SENDQUEUES table. Use this value in the SET SERVER command.

ASN2423E

 The CREATE QSUB command failed because the source table table_owner.table_name that was specified has a primary key but does not have a unique index on the key columns.

DB2 for z/OS tables with a primary key must also have a unique index on the primary key columns. Otherwise, the table definition is incomplete and the ASNCLP cannot create a Q subscription for the table.

Create a unique index on the appropriate primary key columns in the source table, and retry the command.

ASN2424E

 The option to specify the release level of the replication control tables on server server_name is not available because the server is on z/OS or an Oracle source database. The script for creating control tables was not generated.

The ability to specify the release, or architecture level, of the Q Capture or Q Apply control tables is only supported on DB2 for Linux, UNIX, and Windows.

Redefine the control tables, making one of the following changes:

ASNCLP command-line program

Omit the RELEASE keyword in the CREATE CONTROL TABLES FOR command.

Replication Center

Do not change the Q Capture release in the Create Q Capture Control Tables wizard or Q Apply release in the Create Q Apply Control Tables wizard.

ASN2425E

 Generating the script for creating Q Capture or Q Apply control tables failed because the specified release level is older than the release level of the DB2 database. Release level specified: specified-release-level. Server name: server-name. DB2 database release level: DB2-release-level.

The release, or architecture level, that is specified for creating Q Capture or Q Apply control tables must match or be newer than the release of the database manager instance where the control tables are being created.

Redefine the control tables, specifying a release that is the same or newer than the DB2 database.

ASN2426I

 ASNCLP : The input clause input_parameter is ignored on native z/OS platforms.

Some input parameters are not needed when the ASNCLP program runs on z/OS platforms with JCL:

  • The SET OUTPUT MULTIDIR command for bidirectional and peer-to-peer replication is superseded by DD statements that reference locations where the appropriate source and target SQL statements are written.
  • The LOAD MULTIDIR REPL SCRIPT command is superceded by DD statements that reference the location of the ASNCLP input script for setting up bidirectional or peer-to-peer replication.
  • The PASSWORD keyword is not used because user authentication is handled through the communications database (CDB).

This message is for your information only. No action is required.

ASN2427E

 ASNCLP : The -EXE keyword is not supported on native z/OS platforms.

When the ASNCLP program runs on z/OS platforms with JCL, the execute-immediately mode that is indicated by the -EXE keyword is not supported.

Provide the commands in an input file that is executed with JCL.

ASN2428E

 The database alias alias that was retrieved from the CAPTURE_ALIAS column of the IBMQREP_CAPPARMS table does not match the alias alias that was specified to connect to the database.

The CAPTURE_ALIAS column stores the alias information that was used to connect to the database when the Replication Center or ASNCLP command-line program was used to create Q Capture control tables. However, the alias that is stored in the column does not match the alias that was used for the current database connection. This situation can happen if the database was cataloged with one alias on the system where the tools were used, and later cataloged on a different system by using a different alias.

Catalog the database again and use the same alias that was used when control tables were created.

ASN2429I

 ASNCLP : The DB2 subsystem subsystem_ID is used for the default connection.

The stored procedure SYSPROC.ADMIN_INFO_SSID returned the name of the communications database (CDB) to which the ASNCLP first connects. Use this CDB to set up connectivity information for replication source and target servers to which the ASNCLP needs to connect.

This message is for your information only. No action is required.

ASN2430W

 You mapped a source table column with a CHAR data type to a target table column with the Informix Boolean data type. Ensure that only the following values are inserted or updated into the source column: t, f, and NULL. These are the only allowed values for the Informix Boolean type. The Informix Boolean column in the target table only accepts the values t, f, and NULL. The t and f are not case sensitive, so T and F are also allowed. Any other values that are inserted or updated into the source column that is mapped to the Boolean column will cause an error at the target. If you expect to insert or update any values other than t, f, or NULL into the source column, map the column to a target column that does not use the Informix Boolean data type.

ASN2431E

 The Q subscription Q_subscription_name cannot be created because the Q Capture program's compatibility level compatibility_level is higher than the Q Apply program's architecture level arch_level.

An older version of the Q Apply program can only work with a newer version of the Q Capture program if the value of the COMPATIBILITY column in the IBMQREP_CAPPARMS table matches the Q Apply version, which is saved in the ARCH_LEVEL column in the IBMQREP_APPLYPARMS table.

Change the Q Capture COMPATIBILITY value to match the version of the Q Apply program, or upgrade the Q Apply program to the same version as the Q Capture program.

ASN2432E

 The Q Capture program's architecture level arch_level at server capture_server and schema capture_schema does not match the Q Apply architecture level arch_level at server apply_server and schema apply_schema. The Q subscription cannot be created or started.

Either the Q Capture program or Q Apply program is at Version 9.7, and the other program is at an older version. In a multidirectional replication configuration, all of the programs must be at the same version. The ARCH_LEVEL and COMPATIBILITY columns in the IBMQREP_CAPPARMS table must match the value of the ARCH_LEVEL column in the IBMQREP_APPLYPARMS table.

Upgrade the down-level Q Capture or Q Apply program to Version 9.7 or to the equivalent PTF on z/OS, and then create or start the Q subscription.

ASN2433E

 Q Capture program's architecture level arch_level at server capture_server and schema capture_schema is identical to the Q Apply architecture level arch_level at server apply_server and schema apply_schema. However, the compatibility level compatibility_level at the Q Capture server is at a lower level. The Q subscription cannot be created or started.

In a multidirectional replication configuration, the values of the ARCH_LEVEL column in the IBMQREP_APPLYPARMS table and the values of the ARCH_LEVEL and COMPATIBILITY columns in IBMQREP_CAPPARMS table must all match.

Update the value of the COMPATIBILITY column to match the Q Apply and Q Capture ARCH_LEVEL columns, then create or start the Q subscription.

ASN2434I

 ASNCLP : ASNCLP is unable to retrieve the subsystem identifier (SSID) of the DB2 subsystem that is used for the default connection. SQLCODE sql_code.

On native z/OS platforms, the ASNCLP calls the SYSPROC.ADMIN_INFO_SSID stored procedure to return the name of the communications database (CDB) that the program uses for connectivity to source and target servers. The stored procedure might not be installed, or the ASNCLP does not have the EXECUTE privilege on the stored procedure.

Ensure that SYSPROC.ADMIN_INFO_SSID is installed and that the user ID that runs the ASNCLP has the correct privileges to execute the procedure.

ASN2435E

 ASNCLP : The input clause input_parameter is not allowed on native z/OS platforms.

On native z/OS platforms, the ASNCLP uses the SET BIDI NODE SERVER or SET PEER NODE SERVER commands to specify the paired Q Capture and Q Apply programs at each server for bidirectional or peer-to-peer replication. The SET SERVER MULTIDIR command is not used on native z/OS.

Use the SET BIDI NODE SERVER or SET PEER NODE SERVER command.

ASN2436E

 The database alias alias that was retrieved from the APPLY_ALIAS column of the IBMQREP_APPLYPARMS table does not match the alias alias that was specified to connect to the database.

The APPLY_ALIAS column stores the alias information that was used to connect to the database when the Replication Center or ASNCLP command-line program was used to create Q Apply control tables. However, the alias that is stored in the column does not match the alias that was used for the current database connection. This situation can happen if the database was cataloged with one alias on the system where the tools were used, and later cataloged on a different system by using a different alias.

Catalog the database again and use the same alias that was used when control tables were created.

ASN2437E

 A Q subscription cannot be created because the Q Capture control tables are at architecture level arch_level, which is not supported by the Q Apply architecture level arch_level on Linux, UNIX, and Windows, or by Q Apply on z/OS at any architecture level.

When the Q Capture program is at Version 9.8 (a value of 0908 in the ARCH_LEVEL column of the IBMQREP_CAPPARMS table), replication is only supported when the Q Apply control tables are in a DB2 for Linux, UNIX, or Windows database that is at Version 9.7 Fix Pack 2 or higher.

Take one of the following actions depending on the location of the Q Apply control tables:

DB2 for Linux, UNIX, and Windows

Upgrade the database manager to V9.7 Fix Pack 2 or later.

DB2 for z/OS

Use a pre-V9.8 Q Capture program in the configuration.

ASN2438E

 The Q subscription cannot be created because the Q Capture program is at Version version and the value of the COMPATIBILITY column in the IBMQREP_CAPPARMS table is current_value. The expected value for COMPATIBILITY is expected_value.

When the Q Capture program is at the specified architecture level (as recorded in the ARCH_LEVEL column of the IBMQREP_CAPPARMS table), the value of the COMPATIBILITY column must be the expected value that is shown in the message text.

Use the Q Replication Dashboard, Replication Center, or SQL to update the value of the COMPATIBILITY column.

ASN2439E

 The same queue manager name name was provided for queue managers that are on two different systems. Queue manager names must be unique across the network. The command failed.

WebSphere MQ requires that queue managers that are connected within a network have unique names even when they are on different systems.

Provide a unique queue manager name or let the CREATE MQ SCRIPT command pick a unique queue manager name by not specifying the queue manager name in the QMANAGER keyword.

ASN2440E

 The Replication Center cannot obtain the DB2 for z/OS subsystem ID because the SYSPROC.ADMIN_INFO_SSID stored procedure is not installed.

The Replication Center uses the subsystem ID to connect to DB2 for z/OS to create control tables or perform other tasks. The stored procedure for providing the subsystem ID is SYSPROC.ADMIN_INFO_SSID. On DB2 for z/OS Version 10, SYSPROC.ADMIN_INFO_SSID is installed by default. On DB2 for z/OS version 8 and Version 9, the job to install the SYSPROC.ADMIN_INFO_SSID stored procedure is DSNTIJSG.

Install the SYSPROC.ADMIN_INFO_SSID stored procedure at the source or target subsystem, and then retry the action.

ASN2441E

 The CREATE QSUB command does not support the option REPLICATE ADD COLUMN if the source or target DB2 subsystem is earlier than Version 10.

The REPLICATE ADD COLUMN function is valid only if both the source and target are at DB2 for z/OS Version 10 or later.

Either specify both a source and target subsystem that are at Version 10 or later, or do not specify the REPLICATE ADD COLUMN keywords.

ASN2442E

 The action action_name cannot be completed because the required information for the bidirectional or peer-to-peer node node_number was not provided in an earlier command.

The CREATE CONTROL TABLES or CREATE REPLQMAP commands contain a reference to a node number. The node number is used to identify the servers that are involved in bidirectional or peer-to-peer replication. However, the node information was not set in a prior SET BIDI NODE or SET PEER NODE command.

Issue the SET BIDI NODE or SET PEER NODE command to identify the server with a node number before specifying the node number in the CREATE CONTROL TABLES and CREATE REPLQMAP commands.

ASN2443W

 The target table table_owner.table_name contains a BUSINESS_TIME WITHOUT OVERLAPS (BTWO) clause in its primary key or unique constraint specification, but the source table table_owner.table_name does not have the same option. The Q Apply program might encounter errors.

The target is defined with a BUSINESS_TIME period clause that uses the WITHOUT OVERLAPS option. With this option, the BUSINESS_TIME period value for a matching key cannot be overlapped. If the source table contains overlapped BUSINESS_TIME values, the Q Apply program will receive SQL errors when it applies these changes to the target table.

Drop the primary key or unique constraint on the target table and redefine it without the WITHOUT OVERLAPS option.

ASN2444E

 The source table table_owner.table_name is not a system period temporal table or bitemporal table, nor is versioning enabled for the table. A Q subscription or subscription-set member will not be created for the history table.

The attempt to create a Q subscription or subscription-set member for the history table failed because the source table is not a system period temporary table, bitemporal table, or a table with versioning enabled. Therefore, the source table does not have a history table.

Take one of the following actions:

  • Alter the source table by specifying the ADD PERIOD SYSTEM_TIME and ADD VERSIONING USE HISTORY TABLE clauses, and then reissue the CREATE QSUB or CREATE MEMBER command.
  • Do not specify INCLUDE HISTORY TABLE when creating the Q subscription or subscription-set member.

ASN2445E

 The attempt to create a Q subscription or subscription-set member for the source table table_owner.table_name failed. The source table has a SYSTEM_TIME or BUSINESS_TIME period defined, but the target table table_owner.table_name does not have a SYSTEM_TIME or BUSINESS_TIME period defined.

A Q subscription or subscription-set member cannot be created unless both the source and target table are correctly defined. In order to define a temporal table on the target, either a SYSTEM_TIME or BUSINESS_TIME period must be defined.

Define a SYSTEM_TIME or BUSINESS_TIME period on the target table by using the ALTER TABLE statement, and then reissue the CREATE QSUB or CREATE MEMBER command.

ASN2446W

 No period period_name exists on the source table table_owner.table_name. The PERIOD keyword that was used in the CREATE QSUB or CREATE MEMBER command is ignored.

You can only use the PERIOD keyword when you are subscribing a table that has a SYSTEM_TIME or BUSINESS_TIME period defined.

Do not specify the PERIOD clause when creating a subscription, or define a period on the source table and then reissue the command.

ASN2447W

 The target temporal table table_owner.table_name has versioning enabled even though the source history table table_owner.table_name is part of a Q subscription or subscription-set member. SQL conflicts might occur when rows are applied to the target table.

The versioning attribute on the temporal table at the target causes the database manager to update the table in addition to updates that are made by the Q Apply or Apply program. This can cause SQL conflicts at the table.

Either remove the subscription on the history table or perform an ALTER TABLE to remove versioning on the target temporal table.

ASN2448E

 The ASNCLP program could not create a history table for the target table table_owner.table_name because no name was specified for the history table in the CREATE QSUB or CREATE MEMBER command.

To create a Q subscription or subscription-set member for a temporal table, the target table must either already have a history table, or you must provide a name for the history table so the ASNCLP program can create the history table.

Specify a name that can be used to create the target history table or create a history table for the target table. Then reissue the command.

ASN2449E

 An error occurred while trying to generate the DataStage definition (.dsx) files that create jobs to read from a consistent-change data (CCD) table. The files were not created. Reason code: reason_code.

One of the following problems, identified by a reason code, caused the generation of the .dsx files to fail:

1

The IBMSNAP_FEEDETL control table does not exist at the Apply control server. This table is required to identify SQL Replication subscription sets with at least one CCD table member that is read by IBM InfoSphere DataStage.

2

The subscription set does not include any member CCD tables that are noncondensed and noncomplete.

Review the reason codes in the explanation, and take the appropriate action:

1

Create the IBMSNAP_FEEDETL control table manually by using the sample in the SQLLIB/samples/repl/sql directory and regenerate the .dsx file.

2

Ensure that the subscription set has at least one member CCD table that is noncondensed and noncomplete.

ASN2450E

 Stored procedure target are not supported when either the Q Capture control tables or Q Apply control tables are at arch_level architecture level.

When the version of the control tables at the source or target is 0908 (Version 9.8), replication to stored procedure targets is not supported.

Select a different target type.

ASN2451E

 The ERROR ACTION 'B' is not supported when the target table is on Linux, UNIX, or Windows.

The value 'B' for the ERROR ACTION keywords in the CREATE QSUB command prompts the Q Apply program to spill change messages for the Q subscription to a temporary spill queue when an error occurs. ERROR ACTION 'B' is only supported for z/OS target tables.

Choose a different value for ERROR ACTION and rerun the CREATE QSUB command.

ASN2458E

 The value B for the ERROR ACTION keyword in the CREATE QSUB command is not supported when the source or target table has referential integrity constraints.

You can specify B for ERROR ACTION to prompt the Q Apply program to put change messages for the Q subscription in a temporary spill queue when an SQL error occurs and until the error is resolved. However, the B value is not supported when the source or target table for the Q subscription is involved in a referential integrity relationship with other tables.

Specify a different value for ERROR ACTION and resubmit the CREATE QSUB command.

ASN2459E

 The target nickname nickname_owner.nickname_name references a table on the remote server remote_server but the Q Apply control table nicknames reference control tables on a different remote server remote_server. The target nickname and Q Apply control table nicknames must point to the same remote server.

The target nickname and the Q Apply control table nicknames must reference tables on the same remote server because the Q Apply program updates the nickname target and some control tables in the same commit scope and the federated wrapper does not support two-phase commit.

Take one of the following actions and then retry the CREATE QSUB command:

  • Create a target nickname that points to the same remote server as the Q Apply control tables.
  • Let the ASNCLP program create the nickname by not specifying the EXIST clause.

ASN2460E

 A Q subscription could not be created for source table table_owner.table_name because the LOAD from CURSOR option was specified but no nickname was provided. The LOAD from CURSOR option that uses a cataloged DB2 alias instead of a nickname is not available because the Q subscription includes one or more XML columns.

The Q subscription specifies that the Q Apply program should load the target table (automatic load) by using the LOAD from CURSOR utility. However, this utility cannot be used.

This message is returned when the target database is at Version 9.7 Fix Pack 4 or later and no nickname is provided.

In DB2 pureScale environments only:

Because the DB2 pureScale Feature is not supported in a federated environment, the LOAD from CURSOR utility can use an alias instead of a nickname in a DB2 pureScale environment. However, the LOAD from CURSOR utility cannot use an alias if the Q subscription includes one or more XML columns. This message is returned in a DB2 pureScale environment when no nickname is provided and there are one or more XML columns in the Q subscription.

Recreate the Q subscription, specifying a nickname for the LOAD FROM CURSOR option, or select a different load option such as "Best available: Let the Q Apply program choose a load option" in the Replication Center (LOAD TYPE 0 in the ASNCLP command-line program) or the EXPORT and IMPORT combination of utilities.

In DB2 pureScale environments only:

Recreate the Q subscription, specifying a different load option such as "Best available: Let the Q Apply program choose a load option" in the Replication Center (LOAD TYPE 0 in the ASNCLP command-line program) or the EXPORT and IMPORT combination of utilities.

ASN2461E

 LOAD from CURSOR was chosen for the Q subscription (LOAD TYPE 1) but the keywords to specify a nickname for the source table were not provided in the CREATE QSUB command. The source server server_name is at version version and this version requires a source nickname for LOAD from CURSOR.

At the specified server level, the LOAD from CURSOR option requires a nickname for the source table. Nicknames are not required for Version 9.7 Fix Pack 4 and later.

Use the NICKNAME or NEW NICKNAME RMT SERVERNAME keywords to specify an existing or new nickname and reissue the CREATE QSUB command.

ASN2462E

 The CREATE QSUB command specifies to create multiple Q subscriptions that use the LOAD from CURSOR option with a nickname for the source table. However, only a single nickname nickname_owner.nickname_name was specified for the source table.

When you create multiple Q subscriptions, it is recommended that you use the NAMING PREFIX option with the NEW NICKNAME RMT SERVERNAME keywords so that the ASNCLP program can generate a unique nickname for each source table.

Modify the CREATE QSUB command to use the NAMING PREFIX option and reissue the command.

ASN2463E

 The command command is not supported because one or more of the servers in your configuration is a DB2 for z/OS subsystem or pre-Version 10 DB2 for Linux, UNIX, and Windows database.

The provided command is only supported if all the databases that are involved in the configuration are on DB2 for Linux, UNIX, and Windows Version 10 or higher.

Reissue the command on a DB2 for Linux, UNIX, and Windows database at Version 10 or higher.

ASN2464E

 A schema-level Q subscription cannot be created for schema schema_name because a schema-level Q subscription already exists for another schema existing_schema that uses the same queue map queue_map_name, and these two schemas overlap.

The expression that was used to select schemas for the schema-level Q subscription overlaps or conflicts with the schema of an existing schema-level Q subscription. Overlapping schemas are not supported. For example, if a schema-level Q subscription is created for schema pattern "ANU%".T%, you cannot create another schema-level Q subscription for pattern "ANU1"."T%" that uses the same replication queue map.

Provide a different expression that does not overlap with existing schema-level Q subscriptions or drop the existing schema-level Q subscription and reuse this expression.

ASN2465E

 A schema-level Q subscription of configuration type configuration_type cannot be created for schema schema because table-level Q subscriptions for some tables that belong to this schema already exist under a different configuration type configuration_type and use the same replication queue map queue_map_name.

Q subscriptions that belong to a schema-level Q subscription and use the same replication queue map should all be of the same configuration type (unidirectional, bidirectional, or peer-to-peer).

Drop the existing Q subscription before creating the schema-level Q subscription.

ASN2466E

 A schema-level Q subscription of configuration type configuration_type cannot be created for schema schema because table-level Q subscriptions for some tables that belong to this schema have the same configuration type and use the same replication queue map queue_map_name, but have different values for properties such as conflict action and conflict rule.

Table-level Q subscriptions that belong to the same schema-level Q subscription, have the same configuration type (unidirectional, bidirectional, or peer-to-peer), and use the same replication queue map must have the same conflict action and conflict rule.

Drop the existing Q subscriptions before creating the schema-level Q subscription.

ASN2467E

 The name name that was provided to identify the list of Q subscription options for Q subscription type type cannot be used because another list of Q subscription options with the same name already exists for Q subscription type type at server server_name under Q Capture schema schema.

The CREATE SUBSCRIPTION OPTIONS command sets options for all Q subscriptions of a given configuration type (unidirectional, bidirectional, or peer-to-peer) within a given schema. The name for the list of options must be unique for a Q Capture schema.

Provide a different name for the list of options and reissue the command.

ASN2468W

 The table table_owner.table_name matches the provided schema pattern schema_pattern and source table pattern table_pattern but is already part of a Q subscription. The SCHEMA_SUBNAME column for this Q subscription will be updated to schema_subname.

A table-level Q subscription cannot be created for the provided table because one already exists. But the SCHEMA_SUBNAME column in the IBMQREP_SUBS and IBMQREP_TARGETS tables will be updated to the provided value to make this Q subscription part of the schema-level Q subscription.

This message is for your information only. No action is required.

ASN2469W

 The option TARGET EXISTS VALIDATION NO was chosen and so the ASNCLP program will assume that the source and target tables are identical and will not perform any checks on source and target tables.

When the option TARGET EXISTS VALIDATION NO is chosen, the ASNCLP program does not perform any checks such as whether the target table exists, whether the column mappings are compatible between the source and target tables, and whether constraints match between source and target tables. The ASNCLP program will only generate the insert statements into the control tables to create the Q subscription.

To avoid problems with the Q Capture and Q Apply programs, make sure that the target table exists and that the source and target tables are identical before using this option.

ASN2470E

 The options name options_name that was specified in the OPTIONS clause in the CREATE SCHEMASUB or CREATE QSUB command does not exist.

The options name identifies a set of options for all table-level Q subscriptions within a schema-level Q subscription. A row that is identified by the options name should exist in the IBMQREP_SUBS_PROF table before table-level Q subscriptions can be created using the specified attributes.

Issue a CREATE SUBSCRIPTION OPTIONS command to first create the options before using the options name in the CREATE SCHEMASUB or CREATE QSUB command. If the CREATE SUBSCRIPTION OPTIONS command is already specified in the input file, make sure that the SET RUN SCRIPT NOW command is used to run the generated script immediately.

ASN2471E

 The type type of the Q subscription that was specified in the CREATE SUBSCRIPTION OPTIONS command with the options name options_name does not match the Q subscription type type that was specified in the CREATE SCHEMASUB or CREATE QSUB command.

The Q subscription types (unidirectional, bidirectional, or peer-to-peer) should match between the CREATE SUBSCRIPTION OPTIONS command and the CREATE SCHEMASUB or CREATE QSUB commands that use the options. Otherwise, the Q subscription properties might be incompatible.

Provide another options name that has the same Q subscription type that was specified in the CREATE SCHEMASUB or CREATE QSUB command. You can also omit the OPTIONS clause and the ASNCLP program will pick the product defaults for that Q subscription type.

ASN2472I

 The START SCHEMASUB command was processed for schema-level Q subscription name. A CAPSTART signal will be inserted into the schema.IBMQREP_SIGNAL table for number Q subscriptions that are part of the schema-level Q subscription.

The START SCHEMASUB command was issued with the ALL option. All Q subscriptions that belong to the schema-level Q subscription in new and inactive state are activated.

This message is for your information only. No action is required.

ASN2473I

 The START SCHEMASUB command was processed for schema-level Q subscription name. A CAPSTART signal was inserted into the schema.IBMQREP_SIGNAL table for the schema-level Q subscription.

A CAPSTART signal was inserted to activate the specified schema-level Q subscription. The Q Capture program will start capturing changes for source tables that are part of the schema-level Q subscription.

This message is for your information only. No action is required.

ASN2474I

 The START SCHEMASUB command was processed for schema-level Q subscription name. A CAPSTART signal was not inserted into the schema.IBMQREP_SIGNAL table for the schema-level Q subscription because the Q Capture program is already capturing changes for source tables that are part of the schema-level Q subscription.

The schema-level Q subscription is alreadly in active state. No script is generated to start the schema-level Q subscription.

This message is for your information only. No action is required.

ASN2475I

 The STOP SCHEMASUB command was processed for schema-level Q subscription name. A CAPSTOP signal was inserted into the schema.IBMQREP_SIGNAL table for number table-level Q subscriptions that belong to the schema-level Q subscription.

The STOP SCHEMASUB command was issued with the ALL option. All active Q subscriptions that belong to the schema-level Q subscription are deactivated.

This message is for your information only. No action is required.

ASN2476I

 The STOP SCHEMASUB command was processed for schema-level Q subscription name. A CAPSTOP signal was inserted into the schema.IBMQREP_SIGNAL table for the schema-level Q subscription.

In response to the STOP SCHEMASUB command, the ASNCLP program generated a SQL script to insert a CAPSTOP signal. The signal prompts the Q Capture program to stop capturing changes for all source tables within the schema.

This message is for your information only. No action is required.

ASN2477I

 The STOP SCHEMASUB command was processed for schema-level Q subscription name. However, a CAPSTOP signal was not inserted into the schema.IBMQREP_SIGNAL table because the schema-level Q subscription is already in inactive state.

Because the schema-level Q subscription is already inactive, the ASNCLP program did not generate a script to stop the schema-level Q subscription.

This message is for your information only. No action is required.

ASN2478E

 A schema-level Q subscription with name name does not exist at the server server under schema schema. No script is generated.

The schema-level Q subscription that was specified in the DROP SCHEMASUB command does not exist in the IBMQREP_SCHEMASUBS table and cannot be deleted.

Provide an existing schema-level Q subscription name and reissue the command.

ASN2479I

 Number table-level Q subscriptions that belong to the schema-level Q subscription name will be deleted.

The DROP SCHEMASUB command was issued with the ALL option. All table-level Q subscriptions that belong to the schema-level Q subscription will be deleted.

This message is for your information only. No action is required.

ASN2480E

 The provided list of Q subscription options options_list does not exist at server server_name under Q Capture schema schema and cannot be deleted.

The IBMQREP_SUBS_PROF table stores the user-defined options for all Q subscriptions of a given type within a schema-level Q subscription. A row with the provided options name cannot be found in the IBMQREP_SUBS_PROF table. No SQL script is generated to delete the options list.

Provide a different name for the options list and rerun the DROP SUBSCRIPTION OPTIONS command.

ASN2481E

 The set of Q subscription options options_name cannot be deleted because one or more schema-level Q subscriptions are using the options.

The Q Capture and Q Apply programs refer to the saved list of Q subscription options to create new Q subscriptions for schema-level Q subscriptions that use this options name. If the options list is deleted, errors will occur for the running replication programs.

Provide the name of a different set of Q subscription options to delete, or delete any schema-level Q subscriptions that are using the options and then delete the options.

ASN2482I

 The MQDEFAULTS option to pick default values for WebSphere MQ objects was chosen in the CREATE CONTROL TABLES command. The ASNCLP program will assign the following defaults: queue manager: queue_manager; administration queue: admin_queue; restart queue: restart_queue.

When the MQDEFAULTS option is specified, the ASNCLP program creates control tables with the same defaults for WebSphere MQ objects that are generated by the CREATE MQ SCRIPT command.

This message is for your information only. No action is required.

ASN2483I

 The MQDEFAULTS option to pick default values for WebSphere MQ objects was used in the CREATE REPLQMAP command. The ASNCLP program will assign the following defaults: administration queue: admin_queue; receive queue: recv_queue; send queue: send_queue.

When the MQDEFAULTS option is specified, the ASNCLP program creates a replication queue map with the same defaults for WebSphere MQ objects as the defaults that are generated by the CREATE MQ SCRIPT command.

This message is for your information only. No action is required.

ASN2484W

 The option to drop control tables on the server that is specified by node number number was chosen, but the control table table_name does not exist at server server_name under the specified schema schema.

The command specifies that the ASNCLP program should drop both Q Capture and Q Apply control tables at the server that is identified by the node number. However, the action cannot be carried out because both Q Capture and Q Apply control tables do not exist.

Provide a different schema that has both Q Capture and Q Apply control tables or use the regular DROP CONTROL TABLES command to individually drop either the Q Capture or Q Apply control tables at the server.

ASN2485E

 The keyword keyword is not supported if either the source server or target server is not on DB2 for Linux, UNIX, and Windows Version 10 or higher.

The option is only supported on DB2 for Linux, UNIX, and Windows V10 or higher.

Remove the option and reissue the command.

ASN2486E

 The action action_name cannot be completed because the required information for node node_number was not provided.

Node numbers are used to identify the servers in bidirectional replication. A reference to a node number was made in the CREATE CONTROL TABLES FOR or CREATE REPLQMAP command but the node information was not set in a prior SET BIDI NODE command.

Issue the SET BIDI NODE command before you use the node number in a CREATE CONTROL TABLES FOR or CREATE REPLQMAP command.

ASN2487I

 The queue manager for MQSERVER server_number at host hostname and port port_number is local to the system where the ASNCLP program runs. The ASNCLP program will run the WebSphere MQ setup script for this server.

If you use the RUN NOW option with the CREATE MQ SCRIPT command and the ASNCLP program is running on the same system as the queue manager, the ASNCLP generates the script and then runs the script. If the queue manager is on a different system, the ASNCLP does not run the script even if RUN NOW is specified.

This message is for your information only. No action is required.

ASN2488W

 The queue manager for MQSERVER server_number at host hostname and port port_number is remote from the system where the ASNCLP program runs. The ASNCLP program will not run the WebSphere MQ setup script for this server even though the RUN NOW option is specified.

If you use the RUN NOW option with the CREATE MQ SCRIPT command and the ASNCLP program is running on a different system than the queue manager, the ASNCLP generates the script but does not run the script. If the queue manager is on the same system, the ASNCLP runs the script when RUN NOW is specified.

Run the generated WebSphere MQ script by using the following command:

 runmqsc <queue_manager_name> <     <filepath>/<script_file_name>

ASN2489E

 The option WITH LOGMARKER is specified in the CREATE QSUB command and the target table or nickname owner.name exists but does not have the IBMSNAP_LOGMARKER column.

The target table or nickname must have the IBMSNAP_LOGMARKER column to use the WITH LOGMARKER option for the Q subscription.

Perform one of the following actions and rerun the command:

  • Alter the target table to add the IBMSNAP_LOGMARKER column with a data type of TIMESTAMP and NOT NULL WITH DEFAULT.
  • Use another target table that has the IBMSNAP_LOGMARKER column.

ASN2490E

 The target table or nickname owner.name contains the column IBMSNAP_LOGMARKER but the data type of the column data_type does not match the required data type data_type.

The data type of the column IBMSNAP_LOGMARKER must match the Q Replication requirements or the Q Apply program does not activate the Q subscription.

Perform one of the following actions and rerun the command:

  • Use a different target with a valid definition of the IBMSNAP_LOGMARKER column.
  • Use a new target table.

ASN2491E

 The option WITH LOGMARKER is not supported because either the Q Apply server is on DB2 for z/OS and the control tables are not at Version 10 or higher (ARCH_LEVEL of 100Z) or on DB2 for Linux, UNIX, and Windows and not at Version 9.7 Fix Pack 4 or higher.

The WITH LOGMARKER option of the CREATE QSUB command adds the timestamp of when the source row was changed to the target table or nickname. This option is only supported in the following cases:

  • The Q Apply server on Linux, UNIX, and Windows at Version 9.7 FP4 or higher.
  • The Q Apply server is on z/OS and the architecture level is 100Z or higher, which corresponds to Version 10, and the PTF that corresponds to Version 9.7 Fix Pack 4 is installed.

Upgrade the Q Apply server to the version and PTF or fix pack that supports this option, and resubmit the CREATE QSUB command.

ASN2494E

 A schema-level Q subscription with name name already exists at the server server_name under schema schema.

The name that was provided with the CREATE SCHEMASUB command already exists in the IBMQREP_SCHEMASUBS table. A duplicate schema-level Q subscription cannot be created.

Provide a different name and reissue the CREATE SCHEMASUB command.

ASN2496E

 Target consistent-change data (CCD) tables have not been upgraded to 16-byte log sequence number (LSN) columns that are required when the target server is at DB2 version version.

When the source server is at DB2 Version 10, target CCD tables require 16-byte LSN columns (IBMSNAP_COMMITSEQ, IBMSNAP_INTENTSEQ) to hold log sequence numbers.

Follow the steps in the Version 10 migration information to upgrade target CCD tables to 16-byte LSN columns and and restart the Q Apply program.

ASN2497E

 The WITH LOGMARKER option cannot be used because the source table table.owner_table.name has an IBMSNAP_LOGMARKER column.

You can populate an IBMSNAP_LOGMARKER column in a target table in two different but mutually exclusive ways:

  • By specifying the WITH LOGMARKER keywords in the CREATE QSUB command. With this method, the IBMSNAP_LOGMARKER column is added to the target table and is populated with timestamp values taken directly from the source recovery log.
  • By including an IBMSNAP_LOGMARKER column in the source table and mapping the column to a matching IBMSNAP_LOGMARKER column in the target table. With this method, the target column is populated with values from the source column. This method can be used in a three-tier configuration where the IBMSNAP_LOGMARKER column at Tier 2 is populated from the recovery log at Tier 1, and in turn its values are replicated to populate the column at Tier 3.

If you have a source column named IBMSNAP_LOGMARKER, you cannot use the WITH LOGMARKER keywords.

Reissue the CREATE QSUB command, omitting the WITH LOGMARKER option. Map the IBMSNAP_LOGMARKER column in the source table to the matching target column. This method ensures that values in the IBMSNAP_LOGMARKER column are from the source table and not from the log.

ASN2498E

 The action action failed. The architecture level arch_level of the Apply control tables is not compatible with the Capture compatibility value compatibility.

The source server is at DB2 Version 10, which uses 16-byte log sequence numbers (LSN). To replicate data from Version 10, the Apply program must work with control tables that are migrated to Version 10 and 16-byte LSN values.

Migrate the Apply control server to Version 10.

ASN2499E

 The action action failed. The source and target consistent-change data (CCD) tables are incompatible.

Both source and target CCD tables must have either 10-byte or 16-byte columns to hold log sequence numbers (LSN).

Upgrade the target CCD table to 16-byte LSN columns if the source CCD table uses 16-byte LSN columns, or upgrade the source CCD table to 16 byte-LSN columns. The source CCD table can be either an external CCD table that you create or a CCD table that is maintained by an Apply program or Q Apply program, in which case migration of these servers is also required.

ASN2500E

 The TYPE CCD option cannot be used because the source table table.owner_table.name has the following IBMSNAP_% columns: columns.

You can populate the IBMSNAP_% columns in a target table in two different but mutually exclusive ways:

  • By specifying the TYPE CCD keyword in the CREATE QSUB command. With this method, the target type is set to 2 and the IBMSNAP_% columns in the target table are populated with values taken directly from the source recovery log.
  • By including the IBMSNAP_% columns in the source table and mapping the column to a matching IBMSNAP_% column in the target table. With this method, the target column is populated with values from the source column. This method can be used in a three-tier configuration where the IBMSNAP_% column at Tier 2 is populated from the recovery log at Tier 1, and in turn its values are replicated to populate the column at Tier 3.

If you have a source column named one of the IBMSNAP_% columns, you cannot use the TYPE CCD keyword.

Reissue the CREATE QSUB command, omitting the TYPE CCD option to indicate that the target is a regular user table. Map the IBMSNAP_% columns in the source table to the matching target column. This method ensures that the IBMSNAP_% column is from the source table and not from the log.

ASN2503E

 The TARGET keyword is not supported in the ALTER ADD COLUMN command because of the DB2 version, architecture level, or compatibility settings of the source or target server. Reason code reason_code.

The option to specify target column names with the ALTER ADD COLUMN command is allowed only in the following cases:

Linux, UNIX, Windows

Source or target servers are on DB2 Version 9.7 Fix Pack 5 or higher and the value of the COMPATIBILITY column in the IBMQREP_CAPPARMS table is 0907 or higher.

z/OS

The architecture level of the Q Capture or Q Apply control tables (ARCH_LEVEL column in the IBMQREP_CAPPARMS or IBMQREP_APPLYPARMS table) is 0907 or higher and the value of the COMPATIBILITY column in the IBMQREP_CAPPARMS table is 0907 or higher.

The following values are valid for the reason code:

0

The Q Capture server is on DB2 for Linux, UNIX, and Windows V9.7 FP5 or higher but COMPATIBILITY is lower than 0907.

1

The Q Capture server is on DB2 for Linux, UNIX, and Windows V9.7 FP4 or lower.

2

The Q Capture server is on DB2 for z/OS and ARCH_LEVEL is lower than 0907.

3

The Q Capture server is on DB2 for z/OS but COMPATIBILITY is lower than 0907.

4

The Q Apply server is on DB2 for Linux, UNIX, and Windows V9.7 FP4 or lower.

5

The Q Apply server is on DB2 for z/OS and ARCH_LEVEL is lower than 0907.

Follow these steps:

  1. Upgrade the Q Capture server, Q Apply server or both to either DB2 for Linux, UNIX, and Windows V9.7 FP5 or higher with the required compatibility setting or DB2 for z/OS with the required compatibility setting and architecture level.
  2. Rerun the command.

ASN2506E

 A schema-level Q subscription subscription_name that uses replication queue map queue_map_name cannot be created because the expression expression that was provided for the schemas or tables to include or exclude from the Q subscription is invalid.

You can use the percentage sign (%) as a wild card to specify schema-level Q subscriptions and the Q Capture program automatically creates a Q subscription for all tables within the schemas with names that match the wild-card expression. However the wild card can only be specified as a suffix when you use the folllowing keywords:

  • OWNER LIKE
  • NAME LIKE
  • EXCLUDE NAME

Wild cards that are used as a prefix (for example "%AN" or "%AN%") are not supported, and no wild cards are allowed with the EXCLUDE OWNER keywords.

Change to an allowed wild-card expression and reissue the CREATE SCHEMASUB command.

ASN2508I

 The REINIT SCHEMASUB command was processed for the schema-level Q subscription name.

The REINIT SCHEMASUB command prompts the ASNCLP program to generate a SQL script to insert a REINIT_SCHEMASUB signal into the IBMQREP_SIGNAL table. The signal causes the Q Capture program to reread the saved options for the schema-level Q subscription.

This message is for your information only. No action is required.

ASN2509I

 The REINIT SCHEMASUB command was processed for schema-level Q subscription name but a script to insert a REINIT_SCHEMASUB signal into the schema.IBMQREP_SIGNAL table was not generated because the schema-level Q subscription is inactive.

Schema-level Q subscriptions must be in active (A) state for a REINIT_SCHEMASUB signal to be processed.

Issue the START SCHEMASUB command and then issue the REINIT SCHEMASUB command.

ASN2510E

 A schema-level Q subscription with name name does not exist at the server server under schema schema and so could not be deleted.

The attempt to delete a schema-level Q subscription failed because the specified Q subscription name does not exist in the IBMQREP_SCHEMASUBS table.

Provide an existing schema-level Q subscription name and rerun the action.

ASN2511E

 The column column_name of data type data_type in target table table_owner.table_name cannot be populated with the timestamp of when the source row was changed because the column data type does not match the required data type required_data_type.

The target table must have a timestamp column in order for the table to serve as a point-in-time table. This type of table stores the time that each row change was committed at the source database.

Redo the action to create the Q subscription after making one of these changes:

  • Use a different column in the target table that is defined with the TIMESTAMP data type.
  • Use a different target table that includes a timestamp column.

ASN2512E

 The column column_name in target table table_owner.table_name cannot be populated with the timestamp of when the source row was changed because the target column is already mapped to a source column column_name in table table_owner.table_name.

The specified column in the target table is already mapped to a source column, so you cannot specify this column to be populated with the timestamp of when the source row was changed. The timestamp is taken from the recovery log at the source database.

Redo the action to create the Q subscription after making one of these changes:

  • Use a different eligible column in the target table to map to the source recovery log.
  • Remove the source column mapping:
    • Use the TRGCOLS EXCLUDE option to exclude the target column from any direct mapping to a source column.
    • If you are already using the TRGCOLS INCLUDE option with the column, then remove the column from the list of target columns to include.

ASN2513E

 The target table or nickname owner.name cannot be used as a point-in-time table or nickname because it does not contain any timestamp columns.

A point-in-time table or nickname includes an additional column that is populated with the timestamp of when the source row was changed. To use this option, the target table or nickname must have at least one column that is defined with the TIMESTAMP data type.

Perform one of the following actions:

  • In the Replication Center, deselect the Point-in-time option on the Source and Target page of the Q Subscription Properties notebook for this table or nickname.
  • Alter the target table to include a timestamp column and then redo the action.
  • Do not create a Q subscription that includes this target table or nickname.

ASN2514E

 The target table or nickname owner.name does not have any eligible column to store the timestamp of when the source row changed. All of the timestamp columns in the table or nickname are already mapped to source table columns.

A point-in-time table or nickname includes an additional column that is populated with the timestamp of when the source row was changed. To use this option, the target table or nickname must have at least one timestamp column that is not mapped to a source column.

Redo the action to create the Q subscription after making one of these changes:

  • In the Replication Center, clear the Point-in-time check box on the Source and Target tab of the Q Subscription Properties notebook.
  • Make one of the timestamp columns in the target table columns eligible for the point-in-time mapping by following these steps:
    1. On the Column Mapping page, remove the source-target mapping for a timestamp column in the target table.
    2. Select the target column and click Map to LOGMARKER to map the column to the value from the source recovery log.

ASN2515W

 An existing nickname could not be found on the federated database database_name for the remote table table_owner.table_name. A new nickname owner.name will be created.

When you create multiple Q subscriptions for federated targets, the Replication Center uses the target object profile that you created to determine whether to use an existing nickname or create a new nickname. The option to use an existing nickname was selected in the profile, but the Replication Center did not find an existing nickname that points to the table on the non-IBM server. A new nickname will be created for the remote table.

This message is for your information only. No action is required.

ASN2516E

 The nickname owner.name exists on the federated database database_name, but the nickname does not point to the remote table table_owner.table_name that was specified as the target table for the Q subscription.

When you create multiple Q subscriptions for federated targets, the Replication Center uses the target object profile that you created to determine whether to use an existing nickname or create a new nickname. The option to use an existing nickname was selected in the profile and a nickname exists on the federated database that matches the profile. However, this nickname does not point to the remote target table.

Take one of the following actions:

  • On the Target Tables page of the Create Q Subscriptions wizard, click Change, and then on the Target Object Profiles notebook, clear the Use existing nicknames checkbox. The Replication Center then creates a nickname that points to the remote target table.
  • Create a nickname that points to the remote target table, and use this existing nickname for the Q subscription.

ASN2517E

 More than one nickname points to the remote table table_owner.table_name and so the Replication Center cannot determine which nickname to use.

When you create multiple Q subscriptions for federated targets, the Replication Center uses the target object profile that you created to determine whether to use an existing nickname or create a new nickname. The option to use an existing nickname was chosen in the profile, but you must use the Q Subscription Properties notebook to specify which nickname to use.

Follow these steps:

  1. On the Review Q Subscriptions page of the wizard, select the Q subscription that specifies this remote table and click Properties.
  2. On the Source and Target tab of the Q Subscription Properties notebook, select a nickname from the Existing nicknames list.

ASN2521E

 The compatibility value value is not supported because the Q Capture control tables are at Version 10.1.

The Q Capture compatibility parameter specifies the level of messages that are sent to the Q Apply program. When the Q Capture program is at Version 10.1 on Linux, UNIX, and Windows, the supported values for the compatibility parameter are 1001 and 0907.

Use the Q Replication Dashboard or SQL to set the value in the COMPATABILITY column of the IBMQREP_CAPPARMS table to 1001 if the Q Apply program is at Version 10.1 on Linux, UNIX, or Windows, or 0907 if the Q Apply program is at Version 9.7. Then reissue the ASNCLP command.

ASN2523E

 You cannot use the Replication Center on Oracle source databases to perform operational tasks such as starting or stopping replication and event publishing programs or managing send or receive queues.

The Replication Center function to run commands that operate on replication or publishing programs is not supported on Oracle source databases.

To start the Q Capture program, open a console on the Oracle server and use the asnoqcap command. To issue commands to a running Q Capture program, use the asnoqccmd command.

ASN2524E

 One or more values are missing for the required parameter or parameters parameter_names. You must specify values for both MQLOG and MQDATA when you specify the MULTIINST option with the CREATE MQ SCRIPT command. No script is generated.

In a multi-instance queue manager configuration, you must specify the MQLOG and MQDATA keywords with CREATE MQ SCRIPT. MQLOG specifies the directory where the queue manager writes its log, and MQDATA specifies the directory that is used to hold the queue manager data files. All instances of the multi-instance queue manager use the specified directories.

Reissue the CREATE MQ SCRIPT command, specifying values for MQLOG and MQDATA.

ASN2525E

 The PARALLEL SENDQS option is not supported because one or more of the databases in your configuration is on an unsupported version or platform. No script is generated.

The source or target databases or both are at an unsupported architecture level .

Ensure that the databases in your configuration meet the version or platform requirements and then reissue the command.

ASN2526E

 The PARALLEL SENDQS option is not supported because the Q Capture control tables, Q Apply control tables, or both are at an architecture level that is lower than 1021. No script is generated.

The PARALLEL SENDQS option is supported only if both Q Capture and Q Apply control tables are at architecture level of 1021 or higher.

Migrate the control tables to the 1021 architecture level and rerun the command.

ASN2527I

 A value value was specified for the PARALLEL SENDQS option, which indicates that the send queue queue_name will run in multiplexing mode. All of the underlying parallel send queues for this send queue must exist before you start replication. A SQL script to create or alter the replication queue map was generated.

Because the send queue will run in multiplexing mode, the Q Capture program expects all underlying parallel send queues to exist before replication is started. The number of send queues and channels that you create should match the value that was specified for PARALLEL SENDQS.

Make sure that the appropriate number of queues are created before you start replication.

ASN2528I

 The number of parallel send queues for replication queue map queue_map_name was changed from old_value to new_value while the queue map is active. A script to alter the queue map was generated. After the script is run, make sure to reinitialize or stop and start the Q Capture program so that it begins to use the new value.

The new value is not used until the Q Capture program rereads the properties of queue map, which requires that you reinitialize or stop and start Q Capture

Reinitialize or stop and start the Q Capture program.

ASN2529E

 Using a multiplexed send queue in two different queue maps is not supported. The send queue queue_name that was specified for replication queue map queue_map_name is also being used by replication queue map queue_map_name. The second queue map is defined to use send queue multiplexing. It uses num_parallel_sendqs send queues and also specifies the send queue queue_name.

The send queue that was specified for the queue map is being used by another queue map that is defined with multiplexing. Although there is no entry in the IBMQREP_SENDQUEUES table with this send queue name, it can be inferred that the send queue is already being used because of the base send queue name.

Provide a different send queue name for the queue map that you are creating or altering and rerun the command.

ASN2530I

 The replication queue map queue_map_name is defined with number parallel send queues. The validation checks are performed on all of the send queues.

The ASNCLP program will perform validation checks on all of the parallel send queues that are specified for the queue map, and will also check all of the WebSphere MQ channels that are associated with the send queues.

This message is for your information only. No action is required.

ASN2531E

 The PARALLEL SENDQS option was specified with the CREATE MQ SCRIPT command, but the required keywords PLATFORM ZOS were not specified. No script is generated.

Because send queue multiplexing is supported only on z/OS, if you specify the keywords PARALLEL SENDQS you must also specify PLATFORM ZOS.

Specify the PLATFORM ZOS keywords and rerun the command.

ASN2539E

 The EXIST option was specified under the INCLUDE HISTORY clause to indicate that a history table exists on the target. However, no history table was found for the target table table_owner.table_name. No script was generated.

The EXIST option specifies that a history table is already created for the target temporal table. In this situation the ASNCLP program creates a Q subscription for both the temporal table and the history table. The ASNCLP program was unable to find a history table, so no Q subscription was created.

Take one of the following actions and rerun the CREATE QSUB command:

  • Remove the EXIST clause and use the HIST_TARGET NAME keywords to specify a name for the history table so that the ASNCLP program can create the history table.
  • Create the history table, alter the target table to enable versioning, and use the EXIST option.

ASN2540E

 The target table table_owner.table_name has the SYSTEM_TIME period column defined but the ASNCLP program did not find a history table. No script was generated.

To create a Q subscription for a target temporal table, the table must have an associated history table. Versioning also must be enabled on the table to make it a complete system temporal table.

Create the history table, alter the target table to add versioning, and rerun the CREATE QSUB command.

ASN2541E

 A primary key or unique index was detected on the IBMQREPVERTIME column or IBMQREPVERNODE column in the source table table_name on server server_name. Q subscriptions for peer-to-peer replication do not allow primary keys or unique indexes on these columns.

The IBMQREPVERTIME and IBMQREPVERNODE columns are used to track different versions of row changes in peer-to-peer replication. These columns are reserved for use by Q Replication and cannot have primary keys or unique indexes.

Remove the primary key or unique index that is defined on the IBMQREPVERTIME column, IBMQREPVERNODE column, or both, and then reissue the action to create a Q subscription.

ASN2542E

 Bidirectional and peer-to-peer replication of DB2 for z/OS temporal tables is not supported. The Q subscription was not created.

Replication of system-period temporal tables and application-period temporal tables is supported for unidirectional Q subscriptions only on DB2 for z/OS.

Specify a non-temporal table for the bidirectional or peer-to-peer Q subscription, or create a unidirectional Q subscription for the temporal table.

ASN2543E

 The command command is not supported because one or more of the databases in your configuration are DB2 for Linux, UNIX, and Windows Version 10.5 Fix Pack 5 or older or DB2 for z/OS with an architecture level that is older than 1021. No SQL is generated.

Commands that are used to configure multiple consistency groups are supported only if the databases that are involved in the configuration are on DB2 for z/OS with an architecture level of 1021 or higher, or on DB2 for Linux, UNIX, and Windows Version 10.5 Fix Pack 6 or newer with an arch_level value of 1133 or higher.

Ensure that all databases that are part of the configuration are at a supported DB2 level and architecture level and reissue the command.

ASN2544E

 The command to create or alter a multiple consistency group failed because Q Apply control tables do not exist on the server server. No SQL is generated.

At least one set of Q Apply control tables must exist to create or alter a multiple consistency group.

Create the Q Apply control tables using the CREATE CONTROL TABLES command and rerun the command.

ASN2545E

 The multiple consistency group group_name cannot be created or altered because the required control tables are missing.

The control tables ASN.IBMQREP_MCGSYNC and ASN.IBMQREP_MCGPARMS must be created before you can create or alter a multiple consistency group. These control tables are created when you create Q Apply control tables at Version 10.2.1 or later, or when you migrate existing control tables to the 1021 architecture level.

Create the Q Apply control tables by using the replication administration tools or by running the Version 10.2.1 or later migration scripts.

ASN2546E

 The multiple consistency group group_name cannot be created because another multiple consistency group with the same name already exists.

When you create a multiple consistency group, a row is inserted into the ASN.IBMQREP_MCGPARMS table to identify the group. Each group (or row in the table) must have a unique value for the multiple consistency group name (MCGNAME column).

Provide another multiple consistency group name that does not already exist at the server and rerun the command.

ASN2547E

 The multiple consistency group group_name does not exist and thus cannot be altered or dropped. No SQL script is generated.

The ASN.IBMQREP_MCGPARMS table does not contain an entry for the specified multiple consistency group name, so the attempt to alter or drop the group failed.

Provide another multiple consistency group name that already exists at the server and rerun the command.

ASN2548E

 The option to add replication queue map queue_map_name as a consistency group was specified, but one or more databases in the configuration are on DB2 for Linux, UNIX, and Windows or on a DB2 for z/OS subsystem with replication control tables that have an architecture level that is older than 1021. The queue map cannot be created or altered.

The option to add a replication queue map to a multiple consistency group is only supported on DB2 for z/OS subsystems with replication control tables that have an architecture level of 1021 or higher.

Take one of these actions:

  • If either one of the databases in your configuration is on DB2 for Linux, UNIX, and Windows, then remove the option to add the queue map to a multiple consistency group and rerun the command.
  • If all of your databases are on DB2 for z/OS subsystems then take one of the following steps before rerunning the command to add the queue map to a multiple consistency group:
    1. Migrate your replication setup to the 1021 architecture level (Version 10.2.1).
    2. Create the multiple consistency group by using the CREATE MULTIPLE CONSISTENCY GROUP command.

ASN2549E

 The option to add a replication queue map to a multiple consistency group or remove the queue map from the group was specified, but the multiple consistency group does not exist. The queue map cannot be created, altered, or removed from the group. Queue map: queue_map_name. Multiple consistency group: group_name.

The multiple consistency group must already exist before you can add a replication queue map to it or removing a queue map from it.

Create a multiple consistency group by issuing the CREATE MULTIPLE CONSISTENCY GROUP command and then rerun the command.

ASN2550E

 The option to add replication queue map queue_map_name as a consistency group was specified, but the replication queue map is already part of the specified multiple consistency group group_name. The queue map cannot be altered.

Queue maps and the consistency groups that they represent cannot be part of more than one multiple consistency group.

Specify a replication queue map that represents a consistency group is not already part of a multiple consistency group and rerun the command.

ASN2551E

 The consistency group that is represented by replication queue map queue_map_name does not belong to the multiple consistency group group_name and so it cannot be dropped from the group. The action to change the queue map's properties so that it is not part of the group failed.

The consistency group that is represented by the replication queue map must be part of a multiple consistency group before you can change the queue map properties to remove its consistency group from the multiple consistency group.

Specify a replication queue map that represents a consistency group is part of a multiple consistency group and rerun the command.

ASN2552E

 The attempt to remove the consistency group that is represented by replication queue map queue_map_name from the multiple consistency group group_name failed because the state of the consistency group in the ASN.IBMQREP_MCGSYNC table is active. The action to change the queue map's properties so that it is not part of the group failed.

A consistency group must be in an inactive state to remove it from a multiple consistency group.

Deactivate the consistency group by issuing the mcgsynchoff command and then rerun the command.

ASN2553E

 The operation could not be completed. Operations such as starting or stopping replication programs with the Replication Center are not supported on Oracle databases.

Operations that require the DB2 Administration Server are not supported when the source is an Oracle database or the target uses native replication to an Oracle database.

Use the asnoqcap, asnoqapp, or asnoqccmd system commands to run these operations natively on Oracle.

ASN2554E

 The command_name command is not supported because one or more of the databases in your configuration is DB2 for Linux, UNIX, and Windows, or is on a DB2 for z/OS subsystem with a control table architecture level that is older than 1021. No SQL is generated.

Commands that are used to add columns to the replication key of a Q subscription are supported only if all of the databases that are involved in the configuration are on DB2 for z/OS with a control table architecture level of 1021 or higher.

Ensure that all databases that are part of the configuration are on DB2 for z/OS with architecture level of 1021 or higher, and then reissue the command.

ASN2555E

 The command_name command is not supported because the Q subscription is not active. No SQL is generated. Q subscription: name.

The command to add a column to the replication key of a Q subscription is only supported if the Q subscription is in active (A) state.

Start the Q subscription and ensure that its state is A before rerunning the command.

ASN2556E

 The command_name command is not supported because the target is a noncondensed CCD table. No SQL is generated. Q subscription: name.

If the target is a consistent-change data (CCD) table with the noncondensed attribute, the ASNCLP program selects the first column as the key for replication and no other columns are allowed as part of the key.

Specify a different Q subscription that does not have a noncondensed CCD target and rerun the command.

ASN2557E

 The column column_name cannot be added to the replication key because the data type of the column is invalid for the replication key. No SQL is generated. Q subscription: name. Column data type: data_type.

Columns that are used as keys for replication must be eligible to be part of a predicate. The provided column is not eligible because of its data type, and therefore it cannot be part of the replication key.

Provide a different column with a data type that allows the column to be part of a predicate and rerun the command.

ASN2558E

 The column column_name cannot be added to the replication key because the column is not part of the Q subscription. No SQL is generated. Q subscription: name.

A column must be part of a Q subscription before it can be added to the replication key.

Add the column to the Q subscription by using the ALTER ADD COLUMN command and rerun the command.

ASN2559E

 The column column_name is not supported as part of the replication key because the target is a stored procedure. No SQL is generated. Q subscription: name.

The command to add a column to the replication key of a Q subscription is not supported for stored procedure targets.

Specify a different Q subscription that does not have a stored procedure target and rerun the command.

ASN2560E

 The command command_name is not supported because the Q subscription is for peer-to-peer replication. Q subscription: name.

The command to add a column to the replication key of a Q subscription is not supported in peer-to-peer configurations.

Specify a different Q subscription that is not for peer-to-peer replication and rerun the command.

ASN2561E

 The column cannot be added to the replication key of the Q subscription because it is not part of the source table. Column: column_name. Q subscription: name. Source table: table_owner.table_name.

Before you can use the ADD REPL KEY COL command to add a column to the replication key, the column must be part of the source table and part of the Q subscription for the table.

Take one of the following actions and rerun the command:

  • Provide a different column name that exists in the source table and is part of the Q subscription.
  • Add the column to the source table and then add it to the Q subscription by using the ALTER ADD COLUMN USING SIGNAL command.

ASN2663I

 Q Replication operations within the Replication Center are deprecated and might not be present in future releases.

Operational tasks for Q Replication have largely been replaced with those in the IBM InfoSphere Data Replication Dashboard. Some operations are not present in the dashboard such as starting, stopping, and reinitializing the replication programs. These tasks are recommended to be run on the systems where the replication programs run.

Use the IBM InfoSphere Data Replication Dashboard to manage Q subscriptions and publications, change saved operational parameters, and to generate reports. For operational tasks such as starting, stopping, or reinitializing the replication programs, use the following methods depending on the operating system:

Linux, UNIX, and Windows

Use system commands or set up a service on Windows to start and stop the programs.

z/OS

To start the programs, use JCL or a started task. To issue commands to running replication or publishing programs such as stop or reinitialize, use the MODIFY command.

ASN2664I

 SQL Replication operations within the Replication Center are deprecated and might not be present in future releases.

Because the DB2 Administration Server (DAS) is deprecated, these Replication Center functions that depend on DAS are also deprecated:

Capture

Starting, stopping, suspending, resuming, pruning, reinitializing, changing operational parameters, and checking status

Apply

Starting, stopping, and checking status. The other operations are also deprecated because you can use asnanalyze to obtain the information.

You can generate SQL Replication reports for messages, throughput analysis, and latency by using asnanalyze. Other operations such as starting, stopping, and reinitializing the replication programs are recommended to be run on the systems where the replication programs are run.

ASN2682E

 The command command failed because the SRC_TIMEZONE column is null in the schema.IBMQREP_CAPPARMS table. Use the ALTER CAPTURE PARAMETERS command to provide a valid value for SRC_TIMEZONE.

When the replication target is a CDC Apply program, you must supply the time zone of the source server. Use the SOURCE TIMEZONE option in the ALTER CAPTURE PARAMETERS command to specify the time zone from which the source data originates, as found in the IANA Time Zone Database.
  1. Issue the ALTER CAPTURE PARAMETERS command with the SOURCE TIMEZONE option.
  2. Reissue the previous command.

ASN2695E

 CCD target tables are not supported with the current Q Capture architecture level and compatibility settings and Q Apply architecture level. Q Capture arch_level: arch_level. Compatibility: compatibility. Q Apply arch_level: arch_level.

You cannot replicate to a CCD target table when the Q Capture arch_level and compatibility and Q Apply arch_level are at the specified values.

Change the Q Capture compatibility or upgrade Q Apply to a supported arch_level.

ASN2696E

 The password file filename does not exist. The command failed.

A password file was specified with the SET PWDFILE command but the ASNCLP program was unable to find a file with the specified name and location. The password file must exist in the specified directory.

Make sure that the password file exists in the specified directory and reissue the command.

ASN2697E

 The system could not allocate memory to store ID and password information. The command failed.

The SET PWDFILE command reads ID and password information from a specified password file and saves the information in system memory to use in connecting to replication servers. Allocation of the required amount of memory failed.

Make sure there is 4K of free system memory to store ID and password information and reissue the command.

ASN2698E

 The password file filename could not be decrypted. Reason code: reason_code.
The password file could not be decrypted. The following values are valid for the reason code:
-4
The file cannot be accessed.
-6
The file name is too long.
-11
The decryption algorithm failed.
Review the reason codes in the explanation and take the appropriate action:
-4
Make sure that the user ID has proper permission to access the password file.
-6
Make sure that the file name length is less than 128 characters.
-11
Make sure that the specified password file was generated by the asnpwd command.

ASN2699I

 Control tables created at level control-tables-level, which is the highest level supported by ASNCLP version asnclp-version.

In response to a CREATE CONTROL TABLES FOR command, the ASNCLP program created new control tables for the program and inserted the specified value in the CONTROL_TABLES_LEVEL column of the IBMQREP_CAPPARMS or IBMQREP_APPLYPARMS table.

This message is for your information only. No response is required.

ASN2700I

 Use the ASNCATM utility to upgrade the control tables to a higher level, if needed.

The ASNCLP program created control tables at the specified level. If you want to upgrade the control tables to a higher level, use the ASNCATM utility.

This message is for your information only. No response is required.