DSXchange

Define 'some time'? Is the job running long enough and not doing enough that an idle timeout is kicking in on the target instance? Have you gotten your DBAs involved, traced what is happening on the target side? What update action are you using? Transaction size? Array size?

What he said.

Encrypted how?

Only reason I said that was because it was already empty.

The latter.

Your 'problem' is going to be the fact that DataStage really only supports one client version at a time. So best to stick with the 8i stage, leverage the 8i client and use it to access both the 8i and 9i databases.

As noted, the suffix of the file being sent makes no difference. A 'put' or 'mput' will gladly move them along just like any other file. Find someone at your site more familiar with shell scripting and ask them for help... best to have eyes right there with you. Either that or explain what 'not goin...

Welcome aboard! :D That's not very much information to go on. There shouldn't be any issues connecting to an Oracle instance on another server, that's normal stuff. All we can tell from the error is the connection was broken - could be network issues, an idle timeout, any number of things that are n...

cocardoso wrote:I'm using DataStage version 5.2 and I didn't see any way to execute this query.

Use the Administrator... find the Project and click the 'Command' button.

sumesh.abraham wrote:DS.REINDEX ALL command can be executed now as per the procedure stated by you.

You seem to have skipped all the other parts of what little of a 'procedure as stated by me' exists in this thread. Where did I tell you to query anything?

Oh well, at least you can't make your problem any worse.

Is there any such beast around here? Other than asking Kim to host something for me again, that is.

It shows "SQL+" because it is asking for the rest of your statement... you need a semi-colon at the end of the statement to get it to actually run. You need to ensure ALL connections are closed before running the reindex command or you are wasting your time. Best to do this by shutting the DataStage...

Create a new job with a Stored Procedure stage linked to a Transformer and then a Sequential file stage. Set the Procedure type to 'Source' on the Syntax tab. Run it after the other job finishes, a Sequence job can do that easily for you unless you've got another form of job control in place. And fi...

More than likely, the repository indexes are corrupt. Do an exact search of the site for DS.REINDEX ALL for the procedure to follow.

Oddly enough, the Stored Procedure stage. What exact 7.x version of DataStage do you have?