Mark, Thanks for the info. Yes, I was unable to register licenses after getting the message. The 32 to 64 bit stuff is interesting because we did go from the 32 bit TSM on one machine to 64 bit on the other machine. I will be contacting IBM support to see if we can get this resolved. I'd hate to mess up my database. Jim
At 02:43 PM 10/6/2004 -0500, you wrote:
Jim,
I just had a customer do an upgrade similar to what you describe and they had the same problem. It turned out that they installed both the 32 bit and 64 bit code on the machine. This is obviously not a good thing! BTW, you will probably notice you can't register any licenses either. When I called IBM support to make sure that this could be cleaned up by just doing an uninstall and then reinstall just the correct filesets they gave me some interesting info. First of all make a DB backup if possible. Also, hopefully you have a backup of the DB from right before you migrated. There is a slight chance that the TSM DB could have gotten corrupted, that is the reason for the DB backups. Then you can simply uninstall all of the TSM filesets and reinstall just the correct ones for EITHER 32 bit OR 64 bit, refer to the README file for the exact filesets. They, also pointed out that the other way to cause this problem is to have a mismatch, again 32 vs. 64 bit, between the TSM code and the license code, so check for that as well. But, either way the answer is backup the DB (CYA) and then uninstall and reinstall. We did not experience any TSM DB corruption, but we had the server running for a very short period of time with almost no activity before we caught the problem and got it fixed.
IMHO, IBM should fix their LPP's so that you can not inadvertently install conflicting filesets!
Let us know how you make out.
-- Regards, Mark D. Rodriguez President MDR Consulting, Inc.
=============================================================================== MDR Consulting The very best in Technical Training and Consulting. IBM Advanced Business Partner SAIR Linux and GNU Authorized Center for Education IBM Certified Advanced Technical Expert, CATE AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux Red Hat Certified Engineer, RHCE ===============================================================================
Jim Sporer wrote:
We were running TSM server version 5.2.2.4 on an AIX 5.1 machine. Yesterday we moved the TSM server to a new AIX machine running AIX 5.2. We installed TSM server version 5.2.2.4 on the new machine so the only difference was we are running AIX 5.2. We restored the TSM database to the new server and that went ok. We started the server and got message "ANR9613W error loading the ./dsmlicense for licensing function: Exec format error". At that point client nodes could not perform backups because of a licensing issue, ANR0439W was the message we were getting. I did a search on the message ANR9613W at IBM.COM and one of the hits was something about using a down level C library, xlc.rte 5.0.2.1. We are using xlc.rte 6.0.0.0 on the new aix machine. I decided to move the ./dsmlicense file from the old machine to the new machine and when I restarted the TSM server it came up without the error. Has anybody seen anything like this? Jim Sporer
