Automatic commit/rollback when debugging

Hi,
A colleague of mine who I asked to use SQL Developer instead of TOAD for debugging, was very surprised to found his debug session to have committed at the end. TOAD doesn't. He lost a lot of time undoing the unintended changes.
He made me remember I went to the same thing when I first used sqldev.
Instead of automatically assuming you want to commit or rollback, this really should be asked on successful completion. Or set a preference: ask, commit, or rollback.
Anyone who agrees, please vote on the added feature request: http://htmldb.oracle.com/pls/otn/f?p=42626:39:1493919074214847::NO::P39_ID:28041
Thanks,
K.

It's not really a bug, but a nasty feature.
You can only vote on the mentioned request to add weight for future implementation.
Until then you can put a breakpoint before completion, and when halted there, stop execution with the red stop button.
Have fun,
K.

Similar Messages

Automatic comm channel when assigning Business system during configuration

Hi all,
In scenario file to file during Configuration,
During assigning business system there is a check box:
<b> 'Create communication channels automatically' </b>
I am planning to use File adapter on both receiver and sender side..
The question is Do I check this box or not ? If I do check this box it creates for me HTTP adapter ...Do I need it or not? I am clearly only using file adapter
thanks all !
Jon

U cannot use it in ur scenario. This function is supported for the following adapter types:
- XI Adapter
- HTTP Adapter
- IDoc Adapter
- RFC Adapter
See this
http://help.sap.com/saphelp_nw04/helpdata/en/42/d1a4d665c5574fa6e19784358ec948/content.htm
Regards,
Prateek

Suggestions for Automatic Commit/Rollback

Consider the following scenario:
A list page displays all of the records currently stored in a table. A user clicks on a link on the list page that fires the Create event and takes them to another page for entering the details of the new record. The user decides they made a mistake and clicks their browser's Back button to abort the process. There is now a new, unpopulated record on the list page.
What is the best way to handle this situation if the user cannot be concerned with manual Commits or Rollbacks? Committing after the new record details are submitted seems okay, but rolling back every time the list page is loaded renders the First/Previous/Next/Last navigation buttons useless.
Thanks,
Ryan

Create Action in ADF JSP bindings is meant to create and insert a new row into collection (and if the dataControl in action is ADFBC, then it also marks the row as temporary/initialized as indicated above).
To achieve the backbutton support, for such cases in ADF apps, we recommend using a cancel operation that is bound to 'delete' Action on the iterator which 'removes' the newly created temporary row from the collection so that it's not visible in the collection at all.
Using browser back button after create action will result in the temporary new row in the collection as noted above.
This was designed as per numerous feedback on OTN for our previous JSP solution for creating new rows where a number of teams complained about duplicate row creation on a create row action. You could still achieve this as suggested above by creating a new and initialized row and then copying it's values on the form and then removing the row and then recreating another new row on submit. Note that that requires extra copying of all display values etc and in ADF we decided to avoid that route.

Commit/Rollback in Stored Procedures

I'm just confused about how this setup works. I understand that ODP.NET is in autocommit mode by default, and any INSERT, UPDATE, or DELETE commands are committed automatically. If they fail for any reason, obviously the row(s) are not modified.
But how about sprocs? Do they autocommit as well? If so how are rollbacks handled? Do I need to explicitly create a transaction and commit/rollback? Is it best practice to commit/rollback in the .NET transaction or in the sproc itself?
As you can see, I'm just really looking for info on how these two interact. Any info you can provide will be extremely helpful.
Thanks!

Hello,
When ODP.NET is operating in auto-commit mode (the default as you note) this applies to PL/SQL calls as well.
I am of the opinion that the client should be in charge of a transaction and I do not commit/rollback inside PL/SQL code (unless of course I am writing PL/SQL that is the client of other PL/SQL code).
Here's a bit from Tom Kyte on the subject:
http://tkyte.blogspot.com/2007/03/dreaded-others-then-null-strikes-again.html
Just search for the text "Who control the commit?" on that page.
Regards,
Mark

JDBC adapter Commit/Rollback

Hi Guys, I got a question regarding JDBC adapter auto commit. Hopefully you guys can help me :). Until now, when my XI calling a storedprocedure in ORACLE using JDBC adapter, it will automatically commit the calling. When i see my configuration for the JDBC adapter receiver, the checkbox for Enable Autocommit is thicked. My question is, is there anyway that we handle the commit or rollback ourself. How we can handle that? Is it from the BPM or just from the Configuration.
Thank you very much in advance for all replies, advices and answer. Cheers guys..

