Page 1 of 1

Unable to load subroutine on host (30105).

Posted: Mon May 02, 2005 8:17 am
by CMarques
DS Design is running on Windows, DS SErver on Unix.

First, I had:
Failed to connect to host: MYDSSERVER, project: MYDSPROJ01
( The directory you are connecting to either is not a UV account or does not exist (39125))

>> I tried to recover.

After that I am getting:

Error calling subroutine: DSR_PROJECT (Action=1); check DataStage is set up correctly in project MYDSPROJ01
(Unable to load subroutine on host (30105))

Posted: Mon May 02, 2005 8:22 am
by chulett
Welcome aboard. Sorry it couldn't be under better circumstances.

Please define "tried to recover"... what exactly did you do?

Posted: Mon May 02, 2005 8:23 am
by kcbland
First of all, is this a new installation?

Second, what do you mean by recover? What did you do?

Posted: Mon May 02, 2005 10:08 am
by CMarques
I have recovered using:

VERIFY.SQL SCHEMA MYDSPROJ01 FIX

at project home. Without to be an administrator of VOC (dsadm).

Posted: Mon May 02, 2005 11:22 am
by chulett
I think that, if you search the forum, you'll find that the FIX option actually removes any record of the project. :?

There were several discussions in the recent past that could be found using those keywords from what I remember, they might help with a solution to your problem.

Posted: Mon May 02, 2005 9:07 pm
by ray.wurlod
FIX can remove or create system table entries, depending on whether the schema (project) is specified by name or pathname.

:!:
Never use FIX straight away. Always run VERIFY.SQL without FIX first, so that it reports to you what it intends to do.

Posted: Tue May 03, 2005 4:19 am
by CMarques
I follow your indication and got this:

>VERIFY.SQL SCHEMA MYDSPROJ01
Checking permission.
* The VOC at '/opt/Ascential/DataStage/Projects/MYDSPROJ01' is not a schema
VOC.
* Data for the schema '' 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.