DSXchange

That is the problem, even FIX option gives the same result. ** '/path/Project' is not a DataStage account. Items marked with a '**' are situations where VERIFY.SQL could not continue. But Adminsitrator client cannot create an account with the same name. Which gives the error of 'Schema already exist...

After deleting the directory, VERIFY.SQL SCHEMA 'path/project' gives
"'path/project' is not a DataStage account."

Woof...
This Black magic worked.
But License part was not update correctly, rather blank was populated.

So it is not a fixed width. Or atlease space should be padded at the last.
You can opt the methond suggested by Ray.
I guess the last column would be Char field. Make it to Varchar.

If it is a fixed width how can it be variying line feed.
Can you provide some example.

chulett wrote:Be in that directory when you launch 'dssh' - it will prompt you for the rest.

Got it.

But still the ideal compatability didnt helped. When i access from adminsitrator client, it gave out error code (30105) and Message of 'DSR_NLS (Action=14); Check Datastage is set up correctly'

How you managed to limit the rows of only 4 to the lookup at a time? How you manage to do a insert and update from the lookup? What was the condnititon for the failure? For the update and insert, use two links from transformer to a funnel. If conditon met, one should update and other should insert. ...

Illegal to INSERT into table used by subquery. Is there any thing we need to add up the query. I also treid with INSERT INTO UV.ACCOUNT(@ID, NAME, PATH) VALUES (SELECT 'Project2', NAME, '/pathname/Project2' FROM UV.ACCOUNT WHERE @ID = 'Project1'); no use. The name part has DataStage/{Version}/{Serv...

ArndW wrote:Create an empty directory in that location pointed to by the UV.ACCOUNT, then execute a 'dssh' and create an empty account using ideal compatibility.

May I know how to create an empty accout using dssh.

Sorry that I didnt noticed that it is of Server forum. Compress stages i avaiable only in PX.
BTW as Kenneth suggested, beyond the thershold of 10K should be considred to directly by skiping the DS.
If compression is the only criteria looked for, some external compression can be followed.

A project was currupted long back. All I am doing is to find a possible way to recover back, by creating a new proejct and inserting an entry into UV.ACCOUNT and copying the filestystem from the old project. But become a vain attempt. Also a understood that it may screw up the exixting projects as w...

It sounds certainly the permission issue.
Was the system and Datastage server restarted after given necessary permisson to the users?

Any stages used in datastage doesnt reduces any used in it.
But you can use compress stage initially to compress the files if required.

Could be this useful...

But Binary/Varbinary/LongVarBinary could be used.