ADSM-L

Re: [ADSM-L] internal server error detected

2017-01-31 10:05:39
Subject: Re: [ADSM-L] internal server error detected
From: Chavdar Cholev <chavdar.cholev AT GMAIL DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 31 Jan 2017 17:04:42 +0200
Hello again,
may be  changes in SAN infra...
Have you checked if tape drives are "visible" for the OS where STA is
installed
and validate lan-free <STA_name> from TSM server ?


On Tue, Jan 31, 2017 at 4:59 PM, Chavdar Cholev <chavdar.cholev AT gmail DOT 
com>
wrote:

> Hi Eric,
> I had similar situation..
> We had enough scratch taped in library, but for stg pool (ORA_PROD for
> example) we set Maximum Scratch Volumes Allowed =100 and when checked
> q stg ORA_PROD f=d we found that Number of Scratch Volumes Used = 100 also
> and in this case we got similar message s you
>
> HTH
> Chavdar
>
> On Tue, Jan 31, 2017 at 4:47 PM, Loon, Eric van (ITOPT3) - KLM <
> Eric-van.Loon AT klm DOT com> wrote:
>
>> Hi Sasa (and all others who responded)!
>> The issue seems to be on the Storage Agent side, all other clients and
>> the server itself operate normally. So no errors are seen in the DB2 log.
>> The STA was stopped and started, but to no avail. Everything was working
>> fine on this client until this morning...
>> On the server all drives and paths are online. The paths defined for the
>> STA are also online. We have 1300 scratch tapes available in the library...
>> I'm lost.
>> Kind regards,
>> Eric van Loon
>> Air France/KLM Storage Engineering
>>
>> -----Original Message-----
>> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
>> Of
>> Sasa Drnjevic
>> Sent: dinsdag 31 januari 2017 14:03
>> To: ADSM-L AT VM.MARIST DOT EDU
>> Subject: Re: internal server error detected
>>
>> This log is almost always helpful:
>>
>> /home/instance_owner/sqllib/db2dump/db2diag.0.log
>>
>> Or it could be rotated into db2diag.n.log in the same directory.
>>
>> Regards,
>>
>> --
>> Sasa Drnjevic
>> www.srce.unizg.hr
>>
>>
>>
>>
>> On 31.1.2017. 13:56, Loon, Eric van (ITOPT3) - KLM wrote:
>> > Hi guys!
>> > I have an Oracle client which backup failed with the following error in
>> the tdpoerror.log:
>> >
>> > 01/31/2017 09:08:35 ANS0278S The transaction will be aborted.
>> > 01/31/2017 09:08:35 ANS0278S The transaction will be aborted.
>> > 01/31/2017 09:08:35 TID<19506> ==> ANS0278S (RC157)  The transaction
>> will be aborted.
>> > 01/31/2017 09:08:35 ANS1312E Server media mount not possible
>> > 01/31/2017 09:08:35 ANS1312E Server media mount not possible
>> > 1/31/2017 09:08:35 TID<19506> ==> ANS1312E (RC12)   Server media mount
>> not possible
>> >
>> > The TSM server shows the following error:
>> >
>> > 01/31/2017 09:08:32 ANR0530W Transaction failed for session 9302740 for
>> node QVIPNBDORA01_02-ORC (TDPO Linux86-64) - internal server error
>> detected. (SESSION: 9302740)
>> > 01/31/2017 09:08:35 ANR0525W (Session: 7358241, Origin: QVIPNBDORA01)
>> Transaction failed for session 277695 for node QVIPNBDORA01_02-ORC (TDPO
>> Linux86-64) - storage media inaccessible. (SESSION: 7358241)
>> >
>> > The Oracle client is backing up through a storage agent and the
>> 'internal server error' seems to cause the scratch tape mount to fail which
>> results in the 'storage media inaccessible' message. Does anybody have an
>> idea where to look for the cause of the 'internal server error'?
>> > Thanks for any help in advance!
>> > Kind regards,
>> > Eric van Loon
>> > Air France/KLM Storage Engineering
>> > ********************************************************
>> > For information, services and offers, please visit our web site:
>> http://www.klm.com. This e-mail and any attachment may contain
>> confidential and privileged material intended for the addressee only. If
>> you are not the addressee, you are notified that no part of the e-mail or
>> any attachment may be disclosed, copied or distributed, and that any other
>> action related to this e-mail or attachment is strictly prohibited, and may
>> be unlawful. If you have received this e-mail by error, please notify the
>> sender immediately by return e-mail, and delete this message.
>> >
>> > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or
>> its employees shall not be liable for the incorrect or incomplete
>> transmission of this e-mail or any attachments, nor responsible for any
>> delay in receipt.
>> > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
>> Airlines) is registered in Amstelveen, The Netherlands, with registered
>> number 33014286
>> > ********************************************************
>> >
>> ********************************************************
>> For information, services and offers, please visit our web site:
>> http://www.klm.com. This e-mail and any attachment may contain
>> confidential and privileged material intended for the addressee only. If
>> you are not the addressee, you are notified that no part of the e-mail or
>> any attachment may be disclosed, copied or distributed, and that any other
>> action related to this e-mail or attachment is strictly prohibited, and may
>> be unlawful. If you have received this e-mail by error, please notify the
>> sender immediately by return e-mail, and delete this message.
>>
>> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
>> employees shall not be liable for the incorrect or incomplete transmission
>> of this e-mail or any attachments, nor responsible for any delay in receipt.
>> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
>> Airlines) is registered in Amstelveen, The Netherlands, with registered
>> number 33014286
>> ********************************************************
>>
>>
>