Weblogic 8.1SP4 Db2 "Abnormal end unit of work condition occurred"

I am getting the following error when calling resultSet.next()
java.sql.SQLException: [BEA][DB2 JDBC Driver][DB2]Abnormal end unit of work condition occurred.
at weblogic.jdbc.base.BaseExceptions.createException(Ljava.lang.String;Ljava.lang.String;I)Ljava.sql.SQLException;(Unknown Source)
at weblogic.jdbc.base.BaseExceptions.getException(I[Ljava.lang.String;Ljava.lang.String;I)Ljava.sql.SQLException;(Unknown Source)
        at weblogic.jdbc.db2.drda.DRDARequest.processSQLCA(Lweblogic.jdbc.base.BaseWarnings;)V(Optimized Method)
        at weblogic.jdbc.db2.drda.DRDARequest.processCodePoint(IILweblogic.jdbc.base.BaseWarnings;)Z(Optimized Method)
        at weblogic.jdbc.db2.drda.DRDAStatementRequest.processCodePoint(IILweblogic.jdbc.base.BaseWarnings;)Z(Optimized Method)
        at weblogic.jdbc.db2.drda.DRDAResultSetRequest.processCodePoint(IILweblogic.jdbc.base.BaseWarnings;)Z(Optimized Method)
        at weblogic.jdbc.db2.drda.DRDARequest.processReply(Lweblogic.jdbc.base.BaseWarnings;)V(Optimized Method)
        at weblogic.jdbc.db2.drda.DRDARequest.ensureBytes(ILweblogic.jdbc.base.BaseWarnings;)V(Optimized Method)
        at weblogic.jdbc.db2.drda.DRDARequest.processSQLCA(Lweblogic.jdbc.base.BaseWarnings;)V(Optimized Method)
        at weblogic.jdbc.db2.drda.DRDAResultSetRequest.getNextRow(Lweblogic.jdbc.base.BaseWarnings;)Z(Optimized Method)
        at weblogic.jdbc.db2.DB2ImplResultSet.fetchAtPosition(I)Z(Optimized Method)
        at weblogic.jdbc.base.BaseImplResultSet.next()Z(Optimized Method)
        at weblogic.jdbc.base.BaseResultSet.next()Z(Optimized Method)
        at weblogic.jdbc.wrapper.ResultSet_weblogic_jdbc_base_BaseResultSet.next()Z(Optimized Method)

chk this link ::
http://www.dbforums.com/db2/1635479-sql-error-911-sqlstate-40001-rollback-due-deadlock-timeout-reason-68-a.html
http://businessintelligence.ittoolbox.com/groups/technical-functional/brio-l/db2-error-from-scheduled-job-1061846
might be useful for u.ang google it.

Similar Messages

Error: Abnormal end unit of work condition occurred

I using Weblogic 8.1 sp4, Db2/NT 8.2.9, JDK 1.4,JDBC in multithreaded environment
When i issue resultset.next(), sometimes (very few times that too when number of units of processing is a bit high) it give me the following error:
java.sql.SQLException: [BEA][DB2 JDBC Driver][DB2]Abnormal end unit of work condition occurred.
at weblogic.jdbc.base.BaseExceptions.createException(Ljava.lang.String;Ljava.lang.String;I)Ljava.sql.SQLException;(Unknown Source)
at weblogic.jdbc.base.BaseExceptions.getException(I[Ljava.lang.String;Ljava.lang.String;I)Ljava.sql.SQLException;(Unknown Source)
        at weblogic.jdbc.db2.drda.DRDARequest.processSQLCA(Lweblogic.jdbc.base.BaseWarnings;)V(Optimized Method)
        at weblogic.jdbc.db2.drda.DRDARequest.processCodePoint(IILweblogic.jdbc.base.BaseWarnings;)Z(Optimized Method)
        at weblogic.jdbc.db2.drda.DRDAStatementRequest.processCodePoint(IILweblogic.jdbc.base.BaseWarnings;)Z(Optimized Method)
        at weblogic.jdbc.db2.drda.DRDAResultSetRequest.processCodePoint(IILweblogic.jdbc.base.BaseWarnings;)Z(Optimized Method)
        at weblogic.jdbc.db2.drda.DRDARequest.processReply(Lweblogic.jdbc.base.BaseWarnings;)V(Optimized Method)
        at weblogic.jdbc.db2.drda.DRDARequest.ensureBytes(ILweblogic.jdbc.base.BaseWarnings;)V(Optimized Method)
        at weblogic.jdbc.db2.drda.DRDARequest.processSQLCA(Lweblogic.jdbc.base.BaseWarnings;)V(Optimized Method)
        at weblogic.jdbc.db2.drda.DRDAResultSetRequest.getNextRow(Lweblogic.jdbc.base.BaseWarnings;)Z(Optimized Method)
        at weblogic.jdbc.db2.DB2ImplResultSet.fetchAtPosition(I)Z(Optimized Method)
        at weblogic.jdbc.base.BaseImplResultSet.next()Z(Optimized Method)
        at weblogic.jdbc.base.BaseResultSet.next()Z(Optimized Method)
        at weblogic.jdbc.wrapper.ResultSet_weblogic_jdbc_base_BaseResultSet.next()Z(Optimized Method)
Please let me know the solution to this problem..

chk this link ::
http://www.dbforums.com/db2/1635479-sql-error-911-sqlstate-40001-rollback-due-deadlock-timeout-reason-68-a.html
http://businessintelligence.ittoolbox.com/groups/technical-functional/brio-l/db2-error-from-scheduled-job-1061846
might be useful for u.ang google it.

Error when IMPORT using INDEXFILE IMP-00009: abnormal end of export file

Hi,
I met the following error while I am doing IMPORT (creating ddl using INDEXFILE option) as.
imp system/oracle@hpfw9i file='F:\C2Prop\ProdDump20051109.dmp' fromuser=FWORKSADM touser=FWORKSADM indexfile=ddlfile.sql log=st-imp.log
. . skipping table "FWDEFECTCOMPONENT_PN21"
. . skipping table "FWDEFECTCOMPONENT_PN22"
. . skipping table "FWDEFECTCOMPONENT_PN23"
. . skipping table "FWDEFECTCOMPONENT_PN24"
. . skipping table "FWDEFECTCOMPONENT_PN25"
. . skipping table "FWDEFECTCOMPONENT_PN26"
. . skipping table "FWEQPATTRIBUTE"
. . skipping table "FWEQPATTRIBUTEHISTORY"
IMP-00009: abnormal end of export file
Import terminated successfully with warnings.
Have you ever experienced the following error message when you imported the db..?
Also I could see the import was not done successfully when I compared my ddlfileold.sql which is already done using this same dump file
My actions to make ddlfile
- I have tried three times to make ddlfile but I failed all and met the same error message.
try 1 : using 9210 version
try 2 : using 9206 version
try 3 : using 9206 version at other machine.
I need your advice and help.
Thanks,
Riaz.

This means the export dump file is corrupted.
In UNIX see this command to see whether the dump file is complete
$ tail expdat.dmp
It should have EXIT in the last line.

Help Me Abt - IMP-00009: abnormal end of export file

when i try to import from dmp files the following error occured.
IMP-00009: abnormal end of export file
i don;'t know , why.
please help me.
Asif Iqbal
Software Engineer ( Karachi, Pakistan ).

Also, please make ensure you FTP the dump file in binary mode and compare the file sizes before and after the transfer.
Edited by: SKU on 12-Jan-2009 12:32

IMP-00009: abnormal end of export file

When I try to import my dump file i receive this error IMP-00009: abnormal end of export file even if my buffer is set to 2000000000.
Any help would be great.
Regards

The export file is probably from an aborted Export session. Better retry the export and then import it again, if possible.
If not possible, report this as an Import bug and submit the export file that caused this error to Oracle Support Services.
Thanks and Best Regards,
-aijaz

Import utility IMP-00009: abnormal end of export file.

IMP-00009: abnormal end of export file.
I have received a 34 GB dmp file exported using exp utility 9.2. and i am importing it into 10.2.0.1.0
1) Not sure wheher its exported from Unix or windows.. how to make out?
2)I imported using ...BIN>imp user1/pwd FILE=C:\exp.dmp
SHOW=y fromuser=user2 touser=user1 ROWS=Y IGNORE=y GRANTS=y Constraints=
y log=C:\exp.log
Note my login user and my to user are same and i have grant DBA to user1.
3)When i import, after an hour+ it terminates saying abruprt end of export file.
4)I am not aware of the command used for export whether its FULL DB or only user etc.... how to find out? from show = y i selected 1 username and used it as from user.
5)This file was sent to me through a FTP server from where i downloaded.
Plz help i need to import urgently, what should i be doing?

