Re: Having problem generating TDP Exchange scheduler in cluster

2010-11-19 Thread Del Hoobler
Your TSM client does not need to be at the same level as your Data Protection for Exchange. It seems like you already read Chapter 6 titled "Using the Tivoli Storage Manager scheduler" in the Data Protection for Exchange User's Guide since it covers the things to pay attention to when setting up i

64-bit ODBC

2010-11-19 Thread Zoltan Forray/AC/VCU
Does anyone know if there is going to be a 64-bit ODBC driver? My SQL guy is complaining that we are down to only 1-32bit SQL server but there aren't any 64bit ODBC drivers Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor..

Having problem generating TDP Exchange scheduler in cluster

2010-11-19 Thread cc1702004
Hi, Sorry, I just copy and paste quickly the sample and made some misallignment in my sample. The clusternode command is in separate line in the dsm.opt file and the node and password is correct (I just use different name in the sample command). I have installed client scheduler and CAD service

Re: Extractdb cannot open en_US or AMENG

2010-11-19 Thread Keith Arbogast
Remco, Thank you for the suggestion, but I reran with DSMSERV_DIR set to /opt/tivoli/tsm/upgrade/bin, and got this error. Keith [tsmi...@tsminxy tsminxy]$ tail -f insert.out ANR7801I Subsystem process ID is 31708. ANR4979W Use of environment variable DSMSERV_DIR is no longer supported. ANR0900I P

Re: Extractdb cannot open en_US or AMENG

2010-11-19 Thread Remco Post
Set DSMSERV_DIR -- Gr., Remco On 19 nov. 2010, at 15:55, Keith Arbogast wrote: > I am running the extractdb step to migrate from TSM 5.5 to TSM 6.2.2.0. The > errors below were written to extract.out early in the extractdb process. > Should I stop the extractdb to fix this, or let it run?

Extractdb cannot open en_US or AMENG

2010-11-19 Thread Keith Arbogast
I am running the extractdb step to migrate from TSM 5.5 to TSM 6.2.2.0. The errors below were written to extract.out early in the extractdb process. Should I stop the extractdb to fix this, or let it run? No other messages have been written to extract.out. If I should stop, what's the best

Re: Having problem generating TDP Exchange scheduler in cluster

2010-11-19 Thread Richard Sims
If the password is accurate, then what needs to be questioned is the nodename which is the allied part of the authentication. Your original posting quoted the software message Authenticating TSM password for node SGISGEXBE01_EX but that nodename does not match what you expect. That needs to

SV: Having problem generating TDP Exchange scheduler in cluster

2010-11-19 Thread Christian Svensson
In your text did you type /password:/exchg01_ex as password with a "/exchg01_ex" and not /password:exchg01_ex Also do I recommend that you maybe start the DSMC client with the correct OPT file to verify that everything looks OK. Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: c