ADSM-L

Re: [ADSM-L] ODBC errors after upgrading to V5.3.5

2008-04-01 12:19:52
Subject: Re: [ADSM-L] ODBC errors after upgrading to V5.3.5
From: Bill Boyer <bjdboyer AT COMCAST DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 1 Apr 2008 16:17:06 +0000
Sorry but I already backed it off to the 532 version. I did several uninstalls 
and removed the data source to have AV recreate it. 
Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Andrew Raibeck <storman AT US.IBM DOT COM>

Date:         Tue, 1 Apr 2008 09:49:16 
To:ADSM-L AT VM.MARIST DOT EDU
Subject: Re: ODBC errors after upgrading to V5.3.5


Hi Bill,

FYI, there is no dependency between ODBC driver and installed TSM client.
The ODBC driver is a self-contained entity. So at least for the purposes
of ODBC, changing client levels has no effect.

I have seen this reported by several customers, but we are unable to
recreate this in the lab. In at least one case, we have seen the problem
go away if, after installing the 5.3.5 driver, a new account is created
and used to run the ODBC application (note that this is not a solution,
but does suggest it could be related to the account, and also acts as a
workaround). In all cases, we have seen a simple ODBC test application
"smoke test" the driver successfully.

If you are in a position where you can work with us to iteratively
recreate the problem as needed to diagnose, it would be great if you would
open a PMR.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 04/01/2008
07:46:58 AM:

> No we have it running at multiple sites on different levels of the
> client with no problem. I backed it off to 5320 and it now works. I
> did several installs and uninstalls of the 535 code with reboots
> with no luck. 532 is working and I will just leave it alone for now.
> Sent from my Verizon Wireless BlackBerry
>
> -----Original Message-----
> From: Howard Coles <Howard.Coles AT ARDENTHEALTH DOT COM>
>
> Date:         Tue, 1 Apr 2008 09:24:18
> To:ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: ODBC errors after upgrading to V5.3.5
>
>
> You need to update the client to match if you haven't already, otherwise
> it will not work.
> Not only that but it could very well be an Autovault problem, Autovault
> tends to be version specific.
> We ran it at one site, but didn't keep it.
>
> See Ya'
> Howard
>
>
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> > Of Bill Boyer
> > Sent: Tuesday, April 01, 2008 9:10 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: [ADSM-L] ODBC errors after upgrading to V5.3.5
> >
> > I have Autovault running on aa Windows2000 server with an old 5.1
> > client and
> > ODBC drive. I upgraded the ODBC to 5.3.5 and the thing just stopped
> > working.
> > I don't think it's an Autovault issue. Turning on the ODBC trace I see
> > the
> > error. Unfortunately this server doesn't have Excel loaded.
> >
> >
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4        SQLAllocHandle.cpp(
> > 454):
> > optProcessOptions() failed, rc = 400
> >
> >
> >
> > And looking up the 400 return code in dsmrc.h I see invalid
> > parameter/option. Is there tracing or error codes somewhere else that
> > would
> > tell me WHAT option is invalid? Here's the entire adsmodbc.trc output:
> >
> >
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4               DllMain.cpp(
> > 248):
> > --------------------------------- BEGIN TRACE
> > ---------------------------------
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4               DllMain.cpp(
> > 250):
> > Tivoli Storage Manager ODBC Driver
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4               DllMain.cpp(
> > 259):
> > Version 5.3.5.0 0312FB
> >
> >
> >
> >
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4               DllMain.cpp(
> > 260):
> > Entering DllMain() - DLL_PROCESS_ATTACH.
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4               DllMain.cpp(
> > 326):
> > Exiting DllMain(), rc = 'true'.
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4        SQLAllocHandle.cpp(
> > 245):
> > Entering SQLAllocHandle()
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4        SQLAllocHandle.cpp(
> > 276):
> > HandleType = Environment (1)
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4        SQLAllocHandle.cpp(
> > 279):
> > InputHandle  = 0x00000000
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4        SQLAllocHandle.cpp(
> > 282):
> > OutputHandle = 0x00b02704
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4        SQLAllocHandle.cpp(
> > 340):
> > Entering tsmAllocHandleEnv()
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4        SQLAllocHandle.cpp(
> > 342):
> > hEnv  = 0x00b02704
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4                Common.cpp(
> > 516):
> > Entering tsmCreateMutex()
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4                Common.cpp(
> > 532):
> > Exiting tsmCreateMutex()
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4                Common.cpp(
> > 516):
> > Entering tsmCreateMutex()
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4                Common.cpp(
> > 532):
> > Exiting tsmCreateMutex()
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4        SQLAllocHandle.cpp(
> > 454):
> > optProcessOptions() failed, rc = 400
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4                Common.cpp(
> > 615):
> > Entering tsmDestroyMutex()
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4                Common.cpp(
> > 617):
> > mutex = 0x000000e4
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4                Common.cpp(
> > 634):
> > Exiting tsmDestroyMutex()
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4                Common.cpp(
> > 615):
> > Entering tsmDestroyMutex()
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4                Common.cpp(
> > 617):
> > mutex = 0x000000e0
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4                Common.cpp(
> > 634):
> > Exiting tsmDestroyMutex()
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4        SQLAllocHandle.cpp(
> > 467):
> > Exiting tsmAllocHandleEnv()
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4        SQLAllocHandle.cpp(
> > 317):
> > *OutputHandle = 0x00000000
> >
> > Tue Apr 01 08:19:04 2008 000012a4 000012b4        SQLAllocHandle.cpp(
> > 318):
> > Exiting SQLAllocHandle()
> >
> > Tue Apr 01 08:23:42 2008 000012a4 000012b8               DllMain.cpp(
> > 290):
> > Entering DllMain() - DLL_THREAD_DETACH.
> >
> > Tue Apr 01 08:23:42 2008 000012a4 000012b8               DllMain.cpp(
> > 326):
> > Exiting DllMain(), rc = 'false'.
> >
> > Tue Apr 01 08:58:07 2008 000012a4 000012b4               DllMain.cpp(
> > 297):
> > Entering DllMain() - DLL_PROCESS_DETACH.
> >
> > Tue Apr 01 08:58:07 2008 000012a4 000012b4               DllMain.cpp(
> > 300):
> > ---------------------------------- END TRACE
> > ----------------------------------
<Prev in Thread] Current Thread [Next in Thread>