Unexpected error 16 fetching row in table "Backup.Nameview"

[Zoltan Forray]

Server is RH Linux 6.2.4.000 (yes, I am aware of the 6.2.4.200 patch but
nothing in the readme/descriptions address anything similar/related).
 Client is W2K3 6.3.0.18 client

These errors are becoming a nightly problem.  From the server side:

10/11/2012 2:03:48 AM ANR0106E imbkqry.c(1358): Unexpected error 16
fetching row in table "Backup.Nameview".
10/11/2012 2:03:48 AM ANRD_2341696307 DoBackQry(smnode.c:17702)
Thread<4122>: Unexpected rc=19 from imGetNextBackup
10/11/2012 2:03:48 AM ANRD Thread<4122> issued message  from:
10/11/2012 2:03:48 AM ANRD Thread<4122>  0xc8f063 OutDiagToCons
10/11/2012 2:03:48 AM ANRD Thread<4122>  0xc91ce8 outDiagfExt
10/11/2012 2:03:48 AM ANRD Thread<4122>  0xa8658b DoBackQry
10/11/2012 2:03:48 AM ANRD Thread<4122>  0xa99bc8 SmNodeSession
10/11/2012 2:03:48 AM ANRD Thread<4122>  0xac31bf
SmSchedSession
10/11/2012 2:03:48 AM ANRD Thread<4122>  0xa5ef3f
HandleNodeSession
10/11/2012 2:03:48 AM ANRD Thread<4122>  0xa61e5d
smExecuteSession
10/11/2012 2:03:48 AM ANRD Thread<4122>  0xd152fb
psSessionThread
10/11/2012 2:03:48 AM ANRD Thread<4122>  0xd06303 StartThread
10/11/2012 2:03:48 AM ANRD Thread<4122>  0x33db007851 *UNKNOWN*
10/11/2012 2:03:48 AM ANRD Thread<4122>  0x33da8e811d *UNKNOWN*

>From the client side:

10/11/2012 02:03:45 cuGetBackQryResp: Server aborted txn, reason: 1
10/11/2012 02:03:45 ANS1999E Incremental processing of '\\acipenser\i$'
stopped.

10/11/2012 02:03:46 ANS1301E Server detected system error

FWIW, this is our largest Windows server, object-wise.  *>60M* objects
scanned.  Total backups occupancy is >*378M* objects and 60TB.  Running
Journal and MEMORYEFFICIENTBACKUP  since the server only has 8GB memory.

Googling produces nothing usable/helpful. Looking for any ideas on how to
diagnose/resolve this...

--
*Zoltan Forray*
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html

Re: TSM 6.1 - IC68245 - Unexpected error 2 fetching row in table during RECLAIMS

[Prather, Wanda]

They show up on their own during reclamation (and reclamation fails on that 
volume).
Sounds like the patch cleans them up.
Thanks!

W

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Zoltan 
Forray/AC/VCU
Sent: Tuesday, October 19, 2010 12:02 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM 6.1 - IC68245 - Unexpected error 2 fetching row in 
table during RECLAIMS

FWIW, we have been at 6.1.4.1 for a while and are no longer seeing the
errors.  How would I check for the orphans?
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html



From:
"Prather, Wanda" 
To:
ADSM-L@VM.MARIST.EDU
Date:
10/19/2010 11:13 AM
Subject:
[ADSM-L] TSM 6.1 - IC68245 -  Unexpected error 2 fetching row in table
during RECLAIMS
Sent by:
"ADSM: Dist Stor Manager" 



Anybody on 6.1 who has survived and recovered from IC68245,

Can you tell me whether upgrading to 6.1.4.1 (or a 6.2 x) to get the
fixing code actually takes care of the orphans for you, or does it just
stop new orphans from being created?

Trying to figure out whether it's best to go ahead and upgrade first, or
have Tivoli support clean up the orphans one at a time

Thanks!

