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.

Similar Messages

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.

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

Rule Execution : Error while executing a rule session unit of work

Error while executing a rule session unit of work.
The rule session CreditRule:130002 failed to execute a unit of work.
Check the underlying exception and correct the error. Contact oracle support if error is not fixable.
I have created a simple rule and using a decision service and a decide process activity I have tried to run the orchestration.
After compiling and saving and re-opening the orchestration flow looks correct.
When I execute the process I get the above error.
Is this something wrong with the Rule ?
Can anyone offer any advice
Thanks
Cliff

Hi.
Any further advice on this issue?
Getting the same problem and cannot figure out a solution.
How do I check the "underlying exception" btw?

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.

I have an Epson 2200 which was in perfect working condition until just now when I received the following error message: /Library/Printers/EPSON/InkjetPrinter2/Filter/rastertoescpII.app/Contents/MacOS /. What to do???

I have an Epson 2200 which was in perfect working condition until just now when I received the following error message: /Library/Printers/EPSON/InkjetPrinter2/Filter/rastertoescpII.app/Contents/MacOS /. What to do???

Hello kelsey1942,
It sounds like you are not able to print to your Epson 2200. I found an article with steps you can take to troubleshoot printer issues on a Mac:
Follow these steps until the issue is addressed:
Make sure that the printer is powered on, has ink / toner, and that there are no alerts on the printer’s control panel. Note: If you cannot clear an alert on the printer's control panel, stop here and check the printer's documentation or contact the manufacturer for support.
Ensure the printer is properly connected to a USB port on the Mac or AirPort base station / Time Capsule. If the printer is a network-capable printer, make sure that it is properly connected to your home network.
Use Software Update to find and install the latest available updates. If an update is installed, see if the issue persists.
Open the Print & Scan pane or Print & Fax (Snow Leopard) pane in System Preferences.
Delete the affected printer, then add the printer again.
If the issue persists, try these additional steps:
Reset the printing system, then add the printer again.
If the issue still persists, reset the printing system again. Download and install your printer's drivers. Then, add the printer again.
Contact the printer vendor or visit their website for further assistance.
Additional Information
Note: If your printer is wireless-capable, you should first add the printer to your network. Use the printer's control panel, or temporarily connect the printer to your Mac via USB. For more details, see this article.
You can find the full article here:
Troubleshooting printer issues in OS X
http://support.apple.com/kb/TS3147
Thank you for using Apple Support Communities.
Best,
Sheila M.

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.

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

Can I create my own logical unit of work (LUW)?

Good day, everyone!
This is an off-shoot to a Why does the NOCOMMIT parameter not work in HR_INFOTYPE_OPERATION? yesterday in this forum.
It appears that the FM I'm calling is going to do a commit, no matter what. The only thing I can tell is that the NOCOMMIT parameter is used to do a rollback only in the event of a problem.
What I'd like to do is somehow "encapsulate" my call to this function with my own "LUW" designation so that, depending on what a user selects in a selection screen (run as test only? checkbox) I can rollback changes on my own. Unfortunately, I don't know if this is even possible and, if so, how to do it. I need to do something because the end users running this function would like to be able to do a "test run" of all the address transactions to see if there's any errors, data that still needs cleaned up, etc.
Any ideas? Points awarded for all helpful answers, as always.

Hai Dave Packard
Go through the following Link
For Logical database
Logical Unit of Work (LUW)
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
each time you start a transaction
when the database changes of the previous LUW have been confirmed (database commit) or
when the database changes of the previous LUW have been cancelled (database rollback)
An LUW ends
when the database changes have been confirmed (database commit) or
when the database changes have been canceled (database rollback)
Database commit and rollback
Within an LUW, database changes are not made until after a database commit. Prior to this, any database change can be canceled by a database rollback.
In the R/3 System, a database commit is triggered either automatically or by the ABAP/4 command COMMIT WORK or the appropriate Native SQL command for the database system.
Similarly, a database rollback is triggered either automatically or by the ABAP/4 command ROLLBACK WORK or the appropriate Native SQL command for the database system.
A database commit is triggered automatically by
each screen change, and especially after the ABAP/4 commands CALL SCREEN, CALL DIALOG, CALL TRANSACTION, MESSAGE or
a Remote Function Call
A database rollback is triggered automatically by
errors which occur at runtime or
the ABAP/4 command MESSAGE with the message type 'A'
After each database commit or rollback, the database locks set in the LUW are released (see Database Locking).
Thanks & regards
Sreenivasulu P
Message was edited by: Sreenivasulu Ponnadi

