DSXchange

What if you provide an alias name in source.

like

Selecting and deleting from same table will not cause locks unless you lock with 'FOR UPDATE'.

It may result in blowing your temp, rollback or redo spaces (depending on version and action in Oracle).

Create a property (similar to parameters) and use it in your code.

When you use the build-op in your job, you will be able to pass the value as you do for any normal stage.

Create a property (similar to parameters) and use it in your code.

When you use the build-op in your job, you will be able to pass the value as you do for any normal stage.

Oops!! I was working in PX.

Server edition does ignore it.

Craig,

Try running following SQL query in DataStage (Oracle Stage)

SELECT
dummy
-- #SomeThing
FROM
-- #SomeOtherThing
DUAL

This will fail.

Comments are ignored in the db. Not in DS.

Why are we in times before sequencers were introduced ?

Can you Ctrl-V you update SQL here ?

Does not matter. DS will still parse and give the error.

Did you check the event log in server?

Did you check the event log in server?

DataStage does its own parsing of parameters before sending to the db.

So your query will be parsed incorrectly.

If you see the SQL in error message, you can see what is sent.

DataStage does its own parsing of parameters before sending to the db.

So your query will be parsed incorrectly.

If you see the SQL in error message, you can see what is sent.

As you are in Windows, you can check your event log viewer to see any warning / fatal messages during that time.

Could it be a 2Gb+ problem?

What if you remove the transform and make it a
'hashed file -> seq file' job?