Wanda Prather  |  Senior Technical Specialist  | wprat...@icfi.com<
mailto:wprat...@icfi.com>  |  www.jasi.com
ICF Jacob & Sundstrom  | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202
| 410.539.1135

Re: TSM 6.1 - IC68245 - Unexpected error 2 fetching row in table during RECLAIMS

[Zoltan Forray/AC/VCU]

FWIW, we have been at 6.1.4.1 for a while and are no longer seeing the
errors.  How would I check for the orphans?
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html



From:
"Prather, Wanda" 
To:
ADSM-L@VM.MARIST.EDU
Date:
10/19/2010 11:13 AM
Subject:
[ADSM-L] TSM 6.1 - IC68245 -  Unexpected error 2 fetching row in table
during RECLAIMS
Sent by:
"ADSM: Dist Stor Manager" 



Anybody on 6.1 who has survived and recovered from IC68245,

Can you tell me whether upgrading to 6.1.4.1 (or a 6.2 x) to get the
fixing code actually takes care of the orphans for you, or does it just
stop new orphans from being created?

Trying to figure out whether it's best to go ahead and upgrade first, or
have Tivoli support clean up the orphans one at a time

Thanks!

Wanda Prather  |  Senior Technical Specialist  | wprat...@icfi.com<
mailto:wprat...@icfi.com>  |  www.jasi.com
ICF Jacob & Sundstrom  | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202
| 410.539.1135

TSM 6.1 - IC68245 - Unexpected error 2 fetching row in table during RECLAIMS

[Prather, Wanda]

Anybody on 6.1 who has survived and recovered from IC68245,

Can you tell me whether upgrading to 6.1.4.1 (or a 6.2 x) to get the fixing 
code actually takes care of the orphans for you, or does it just stop new 
orphans from being created?

Trying to figure out whether it's best to go ahead and upgrade first, or have 
Tivoli support clean up the orphans one at a time

Thanks!

Wanda Prather  |  Senior Technical Specialist  | 
wprat...@icfi.com  |  www.jasi.com
ICF Jacob & Sundstrom  | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202 | 
410.539.1135

TransErrno: Unexpected error from opendir, errno = 9

[Huebschman, George J.]

First, I apologize for the lengthy posting.
I have an AIX client that Failed its backup and I don't have a clear
idea why.

I found some old APARS related to TransErrno errors, but nothing that
seemed to fit.

Client AIX - oslevel 5.3.0.0
TSM Client V5 R4 L1.0

TSM Server  - oslevel 5.3.0.0
TSM Server V5 R5 L1.0

Checking the dsmerror and dsmsched I found the following just before the
backup ended:
dsmerror.log:
01/07/10   03:27:10 TransErrno: Unexpected error from opendir, errno = 9
01/07/10   03:27:10 ANS1228E Sending of object
'/usr/dt/appconfig/icons/C/Dtaudio.t.bm' failed
01/07/10   03:27:10 ANS4005E Error processing
'/usr/dt/appconfig/icons/C/Dtaudio.t.bm': file not found
01/07/10   03:27:10 ANS1228E Sending of object
'/usr/dt/appconfig/icons/C/Dthitem.m_m.bm' failed
01/07/10   03:27:10 ANS4005E Error processing
'/usr/dt/appconfig/icons/C/Dthitem.m_m.bm': file not found
01/07/10   03:27:11 ANS1999E Incremental processing of '/usr' stopped.
** 01/07/10   03:27:11 ANS1028S An internal program error occurred.  **
01/07/10   03:27:11 ANS1512E Scheduled event '3AM-DAILY-INCR' failed.
Return code = 12.

"File not found" errors are nothing new - The file was there when the
backup began, then were gone by the time the client processed to that
point.  I don't expect them to fail a backup.  I am inclined to regard
them as coincidental but unrelated.

How do I get more information on the cause of this ANS1028S?

dsmsched.log:

