By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,924 Members | 1,793 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,924 IT Pros & Developers. It's quick & easy.

How to fix importing error: SQL3306N An SQL error "-289 ?

P: 1
hope someone can help me out in this error!
thanks alot!

EXPORT TO "D:\PROGRA~1\IBM\SQLLIB\WEBCPTAB.IXF" OF IXF MESSAGES "D:\PROGRA~1\IBM\SQLLIB\WEBCPTAB.EXM" SELECT * FROM DB2ADMIN.MCREC

Number of rows exported: 1271587


IMPORT FROM "D:\PROGRA~1\IBM\SQLLIB\WEBCPTAB.IXF" OF IXF COMMITCOUNT 5000 MESSAGES "D:\PROGRA~1\IBM\SQLLIB\WEBCPTAB.IMM" CREATE INTO DB2ADMIN.MCRECTEST IN WARRANTY01 INDEX IN WARRANTY02
SQL3306N An SQL error "-289" occurred while inserting a row into the table.
Feb 22 '07 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Hope you have had a reply .. just in case ... error is a tablespace free space problem .. thus extend/resize
Nov 4 '10 #2

vijay2082
100+
P: 112
Hi,

this probably points towards a space issue, which can result for various underlying conditions. Look at your diagnostic log file whihc will give you more information on what went wrong at the database level.

You can know the location of your diagnostic log files using below command

db2 get dbm cfg|grep -i "diag"

Look for the value set for DIAGPATH where you can find db2diag.log file

Complete listing for the error code for db2 v9.5 is as below:

C:\Windows\system32>db2 " ? sql289n "


SQL0289N Unable to allocate new pages in table space
"<tablespace-name>".

Explanation:

One of the following conditions is true on one or more database
partitions:

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 A rebalance is in progress, but has not progressed far enough
to enable the newly added space to be used.

4 A redirected restore is being done to containers that are too
small.

5 A rollforward is being done following a redirected restore and
all the containers assigned to this tablespace are full.

6 A rollforward skipping add containers is being done and all the
containers assigned to this tablespace are full.

7 An attempt was made to create a table space with less than 5
usable extents.

8 An auto-resize table space has reached its maximum size and all
of the containers are full. Alternately, there is not enough
space between the current size and the maximum size for
containers to be extended or added so an automatic increase in
space is not possible.

9 An automatic storage table space is being created with a value
for initial size that does not result in an equal distribution
of container space. As a result, a higher value is being used
but this value is larger than the maximum size specified.

10 A DMS table space enabled for auto-resize has not reached its
maximum size but one of the file systems on which the
containers exists is full and the container cannot grow.

11 A DMS table space enabled for auto-resize has not reached its
maximum size and the file systems on which the table space
resides are not full. However, a container operation (or a
subsequent rebalance) is in progress and the auto-resize
capability is suspended until it is complete.

12 A table space with the auto-resize feature enabled that is
managed by a database, or automatic storage, cannot increase in
size because the table space is in a WRITE SUSPEND state.

User response:

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 Wait for the rebalancer to finish.

4 Perform the redirected restore again to larger containers.

5 Perform the redirected restore again to larger containers.

6 Perform the rollforward again allowing add containers, or
perform a redirected restore to larger containers.

7 Resubmit the CREATE TABLESPACE statement, ensuring that the
table space has at least 5 usable extents.

8 Increase the maximum size for the table space.

9 Reduce the initial size or increase the maximum size for the
table space.

10 Add a new stripe set of containers to the table space. Existing
containers will no longer grow, only those new containers in
the last range of the table space are extended when an
automatic resize occurs.

11 Wait for the operation and subsequent rebalance to complete.

12 The table space must be removed from the WRITE SUSPEND state
before new pages can be allocated.

sqlcode: -289

sqlstate: 57011

Cheers, Vijay
Nov 11 '10 #3

Post your reply

Sign in to post your reply or Sign up for a free account.