Now, I guess that means with 6.1.3.3 installed since 2010, I can't see the light even going to 6.2 or 6.3 with tablespace in db2 9.5 format. A fellow DBA suggested that if the 6.1.3.3 database was really migrated to 6.2 db2 9.7 , tablespace could be converted to 9.7 format. Do I really want to go into that ??? No, I am seriously thinking about starting a brand new TSM server with 6.3 and let 6.1 die... Thanks for all this info.
Pierre Billaudeau Analyste en stockage Livraison des Infrastructures Serveurs Société des Alcools du Québec 514-254-6000 x 6559 -----Message d'origine----- De : ADSM: Dist Stor Manager [mailto:[email protected]] De la part de Zoltan Forray/AC/VCU Envoyé : 28 février 2012 09:39 À : [email protected] Objet : Re: [ADSM-L] Deployment Engine Failed to initialize WOW - such harsh words about 6.1 ! I don't agree......my main production 6.x system is 6.1.5.10 with no issues. At least it hasn't had this wacky, problem my other 6.2.x servers have had with a DB backup randomly, intermittently failing with no discernible reason....(note, there are docs that say you really need to be at least at 6.1.4.1 to resolve some big problems, especially with reorgs) Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services [email protected] - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html From: "Prather, Wanda" <[email protected]> To: [email protected] Date: 02/28/2012 05:57 AM Subject: Re: [ADSM-L] Deployment Engine Failed to initialize Sent by: "ADSM: Dist Stor Manager" <[email protected]> What Remco said. Nothing Good will Happen on 6.1. I finally got a production system stable on 6.1.3 by disabling reorgs, but that was Windows. I wouldn't even think of doing it on Linux. W -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Remco Post Sent: Monday, February 27, 2012 5:10 PM To: [email protected] Subject: Re: [ADSM-L] Deployment Engine Failed to initialize Hi, do not use TSM server 6.1, not even if you have no other options. 6.1 does not even begin to approach alpha quality software. IBM should never have shipped it. I can't think of a single good reason to install 6.1. Go with 6.2.3 or newer or 6.3 something. On 27 feb. 2012, at 22:57, George Huebschman wrote: > We are getting the "Deployment Engine Failed to Initialize" when > running ./install.bin for TSM Server 6.1 on a clean new RHEL server. > I see lots of noise out here about this error, in and out of the TSM world. > > (We have another TSM installation of TSM 6.3 on a VM that isn't even > QA as such, just a practice install.) Documetation specifies that > there be 2GB available in the home directory. > We only have 1.6 GB, BUT so does the successful 6.3 install. > We had the error on the first and subsequent 3 attempts to run the > install. We did not find any .lock or .lck files. > I am told that SELINUX is set to permissive. > > Except for the home directory, the other space guidelines were met. > The install is being done as root. > > Looking at the TSM related posts about this issue, I didn't notice any > for releases after 6.1. > Is that because I didn't look hard enough? Or, was documentation > improved, or was a bug fixed? > Should I talk someone into 6.2 to get past this? > > Most of my experience has been with 5.* I have read the install guide > (most of it) for 6.2, which is what I thought we were installing. Do > I need to step back in documentation? > > > -- > George Huebschman > > "When you have a choice, spend money where you would prefer to work if > you had NO choice." -- Met vriendelijke groeten/Kind Regards, Remco Post [email protected] +31 6 248 21 622 ------------------ Information confidentielle : Le présent message, ainsi que tout fichier qui y est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; il est de nature confidentielle et peut constituer une information privilégiée. Nous avertissons toute personne autre que le destinataire prévu que tout examen, réacheminement, impression, copie, distribution ou autre utilisation de ce message et de tout fichier qui y est joint est strictement interdit. Si vous n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de courriel et supprimer ce message et tout document joint de votre système. Merci.
