> The select @@servername returned lowercase pc1162. The DBA had some
> difficulty changing it to uppercase due to replication subscriptions or
some
> such, but after he did up date it, it now works. Does this mean that TDP
> SQL cannot handle mixed case server names? (That last question is jus
interest - we are no longer stopped.)
Thanks Del.
Allan.
-Original Message-
From: Del Hoobler [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 14, 2002 1:34 PM
To: [EMAIL PROTECTED]
Subject: Re: tdpsqlc query error: ACO0261I
Allan,
I think the casing is the problem. I am wondering
how
Allan,
I think the casing is the problem. I am wondering
how the filespace was created with the lowercase...
I believe this is obtained from SQL.
>From the SQL QA, can you issue:
select @@servername
to see what it returns?
If it shows lower case, try adding the name
back in in upper case w
TECTED]
Subject: Re: tdpsqlc query error: ACO0261I
> Our DBAs are getting the following error when issuing "tdpsqlc query
> tsm pubs" using the TDP SQL 2.2.0.01 CLI:
>
> ACO0261I There are no backups for the server named PC1162\meta\.
>
> client is TDP SQL 2.2.0.01 with
> Our DBAs are getting the following error when issuing "tdpsqlc query tsm
> pubs" using the TDP SQL 2.2.0.01 CLI:
>
> ACO0261I There are no backups for the server named PC1162\meta\.
>
> client is TDP SQL 2.2.0.01 with SQL 7 running on Windows 2000 Pro
> server is TSM 4.1.3.0 on NT 4.0
>
> An
Our DBAs are getting the following error when issuing "tdpsqlc query tsm
pubs" using the TDP SQL 2.2.0.01 CLI:
ACO0261I There are no backups for the server named PC1162\meta\.
client is TDP SQL 2.2.0.01 with SQL 7 running on Windows 2000 Pro
server is TSM 4.1.3.0 on NT 4.0
Any ideas what mi