01/07/10   03:27:11 Normal File--> 1,875
/usr/dt/appconfig/icons/C/Dtshell.m.pm [Sent]
01/07/10   03:27:11 Normal File--> 1,368
/usr/dt/appconfig/icons/C/Dtshell.m_m.bm [Sent]
01/07/10   03:27:11 Normal File-->   753
/usr/dt/appconfig/icons/C/Dtshell.st.bm [Sent]
01/07/10   03:27:11 Normal File-->   763
/usr/dt/appconfig/icons/C/Dtshell.st_m.bm [Sent]
01/07/10   03:27:11 ANS1999E Incremental processing of '/usr' stopped.
01/07/10   03:27:11 --- SCHEDULEREC STATUS BEGIN
01/07/10   03:27:11 Total number of objects inspected:8,170
01/07/10   03:27:11 Total number of objects backed up:6,799
01/07/10   03:27:11 Total number of objects updated:  0
01/07/10   03:27:11 Total number of objects rebound:  0
01/07/10   03:27:11 Total number of objects deleted:  0
01/07/10   03:27:11 Total number of objects expired:  0
01/07/10   03:27:11 Total number of objects failed:  78
01/07/10   03:27:11 Total number of bytes transferred:173.06 MB
01/07/10   03:27:11 Data transfer time:   10.19 sec
01/07/10   03:27:11 Network data transfer rate:17,390.74 KB/sec
01/07/10   03:27:11 Aggregate data transfer rate:  5,503.06 KB/sec
01/07/10   03:27:11 Objects compressed by:0%
01/07/10   03:27:11 Elapsed processing time:   00:00:32
01/07/10   03:27:11 --- SCHEDULEREC STATUS END
*** 01/07/10   03:27:11 ANS1028S An internal program error occurred.
***
01/07/10   03:27:11 --- SCHEDULEREC OBJECT END 3AM-DAILY-INCR 01/07/10
03:00:00
01/07/10   03:27:11 ANS1512E Scheduled event '3AM-DAILY-INCR' failed.
Return code = 12.

Yes, I looked at the client online help for ANS1028S.
I found an old APAR that sounds related:
IC44226: TSM CLIENT ABORTS BACKUP WITH ANS1028S ERROR MESSAGE - The TSM
client may abort a backup with an ANS1028S Internal
Program Error due to an unexpected return code from the
operating system. TSM Versions Affected: 5.2

George Huebschman
Storage Support Team, Media Librarian
Legg Mason, LMTS
410 580-7911 (office)
410 522-8581 (mobile)

Please consider the environment before printing this e-mail



IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason 
therefore recommends that you do not send any confidential or sensitive 
information to us via electronic mail, including social security numbers, 
account numbers, or personal identification numbers. Delivery, and or timely 
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends 
that you do not send time sensitive 
or action-oriented messages to us via electronic mail.

This message is intended for the addressee only and may contain privileged or 
confidential information. Unless you are the intended recipient, you may not 
use, copy or disclose to anyone any information contained in this message. If 
you have received this message in error, please notify the author by replying 
to this message and then kindly delete the message. Thank you.

Re: VSS: Unexpected error calling routine MoveFileExW on Win2k3 Client

[Markus Engelhard]

Dear Wanda, dear Tim,

thanks for the feedback. OFS is required for a couple of systems for BMR. I
fully agree that it does not take care of all aspects of recovery and
databases are a case to be taken care of with great caution in regard to
consitent backups. For this part of recovery I prefer to use the TDP
modules or offline backups for systems we can afford a downtime for.
The VSS just had this one hickup and has been working since, no reboot. If
the error occurs again, an upgrade of the client version will be my next
step. I was just curious as the "MoveFileExW" part was new to me, I
believed I had been through most of the VSS errors already last year,
successfully fixing the issues thanks to postings to be found on this list.

Looking forward to see a lot of you at the TSM symposium!

Markus



