DSXchange

That's because 'sqlplus' is an Oracle utility. Talk to your DBA, they can help you with the command and syntax you'd need.

Our requirement is to control a Job Sequence from another job(in job control). Is it possible to do it or is there any other alternative available to acheive the same. Of course there are alternatives. I, for one, would not run a Sequence job from the Job Control tab of another job. One alternative...

No can do. But if you explained your XML structure and what you are trying to do, then people may be able to explain how you could accomplish that. Examples are always good.

Yes, it is possible as long as 'Job Administration in Director' is enabled for the Project. You could always turn that off if you want to disable it for everyone.

Hmmm...

Create a new hashed file, write the records you want to keep to it and then do the delete / rename switcheroo. Or create a VOC record (if pathed) and then use SQL to delete those records.

What does this have to do with Oracle or this subject? Nothing.

Please start a new thread (Post New Topic) in the appropriate forum based on the job type. If unsure, post in the General forum.

If you've figured out something that's not here in the forums, can you please do a couple of things? First would be to mark the thread as Resolved (button at the top of the screen) and secondly post back and let us know what your solution was? It will be of service to any future searchers with the s...

Did you try searching? I got 11 hits for "scientific notation", perhaps one of those would be helpful. Either that or "exponent" should turn something up.

That's because it thinks it failed so needs to be rerun. Try using different triggers from it to the first job, I believe the Unconditional trigger is confusing it (and us). The routine had a unconditional link to Job1, and a fail trigger to a dummy sequencer. Change the "Unconditional" trigger to a...

Guys, this isn't Usenet or someplace where you need to quote entire messages when you reply so people know what's being discussed. It's all here so just use the dang 'Reply to topic' button and if needed only quote relevant snippets to clarify the points you are making. Oh, and before I forget:

Then it's done and your log is just trying to catch up. Use CLEAR.FILE from the Administator if you know the job number:


Where nnnn is the job number in question.

Job design doesn't matter. It may show a Finished status, but the process writing your bazillion warnings is still alive and kicking. Find the phantom process and kill it from your O/S.

All the activities are set to be skipped if a failure occurs. Is this your 'Do not checkpoint' comment from before? If so, you misunderstand the option. By default, completed activities are skipped on a 'Restart'. By enabling 'Do Not Checkpoint' you are saying that you always want that stage to run...

Actually, i kept them as it is initially and did the "View Data" but then i got the error saying "Attempt to convert string value '01-SEP-01' to Timestamp type unsuccessful". But i checked the source datatype in table table and it is actually a date format. Datatype is only one piece of the puzzle....

All the activities are set not be checkpointed (so that, in case of failure, next execution will start in the failed job). I set things so that job2 fails. You mean the Routine Activity stage is the only one to be not checkpointed, yes? Understand that checkpoints only work if the Sequence job abor...