Here is our solution to this problem which was the sql server name as stored
in the sql database was null. When it was set to the proper name, tdpsql
gui worked. You can get the server name by doing a sql select @@servername
On Thu, 28 Jun 2001, Bruce Kamp wrote:
> I am having the same problem with SQL 7.0 SP2. I have had this issue open
> with Tivoli support for 2-3 months now with no resolution. I did install
> SQL 7 with different character set. Version 1.1 work fines. I was never
> able to get 2.2 to work at all. So far this is the only fixtest they have
> had me try (did not work for me...):
>
> I received a response from our development team requesting that you try
> installing fixtest IC29849_01.exe for TDP for SQL v2.2. According to them,
> it fixes some character set/language problems with SQL Server and so could
> be related to the problem you are currently experiencing. I have attached
> both the readme file and fixtest for you to install. The readme will
> provides the following information regarding what APARs are fixed:
> ****************************************************************************
> ********
> The following problems are fixed in this FIXTEST:
>
> IC29849
>
> When using the TDP for SQL 2.2 GUI or command line one may have
> encountered this error:
> ACO5422E Received the following from the MS SQL server:
> SQL-DMO The name 'Unicode locale ID' was not found in the
> ConfigValues collection. If the name is a qualified name, use
> to separate various parts of the name, and try again.
> Microsoft SQL-DMO (HRESULT:0x80045510)
> The problem occurred with any SQL Server 7.0 sort order that is case
> sensitive, such as binary or dictionary order. A query SQL or any
> backup command would fail. Both the GUI and the command line would
> not work. SQL 2000 does not experience this problem.
>
> IC30018
>
> The /relocate option on the command line does not process
> logical file names that are transaction log files.
> When used with the /partial option, it would not process logical
> file names that were not members of the /groups or /files specified.
>
> -----Original Message-----
> From: Del Hoobler [mailto:hoobler AT US.IBM DOT COM]
> Sent: Thursday, June 28, 2001 6:54 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: tdpsql v2.2 gui opens then immediately closes
>
>
> Joel,
>
> Are you able to do a backup from the command line interface?
> It looks as if the communication with the SQL server is
> causing some type abnormal program termination.
> The only thing I can think of right off hand is that
> the registry containing connection information was somehow
> corrupted... but without a trace there is no way I can tell.
> To get to the bottom of this, it will require some
> traces to be gathered. Please call IBM/Tivoli support.
>
> Thanks,
>
> Del
>
> ----------------------------------------------------
>
> Del Hoobler
> IBM Corporation
> hoobler AT us.ibm DOT com
>
> "It's a beautiful day. Don't let it get away." -- Bono
>
>
>
>
> Joel Fuhrman
> <[email protected] To: ADSM-L AT VM.MARIST DOT EDU
> NGTON.EDU> cc:
> Sent by: "ADSM: Subject: tdpsql v2.2 gui
> opens then immediately closes
> Dist Stor
> Manager"
> <[email protected]
> T.EDU>
>
>
> 06/27/2001 11:17
> PM
> Please respond
> to "ADSM: Dist
> Stor Manager"
>
>
>
>
>
> tpdsql version 2.2 was working but now the gui window opens and then
> immediately closes.
>
> The tdpsql.log file show the request QUERY SQL but there is no connection
> to
> the TSM 4.1.3.0 Server running on AIX 4.3.3 ML06 and there is no entry in
> the dsierror.log file. A command line tdpsqlc QUERY SQL gets the same
> results. However, a tdpsqlc QUERY TSM * /all does list the backups.
>
> Any suggestions as to what would cause this?
>
|
