DSXchange

What would need to happen if you ran out of data files and you hadn't seen this control file yet? Keep looping and doing nothing, assuming that more files will be coming? If so, that's going to severely complicate the job design for you. Why not wait for the control file to arrive using the Wait For...

It usually means you didn't source the dsenv file. Can you show us the actual command you ran to do that?

What's different about the target table in QA? Regardless, see if an exact search for "Unable to insert a record into the table" helps.

Excellent. Please mark your post as Resolved using the button at the top of the page.

An exact search for "only top-level fields are accepted" found 7 other posts that mention that phrase.

Run the job on one node to simplify things and then use a constraint like:
p_RowCountLimit would be a Job Parameter.

Why not just stop writing to the file when the count passes a certain limit? A constraint would do that for you and you could use a job parameter for the actual limit.

You end a loop early simply by branching out of it past the End Loop stage. Easiest way to do that is park a Sequencer set to 'Any' right after it and branch to that based on the filename found.

As long as there are zero transformations involved in the process, yes - it's called RCP or Runtime Column Propogation. Search here or in your pdf manuals for all of the gory details.

You need to understand the data types you have available to you in Oracle: DATE: Date with 'optional' time component. TIMESTAMP: Same as DATE but time is stored to the millisecond. VARCHAR2: String. There's more to the TIMESTAMP, of course, it supports different millisecond scales and has TIMEZONE o...

It's been working today for me as well as it ever does.

Look at the table that was created and tell us what data type the target field is. That's where we have to start. If you treat it as a String in your job, Oracle will create the table with a VARCHAR2 field, which I've already noted is what you'd need to use for store time information.

They're in Appendix B of the Parallel Job Developer Guide pdf.

Dang, too slow.

Once again I must ask what your target field's data type is. While an Oracle DATE field supports an 'optional' time portion, the date itself is not optional and must be a valid date.

If all you truly want to store is a time, you'll need a VARCHAR2 field for that.

Of course. The StringToDate() function takes the format of the incoming string so just get that right and convert any valid date.