Commit not committing

All of the demo EJBs that use BMP won't commit their chainges. Even the transactional beans that use a UserTransaction actually never get commited to the database.
What causes this? I not the examples but the database is causing this behavior to any BMP EJB, the CMP beans work as they should.
any help would be greatly appreciated

Hi,
This might be due to STATUS_INITIALIZED status. After setting the attributes values from your code are you setting other values also from front end ?
If you are not setting any other values, your row status will remain STATUS_INITIALIZED and thus it will not commit the data to DB.
--Sushant

Similar Messages

RFC fetching data from table which is not commited

Hi Experts,
               I have a query regarding commit work.Below is the RFC that i have written
FUNCTION ZBAPI_CREATE.
*"*"Local Interface:
*" TABLES
*"      IT_ZABAP_RFC STRUCTURE ZBAPI_RFC_STR OPTIONAL
*"      RETURN STRUCTURE BAPIRET2 OPTIONAL
CALL FUNCTION 'ZBO_BAPI_CREATE'
TABLES
   IT_ZABAP_RFC       = IT_ZABAP_RFC
   RETURN             = return
Break-point.
DATA lt TYPE TABLE OF ZBAPI_RFC_STR_MAIN.
CALL FUNCTION 'ZBAPI_SEARCH_RANGE'
* EXPORTING
*   IS_STR        =
TABLES
   ET_TAB        = lt
*   RETURN        =
ENDFUNCTION.
here in first RFC call i am creating a record in ZTABLE , and then at break-point
i check the ZTABLE where it does not create any record because data is not commited into ZTABLE upto this point, but just after it i have written code for fetching data from ZTABLE but i am able to get this new record in lt.
Can anybody please explain that from where this serach RFC is providing data because inside serach i am simply selecting data from ZTABLE.
Regards,
Abhishek Bajpai
Edited by: ABHISHEK BAJPAI on Jan 28, 2009 1:12 PM

Hi Thomas,
                 Thanks for reply , i checked in ZTABLE ,before search RFC call data is not there but if i commit explicitly only then it is showing data in ZTABLE. Actually my requirement is different -
I have two RFCs 1. Create 2. Search , Now from web dynpro user will call first Create RFCs but at this point it should not insert record in ZTABLE and just after it user will call another search RFC and in this search he should be able to get these newly created records.
I want to have the functionality which a user gets when working with normal database front end like SQLPLus for Oracle. In these scenarios we see that whenever user does any insert or update the data sits in the table but still it is not committed. So there he fires Select query he sees the inserted data. But if he logs off from SQL PLUS and then logs in again, and fires Select query he does not see the data as it was not committed. I want a similiar functionalty in which if user inserts the data through Create RFC and fires the Select query through Search RFC then he can see the newly Created data also even though this data is not committed.
Although if i call create RFC in update task it will not update ZTABLE but in this situation , if user will call search RFC he will not be able to get newly created records.
So my requirement is that i should be able to get those records which are not commited in ZTABLE .If you have still any doubt regarding my question then please let me know.
Regards,
Abhishek

Trigger changes are not committing to the database

I have 9iAS and 9i DB both on my laptop.
I am having a problem in which a trigger run off a WHEN_BUTTON_PRESSED function is not committing the changes to the database. In the trigger I have:
1 record insert into table A.
1 record update to table B.
1 record insert into table C.
1 delete from table D.
None of the data is related.
I have tried various combinations of the below to get the changes to commit:
POST;
COMMIT_FORM;
Exit_Form(NO_COMMIT, NO_ROLLBACK);
MESSAGE('Got past COMMIT');
COMMIT;
CLEAR_FORM(NO_COMMIT);
ENTER_QUERY;
I am getting varying amounts of "FRM: 40508 Oracle Error: Unable to INSERT record" statements. Even so, many times the form would act as if the changes had been properly applied. But when I did a separate DB verification, I would see that the changes are not being committed. Also, most of the time the changes would also be reflected in the calling form queries, but when I exit, all changes are rolled back no matter how many commit stmts are in the trigger.
I have finally gotten the form to do what I want to do (the 4 steps noted above), but I had to add a FORMS_DDL('COMMIT'); stmt and I am still getting a FRM 40508, but at least the changes are appearing in the db.
Any ideas on why so many troubles in getting the changes to commit??? I have spent a ton of hours trying "what ifs" to see what might work. Also, this trigger is the only real "code" in the forms.
Kim