I also read that FULL=Y is not supported when i import 9i dmp into 10g dmp. Is it true?False
It is an export of the Backup it seems. What difference does it make if we export from DB Backup and export from DB itself?There is nothing called export of a backup.The dump is created by an oracle binary called EXPORT.
You can execute this command against an oracle database
exp username/pwd@hoststring file=c:\oracle\bk\test.dmp fully=y....and so on

Abnormal end of export file

Hi!
During an import, Oracle generates the following error:
Abnormal end of export file ...
Is any way or hint to fix the end of file ??
TIA
Angel Castro

Hi Angel
In that case passed 2 possible things:
1.- The transfer to the tape or from the tape ot disk was not in binary mode
2.- The export utility did not finish succesful the exportation when somebody was doing that activity.
Joel PÃ©rez
http://www.oracle.com/technology/experts

IMP-00009: abnormal end of export filekgepop: -Please help

Sir,
IMP-00009: abnormal end of export filekgepop: no error frame to pop to for error 21500
I am getting this error. IMP-00009 abnoramal end of export file.
Why this this is happening? What I have to do to avaoid this?
How can we avoid compilation errors for views and procedures during import?
Can any one please give a help
regards
Mathew

Sir,
The excact error is
IMP-00009: Abnormal end of export filekgepop:no error frame to pop to for error 21500
This his is the error message comming at the end od command window during the import.
Following is the end of IMPort log file
. . importing table "BRANCH" 1 rows imported
. . importing table "ERROR_DETAILS" 24 rows imported
. . importing table "INDEX_CONTENT_PROPERTIES" 43 rows imported
. . importing table "LABEL" 0 rows imported
. . importing table "LINKS" 0 rows imported
. . importing table "LOCKS" 0 rows imported
. . importing table "OBJECT" 27763 rows imported
. . importing table "PARENT_BINDING" 27643 rows imported
. . importing table "PERMISSIONS" 19 rows imported
. . importing table "PROPERTIES" 450312 rows imported
. . importing table "PUBLISH_CONTENT_PROPERTIES" 45 rows imported
. . importing table "PUBLISH_TYPES" 4 rows imported
. . importing table "URI" 27769 rows imported
. . importing table "VERSION" 27643 rows imported
. . importing table "VERSION_CONTENT"
After this the error
IMP-00009: Abnormal end of export filekgepop:no error frame to pop to for error 21500
is displayed in command window.
regards
Mathew

