Dynamic RDBMS stage not remembering User-defined SQL option

crsimms · Post by **crsimms** » Wed Jun 07, 2006 2:41 pm

Hello,

I am attempting to use the Dynamic RDBMS stage within a DataStage server 7.5.1 job, but an odd thing is happening. I want to use the User-defined SQL Update Action and the stage does allow me to select it. However, after I press the OK button and then open the stage back up, the Update Action has been reset to Insert new rows only. I can say that I have never run into this problem before and nothing that I do seems to remedy the problem. One thing to note is that the stage will remember Update Actions up to and including the Insert new rows option and that the stage is being used after a transformer.

Any help is appreciated,

Chris

DSguru2B · Post by **DSguru2B** » Wed Jun 07, 2006 2:58 pm

what do you mean by "does not allow me to select it"
You mean once you hit ok after typing in your sql and then you reopen it, your sql is gone?
I had this problem with the udb stage with user defined sql, i did not find a definite remedy for it. My work around was to type in the sql, copy it, hit some other tab, come back to the user define sql again and if it was gone, paste it again. It would always stay after the second time. Try doing that, or contact Ascential. This very much smells like a bug to me.
Regards,

crsimms · Post by **crsimms** » Wed Jun 07, 2006 3:16 pm

Chuck,

What I mean by not being able to select it is that while I can choose the option, the DataStage client will not remember this selection. When the stage is reopened, the Insert new rows only Update action is defined.

Regards,

Chris

jdmiceli · Post by **jdmiceli** » Wed Jun 07, 2006 4:50 pm

I have this same issue, but have also noticed that it never actually inserts any data into the target table. It shows it processed X number of rows, but no rows exist in the table upon completion of the job. My basic setup is DS Server 7.5.1, SQL Server 2000 to SQL Server 2000, RDBMS stage at both ends. The job is braindead simple:

Source table --> Transform (no manipulation of data) --> Target table

Is this normal for the RDBMS control?

Thanks!

chulett · Post by **chulett** » Wed Jun 07, 2006 5:39 pm

Well... processed X rows just means they were sent to the target database, it doesn't mean any were actually 'accepted' by it.

What does your job's log show? Warnings up the Wazoo?

What happens if you hang a reject link off the transformer?