SQL1700N | The reserved schema name "<name>" was found in the database during database migration. |
Explanation: The database contains one or more database objects which use the schema name "<name>" that is reserved by the current Database Manager.
The command cannot be processed.
User Response: Ensure that all the database objects that use the reserved schema name are dropped and recreate the objects using a different schema name. This correction must be made in the release of Database Manager where the database was originally created. Ensure that no reserved schema names are in use before attempting the migration again. Then, resubmit the database migration command under the current release of Database Manager.
SQL1701N | The database cannot be migrated because the last session was abnormally terminated. |
Explanation: The last database operation was abnormally terminated (for example, a power failure) under the previous database manager. Database migration cannot be done until the database has been restarted.
The command cannot be processed.
User Response: The database must be restarted. You must issue the RESTART DATABASE command using the release of Database Manager where the database was last accessed. Then, resubmit the database migration command under the current release of Database Manager.
SQL1702W | The "<protocol>" connection managers have started successfully. |
User Response: No action required.
SQL1703W | The db2event directory could not be created during database migration. |
Explanation: The database was migrated successfully but the db2event directory could not be created.
This is a warning only.
User Response: The db2event directory must be created if the event monitor is to be used. The db2event directory must be created in the database directory where the migrated database resides. The database directory of the migrated database can be determined by invoking LIST DATABASE DIRECTORY.
SQL1704N | Database migration failed. Reason code "<reason-code>". |
Explanation: Database migration failed. The reason codes are as follows:
User Response: Possible solutions based on the reason code are:
SQL1705W | Unable to update a database directory entry to the current release level. |
Explanation: One or more database aliases could not be updated in the database directory for a database which has just been migrated from a previous release.
User Response: Uncatalog the database alias(es) for the migrated database and re-catalog the database alias using the same information.
SQL1706W | At least one non local database was detected in the node directory for this instance during word size instance migration. |
Explanation: While performing word size instance migration, at least one database not created under this instance was encountered. Such databases must have the same word size as this instance for migration to complete successfully.
User Response: Ensure that all databases cataloged at the instance have the same word size.
SQL1707N | Unable to migrate the instance word size. |
Explanation: There was an error while attempting to migrate the word size of the instance. Please contact your IBM service representative.
User Response: Contact your IBM service representative.
SQL1708W | Database migration completed with the following warning code: "<warning-code>". |
Explanation: Database migration completed with a warning. The warning codes are as follows:
User Response: Possible solution based on the warning codes:
SQL1749N | The NOT LOGGED INITIALLY attribute cannot be activated for table "<table-name>" since it was not created with NOT LOGGED INITIALLY. |
Explanation: The table "<table-name>" was not created with the NOT LOGGED INITIALLY attribute specified and therefore this attribute cannot be activated using ALTER TABLE.
The statement cannot be processed.
User Response: Remove the NOT LOGGED INITIALLY clause from the ALTER TABLE statement.
sqlcode: -1749
sqlstate: 429AA
SQL1750N | Foreign keys cannot reference a parent key table "<table-name>" that was created with the NOT LOGGED INITIALLY clause. |
Explanation: A table that was created with the NOT LOGGED INITIALLY clause cannot be referenced by a foreign key.
User Response: Remove the foreign key reference to "<table-name>" in the ALTER or CREATE TABLE statement.
sqlcode: -1750
sqlstate: 429A0
SQL1751N | The resulting nodegroup would not contain any nodes that can be used in a partition map. |
Explanation: A nodegroup must contain at least one node that can be used in a partition map. If a node is added to a nodegroup WITHOUT TABLESPACES, it cannot be included in the partition map because there are no containers for the table spaces defined on the nodegroup. If a node is added LIKE another node and the other node does not have containers for all table spaces on the nodegroup then neither node can be included in the partition map.
User Response: Do not drop all the nodes in the nodegroup without adding at least one node. If tablespaces are already defined on the nodegroup but there are no tables, ensure that at least one node has containers for all the table spaces.
sqlcode: -1751
sqlstate: 428C0
SQL1752N | The table space cannot be created in the nodegroup "<ngname>". |
Explanation: The nodegroup IBMTEMPGROUP can be specified if and only if the table space is a system temporary table space.
User Response: For system temporary table spaces, specify nodegroup IBMTEMPGROUP. For other table space types, specify a nodegroup other than IBMTEMPGROUP.
sqlcode: -1752
sqlstate: 429A1
SQL1753N | Node "<node-number>" does not have containers for all the system temporary table spaces defined in the nodegroup IBMTEMPGROUP. |
Explanation: A node must have containers defined for all the system temporary table spaces defined in the nodegroup IBMTEMPGROUP for this database before it can be included in a nodegroup.
User Response: Issue the ALTER TABLESPACE statement to add containers on every node for every system temporary table space in the database.
sqlcode: -1753
sqlstate: 57052
SQL1754N | The index table space or long table space is not in the same nodegroup as the primary table space. |
Explanation: All the table spaces specified in the CREATE TABLE statement must belong to the same nodegroup.
User Response: Make sure all the table spaces specified in the CREATE TABLE statement belong to the same nodegroup.
sqlcode: -1754
sqlstate: 42838
SQL1755N | Node "<node-number>" does not have containers for all the table spaces defined in the nodegroup "<ngname>". |
Explanation: A node must have containers defined for all the table spaces defined in a nodegroup before that node can be included in a redistribution operation of a nodegroup.
User Response: Issue the ALTER TABLESPACE statement to add containers on the node for all the table spaces defined in the nodegroup.
SQL1756N | More than one clause specifies containers without the ON NODES clause. |
Explanation: For the CREATE TABLESPACE, the USING clause without the ON NODES clause can only be specified once.
For the ALTER TABLESPACE, the ADD clause without the ON NODES clause can only be specified once.
The statement was not processed.
User Response: Correct the statement and reissue it.
sqlcode: -1756
sqlstate: 428B1
SQL1757N | A USING clause without an ON NODES clause is missing. |
Explanation: In CREATE TABLESPACE statement, every USING clause specifies the ON NODES clause. However not all the nodes in the nodegroup are included, and therefore not all nodes in the nodegroup have containers.
The statement is not processed.
User Response: Ensure that the USING clause without the ON NODES clause is specified or that each node in the nodegroup is included once in an ON NODES clause.
sqlcode: -1757
sqlstate: 428B1
SQL1758W | The containers not designated for specific nodes are not used by the table space on any node. |
Explanation: The ALTER TABLESPACE and CREATE TABLESPACE statement includes container specification for all the nodes in the nodegroup. The specification of the containers that is not followed by an ON NODES clause is redundant and has been ignored.
The statement has been processed.
User Response: If the containers are needed on some of the nodes, issue an ALTER TABLESPACE statement to add the necessary containers.
sqlcode: -1758
sqlstate: 01589
SQL1759W | Redistribute nodegroup is required to change data partitioning for objects in nodegroup "<nodegroup-name>" to include some added nodes or exclude some dropped nodes. |
Explanation: This warning indicates that a change being made using the ALTER NODEGROUP or ALTER TABLESPACE statements has not caused the partitioning map for the nodegroup to be changed. The partitioning map for a nodegroup is only changed immediately by these statements if there are no tables defined using any table space defined in the nodegroup or the node being dropped is not in the partitioning map.
This warning is issued in the following cases:
For all of these cases, a table is already defined using a table space in the nodegroup.
User Response: If you want the node included or excluded for data partitioning then issue the REDISTRIBUTE NODEGROUP command or API. Another alternative is to drop all tables that use table spaces in the nodegroup.
sqlcode: +1759
sqlstate: 01618
SQL1760N | The CREATE statement for stored procedure "<procedure-name>" must have a valid LANGUAGE clause, EXTERNAL clause and PARAMETER STYLE clause. |
Explanation: A required clause is missing in the CREATE for procedure "<procedure-name>". LANGUAGE, EXTERNAL and PARAMETER STYLE must be specified.
User Response: Add the missing clause, then try again.
sqlcode: -1760
sqlstate: 42601
SQL1761N | The nodegroup "<ngname>" is not defined for the buffer pool "<bpname>". |
Explanation: The nodegroup for the table space has not been defined for the buffer pool. The table space cannot be created or altered to use this combination of nodegroup and buffer pool.
The statement cannot be processed.
User Response: The possible actions are:
sqlcode: -1761
sqlstate: 42735
SQL1762N | Unable to connect to database because there is not enough space to allocate active log files. |
Explanation: There is not enough disk space to allocate active log files.
User Response: Reduce values for LOGPRIMARY and/or LOGFILSIZ database configuartion parameters so that a smaller set of active log files are used.
SQL1763N | There are multiple container actions in the ALTER TABLESPACE statement. |
Explanation: There is more than one type of container action (ADD, EXTEND, or RESIZE) in an ALTER TABLESPACE statement. You can only specify one type of action within a single ALTER TABLESPACE statement. However, you can specify the same action multiple times over different containers within the statement.
User Response: Specify only one type of container action in the ALTER TABLESPACE statement.
sqlcode: -1763
sqlstate: 429BC
SQL1764N | Specified size for a RESIZE action in an ALTER TABLESPACE statement is smaller than the current size of the table space container. |
Explanation: The size specified in an ALTER TABLESPACE statement using the RESIZE action is smaller than the current size of the table space container. You can only increase the size of a container.
User Response: Specify a size that is larger than the current size value of the table space container.
sqlcode: -1764
sqlstate: 560B0