Brett -
You're probably right about the intention, but this is a place where people can come and share styles, ideas, and coding tricks, I don't understand why someone would say that. Additionally, I had a professor who was a complete momo that said that all the time (consequently, his lax attitude towards teaching crippled the IS program where I graduated and most likely will cause it to no longer be available). It's a personal peeve of mine, just to let you know where I was coming from.
Secondly, the problem I'm having may have to do with what you said, however I can't be sure. To give a better description of my scenerio, I created a form that allows the user to load information about an employee by querying a SSN. Most of this information is for display only. Six fields are available to be updated and I wrote a DML UPDATE statement that I placed inside a WHEN-BUTTON-PRESSED trigger. However, these changes won't be written to the DB because Forms is attempting to write my entire datablock, instead of just following the specified DML statements. I'm at a loss as to why this would happen, but for simplicity's sake, I would listen to ideas of how to suppress this from happening so only my statements are used when updating the DB. If you can help, thank you, if not, then thank you for your time.
Steve

Records Not Commiting - PLSQL Block

Hi,
Good Day to all..
DECLARE
v_annotation_id_1   VARCHAR2(200):='101';
v_annotation_type_1 VARCHAR2(200):='OMG';
v_j                 NUMBER;
v_user_id_string    VARCHAR2(200);
v_user_id           NUMBER;
BEGIN
FOR v_j IN 1..2
LOOP
    SELECT MAX(TRUNC(NVL(user_id,0)))
    INTO v_user_id_string
    FROM TABLE_XXX;
    v_user_id:= to_number(trim(v_user_id_string))+1;
    dbms_output.put_line('v_user_id_string-->'||v_user_id_string);
    dbms_output.put_line('v_user_id-->'||v_user_id);
    INSERT
    INTO TABLE_XXX
        TTT_annotation_id,
        user_id,
        digital_package_id,
        annotation_id,
        time_code,
        annotation_type,
        created_date,
        created_by
      VALUES
        seq_TTT_annotation_id.nextval,
        v_user_id,
        1004,
        v_annotation_id_1,
        100,
        v_annotation_type_1,
        sysdate,
        'TTTService'
       dbms_output.put_line('v_user_id 1 -->'||v_user_id);
    INSERT
    INTO TABLE_XXX
        TTT_annotation_id,
        user_id,
        digital_package_id,
        annotation_id,
        time_code,
        annotation_type,
        created_date,
        created_by
      VALUES
        seq_TTT_annotation_id.nextval,
        v_user_id,
        1004,
        v_annotation_id_1,
        100,
        v_annotation_type_1,
        sysdate,
        'TTTService'
      dbms_output.put_line('v_user_id 2 -->'||v_user_id);
     COMMIT;
     DBMS_OUTPUT.PUT_LINE('SQL%ROWCOUNT -->'||SQL%ROWCOUNT);
END LOOP;
COMMIT;
END;
Sample Output
v_user_id_string-->100002828932367
v_user_id-->100002828932368
v_user_id 1 -->100002828932368
v_user_id 2 -->100002828932368
SQL%ROWCOUNT -->0
v_user_id_string-->100002828932368
v_user_id-->100002828932369
v_user_id 1 -->100002828932369
v_user_id 2 -->100002828932369
SQL%ROWCOUNT -->0
TABLE_XXX --> Primary Key - TTT_annotation_id NOT NULL Datatype: NUMBER
Data is not getting committed; when i checked the SQL%ROWCOUNT it shows "0".
I have no idea why it is not commiting the data.
All the sessions are either COMMITTED or ROLLBACK.
Thanks for reply....

You are over committing.
SQL> create table t (n number);
Table created.
SQL> set serverout on
SQL> begin
2    insert into t values (1);
3    dbms_output.put_line ('Rows inserted: '|| sql%rowcount);
4 end;
5 /
Rows inserted: 1
PL/SQL procedure successfully completed.
SQL> edi
Wrote file afiedt.buf
1 begin
2    insert into t values (1);
3    commit;
4    dbms_output.put_line ('Rows inserted: '|| sql%rowcount);
5* end;
SQL> /
Rows inserted: 0
PL/SQL procedure successfully completed.Commit ends the current transaction and will result in subsequent sql%rowcount being zero.

Delete operation not commited

Hello,
I have a Delete operation which is never commited. When I click on delete button, the view object's row is deleted. But when I click on Commit button (which is the Commit operation of the Root Application Module), the delete operation is not commited. Debugging, I see that doDML method is not called.
Any idea on what happens?

Yes the View is editable.
I can't create a fresh page to test this, but I can test directly debugging the application module. And I have the same problem. If I update or create a row, I can commit. But if I delete a row, the Commit button is not enabled.
With "Commit Button from Application Module Data Controls > Operations > Commit/Rollback", did you mean to execute Commit operation from bindings? If yes, it's same problem.
Maybe it is because of some hacks I have done in VOImpl classes. I will see if I can test this without my hacks.

UnitOfWork is not committing in JBOSS

