Messages Reference

SQL0200 - SQL0299

Cause: The column "<name>" is used in the statement and there is more than one possible column to which it could refer. This could be the result of:

• two tables specified in a FROM clause that have columns with the same name

• the ORDER BY clause refers to a name that applies to more than one column in the select list

• a reference to a column from the subject table in a CREATE TRIGGER statement does not use the correlation name to indicate if it refers to the old or new transition variable.

The column name needs further information to establish which of the possible table columns it is.

The statement cannot be processed.

Action: Add a qualifier to the column name. The qualifier is the table name or correlation name. A column may need to be renamed in the select list.

sqlcode: -203

sqlstate: 42702

Cause: This error is caused by one of the following:

• The object identified by "<name>" is not defined in the database.

• A data type is being used. This error can occur for the following reasons:

  • If "<name>" is qualified, then a data type with this name does not exist in the database.

  • If "<name>" is unqualified, then the user's function path does not contain the schema to which the desired data type belongs.

  • The data type does not exist in the database with a create timestamp earlier than the time the package was bound (applies to static statements).

  • If the data type is in the UNDER clause of a CREATE TYPE statement, the type name may be the same as the type being defined, which is not valid.

• A function is being referenced in one of:
  • a DROP FUNCTION statement
  • a COMMENT ON FUNCTION statement
  • the SOURCE clause of a CREATE FUNCTION statement

    If "<name>" is qualified, then the function does not exist. If "<name>" is unqualified, then a function of this name does not exist in any schema of the current function path. Note that a function cannot be sourced on the COALESCE, NULLIF, or VALUE built-in functions.

This return code can be generated for any type of database object.

DataJoiner users: the object identified by "<name>" is not defined in the database or "<name>" is not a nickname in a DROP NICKNAME statement.

Some DataJoiner data sources do not provide the appropriate values for "<name>". In these cases, the message token will have the following format: "OBJECT:<data source> TABLE/VIEW", indicating that the actual value for the specified data source is unknown.

The statement cannot be processed.

Action: Ensure that the object name (including any required qualifiers) is correctly specified in the SQL statement and it exists. For missing data type or function in SOURCE clause, it may be that the object does not exist, OR it may be that the object does exist in some schema, but the schema is not present in your function path.

DataJoiner users: if the statement is DROP NICKNAME, make sure the object is actually a nickname. The object might not exist at DataJoiner or at the data source. Verify the existence of the DataJoiner objects (if any) and the data source objects (if any).

sqlcode: -204

sqlstate: 42704

Cause: If "<object-name>" is a table or view, then "<name>" is a column that is not defined in "<object-name>". If "<object-name>" is a structured type, then "<name>" is an attribute that is not defined in "<object-name>".

DataJoiner users: "<object-name>" could refer to a DataJoiner nickname.

The statement cannot be processed.

Action: If "<object-name>" is a table or view, verify that the column and table or view names (including any required qualifiers) are specified correctly in the SQL statement. If "<object-name>" is a structured type, verify that the attribute and type names (including any required qualifiers) are specified correctly in the SQL statement.

Also, if you receive this error during a REORG or an IMPORT, the column names in the index may violate the database manager naming rules as defined in the Administration Guide.

sqlcode: -205

sqlstate: 42703

Cause: This error can occur in the following cases:

• For an INSERT or UPDATE statement, the specified column is not a column of the table, or view that was specified as the object of the insert or update.
• For a SELECT or DELETE statement, the specified column is not a column of any of the tables or views identified in a FROM clause in the statement.
• For an ORDER BY clause, the specified column is a correlated column reference in a subselect, which is not allowed.
• For a CREATE TRIGGER statement:
  • A reference is made to a column of the subject table without using an OLD or NEW correlation name.
  • The left hand side of an assignment in the SET transition-variable statement in the triggered action specifies an old transition variable where only a new transition variable is supported.

The statement cannot be processed.

Action: Verify that the column and table names are specified correctly in the SQL statement. For a SELECT statement, ensure that all the required tables are named in the FROM clause. For a subselect in an ORDER BY clause, ensure that there are no correlated column references. If a correlation name is used for a table, verify that subsequent references use the correlation name and not the table name.

For a CREATE TRIGGER statement, ensure that only new transition variables are specified on the left hand side of assignments in the SET transition-variable statement and that any reference to columns of the subject table have a correlation name specified.

