ASN2700E The server name "<server_name>" is invalid.
Explanation: The first character of the database server name is invalid.
User Response: Refer to the section on naming conventions for information on valid server names. Then provide the correct server name.
ASN2701E The database "<database_name>" or subsystem "<subsystem_name>" must be an 8-bytes-or-less alias name.
Explanation: The server name consists of more than eight characters.
User Response: Enter the correct alias name. It must consist of eight characters or less.
ASN2702I SQL CONNECT to"<server_type>" "<server_name>" succeeded.
Explanation: This message is for your information only.
User Response: No action is required.
ASN2703E SQL CONNECT to"<server_type>" "<server_name>" failed. Sqlstate is "<sqlstate>", sqlcode is "<sqlcode>", sqlerrm is "<sqlerrm>", sqlerrp is "<sqlerrp>".
Explanation: The migration tool cannot connect to the server.
User Response: Refer to the SQLSTATE values section of your database messages and codes manual.
ASN2704I Action "<action>" for "<table_name>" table starts.
Explanation: This message is for your information only.
User Response: No action is required.
ASN2705I Action "<action>" for "<view_name>" view starts.
Explanation: This message is for your information only.
User Response: No action is required.
ASN2706I Action "<action>" for "<table_name>" table succeeded.
Explanation: This message is for your information only.
User Response: No action is required.
ASN2707I Action "<action>" for "<view_name>" view succeeded.
Explanation: This message is for your information only.
User Response: No action is required.
ASN2708E Action "<action>" for "<table_name>" table failed.
Explanation: The migration fallback or the cleanup for the table failed.
User Response: Refer to the previous SQL statement execution to find the SQLSTATE value for the error message.
ASN2709E Action "<action>" for "<view_name>" view failed.
Explanation: The action for the view, MIGRATE, FALLBACK or CLEANUP, failed.
User Response: Refer to the previous SQL statement execution for the SQLSTATE value for the error message.
ASN2710E The BUILDDB action was not done for subscriber "<subscriber_userid>" at "<server_type>" "<server_name>".
Explanation: The BUILDDB step was not executed for the subscriber.
User Response: Perform the BUILDDB and the PREPARE step for the subscriber.
ASN2711E The BUILDDB action was not done for "<server_type>" "<server_name>".
Explanation: The BUILDDB step was not executed for the server.
User Response: Perform the BUILDDB and PREPARE steps for the server.
ASN2712E The requested version "<version>" is invalid.
Explanation: The control table version value entered is not valid.
User Response: Correct the value and reenter it or enter L to run the latest version.
ASN2713E The PREPARE action must be executed before the MIGRATE or FALLBACK action.
Explanation: The PREPARE step was not executed before the MIGRATE step.
User Response: Perform the PREPARE step before performing the MIGRATE step.
ASN2714I Action "<action>" for "<server_type>" "<server_name>" started or action "<action>" for "<subscriber>""<userid>".
Explanation: This message is for your information only.
User Response: No action is required.
ASN2715I Action "<action>" for "<server_type>" "<server_name>" succeeded or action "<action>" for "<subscriber>""<userid>".
Explanation: This message is for your information only.
User Response: No response is required.
ASN2716E Action "<action>" for "<server_type>" "<server_name>" failed or action "<action>" for "<subscriber>""<userid>".
Explanation: The migration, fallback, or cleanup for the server failed.
User Response: Refer to the previous SQL statement execution for the SQLSTATE value and then refer to the listing of that value in the message information for your platform to determine the cause of the error.
ASN2717E Data server "<data_server_name>" has not been migrated yet.
Explanation: The data server with dependent subscriptions has not been migrated yet.
User Response: Migrate the data server.
ASN2718I Data server "<data_server_name>" has been migrated.
Explanation: This message is for your information only.
User Response: No action is required.
ASN2719E Action "<action>" for table "<table_name>" was not performed.
Explanation: The action for the table was not executed.
User Response: Repeat the action.
ASN2720E Action "<action>" for view "<view_name>" was not performed.
Explanation: The action for the view was not executed.
User Response: Repeat the action.
ASN2721I Current userid is "<user_id>" and "<server_type>" alias is "<alias_name>".
Explanation: This message is for your information only.
User Response: No action is required.
ASN2722I No registration information was collected at version "<version>".
Explanation: This message is for your information only.
User Response: No action is required.
ASN2723I No subscription information was collected at version "<version>".
Explanation: This message is for your information only.
User Response: No action is required.
ASN2724I Table "<table_name>" already exists.
Explanation: This message is for your information only.
User Response: No action is required.
ASN2725I View "<view_name>" already exists.
Explanation: This message is for your information only.
User Response: No action is required.
ASN2726I Table "<table_name>" does not exist.
Explanation: This message is for your information only.
User Response: No action is required.
ASN2727I View "<view_name>" does not exist.
Explanation: This message is for your information only.
User Response: No action is required.
ASN2728I More than one table "<table_name>" exists.
Explanation: This message is for your information only.
User Response: No action is required.
ASN2729E SQL message is "<sqlmsg>", sqlcode is "<sqlcode>", sqlerrm is "<sqlerrm>", sqlerrp is "<sqlerrp>".
Explanation: The SQL statement execution failed.
User Response: Refer to the SQL message and the SQLCODE values section of your database messages and codes manual.
ASN2730E No alias name was found for the server "server_type>" "server_name>".
Explanation: No alias name was found for the "server_type>" "server_name>" was not provided at the BUILDDB step.
User Response: Provide the complete list of server alias names to the BUILDDB program and run the program again.
ASN2733I The global control information of version "<version>" has been prepared at "<"timestamp>.
Explanation: The SQL statement execution failed.
User Response: Refer to the SQLSTATE values section of your database messages and codes manual.
ASN2734E The file "<file_name>" cannot be opened.
Explanation: This file is either in error or does not exist.
User Response: Verify that the file has been installed correctly. If it has but it still cannot be opened, contact your IBM Service representative. If it has not been installed correctly, reinstall it.
ASN2735E The requested version "<version>" was not found.
Explanation: The information for the requested version cannot be found.
User Response: See the ASN.VERSION_CONTROL table for the available version number specified.
ASN2736E The action parameter was not provided, or was not specified before the keyword parameters.
Explanation: The value for one of the actions (MIGRATE, FALLBACK, or CLEANUP) was not entered before the keyword parameters.
User Response: Enter the action parameter before the keyword parameters.
ASN2737E Too many parameters were entered.
Explanation: The number of parameters entered exceeded the number allowed for the action.
User Response: Verify the necessary parameters and reenter the command.
ASN2738E This parameter is not a keyword parameter: "<parameter_name>".
Explanation: The parameter entered is not a keyword parameter.
User Response: Enter ASNMIG to see the help for the command syntax. Then enter the correct keyword parameter.
ASN2739E Invalid action parameter was entered. Valid actions are BUILDDB, PREPARE, MIGRATE, FALLBACK, and CLEANUP.
Explanation: The action parameter entered is not a valid value.
User Response: Enter ASNMIG to see a listing of the valid action parameters. Then enter the correct action parameter.
ASN2740E Invalid parameter: "<keyword_parameter>".
Explanation: The parameter segment entered was not one of the following: D=, S=, C=, T=, U=, or V=.
User Response: Enter the correct parameter.
ASN2741E Invalid combination of keyword parameters.
Explanation: The keyword parameters specified for the action were incorrectly entered.
User Response: See "Migrating DPROPR from Version 1 to Version 5" for the keywords needed for migration.
ASN2742E SQL SELECT failed. Sqlstate is "<sqlstate>", sqlcode is "<sqlcode>", sqlerrm is "<sqlerrm>", sqlerrp is "<sqlerrp>".
Explanation: The SQL statement execution failed.
User Response: Refer to the SQL message and the SQLCODE values section of your database messages and codes manual.
ASN2743I The column being added already exists.
Explanation: This message is for your information only.
User Response: No action is required.
ASN2744I The row being inserted already exists.
Explanation: This message is for your information only.
User Response: No action is required.
ASN2745I The row being updated already exists.
Explanation: This message is for your information only.
User Response: No action is required.
ASN2746I The V5 registrations defined after the last migration were lost.
Explanation: The Version 5 registrations defined after the last migration from Version 1 to Version 5 were lost because of fallback.
User Response: Register Version 5 after the next migration.
ASN2747I The action "<action>" ended successfully.
Explanation: This message is for your information only.
User Response: No action is required.
ASN2748E The action "<action>" ended unsuccessfully.
Explanation: An error occurred during the BUILDDB or PREPARE action.
User Response: Find the error in the action trace file and rerun the action.
ASN2749E The "<action>" partially succeeded because it could not connect to some servers.
Explanation: A wrong server name was provided.
User Response: Rerun the action using the correct server name.
ASN2750E No V1 control server name exists in "<userid>" ROUTING1 table. Fallback from V5 to V1 cannot be performed.
Explanation: The subscriber's routing table contains no rows so fallback cannot be performed.
User Response: Determine why the ROUTING1 table is empty and rebuild it.
ASN2751E SQL PREPARE failed. Sqlstate is"<sqlstate>", sqlcode is "<sqlcode>", sqlerrm is "<sqlerrm>", sqlerrp is "<sqlerrp>".
Explanation: The subscriber's routing table contains no rows so fallback cannot be performed.
User Response: Determine why the routing table is empty and rebuild it.
ASN2752E SQL OPEN CURSOR failed. Sqlstate is"<sqlstate>", sqlcode is "<sqlcode>", sqlerrm is "<sqlerrm>", sqlerrp is "<sqlerrp>".
Explanation: The SQL statement execution failed.
User Response: Refer to the SQL message and the SQLCODE values section of your database messages and codes manual.
ASN2753E SQL FETCH CURSOR failed. Sqlstate is"<sqlstate>", sqlcode is "<sqlcode>", sqlerrm is "<sqlerrm>", sqlerrp is "<sqlerrp>".
Explanation: The SQL statement execution failed.
User Response: Refer to the SQL message and the SQLCODE values section of your database messages and codes manual.
ASN2754I SQL CLOSE CURSOR failed. Sqlstate is"<sqlstate>", sqlcode is "<sqlcode>", sqlerrm is "<sqlerrm>", sqlerrp is "<sqlerrp>".
Explanation: The SQL statement execution failed.
User Response: Refer to the SQL message and the SQLCODE values section of your database messages and codes manual.
ASN2755I This PREPARE run is for validation only.
Explanation: This message is for your information only.
User Response: No action is required.
ASN2756I Action "<action>" trace file is "<action>".TRC file.
Explanation: The program trace containing records of the action is in the "<action>".TRC file BUILDDB, PREPARE, MIGRATE, FALLBACK, or CLEANUP).
User Response: Check the trace file to see if there were any errors.
ASN2757I Action "<action>" report file is "<action>".RPT file
Explanation: This file is created during the migration (PREPARE, MIGRATE, FALLBACK, or CLEANUP).
User Response: Check the report file to see the summary of migration activity and resolve any errors before continuing with migration.
ASN2758E The migration tool cannot execute on this platform "<platform_name>".
Explanation: Migration could not be performed because of incompatibility between the migration tool and the database it is running on. The problem is probably caused by an error in the installation of the program.
User Response: Refer to the installation section and reinstall the program. Then run the migration tool.
ASN2759E Invalid optional parameter "<parameter_value>". Accepted parameters are 'V' for Validate and 'O' for Override.
Explanation: The only acceptable validation parameter is V.
User Response: Specify V for the validation parameter and reenter it.
ASN2760I Checking if auto-registration for subscriber "<userid>" exists.
Explanation: This message is for your information only.
User Response: No action is required.
ASN2761W Auto-registration has been detected at the copy server "<server_name>". The ASN.IBMSNAP_CD_CNTL and pruning control tables need to be migrated first.
Explanation: The ASN.IBMSNAP_CD_CNTL and pruning control tables may not have been migrated at the copy server.
User Response: Migrate the ASN.IBMSNAP_CD_CNTL and pruning control tables at the copy server.
ASN2762I Please issue the following command: ASNMIG "<action>" D="<migration db>" S="<V1 data server>" V="<version>".
Explanation: This message follows ASN2761W. The ASN.IBMSNAP_CD_CNTL and pruning control tables may not have been migrated at the copy server.
User Response: Issue the command recommended in the message.
ASN2763I No auto-registration for subscriber "<userid>" has been detected.
Explanation: This message is for your information only.
User Response: No action is required.
ASN2764I The ASN.IBMSNAP_CD_CNTL and pruning control tables created from auto-registration task for subscriber"<subscriber>"'s subscription have been migrated.
Explanation: This message is for your information only.
User Response: No action is required.
ASN2765I The action "<action>" SQL file is "<action>".SQL file.
Explanation: The SQL statement generated by the BUILDDB action is written to the "<action>".SQL file (a DB2 statement file).
User Response: Use the DB2 Command Line Processing (CLP) facility to execute the SQL statement in the file.
ASN2766W Auto-registration has been detected at the target server "<server_name>". The ASN.IBMSNAP_REGISTER and ASN.IBMSNAP_PRUNCNTL tables can be fallen back, but not necessary.
Explanation: The ASN.IBMSNAP_REGISTER and the ASN.IBMSNAP_PRUNCNTL tables may not have fallen back at the copy server.
User Response: Fall back the ASN.IBMSNAP_REGISTER and the pruning control tables at the copy server, if desired.
ASN2767E The list of servers must include at least one valid database alias preceding the wildcard character (*).
Explanation: Either all the server aliases entered were invalid or no alias was entered with the wildcard character (*). The wildcard character alone is not sufficient for the program to run.
User Response: Reenter the wildcard character with the proper server alias.
ASN2768W The wildcard character (*) was not specified, so ensure that you did include the complete list of servers for collection.
Explanation: No wildcard character (*) was entered during the BUILDDB action.
User Response: You can continue with the provided server list if this is your intention. If not, reenter the server list with the wildcard character.
ASN2769E SQL EXECUTE/EXECUTE IMMEDIATE failed. Sqlstate is "<sqlstate>", sqlcode is "<sqlcode>", sqlerrm is "<sqlerrm>", sqlerrp is "<sqlerrp>".
Explanation: The SQL statement execution failed.
User Response: Refer to the SQL message and the SQLCODE values section of your database messages and codes manual.
ASN2770E All Applys having subscriptions from data server "<server_name>" must fall back first.
Explanation: At least one Apply subscribed from this data server has not fallen back yet.
User Response: Perform the FALLBACK for all Applys before the Capture.
ASN2771I Subscriber "<userid>" does not have rows in the subscription tables.
Explanation: The IBM Replication V5 tables contain no information that would allow a fallback to DPROPR V1 for that subscriber.
User Response: Verify that the subscriber userid is correct. If it is, review the executed actions.
ASN2772E SQL COMMIT failed. Sqlstate is "<sqlstate>", sqlcode is "<sqlcode>", sqlerrm is "<sqlerrm>", sqlerrp is "<sqlerrp>".
Explanation: The SQL statement execution failed.
User Response: Refer to the SQL message and the SQLCODE values section of your database messages and codes manual.
ASN2773I To change to override option, reissue the command with the parameter: "O".
Explanation: The PREPARE action has been performed at the specified version.
User Response: To restart the program, specify the additional "O" to override the values in the DPROP V1 global control table in the migration database.