Error due to out of memory condition

Hi,
system: Windows XP, 2 GM RAM, Indesign CS3
I placed two files in Indesign: the first is .ai (1.1 MB, probably exported form a CAD program), the second is .psd (53 MB). When I try to print to .ps file, Indesign displays the message: "Export error: error due to out of memory condition". If I: 1. export to PDF, everything is OK, 2. rasterize .ai in Photoshop, then import the resulting .psd to Indesign, print to .ps file is OK.
Does somebody has an answer to my problem?

My gues is "mistakes" was referred to simply not outputting as intended by the designer. I had output issues when going directly to PDF and had to also continue the old way of doing thinkgs by outputting to .ps then distill to PDF. The "mistakes" that occured for me were nearly unnoticed. The publication was a 128+4 product catalog that had a header at the top of each page. I never had any problems outputting in the past. At the time, I just had updated to CS3 (XP Pro SP3 Dual Core 4 gigs ram). I was advised that outputting directly to PDF had been durastically improved. I output my files without "mistakes" or errors, or so I thought. After proofing, I didn't realize that all of the drop shadows for the header headline were not applied. The problem though, wasn't that they were applied to all headers, just beginning at page 60 or so, halfway through. After getting the finished publication back, I didn't notice it for a few months. After noticing it, I investigated. Several troubleshooting hours later (after forum posts and other expert help), I/we concluded that it was simply a program deficiency. During my trouble shooting, I looked at several areas mainly focusing on the transparency settings. I output the document several times. I finally exported each page separately and found that that was the only way that I could output every page to include the dropshadow in each header page (past page 60 or so).
I have been past that issue for a while now. Now I am on Win 7, Quad core, 6 gigs of ram, and don't have the outputting problem that I used to. Now I occasionally get this "Error due to out of memory condition" which is BS because my hardware specs are beyond reasonable for what I typically create in my workflow. Most of the time, my memory is only at about half of its capacity when I get this error. Not when I have a PS open with a large multipage file that I am working on. My out of memory error happens during file output or just when performing ordinary layout functions in InDesign.
When on my personal computer (Aluminum iMac 2.4 Core2 duo, 4 gigs of ram, 512 video, CS4 & CS5) I have neither of the above issues.

Error in WEB IC FOR WORK ITEM "Choose an assignment reason"

We are getting an error in WEB IC where user is trying to resubmit the work item by giving the resubmission date, re submission reason , Status, and sub status
but when users are trying to save it they are getting an error i.e. "Choose an assignment reason" and they are not able to complete the process
I know there is config for maintaining "Define Reasons for Assignment of Work Items" in SPRO under work items, but this config is not applicable since we are not assigning work item to a new unit and/or a new collection specialist, or removing any assignment. we are just re submitting the work items
Any help on this will be highly appreciated.

Hi,
Just a thought - on a couple of my previous projects we had some custom CRM Fron-end validation between Work Item Sub Status and either re-assignment reason and/or Closing result code.
Perhaps check with your Development support team to ensure no such cross-validation exists upon saving.
Regards,
Ivor Martin

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

RE:logical unit of work

Hi guys,
What do u mean by logical unit of work...Can anyone explain me with an example.
Regards,
Alex.

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.
Regards
vasu

Related to LUW(logical unit of work)

Hi Experts,
      Based on an inbound idoc i need to change some data in delivery. SD_DELIVERY_UPDATE_PICKING is used to update delivery(PGI details). And also i need to change some other data(which is not possible with the above function module), so i used WS_DELIVERY_UPDATE.
       But the problem is these 2 function modules are calling the standard SAP routines which are used in the program(SAPLV50L) which used for VL02N.
     Now i changed my code, instead of FM <b>WS_DELIVERY_UPDATE</b> i used BDC, now it is giving error like 'This delivery(number) is currently processed by another user (my user id) which means i am trying to change it in same program.
   How can i use these above 2 Function modules in my program. Even i am using COMMIT WORK it creates problem.
    Is there any Function module or any command(other than COMMIT WORK) to ends a LUW(Logical Unit of Work).
   I need your inputs.
cheers,
Bujji

Hi,
       You can do one thing to over come this problem.....
After calling the 1st function module .....using do --while loop check if the update has taken place by checking the tables.......Once its done you can call the second function module......
I think we can also check for locked objects ....let me think over it
regards,
vijay

Error: Abnormal end unit of work condition occurred

Similar Messages

Maybe you are looking for