Hi
Try this out
You can programmatically set auto commit to true as in follows
// Load the Oracle JDBC driver
DriverManager.registerDriver(new oracle.jdbc.OracleDriver());
// Connect to the database
// You can put a database hostname after the @ sign in the connection URL.
Connection conn =
DriverManager.getConnection ("jdbc:oracle:oci:@", "scott", "tiger");
// It's faster when auto commit is off
<b>conn.setAutoCommit (true); </b>
// Create a Statement
Statement stmt = conn.createStatement ();
regards
krishna

Commit / RollBack

Hi,
I want to execute 2 or more database operation in one transcation with commit/rollback mechanism.
Below is my code,
How can i make it has commit /rollback (in one transaction).
Thanks.
InitialContext ctx = new InitialContext();
DataSource ds = (DataSource) ctx.lookup("jdbc/SAPXXXDB");
Connection con1 = ds.getConnection();
Connection con2 = ds.getConnection();
PreparedStatement pstm1 =con1.prepareStatement("insert into ZTABLE1(...)Values(...)";
PreparedStatement pstm2 =con2.prepareStatement("insert into ZTABLE2(...)Values(...)";
pstm1.executeUpdate();
pstm2.executeUpdate();
con1.close();
con2.close();

Hi Cemil Bozlagan ,
When a connection is created, it is in auto-commit mode. This means that each individual SQL statement is treated as a transaction and is automatically committed right after it is executed.
The way to allow two or more statements to be grouped into a transaction is to disable auto-commit mode by using Connection object.
con.setAutoCommit(false);
Once auto-commit mode is disabled, no query statements are committed until you call the method commit explicitly. All statements executed after the previous call to the method commit are included in the current transaction and committed together as a unit.
Have a look
PreparedStatement pstm1 =con1.prepareStatement("insert into ZTABLE1(...)Values(...)";
PreparedStatement pstm2 =con2.prepareStatement("insert into ZTABLE2(...)Values(...)";
pstm1.executeUpdate();
pstm2.executeUpdate();
con.commit();
con.setAutoCommit(true);
To roll back the transaction based on ur requirement u can use
con.rollback()
Regards,
srikanth

How to avoid the Commit/Rollback dialog box

I've a JClient app with two frames wich relate to the same appllication module with the same connection (I need it because I want a single commit).
I start the first frame,then I click a button to start the second frame, I insert data in the second one and I see the commit/rollback buttons in both navebars enabled.
When I close the secod frame, without committing (because I want to commit at the end of the whole process) I receive the Commit/Rollback dialog box.
How can I solve that problem ?
TIA
Tullio

Remove or conditionalize the code in generated Form/Frame.java class that binds a WindowListener to the Frame like:
    addWindowListener(new WindowAdapter()
        public void windowClosing(WindowEvent e)
          _popupTransactionDialog();
          JUApplication juApp = panelBinding.getApplication();
          if (juApp != null)
            juApp.release();
          System.exit(0);
}You may either conditionlize the above windowClosing method or the code in generated method
private void _popupTransactionDialog()

Commit Rollback for Parent & Child table

Hi,
I need to load data to a parent table and child table (Record by Record), i.e one record will be loaded to the parent table and the related child record will be loaded to child table.
After first record loaded to child table, the next record will be loaded to the parent table.
My requirement is, I should not commit the parent table before the child record is transferred (so that i can rollback if my record got failed). So I have set the parent table IKM commit option to NO. Because of this, my child record is not loaded to the correcsponding target table, its failed because the parent record is not commited.
Do we have any possiblities to overcome this issue.
Thanks in Advance,
Ram Mohan T

Cezar,
I couldn't make the CKM options to "No Commit". When i did that i am getting the following error at step "16 - Control - CUSTOMER_DET - insert PK errors" ,
12838 : 72000 : java.sql.SQLException: ORA-12838: cannot read/modify an object after modifying it in parallel.
This error occurs at the CKM. so i have made all the CKM options to "commit" and IKM, LKM to "No Commit". It seems to be fine.
Cezar,
I have some plan for the scenario that i mentioned in the previous update (One dept id and all related employees). Please verify this,
1) create a procedure which extracts dept_id from source tab and passes it to the scenario(in target tab) of a package.
2) This package has the variable of dept_id, interface1 which loads data to dept and following that another procedure(2).
3) This procedure2 will extract the emp_id that corresponds to the value of the variable dept_id. And passes this emp_id to tha scenario in target tab.
4) This scenario is of a package which has the emp_id variable and interface2 for loading employees.
While executing this plan, the problem is,
1) Interface1 which loads Dept_Id is not commited (due to the KMs with commit set to "No Commit"), so that the employee records are getting loaded to the error table.
2) I have made the interface1 KM commit option to "Default: Yes " (But still the Knowledge modules steps are No commit), but still the child records are getting loaded to error table.
3) As per the above scenario, all these transforamtions are not taking in the same transaction. Thats the problem i believe.
Do we have any possiblities to overcome this Cezar?
Thanks in Advance,
Ram Mohan T
Edited by: T. Ram Mohan on Mar 5, 2009 11:43 AM

