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

SQL10004C error

P: n/a
I have a number of DB2 v8.1 FP4a instances that have been running fine on an
AIX server for quite some time. I installed alternate FP7 last week and
created a new instance at that level today. I'm not sure exactly when it
started, and this may or may not be related to FP7, but for some reason when
I do a "db2 list db directory" on the server as the instance id, I am
getting the following error for all the FP4a instances. It works fine in the
FP7 instance.

SQL10004C An I/O error occurred while accessing the database directory.
SQLSTATE=58031

Can anyone give me a clue about what's going on?
--
Carl Draus
IBM SWG-RTP Application & Server Support, RTP, NC
http://w3.helpme.raleigh.ibm.com
cd****@us.ibm.com, (919) 254-5382, T/L 444-5382
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
I found the answer and it IS related to alternate FP7. This is what bit me:

IY62715: WHEN BOTH V8.2 AND V8.1 RESIDE ON THE SAME SERVER, THE DB DIR
OFV8.1 INSTANCES MAY BE MIGRATED TO V8.2 UNEXPECTEDLY.

APAR status
OPEN

Error description

Using the alternate fixpak, a server may have both V8.1 and V8.2
instances at the same time. In such environment, if discovery
functionality of db2 is invoked, then all the instances in the
server are examined. This causes the migration of the database
directory format (sqldbdir) for the V8.1 databases. Once,
migrated, connect to these databases will fail with SQL10004C.

Local fix

To avoid this problem, disable the discovery for the V8.1
instances. That is,
db2 update dbm cfg using DISCOVER DISABLE
db2 update dbm cfg using DISCOVER_INST DISABLE
..
If the problem has already occurred, de-migrate the database
directory of the V8.1 instances back to V8.1 format from V8.2.
db2demigdbd <instance home>/sqllib 2
..
Note that for both workarounds above, you need not touch V8.2
instances.

"Carl Draus" <cdraus at us ibm com> wrote in message
news:41********@news3.prserv.net...
I have a number of DB2 v8.1 FP4a instances that have been running fine on an AIX server for quite some time. I installed alternate FP7 last week and
created a new instance at that level today. I'm not sure exactly when it
started, and this may or may not be related to FP7, but for some reason when I do a "db2 list db directory" on the server as the instance id, I am
getting the following error for all the FP4a instances. It works fine in the FP7 instance.

SQL10004C An I/O error occurred while accessing the database directory.
SQLSTATE=58031

Can anyone give me a clue about what's going on?
--
Carl Draus
IBM SWG-RTP Application & Server Support, RTP, NC
http://w3.helpme.raleigh.ibm.com
cd****@us.ibm.com, (919) 254-5382, T/L 444-5382

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.