Admin Client for DB2 7.1 Fixpack 2 64bit 
Author Message
 Admin Client for DB2 7.1 Fixpack 2 64bit
Hi,

we installed Fixpack 2 for DB2 7.1 on Solaris and
migrated the instance to 64bit. Existing clients do
not connect to this instance. They report SQL1434

We installed Fixpack 2 forAdministration Client 7.1.
Adding the instance results in DBA0102 with reason -1.
None of the possible reasons for DBA0102 holds in
our environment.

What else do we have to do in order to be able to connect
to the 64bit instance from all clients.

Thanks

Holger



Sat, 23 Aug 2003 02:09:45 GMT
 Admin Client for DB2 7.1 Fixpack 2 64bit

You can't connect to a 64-bit instance from all clients.  64-bit DB2
supports only:
1. 64-bit clients (available on AIX, Solaris and HP-UX)
2. DB2 Connect clients

32-bit clients and the Control Center will not be supported until v8.
See chapter 8 in this manual:

http://www-4.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/d...

Quote:

> Hi,

> we installed Fixpack 2 for DB2 7.1 on Solaris and
> migrated the instance to 64bit. Existing clients do
> not connect to this instance. They report SQL1434

> We installed Fixpack 2 forAdministration Client 7.1.
> Adding the instance results in DBA0102 with reason -1.
> None of the possible reasons for DBA0102 holds in
> our environment.

> What else do we have to do in order to be able to connect
> to the 64bit instance from all clients.

> Thanks

> Holger



Sat, 23 Aug 2003 02:45:34 GMT
 Admin Client for DB2 7.1 Fixpack 2 64bit

Quote:
> You can't connect to a 64-bit instance from all clients.  64-bit DB2
> supports only:
> 1. 64-bit clients (available on AIX, Solaris and HP-UX)
> 2. DB2 Connect clients

Does that mean that we have to install DB2 Connect EE on a separate
workstation (NT?) which is then able to connect to our 64-bit instance
on Solaris?

Is it possible to create a new 32-bit instance on the machine
where the 64-bit instance exists? I didn't find anything in the
manual given below that says that it is not possible. It only
describes how one can return to the 32-bit version of a
previously migrated instance by means of a backup.

Thanks in advance

Holger

 32-bit clients and the Control Center will not be supported until v8.
 See chapter 8 in this manual:

http://www-4.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/d...
.d2w/report?fn=db2v7q9frm3toc.htm

 > Hi,
 >
 > we installed Fixpack 2 for DB2 7.1 on Solaris and
 > migrated the instance to 64bit. Existing clients do
 > not connect to this instance. They report SQL1434
 >
 > We installed Fixpack 2 forAdministration Client 7.1.
 > Adding the instance results in DBA0102 with reason -1.
 > None of the possible reasons for DBA0102 holds in
 > our environment.
 >
 > What else do we have to do in order to be able to connect
 > to the 64bit instance from all clients.



Sat, 23 Aug 2003 23:30:58 GMT
 Admin Client for DB2 7.1 Fixpack 2 64bit
Yes, you would install DB2 Connect on the client (such as NT).  We have have
64-bit clients on AIX, Solaris and HP today (DB2 Connect would not be needed on
those operating systems).

You can also create a 32-bit instance on the Solaris box.  Each database can
only belong to one of the instances.

Quote:

> > You can't connect to a 64-bit instance from all clients.  64-bit DB2
> > supports only:
> > 1. 64-bit clients (available on AIX, Solaris and HP-UX)
> > 2. DB2 Connect clients

> Does that mean that we have to install DB2 Connect EE on a separate
> workstation (NT?) which is then able to connect to our 64-bit instance
> on Solaris?

> Is it possible to create a new 32-bit instance on the machine
> where the 64-bit instance exists? I didn't find anything in the
> manual given below that says that it is not possible. It only
> describes how one can return to the 32-bit version of a
> previously migrated instance by means of a backup.

> Thanks in advance

> Holger

>  32-bit clients and the Control Center will not be supported until v8.
>  See chapter 8 in this manual:

> http://www-4.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/d...
> .d2w/report?fn=db2v7q9frm3toc.htm


>  > Hi,

>  > we installed Fixpack 2 for DB2 7.1 on Solaris and
>  > migrated the instance to 64bit. Existing clients do
>  > not connect to this instance. They report SQL1434

>  > We installed Fixpack 2 forAdministration Client 7.1.
>  > Adding the instance results in DBA0102 with reason -1.
>  > None of the possible reasons for DBA0102 holds in
>  > our environment.

>  > What else do we have to do in order to be able to connect
>  > to the 64bit instance from all clients.



Sun, 24 Aug 2003 00:33:19 GMT
 Admin Client for DB2 7.1 Fixpack 2 64bit
I believe you could also use DB2 Connect Personal Edition (it also contains client
code) as long as you don't have any inbound connections coming into the NT machine.
Quote:

> Yes, you would install DB2 Connect on the client (such as NT).  We have have
> 64-bit clients on AIX, Solaris and HP today (DB2 Connect would not be needed on
> those operating systems).

> You can also create a 32-bit instance on the Solaris box.  Each database can
> only belong to one of the instances.