--
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet.

Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der
Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch
raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser
Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder
grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch
virenbefallene Software oder E-Mails aus.

Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch
schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer
irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden.
__

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorised copying, disclosure or distribution of  the material in this
e-mail or of parts hereof is strictly forbidden.

We have taken precautions to minimize the risk of transmitting software
viruses but nevertheless advise you to carry out your own virus checks on
any attachment of this message. We accept no liability for loss or damage
caused by software viruses except in case of gross negligence or willful
behaviour.

Any e-mail messages from the Bank are sent in good faith, but shall not be
binding or construed as constituting any kind of obligation on the part of
the Bank.

Re: VSS: Unexpected error calling routine MoveFileExW on Win2k3 Client

[Timothy Hughes]

"If this is a systemstate backup error, it's not surprising.  Even with 
all the MS patches on, and with VSSADMIN LIST WRITERS showing no error, 
you'll

occasionally have issues with VSS doing system state backups."

Yeah, I agree with Wanda a couple of months ago, we were having  
systemstate backup errors with MS patches and upgraded some  from 5.5.0 
then>> 5.5.1 then >> 5.5.1.10 to 5.5.1.16. It didn't help until Tivoli 
recommended we upgrade to client 5.5.2 that seemed to solve the issue 
and even now occasionally NOT often  we still have VSS errors from time 
to time.


VSS can be a pain


If this is a systemstate backup error, it's not surprising.  Even with all
the MS patches on, and with VSSADMIN LIST WRITERS showing no error, you'll
occasionally have issues with VSS doing system state backups.
It will either clear up on its own, or you'll have to schedule a reboot to
make it go away.

OTOH, do you have TSM Open File Support enabled on teh Win2K3 client?  And
are you using it for something in particular?

I tell my customers NOT to enable Open File support on Windows except in
very rare cases.

