Re: SQL1072C Red Hat Linux 8, DB2 7.2

Re: SQL1072C Red Hat Linux 8, DB2 7.2

 

  





How are you changing the db2profile for each connection? I think you may
be still holding on to shared libraries for each one. Have you logged out
and logged back in with the different instance?

Dan Callahan IT Specialist
603-472-4121 t/l 525-4121
[Email address protected]
[Email address protected]




"Nils Ottar Molde
"
<db2udbdba-ezmlms To
hield-x98397226.x "LazyDBA Discussion"
[Email Address Removed] <[Email address protected]
a.com> cc

05/23/2004 07:56 Subject
PM SQL1072C Red Hat Linux 8, DB2 7.2










Hi all.

Here's the problem.

Created one instance db2inst1, started the database manager, and
created a database (XDTGOM). Everything works perfect. Stopped the
database manager for this instance.

Created new instance db2ix01, started the database manager and created
another database (XGPS), and again. everything works perfect.

I can start the database manager in both the instances without
problems, but I can not connect to the two databases at the same time.
When I try to connect to the second database (wich of the databases I
connect to first or second does not matter), I get the following
message :

***************

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

***************

The usual problem seems to be i-node conflict of the sqllib catalog
for the two instances. I do not think this is the problem here, as I
can start the two instances at the same time with no problem. Also ls
-id shows different inode number for the two sqllib catalogs. (I do
not have multiple filesystems)

It seems to be the two databases that fight for the same resources.
All suggestions to solutions I have read so far seems to address the
problem of not managing to start the database manager in two instances
at the same time. This is not an issue here. It is connecting to the
databases that triggers the conflict.

Any ideas would be hugely appreciated.

Cheers
Nils


Best Regards/Med vennlig hilsen

<http://www.susoft.com/>

Nils Ottar Molde
Executive Software Engineer

Dir.line: +47 5530 9520
Mobile: +47 9823 9520
<mailto:[Email address protected] [Email address protected]
www.susoft.com <http://www.susoft.com/>

HEAD OFFICE: Nøstegt 74, N-5011 Bergen, NORWAY | Phone: +47 5530 9500 |
Fax: +47 5530 9501
OSLO: Langkaia 1, N-0150 Oslo, NORWAY | Phone: +47 2310 0400 | Fax: +47
2310 0401
DENMARK: PowerOfThePen, Langebrogade 6-J, DK-1411 Copenhagen K, DENMARK |
Phone: +45 3332 3180 | Fax: +45 3266 1110

<http://www.susoft.com/produkt_hovedside.html>
Making Your Business More Profitable



---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe, e-mail: db2udbdba-[Email address protected]
For additional commands, e-mail: db2udbdba-[Email address protected]



DB2 & UDB email list listserv db2-l LazyDBA home page