• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

TSM 5.5.7 Defrag procedure not working

travelsick

ADSM.ORG Member
Joined
Oct 27, 2010
Messages
66
Reaction score
3
Points
0
So here I am, trying to export a 5.5.7 tsm server to 6.4. Unfortunately, my TSM db is 99.96% fragmented and 520 GB in size. I can't reduce it b/c of the fragmentation, and the exports are excruciatingly slow. So let's bite the bullet and defrag this puppy for a faster export to the 6.x environment. Or so that's the theory.

I've backed up my DB, volhist, devconfig, everything....
I've halted and unloaded the db to a devconfig defined devclass. The new file is a svelt 150 GB. :)
On the subsequent loadformat, I get an "Error opening file '/tsm/log01/tivoli3/log01', errno = 2"

bash-3.00# /opt/tivoli/tsm/server/bin/dsmserv -o /tsm/config/tivoli3/dsmserv.opt loadformat 1 file:/tsm/config/tivoli3/loadflogs.vols2 6 file:/tsm/config/tivoli3/loadfdb.vols2

ANR0900I Processing options file /tsm/config/tivoli3/dsmserv.opt.

Tivoli Storage Manager for Solaris SPARC
Version 5, Release 5, Level 7.0

Licensed Materials - Property of IBM

(C) Copyright IBM Corporation 1990, 2009.
All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.

ANR7800I DSMSERV generated at 13:34:57 on Jan 28 2013.
ANR7801I Subsystem process ID is 29976.
ANR4726I The ICC support module has been loaded.
Error opening file '/tsm/log01/tivoli3/log01', errno = 2

I'm not finding anything useful for this error. Any thoughts/ideas?
Is this a permissions issue? I'm sudo su - into root when running the dsmserv loadformat.
I tried this after deleting the original log/dbvols (after the unload) b/c the loadformat should create new files.
I've also tried this after dsmfmt to reallocated the space for the log/db vols. Same error.
 

marclant

ADSM.ORG Moderator
Joined
Jun 16, 2006
Messages
3,619
Reaction score
580
Points
0
Location
Canada
Website
www-947.ibm.com
Error 2 means "ENOENT No such file or directory" source: http://www.ioplex.com/~miallen/errcmp.html

Did you format the volumes listed in the list of log file and list of database files using DSMFMT prior to issuing loadformat? Are the filenames in your list identical to those used with DSMFMT?
Also, the volumes in the file lists should be fully qualified paths and enclosed in double-quotes.
source: https://ibm.biz/BdR6fz
 
Last edited:

travelsick

ADSM.ORG Member
Joined
Oct 27, 2010
Messages
66
Reaction score
3
Points
0
Thanks for the quick response and the link - I'll admit that I'm not a Linux admin. But yes sir, they do exist. I even opened up their permissions and got the same error.

bash-3.00# ls -ls /tsm/log01/tivoli3/
total 18892944
2099216 -rwxrwxrwx 1 root root 1074790400 May 27 09:36 log01
2099216 -rwxrwxrwx 1 root root 1074790400 May 27 09:36 log02
2099216 -rwxrwxrwx 1 root root 1074790400 May 27 09:37 log03
2099216 -rwxrwxrwx 1 root root 1074790400 May 27 09:37 log04
2099216 -rwxrwxrwx 1 root root 1074790400 May 27 09:38 log05
2099216 -rwxrwxrwx 1 root root 1074790400 May 27 09:38 log06
2099216 -rwxrwxrwx 1 root root 1074790400 May 27 09:38 log07
2099216 -rwxrwxrwx 1 root root 1074790400 May 27 09:39 log08
2099216 -rwxrwxrwx 1 root root 1074790400 May 27 09:39 log09
bash-3.00# ls -ls /tsm/db01/tivoli3/
total 1112289956
0 -rwxrwxrwx 1 root root 0 Mar 31 11:17 adsmserv.lock
209717376 -rwxrwxrwx 1 root root 107375230976 May 27 09:52 db01
209717376 -rwxrwxrwx 1 root root 107375230976 May 27 10:03 db02
209717376 -rwxrwxrwx 1 root root 107375230976 May 27 10:15 db03
209717376 -rwxrwxrwx 1 root root 107375230976 May 27 10:29 db04
209717376 -rwxrwxrwx 1 root root 107375230976 May 27 10:44 db05
63703072 -rwxrwxrwx 1 root root 32615956480 May 27 11:05 db06
2 -rwxrwxrwx 1 root root 480 Mar 31 12:53 dsmserv.dsk
2 -rwxrwxrwx 1 root root 480 Mar 31 12:53 dsmserv.dsk.copy

Note: I plan on reducing the multiple logvols to just 1 larger vol once I get the thing loaded. I'm new to this company and they have a lot of unusual issues, like the split logvols.

Content of the loadformat input files: loadflogs.vols2 and loadfdb.vols2
'/tsm/log01/tivoli3/log01' 1024
'/tsm/log01/tivoli3/log02' 1024
'/tsm/log01/tivoli3/log03' 1024
'/tsm/log01/tivoli3/log04' 1024
'/tsm/log01/tivoli3/log05' 1024
'/tsm/log01/tivoli3/log06' 1024
'/tsm/log01/tivoli3/log07' 1024
'/tsm/log01/tivoli3/log08' 1024
'/tsm/log01/tivoli3/log09' 1024
Create a file: loadfdb.vols with the following 10 lines:
'/tsm/db01/tivoli3/db01' 102400
'/tsm/db01/tivoli3/db02' 102400
'/tsm/db01/tivoli3/db03' 102400
'/tsm/db01/tivoli3/db04' 102400
'/tsm/db01/tivoli3/db05' 102400
'/tsm/db01/tivoli3/db06' 31104
 

marclant

ADSM.ORG Moderator
Joined
Jun 16, 2006
Messages
3,619
Reaction score
580
Points
0
Location
Canada
Website
www-947.ibm.com
Ok, 2 things.

First, I see 9 log files, but "1" is specified in the loadformat command: "
The number of names must match the number specified by the number_of_log_files parameter.
source: https://ibm.biz/BdR6fz

Second, the 2 input files should not include the size, just the name. You specify the size when you format them using DSMSMT, the list is just that, a list of the files.
 

travelsick

ADSM.ORG Member
Joined
Oct 27, 2010
Messages
66
Reaction score
3
Points
0
Yes, the "1" was a mistake. I reran with the "9" and got the exact same results. The input files.... THAT seems to be the ticket! The recover log format has already finished all 9 small volumes, and now the long wait as it formats the database. Thanks a ton, marclant!!! I feel like a fool, but am glad to know it was a simple mistake easily corrected.
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 18 18.2%
  • Keep using TSM for Spectrum Protect.

    Votes: 61 61.6%
  • Let's be formal and just say Spectrum Protect

    Votes: 12 12.1%
  • Other (please comement)

    Votes: 8 8.1%

Forum statistics

Threads
31,755
Messages
135,382
Members
21,748
Latest member
fabiont
Top