Open File Support does not give you valid backups of most Windows locked
files (like SQL DB's, for example).  The only time you should use it, is if
you have a particular application that you know you can get valid backups
with Open File Support, and no other way.  And the reason to have it turned
off, is that if it is enabled you tend to get bogus errors like this from
it.

"VSS is like a Nose, sometimes it Runs, sometimes it Blows" -- me


On Mon, Jul 13, 2009 at 7:09 AM, Markus Engelhard <
markus.engelh...@bundesbank.de> wrote:

 


Dear all,

has anyone come across the following eventlog error message while backing
up a W2K3 client?

Volume Shadow Copy Service error: Unexpected error calling routine
MoveFileExW

TSM backups work, nothing in the TSM error log or schedlog. No change,
client has been working happily for quite a while like 1000+ others.
VSSADMIN LIST WRITERS returns no error.
I don't believe it is a TSM issue in the end.

I'm just curious as MS, IBM, google and the forum don´t come up with much
apart from NetBackup stuff from 2005 and Windows 2000 cluster errors dating
way back.

VSSADMIN LIST WRITERS returns no error.

TSM Server is Solaris9, TSM Version 5.5.2.1
TSM Client is Window2003, current os patches (deemed essential for VSS to
work, been through that)
TSM Client Version 5.3.4.0 (I know, out of service, but hard to keep up in
a large environment)

Thanks for your help, all the stuff on the forum is really appreciated!

Markus


--
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet.

Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der
Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch
raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser
Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder
grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch
virenbefallene Software oder E-Mails aus.

Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch
schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer
irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden.
__

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorised copying, disclosure or distribution of  the material in this
e-mail or of parts hereof is strictly forbidden.

We have taken precautions to minimize the risk of transmitting software
viruses but nevertheless advise you to carry out your own virus checks on
any attachment of this message. We accept no liability for loss or damage
caused by software viruses except in case of gross negligence or willful
behaviour.

Any e-mail messages from the Bank are sent in good faith, but shall not be
binding or construed as constituting any kind of obligation on the part of
the Bank.



 

Re: VSS: Unexpected error calling routine MoveFileExW on Win2k3 Client

[Wanda Prather]

If this is a systemstate backup error, it's not surprising.  Even with all
the MS patches on, and with VSSADMIN LIST WRITERS showing no error, you'll
occasionally have issues with VSS doing system state backups.
It will either clear up on its own, or you'll have to schedule a reboot to
make it go away.

OTOH, do you have TSM Open File Support enabled on teh Win2K3 client?  And
are you using it for something in particular?

I tell my customers NOT to enable Open File support on Windows except in
very rare cases.

Open File Support does not give you valid backups of most Windows locked
files (like SQL DB's, for example).  The only time you should use it, is if
you have a particular application that you know you can get valid backups
with Open File Support, and no other way.  And the reason to have it turned
off, is that if it is enabled you tend to get bogus errors like this from
it.

"VSS is like a Nose, sometimes it Runs, sometimes it Blows" -- me


On Mon, Jul 13, 2009 at 7:09 AM, Markus Engelhard <
markus.engelh...@bundesbank.de> wrote:

> Dear all,
>
> has anyone come across the following eventlog error message while backing
> up a W2K3 client?
>
> Volume Shadow Copy Service error: Unexpected error calling routine
> MoveFileExW
>
> TSM backups work, nothing in the TSM error log or schedlog. No change,
> client has been working happily for quite a while like 1000+ others.
> VSSADMIN LIST WRITERS returns no error.
> I don't believe it is a TSM issue in the end.
>
> I'm just curious as MS, IBM, google and the forum don´t come up with much
> apart from NetBackup stuff from 2005 and Windows 2000 cluster errors dating
> way back.
>
> VSSADMIN LIST WRITERS returns no error.
>
> TSM Server is Solaris9, TSM Version 5.5.2.1
> TSM Client is Window2003, current os patches (deemed essential for VSS to
> work, been through that)
> TSM Client Version 5.3.4.0 (I know, out of service, but hard to keep up in
> a large environment)
>
> Thanks for your help, all the stuff on the forum is really appreciated!
>
> Markus
>
>
> --
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte
> Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet.
>
> Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der
> Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch
> raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser
> Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder
> grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch
> virenbefallene Software oder E-Mails aus.
>
> Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch
> schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer
> irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden.
> __
>
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorised copying, disclosure or distribution of  the material in this
> e-mail or of parts hereof is strictly forbidden.
>
> We have taken precautions to minimize the risk of transmitting software
> viruses but nevertheless advise you to carry out your own virus checks on
> any attachment of this message. We accept no liability for loss or damage
> caused by software viruses except in case of gross negligence or willful
> behaviour.
>
> Any e-mail messages from the Bank are sent in good faith, but shall not be
> binding or construed as constituting any kind of obligation on the part of
> the Bank.

VSS: Unexpected error calling routine MoveFileExW on Win2k3 Client

[Markus Engelhard]

Dear all,

has anyone come across the following eventlog error message while backing
up a W2K3 client?

Volume Shadow Copy Service error: Unexpected error calling routine
MoveFileExW

TSM backups work, nothing in the TSM error log or schedlog. No change,
client has been working happily for quite a while like 1000+ others.
VSSADMIN LIST WRITERS returns no error.
I don't believe it is a TSM issue in the end.

I'm just curious as MS, IBM, google and the forum don´t come up with much
apart from NetBackup stuff from 2005 and Windows 2000 cluster errors dating
way back.

VSSADMIN LIST WRITERS returns no error.

TSM Server is Solaris9, TSM Version 5.5.2.1
TSM Client is Window2003, current os patches (deemed essential for VSS to
work, been through that)
TSM Client Version 5.3.4.0 (I know, out of service, but hard to keep up in
a large environment)

Thanks for your help, all the stuff on the forum is really appreciated!

Markus


--
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet.

Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der
Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch
raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser
Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder
grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch
virenbefallene Software oder E-Mails aus.

Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch
schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer
irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden.
__

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorised copying, disclosure or distribution of  the material in this
e-mail or of parts hereof is strictly forbidden.

We have taken precautions to minimize the risk of transmitting software
viruses but nevertheless advise you to carry out your own virus checks on
any attachment of this message. We accept no liability for loss or damage
caused by software viruses except in case of gross negligence or willful
behaviour.

Any e-mail messages from the Bank are sent in good faith, but shall not be
binding or construed as constituting any kind of obligation on the part of
the Bank.

Re: TransErrno: Unexpected error from GetFSInfo

[Richard Sims]

On Nov 8, 2005, at 8:27 AM, Werner Nussbaumer wrote:


...The only thing that would be nice is if dsmc would display to
directory
which causes problems.


Amen. Programming which knows where a problem is but won't reveal it
just wastes customer time. One approach is to perform a full,
Selective backup of the file system in non-Quiet mode. Another
approach is to perform the 'dsmc i' with client tracing active. I
would first check the OS error log (maybe /var/log/messages?) and see
if there are any NFS mount points within the file system in question,
and then assure that those NFS servers are responsive.

   Richard Sims http://people.bu.edu/rbs

Re: TransErrno: Unexpected error from GetFSInfo

[Werner Nussbaumer]

Thank you for your answer. In errno.h there is:

 /* Connection timed out.  The */
#define ETIMEDOUT  1127  /*  connection to a remote*/
 /*  machine has timed out.* 
  *  If the connection timed   * 
  *  out during execution of   * 
  *  the function that reported* 
  *  this error (as opposed to * 
  *  timing out prior to the   * 
  *  function being called),   * 
  *  it is unspecified whether * 
  *  the function has completed* 
  *  some or all of the* 
  *  documented behavior   * 
  *  associated with a * 
  *  successful completion of  * 
  *  the function. */

The only thing that would be nice is if dsmc would display to directory
which causes problems.

Regards
Werner Nussbaumer 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Sims
Sent: Dienstag, 8. November 2005 14:18
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TransErrno: Unexpected error from GetFSInfo

On Nov 8, 2005, at 7:50 AM, Werner Nussbaumer wrote:

> Hi, we use the TSM client version 5.3 on z/OS OMVS (UNIX). If we start

> "dsmc incr" then we see the following error messages in dsmerror.log:
>
> 08.11.2005 13:06:36 TransErrno: Unexpected error from 
> GetFSInfo:statfs, errno = 1127 ...
>
> There must be some problems for dsmc scanning the directory.
> However is
> there any way to see which directories are causing the problems, and 
> what does error 1127 mean?

See the errno.h header file in your OMVS arena, probably under /usr/
include/.
I don't have access to an OMVS system, but I believe the 1127 is
ETIMEDOUT.
That is most common in a statfs() operation where the file system is a
networked type (e.g., NFS), where the NFSD on the serving system is
having response problems or there are protocol or network problems.
When it happens on a local file system, it could mean disk problems,
which should show up in your OS error log.

A recursive 'ls -lR /fsname' or 'find /fsname -ls' through the file
system may reveal a problem area.

Richard Sims

Re: TransErrno: Unexpected error from GetFSInfo

[Richard Sims]

On Nov 8, 2005, at 7:50 AM, Werner Nussbaumer wrote:


Hi, we use the TSM client version 5.3 on z/OS OMVS (UNIX). If we start
"dsmc incr" then we see the following error messages in dsmerror.log:

08.11.2005 13:06:36 TransErrno: Unexpected error from
GetFSInfo:statfs,
errno = 1127
...

There must be some problems for dsmc scanning the directory.
However is
there any way to see which directories are causing the problems, and
what does error 1127 mean?


See the errno.h header file in your OMVS arena, probably under /usr/
include/.
I don't have access to an OMVS system, but I believe the 1127 is
ETIMEDOUT.
That is most common in a statfs() operation where the file system is a
networked type (e.g., NFS), where the NFSD on the serving system is
having
response problems or there are protocol or network problems.  When it
happens on a local file system, it could mean disk problems, which
should
show up in your OS error log.

A recursive 'ls -lR /fsname' or 'find /fsname -ls' through the file
system may
reveal a problem area.

   Richard Sims

TransErrno: Unexpected error from GetFSInfo

[Werner Nussbaumer]

Hi, we use the TSM client version 5.3 on z/OS OMVS (UNIX). If we start
"dsmc incr" then we see the following error messages in dsmerror.log:

08.11.2005 13:06:36 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:07:45 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:09:42 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:10:51 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:13:57 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:17:04 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:20:10 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:23:17 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:26:23 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:29:29 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:32:38 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:35:47 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:38:56 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:42:02 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127
08.11.2005 13:45:09 TransErrno: Unexpected error from GetFSInfo:statfs,
errno = 1127

There must be some problems for dsmc scanning the directory. However is
there any way to see which directories are causing the problems, and
what does error 1127 mean?

Thanks for any help
Regards
Werner Nussbaumer

Re: Unexpected error 2 fetching row in table "Archive.Objects".

[hassan hani]

thanks you all for your help
concerning the error : "Unexpected error 2 fetching row in table
"Archive.Objects".
there is a solution for the version TSM 5.2.3 which consists of:
Solution:
The archive descriptions table(s) of the failing node needs to be
repopulated again.
This can be done by unconverting and re-converting the node.
Commands:
1. To unconvert the node:
undo archconversion 
2. To re-convert the node:
convert archive 
but i have a problem:
i have version TSM server 5.1, and i don't have the command " undo
archconversion"
is there a solution for the server TSM 5.1
thanks you very much


From: "Loon, E.J. van - SPLXM" <[EMAIL PROTECTED]>
Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Unexpected error 2 fetching row in table "Archive.Objects".
Date: Thu, 25 Nov 2004 13:24:06 +0100
Hi Hassan!
I assume you are running a TSM 5.2.3.x server? (Please report client and
server levels if you post problems)
Checkout the following support document:
http://www-1.ibm.com/support/docview.wss?rs=663&context=SSGSG7&q1=ANR0106E&u
id=swg21189891&loc=en_US&cs=utf-8&lang=en
Kindest regards,
Eric van Loon
-Original Message-
From: hassan hani [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 25, 2004 11:24
To: [EMAIL PROTECTED]
Subject: Unexpected error 2 fetching row in table "Archive.Objects".
hello,
i get this error in log
ANR0106E imarqry.c(4481): Unexpected error 2 fetching row in table
"Archive.Objects".
as a result i can't see my archives
does anyone have an idea how to resolve this
thanks you very much
**
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.
**

Re: Unexpected error 2 fetching row in table "Archive.Objects".

[goc]

aha, i get i got this message too, and to fix it you have to enter
non-supported command ?
thats why you didnt reply as you could ?
thanks ... and continue as always ...
greetz ,
goran
- Original Message -
From: "Richard Sims" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 25, 2004 1:42 PM
Subject: Re: Unexpected error 2 fetching row in table "Archive.Objects".

>i get this error in log
ANR0106E imarqry.c(4481): Unexpected error 2 fetching row in table
"Archive.Objects".
as a result i can't see my archives
does anyone have an idea how to resolve this
When posting, be sure to include your software level so that we know the
context.
Search on that message number at www.ibm.com : there is an APAR.
This is to say that your server will likely benefit from a maintenance
boost.
  Richard Sims

Re: Unexpected error 2 fetching row in table "Archive.Objects".

[Loon, E.J. van - SPLXM]

Hi Hassan!
I assume you are running a TSM 5.2.3.x server? (Please report client and
server levels if you post problems)
Checkout the following support document:
http://www-1.ibm.com/support/docview.wss?rs=663&context=SSGSG7&q1=ANR0106E&u
id=swg21189891&loc=en_US&cs=utf-8&lang=en
Kindest regards,
Eric van Loon


-Original Message-
From: hassan hani [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 25, 2004 11:24
To: [EMAIL PROTECTED]
Subject: Unexpected error 2 fetching row in table "Archive.Objects".


hello,

i get this error in log

ANR0106E imarqry.c(4481): Unexpected error 2 fetching row in table
"Archive.Objects".


as a result i can't see my archives


does anyone have an idea how to resolve this

thanks you very much


**
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.
**

Re: Unexpected error 2 fetching row in table "Archive.Objects".

[Richard Sims]

>i get this error in log
>
>ANR0106E imarqry.c(4481): Unexpected error 2 fetching row in table
>"Archive.Objects".
>
>as a result i can't see my archives
>
>does anyone have an idea how to resolve this

When posting, be sure to include your software level so that we know the
context.

Search on that message number at www.ibm.com : there is an APAR.
This is to say that your server will likely benefit from a maintenance boost.

   Richard Sims

Unexpected error 2 fetching row in table "Archive.Objects".

[hassan hani]

hello,
i get this error in log
ANR0106E imarqry.c(4481): Unexpected error 2 fetching row in table
"Archive.Objects".
as a result i can't see my archives
does anyone have an idea how to resolve this
thanks you very much

Unexpected error ?

[goc]

 hi all
 since upgrading to 5.2.3.0
 this shows up every night
 2004-11-15 16:23
 anyone seen this before ?
 i suspect it has sometzhing to do with expiration process coz it has
small session number , all other processes from that time had proc number
around 33000
 expiration lasts for 7 hours
 no other related messages in actlog can be found .. ANR0106E
imarqry.c(4996): 2 fetching row in table "Archive.Objects".
(SESSION: 8488, PROCESS: 1773)

Re: TransErrno: Unexpected error

[Lisa Cabanas]

Tony--
on wintel this usually means that there is some corruption on the disk and
a chkdsk needs to be run.  The 131 means system error.

Knowing very little about Linux-- can you run a consistency checker, like
fsck or chkdsk?

good luck!

-lisa



"Trinh, Tony"
 cc:
Sent by: Subject: TransErrno: Unexpected error
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
IST.EDU>


01/16/2003
10:08 AM
Please respond
to "ADSM: Dist
Stor Manager"





Hello TSMer's,



Have any ran into this problem. This is from a Linux client version 4.2.0.0
server is 4.2.1.19





01/16/2003 15:44:17 TransErrno: Unexpected error from lstat, errno = 75



01/16/2003 15:44:17 PrivIncrFileSpace: Received rc=131 from
fioGetDirEntries:  /

  /opt/mysql_back/tracking



01/16/2003 15:44:18 ANS1028S Internal program error.  Please see your
service re

presentative.







Your humble servant,



--= Tony Trinh
 Tivoli Storage Manager Admin (TSM)
 c: 408-221-7867
 Storage, Backup - Intel =--







Sometimes each day is a battle.. so we try to make each day a
victoryone day at a time




(See attached file: image001.gif)

<>

TransErrno: Unexpected error

[Trinh, Tony]

Hello TSMer's,



Have any ran into this problem. This is from a Linux client version 4.2.0.0
server is 4.2.1.19





01/16/2003 15:44:17 TransErrno: Unexpected error from lstat, errno = 75



01/16/2003 15:44:17 PrivIncrFileSpace: Received rc=131 from
fioGetDirEntries:  /

  /opt/mysql_back/tracking



01/16/2003 15:44:18 ANS1028S Internal program error.  Please see your
service re

presentative.







Your humble servant,



--= Tony Trinh
 Tivoli Storage Manager Admin (TSM)
 c: 408-221-7867
 Storage, Backup - Intel =--







Sometimes each day is a battle.. so we try to make each day a
victoryone day at a time




<>