I am unclear as to why you want or need a CLOSE command - which I have used only with cursor processing - which doesn't apply here.
Note that even with UPSERT you can choose your commit frequency and thus process large amounts of data without running risk of rollback space problems.
Are you having problems with using the LOAD method with TRUNCATE of the table?
Hi ArndW, I checked again and Write mEthod = Load, Write Mode = Append.
I dont know but the analyst said that we dont use Upsert on updating the table.
If you are doing a standard Oracle LOAD method then there is no need for any specific cursor handling and CLOSE statement. Have you tried running the job?
We have not tried testing the job. My colleague mentioned that if our insert failed, we need to rollback the data. And commit if the insert is successful.
Since you are truncating the table, the issue of rollback on failure is moot; but DataStage will do a rollback for you. Perhaps it might be best to write this job and see if it meets your requirements, and if it doesn't you can post any questions you might have on this forum.