TSM 5.5.4 (Solaris 10) to TSM 7.1.1 (SuSe Linux 11)

[lipi]

Hello everybody!.

I am migrating a TSM 5.5.4 installed on a Solaris 10 to a new machine running SLES 11 SP3 with TSM 7.1.1.

I followed all the guidelines of http://www-01.ibm.com/support/knowl...0/com.ibm.itsm.srv.upgrd.doc/t_srv_upgrd.html , except that one that says to upgrade the server at least to 5.5.6. It seems like a recommendation but not mandatory.

I started on TSM 7.1.1 the dsmupgx utility and the migration started, fine, but when it's time to load and extract the database an error ocurrs during the process.

Below are the 3 logs, the wizard log (dsmupgrx.trc), the new server log (InsertDB.out), and old server log (ExtractDB.out). The errors appears on the old server while reading the database. I'm afraid of a hardware issue but the server was working fine and I managed to do the dbbackup successfully.

Any ideas? Should I move to 5.5.7 before starting migration?

[TSM03][root@tsm03 db2]# cat /var/tivoli/tsm/dsmupgdx.trc
...
Fri Mar 06 19:13:39 CET 2015 com.tivoli.dsm.ServerConfig.ProcessMonitor.read(): File /opt/tivoli/tsm/server/bin/Extract.Out now being read.
Fri Mar 06 19:13:40 CET 2015 com.tivoli.dsm.ServerConfig.ProcessMonitor.read(): File /tsm/db/tsminst1/tsminst1/InsertDB.Out now being read.
Fri Mar 06 19:14:00 CET 2015 com.tivoli.dsm.ServerConfig.ServerDB$GenericThread.run(): exit
Fri Mar 06 19:14:00 CET 2015 com.tivoli.dsm.ServerConfig.ProcessMonitor.run(): exit
Fri Mar 06 19:14:01 CET 2015 com.tivoli.dsm.ServerConfig.ProcessMonitor.cancel(): exit
Fri Mar 06 19:14:01 CET 2015 com.tivoli.dsm.UpgradeWizard.DoInsertPanel$BoxHandler.signalEvent(): enter, event=insertDbDone, rc=499

-----------------------------------

[TSM03][root@tsm03 db2]# cat /tsm/db/tsminst1/tsminst1/InsertDB.Out
ANR1336I INSERTDB: Ready for connections from the source server. Remaining
time: 0:54:30
ANR0408I Session 1 started for server $UPGRADESOURCE$ (Solaris SPARC ) (Tcp/Ip)
for V6 Database Upgrade.
ANR1379I INSERTDB: Read 0 bytes and inserted 0 database entries in 0:00:00
(0.00 megabytes per hour).
ANR1377I Analyst authority has been revoked for administrator id 195.
ANR1337I A DBBACKUP trigger has been removed.
ANR1337I A DBSPACE trigger has been removed.
ANR9999D_1158055553 StartWorker(tbinsert.c:7869) Thread<24>: Failed to find
table definition for table DSKV0000000329.
ANR9999D Thread<24> issued message 9999 from:
ANR9999D Thread<24>  0x00000000ec8ff3 OutDiagToCons
ANR9999D Thread<24>  0x00000000ecbfe1 outDiagfExt
ANR9999D Thread<24>  0x00000000be7152 DispatchVerb
ANR9999D Thread<24>  0x00000000becf01 tbxiSendVerbToIOThread
ANR9999D Thread<24>  0x00000000d66c50 SmV6UpgradeSession
ANR9999D Thread<24>  0x00000000c47340 DoV6Upgrade
ANR9999D Thread<24>  0x00000000c53074 smExecuteSession
ANR9999D Thread<24>  0x00000000f80657 psSessionThread
ANR9999D Thread<24>  0x00000000f6c3cf StartThread
ANR9999D Thread<24>  0x007ffff7736806 *UNKNOWN*
ANR9999D Thread<24>  0x007ffff423102d *UNKNOWN*
ANR9999D_1069756970 tbxiSendVerbToIOThread(tbinsert.c:2491) Thread<24>: Failure
1131 dispatching verb.
ANR9999D Thread<24> issued message 9999 from:
ANR9999D Thread<24>  0x00000000ec8ff3 OutDiagToCons
ANR9999D Thread<24>  0x00000000ecbfe1 outDiagfExt
ANR9999D Thread<24>  0x00000000becf3c tbxiSendVerbToIOThread
ANR9999D Thread<24>  0x00000000d66c50 SmV6UpgradeSession
ANR9999D Thread<24>  0x00000000c47340 DoV6Upgrade
ANR9999D Thread<24>  0x00000000c53074 smExecuteSession
ANR9999D Thread<24>  0x00000000f80657 psSessionThread
ANR9999D Thread<24>  0x00000000f6c3cf StartThread
ANR9999D Thread<24>  0x007ffff7736806 *UNKNOWN*
ANR9999D Thread<24>  0x007ffff423102d *UNKNOWN*
ANR0409I Session 1 ended for server $UPGRADESOURCE$ (Solaris SPARC ).
ANR1816W The names of one or more files were truncated. Examine log file
truncatn.log for details.
ANR1396E INSERTDB: Process 1, database insert, has completed with errors.
ANR1397I INSERTDB: Found 62 database objects.
ANR1398I INSERTDB: Processed 62 database objects.
ANR1399I INSERTDB: Failed to process 0 database objects.
ANR1517I INSERTDB: Processed 3,586,177 database records.
ANR1518I INSERTDB: Read 159,751,620 bytes.
ANR1519I INSERTDB: Elapsed time was 0:03:23.
ANR1445I INSERTDB: Throughput was 2695.57 megabytes per hour.
ANR0369I Stopping the database manager because of a server shutdown.


