Page 1 of 1

The directory you are connecting to either is not UV Account

Posted: Fri Oct 22, 2010 9:27 pm
by srireddypunuru
Hi ,
I'm getting the following error while connecting to one of the project
Failed to connect to DataStage server: BHD2IIS001.BHDEV1.IBM.COM, project: BHDEVCN1
( The directory you are connecting to either is not a UV account or does not exist (39125))
i searched the forums about this error . and i executed the below command form the "/opt/IBM/InformationServer/Server/DSEngine/bin# dssh LOGTO BHDEVCN1"
and nothing got the output from the command . i restart the server also. but i'm getting the same error.In the same server we have one more project , i'm able to login to the second project sucessfully. we dont have the back up the project. could you please help me on resolving this issue..

Posted: Fri Oct 22, 2010 9:35 pm
by chulett
The key question is where are you running this command from? You need to do so from the main project directory for the project you want to initially connect to.

Posted: Fri Oct 22, 2010 9:43 pm
by srireddypunuru
I ran the command from the main project directory and got the following below error.

bhd2iis001:/opt/IBM/InformationServer/Server/Projects/BHDEVCN1# /opt/IBM/InformationServer/Server/DSEngine/bin/dssh LOGTO BHDEVCN1
WARNING: Internal file corruption detected during file open!
File must be repaired, possible truncation.
hsize: 1024
bsize: 278441472
fsize: 533443
WARNING: Internal file corruption detected during file open!
File must be repaired, possible truncation.
hsize: 1024
bsize: 278441472
fsize: 533443

Posted: Sat Oct 23, 2010 1:16 am
by ray.wurlod
You will not be able to get in to this project until the corruption is repaired. Unfortunately we have no information about which file it is. Based on the size and the message I'm going to guess that it's the VOC file.

While attached to that directory, execute the following command to determine whether this is an accurate assessment.

Code: Select all

/opt/IBM/InformationServer/Server/DSEngine/bin/fixtool -file VOC

Posted: Sat Oct 23, 2010 6:10 am
by srireddypunuru
Hi Ray,
I executed the command you mentioned above.. your right it is problem with VOC file . and i got the below Error

WARNING: Internal file corruption detected during file open!
File must be repaired, possible truncation.
hsize: 1024
bsize: 278441472
fsize: 533443
Filename: VOC

Start Diagnostics.
0 Errors found in physical structure.
WARNING: Internal file corruption detected during file open!
File must be repaired, possible truncation.
hsize: 1024
bsize: 278441472
fsize: 533443
1 Errors found in file header.

An error has occurred when running.

Error: Group range specified is not valid

Posted: Sat Oct 23, 2010 1:15 pm
by ray.wurlod
Take a backup of VOC then try to repair it. Log in as dsadm or root.

Code: Select all

cp VOC VOC.backup

/opt/IBM/InformationServer/Server/DSEngine/bin/fixtool -file VOC -fix
If the VOC file can not be fixed by this method, delete the entire account and restore a good copy from system backup.

Posted: Sat Oct 23, 2010 8:12 pm
by srireddypunuru
Hi Ray,
I Executed the command but i got the same Error

WARNING: Internal file corruption detected during file open!
File must be repaired, possible truncation.
hsize: 1024
bsize: 278441472
fsize: 533443
Filename: VOC

Start Diagnostics.
0 Errors found in physical structure.
WARNING: Internal file corruption detected during file open!
File must be repaired, possible truncation.
hsize: 1024
bsize: 278441472
fsize: 533443
1 Errors found in file header.

An error has occurred when running.

Error: Group range specified is not valid

We dont have any system backup . is there any way to repair this file.

Posted: Sat Oct 23, 2010 8:31 pm
by chulett
So, seriously... no backups of this? Not even an export of the project? Need to reconsider that policy if that's the case.

Open a case with your official support provider and see what they can do. They should have people whom you can give access to your system (either directly or via a 'shared desktop' of some sort) who may be able to correct your issue.

Posted: Sun Oct 24, 2010 11:09 am
by ray.wurlod
You don't appear to have used the -fix option.