sqlcode: -206

sqlstate: 42703

Cause: A SELECT statement with a set operator contains an ORDER BY clause, which specifies column names. In this case, the list of columns in the ORDER BY clause must contain only integers.

The statement cannot be processed.

Action: Specify only integers in the list of columns in the ORDER BY clause.

NOTE: This error is only applicable to releases of DB2 prior to Version 2 and hosts accessed through DB2 Connect.

sqlcode: -207

sqlstate: 42706

Cause: The statement is not valid because a column "<name>" specified in the ORDER BY list is not specified in the SELECT list and is not in the result table. Only columns in the result table can be used to order that result when the fullselect of the select-statement is not a subselect.

The statement cannot be processed.

Action: To correct the syntax of the statement, either add the specified column to the result table or delete it from the ORDER BY clause.

sqlcode: -208

sqlstate: 42707

Cause: The exposed table, view, alias, or correlation name specified by "<name>" is identical to another exposed table, view, alias, or correlation name in the same FROM clause.

If the statement is a CREATE TRIGGER, the REFERENCING clause may have specified the same name as the subject table or may have the same name for more than one of the OLD or NEW correlation names or the NEW_TABLE or OLD_TABLE identifiers.

The statement cannot be processed.

Action: Rewrite the FROM clause of the SELECT statement. Associate correlation names with table, view, or alias names so no exposed table, view, alias, or correlation name is identical to any other exposed table, view, alias, or correlation name in the FROM clause.

For a CREATE TRIGGER statement, change the names in the REFERENCING clause so that there are no duplicates.

sqlcode: -212

sqlstate: 42712

Cause: The expression identified by the first part of the expression "<expression-start>" in the "<clause-type>" clause is not valid for the reason specified by the "<reason-code>" as follows:

1

The fullselect of the select-statement is not a subselect. Expressions are not allowed in the ORDER BY clause for this type of select-statement. This reason code occurs only when "<clause-type>" is ORDER BY.

2

DISTINCT is specified in the select clause and the expression cannot be matched exactly with an expression in the select list. This reason code occurs only when "<clause-type>" is ORDER BY.

3

Grouping is caused by the presence of a column function in the ORDER BY clause. This reason code occurs only when "<clause-type>" is ORDER BY.

4

Expression in a GROUP BY clause cannot be a scalar-fullselect. This reason code occurs only when "<clause-type>" is GROUP BY.

5

The left side of a dereference operator in a GROUP BY clause cannot be a variant function. This reason code occurs only when "<clause-type>" is GROUP BY.

The statement cannot be processed.

Action: Modify the select-statement based on the reason specified by the "<reason-code>" as follows:

1

Remove the expression from the ORDER BY clause. If attempting to reference a column of the result, change the sort key to the simple-integer or simple-column-name form.

2

Remove DISTINCT from the select clause or change the sort key to the simple-integer or simple-column-name form.

3

Add a GROUP BY clause or remove the column function from the ORDER BY clause.

4

Remove any scalar-fullselect from the GROUP BY clause. If grouping is desired on a column of the result that is based on a scalar-fullselect use a nested table expression or a common table expression to first provide a result table with the expression as a column of the result.

5

Remove any variant function from the left side of the dereference operators in the GROUP BY clause.

sqlcode: -214

sqlstate: 42822

Cause: A predicate includes a list of elements on the right or left side (or both sides) of the predicate operator. The number of elements must be the same on both sides. These elements may appear in a list of expressions enclosed in parentheses or as elements of a select list in a fullselect.

The statement cannot be processed.

Action: Correct the predicate with mismatched number of elements on each side of the predicate operator.

sqlcode: -216

sqlstate: 428C4

Cause: The current value of one of the Explain special registers has been set to EXPLAIN. This value allows dynamic SQL statements to be prepared and explained but prevents any dynamic statement from being executed.

Action: Change the value of the appropriate Explain special register to a setting other than EXPLAIN by issuing the appropriate SET statement from the interface or application that is encountering this condition.

sqlcode: +217

sqlstate: 01604

Cause: The Explain facility has been invoked but was unable to find the required Explain table "<name>". The Explain tables must be created prior to invoking Explain.

