DSXchange

Luckily, I haven't had the pleasure of dealing with TIMESTAMP WITH TIMEZONE data types in Oracle, so can't really offer an advice from personal experience. You are correct in that DataStage only officially supports DATE fields, not any flavor of the true TIMESTAMP types. At least that's true for any...

And if file has a header record for the column names?

A generic link row count check for zero always works.

Do you know if this limitation is specific to the Oracle Enterprise stage? It must be as I have a couple of my peoples who loves the long user-defined sqls and I haven't run into this issue on the Server side. I just pulled one example at random and pasted it into Word for some stats: Characters: 48...

For #5, I'd suggest that you make 'dstage' everyone's primary group if at all possible.

I guess I haven't really seen this because, outside of the Dev environment anyway, a single functional id is used to compile and run all jobs. Always done it that way.

Where exactly does "Ascential make mention of it"?

Ah... I always seem to forget about the Windows angle on the Data Direct drivers. Still... don't use a routine.

Or just reboot the server.

It's more possible than you imagine.

Check the sdk Date routine called 'DateGenerticToTimestamp', perhaps just use it directly or 'adapt' the code into your own routine.

OCI is Oracle, not sure why you mentioned it. And if you don't have the client installed, you can't use the Sybase plug-in to import metadata. However, you should be able to use ODBC to import the definitions. Have you tried that?

The first post is confusing. I had no idea what the issue was you are facing and so was perfectly happy to let someone else to take a stab at it. However...

How about taking a stab at rephrasing your situation?

What is your datatype in the Sequential file stage? Use a Varchar if you don't want the reader to muck with the values.

Again, you do not want nor need to do this in a routine. That would require some low-level programming using the BCI functions Ray mentioned, the purchase of drivers to leverage and some serious tutoring. Put it out of your mind. Use the tool as it was meant to be used. Write a job to do this, the ...

rameshrr3 wrote:Now the user group comes back to me and says precision is important, and those 2 extra digits in the sum are a cause for concern.

So, precision is important and yet they want a less precise number?

As noted, round or truncate the result, whichever is appropriate for your user group.

theverma wrote:I am trying to run a Job from Command Line Interface in Administrator.

Why? That's not the place to be doing that. You need to use dsjob from the 'command line interface' provided by your operating system.