By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,924 Members | 1,651 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.

DB2 Instance Crashing

P: n/a
We are in the process of migrating from Version 7, running on an OS/2
server, to Version 8.2, running on a Windows 2003 server. I have
created two databases on the new server, and have moved the data into
the databases. One of the databases has a single user entering
transactions and the DB2 instance has crashed multiple times. The
Windows Event Viewer has the following warnings prior to DB2 crashing.
The first message occurs 4 times, the one showing and for the
"TEMPSPACE1" (ID "1"), "USERSPACE1" (ID "2"), "SYSTOOLSPACE" (ID "3")
table spackes. Then the last warning occurs.

------------------------------
2006-04-25-08.25.19.665000 Instance:DB2 Node:000
PID:2000(db2syscs.exe) TID:976 Appid:0A0365AF.B308.060425121145
buffer pool services sqlbStartPools Probe:2 Database:XYZ

ADM6073W The table space "SYSCATSPACE" (ID "0") is configured to use
buffer
pool ID "1", but this buffer pool is not active at this time. In the
interim
the table space will use buffer pool ID "4096". The inactive buffer
pool
should become available at next database startup provided that the
required
memory is available.
----------------------------------------
2006-04-25-08.25.19.915001 Instance:DB2 Node:000
PID:2000(db2syscs.exe) TID:976 Appid:0A0365AF.B308.060425121145
sort/list services sqlsOptimizeNumMergeRuns Probe:10 Database:XYZ

ADM9000W Prefetching was disabled during sort merge; performance may
be
suboptimal. If this message persists, consider increasing the buffer
pool size
for temporary table space "TEMPSPACE1" (ID "1") or increase the value
of the
SORTHEAP DB configuration parameter to reduce the extent of sort
spilling.
---------------------------

On the OS/2 server, the SORTHEAP parameter was set to 256, and there
was never a problem. On the Windows 2003 server, I have moved it to
1352 pages, but still get the errors. At this point there are only a
few users that connect to the new server, but I need to resolve this
before I continue the upgrade\migration. Does anyone have any
suggestions?

Thanks in advance,
Bob

Apr 25 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
>From you message, not enough memory for DB2

Apr 25 '06 #2

P: n/a
The server has 3 GB of RAM. I think it is a configuration setting. I
have been adjusting them, but the problem is still occurring. Last
night I used the Configuration Advisor on the database that has been
having the errors. Hopefully this will eliminate the errors. I have
also thought about creating a separate instance for each database. Are
the any pros or cons to this?

Apr 26 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.