Message Reference

SQL1700 - SQL1799

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:

1

an invalid schema name was found.

2

database is not migrateable. The database could be in one of the following states:

backup pending state
roll-forward pending state
transaction inconsistent state.

3

database logs are full.

4

insufficient disk space.

5

cannot update database configuration file.

6

failed to relocate database.

7

failed to access the database subdirectory or one of the database files.

8

failed to update database container tag.

9

table space access is not allowed.

10

an invalid type name was found.

11

structured type and function have the same name.

12

structured type/table has an invalid attribute.

13

structured type encountered.

User Response: Possible solutions based on the reason code are:

1: The reserved schema names are: SYSIBM, SYSCAT, SYSSTAT, and SYSFUN. Ensure that all the database objects that use one or more of these schema names are dropped and recreate the objects using a different schema name. This correction must be made in the release of database manager in use prior to the current release. Resubmit the database migration command under the current release.
2: Correct the database state by going back to release of database manager in use prior to the current release and perform any necessary corrective action to the database. Resubmit the database migration command under the current release.
3: Increase the database configuration parameters logfilsiz or logprimary to a larger value. Resubmit the database migration command.
4: Ensure that there is sufficient disk space and resubmit the database migration command.
5: There was a problem in updating the database configuration file. Ensure that the database configuration file is not being held exculsively by any users and is updateable. Resubmit the database migration command. If the problem persists, inform your IBM service representatives.
6: Restore the database from the database backup.
7: Restore the database from the database backup.
8: Resubmit the database migration command. If the problem persists, contact your IBM service representative.
9: Correct the table space by going back to the release of the database manager in use prior to the current release. Refer to message SQL0290N for the suggested actions to take to correct the table space.
10: The type name is reserved by the system. Ensure that the type and database objects that use the type are dropped and recreated using a non-reserved type name. This correction must be made in the release of database manager in use prior to the current release. Resubmit the database migration command under the current release.
11: A structured type and function (with no arguments) belonging to the same schema cannot have the same name. Ensure that the type or function and database objects that use the type or function are dropped and recreated using a different name. This correction must be made in the release of database manager in use prior to the current release. Resubmit the database migration command under the current release.
12: Attribute may have defaults, may be defined as long varchar or long vargraphic, or include null constraints. The attribute has to be dropped and added back to the type according to the attribute definition rules in the CREATE TYPE statement.
13: Restore the database from the database backup. Drop all structured types (and related objects, e.g., typed tables, typed views). Resubmit the database migration command.

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.

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 temporary table space.

User Response: For temporary table space, 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 temporary table spaces defined in the nodegroup IBMTEMPGROUP.

Explanation: A node must have containers defined for all the 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 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:

One or more nodes are added using ALTER NODEGROUP ADD NODE
One or more nodes are dropped using ALTER NODEGROUP DROP NODE
Containers are added for table space and no further containers are required for a node to be used.

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:

specify a buffer pool that has defined the nodegroup for the table space
alter the buffer pool to add the nodegroup of the table space
If CREATE TABLESPACE, specify a nodegroup that is defined for the buffer pool.

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.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]