Hi, All,
I have some question on the alternate server for the DB connection on
db2 connect server.
There is one db2 connection to one host database on the server with
the following cfg:
Database 13 entry:
Database alias = DBG0
Database name = DBG0
Node name = DBG0
Database release level = a.00
Comment =
Directory entry type = Remote
Authentication = SERVER_ENCRYPT
Catalog database partition number = -1
Alternate server hostname = test.net
Alternate server port number = 3774
If I want to upgrade the db2 connect server to stop the instance, the
client application configured with the new connetion to DBG0 by this
db2 connect server will go through the alternate server test.net?
Because the db2 connect stop, client can still get the alternate
server information?
Another question on FixPak.
Has db2 different code for db2 WSE, ESE and db2 connect for one FixPat
of one platform?
Or different db2 product has diferent FixPat code?
Thanks,
I have some question on the alternate server for the DB connection on
db2 connect server.
There is one db2 connection to one host database on the server with
the following cfg:
Database 13 entry:
Database alias = DBG0
Database name = DBG0
Node name = DBG0
Database release level = a.00
Comment =
Directory entry type = Remote
Authentication = SERVER_ENCRYPT
Catalog database partition number = -1
Alternate server hostname = test.net
Alternate server port number = 3774
If I want to upgrade the db2 connect server to stop the instance, the
client application configured with the new connetion to DBG0 by this
db2 connect server will go through the alternate server test.net?
Because the db2 connect stop, client can still get the alternate
server information?
Another question on FixPak.
Has db2 different code for db2 WSE, ESE and db2 connect for one FixPat
of one platform?
Or different db2 product has diferent FixPat code?
Thanks,