We are working on Parallel extender on 8.1 on the AIX environment.
We are using ODBC enterprise stage to read and load data into MS SQL Sever 2005 tables.
How do we set commit intervals in this stage?
We will want commit to happen only after the entire load is complete. Incase the job fails due to various reasons, no record should get committed to the target table.
I am sure there must be a way out and requesting experts to help us out.
Thanks in advance
Commit intervals in ODBC enterprise stage
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 21
- Joined: Wed Jun 30, 2004 3:48 am
Commit intervals in ODBC enterprise stage
Thanks,
Anitha
Anitha
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Like so many other things in the parallel execution environment it's managed through environment variables rather than through stage properties. It's probably a good idea to add the environment to the job, or to a parameter set that the job includes.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 21
- Joined: Wed Jun 30, 2004 3:48 am
Thank you. Can you please help with pointers on the environment variables that have to be set for this one.ray.wurlod wrote:Like so many other things in the parallel execution environment it's managed through environment variables rather than through stage properties. It's probably a good idea to add the environment to th ...
Thanks,
Anitha
Anitha
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 21
- Joined: Wed Jun 30, 2004 3:48 am
Is there anyway i seta value to this environment variable such that the commit happens only after the job completes?
I have been trying to check for this but have been getting to see that
if APT_RDBMS_COMMIT_ROWS is set to 0, a negative number, or
an invalid value, a warning is issued and each partition commits only
once after the last insertion. But I am wanting to set such that the database gets committed only after the job is complete.
I have been trying to check for this but have been getting to see that
if APT_RDBMS_COMMIT_ROWS is set to 0, a negative number, or
an invalid value, a warning is issued and each partition commits only
once after the last insertion. But I am wanting to set such that the database gets committed only after the job is complete.
Thanks,
Anitha
Anitha
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The separate processing nodes are separate. The only way you can accomplish what you are doing is to run on one node only. Unless, of course, you can figure out a way to wrap the entire DataStage job in a single transaction.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.