6/10/2023 0 Comments Oracle kill sessionTherefore, again, no rolling back transactions were captured by any query. Select max (user_commit) max_user_commit from trace_table Īs you can see there are user rollbacks, and commits but the only flag captured is 7683. Select min (user_commit) min_user_commit from trace_table Select max(user_rollback) max_user_rollback from trace_table ![]() Select min(user_rollback) min_user_rollback from trace_table Select count (*) count_rback_alternate_all_text from alternate_all_text where data_indicator='rolling_back' Select count (*) count_all_alternate_all_text from alternate_all_text where data_indicator='all' Select distinct flag distinct_flag_all_text from all_text Here is some data from the tables that I insert data into: ![]() Insert into trace_table(text, sqldate, user_commit) select 'user_commit_value',sysdate,value from v$sysstat where name='user commits' Insert into trace_table(text, sqldate, user_rollback) select 'user_rollback_value',sysdate,value from v$sysstat where name='user rollbacks' Select USERNAME,SID,SERIAL#,OSUSER,TERMINAL,SEGMENT_NAME, flagįrom v$transaction,dba_rollback_segs,v$session Select sql_text,USERNAME,SID,SERIAL#,OSUSER,TERMINAL, flag,'rolling_back' Select sql_text,USERNAME,SID,SERIAL#,OSUSER,TERMINAL, flag,'all' This is the text of the job that executes every minute: ![]() Hello I placed a job in my database when the transactions were created. This sql is created by an application that opens more than one session at a time, therefore studying any one session won't help me much, I have to look at all of them.
0 Comments
Leave a Reply. |