DSXchange

That would be more of a conversion than a migration, IMHO, seeing as how it would involve code changes and a switch to PX jobs.

It's always an active stage that aborts, so in a Server job that pretty much means it will always be reported by the Transformer regardless of what actually causes the error. Saying your Oracle client is "9i" doesn't really tell anyone much, you really need to know the exact version which ...

Too bad the two 'Yes' votes didn't bother to post exactly what behaviour they were seeing, same or otherwise.

I thought that was something added in the 8.1 release and they were still out in the 'old' repository in 8.0.1.

No, you'd have to search for something else to find things like that. Since 'phantom' is a background process for a running job, that's all you'll find.

That -100 error code is pretty generic from what I've seen. Best to start your own thread and post your relevant details rather than jump on the end of someone else's resolved issue.

Those are hashed files, a.k.a. database tables in the repository. And 3 hours is a long time. Can you view the log for a specific invocation of the job rather than the 'base' job?

The number of nodes is an element of the config file you use with the job. One would typically have multiple configurations to choose from, add $APT_CONFIG_FILE to the job and override it to point to a one-node config.

The logs are in database tables. And how long did you wait before you decided it was hung?

Further details really depend on exactly what is meant by a 'migration project' and the tasks around that. Could be all that's needed is a dsx export on the 7 side imported into the 8 side of the house.

Unless you need the precise status of every job, I wouldn't bother to loop thru them all. Sounds like a quick "ps -ef |grep phantom| grep -v grep" could get you what you need.

Run the job on one node.

Did you copy the job or ever setup or switch to 'user-defined' sql? It stores that separately, any chance that's what you are seeing?

Sure, that's another option. If you go the 'after job' route and scan the log, make sure you check the INTERIM status to know if there has been a problem or not.

any way i am not the premium member so i can't see the full suggestion given by you... You have seen the full suggestion, all you missed were a handful of words unrelated to the actual solution so I've unmarked it. Regardless, seriously consider a premium membership, there's way too much help and u...