SQL1072C

[Tomas Hallin]

Hello,

I have some problems with a DB2 instance that refuses to start. When
I try starting it, I get the following:

SQL1072C The database manager resources are in an inconsistent state.
DB2 may have been incorrectly terminated, or another application may
be using system resources in a way which conflicts with DB2's use of
system resources. System resource cleanup may be required.

I've cleaned up all processes, used db2nkill, nothing is running.
/etc/services looks fine, db2diag.log doesn't provide any hints. I
have two databases in the instance that I would like to save.

Here's my idea: I blow the instance away, while leaving the
filesystem containing the database and local database directory.
After recreating the instance, can I just catalog the databases, pointing to the
directory holding them and the local database directory? Is this a
workable approach? Any other ideas?

Thanks,

/T

Tomas Hallin
Database Administration
Robert Half International
Pleasanton, CA

[Sylv1]

If you're running under a recent AIX maintenance problem,
there is a well know problem when trying to run more than one
db2 instance.
In order to check whether you hit this problem , at db2 instance prompt :
. run ipclean -a
. make sure that no ressource is in the system for this instance(ipcs)
. go in ~insthome/sqllib
. mv .ftok .ftoc.old
. touch .ftok

Hope this help...Sylv1

[Sivakumar Shanmugam]

Hi... Looks like there may be an inode conflict while running with
multiple instance..This a known DB2 problem.. To check to see inode is
same for all the instances issue following command against sqllib
directory available in each instance home directory...
ls -lid sqllib

If the inode is number is same for the all the instances then you
are having inode conflict.....
'
Here is the solution...

For single-node instances, perform the following as the
instance owner from the sqllib directory:

- delete the .ftok file

rm .ftok

- create a new .ftok file

touch .ftok

For multi-node instances, perform the following as the
instance owner:

- create another directory at the same level as sqllib

- move everything from under sqllib to the new directory

- delete sqllib

- rename the new directory to sqllib

-- Siva

"Sylv1" <sy...@invalid.netcourrier.com> wrote in message news:<3c96481c$0$23192$626a...@news.free.fr>...

[Peter J. DiFondi]

I've tried your solution before ant it seemed to work.. I can't imagine,
however, it being supported by DB2.

I ended up exporting the data. dropping the tables and recreating... just to
be safe..

"Tomas Hallin" <jav...@hotmail.com> wrote in message
news:2cceadd.02031...@posting.google.com...

[A Log]

Yes, its a famous bug on AIX and its one of the solutions suggested by
IBM(I think) ;)