DSXchange

No, as Arnd noted you need a different version of DataStage to actually run PX jobs on Windows. 7.5x2 - yes, with an 'x'. Or an 8 release.

You marked your post as 'Windows' meaning a Windows server installation. If indeed you are on UNIX, then yes - your scheduling user will need access to both "cron" and "at" (assuming both repeating and one-time schedules are needed) and you'll need to talk to a SysAdmin to arrange inclusion in both ...

As noted, most solutions to this problem involve your DBA.

http://www.cryer.co.uk/brian/oracle/ORA01555.htm

My two shiny pennies worth - You are much (much) better off taking the 'scripted sqlplus' approach that futzing with BCI. If you haven't already, create a generic sqlplus script to run any sql you need and then check the results for errors. Once it's made bullet-proof you can instantly leverage any ...

Please post all of the error messages from your job's log. Don't mask / change the names of the columns so we can see everything, including the log record with all of the individual field values it attempted to insert. What is the data type for the problem field in both Oracle and DataStage? Are you...

In any database? No. And can you guarantee that if your CHAR(2) field isn't 'XX' or 'YY' that there's always a valid number there?

ray.wurlod wrote:for example "update then insert" means "try an update and, if that fails because the record doesn't exist, then insert the record".

Fixed that for yah.

Did you search for "century pivot"? That is what tells DataStage when to switch the century from 1900 to 2000, i.e. what year to 'pivot' the century change around.

np. Just make sure you recognize the potential problem with this approach - can you guarantee your job will always complete in less than an hour? If not, then any overlapping schedule will fail to start. Also note that, unless we are talking about a restartable sequence job here, that a failed job w...

From Director:

1. Select job
2. Add to Schedule (right-click or clock icon)
3. Select the 'Every' radio button
4. Make sure Monday thru Friday are highlighted
5. Set time to 9:00 AM
6. Click OK
7. Set parameters
8. Click Schedule

Repeat for 10AM, 11AM, etc etc up to 6PM.

Again, no. Your 'requirement' makes no sense, push back on it. Load it using the DB2 stage... or perhaps ODBC but certainly not with the Oracle stage.

The 'Add to Schedule' reference was for DataStage Director if you are allowed to use it. Or just do the same for AutoSys, schedule the job to run once per hour during your window.

No, you don't. Perhaps you have a requirement to combine DB2 and Oracle data in a job, but you're not going to be connecting to DB2 from the Oracle Enterprise stage.

'Add to Schedule' once per hour during those times. Or build job control that runs the job in a loop and sleeps until the hour arrives, exiting after the 6PM run.

Use a hex editor to determine what the "square" character actully is, many are free out there in the inter-tubes. I don't have any way to get examples of this output myself, it would probably help if you posted a sample of the ouput you are trying to consume.