ADSM-L

Re: [ADSM-L] ANS1030E The operating system refused a TSM request form memory allocation

2008-01-24 16:33:19
Subject: Re: [ADSM-L] ANS1030E The operating system refused a TSM request form memory allocation
From: Hans Christian Riksheim <HCR AT STERIA DOT NO>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 24 Jan 2008 21:57:52 +0100
Hi!
 
Several possibilites here.
 
First find out if the AIX error log tells you something.
 
Limits:
Check in /etc/security/limts if there are any restrictions on memory usage. I 
usually set all to -1(unrestricted) to be sure.
 
Memory leak in 'dsmc schedule':
After a while this process tends to grab a lot of memory and not release it 
properly.(1 GB or more at times). If so restart it. Check with "ps auxww" or 
similar.
 
Monitor system resource usage while backup is running. For example run "nmon" 
and check system memory and the amount of memory dsmc uses. If %numperm 
increases a lot and the system starts to swap you may have a problem with file 
cache exhausting all your memory. This can be tuned in AIX.
 
If the "dsmc" process is taking all the memory you should either restrict usage 
with the "memoryefficient" option, add memory to the system or complain to 
IBM(I mean, 1,5 mill files isn't that uncommon.)
 
 
Hans Chr.
 
 

________________________________

Fra: ADSM: Dist Stor Manager på vegne av Timothy Hughes
Sendt: to 24.01.2008 20:51
Til: ADSM-L AT VM.MARIST DOT EDU
Emne: ANS1030E The operating system refused a TSM request form memory allocation



Hello all,


One of our AIX clients is failing, The dsmerror.log shows the ANS1030E
The operating system refused a TSM request for memory allocation message
below. I found some information but I am still confused to according
what I found this is some sort of "Fat Binary issue" I assume this is
not a TSM problem? Or does it varies in possibilities?

Thanks in Advance!


01/24/08 01:34:09 --- SCHEDULEREC STATUS BEGIN
01/24/08 01:34:09 Total number of objects inspected: 1,543,630
01/24/08 01:34:09 Total number of objects backed up: 777
01/24/08 01:34:09 Total number of objects updated: 0
01/24/08 01:34:09 Total number of objects rebound: 0
01/24/08 01:34:09 Total number of objects deleted: 0
01/24/08 01:34:09 Total number of objects expired: 60
01/24/08 01:34:09 Total number of objects failed: 3
01/24/08 01:34:09 Total number of bytes transferred: 8.34 GB
01/24/08 01:34:09 Data transfer time: 169.83 sec
01/24/08 01:34:09 Network data transfer rate: 51,528.86 KB/sec
01/24/08 01:34:09 Aggregate data transfer rate: 1,690.76 KB/sec
01/24/08 01:34:09 Objects compressed by: 100%
01/24/08 01:34:09 Elapsed processing time: 01:26:16
01/24/08 01:34:09 --- SCHEDULEREC STATUS END
01/24/08 01:34:09 ANS1030E The operating system refused a TSM request
for memory allocation.
01/24/08 01:34:09 --- SCHEDULEREC OBJECT END MIDNIGHT 01/24/08 00:00:01
01/24/08 01:34:09 ANS1512E Scheduled event 'MIDNIGHT' failed. Return
code = 12.
01/24/08 01:34:09 Sending results for scheduled event 'MIDNIGHT'.
01/24/08 01:34:09 Results sent to server for scheduled event 'MIDNIGHT'.



TSM Server 5.3.3.4
AIX 5.3
AIX Client 5.3.4


<html><body><br /><br /><br /><font face="Arial" size="1"><hr>This email 
originates from Steria AS, Biskop Gunnerus' gate 14a, N-0051 OSLO, 
http://www.steria.no. This email and any attachments may contain 
confidential/intellectual property/copyright information and is only for the 
use of the addressee(s). You are prohibited from copying, forwarding, 
disclosing, saving or otherwise using it in any way if you are not the 
addressee(s) or responsible for delivery. If you receive this email by mistake, 
please advise the sender and cancel it immediately. Steria may monitor the 
content of emails within its network to ensure compliance with its policies and 
procedures. Any email is susceptible to alteration and its integrity cannot be 
assured. Steria shall not be liable if the message is altered, modified, 
falsified, or even edited.</font></body></html>