Page 1 of 1

How to delete a lost project in DS7.5

Posted: Sat Sep 25, 2010 3:34 pm
by bcarlson
We had many project directories get deleted recently. Now, we are unable to rebuild some projects. The project directories are gone, but when we try to recreate them in Administrator, we get an error:
DSR.ADMIN: An account called 'carlb04' already exists.
How do we delete a project we cannot see?

Brad.

Posted: Sat Sep 25, 2010 3:35 pm
by bcarlson
By the way, the project shows up in the list of projects in Administrator. If I try to click on it, I get this:
Failed to connect to host: edwdev2.wellsfargo.com, project: carlb04
( The directory you are connecting to either is not a UV account or does not exist (39125))
Brad.

Posted: Sat Sep 25, 2010 5:32 pm
by chulett
Hmmm... I believe that you'll need to leverage the VERIFY.SQL thingamajiggy. Do an exact search for it and take a peek thru the matched posts it brings up.

Posted: Sun Sep 26, 2010 2:47 am
by ray.wurlod
Search for UV_SCHEMA and UV.ACCOUNT too. One of those three will find a solution for you.

Posted: Sun Sep 26, 2010 3:46 pm
by bcarlson
Okay, found a topic that points me in the right direction - project removed outside DataStaage.

To delete the account, I did this - note, the project name is carlb04

Code: Select all

DELETE UV.ACCOUNT carlb04;
That successfully deleted the project.

Posted: Sun Sep 26, 2010 3:50 pm
by bcarlson
Now I am trying to delete the schema.

I tried this (per the link in the previous reply):

Code: Select all

VERIFY.SQL carlb04;
And got these errors:
>VERIFY.SQL carlb04;
** Invalid VERIFY.SQL operation.

1 verify operation discontinued.

Items marked with a '!' are information messages only.
Items marked with a '*' can be fixed by using the FIX option to VERIFY.SQL.
Items marked with a '**' are situations where VERIFY.SQL could not continue.
Also, I tried to recreate the project in Administrator and am now getting this error:
DSR.ADMIN: A schema called 'carlb04' already exists. This must be dropped before the project can be created.
So obviously, the scheam is still out there. What is my next step?


Brad.

Posted: Sun Sep 26, 2010 4:23 pm
by bcarlson
Okay, had the wrong syntax (correct syntax: DataStage projects). Forgot the SCHEMA keyword and got some better info:

Code: Select all

>VERIFY.SQL SCHEMA carlb04
Checking permission.
* '/u001/dev/Ascential/DataStage/Projects/carlb04' is not a DataStage account.
* Data for the schema 'carlb04' should be deleted.

2 fixable errors found.

Items marked with a '!' are information messages only.
Items marked with a '*' can be fixed by using the FIX option to VERIFY.SQL.
Items marked with a '**' are situations where VERIFY.SQL could not continue.
Should I try the FIX or is there a way to DELETE the schema?

Brad.

Posted: Sun Sep 26, 2010 4:28 pm
by bcarlson
Never mind, did the FIX anyway (hey, it's my own project, so if I screw it up, it doesn't affect anyone else :) ). Looks like that was the right thing to do based on the results
>VERIFY.SQL SCHEMA carlb04 FIX
Checking permission.
* '/u001/dev/Ascential/DataStage/Projects/carlb04' is not a DataStage account.
* Deleting catalog data for schema 'carlb04'.
* Deleting table data for 'EXAMPLE1'.
* Deleting columns data for 'PRODUCT'.
* Deleting columns data for 'CODE'.
* Deleting columns data for 'QTY'.
* Deleting columns data for 'DATE'.
* Deleting ownership record for user 'dsadm' on table 'EXAMPLE1'.

2 errors fixed.

Items marked with a '!' are information messages only.
Items marked with a '*' have been fixed.
Items marked with a '**' are situations where VERIFY.SQL could not continue.
And hey, I was able to recreate the project, too!

Thanks all for your help!

Brad.