PMON / abnormal ended processes

Hi,
as far as I understand now, PMON will clear up the resources of an abnormal ended process, release locks, blocks of the process in the database buffer cache and so on.
I'm trying to understand how Oracle will handle processes that has ended abnormal. Assuming an SQL*Plus do a network connection and starts e.g. a long running update. During this update the terminal of SQL*Plus will be killed. Will SQL*Plus rest in the database and what will happens then? Who will remove the network connection, the process from v$session and so on. These dependencies are not clear to me.
May anyone can give me a short explanation or anyone have a good link where this is explained? I know that this will be a complex issue and can't be explained with a few words, but a short explanation could help to find the right hooks to get a deeper understanding.
Thank you in advance!
Best regards,
Alex

Hi,
pgoel wrote:
Hi, I think it is the same PMON who periodically cleans up the occupied resources by such terminated processes.yes, indeed, that will be done by PMON. But I'm trying to understand how PMON will do that work. If an abnormal ended session is in the instance, how will PMON identify it and what will it do?
Regards,
Alex

Weblogic 6.0 DB2 7.2 Solaris 8 IBM Trade2 Benchmark

Hello, I am tring to deploy the IBM Trade2 Sample Kit on Weblogic 6.0 DB2
7.2 Solaris 8, afer I follow the weblogic instructions I get a
TradeEJBs.jar, Trade.war, Theme.war, TradeSample.ear .... but I don´t know
if I have to copy all of them to
/bea/wlserver6.0sp1/config/mydomain/applications or just TradeSample.ear
If I just copy TradeSample.ear I see the application and the web application
in the administrative console but don´t know which URL I have to put in the
explorer to get the application response ... If I just copy Trade.war then
I get response from http://mydomain:7001/Trade/welcome.jsp ... but all the
relative path are to /WebSphereSample/...../classes ....
I ´ve been working a few days on it but I am still confused .... Any help??
Chuchete