> > > You can't connect to a 64-bit instance from all clients.  64-bit DB2
> > > supports only:
> > > 1. 64-bit clients (available on AIX, Solaris and HP-UX)
> > > 2. DB2 Connect clients

> > Does that mean that we have to install DB2 Connect EE on a separate
> > workstation (NT?) which is then able to connect to our 64-bit instance
> > on Solaris?

> > Is it possible to create a new 32-bit instance on the machine
> > where the 64-bit instance exists? I didn't find anything in the
> > manual given below that says that it is not possible. It only
> > describes how one can return to the 32-bit version of a
> > previously migrated instance by means of a backup.

> > Thanks in advance

> > Holger

> >  32-bit clients and the Control Center will not be supported until v8.
> >  See chapter 8 in this manual:

> > http://www-4.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/d...
> > .d2w/report?fn=db2v7q9frm3toc.htm


> >  > Hi,

> >  > we installed Fixpack 2 for DB2 7.1 on Solaris and
> >  > migrated the instance to 64bit. Existing clients do
> >  > not connect to this instance. They report SQL1434

> >  > We installed Fixpack 2 forAdministration Client 7.1.
> >  > Adding the instance results in DBA0102 with reason -1.
> >  > None of the possible reasons for DBA0102 holds in
> >  > our environment.

> >  > What else do we have to do in order to be able to connect
> >  > to the 64bit instance from all clients.



Sun, 24 Aug 2003 01:50:08 GMT
 Admin Client for DB2 7.1 Fixpack 2 64bit
Creating a new 32-bit instance on the Solaris box delivers the
error message given below. Creating an additional 64-bit
instance works without any problem. Any ideas why the
update of the dbm cfg file fails?

Thanks

-----------------------------------------
db2icrt -w 32 -u db2fenc2 db2inst2

content oflog file:

       Program name = db2idbm
Instance home dir = /local/db2/db2inst2,   Sysadm group = db2iadm1
Instance type = 3,  Auth type = SERVER

DB21016E  The Command Line Processor encountered a system error while
sending
the command to the backend process.
Update DBM cfg SYSADM_GROUP errcode = 8
DBI1281E The database manager configuration file could not be
          initialized.

Explanation:  An error occurred when attempting to initialize the
database manager configuration file. A DB2 Version 7 instance
could not be created or migrated.

User Response:  Refer to the log file for problem determination.
Resolve the problem and try the command again. If the problem
persists, please contact IBM Support.

DBI1079I Output is saved in the log file /tmp/db2icrt.log.19281.

Explanation:  All processed and failed operations have been saved
into this log file.

User Response:  Do not modify this file in any way. This file is
for IBM Technical Support reference.
-----------------------------------------



Quote:
> Yes, you would install DB2 Connect on the client (such as NT).  We have
have
> 64-bit clients on AIX, Solaris and HP today (DB2 Connect would not be
needed on
> those operating systems).

> You can also create a 32-bit instance on the Solaris box.  Each database
can
> only belong to one of the instances.



Sun, 24 Aug 2003 17:03:59 GMT
 Admin Client for DB2 7.1 Fixpack 2 64bit

Quote:

>Creating a new 32-bit instance on the Solaris box delivers the
>error message given below. Creating an additional 64-bit
>instance works without any problem. Any ideas why the
>update of the dbm cfg file fails?

I would guess you have /usr/lib/libdb2.so pointing at
/opt/IBMdb2/V7.1/lib64/libdb2.so.  The links are not supported in a dual-bit
environment.  If you need to run 32 and 64 simultaneously, you must remove
those links.  Use /opt/IBMdb2/V7.1/cfg/db2rmln to remove them.


Sun, 24 Aug 2003 21:21:51 GMT
 Admin Client for DB2 7.1 Fixpack 2 64bit

Quote:
>Creating a new 32-bit instance on the Solaris box delivers the
>error message given below. Creating an additional 64-bit
>instance works without any problem. Any ideas why the
>update of the dbm cfg file fails?
> I would guess you have /usr/lib/libdb2.so pointing at
> /opt/IBMdb2/V7.1/lib64/libdb2.so.  The links are not supported in a
dual-bit
> environment.  If you need to run 32 and 64 simultaneously, you must remove
> those links.  Use /opt/IBMdb2/V7.1/cfg/db2rmln to remove them.

The links do currently not exit on our Solaris box. Thanks for
any further suggestions.

Holger



Sun, 24 Aug 2003 23:46:26 GMT
 
 [ 8 post ] 

 Relevant Pages 

1. Is DB2 UDB 7.1 for W2k fixpack available?

2. DB2 7.1 PDE or DB2 7.1 EE

3. DB2 7.1 admin server connect refused

4. Errors: 7.1 FixPack 2 under WinNT

5. How do you installing DB2 UDB fixpacks on Windows-98 clients from the Server

6. Client programming for IBM DB2 OLAP Server 7.1

7. DB2 PDE 7.1 on RedHat 7.1 problem

8. DB2 UDB 7.1 fp3 AIX 4.3.3 db2 command processor and crontab

9. DB2 CAE V5.2 (fixpack 15) and DB2 Connect EE V7.1

10. Connect to db2 5.2 Server from db2 7.1

11. Multiple versions of UDB Administration client (6.1 and 7.1 client)

12. Books for Admin Online 7.1?


 
Powered by phpBB® Forum Software