-----------------------------------


root@bsctsm03 # cat /opt/tivoli/tsm/server/bin/Extract.Out
ANR4029I EXTRACTDB: Database checkpoint started.
ANR4030I EXTRACTDB: Database checkpoint completed.
ANR0610I EXTRACTDB started by ADMINISTRATOR as process 1.
ANR0408I Session 2 started for server $UPGRADETARGET$ (Linux/x86_64) (Tcp/Ip)
for V6 Database Upgrade.
ANR0408I Session 1 started for server MASTER (Linux/x86_64) (Tcp/Ip) for
library sharing.
ANR0409I Session 1 ended for server MASTER (Linux/x86_64).
ANR8920I Initialization and recovery has ended for shared library SL8500_LTO3_-
LIBRARY.
ANR0408I Session 3 started for server MASTER (Linux/x86_64) (Tcp/Ip) for
library sharing.
ANR0409I Session 3 ended for server MASTER (Linux/x86_64).
ANR8920I Initialization and recovery has ended for shared library SL8500_LTO4_-
LIBRARY.
ANR1305I Disk volume /dev/rdsk/c6t600A0B800011F35C00004BDE4639CEE4d0s6 varied
online.
ANR1305I Disk volume /dev/rdsk/c6t600A0B800011F35C00004CFD4639D45Ad0s6 varied
online.
ANR1305I Disk volume /dev/rdsk/c6t600A0B800011F36C0000D628463968E5d0s6 varied
online.
ANR1305I Disk volume /dev/rdsk/c6t600A0B800011F36C0000D67D4639CF93d0s6 varied
online.
ANR1305I Disk volume /dev/rdsk/c6t600A0B800011F36C0000D6B64639D075d0s6 varied
online.
ANR1305I Disk volume /dev/rdsk/c6t600A0B800011F35C00004C074639CFF2d0s6 varied
online.
ANR1305I Disk volume /dev/rdsk/c6t600A0B800011F35C00004D274639D548d0s6 varied
online.
ANR1305I Disk volume /dev/rdsk/c6t600A0B800011F36C0000D8484639D5B1d0s6 varied
online.
ANR1393I EXTRACTDB: Terminating output stream 1 due to error on server
$UPGRADETARGET$.
ANR0409I Session 2 ended for server $UPGRADETARGET$ (Linux/x86_64).
ANR9999D_2883269647 GetAllocInfo(tbxtract.c:4671) Thread<1>: Error 4 queuing
work element for smpPage 42118144.
ANR9999D Thread<1> issued message 9999 from:
ANR9999D Thread<1>   0x00000001017E15B0  OutDiagToCons
ANR9999D Thread<1>   0x00000001017F735C  outDiagfExt
ANR9999D Thread<1>   0x00000001008F48D0  GetAllocInfo
ANR9999D Thread<1>   0x00000001008DE40C  tbExtractRecs
ANR9999D Thread<1>   0x0000000100373824  AdmExtractDb
ANR9999D Thread<1>   0x00000001003717DC  admExtractDB
ANR9999D Thread<1>   0x0000000100071384  ExtractDB
ANR9999D Thread<1>   0x000000010006AE90  main
ANR9999D Thread<1>   0x0000000100067C9C  _start
ANR1396E EXTRACTDB: Process 1, database extract, has completed with errors.
ANR1383I EXTRACTDB: Found 8 database objects.
ANR1384I EXTRACTDB: Processed 8 database objects.
ANR1385I EXTRACTDB: Skipped 0 empty database objects.
ANR1386I EXTRACTDB: Failed to process 0 database objects.
ANR1387I EXTRACTDB: Processed 3,600,648 database records.
ANR1388I EXTRACTDB: Read 120,690 database pages.
ANR1389I EXTRACTDB: Wrote 219,108,400 bytes.
ANR1390I EXTRACTDB: Elapsed time was 0:03:22.
ANR1391I EXTRACTDB: Throughput was 3706.93 megabytes per hour.
ANR1394E EXTRACTDB: Failed to start or failed to complete successfully.

 

[moon-buddy]

On which Solaris hardware is TSM 5.5.4 running on? SPARC or X86_64?

 

[lipi]

On which Solaris hardware is TSM 5.5.4 running on? SPARC or X86_64?

It's a SPARC v9

 

[moon-buddy]

Looks like the systems are not compatible.

I am not sure that you can migrate from a SPARC based system to an INTEL based system.

 

[erwanns]

Hello,
I've never done this king of migration from AIX, HP-UX or Solaris to Linux x86_64.
Reading the doc, it seems that it can be done from SPARC (it's not specified, but as it's possible from AIX, the process knows how to deal with endianess).
Note that it's clearly stated that you must upgrade source server to 5.5.6 at least. You should give it a try.

Erwann

 

[lipi]

Hello everybody,

After some time, I managed to migrate the server.

How? -> just upgrade the server and the upgrade utilities to 5.5.7 following the instructions that are in the "5.5.4 TSM Install Guide" that points you how to install a fixpack (basically pkgrm and pkgadd).

After that, I started the wizard as the instructions says, and all went perfectly fine. I got a throughput of 6042.57 megabytes per hour, so I migrated my ~140GiB database in 23h.

One curious fact is that the wizard, at the end of the process, showed me a 405 return code. I was beginning to cry when I've found a note from IBM telling that it's a common problem...:

Tivoli Storage Manager V6.1 Upgrade wizard may show nonzero return code when action was successful.

It's a note for 6.1, but happens exactly the same on 7.1.1.

Now I have to start the new instance and test everything.


Thank you for your time.
Felip M.