Oracle Error Ora-00034
Library mySQL Code Library PHP Code Library JavaScript Code Library Oracle Terms & Definitions Oracle Error Codes PSOUG Community Blogs Oracle Jobs Board PSOUG Forum Oracle User Group Directory Free Oracle Magazines Online Learning Center PSOUG Presentations Advanced Code Search News and Events Sponsors Page Submit Code Contact Us Oracle Error: ORA-00034 Error Description: Cannot string in current PL/SQL session Error Cause: An attempt was made to issue a commit or rollback from a PL/SQL object (procedure, function, package) in a session that has this disabled (by "alter session disable commit in procedure"). Action: Enable commits from PL/SQL in this session, or do not attempt to use commit or rollback in PL/SQL when they are disabled in the current session. There haven't been any comments added for this error yet. You may add one if you like. Add a comment Name: Email: URL: Chars left:1000 (1000 max) (No HTML, but newlines will be preserved) Home : Code Library : Sponsors : Privacy : Terms of Use : Contact Us 73 users online © 2009 psoug.org PSOUG LOGIN Username: Password: Forgot your password?
in Oracle Database. Oracle Error: ORA-00034 Description: Cannot COMMIT or ROLLBACK in Current PL/SQL Session. Reason(s) for this Oracle error: This error will be raised when an attempt is made to issue a COMMIT or ROLLBACK command from PLSQL Procedure, Function or Package where in which these are disabled for the current session by using the following command: ALTER SESSION DISABLE COMMIT IN PROCEDURE Possible steps to solve this error: 1) Enable COMMIT and/or ROLLBACK whichever http://psoug.org/oraerror/ORA-00034.htm you want to use for the current session. This can be done by the following command ALTER SESSION ENABLE COMMIT IN PROCEDURE 2) Make sure not to use COMMIT or ROLLBACK command in the PLSQL Procedure, Function or Package when they are disabled. Related FAQs ORA-00033 Error -> Current Session has Empty Migration Password This explains the http://www.nullskull.com/faq/1475/ora00034-error--cannot-commit-or-rollback-in-current-plsql-session.aspx oracle error, ORA-00033 in detail, the possible reason(s) and steps to solve the same in Oracle Database. ORA-00032 Error -> Invalid Session Migration Password This explains the oracle error, ORA-00032 in detail, the possible reason(s) and steps to solve the same in Oracle Database. ORA-00031 Error -> Session marked for kill This explains the oracle error, ORA-00031 in detail, the possible reason(s) and steps to solve the same in Oracle Database. ORA-00030 Error -> User Session ID does not exist This explains the oracle error, ORA-00030 in detail, the possible reason(s) and steps to solve the same in Oracle Database. ORA-00029 Error -> Session is not a User Session This explains the oracle error, ORA-00029 in detail, the possible reason(s) and steps to solve the same in Oracle Database. ORA-00028 Error -> Your Session has been Killed This explains the oracle error, ORA-00028 in detail, the possible reason(s) and steps to solve the same in Oracle Database. ORA-00034 Error -> Cannot COMMIT or ROLLBACK in Current PL/SQL Session(1447 Views)
CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. https://community.oracle.com/thread/2407037 Please turn JavaScript back on and reload this page. Please http://sqle.ru/index.php/Oracle_PL/SQL/PL_SQL/Transaction enter a title. You can not post a blank message. Please type your message and try again. More discussions in Oracle Application Server Portal All PlacesFusion MiddlewareWebCenterOracle Application Server Portal This discussion is archived 7 Replies Latest reply on Jan oracle error 2, 2013 9:23 AM by Filip Gh Oracle Portal item cannot be deleted using dav (Bad File Descriptor) Filip Gh Jun 21, 2012 9:12 AM I cannot delete an Oracle Portal item with webdav. I get an error 500 and the item is not deleted. When this same user logs in oracle error ora-00034 as portal user with a browser, the item kan be deleted. So the user permissions are probably not the problem. What can be the problem? How do I have to solve this?
Info found in log files
C:\OraHome_2\webcache\logs
Here I find an access.log file, but this one does not seem to contain anything useful.C:\OraHome_2\Apache\Apache\logs\
Here I find two recent log files:access_log.1340236800
HTTP/1.1" 207 3215 192.168.6.57 - - [21/Jun/2012:09:28:53 +0200] "DELETE /dav_portal/portal/Bibnet/Open_Vlacc_regelgeving/Werkgroepen/vlacc_wgCAT/fgtest.txt HTTP/1.1" 500 431error_log.1340236800
[Thu Jun 21 09:28:53 2012] [error] [client 192.168.6.57] [ecid: 3781906711623,1] Could not DELETE /dav_portal/portal/Bibnet/Open_Vlacc_regelgeving/Werkgroepen/vlacc_wgCAT/fgtest.txt. [500, #0] [mod_dav.c line 2008] [Thu Jun 21 09:28:53 2012] [error] [client 192.168.6.57] [ecid: 3781906711623,1] (9)Bad file descriptor: Delete unsuccessful. [500, #0] [dav_ora_repos.c line 8913] In the error log, you also often find back message : [Thu Jun 21 10:33:02 2012] [notice] [client 192.168.6.57] [ecid: 3421133404379,1] ORA-20504: User not authorized to perform the requested operation This has probin PL SQL 4 interaction between savepoints and autonomous transactions. 5 set transaction use rollback segment 6 The pragma is legal in top-level anonymous blocks: 7 The pragma is not legal in nested blocks: 8 The pragma is valid in a packaged procedure. 9 The pragma is valid in both standalone and local subprograms. Autonomous transactions. SQL> SQL> CREATE TABLE MyTable ( 2 num_col NUMBER, 3 char_col VARCHAR2(60) 4 ); TABLE created. SQL> SQL> CREATE OR REPLACE PROCEDURE Autonomous AS 2 PRAGMA AUTONOMOUS_TRANSACTION; 3 BEGIN 4 INSERT INTO MyTable VALUES (-10, "Hello from Autonomous!"); 5 COMMIT; 6 END Autonomous; 7 / Procedure created. SQL> SQL> BEGIN 2 INSERT INTO MyTable VALUES (-10, "Hello from the parent!"); 3 4 Autonomous; 5 6 ROLLBACK; 7 END; 8 / BEGIN * ERROR at line 1: ORA-00034: cannot COMMIT IN current PL/SQL session ORA-06512: at "sqle.AUTONOMOUS", line 5 ORA-06512: at line 4 SQL> SQL> SELECT * FROM MyTable WHERE num_col = -10; no rows selected SQL> SQL> DECLARE 2 PRAGMA AUTONOMOUS_TRANSACTION; 3 BEGIN 4 INSERT INTO MyTable (num_col) VALUES (1); 5 END; 6 / DECLARE * ERROR at line 1: ORA-06519: active autonomous transaction detected AND rolled back ORA-06512: at line 5 SQL> SQL> DROP TABLE MyTable; TABLE dropped. SQL> SQL> Calling an autonomous function from SQL. SQL> CREATE TABLE MyTable ( 2 num_col NUMBER, 3 char_col VARCHAR2(60) 4 ); TABLE created. SQL> SQL> CREATE OR REPLACE FUNCTION LogParam(p1 IN NUMBER) 2 RETURN NUMBER AS 3 PRAGMA AUTONOMOUS_TRANSACTION; 4 BEGIN 5 INSERT INTO MyTable (num_col, char_col) 6 VALUES (p1, "Logged!"); 7 COMMIT; 8 RETURN p1; 9 END LogParam; 10 / FUNCTION created. SQL> SQL> SELECT LogParam(1) FROM dual; SELECT LogParam(1) FROM dual * ERROR at line 1: ORA-00034: cannot COMMIT IN current PL/SQL session ORA-06512: at "sqle.LOGPARAM", line 7 SQL> SQL> SELECT num_col 2 FROM MyTable 3 WHERE char_col = "Logged!"; no rows selected SQL> SQL> DROP TABLE MyTable; TABLE dropped. SQL> SQL> Commit an insert statement in PL SQL SQL> SQL> CREATE TABLE t ( x int ); TABLE created. SQL> SQL> SQL> begin 2 FOR i IN 1 .. 100000 3 loop 4 INSERT INTO t VALUES ( i ); 5 commit; 6 end loop; 7 end; 8 / PL/SQL procedure successfully completed. SQL> SQL> DROP TABLE t; TABLE dropped. SQL> SQL> SQL> -- interaction between savepoints and autonomous transactions. SQL> SQL> CREATE TABLE MyTable ( 2 num_col NUMBER, 3 char_col VARCHAR2(60) 4 ); TABLE created. SQL> SQL> CREATE OR REPLACE PROCEDURE AutoPr