DSXchange

If you have no experience with BASIC, the last thing you want to tackle is using it to 'connect to db and executing SQL statements'.

Why not just make a copy of the routine in question and see about modifying it to suit your needs? It already does most of what you want...

No clue why what you are doing would cause the errors you are seeing. I'm just curious enough to ask - why not just use an OCI stage? Or use the DRS stage set to Oracle so it sticks with the native interface? In other words, why use ODBC for this?

Try this in SQL create table abc ( a char primary key not null ) select * from abc insert into abc values('') insert into abc values(null) U will notice the difference. Just for the record, try this in Oracle and both will fail - which is why I asked about the target database... and probably why Wo...

If you want the 'first' rather than the 'last', you need to sort input on your key fields in a descending order rather than ascending. Then all you'll have in the hash when you are done are the first (lowest) values for any duplicate keys.

Doesn't matter what your limits are in the Director or Administrator when you run the job from the command line and use the -warn parameter. So, unless we are running into a bug, there must be something in your job that is overriding your command line option. You didn't answer when Ray asked "Do you...

What is your target database and what stage are you using to write to it?

Sure. Just don't try to use it.

Thanks . but i working on PX . not server . Then post in the PX forum. I didn't notice you had it marked as 'Parallel' so you got a Server answer. i other problem is job is already made so do i need to check each column or any easy way is there. Not really any 'easy' way. You don't mention what you...

Like all generated SQL, the 'where' clause is defined strictly by which fields you have marked as Keys. Are you sure you need to use Replace Existing? It is different from Update in that it does a delete and insert for each record rather than just a simple update. It would typically (only?) be used ...

Um, ok... go ahead. Since I don't see a question anywhere, let me throw out a couple of random thoughts. Use the Num() function to check for numeric. Search the forum for caveats on its use and some things that might test true for numerics when they may not be. Write a routine to do your date conver...

Simplest place is from the 'Command' window of the Administrator.

Can you let us know what, out of all of this, actually solved your problem?

That and formatting the "date" field to look like 13-JUN-05 should let it go right into oracle. Only if that is the current NLS_DATE_FORMAT for the target database. Granted, DD-MON-RR is the default out of the box, but still... I prefer a method that works regardless of the default date format. May...

Good point. The OP has already stated that his 'Rows per transaction' setting is 1 so each row is committed. However, what is your 'Array size' setting? If that's not set to 1 as well I could see your problem occurring.

Peter, there was just recently two independant threads on this very topic, one here and one at ADN.

The 'Create Hash' check-box enables the 'Options' available when doing so, one of which is deleting the hash each time the job runs.