Hi All,
I'm using Toplink in Jboss 4.0.5 and getting the JDBC connection as:
uow = session.acquireUnitOfWork();
DatabaseLogin login = session.getLogin();
conn = (java.sql.Connection)login.connectToDatasource(null);
After performing the transactions its not commiting to the database, instead it gets committed as soon as I stop Jboss server.
Please help me to fix this issue..
Thanks

You should first make sure your session.login is completed before starting to use the session. I am unsure why you are accessing the connection. The connection returned will not necessarily be the one used by TopLink. You should just use the UnitOfWork and then rely on TopLink to properly access the configured data source during the transactional write.
The real issues surrounding TopLink's UnitOfWork and integration with the container is the type of transaction control and the type of data source being used.
JTA: Ensure you have a managed data source where the container controls the transactions. Then ensure you configure TopLink to use external transaction control. The UnitOfwork will be registered with the active JTA transaction and will write its SQL during the JTA call-backs and not on UnitOfWork.commit()
RESOURCE_LOCAL (JDBC): Ensure the data source is not managed (i.e. no JTA). Here the UnitfWork.commit() will cause Toplink to begin the transaction and write your changes.
Doug

Why is my CLEAR_BLOCK(no_validate) not committing to the database?

What I need is when the alert button 1 is selected fo to the detail block(ADM) and just delete everything for the current master id. When I click on the button it deletes for a split second and all the data comes back.Quite confused..
IF Id_Null(al_id) THEN
Message('Alert does not exist');
RAISE Form_Trigger_Failure;
ELSE
al_button := Show_Alert(al_id);
IF al_button = ALERT_BUTTON1 THEN
     :global.cl_blk := 'Y';
     go_block('ADM');
     CLEAR_BLOCK(no_validate);
     synchronize;
     go_item('adm.dci_name');
     execute_query;
else
          :global.cl_blk := 'N';
GO_ITEM('AM.MAPPING_LEVEL');
END IF;
END IF;

Why is my CLEAR_BLOCK(no_validate) not committing to the database?Better read the Clear_Block on-line help. I think you are mistaking the No_Validate parameter with the Do_Commit parameter.
The No_Validate parameter "*+Form Builder flushes the current block without validating the changes, committing the changes, or prompting the end user.+*"
With No_Validate, your changes are discarded, and NOT committed.

Commit Not reflected

Hello all,
I have an oracle 9i database -> 9.2.0.8.0.
On this database we have a table that has close to 40,00000 records.
When we are doing an insert to this table as :
insert into <Table1> select * from <Table2> where date> sysdate - 1/24;
commit;
it says 70 records inserted.
When I check for the destination table these 70 records have not come in, I once again ran the above query followed by the commit statement.
and then rechecked the records but still they were not available.
I disconnected the session and connected back again and found 140 records, I deleted these 140 records and then ran the above query again and this time it got reflected, I was able to see the 70 records in the destination table.
I am not able to find out what might be this strange behavior.
Can anyone please put some light into this issue or give some suggestions why this might have occurred.
if you would require further information please revert back to me.
Thanks and Regards
CK

There is another thread going on with the same discussion, please post replies to that thread
Re: Commit Not reflected

Commit not working in Oracle !!

Hi all,
I have created a JDBC System using the following link.
http://help.sap.com/saphelp_nw04/helpdata/en/ab/082484173ae045ab8dad8a41d33da3/frameset.htm
The JDBC Datasource is working absolutely fine , in my database actually autocommit is off , so i need to commit a transaction explicity , when i try using connection.commit() , it gives me the following eroor
Commit not possible , xadatasource.
Can any one provide the reason for this , and what is the alternative for the Same.
Points will be rewarded for helpful answers
Regards
Sara

Hi Sara,
Are you using XADatasource ?I think it is an issue (http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigDataSources)with that
try using this
DataSource Type :-ConnectionPoolDataSource
ClassName:-oracle.jdbc.pool.OracleConnectionPoolDataSource
just restart the service and use it in your code.
Thanks
Pankaj

Commit not complete

Hi,
My program is written in ProC,which consists of several insert statement followed by commit.
But when i exit the application i am getting an error " COMMIT NOT COMPLETE ".
Need your suggestion very urgently.
Thanks,
Chitrasen

Judging from the lack of response, I think you need to post a little more information.
Are you sure all the inserts are successful? are you checking Oracle status after each one?
Are you sure that the commit is called? Is successful? Are the rows you inserted visible in the database (eg from SQL*Plus)?
How do you "exit the application"? Is there a chance that after your commit, something in the application initiates a new transaction?
Where does this "COMMIT NOT COMPLETE" message come from?
PS probably better to continue this post in the Call Interface forum which covers PRO* as well as OCI - see Oracle Call Interface (OCI)
HTH
Regards Nigel