CERT is a security group ...
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
Tangosol Server: Enabling enterprise application customization
"Daniel Hoppe" <[email protected]> wrote in message
news:[email protected]..
Cameron,
what is 'certs'?
Cheers,
Daniel
-----Ursprüngliche Nachricht-----
Von: Cameron Purdy [mailto:[email protected]]
Bereitgestellt: Samstag, 26. Mai 2001 05:28
Bereitgestellt in: misc
Unterhaltung: Solaris Version Recommendations for WebLogic 6.0?
Betreff: Re: Solaris Version Recommendations for WebLogic 6.0?
... just remember to check certs regularly, and if you go with an older
version, start by checking all existing advisories.
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
Tangosol Server: Enabling enterprise application customization
"Charlie Therit" <[email protected]> wrote in message
news:[email protected]..
I'm partial to Solaris 8 because of its improved VM File I/O caching
algorithm. However, all three have good diagnostic and tuningabilities
and would work well with WebLogic.
-Charlie
Daniel Hoppe wrote:
Hi,
I guess that the larger part of you is using WebLogic on the Solaris
platform. I am currently planning a migration from WinNT to Solaris
and
I would like to know if there are certain pros and cons for using
WebLogic 6.0 on either Solaris 2.6, 2.7 or on Solaris 8. From the
windows world it's quite a good assumption to go for 'newer isbetter /
more stable' but I'm not sure if I can transfer this to the Solaris
world as well.
Thanks for your input!
Daniel

Sequencing 3 sceanrios as one logical unit of work

Hi,
I have 3 business services BS1,BS2,BS3
BS1 is source database DB1 which has 2 tables DB1_table1,DB1_table2
BS2 is another source datbase DB2 which has one table DB2_table1
BS3 is target database DB3 which has 2 tables DB3_table1,DB3_table2
And the three scenarios are as below
1.Data from DB1_table1 has to be inseted into DB3_table1 -
from BS1 to BS3
2.Data from DB1_table2 hasto be inserted into DB3_table2 -
from BS1 to BS3
3.Data from DB2_table1 has to be inserted into DB3_table2 -
from BS2 to BS3
But i want all these 3 sceanrios as one logical unit of work and 1,2,3 should be in a sequence.If any one of these fails remaining processes should fail. for ex if 1 fails 2,3 should not occur.
How can i achieve this?
Thanks & Regards,
Jyothsna

