Db batch update problem

Question

I have a real problem with doing a batch update in SOA Suite and have tried a number of different approaches but they have all failed at some point. My requirement is really quite simple.
I have a simple table - MY_TABLE:
Columns:
PK_ID - primary key
ATTR_1 - not a primary key but selection criteria for on which to update.
ATTR_2 - value to update
In oracle the above update statement would look something like:
update MY_TABLE set ATTR_2=<some value> where ATTR_1=<some value>
However I don't want to update a single row, I want to update a number of rows at the same time based on a number of different ATTR_1 values. So my approaches so far have been:
a) use the Update functionality of the DB Adapter. The problem with this is that the DB adapater insists on updating by primary key. I do not have the primary key, I have another column for which I want to use as the criteria. So this won't work.
b) Create a two stage process whereby I retrieve the primary keys based on ATTR_1 and feed this into approach a). Problem is that now I need to do a select based on a list of ATTR_1 values. The Select feature of the DB adapter does not allow selection based on a number of attributes, just one. i.e. the SQL that it creates for you is something like SELECT VALUES FROM TABLE WHERE CRITERIA = <some value>. What you would really need is SELECT VALUES FROM TABLE WHERE CRITERIA IN <some value>, but the Select feature won't allow this.
c) This brings me on to the next approach. So I am going to try and use the DB adapter in Pure SQL mode. The SQL I define is something like:
update MY_TABLE set ATTR_2=#myValue2 where ATTR_1 in #myValue1
To get this work I have had to do some XSLT to convert my repeating element of ATTR_1 into a concatonated string e.g. ('myValue1','myValue1','myValue1'). The XSLT to do this sort of broke the XSLT GUI in SOA Suite, but it seems to work at runtime and creates the correct XML request to the DB adapter, however no rows are being updated and there is no error message either.
This simple DB update is seemingly beyond my grasp. Can anyone help?
Also I have no intention of looping through BPEL doing a single update at a time. The performance hit for a large number of records would be prohibitive.
Edited by: user10103872 on 28-Nov-2010 10:42
Edited by: user10103872 on 28-Nov-2010 10:43

Answer 1

>
I am thinking to write a procedure call to loop the sql statement "update table_A set version_no='1';"
>
Please don't do that. That will result in other complex issues and is not the solution to this problem.
When you try to do any insert, update or delete, Oracle generates UNDO (which basically has all the data to revert back the changes, in case you decide to do a rollback).
In your case, the UNDO Table space is not sized appropriately for this large update that you are trying to run. So, you need to fix that, by sizing it appropriately or by Using Auto-Extensible Table spaces.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/undo.htm#BABJCFFE