If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Question re: ReOrg

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 11-16-05, 15:26
bunzo bunzo is offline
Registered User
 
Join Date: Apr 2005
Posts: 28
Question re: ReOrg

Using DB2 UDB v7.2 under Windows Server 2000.

I have a database that contains 9 tables. I'm having performance problems when running queries on the primary data table. I shut down all applications that connect to this database and ran RunStats on all tables. I then ran a ReOrg on 8 of 9 tables. When selecting the ReOrg from within the Control Panel, I am prompted to select a table space and an index. Most tables would reorg successfully when I selected TempSpace1 and the index identified as the pk_index. Some failed with an SQL2216N and a -1218 message code. (I cannot find the explanation for this error code). If I rerun the reorg and do not identify an index, they run successfully.

Can anyone explain this?

I am running the RunStats on the primary data table now. It's been running for over 2hrs now and not completed yet. There are approximately 100+ million records in this table. Record length is listed as 51 bytes. 8 columns. I've run a ReOrg on this table before and it ran for 6.5hrs before coming back and telling me that the table data and the indexes are inconsistent.
Reply With Quote
  #2 (permalink)  
Old 11-16-05, 15:46
n_i n_i is offline
:-)
 
Join Date: Jun 2003
Location: Toronto, Canada
Posts: 4,449
Quote:
Originally Posted by bunzo
failed with an SQL2216N and a -1218 message code. (I cannot find the explanation for this error code).
Code:
$ db2 "? SQL1218N "


SQL1218N There are no pages currently available in bufferpool
          "<buffpool-num>".

Explanation:

All of the pages in the bufferpool are currently being used.  A
request to use another page failed.

 The statement cannot be processed.

User Response:

The bufferpool is not large enough to provide pages to all
database processes or threads at this time.  The bufferpool is
too small or there are too many active processes or threads.

 The statement may be successful if executed again.  If this
error occurs frequently, some or all of the following actions may
prevent further failures:

1.    increase the bufferpool size

2.    decrease the maximum number of database agents and/or
    connections

3.    decrease the maximum degree of parallelism

4.    decrease the prefetch size for table spaces that are in this
    bufferpool

5.    move some table spaces into other bufferpools.

 sqlcode :  -1218

 sqlstate :  57011
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On