Hi,
you can able to achive this using BPM.Check the below links for creating BPM scenarios..
[https://weblogs.sdn.sap.com/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken]]
[Schedule Your BPM]
[Walkthrough with BPM]
[The specified item was not found.]
[RFC Scenario using BPM --Starter Kit]
[/people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi]
[The specified item was not found.]
[One Logical System Name for serveral BPM Acknowledgements]
[Illustration of Multi-Mapping and Message Split using BPM in SAP Exchange Infrastructure]
[Posting multiple IDocs with Acknowledgement]
Regards,
Prakasu

What is luw (logical unit of work)

pls tell me what is luw (logical unit of work)
what r the types of luw .
2 what ispurpose of code inspector and extended program check
pls expalin the diffrence b/w those two
3what are the candidate keys in db tables
4 what is the difference b/w occurs 1 and occurs 2 clauses
data : begin of itab occurs 0 .
data : itab type standard table of structure type initial size 1 with header line
pls tell diffrence between theese two statements
5can u pls tell what is the client in sap
pls tell answers to questions
pls dont give any websites addresses to see answers
6 what is the transaction from database point of view
7 what is the variant in alv reports
how do we use reuse_alv_grid_variant_get fun module in alvs

hi,
this gives complete idea
SAP LUW
Since, as a rule, an application program is processed by several work processes in succession, and every change of the work process is linked with an implicit database commit , an application program is not automatically linked with a single database LUW. This applies in particular to dialog-oriented applications, in which one database LUW is assigned to one dialog step.
To ensure the data consistency of application programs that are executed across different work processes, the application statements are not directly executed in an SAP LUW, rather, are first registered and then executed by a single work process, that is, in a single database LUW.
Two techniques are available for bundling the change statements in a database LUW:
Bundling via function modules (update)
Through the statement CALL FUNCTION...IN UPDATE TASK, an update function module is registered for subsequent execution in an update work process.
Bundling via function modules (transactional RFC)
Through the statement CALL FUNCTION... IN BACKGROUND TASK DESTINATION, a remote- compatible function module is registered for subsequent asynchronous execution via the RFC interface (transactional RFC ).
Bundling via subprograms
Through the statement PERFORM ... ON COMMIT, a subprogram is registered for subsequent execution in a different work process.
Statements for SAP LUWs
A SAP LUW is controlled via the Open SQL statements COMMIT WORK, ROLLBACK WORK and SET UPDATE TASK LOCAL.
Note
A function module can be classified either as an update function module or remote-compatible, but not both at the same time. The update helps realize SAP LUWs within an SAP System, while the transactional RFC creates LUWs in distributed systems.
COMMIT WORK
Variants:
1. COMMIT WORK [AND WAIT].
2. COMMIT CONNECTION con.
Effect
Terminates an SAP LUW and stores the changes.
Variant 1
COMMIT WORK [AND WAIT].
Effect
The statement COMMIT WORK completes the current SAP LUW and opens a new one, storing all change requests for the currenta SAP LUW in the process. In this case, COMMIT WORK performs the following actions:
It executes all subroutines registered using PERFORM ON COMMIT.
It triggers an internal event in Object Services that ensures the registration of changes in persistent objects as the last update function module, as well as the subsequent initialization of persistent object attributes.
It initiates the processing of all registered update function modules in the update work process.
This executes all high-priority update function modules registered using CALL FUNCTION ... IN UPDATE TASK in the order of their registration and in a common database LUW. If you do not specify the addition AND WAIT, the program does not wait until the update work process has executed it (asynchronous updating). If you specify the addition AND WAIT, however, program processing after COMMIT WORK will not continue until the update work process has executed the high-priority update function modules (synchronous updating).
If all high-priority update function modules are completed successfully, the statement executes the low-priority update function modules together in a common database LUW.
In parallel, it also executes the individual function modules registered using CALL FUNCTION ... IN BACKGROUND TASK DESTINATION in a separate database LUW for each destination.
It handles all SAP locks set in the current program according to the value of the formal parameter _SCOPE of the corresponding lock function modules.
It triggers a database commit that also terminates the current database LUW.
The completion of statement COMMIT WORK triggers the event TRANSACTION_FINISHED of the system class CL_SYSTEM_TRANSACTION_STATE, where the parameter KIND has the value of the constant CL_SYSTEM_TRANSACTION_STATE=>COMMIT_WORK.
If the statement COMMIT WORK is executed by calling special programs, be aware of the following:
In a program executed using batch input, or if you have called the program using the USING addition of the statement CALL TRANSACTION, COMMIT WORK terminates the batch input processing when using the corresponding settings.
In a program called using CALL DIALOG, COMMIT WORK initiates the processing of subroutines or updated function modules registered using PERFORM ... ON COMMIT and CALL FUNCTION ... IN UPDATE TASK. Therefore, it does not complete the current SAP LUW. The SAP LUW cannot be completed until you execute the COMMIT WORK statement in the calling program.
You cannot execute the COMMIT WORK statement during the updating procedure or during the execution of subroutines registered using PERFORM ... ON {COMMIT|ROLLBACK}.
System fields
sy-subrc Meaning
0 You have specified the AND WAIT addition, and the updating of the update function modules was successful.
4 You have specified the AND WAIT addition, and the updating of the update function modules was not successful.
The COMMIT WORK statement always sets sy-subrc to 0 if the AND WAIT addition is not specified.
Note
The COMMIT WORK statement closes all database cursors . Open SQL statements that access a database cursor later ( SELECT loop and FETCH) raise an exception that cannot be handled.
Variant 2
COMMIT CONNECTION con.
Note
This statement is for internal use only.
It cannot be used in application programs.
Effect
The COMMIT command is not executed on the standard database, but only on the secondary database connection specified by con. con is the name of the database connection as it was specified in the table DBCON in the column CON_NAME. The database connection con can also be specified dynamically in the form (source_text) - the source_text field contains the name of the database connection. The source_text field must be of the type C or STRING.
On the specified secondary database connection, the database commit:
Closes all open database cursors (OPEN CURSOR)
Releases all database locks
Note
Note that the COMMIT CONNECTION DEFAULT statement unlike COMMIT WORK executes a pure database commit on the DEFAULT connection.
Exceptions
Non-Catchable Exceptions
Cause: COMMIT WORK is not possible in a FORM that was called using PERFORM ... ON COMMIT.
Runtime Error: COMMIT_IN_PERFORM_ON_COMMIT
Cause: COMMIT WORK is not allowed in the update.
Runtime Error: COMMIT_IN_POSTING
ROLLBACK WORK
Variants:
1. ROLLBACK WORK.
2. ROLLBACK CONNECTION con.
Effect
Terminates a SAP-LUW without storing the changes.
Variant 1
ROLLBACK WORK.
Effect
The statement ROLLBACK WORK closes the current SAP-LUW and opens a new one. In doing so, all change requests of the current SAP-LUW are canceled. To do this, ROLLBACK WORK carries out the following actions:
Executes all subprograms registered with PERFORM ON ROLLBACK.
Deletes all subprograms registered with PERFORM ON COMMIT.
Raises an internal exception in the Object Services that makes sure that the attributes of persistent objects are initialised.
Deletes all update function modules registered with CALL FUNCTION ...IN UPDATE TASK from the VBLOG and deletes all transactional remote Function Calls registered with CALL FUNCTION ... IN BACKGROUND TASK from ARFCSSTATE and from ARFCSDATA.
Removal of all SAP locks set in the current program in which the formal parameter _SCOPE of the lock function module was set to the value 2.
Triggers a database rollback, which also ends the current database-LUW.
After completion of the statement COMMIT WORK, the event TRANSACTION_FINISHED of the system class CL_SYSTEM_TRANSACTION_STATE is raised, in which the parameter KIND has the value of the constant CL_SYSTEM_TRANSACTION_STATE=>ROLLBACK_WORK.
Variant 2
ROLLBACK CONNECTION con.
Note
This statement is for internal use only.
It cannot be used in application programs.
Effect
The ROLLBACK-statement is not executed on the standard database but only on the secondary database connection, specified through con. con is the name of the database connection as it was specified in table DBCON in column CON_NAME. The database connection con can also be specified dynamically in the form (source_text), in which the field source_text contains the name of the database connection. The field source_text must be of the type C or STRING.
Notes
As all opened database cursors on the respective database connections are closed at ROLLBACK, the attempt to continue a SELECT-loop after a ROLLBACK, leads to a runtime error. Due to the same reason, a FETCH after a ROLLBACK to the then closed cursor, leads to a runtime error. You have to make sure that cursors that are still open, are no longer used after ROLLBACK.
After execution of the statement ROLLBACK, SY-SUBRC is always equal to 0. It is not necessary to check if SY-SUBRC is unequal to 0 after ROLLBACK.
ROLLBACK must not be used during update (CALL FUNCTION ... IN UPDATE TASK) or during the execution of FORMs, which were registered with PERFORM ... ON COMMIT resp. PERFORM ...ON ROLLBACK.
The statement ROLLBACK WORK is implicitly executed if a message of the type A is treated with the addition ERROR_MESSAGE when calling a function module with CALL FUNCTION.
Exceptions
Non-Catchable Exceptions
Cause: ROLLBACK WORK is not allowed within a FORM that is called with PERFORM ... ON COMMIT or PERFORM ... ON ROLLBACK.
Runtime Error: ROLLBACK_IN_PERFORM_ON_COMMIT
Cause: ROLLBACK WORK is not allowed within an update.
Runtime Error: ROLLBACK_IN_POSTING
SET UPDATE TASK LOCAL
Syntax
SET UPDATE TASK LOCAL.
Effect
This statement specifies that the high-priority update function modules - registered during the current SAP LUW using CALL FUNCTION ... IN UPDATE TASK - are registered in the ABAP memory instead of the VBLOG database table. In addition, it specifies that the current work process and not the update work process run these modules during the current database LUW, when the COMMIT WORK statement is executed. This statement has no effect on low-priority update function modules.
At the beginning of every SAP LUW, the local update function is deactivated. If you wish to use it, you must reactivate it again before the first update function module is registered.
System fields
sy-subrc Meaning
0 The local update function is activated.
1 The local update function has not been activated, because the program has already registered at least one update function module for the normal updating procedure in the current SAP-LUW.
Notes
The local update function performs a synchronous update according to the COMMIT WORK statement, independent of the addition AND WAIT.
The occurrence of a database rollback during the local update affects all previous change requests.

JMS Unit-Of-Work in OSB Proxy Service

I'm trying to create a JMS Unit-of-Work OSB Service by populating the JMS transport user properties:
JMS_BEA_UnitOfWork
JMS_BEA_UnitOfWorkSequenceNumber
JMS_BEA_IsUnitOfWorkEnd
However, after publishing all of the messages to the Queue, JMS is not recognizing the end of the UOW.
When I publish the last message in the UOW, I set 'JMS_BEA_IsUnitOfWorkEnd' in the transport header properties to true(). However, when I look at the last message in the queue, it shows correctly that the JMS Properties Key is 'JMS_BEA_IsUnitOfWorkEnd', the Value is 'true', but the type is 'java.lang.String.' I believe the problem could be that the type is incorrect - it should be a java.lang.Boolean. However, I cannot figure out how to make it a boolean. Can you help? Do I need a boolean here? How do I assign a boolen to the transport header? I've tried 'true', 'true()', and xs:boolean('true') and they all wind up be java.lang.String!
Thanks.

string value for JMS_BEA_IsUnitOfWorkEnd should work just fine.
Make sure all messages in the same group has the same JMS_BEA_UnitOfWork value.
you can use OSB to produce unit of work messages.
for the consumer, you need to create a jms proxy using java type, then use a java callout to convert the message array list into xml that you can then process in a for loop.
Edited by: jerry.sy on May 13, 2011 1:38 PM
Edited by: jerry.sy on May 13, 2011 1:40 PM

Logical unit of works

Can some one tell me abt logical unit of work(LUW).

Hi,
A Logical Unit of Work (LUW or database transaction) is an inseparable sequence of database operations which must be executed either in its entirety or not at all. For the database system, it thus constitutes a unit.
LUWs help to guarantee database integrity. When an LUW has been successfully concluded, the database is once again in a correct state. If, however, an error occurs within an LUW, all database changes made since the beginning of the LUW are canceled and the database is then in the same state as before the LUW started.
An LUW begins
o each time you start a transaction
o when the database changes of the previous LUW have been confirmed (database commit) or
o when the database changes of the previous LUW have been cancelled (database rollback)
An LUW ends
o when the database changes have been confirmed (database commit) or
o when the database changes have been canceled (database rollback)
Two types of LUW are:
1) DB LUW - A database LUW is the mechanism used by the database to ensure that its data is always consistent. A database LUW is an inseparable sequence of database operations that ends with a database commit. The database LUW is either fully executed by the database system or not at all. Once a database LUW has been successfully executed, the database will be in a consistent state. If an error occurs within a database LUW, all of the database changes since the beginning of the database LUW are reversed. This leaves the database in the state it had before the transaction started.
2) SAP LUW - A logical unit consisting of dialog steps, whose changes are written to the database in a single database LUW is called an SAP LUW. Unlike a database LUW, an SAP LUW can span several dialog steps, and be executed using a series of different work processes.
More on this .
http://help.sap.com/saphelp_nw2004s/helpdata/en/41/7af4b9a79e11d1950f0000e82de14a/frameset.htm
Regards,
Raghav

