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

Failover problems

P: n/a
2 servers with solaris,veritas cluster and DB2 UDB ESE v8.1 with
fixp10. ON the primary db2 server did I create 2 db2 instances and the
admin instance. It is possible to start both db2 instances and the db2
admin server on the primary server but ...failover works only for the 2
db2 instances and not for the admin server.. Manually ,db2admin start ,
fails with
SQL4404N The DB2 Administration Server does not exist.
Explanation:
The DB2 Administration Server was not found on the machine

Is it something special you have to do with DB2 UDB ESE to get failover
working ? I have done this many times but only with DB2 UDB WSE...
my hair is turning grey because of this so if anyone has some ideas pls
let me know.

Jan 23 '06 #1
Share this Question
Share on Google+
6 Replies


P: n/a
Ian
ka******@hotmail.com wrote:
2 servers with solaris,veritas cluster and DB2 UDB ESE v8.1 with
fixp10. ON the primary db2 server did I create 2 db2 instances and the
admin instance. It is possible to start both db2 instances and the db2
admin server on the primary server but ...failover works only for the 2
db2 instances and not for the admin server.. Manually ,db2admin start ,
fails with
SQL4404N The DB2 Administration Server does not exist.
Explanation:
The DB2 Administration Server was not found on the machine

Is it something special you have to do with DB2 UDB ESE to get failover
working ? I have done this many times but only with DB2 UDB WSE...
my hair is turning grey because of this so if anyone has some ideas pls
let me know.


The DAS instance should not need to be an HA resource. You can just set
up an identical DAS instance on your standby server (which is always
running), and you should be fine.


Jan 23 '06 #2

P: n/a
Ian... maybe I was a bit unclear but my configuration is not with a
standby server ! so it's impossible to have more than one DAS instance
because the home dir is switched between the servers ....

Jan 24 '06 #3

P: n/a
Ian... maybe I was a bit unclear but my configuration is not with a
standby server ! so it's impossible to have more than one DAS instance
because the home dir is switched between the servers ....

Jan 24 '06 #4

P: n/a
ka******@hotmail.com wrote:
Ian... maybe I was a bit unclear but my configuration is not with a
standby server ! so it's impossible to have more than one DAS instance
because the home dir is switched between the servers ....


This is obviously a shared disk setup, and not HADR.

Why not create the DAS on a userid which has a home directory on the
local drives, not the shared disk. Then just create a DAS on each
server.

Jan 24 '06 #5

P: n/a
Ian
ka******@hotmail.com wrote:
Ian... maybe I was a bit unclear but my configuration is not with a
standby server ! so it's impossible to have more than one DAS instance
because the home dir is switched between the servers ....


The DAS (and the resources it depends on, i.e. the DAS instance owner's
home directory) should NOT be set up to failover between the two
servers. The DAS owner's home directory should be local (and unique) to
each server.
Jan 25 '06 #6

P: n/a
we have a similar setup in windows 2k3 environment, where the DAS is
local at each participating node, and the user instances are shared.

regards,
dotyet

Jan 25 '06 #7

This discussion thread is closed

Replies have been disabled for this discussion.