Trigger call procedure - Commit not allow

Hi all,
I need help.
 
I have One table name
EVENTS. 
I have create two trigger on that table. 
Trigger 1 is to add a running number
to events table into "id" column.
Trigger 2 is to pass that running
number in to other procedure after the new row in events complete fill in
database.
 
The error is : Commit not allow in
trigger.
The commit is only on my procedure.
How i want to make it run? Help me.

 
 
 

TRIGGER 1

CREATE
OR REPLACE
TRIGGER AUTONUM_EVENTS_ID1

BEFORE
INSERT
ON
EVENTS
REFERENCING
NEW AS
NEW OLD
AS OLD
FOR
EACH ROW
begin
 select
EVENTS_ID_SEQ.nextval into
:new.ID from
dual;
end;
/
 

TRIGGER 2
CREATE
OR
REPLACE
TRIGGER
PROCESSINFO

AFTER
INSERT
ON
EVENTS

REFERENCING
NEW
AS
NEW
OLD
AS
OLD
FOR
EACH
ROW
DECLARE

BEGIN


 UpdateInfo(:new.ID);


EXCEPTION


WHEN
OTHERS
THEN


-- Consider logging the error
and then re-raise


RAISE;
END
PROCESSINFO;
/


Because of the following :
Restrictions on Trigger Implementation The implementation of a trigger is subject to the following restrictions:
 The PL/SQL block of a trigger cannot contain transaction control SQL statements (COMMIT, ROLLBACK, SAVEPOINT, and SET CONSTRAINT) if the block is executed within the same transaction.If you really want to do a commit then search for autonomous transaction.
Hope that helps
Regards
Raj

Does commit work (commiting the changess to database take same time for ..

Does commit work (commiting the changess to database )take same time for one record and 1000 records

Hi ,
There is some micro seconds differences in updating the recors . If you have huge records ,split the data into parts and insert it .
To avoid errors or warnings ,you can use 'WAIT UPTO 5 SECONDS ' .
Thanks
Jagadeesh.G

Transaction not committed

Hi
how can i find transaction not committed? I cannot find in v$lock, but i want find first transaction, which is not committed and block others.
Any ideas?
Thanks

Use v$transaction view to check uncomiited transactions.
See here it's already discussed:
Re: How to query uncommited transactions
Locked objects can find with this select:
select
c.owner,
c.object_name,
c.object_type,
b.sid,
b.serial#,
b.status,
b.osuser,
b.machine
from
v$locked_object a ,
v$session b,
dba_objects c
where
b.sid = a.session_id
and
a.object_id = c.object_id;

Procedure not committing data despite explicit commit

I have the following code that sets when the users password will expire in our own table as well as in dba_users, but the update statement is not being committed. Does anyone have any ideas why?
create or replace
PROCEDURE COM_UNLOCK_USER(USERNAME IN VARCHAR2, PASSWORD IN VARCHAR2) IS
VSTATEMENT VARCHAR2(200);;
BEGIN
VSTATEMENT := 'UPDATE COM_OPS SET OP_PW_EXPIRY = SYSDATE+60 WHERE OP_USERCODE = :USERCODE';
EXECUTE IMMEDIATE VSTATEMENT USING USERNAME;
COMMIT;
VSTATEMENT := 'ALTER USER '||USERNAME||' IDENTIFIED BY "'||PASSWORD||'" ACCOUNT UNLOCK';
EXECUTE IMMEDIATE VSTATEMENT;
END;

The problem here is quite simple. The forms app is not calling that procedure. There can be no other logical explanation.
i) Search the data dictionary for all occurrences of the procedure and see who owns them. You may have an occurences of the procedure run as the forms owner and another one as the application owner and perhaps you need the application owner procedure to run.
ii) as a test to determine if your procedure is being called put a call into another procedure (autonomous transaction) which simply writes and commits some data to a log table.
If your form is calling this procedure there will be an entry in the log table.
If it doesn't call the procedure there will be no entry in the log table.

Commit Not Working in SQL (but works from icon)

I can't figure this one out. When I write a script I am not getting a commit even though in the statement output it says "committed". However with the very same sql if I take the commit out and just run the statement and then use the commit icon it works. For example this will not commit from sql
delete
from
test_table
where user_id = 'abc123';
commit;
But if I run it like this and click the commit icon it does:
delete
from
test_table
where user_id = 'abc123'
Any info much aprreciated

How are you running it? If you use F9 (or the green arrow) it will only run one statement.
If you use F5 (or the green arrow with a piece of paper behind it) it will run the whole worksheet ( or the selected area) as a script.
If both statements are running you should see
x rows deleted.
Commit succeeded.

Commit not committing

Similar Messages

Maybe you are looking for