Marco,
We just had this happen on Monday on Unidata 6.0.8 on AIX 5.1, we were
told to run "udtdiag" to colloect data about the state of Unidata and stop
and restart Unidata. There is no other way. Here is what Unidata support
told us:
"This is very difficult to chase down. Usually associated with killing a
process. Some structures are left in the lock table (usually at a lower
level than record or group locks - structures that control access to parts
of this table. I do not know of any way to clear this situation without
restarting the database. With the dump, we have a chance to review the
structures. Without a way to force this situation, it is very difficult to
figure out the cause of the problem and fix it. The good news/bad news is
that it is very rare. Good that it doesn't happen much. Bad in that we
have very little data to review to try to fix it."
After running udtdiag:
"It creates a directory you name as an argument and dumps
stuff there. One of the things it dumps is an image of the lock table
along with the tool to analyze it (they have to match - saves us from
reinstalling a specific version of UniData here to analyze the dump). You
would then need to tar that up, compress it and ftp to:
testcase.boulder.ibm.com:/software/toibm/informix
And let us know the name of the file you posted."
Good luck.
"Marco Antonio Rojas Castro" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
03/16/2004 09:50 AM
Please respond to U2 Users Discussion List
To: [EMAIL PROTECTED]
cc:
Subject: CLEANUP problem
I have a problem with CLEANUP daemon
We are using UNIDATA 5.2.9 (100 users license) on Windows 2000
our aplication is made with SB+ 5.4, and SBCLIENT 5.3
When the server is restarted, aprox. 25 users can log on
then, when other users try to log on, this message appear in then screen :
The CLEANUP is cleaning up the dead processes, please wait for a while.
a few minutes later, the sessions logged din't respond
in cleanupd.errlog file, we found theese messages
U_isdeadproc()(D:\branch_52\udtsrc\src\ulc\ulcd_proclist.c,455): to call
U_daemon_latch_cleanup(0) at Mon Mar 15 17:34:42 2004
U_isdeadproc()(D:\branch_52\udtsrc\src\ulc\ulcd_proclist.c, 461): after
calling U_daemon_latch_cleanup(0) at Mon Mar 15 17:34:42 2004
U_daemon_all_latch_cleanup()(D:\branch_52\udtsrc\src\ulc\ulcd_proclist.c,709):
to call U_daemon_latch_cleanup(0), sys_pv=3 at Mon Mar 15 17:34:52 2004
U_daemon_all_latch_cleanup()(D:\branch_52\udtsrc\src\ulc\ulcd_proclist.c,
716): after calling U_daemon_latch_cleanup(0) at Mon Mar 15 17:34:52 2004
U_daemon_all_logical_cleanup(): to call U_logproc_cleanup() on 0 at Sun
Jul
21 20:31:01 2013
U_daemon_all_logical_cleanup(): after calling U_logproc_cleanup() on 0 at
Sun Jul 21 20:31:01 2013
U_isdeadproc()(D:\branch_52\udtsrc\src\ulc\ulcd_proclist.c,455): to call
U_daemon_latch_cleanup(1) at Mon Mar 15 17:35:02 2004
U_isdeadproc()(D:\branch_52\udtsrc\src\ulc\ulcd_proclist.c, 461): after
calling U_daemon_latch_cleanup(1) at Mon Mar 15 17:35:02 2004
U_daemon_all_latch_cleanup()(D:\branch_52\udtsrc\src\ulc\ulcd_proclist.c,709):
to call U_daemon_latch_cleanup(1), sys_pv=3 at Mon Mar 15 17:35:12 2004
U_daemon_all_latch_cleanup()(D:\branch_52\udtsrc\src\ulc\ulcd_proclist.c,
716): after calling U_daemon_latch_cleanup(1) at Mon Mar 15 17:35:13 2004
U_daemon_all_latch_cleanup()(D:\branch_52\udtsrc\src\ulc\ulcd_proclist.c,709):
to call U_daemon_latch_cleanup(2), sys_pv=3 at Mon Mar 15 17:35:14 2004
U_daemon_all_latch_cleanup()(D:\branch_52\udtsrc\src\ulc\ulcd_proclist.c,
716): after calling U_daemon_latch_cleanup(2) at Mon Mar 15 17:35:14 2004
U_daemon_all_latch_cleanup()(D:\branch_52\udtsrc\src\ulc\ulcd_proclist.c,709):
to call U_daemon_latch_cleanup(2), sys_pv=3 at Mon Mar 15 17:35:14 2004
U_daemon_all_latch_cleanup()(D:\branch_52\udtsrc\src\ulc\ulcd_proclist.c,
716): after calling U_daemon_latch_cleanup(2) at Mon Mar 15 17:35:14 2004
U_daemon_all_logical_cleanup(): to call U_logproc_cleanup() on 1 at Sun
Jul
21 20:31:01 2013
U_daemon_all_logical_cleanup(): after calling U_logproc_cleanup() on 1 at
Sun Jul 21 20:31:01 2013
U_daemon_all_logical_cleanup(): to call U_logproc_cleanup() on 2 at Sun
Jul
21 20:31:01 2013
U_daemon_all_logical_cleanup(): after calling U_logproc_cleanup() on 2 at
Sun Jul 21 20:31:01 2013
U_daemon_all_logical_cleanup(): to call U_logproc_cleanup() on 2 at Sun
Jul
21 20:31:01 2013
U_daemon_all_logical_cleanup(): after calling U_logproc_cleanup() on 2 at
Sun Jul 21 20:31:01 2013
U_daemon_all_logical_cleanup(): to call U_logproc_cleanup() on 2 at Sun
Jul
21 20:31:01 2013
U_daemon_all_logical_cleanup(): after calling U_logproc_cleanup() on 2 at
Sun Jul 21 20:31:01 2013
cleanup: accounting for killed user process.
udtno = 1, pid = 2064, uid = 263392, usertype = 1, tty = 145.136.70.11,
timedate = 17:34:38 Mar 15 2004, current time = Mon Mar 15 17:35:27 2004
please, what can I do to solve this ???
Thanks
Marco Rojas C.
Unique S.A.
Lima - Perú
_________________________________________________________________
MSN Amor: busca tu ˝ naranja http://latam.msn.com/amor/
--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users
--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users
