David,

It looks like you are seeing APAR IC30018... which is fixed.
That was fixed quite a while ago in version 2.2.1.
You are running 2.2.0. You should obtain Data Protection
for SQL 5.2.1 and try this operation again.
You can also go to www.ibm.com and search for:
   +tdp +sql +restore +alternate
for additional hints and tips for alternate db restores.

Thanks,

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 10/04/2004
03:53:26 PM:

> I have client W2K with SQL 2000 and TSM client 4.2.1.20 and TDP
> SQL 2.2.0.0.  TSM server is 5.2.3.0 on AIX.  I have been doing FULL
> and LOG backups of this DB for sometime.  SQL DBA wants to restore
> a Productuion DB to another new DB on this SQL server.  DB is about
> 5 GB in size.
>
> I have tried several (at least) command line options and nothing
> works.
>
> tdpsql rest PwHcProd01 /into=prod_92604 /relocate=
> pwhctest01_data,pwhctest01_log /to=F:\MSSQL\data\
> prod_092604.mdf, F:\MSSQL\data\prod_092604_ldf
> /Object=20040926202103\00000928
>
> Is the one that comes closest to working.  The  dbname is
> PwHcProd01 and SQL Enterprise shows the Logical names are pwhctest01_*
> (I guess it was test and moved to Production later.
>
> The above command gives the least errors of many variations tried.
> The DB, prod_092604 does not exist, SQL should create it, right?
>
> See attachment txt file of the actual run, easier than  explaining it.
>
> The "RESTORE FILELISTONLY" it recommends to run  is not in the
> manual and I tried several ways runnignit and it doesn't work.
>
> Any suggestions, please provide VERY SPECIFIC syntax, etc. for
> how to do what we are trying.
>