Page 1 of 1

Datastage jobs cannot be run/execute

Posted: Mon Apr 18, 2005 7:29 pm
by krigg5
hi all,

need some help and advise on how to resolve the below problem.

previously, we had some data migration exercise - migration from EMC to HDS disk . So, all the Datastage ETL jobs and system files being migrated from EMC disk to HDS disk.

Unfortunately, after the migration completed, we try to open and run our datastage job but it can't even being run/execute.

so we decide to shutdown and restart the datastage, but there]s some msg appear while we trying to bring down the datastage. The message appear as below:

root@dwdb01:[/sbin/init.d]#cd /sbin/init.d
root@dwdb01:[/sbin/init.d]#./uv.rc stop
DeadLock Daemon shutdown
Unable to read LOGS.DIR entry from D_UV_LOGS.
Unable to open uvdrlogd Daemon info file.
Unable to locate UVDR log directory.
Daemon stopped.
uniVerse has been brought down.
root@dwdb01:[/sbin/init.d]#

FYI, until now, we're still can't run any job at the datastage. How could we rectify and solve the problem. Please help. :?

Posted: Tue Apr 19, 2005 12:38 am
by ray.wurlod
Migrating DataStage is much more than moving things from one disk to another, just as migrating any database product is much more than moving things.

Now that you've done so, there are quite a few repairs that you will need to do. It might be worth hiring in a competent consultant. Needed repairs include:
    correcting references to Engine in hidden files in / directory
    correcting references to projects in UV.ACCOUNT
    correcting references to project schema information in SQL Catalog (VERIFY.SQL)
    correcting references to secondary indexes in Engine account (SET.INDEX)
    correcting references to secondary indexes in project accounts (SET.INDEX)
    possibly rebuilding indexes in project accounts (DS.REINDEX)
    possibly changing configuration files that contain hard-coded pathnames
    possibly changing DataStage jobs that contains pathnames
    possibly changing pathnames in uvconfig file (e.g. UVTEMP)

There are probably more; inspection would reveal them.

Posted: Tue Apr 19, 2005 1:32 am
by krigg5
ray,

thanks for your reply.

anyway, is there any possibilities for us to re-install back the datastage engine on the server again if all the repairs fail to resolve the above issue?

rgds,

Posted: Tue Apr 19, 2005 5:29 pm
by ray.wurlod
Provided everything is restored to exactly the same location (including hidden files) it should work OK.

Posted: Tue Apr 19, 2005 10:10 pm
by krigg5
ray,

need some help here. We've decided to re-install back the Datastage on the server. But before that, what should we do because the current server had the old datastage engine reside on the server.

how do we remove the current datastage engine and re-install back with new one.

please advice.

thanks.

Posted: Tue Apr 19, 2005 10:14 pm
by krigg5
ray/anyone,

any manual/guide that could help me to install Datastage on Unix because i never do any installation datastage on unix before.

kindly email me @ krigg59@gmail.com

thanking u in advance.

Posted: Wed Apr 20, 2005 4:02 am
by ray.wurlod
Read two documents, both of which you have with the software.

One is the README.

The other is the Installation and Upgrade Guide which you may have to search for on the clients CD, but it's not in any compressed file.

Between them these contain absolutely everything you need to know, including the UNIX kernel parameters that need to be changed - you need to be root (or have the UNIX Administrator's assistance) for this.