IT Support Small Medium Business

As root, I used ’strace64′ to trace system calls of ‘db2icrt’ on a new DB2 UDB v8.2 server running RHEL5 (PPC64) on IBM eServer OpenPower 720 hardware. W/o tracking by strace64, the same command failed right away when a database administrator ran ’sudo db2icrt blahInstanceOptionsHere’.

The same db2icrt command hang, when traced by strace64, as below:

open(”/opt/IBM/db2/V8.1/dasfcn64/”, O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 3
fstat64(3, {st_mode=S_IFDIR|0755, st_size=4096, …}) = 3
fcntl64(3, F_SETFD, FD_CLOEXEC) = 3
getdents64(3,
Any idea why db2icrt would hang when traced by strace64?

• the command syntax is correct. It ran ok when a missing lib was installed.
• why it would hang at getdents64 of a directory of which everybody has access to list contents:

drwxr-xr-x 2 bin bin 4096 Jul 27 09:19 /opt/IBM/db2/V8.1/dasfcn64/

lrwxrwxrwx 1 root root 30 Jul 27 09:19 db2schedapis -> ../das/function64/db2schedapis
lrwxrwxrwx 1 root root 27 Jul 27 09:19 db2mdfile -> ../das/function64/db2mdfile
lrwxrwxrwx 1 root root 27 Jul 27 09:19 db2licsrv -> ../das/function64/db2licsrv
lrwxrwxrwx 1 root root 33 Jul 27 09:19 db2KnownDscvSrv -> ../das/function64/db2KnownDscvSrv

lrwxrwxrwx 1 root root 26 Jul 27 09:19 db2isdas -> ../das/function64/db2isdas
lrwxrwxrwx 1 root root 26 Jul 27 09:19 db2dasfn -> ../das/function64/db2dasfn
lrwxrwxrwx 1 root root 28 Jul 27 09:19 db2dasdbfn -> ../das/function64/db2dasdbfn
lrwxrwxrwx 1 root root 25 Jul 27 09:19 db2ccfn -> ../das/function64/db2ccfn

$ uname -a

Linux db2box 2.6.18-8.el5 #1 SMP Fri Jan 26 14:19:36 EST 2007 ppc64 ppc64 ppc64 GNU/Linux
$ rpm -aq | grep -i strace
strace64-4.5.15-1.el5
$ rpm -qf /opt/IBM/db2/V8.1/instance/db2icrt
IBM_db2cliv81-8.1.0-128

Add to: