How to insert into UV.ACCOUNT

kumar_s · Post by **kumar_s** » Mon Mar 20, 2006 10:56 pm

Hi DSXians,
I mistakenly deleted an accout in UV.ACCOUNT.

May i know, the possibility to insert it back.
Note: The Project directory still exist in unix.

kumar_s · Post by **kumar_s** » Mon Mar 20, 2006 11:05 pm

That was due to wrongly used Wild Chard character. But One of the project is completely removed. But still it gives me error that 'Schema already present, If I recreate with the same name. I have deleted the account. No project directory exist in Unix.

chulett · Post by **chulett** » Mon Mar 20, 2006 11:18 pm

Kumar - search the forum for the use of the VERIFY.SQL command with the FIX option.

ray.wurlod · Post by **ray.wurlod** » Mon Mar 20, 2006 11:43 pm

No, not VERIFY.SQL (this fixes UV_SCHEMA). Yes, you can use a regular INSERT, or even a copy. Maybe ED is even better; open an existing project's record, replace the pathname and file as the name you accidentally deleted. For example, if you deleted Project2 (pathname is /usr/Ascential/DataStage/Projects/Project2) and Project1 still exists in UV.ACCOUNT.

Code: Select all

ED UV.ACCOUNT Project2
LOAD Project1
1
14
G11
R /usr/Ascential/DataStage/Projects/Project2
FILE

chulett · Post by **chulett** » Mon Mar 20, 2006 11:45 pm

Close but no cigar.

kumar_s · Post by **kumar_s** » Tue Mar 21, 2006 1:43 am

ray.wurlod wrote:No, not VERIFY.SQL (this fixes UV_SCHEMA). Yes, you can use a regular INSERT, or even a copy. Maybe ED is even better; open an existing project's record, replace the pathname and file as the name you accidentally deleted. For example, if you deleted Project2 (pathname is /usr/Ascential/DataStage/Projects/Project2) and Project1 still exists in UV.ACCOUNT.
Code: Select all
ED UV.ACCOUNT Project2
LOAD Project1
1
14
G11
R /usr/Ascential/DataStage/Projects/Project2
FILE

Superb :D
Is it like, we loaded the template of Project1 into UV.ACCOUNT for values of Project2 record.
May i know the similar Insert command, I tried but it happily gave me lot of errors.

kumar_s · Post by **kumar_s** » Tue Mar 21, 2006 2:00 am

kumar_s wrote:That was due to wrongly used Wild Chard character. But One of the project is completely removed. But still it gives me error that 'Schema already present, If I recreate with the same name. I have deleted the account. No project directory exist in Unix.

And any idea about this issue??

Code: Select all

SELECT * FROM UV.ACCOUNT WHERE @ID = {project}

gives me 0 records.
Still it doesnt allow me to create a new project.
So may I know what i need to do with UV.SCHEMA

ArndW · Post by **ArndW** » Tue Mar 21, 2006 2:02 am

Kumar, editing the UV.ACCOUNT should be sufficient. What happens if you try a "LOGTO Project2"? It sounds like your changing the values in the editor didn't quite work correctly.

kumar_s · Post by **kumar_s** » Tue Mar 21, 2006 2:05 am

ArndW wrote:Kumar, editing the UV.ACCOUNT should be sufficient. What happens if you try a "LOGTO Project2"? It sounds like your changing the values in the editor didn't quite work correctly.

{project} is not a valid account name.

Is for the one which was deleted from unix, UV.ACCOUNT but cannot be recreated with the same name.
Now if I retry from Datastge Administrator Clinet, it keeps mum.., not even a warning message.

ArndW · Post by **ArndW** » Tue Mar 21, 2006 2:13 am

This tells me that your ED UV.ACCOUNT Project2 was not done correctly; confirmed by your not finding that entry when doing your SELECT * FROM UV.ACCOUNT... statement.

What do you mean

Is for the one which was deleted from unix

- this is a different problem. I understood that you mistakenly deleted an entry from the UV.ACCOUNT file but that the project directory remained intact at UNIX level. The UV_SCHEMA entries will also be in order as long as all you did was remove a record from teh UV.ACCOUNT file.

kumar_s · Post by **kumar_s** » Tue Mar 21, 2006 2:19 am

Sorry for confusing in the same thread. I ll start a new thread.

kumar_s · Post by **kumar_s** » Tue Mar 21, 2006 3:26 am

say if this is the project folder /usr/Ascential/DataStage/Projects/Project2
All of a sudden I got lot of folder under /usr/Ascential/DataStage/Projects.
With the name of Project2_nnnn.
Nearly around 3000. It all contains Type 30. OVER.30,DATA.30 present in it.
By any change its due to the command

Code: Select all

VERIFY.SQL {project} FIX

I executed?

ray.wurlod · Post by **ray.wurlod** » Tue Mar 21, 2006 4:08 am

One should never, ever, ever run VERIFY.SQL in FIX mode without first running it without FIX to see what you are about to "fix". The syntax to repair the Catalog from the project is not what you used. This may be very difficult to recover.

The additional entries in the project directory are probably a result of rebuilding from the Catalog rather than the reverse, and the damage may not be recoverable. Do you have a backup of Project2?

If so, the cleanest method of recovery is probably to remove Project2 using the Administrator, clean up anything that needs to be cleaned up because it couldn't be deleted, then create a new Project2 before restoring its contents from backup.

kumar_s · Post by **kumar_s** » Tue Mar 21, 2006 5:25 am

Sorry, Actually I used the command as you mentioned in other post. (With the the key word SCHEMA).
May I know the Insert command used for UV.ACCOUNTS.

ray.wurlod · Post by **ray.wurlod** » Tue Mar 21, 2006 3:47 pm

The problem with UV.ACCOUNT is that you have to build the licensing string to go into the NAME column. That's why I recommended ED.

Code: Select all

INSERT INTO UV.ACCOUNT(@ID, NAME, PATH) SELECT 'Project2', NAME, '/pathname/Project2' FROM UV.ACCOUNT WHERE @ID = 'Project1';

But if you've screwed the project with an inappropriate use of VERIFY.SQL none of this will help.