The worst thing happened. No-one ever made an export of projects.
"because the repository is on an instance that's part of a backup".
Fresh on the job and the project is gone : a failed cleanup.
It seems that the repository indeed contains all the jobs but i fear it is impossible to recreate them from there.
Is it ?
export from repository
Moderators: chulett, rschirm, roy
-
ray.wurlod
- Participant
- Posts: 54595
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Delete or rename everything into a new location.
Then restore your entire project from backup media into exactly its original location.
That should work (at least as at the time of the last backup, and assuming that that was done correctly, with no DataStage processes happening on the server).
Then restore your entire project from backup media into exactly its original location.
That should work (at least as at the time of the last backup, and assuming that that was done correctly, with no DataStage processes happening on the server).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Thanks for that fast reply.
I found another solution : the Administrator command DS_TOOLS, recreate indices. The project is now viewable through designer, director.
Previously only through Administrator.
Folks here didn't export projects because they always failed after a number of jobs. The reason was the were too big for datastage to handle (500+ jobs) or the job where it failed on contained double names for the links. The solution is to search and destroy that double naming and to export by category.
Thanks !
I found another solution : the Administrator command DS_TOOLS, recreate indices. The project is now viewable through designer, director.
Previously only through Administrator.
Folks here didn't export projects because they always failed after a number of jobs. The reason was the were too big for datastage to handle (500+ jobs) or the job where it failed on contained double names for the links. The solution is to search and destroy that double naming and to export by category.
Thanks !
Ike wrote:Folks here didn't export projects because they always failed after a number of jobs. The reason was the were too big for datastage to handle (500+ jobs) or the job where it failed on contained double names for the links. The solution is to search and destroy that double naming and to export by category.
Hmm... we routinely export 500+ jobs from our projects nightly, so that shouldn't be an issue. Jobs that are still open/locked can be a problem and I'm not sure what you mean by "double naming".
You can't have two things with the same name, regardless of category... unless your repository indexes are corrupted I suppose.-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
When I tried to export each of the projects, it always failed on a job.
The manager just closes on me.
When I then opened the job to get the skip option, it failed on the next en so on.
I haven't seen any double naming myself. (2 links in one job having the same name)
They say it compiled correctly but gave errors on exporting.
I'll try to restore those indexes, thanks for the hint.
That 500+ was a wild guess, in fact, each of those projects have more than 3000 jobs.
The manager just closes on me.
When I then opened the job to get the skip option, it failed on the next en so on.
I haven't seen any double naming myself. (2 links in one job having the same name)
They say it compiled correctly but gave errors on exporting.
I'll try to restore those indexes, thanks for the hint.
That 500+ was a wild guess, in fact, each of those projects have more than 3000 jobs.