This will tell you what "repair" is likely to be effected. It should show you that the entry will be removed from UV_SCHEMA (and a whole lot of other entries from UV_TABLES, UV_COLUMNS and so on). If this seems right, run the same command with the FIX keyword appended.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Ahhh- I realized that after I posted but had to run off to do some work!!!! Thanks for the correction and explanation; I also want to caution against doing anything with the UV_SCHEMA file as it is possible to completely ruin an installation by messing up this file.
same general topic as before - you've got a messed up system; playing with the UV_SCHEMA file might concievably ruin your whole installation, not just one project. You may issue a "DROP SCHEMA {schemaname};" command at TCL. I would prefer that you created an entry in UV.ACCOUNT that points to an empty directory, then use the ADMINistrator tool to delete the (dummy) Project2 from the system in order to ensure that all refernces are removed. BTW, messing up your UV_SCHEMA file might irrevocably ruin you current install, even restoring the UV_SCHEMA from a backup might not work (I've had that happen to me before).
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 well.
The atempt to create an entry in UV.ACCOUNT and droping from Adminstrator client doesnt works, since there is not directry in unix, it throws out error.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
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.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
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'
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Delete the directory and all its contents. Make sure that its parent directory still exists.
Delete the entry from UV.ACCOUNT.
Delete the entry from UV_SCHEMA using VERIFY.SQL with the pathname (not the name) of the schema.
Create new project using Administrator client.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.