Hi all,
I am very new to DB2. Infact I need DB2 while using the MQSI 2.1. I created a new instance of DB2 on AIX5.3,but only recently when I start the Workflow, I noticed that the DAS server is not started. SO I stopped all the DB2 sesrvices using the command db2stop force. But when I try to restart the DAS, it says DAS cannot be started. Can someone please help me regarding this issue?

Following is the error log of one of the DAS:
2006-02-27-15.26.22.269978 pid:282648 tid:1 level:2
DB2 tools - DB2 administration server - dasRootInit() probe:10
data #1 (131 bytes)
DAS startup error. Failed to bind to port 523. Please ensure
that no other applications are using this port. Then restart the DAS.

2006-02-27-15.26.22.270809 pid:282648 tid:1 level:2
DB2 tools - DB2 administration server - dasRootInit() probe:10
data #1 (4 bytes)
-2129723365

2006-02-27-15.26.24.270898 pid:282648 tid:1 level:2
DB2 tools - DB2 administration server - db2dasSearchDscvInit() probe:30
data #1 (4 bytes)
67

2006-02-27-15.26.24.270969 pid:282648 tid:1 level:2
DB2 tools - DB2 administration server - dasRootInit() probe:60
data #1 (4 bytes)
-1

2006-02-27-15.26.24.271018 pid:282648 tid:1 level:2
DB2 tools - DB2 administration server - rrm_main() probe:80
data #1 (4 bytes)
-3020

2006-04-18-15.05.52.745391 pid:495814 tid:1 level:2
DB2 tools - DB2 administration server - readRrmSqlca() probe:20
called OSSHIPCQueue::get()
return code 0x9000000C Invalid parameter

2006-04-18-15.10.52.769480 pid:704724 tid:1 level:2
DB2 tools - DB2 administration server - readRrmSqlca() probe:20
called OSSHIPCQueue::get()
return code 0x90000013 Time out

2006-04-18-15.46.11.830043 pid:700476 tid:1 level:2
DB2 tools - DB2 administration server - readRrmSqlca() probe:20
called OSSHIPCQueue::get()
return code 0x90000013 Time out

2006-04-18-15.56.06.835713 pid:708834 tid:1 level:2
DB2 tools - DB2 administration server - readRrmSqlca() probe:20
called OSSHIPCQueue::get()
return code 0x90000013 Time out

You should drop and recreate the DAS. See the dasdrop and dascrt commands in the Command Reference manual. You do not need to to stop the instance when doing these commands. But you do need root or sudo access. There is only one DAS per server, regardless of the number of DB2 instances.

Hi Marcus,

Thanks for the reply.

But if you look at the inital part of the details, it says something about port 523(Failed to bind port 523).I remember when I again try to bind the fix pack, it's not getting done completely, but just giving no response after a couple of successfull bindings.

Don't you think I should work around issue that before I actually uninstall DAS?