Differences between Commit work, Logical Unit of Work and Roll back work

Hi all,
Can any one explain me in details what is the difference between Commit Work, Logical Unit of Work and Roll back work. Pls explain by providing some example.
and also explain me where and when these are used and what are the importance of using these.
Thanks in advance.
Regards
Ramana Prasad.T

Hi Ramana Prasad,
A Logical Unit of Work (LUW or database transaction) is an inseparable sequence of database operations which must be executed either in its entirety or not at all. For the database system, it thus constitutes a unit.
LUWs help to guarantee database integrity. When an LUW has been successfully concluded, the database is once again in a correct state. If, however, an error occurs within an LUW, all database changes made since the beginning of the LUW are canceled and the database is then in the same state as before the LUW started.
An LUW begins
o each time you start a transaction
o when the database changes of the previous LUW have been confirmed (database
commit) or
o when the database changes of the previous LUW have been cancelled (database rollback)
An LUW ends
o when the database changes have been confirmed (database commit) or
o when the database changes have been canceled (database rollback)
COMMIT WORK.
Executes a database commit and thus closes a logical processing unit or Logical Unit of Work ( LUW ) (see also Transaction processing ). This means that
all database changes are made irrevocable and cannot be reversed with ROLLBACK WORK and
all database locks are released.
COMMIT WORK also
calls the subroutines specified by PERFORM ... ON COMMIT * executes asynchronously any update requests (see CALL FUNCTION ... IN UPDATE TASK ) specified in these subroutines or started just before,
processes the function modules specified in CALL FUNCTION ... IN BACKGROUND TASK ,
cancels all existing locks (see SAP locking concept ) if no update requests exist,
closes all open database cursors (see OPEN CURSOR ) and
resets the time slice counter to 0.
COMMIT WORK belongs to the Open SQL command set.
Return code value
The SY-SUBRC is set to 0.
ROLLBACK WORK.
Closes a logical processing unit by reversing all database changes made since the last COMMIT .
You use this statement if you cannot be certain that all the database changes have been executed correctly.
The update routines are not performed.
ROLLBACK WORK belongs to the Open SQL command set.
Note
If the ROLLBACK statement occurs within a SELECT loop, the processing cannot continue because the database cursor is invalid. After the ROLLBACK statement, you should therefore ensure that all SELECT processing has been explicitly terminated.
<b>Plz. Avoid Duplicate Threads.</b>
Hope this resolves your query.
Reward all the helpful answers.
Regards

Weblogic 8.1SP4 Db2 "Abnormal end unit of work condition occurred"

Similar Messages

Maybe you are looking for