If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Unanswered: TSM error 11 when log archiving

Hi, we have old DB2 system with DB2 v8 on AIX. Due to financial constraints this hasn't been updated yet but works fine.

However TSM password has expired and stopped backup and log archiving. TSM staff reset the password and now backup works but log archiving still failed with the following error. This happened long time ago and resetting the password resolved the issue. However the TSM staff is a new member for the company. Could you give some advice please ?

TSM RC 11 means there isn't space available for storage. Possibly backups and logs belong to different TSM policies and are stored in different pools, this is why backups succeed and log archiving does not.

0011 E
DSM_RC_ABORT_NO_REPOSIT_SPACE
Explanation:
The server does not have any space available to store the object.

System action:
Tivoli Storage Manager ended the current operation.

User response:
You can take any of the following actions:

Request the system administrator to add space to the storage pool.
For Tivoli Storage Manager client, set COMPRESSALWAYS=NO and COMPRESSIon=YES in the options file (DSM.OPT), then the file will be resent uncompressed if it grows during compression.
For API Applications, consult the application's documentation for recommendations regarding compression.
Turn off disk caching in the disk storage pool, and issue MOVE DATA commands to each disk pool volume to clear out the cached bitfiles.

However TSM password has expired and stopped backup and log archiving. TSM staff reset the password and now backup works but log archiving still failed

DB2 loads TSM API when the backup is initiated, but DB2 logger loads it when the instance is started and a portion of it is held in memory until instance recycle. You can try restarting the instance. The real RC from TSM will tell you why it's failing.

for backup you need backup stgpool and for logs you need archive stgpool
usually that can not be the same
we had a similar problem and killed the db2vend process for that db - it will restart
for pw problem it is better to use the generated option and execute dsmapipw

Best Regards, Guy Przytula
Database Software Consultant
Good DBAs are not formed in a week or a month. They are created little by little, day by day. Protracted and patient effort is needed to develop good DBAs.
Spoon feeding : To treat (another) in a way that discourages independent thought or action, as by overindulgence.
DB2 UDB LUW Certified V7-V8-V9-V9.7-V10.1-V10.5 DB Admin - Advanced DBA -Dprop..
Information Server Datastage Certifiedhttp://www.infocura.be

Thanks all and the restart works and do not see any messages on db2diag.log. By the way how should I make sure archiving are happening into TSM without depend on DB2diag.log. In other words how can I prove the issue has resolved.

we use the db2diag command to find messages from last hour that have the text archive in it and ship mail whenever we found this message

Best Regards, Guy Przytula
Database Software Consultant
Good DBAs are not formed in a week or a month. They are created little by little, day by day. Protracted and patient effort is needed to develop good DBAs.
Spoon feeding : To treat (another) in a way that discourages independent thought or action, as by overindulgence.
DB2 UDB LUW Certified V7-V8-V9-V9.7-V10.1-V10.5 DB Admin - Advanced DBA -Dprop..
Information Server Datastage Certifiedhttp://www.infocura.be

Thanks all and the restart works and do not see any messages on db2diag.log. By the way how should I make sure archiving are happening into TSM without depend on DB2diag.log. In other words how can I prove the issue has resolved.

Hi,

You can check if LOG files are going into TSM with this command :
db2adutl query logs

I appreciate this is fixed now. I just wanted to add that when we got a RC 11 and archive logs failing (and backup failing as well) it was because the db2 instance owner could not write to the dsierror.log. (AIX server)

There are two db2 instances on the server and only one of them could write to the log file as it was in it's home directory. In the end we put this line in dsm.sys: