Project Moved, but not running

Henrique · Post by **Henrique** » Fri Dec 16, 2005 5:47 am

Hi all,

Lastest weeks occours a error when a make a job on Designer, the error show follow message: "there is not enough available disk space", but there are 160GB free in filesystem.
So, I moved Project Directory from /dwpp_app/dsadm/Ascential/DataStage/Projects/DW_PPP to /dsrepsppr/dsrepsp/DW_PPP, and the errors began. When I execute a batch, jobs inside this batch doesn't execute...
I think the problem occours because at directory /dwpp_app/dsadm/Ascential/DataStage, datastage engine is installed.
Anybody can help me?

120267 · Post by **120267** » Fri Dec 16, 2005 6:26 am

Hi,
Have you tried compiling these batch jobs,If u are not able to compile then move the header files(user defined) to the Corresponding location.

Thanks,
Siva.G

Henrique · Post by **Henrique** » Fri Dec 16, 2005 7:09 am

Hi Participant, thks for feed-back...
I did, but the same errors occours...

chulett · Post by **chulett** » Fri Dec 16, 2005 8:30 am

You can't just arbitrarily move core stuff around like that.

Free up some space if you need to. Move it back.

kcbland · Post by **kcbland** » Fri Dec 16, 2005 8:31 am

You can't "move" a project. You can create a new project in a different location and import your jobs there, but you can't physically issue a "mv /fromhere/myproject /tothere/project. It screws up internal pointers inside the database. Don't ever do this again.

To fix your problem, consider moving the existing project back and hopefully everything will work again. If not, I hope you have a current export of the jobs. Create a new project where needed and import the jobs there.

Henrique · Post by **Henrique** » Fri Dec 16, 2005 10:03 am

Sorry, I think that I wasn't clear...
When errors began, I:
1. created a UNIX directory /dsrepsppr/dsrepsp/DW_PPP;
2. disconnected Datastage clients;
3. in Datastage Manager, exported project that errors occours, the export was ok;
4. in Datastage Administrator, I deleted project;
5. removed the UNIX directory of project: /dwpp_app/dsadm/Ascential/DataStage/Projects/DW_PPP
6. in Datastage Administrator, created a new Project, same name that was deleted, at directory /dsrepsppr/dsrepsp/DW_PPP;
7. in Datastage Manager, imported project.

well, the rest you know... when I execute a batch, jobs inside this batch doesn't execute...

thnks by feed-back...

kcbland · Post by **kcbland** » Fri Dec 16, 2005 10:24 am

Paste the error messages. We don't know if your jobstreams require prep work in order to run, such as persistent hash files located within the project directory, plugins to be installed, etc...

Henrique · Post by **Henrique** » Fri Dec 16, 2005 11:09 am

Hi kcbland,

when I try to create a new project, at child directory at Datastage Engine (/dwpp_app/dsadm/Ascential/DataStage/Projects/TST_DWPPP), the following errors occours: "DSR.ADMIN: There is not enough available disk space to add a project. '0' Kbytes is needed".

but if I telnet server, the filesystem has 156Gb free, look:
"raid-8#dwpp_app_array 534773760 220521212 156929928 59% /dwpp_app"

if I create a new project at another directory, Datastage don't show de error message, but after I try execute the batchs/jobs, its doesn't work...

[/url]

kcbland · Post by **kcbland** » Fri Dec 16, 2005 11:12 am

When you try to execute the jobs, what are the job error messages?

Henrique · Post by **Henrique** » Fri Dec 16, 2005 11:36 am

Datastage doen't show message errors, only show that Batch is executing but doesn't call any jobs...

kcbland · Post by **kcbland** » Fri Dec 16, 2005 11:51 am

What's in the Batch or Sequencer job logs, is anything running? Can you run a single job and see if it works? We need a lot more information. Does anything work?

ray.wurlod · Post by **ray.wurlod** » Fri Dec 16, 2005 2:45 pm

All the indexing in the Repository is hard coded with the old pathnames. Entries in the system tables (SQL Catalog) also probably haven't been fixed to point to the new locations.
As others have said, you can't just move a project like that.
Remedy the index problem with SET.INDEX commands (reindexing may work, but it's not guaranteed). Remedy the system tables' problem with VERIFY.SQL command.