ADSM-L

Re: Intermittant TSM Server - Database stops

2003-12-15 23:37:17
Subject: Re: Intermittant TSM Server - Database stops
From: "Pole, Stephen" <Stephen.Pole AT HEALTH.WA.GOV DOT AU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 16 Dec 2003 12:36:38 +0800
Hi all,

Sorry to trouble all of you.

Here is an event that happened last week during normal operations, while a
large query was being run on the TSM database.

12/11/03 01:08:13     ANR2561I Schedule prompter contacting ICMC02RPA
(session
                       4174) to start a scheduled operation.

12/11/03 01:08:32     ANR2017I Administrator OPS issued command: FETCH NEXT
50
12/11/03 01:08:37     ANR2958E SQL temporary table storage has been
exhausted.

The explanation seems pretty self explanantory.

The server was restarted all seemed ok for about 12 hours.

We have added another extended the database by means of another dataase
volume and refrained from performing any major SQL queries etc..

Since then, TSM Server stops at random times. (no messages in the actlog)
The server just falls and has to be restarted.

The only clue something has happened is in the errpt -a

LABEL:          CORE_DUMP
IDENTIFIER:     1F0B7B49

Date/Time:       Mon Dec 15 23:33:11 WAUS
Sequence Number: 40038
Machine Id:      0000D62A4C00
Node Id:         rsfm014
Class:           S
Type:            PERM
Resource Name:   SYSPROC

Description
SOFTWARE PROGRAM ABNORMALLY TERMINATED

Probable Causes
SOFTWARE PROGRAM

User Causes
USER GENERATED SIGNAL

        Recommended Actions
        CORRECT THEN RETRY

Failure Causes
SOFTWARE PROGRAM

        Recommended Actions
        RERUN THE APPLICATION PROGRAM
        IF PROBLEM PERSISTS THEN DO THE FOLLOWING
        CONTACT APPROPRIATE SERVICE REPRESENTATIVE

Detail Data
SIGNAL NUMBER
           6
USER'S PROCESS ID:
       44974
FILE SYSTEM SERIAL NUMBER
           2
INODE NUMBER
      215060
PROCESSOR ID
           0
PROGRAM NAME
dsmserv
ADDITIONAL INFORMATION
pthread_k A8
??
_p_raise 64
raise 34
abort B8
AbortServ 80
TrapHandl 13C
??
??

Symptom Data
REPORTABLE
1
INTERNAL ERROR
0
SYMPTOM CODE
PCSS/SPI2 FLDS/dsmserv SIG/6 FLDS/AbortServ VALU/80

End result is that TSM has gone very "flakey" and falls over a odd times.

Has anyone encounter this before. If so what are my options?

We are looking at doing an unloaddb then reload.... etc... (If I can get my
head around the procedure)..

Any help would be greatly appreciated

Thanks in advance TSM'ers!

Cheers



Stephen Pole
WA Dept of Health

stephen.pole AT health.wa.gov DOT au

<Prev in Thread] Current Thread [Next in Thread>