This looks related to a known problem in the 4.2 server code with the resource
waiters logic.
Suggestion is to try increasing the resourcetimeout value
Have a look at query option to see what your resourcetimeout value is.
I have mine set to 100






Burak Demircan <burak.demircan AT daimlerchrysler DOT com> on 10/24/2002 
03:32:42 PM

Please respond to "ADSM: Dist Stor Manager" <adsm-l AT vm.marist DOT edu>

To:   adsm-l AT vm.marist DOT edu
cc:    (bcc: John Naylor/HAV/SSE)
Subject:  Re: Help!!!!!!




**********************************************************************
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**********************************************************************

Hi,
This seems that an unexpected thing occured to your server. I would try to
increase my maintenance level 4.2.2.x
Or at least check 4.2.1.0 patch level if something close to it is there.
One of my server is 4.2.2.13 for enough time and there is no problem.
By the way your DB usage percent is high. I would increase it not the be in
urgent situations.

And i also suspect that your DB is full now or in a situation that even a small
new data to it crashes it.
Try to add 10-20 mbs to your DB and log volumes (CHECK your log also)

Regards,
Burak




        gmurthy AT IN.IBM DOT COM
        Sent by: ADSM-L AT VM.MARIST DOT EDU

        24.10.2002 17:18
        Please respond to ADSM-L

                        To:        ADSM-L AT VM.MARIST DOT EDU
                        cc:
                        Subject:        Help!!!!!!

Hi TSM Guru's,

I have a TSM Server 4.2 Level 1.0 running on AIX.  with  512MB RAM & Paging
Space - 1.6GB.

DB allocated - 11.7GB.
Used                - 10.8GB

I run a schedule in the morning for a backup, which has been running
without any problems for the past one month.
Today morning when the schedule started the server stopped with the error
below.

10/24/2002 07:58:17  ANR7838S Server operation terminated.
10/24/2002 07:58:17  ANR7837S Internal error TXNLOCK16 detected.

The server  is starting ok when i start it again.

But when i started a GUI backup the server stopped with the follwoing
error.

ANR9999D pkthread.c(539): ThreadId<19> Run-time assertion failed:
"waitP->txn-
P->waitingForLock == lockP", Thread 19, File tmlock.c, Line 1919.
ANR7838S Server operation terminated.
ANR7837S Internal error TXNLOCK16 detected.
 0x0000000100009414 pkLogicAbort
 0x00000001000336bc SignalCompatibleWaiters
 0x0000000100033a10 UngrantLock
 0x0000000100034bdc TmReleaseTxnLocks
 0x000000010007ad3c tmEnd
 0x00000001002fe654 SmNodeSession
 0x0000000100305668 HandleNodeSession
 0x000000010030a9c0 smExecuteSession
 0x00000001003e8ecc SessionThread
 0x0000000100007e3c StartThread
 0x090000000022dfe4 _pthread_body
ANR7833S Server thread 1 terminated in response to program abort.


Could somebody help me with this error please.

Thanks in advance

murhy

V S Murthy Gongala
Hursley Dedicated Development Centre
IBM Software Labs
Bangalore, INDIA
Tel : 91-80-5094232