DSXchange

OK, but any reason why they shouldn't be in the dsenv file as well?

Typically that would be accomplished by sourcing your dsenv file:
And then trying the command.

mandyli wrote:I hope convert function it will not do this function.

Sure it will... write out one record, read back many. There's a FAQ posting on this technique as well.

There's a version now? Cool!

pankajp123 wrote:How it will effect if i use server routine in a sequence where job activity will run a parallel job.

There is no 'effect', that's how they are meant to be used - Server routines with any combination of Server or PX jobs.

39 characters or 39 bytes?

what is that GUI export of folder category? can u explain how to do it.. please!! thanks in Advance kamal First off, please just post your questions in the forum thread, there's no need to also send two private messages with questions. Secondly, Rich has already got you covered. This 'GUI' is the M...

Hmmm... not much to go on. Can you go to the RT_BP302 directory in your Project and post the lines around/including line 105 in the "*.TRANS1" file mentioned in your log message?

Shared Containers are reusable pieces of ETL 'code' that can be shared across jobs, and thus their Input/Output link metadata is fixed at creation time.

You don't need them for this - all you need is exclusive (and I do mean exclusive) access to the Project in question to run the command.

As long as you have an Oracle client installed on the DataStage server, then sure, you can switch the DRS stage with minimal implications. Biggest thing may be DATE issues, depending on how you've been handling them before this.

You would 'reschedule' a job in the Director if the time it ran or parameter values for the run needed to change. If you modify the parameters defined in the job, best to Unschedule and then add it back in. Doesn't sound like you modified any parameters in the Sequence, however. How are you 'deployi...

Warnings will about your job when they hit the Warning Limit for that job's run, default is 50. And there's quite a number of considerations when switching from ODBC to native OCI.

Too bad, that works for me, but then I'm using the DRS stage set to 'MSSQL Server'. Works the same for Oracle via OCI, so unsure why ODBC behaviour would be different.

Oracle won't give a warning for updates or deletes of zero records but ODBC will. Why not prequalify the action via hashed lookup, no reason to even issue an update on nothing.