DSXchange

Are you using the wire drivers? If not, do you have an Oracle client installed on your DS server? Plus what Ray asked.

As you know, there is no UserStatus for RoutineActivity in Version 7. Because there's no need for that. It is, however, supported for the Job Activity stage. Ray's point was that if you had used a Job Activity stage to run the job in the Sequence, you could have leveraged that to automatically pass...

Why not just split the field around the dash and then let IConv/OConv translate '06' to '2006', '05' to '2005' etc? No reason to hard-code that.

In other words, continue to do it in the database.

And 'n' = what, exactly?

Called job sets USERSTATUS. Calling routine uses DSGetJobInfo with an InfoType of DSJ.USERSTATUS to retrieve it.

You can't, it's not something that either Oracle or the stage provides. You need to do it the old fashioned way, manually by checking all your 'numeric' fields and what the record in the log shows the values to be. Eyeball. Brain power. Elbow grease... all that rot.

You need to verify the actual number of records available from the view and not perhaps the base tables that make up the view. Views are typically used to constrain output based on whom the view is intended to be used by and to hide any (what could be complex) joins from other processes. Either of t...

'dump'? Trigger != data so you really can't just export from one database and import into another. I would think some manual 'translation' would be in order to get from the Oracle PL/SQL code to whatever MySQL uses for their triggers.

What does this have to do with the Site? Please repost in the correct forum.

No, that parameter is the stage name to query. And the help for DSJ.LINKROWCOUNT says " number of rows that have passed down a link so far ", (emphasis mine) so you should be able to use it in a running job. Now, I've never done that in a PX job, so can't say if there are special caveats with its us...

Doesn't the package installer need to be run by root? I seem to recall that as an issue with its continued use in the past... or has that changed lately?

Basically, if the job doesn't abort then any rows that made it into the database will be committed when the job 'closes' the stage.

Sure - as long as you don't need it in a Job Parameter, for use in a database query for example. Create a stage variable. Use a routine to capture the value and call it in the Initial Value column of the variable. That routine could simply 'cat' or 'type' the file and capture the output. It is what ...

Put any code you are curious about into a 'test' routine in the Administrator and then use the Test functionality there. You may have trouble checking for empty parameters there, so for testing sake change it to check for a recognizable string: If InputArg = 'empty' Then Call DSLogWarn... As to the ...