SQL2216N: Difference between revisions

From EggeWiki
(Created page with "Q: I'm getting this error on DB2 9.7: <pre> Reorg command failed: SQL2216N SQL error "-291" occurred while reorganizing a database table or its indexes. SQLSTATE=01H52 </pre...")
 
mNo edit summary
 
Line 5: Line 5:


A: Your database is currently being backed up. Check the status of your tablespace(s)
A: Your database is currently being backed up. Check the status of your tablespace(s)
You can see the db2 detailed help as follows:
<pre>
$ db2 \? sql0968
SQL0968C  The file system is full.
Explanation:
One of the file systems containing the database is full. This file
system may contain the database directory, the database log files, or a
table space container.
The statement cannot be processed.
User response:
Free system space by erasing unwanted files. Do not erase database
files. If additional space is required, it may be necessary to drop
tables and indexes identified as not required.
On unix-based systems, this disk full condition may be due to exceeding
the maximum file size allowed for the current userid. Use the chuser
command to update fsize. A reboot may be necessary.
This disk full condition may be caused when containers are of varying
sizes. If there is sufficient space in the file system, drop the table
space and recreate it with containers of equal size.
If the statement that could not be processed referenced LOB data types:
*  Ensure that any cursors used in the application are closed
  immediately after their use.
*  Ensure that within the application that COMMIT statements are
  periodically executed.
*  Add additional containers to the system temporary tablespace to hold
  the temporary LOB data during this statement's execution.
sqlcode: -968
sqlstate: 57011
</pre>


[[Category:db2]]
[[Category:db2]]

Latest revision as of 13:46, 13 August 2012

Q: I'm getting this error on DB2 9.7:

Reorg command failed: SQL2216N  SQL error "-291" occurred while reorganizing a database table or its indexes.  SQLSTATE=01H52

A: Your database is currently being backed up. Check the status of your tablespace(s)

You can see the db2 detailed help as follows:

$ db2 \? sql0968


SQL0968C  The file system is full.

Explanation:

One of the file systems containing the database is full. This file
system may contain the database directory, the database log files, or a
table space container.

The statement cannot be processed.

User response:

Free system space by erasing unwanted files. Do not erase database
files. If additional space is required, it may be necessary to drop
tables and indexes identified as not required.

On unix-based systems, this disk full condition may be due to exceeding
the maximum file size allowed for the current userid. Use the chuser
command to update fsize. A reboot may be necessary.

This disk full condition may be caused when containers are of varying
sizes. If there is sufficient space in the file system, drop the table
space and recreate it with containers of equal size.

If the statement that could not be processed referenced LOB data types:
*  Ensure that any cursors used in the application are closed
   immediately after their use.
*  Ensure that within the application that COMMIT statements are
   periodically executed.
*  Add additional containers to the system temporary tablespace to hold
   the temporary LOB data during this statement's execution.

 sqlcode: -968

 sqlstate: 57011