Commit/Rollback on Tab pages

I have three tab pages
1st tab page called master_detal_page. It is base block bound to tables.
2nd tab page called Keyword_page. It is not bound to the table.
3rd tab page called Exit_page. It will popup dialog box ask for save the changes. commit,rollback,exit_form on trigger when-page-change.
I encountered problems that I was unabled ROLLBACK or COMMIT the change I made on 1st or 2nd pages. When I refresh tab pages always display back to orginal records.
Please help me with any technical to solve it. Thanks
Trigger: WHEN-TAB-PAGE-CHANGED
DECLARE
v_result VARCHAR2(30);
BEGIN
IF :SYSTEM.TAB_NEW_PAGE= 'EXIT_PAGE' THEN
v_result := FUNCTION_DISPLAY_MSG_BOX('Do you want to
save changes before existing');
IF v_result = 'YES' THEN
COMMIT;
GO_BLOCK('BLK_1ST_PAGE');
ELSIF v_result = 'NO' THEN
ROLLBACK;
GO_BLOCK('BLK_1ST_PAGE');
ELSE
EXIT_FORM(NO_VALIDATE);
END IF;
END;

what is the error you got? go to menu/display error to see if any.
Then it likely you got saving issue with your master-detail block.
can you save with only master block data? but cannot save if both blocks have new data?
if yes, then you may add when-validate-record trigger to master and detail blocks, with code forms_ddl('post');
then see it makes difference.

Commit/Rollback Buttons Diabled for Pinned Tables?

When I pin a table, the commit/rollback buttons become disabled. Is there a reason for that, or is it a bug?
Java(TM) Platform 1.5.0_12
Oracle IDE 1.5.0.52.03

Finally got some time to let it return. 454 tables takes takes between 9-10 min. I also noticed if I cancel it, SQLDeveloper becomes pretty unresponsive....probably for the remaining 9-10 minutes, but I've been too busy to double check.
As for the Commit/Rollback buttons becoming disabled in 1.5.0, I'm not able to get an exact sequence, it "just seems to start happening". It happens when I have multiple tables pinned. Changes to one will let me commit/rollback, but changes to another will not. The window with the disabled commit/rollback buttons sometimes will not even mark a rownum as changed if it has been updated.
The refresh button still prompts you to save since changes were made. That works as a commit/rollback if the buttons are disabled.

TimesTen doesn't commit/rollback executed DMLs in procedure, so tables were locked.

Hello, when PLSQL_TIMEOUT occured, TimesTen doesn't commit/rollback executed DMLs in procedure, so tables were locked.
Please help. How can I solve this problem?

Looks like I've a mistake, not PLSQL_TIMOUT, after ODBC connection timeot it seems doesn't commit/rollback.
java.sql.SQLException: [TimesTen][TimesTen 11.2.1.8.0 CLIENT]Communication link failure. System call select() failed with OS error 110. This operation has Timed Out. Try increasing your ODBC timeout attribute or check to make sure the target TimesTen Server is running
Also I couldn't find why locked and what locked. My procedure waiting for lock or something I dont know, so timout occured

Automatic commit

Hi
We have implemented an application with jheadstart. Now, we have a new user requeriment for implement "automatic commit". It means that the modificacions on a page must be saved without the user press the button "save".We are trying to implement it with the event "setCurrentRowWithIndex", every time the user move to other register, we want that automatically the application saves the changes. We implemented it in the following way:
- Add commit to the event setCurrentRowWithIndex
<event name="setCurrentRowWithIndex" source="FrmGastoPadre">
<compound>
<invoke method="doIt"
javaType="oracle.jbo.uicli.binding.JUCtrlActionBinding"
instance="${bindings.Commit}"/>
<set target="${bindings.DeptIterator}"
property="currentRowIndexInRange"
value="${ui:tableSelectedIndex(uix, Dept')}"/>
</compound>
</event>
- Also, we added the method setCurrentRowWithIndex to multiRowUpdateEvent form value.
<formValue name="multiRowUpdateEvent" value="setCurrentRowWithIndex"/>
These work more or less. The changes are saved, but the execution order of events is confussing. Like in the previous code, we want commit first and then we want to set the currentRowIndexInRange(move to the next/other register). But, when we execute the code the orden is the oposite, first the currentRowIndexInRange property is set and after it executes the commit. This changes in order of events is confussing, what we are doing wrong? why the events execute in that order if we specify another ?
Thanks in advance.
Liceth

Thank you, the document is very helpful. We have other question. How can we pass a parameter (like id of a row) in a button or primaryClientAction event ?
For example, It's easy with a link:
href="DeleteEmployees.do?event=removeEmployee&id=<c:out value='${Row.Empno}' />"
But, how can we do it with a button event like:
<submitButton event="MyEvento" formName="dataForm"
textAndAccessKey="${nls.SAVE_BUTTON}"/>
or with a event throwed in a primaryClientAction?
<primaryClientAction>
<firePartialAction source="FrmDept"
event="MyEvent"
targets="messageBox _uixState FrmGastoHijo"/>
</primaryClientAction>
Thanks in advance

ON-VALIDATE-ITEM 40737: Illegal restricted procedure COMMIT in WHEN-VALIDAT

Dear All Expersts,
In a form we want to update another table ON-VALIDATE-ITEM Or POST-UPDATE or POST-INSERT Event
Could you please guide us can we do this without any error message i.e
ON-VALIDATE-ITEM
40737: Illegal restricted procedure COMMIT in WHEN-VALIDATE-ITEM trigger.
Please guide.
Thanks & Best Regards
Eidy

Eidy,
Ok, for one thing, the Post-Update and Post-Insert triggers fire during the Post and Commit Transaction processing so it doesn't make any sense that you would attempt to issue a COMMIT in either of these triggers because it is already in the process of COMMITING.
I think it would be best if you explain what it is you what to accomplish rather than how you are trying to accomplish the task. Then we will know why you are attempting a COMMIT (Restricted Built-in) in a When-Validate-Item trigger (will allows DML, Select, and Unrestricted calls).
If you intent is to update/insert a record into a seperate table (say for auditing purposes) when a user changes a value in a different block (table) item - perhaps an After Update/Insert trigger on the database table would be a better option. This makes the secondary update/insert automatic and you don't have to code it in all of your forms.
Again, like I said - if you tell us what you are trying to do, we can tell you if you are going about it the right way.
@DanielB - All I can says is HUH?
Craig...

Automatic commit work after class method?

Hi guys,
after calling a class method, is there an automatic commit work? Or do I have to insert a commit work into the class method?
At which points, a commit work is automatically called?
Regards,
Basti

Hi,
there is so much confusion about commit, commit work and rollback:
1. At the end of LUW and at every interruption (screen display including message issued, RFC calls,...) an implicit database commit occurs.
2. COMMIT WORK will trigger all update task processes that have been registered before (call function in update task, perform on commit). Most BAPI functions use perform on commit. An implicit database commit ist not a COMMIT WORK.
3. Rollback work will delete all pending update tasks inclusing all database updates not yet commited.
4. Only the 'Master'of any process should rule the COMMIT WORK because COMMIT WORK means that ALL pending update tasks are executed. So only the caller on top of the hierarchy should issue the COMMIT WORK because a later ROLLBACK is not possible - ROLLBACK only works if not y<et committed.
These rules work independent of programming feature used - nothing different in oo.
Regards
Clemens

How can i disable imessage from automatically starting up when i turn on macbook air?

how can i disable imessage from automatically starting up when i turn on macbook air? i dont know my imessages to pop up on my laptop when it turns on. But i dont want to disable imessage totally on my macbook.

Welcome to the Apple Support Communities
First of all, check that Messages is closed when you turn off your MacBook. This is so important because, by default, OS X will reopen all opened apps the next time you start your Mac.
Apart from that, when you go to  > Shut Down, or  > Restart, in the window you see to restart or turn off your MacBook, unmark "Reopen windows when logging back in". This will avoid that your Mac opens all opened apps the next time you start the MacBook, so Messages won't start automatically at startup

Automatic commit/rollback when debugging

Similar Messages

Maybe you are looking for