Action: Create the required Explain tables. The SQL Data Definition Language statements needed to create the Explain tables are available in the file called EXPLAIN.DDL in the misc directory under sqllib.

sqlcode: -219

sqlstate: 42704

Cause: The Explain facility has been invoked but the Explain table "<name>" did not have the expected definition. The definition could be incorrect due to:

• Incorrect number of columns defined (if "<name2>" is numeric)
• Incorrect data type assigned to columns (if "<name2>" is a column name).

Action: Correct the definitions of the specified Explain table. The SQL Data Definition Language statements needed to create the Explain tables are available in the file called EXPLAIN.DDL in the misc directory under sqllib.

sqlcode: -220

sqlstate: 55002

Cause: The value of the SQLN field of the SQLDA should be at least as large as the number of columns in the result set.

The database manager has not set any SQLVAR entries (and the SQLDOUBLED flag has been set to "off" (i.e. to the space character)).

Action: Increase the value of the SQLN field in the SQLDA to the value indicated in the message (making sure the SQLDA is large enough to support that amount) and resubmit the statement.

sqlcode: +236

sqlstate: 01005

Cause: Since at least one of the columns in the result set is a distinct type, space should be provided for twice as many SQLVAR entries as the number of columns in the result set. The database manager has only set the Base SQLVAR entries (and the SQLDOUBLED flag has been set off (i.e. to the space character).

Action: If there is no need for the additional information about the distinct type(s) in the result set, then no action is required. If the distinct type information is needed, the value of the SQLN field in the SQLDA should be increased to the value indicated in the message (after making sure that the SQLDA is large enough to support that amount) and the statement should be resubmitted.

sqlcode: +237

sqlstate: 01594

Cause: Since at least one of the columns in the result set is a LOB, space must be provided for twice as many SQLVAR entries as the number of columns in the result set. Note also that one or more of the columns in the result set may be a distinct type.

The database manager has not set any SQLVAR entries (and the SQLDOUBLED flag has been set off (i.e. to the space character).

Action: Increase the value of the SQLN field in the SQLDA to the value indicated in the message (after making sure that the SQLDA is large enough to support that amount) and resubmit the statement.

sqlcode: +238

sqlstate: 01005

Cause: If any of the columns in the result set is a distinct type then space should be provided for twice as many SQLVAR entries as the number of columns in the result set.

The database manager has not set any SQLVAR entries (and the SQLDOUBLED flag has been set off (i.e. to the space character).

Action: If the distinct type information is needed, the value of the SQLN field in the SQLDA should be increased to the value indicated in the message (after making sure the SQLDA is large enough to support that amount) and the statement should be resubmitted. If there is no need for the additional information about the distinct type(s) in the result set, then it is possible to resubmit the statement only providing enough SQLVAR entries to accommodate the number of columns in the result set.

sqlcode: +239

sqlstate: 01005

Cause: An attempt was made to use DEVICE containers. These are not currently supported on this platform.

Action: Use FILE containers or system-managed table spaces instead.

sqlcode: -257

sqlstate: 42994

Cause: One of the following conditions is true:

1. An ALTER TABLESPACE to add containers to the same table space (on the same node) has previously been issued in the same unit of work. Containers for a table space can only be added to one node in one ALTER TABLESPACE statement in a unit of work.
2. The table space to which you are adding containers is currently being rebalanced. Details can be found in the system error log and/or the database manager error log.

Action:

1. If possible, roll back the unit of work and issue a single ALTER TABLESPACE to add all the containers. Otherwise, wait until the rebalance has completed and then try the operation again.
2. Wait until the rebalance has completed and then try the operation again.

sqlcode: -258

sqlstate: 55041

Cause: The map structure keeps a record of how the table space address space is mapped to the various containers. If this gets too complicated, it does not fit in the table space file.

Details can be found in the system error log and/or the database manager error log.

Action: The table space may need to be rebalanced to more evenly distribute the data among the containers. This may simplify the mapping.

If this does not work, try making as many containers as possible the same size. Existing container sizes can be changed by backing up the table space and then using the database administration utility to change the containers. Restore the table space to the new containers.

sqlcode: -259

sqlstate: 54037

Cause: A partitioning key cannot have a LONG-type column.

The statement cannot be processed.

Action: Use only non-LONG type columns for the partitioning key.

If the table does not have a non-LONG type column, either add one to the table and use it for the partitioning key, or define the table without a partitioning key in a single-node nodegroup.

sqlcode: -260

sqlstate: 42962

Cause: The table "<table-name>" consisting of only LONG-type columns cannot be created in a multinode nodegroup. The table must have at least one non-LONG type column for use in a partitioning key.

The statement cannot be processed.

Action: Either create the table with one or more non-LONG type columns, or create the table in a single-node nodegroup.

sqlcode: -262

sqlstate: 428A2

Cause: The specified node range is not valid.

The statement cannot be processed.

Action: Correct the node range in the statement, then try the request again.

sqlcode: -263

sqlstate: 428A9

Cause: You can only add or drop a partitioning key on a table in a single-node nodegroup.

The statement cannot be processed.

Action: Do one of the following and try the request again:

• Define an identical table with a partitioning key.
• Redistribute the nodegroup to a single-node nodegroup.

sqlcode: -264

sqlstate: 55037

Cause: For the CREATE NODEGROUP statement, a node can only appear once in the ON NODES clause.

For the CREATE TABLESPACE and ALTER TABLESPACE statement, a node can appear only once and in only one ON NODES clause.

For the ALTER NODEGROUP statement or REDISTRIBUTE NODEGROUP command, one of the following occurred:

• The node appeared more than once in the ADD NODES or the DROP NODES clause.

• The node appeared in both the ADD NODES and the DROP NODES clause.

• The node to be added is already a member of the nodegroup.

The statement cannot be processed.

Action: Ensure that the node names or node numbers in the ON NODES, ADD NODES, or DROP NODES clause are unique. For the CREATE TABLESPACE and ALTER TABLESPACE statements, ensure that a node appears in no more than one ON NODES clause.

In addition, for the ALTER NODEGROUP statement or REDISTRIBUTE NODEGROUP command:

• Do not specify a node in both the ADD NODES and the DROP NODES clause.

• Remove the node from the ADD NODES clause if the node is already defined in the nodegroup.

sqlcode: -265

sqlstate: 42728

Cause: The node "<node-number>" is not valid for one of the following reasons:

• the node number is not in the valid range of 0 to 999
• the node is not in the node configuration file
• the node is not part of the nodegroup, therefore the requested operation cannot be processed.

The statement cannot be processed.

Action: Depending on the condition:

• issue the statement, command or API with node numbers in the valid range.
• follow the procedure to add a node to the system.
• remove the node from the specified nodes in the statement, command or API.

sqlcode: -266

sqlstate: 42729

Cause: One of the following:

• The nodegroup is being redistributed. It cannot be altered, dropped or redistributed again until the current operation is complete.

• The partitioning key of a table cannot be dropped while the nodegroup of the table is being redistributed.

The statement cannot be processed.

Action: Wait until the redistribution is complete, then try the request again.

sqlcode: -268

sqlstate: 55038

Cause: Because the database contains the maximum number of partitioning maps (32,768), you cannot create a new nodegroup, alter a nodegroup, or redistribute an existing one.

The statement cannot be processed.

Action: Drop one or more nodegroups in the database.

Note: Dropping a nodegroup drops all database objects such as table spaces, tables and views that reside in the nodegroup.

sqlcode: -269

sqlstate: 54033

Cause: The statement cannot be processed because it violates a restriction as indicated by the following reason code:

1

The primary key, each unique constraint, and each unique index must contain all partitioning columns of the table (columns may appear in any order).

2

Update of the partitioning key column value is not supported.

3

A foreign key cannot include any nullable partitioning key columns when defined with ON DELETE SET NULL. This is a special case of reason code 2 since defining such a constraint would result in attempting to update a partitioning key column.

4

A table defined using a multipartition nodegroup or a single-partition nodegroup on other than the catalog partition does not support DATA CAPTURE CHANGES.

5

View created with the WITH CHECK OPTION should not use functions (or reference views that use functions ) that:

• are non-deterministic
• have side effects
• are related to the placement of data (for example nodenumber or partition functions).

These functions must also not be present within referenced views if the new view is created with the CASCADED check option.

6

A transform cannot be defined for a user-defined distinct type.

7

Long fields can only be defined using a table space with a page size that is 4K. A LONG TABLESPACE can only be created using a 4K page size.

8

Structured types are not supported as columns of a table or structured type attribute data types.

9

Triggers are not supported on typed tables.

10

A single default table space cannot be selected since the table has one or more LOB columns which must be placed in a table space with a 4K page size and the rowsize or number of columns in the table requires a table space with an 8K page size.

11

A typed table or typed view cannot be created using a structured type that has no attributes.

12

The type of a source key parameter must be a user-defined structured type.

13

Check constraints cannot be defined on a typed table or the WITH CHECK OPTION cannot be specified on a typed view.

14

Referential constraints cannot be defined on a typed table or to a parent table that is a typed table.

15

A default value cannot be defined for reference type columns.

16

A reference data type or structured data type cannot be used as a parameter data type or a returns data type of a user defined function.

17

The SET CONSTRAINTS statement cannot be used for a typed table.

18

Column level UPDATE and REFERENCES privileges cannot be granted on a typed table or typed view.

19

A specific default value must be specified when defining a default for a column of a typed table.

20

ALTER TABLE is not supported for a summary table.

21

Column length cannot be altered on a table which is a base table for a summary table.

22

Summary tables cannot be defined in a CREATE SCHEMA statement.

23

REPLICATED can only be specified for a summary table defined with REFRESH IMMEDIATE.

24

The triggered-SQL-statement in a BEFORE trigger cannot reference a summary table defined with REFRESH IMMEDIATE.

25

Only one summary table can be specified for a SET CONSTRAINTS statement.

26

The nodegroup being redistributed contains at least one replicated summary table.

27

Replicated summary tables cannot be defined on a table that does not have a unique index existing on one or more columns that make up the replicated summary table.

28

A typed table or summary table cannot be renamed.

29

FOR EXCEPTION clause cannot be specified with a summary table in the SET CONSTRAINTS statement.

Action: The action corresponding to the reason code is:

1

Correct the CREATE TABLE, ALTER TABLE or CREATE UNIQUE INDEX statment.

2

Do not attempt to update the partitioning key columns for a multipartition table or consider deleting and then inserting the row with the new values in the partitioning columns.

3

Make the partitioning key column not nullable, specify a different ON DELETE action, or change the partitioning key of the table so that the foreign does not include any columns of the partitioning key.

4

Either specify DATA CAPTURE NONE or ensure that the table is placed in a table space on a single-partition nodegroup that specifies the catalog partition.

5

Do not use the WITH CHECK OPTION or remove the function or view from the view definition.

6

Transforms are automatic for user-defined distinct types. Use the CREATE TRANSFORM statement for user-defined structured types only.

7

Use a table space with 4K page size for any table that includes long fields. If using DMS table spaces, long fields can be placed in a table space with 4K page size with other table or index data in table spaces with a different page size. When defining a LONG TABLESPACE, use PAGESIZE 4K.

8

Ensure that no column data types are structured types in the CREATE TABLE statement or ALTER TYPE ADD COLUMN statement. Ensure that no attribute data types are structured types in the CREATE TYPE statement or ALTER TYPE ADD ATTRIBUTE statement.

9

Do not define triggers on typed tables.

10

Either reduce the row size or number of columns in the table or specify 2 table spaces such that the long data is in a table space with a 4K page size and the base data is in a table space with an 8K page size.

11

When creating a typed table or typed view, specify a structured type that has at least one attribute defined.

12

Use only a structured type as the type of a source key parameter.

13

In a CREATE TABLE or ALTER TABLE statement for a typed table, do not specify check constraints. In a CREATE VIEW statement of a typed view, do not specify the WITH CHECK OPTION.

14

Do not specify referential constraints involving typed tables in a CREATE TABLE or ALTER TABLE statement.

15

Do not specify a DEFAULT clause for a column with a reference data type in a CREATE TABLE or ALTER TABLE statement.

16

Do not specify a reference type or structured type parameter or returns type that is a reference type when creating a user defined function.

17

Do not specify a typed table in the SET CONSTRAINTS statement.

18

Do not include specific column names when granting REFERENCES or UPDATE privileges on a typed table or typed view.

19

Include a specific value when specifying the DEFAULT clause on a column of a typed table.

20

Drop the summary table and recreate it with the desired attributes.

21

Drop the summary table(s), alter the column length of the base table and then recreate the summary table(s).

22

Issue the CREATE SUMMARY TABLE statement outside of the CREATE SCHEMA statement.

23

Either remove the REPLICATED specification or ensure that REFRESH IMMEDIATE is specified for the summary table definition.

24

Remove the reference to the summary table in the triggered-SQL-statement in the BEFORE trigger.

25

Issue separate SET CONSTRAINTS IMMEDIATE CHECKED statements for each summary table.

26

Drop all replicated summary tables in the nodegroup and then issue the REDISTRIBUTE NODEGROUP command again. Recreate the replicated summary table(s).

27

Ensure that a subset of the columns defined for the summary table also are the set of columns that make up a unique index on the base table.

28

A typed table or summary table name can only be changed by dropping the table and creating it again with the new name. Dropping the table may have implications on other objects that depend on the table and the privileges on the table are lost.

29

Remove the FOR EXCEPTION clause from the SET CONSTRAINTS statement.

sqlcode: -270

sqlstate: 42997

Cause: The index file for the table with fid "<fid>" is required during processing. The file is either missing, or it is not valid.

The statement cannot be processed, and the application is still connected to the database. This condition does not affect other statements that do not use the index on this table.

Action: Ensure that all users are disconnected from the database, then issue the RESTART DATABASE command on all nodes. Then try the request again.

The index (or indexes) is re-created when the database is restarted.

sqlcode: -271

sqlstate: 58004

Cause: The database must be restored before a connection can be done.

No connection was made.

Action: Restore the database, then issue the CONNECT statement again.

sqlcode: -276

sqlstate: 08004

Cause: Commit processing encountered an error. The transaction has been put in the commit state, but the commit processing may not have completed. The application's database connection has been terminated.

The cause of the error is indicated by the "<reason-code>":

1

A node involved in the transaction has failed.

2

Commit was rejected on one for the nodes. Check the db2diag.log file for details.

Action: Determine the cause of the error. It may be necessary to contact the system administrator for assistance since the most common cause of the error is node failure or connection failure. The RESTART DATABASE command will complete the commit processing for this transaction.

sqlcode: -279

sqlstate: 08007

Cause: An existing inoperative view, trigger or summary table "<name>" was replaced by:

• the new view definition as a result of a CREATE VIEW statement

• the new trigger definition as a result of a CREATE TRIGGER statement

• the new summary table definition as a result of a CREATE SUMMARY TABLE statement.

Action: None required.

sqlcode: +280

sqlstate: 01595

Cause: Additional containers cannot be added to a system managed table space. The exception to this is when a nodegroup was modified to add a node without table spaces, then containers can be added once on the new node using the ALTER TABLESPACE command. In general, the table space must be managed by the database in order to add additional containers.

The statement cannot be processed.

Action: To add more containers to a system managed table space, drop and recreate the table space with more containers, ensuring that each container is of the same size and less than the container size limit, or change to a DMS table space.

sqlcode: -281

sqlstate: 42921

Cause: A table in the specified table space does not contain all its parts in that table space. The base table, indexes or long data may be in another table space. Dropping this table space will not completely drop the table. This would leave the table in an inconsistent state. This table space cannot be dropped.

Action: Ensure that all objects contained in table space "<tablespace-name>" contain all their parts in this table space before attempting to drop the table space.

This may require dropping the table "<table-name>" before dropping the table space.

sqlcode: -282

sqlstate: 55024

Cause: A database must contain at least one temporary table space with a 4K page size. Dropping table space "<tablespace-name>" would remove the last temporary table space with a 4K page size from the database.

Action: Ensure there will be another temporary table space with a 4K page size in the database before attempting to delete this table space.

sqlcode: -283

sqlstate: 55026

Cause: The CREATE TABLE statement specified a table space named "<tablespace-name>" following the clause "<clause>" that is not a valid type of table space for this clause.

This can occur in the following situations:

• "<tablespace-name>" was specified on the IN clause and the table space is not a REGULAR table space.

• "<tablespace-name>" was specified on the LONG IN clause and the table space is not a LONG, managed by database table space.

• "<tablespace-name>" was specified on the INDEX IN clause and the table space is not a REGULAR, managed by database table space.

Action: Correct the CREATE TABLE statement to specify a table space with the correct type for the "<clause>" clause.

sqlcode: -284

sqlstate: 42838

Cause: If the primary table space is a system managed table space, all table parts must be contained in that table space. A table can have parts in separate table spaces only if the primary table space, index table space and long table space are database managed table spaces.

Action: Either specify a database managed table space for the primary table space, or do not assign the table parts to another table space.

sqlcode: -285

sqlstate: 42839

Cause: The CREATE TABLE statement did not specify a table space.

A table space having sufficient page size

• with the name IBMDEFAULTGROUP, or
• defined by the user, or
• with the name USERSPACE1

does not exist in the database. These are the valid defaults. Sufficient page size of a table is determined by either the byte count of the row or the number of columns.

Action: Specify a valid table space name in the CREATE TABLE statement or ensure that a valid default table space exists in the database.

sqlcode: -286

sqlstate: 42727

Cause: The CREATE TABLE statement specified a table space named SYSCATSPACE which is reserved for catalog tables.

Action: Specify a different table space name.

sqlcode: -287

sqlstate: 42838

Cause: The table space being defined is for use with large objects and long strings. These can only be stored in table spaces that are defined in database managed space. Thus a long table space cannot be defined to use system managed space.

Action: Remove the keyword LONG or change to MANAGED BY DATABASE in the CREATE TABLESPACE statement.

sqlcode: -288

sqlstate: 42613

Cause: One of the following conditions is true:

1. One of the containers assigned to this SMS table space has reached the maximum file size. This is the likely cause of the error.
2. All the containers assigned to this DMS table space are full. This is the likely cause of the error.
3. The table space object table for this DMS table space is full.
4. A rebalance is in progress, but has not progressed far enough to enable the newly added space to be used.
5. A redirected restore is being done to containers that are too small.
6. A rollforward is being done following a redirected restore and all the containers assigned to this tablespace are full.
7. A rollforward skipping add containers is being done and all the containers assigned to this tablespace are full.

Details can be found in the system error log and/or the database manager error log.

Action: Perform the action corresponding to the cause of the error:

1. either switch to a DMS TABLESPACE or recreate the SMS TABLESPACE with more directories (PATHs) such that: (number of directories) >= (max tablesize / maxfilesize). Note that maximum file size is operating system dependent.
2. add new container(s) to the DMS table space and try the operation again, after the rebalancer has made the new pages available for use.
3. drop unnecessary tables from this DMS table space.
4. wait for the rebalancer to make more progress.
5. perform the redirected restore again to larger containers.
6. perform the redirected restore again to larger containers.
7. perform the rollforward again allowing add containers, or perform a redirected restore to larger containers.

sqlcode: -289

sqlstate: 57011

Cause: A process attempted to access a table space which is in an invalid state for which the intended access is not allowed.

• If the table space is in a quiesced state, only processes which also hold the table space in a quiesced state are allowed access to the table space.
• If the table space is in any other state, only the process which is performing the action specified is allowed access to the table space.
• A temporary table space cannot be dropped which contains active temporary tables.
• The SET CONTAINER api cannot be used to set the container list unless the table space is in a "restore pending" state.

Details can be found in the system error log and/or the database manager error log.

Action: Possible actions include:

• If the table space is in a quiesced state, attempt to acquire a quiesced share or quiesced update state on the table space. Or, attempt to quiesce reset the table space.
• If the table space is in any other state, wait until the table space has returned to normal state before attempting to access the table space.

Refer to the systems administration guide for further information about the table space states.

sqlcode: -290

sqlstate: 55039

Cause: An attempt was made to change the state of a table space. Either the new state is not compatible with the current state of the table space, or an attempt was made to turn off a particular state and the table space was not in that state.

Details can be found in the system error log and/or the database manager error log.

Action: Table space states change when a backup is taken, the load completes, the rollforward completes, etc., depending on the current state of the table spaces. Refer to the systems administration guide for further information about the table space states.

sqlcode: -291

sqlstate: 55039

Cause: An internal database file could not be created. Details can be found in the system error log and/or the database manager error log.

Action: Check that the directory containing the file is accessible (e.g. mounted) and writeable by the database instance owner.

sqlcode: -292

sqlstate: 57047

Cause: One of the following conditions is true:

• A container (directory, file or raw device) was not found.
• A container is not tagged as being owned by the proper table space.
• A container tag is corrupt.

Details can be found in the system error log and/or the database manager error log.

Action: Try the following:

1. Check that the directory, file or device exists and that the file system is mounted (if it is on a separate file system). Containers must be readable and writable by the database instance owner.

2. If you have a recent backup, try restoring the table space or database. If that fails because of the bad container and the container is not a DEVICE type, try manually removing the container first.

3. Call your IBM service representative.

sqlcode: -293

sqlstate: 57048

Cause: Table space containers may not be shared. The possible causes of this error include the following.

• A CREATE TABLESPACE or ALTER TABLESPACE statement included a container that is already in use by another table space.

• A CREATE TABLESPACE or ALTER TABLESPACE statement included a container from a table space that has been dropped but the drop statement has not been committed.

• An ALTER NODEGROUP statement used to add a node used the containers of a LIKE node that is on the same physical node. These containers would therefore already be in use.

• A CREATE TABLESPACE or ALTER TABLESPACE statement is attempting to use the same container on more than one logical node on a single physical node. The same containers cannot be used for more than one node on the same physical node.

• An ADD NODE command or API used the containers from the temporary table spaces of a LIKE node that is on the same physical node. These containers would therefore already be in use.

Details can be found in the system error log and/or the database manager error log.

Action: Ensure the containers are unique.

• For the CREATE or ALTER TABLESPACE statement, specify a different container for the table space.

• For the CREATE or ALTER TABLESPACE statement including a container from a dropped table space, try again after the drop statement is committed or specify a different container.

• For the ALTER NODEGROUP statement, reissue the statement using the WITHOUT TABLESPACES clause, and then use the ALTER TABLESPACE statement to create unique containers for the new node.

• For CREATE or ALTER TABLESPACE statements where the environment includes more than one logical node on a physical node, ensure that the same containers are not specified for such logical nodes.

• For an ADD NODE command or API, reissue the statement using the WITHOUT TABLESPACES clause, and then use the ALTER TABLESPACE statement to create unique containers at the new node for the temporary table spaces.

sqlcode: -294

sqlstate: 42730

Cause: The total space required to store the list of containers exceeds the space allotted for this table space in the table space file.

Details can be found in the system error log and/or the database manager error log.

Action: Try one or more of the following:

• Use symbolic links, mounted file systems, etc. to shorten the new container names.
• Back up the table space and then use the database administration utility to reduce the number and/or name lengths of the containers. Restore the table space to the new containers.

sqlcode: -295

sqlstate: 54034

Cause: This database contains the maximum number of table spaces. No more can be created.

Details can be found in the system error log and/or the database manager error log.

Action: Delete table spaces that are not being used any more. Combine small table spaces by moving all data into one of them and deleting the other.

sqlcode: -296

sqlstate: 54035

Cause: The full path specifying the container name exceeds the maximum length allowed. If the container was specified as a path relative to the database directory, the concatenation of these two values must not exceed the maximum length.

Details can be found in the system error log and/or the database manager error log.

Action: Shorten the path length.

sqlcode: -297

sqlstate: 54036

Cause: The container path violates one of the following requirements:

• Container paths must be valid fully-qualified absolute paths or valid relative paths. The latter are interpreted relative to the database directory.
• The path must be read/write accessible to the instance id (check file permissions on UNIX-based systems).
• Containers must be of the type specified in the command (directory, file or device).
• Containers (directories) in system managed table spaces must be empty when designated as containers and must not be nested underneath other containers.
• The containers for one database must not be located underneath the directory of another database, and they may not be underneath any directory that appears to be for another database. This rules out any directory of the form SQLnnnnn, where 'n' is any digit.
• The container must be within the file size limit for the operating system.
• Containers (files) for dropped database managed table spaces can only be reused as containers (directories) for system managed table spaces after all agents terminate and vice versa.
• During a redirected restore, an SMS container was specified for a DMS table space or a DMS container was specified for an SMS table space.

This message will also be returned if any other unexpected error occurred which prevents DB2 from accessing the container.

Details can be found in the system error log and/or the database manager error log.

Action: Specify another container location or change the container to make it acceptable to DB2 (such as changing file permissions) and try again.

sqlcode: -298

sqlstate: 428B2

Cause: The container that you are attempting to add has already been assigned to the table space.

Details can be found in the system error log and/or the database manager error log.

Action: Choose another container and try again.

sqlcode: -299

sqlstate: 42731

[ DB2 List of Books | Search the DB2 Books ]