You can try to first resolve the port issue if you want to. There is an AIX command that shows what ports are being used (I don't know the command off hand) or you could look in /etc/services to see if that port is defined.

Dropping the DAS and recreating it can be done very quickly, and that is what I would try first if it were me. The DAS is unrelated the database instances and does not need binding, so I am not sure what other problems you have with the database instances. Maybe you have not installed the fixpack correctly. On AIX, make sure you have followed all the directions, including running ipcclean.

Make sure that you have java installed on that machine and the DAS points to it in the path configuration:

db2 get admin cfg

Hi Marcus

I'm having the same problem and I checked everything

I think it's a bug in Fixpak 10 - IBM suggests that its because
og the file system not being enabled for suid - in order to run
the dasrrm - but I checked that as well and I simply cannot get
it to run.

Sincerely Yours

So do you think there is no solution for this problem without changing the configuration?
Please let me know of any solution.This is a major issue for my survival in the job

What is the ownership/permission on $DASHOME/das/adm/db2dasrrm executable?

Have encountered the same problem just last night.
Using RHEL 2.1 and DB2 8.2.

Got SQL4401C when attempting to restart the db2admin server.

Dropped and recreated db2as to no avail.
With "ps -aux" I noticed that there were multiple entries for db2as, namely:

db2as 7418 0.0 0.4 18712 4316 ? S 00:46 0:00 /home/db2as/das/adm/db2dasrrm
db2as 7451 0.0 0.4 18712 4316 ? S 00:46 0:00 /home/db2as/das/adm/db2dasrrm

This would suggest that somehow the db2 still believes that the admin server is running on port 523 and is unable to clean up.

As this was a production server, I'm not permitted to simply kill these rouge entires so attempted to mimic the same failure on the dev server.
If you rename the /home/db2as/das directory and then drop the admin server you get the SQL4401C failure when recreating the admin server.

ps -aux should confirm this.

I then killed off the rouge processes (on the dev server) using:

kill -9 <pid>
Where pid is the process id (as 7418 from the above example).

I should note that this didn't take down the db2 server instance (made sure by establishing a db2 database connection).

Then under the db2as user I was able to issue the "db2admin start" command successfully to restart the admin server.

Hope this helps

Ozzy

You are THE MAN

Didn't think a minute about checking processes

And sure enough I had 2 <defunct> dasusr1 processes
blocking access to port 523 - killed them and everything worked
like a charm !! - bet it works for the rest of the gang as well

If you ever come to Copenhagen i'm buying all the beer you
can drink

Sincerely Yours

Hi Kristian,

Glad to be of help.
Regards
Andy

I'm sorry for replying so late, but this DB2 work was kept aside for a few days and now it's back
-r-sr-xr-x 1 root dasadm1 538585 May 17 12:08 db2dasrrm
Tried to follow the stuff given in:
http://www-1.ibm.com/support/docview...id=swg21198111

I did a 'dasupdt', but....
# pwd
/usr/opt/db2_08_01/instance
# dasupdt
SQL4410W The DB2 Administration Server is not active.
SQL4401C The DB2 Administration Server encountered an error during startup.
DBI1070I Program dasupdt completed successfully.

Here's my db2dasdiag.log file:
2006-05-17-13.56.28.311963 pid:516190 tid:1 level:2
DB2 tools - DB2 administration server - dasRootInit() probe:10
data #1 (131 bytes)
DAS startup error. Failed to bind to port 523. Please ensure
that no other applications are using this port. Then restart the DAS.

2006-05-17-13.56.28.312065 pid:516190 tid:1 level:2
DB2 tools - DB2 administration server - dasRootInit() probe:10
data #1 (4 bytes)
-2129723365

2006-05-17-13.56.30.312143 pid:516190 tid:1 level:2
DB2 tools - DB2 administration server - db2dasSearchDscvInit() probe:30
data #1 (4 bytes)
67

2006-05-17-13.56.30.312221 pid:516190 tid:1 level:2
DB2 tools - DB2 administration server - dasRootInit() probe:60
data #1 (4 bytes)
-1

2006-05-17-13.56.30.312269 pid:516190 tid:1 level:2
DB2 tools - DB2 administration server - rrm_main() probe:80
data #1 (4 bytes)
-3020

I am just worried to drop and recreate DAS because it might affect the workflow since I have already associated it with this DAS.
KINDLY HELP ME......

Have you tried

'ps -fu dasusr1' to see if you have any defunct processes
trying to connect to port 523 ?

I do not see any defunt process as such. Here is the outputI logged in as dasusr4)

$ id
uid=104(dasusr4) gid=102(dasadm1) groups=1(staff)
$ ps -fu dasusr4
UID PID PPID C STIME TTY TIME CMD
dasusr4 741406 848044 0 08:54:14 pts/2 0:00 ps -fu dasusr4
dasusr4 848044 606348 0 08:54:04 pts/2 0:00 -ksh

I tired to see this with all other UID's but none of them have any other processes.

Well your daslog is clear enough

Something IS blocking access to port 523

Try checking your /etc/services file to see
if the port is allocated to another program ?

Hi,
Here's is what is given in /etc/services file:
ibm-db2 523/tcp # IBM-DB2
ibm-db2 523/udp # IBM-DB2
which inddicates that it's DB2 using port 523.If this is the case, then there should be someother reason why DAS is not starting up.
Please guide me...