Life time of data in a Global Temporary Table.

Dear Friends,
I have a global temporary table in which I insert some values via a backend package, when forms start up and accessing it via the same package when user performs some changes in it - storing the value and during exit saving it in the master table. My problem is the data is not accessible while processing. I'm using Oracle9i Enterprise Edition Release 9.2.0.1.0 database and Forms [32 Bit] Version 6.0.8.8.0. I also give you the script in using which I created the temporary table.
CREATE GLOBAL TEMPORARY TABLE GTT_PRA
A1 VARCHAR2(10 BYTE) NOT NULL,
A2 VARCHAR2(15 BYTE) NOT NULL,
A3 VARCHAR2(10 BYTE) NOT NULL
ON COMMIT DELETE ROWS;
Why is that so? Please help me.
With Regards,
Senthil .A. Perumal.

Dear Arun,
Thank you for your script. But I'm accessing a large table, so for each and every process, the table get populated and grows very large giving some space problem, that is why I'm deleting rows when commiting. I would appreciate your help.
Dear Yogesh,
From the same forms I'm calling the backend package - will that be a different session. Once I'm calling to populate the table and next time I'm calling to store the user modified data and finally calling to store the data to master table. I think all are in the same sessions. Please reply me.
Thank you dear friends fr your immediate response. I would really appreciate it.
Regards,
Senthil .A. Perumal.

Similar Messages

DDL time changes on commit of Global temporary table

Hi,
I have created a global temporary table with on commit delete rows.
Whenever I execute commit command the DDL time of the global temporary table changes.
Just wanted to know whether commit on Global temporary table is DDL. I had expected it to be an DML operation.
Thanks,
Pawan

I do not get that effect:
orcl112> create global temporary table gtt1(c1 date);
Table created.
orcl112> select last_ddl_time from user_objects where object_name='GTT1';
LAST_DDL_TIME
2013-07-22 12:44:02
orcl112> insert into gtt1 values(sysdate);
1 row created.
orcl112> commit;
Commit complete.
orcl112> select last_ddl_time from user_objects where object_name='GTT1';
LAST_DDL_TIME
2013-07-22 12:44:02
orcl112> select * from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE 11.2.0.3.0 Production
TNS for 64-bit Windows: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
orcl112>

Datas deletion from Global Temporary table when clear command is given

Dear All,
How to Delete datas from global temporary Table when clear command is given in forms
Suggest me syntax..
Pls help..
Regards,
Gokul.B

http://psoug.org/reference/gtt.html
Francois

How to purge data in a global temporary table from another session

I've got a problem with vendor-delivered web-based software (jdbc) that periodically "hangs." When that happens, I have to kill the database session before retrying the process. This "workaround" does NOT clean up the temporary tablespace. Is there anyway (outside of bouncing the database) to truncate temporary tables regardless of sessionid? Thanks.

In 8i the space used by temporary segments is not dropped in a temporary tablespace. The space is available for other queries or temporary tables. This avoids the costs of allocating and releasing space for temporary segments.

Direct Path Loading Issues with Global Temporary Tables - OCI & OCILib

I am writing some code to import data into a warehouse from a CPU grid which computes risk data. Due to the fact a computing grid is used there will be many clients which can load the data concurrently and at any point in time.
Currently the import uses Binding in OCCI and chunking with a prepared statement to import the data into a global temporary table in a staging area after which a stored procedure is called within the same session which will process the data and load the data into a star schema.
The GTT has the advantage that if any clients have issues no dirty data will be left and each client only sees their own instance of the data.
I have been looking at using direct path loading to increase the performance of the load and have written some OCI code to perform the same task. I have manged to import the data into a regular heap based table using the OCI direct path apis. However when I try and use the same code to import against a Global Temporary Table I get an OCI Error (ORA-00600: internal error code, arguments: [6979], [16], [1], [1318528], [], [], [], [], [], [], [], [])
I get error when the function OCIDirPathPrepare is executed. The same issue occurs in both OCI and OCILib.
Is it not possible to use Direct Path Loading against a Global Temporry Table ? Because you can use the /*+ APPEND */ hint and load global temporary tables this way from tools like SQL Devloper / toad which is surely informing the SQL Engine to use Direct Path ?
Looking at the table USER_OBJECTS I can see that for a Global Temporary Table the DATA_OBJECT_ID is null. Does this mean that it is impossible to us a direct path load into Global Temporary Tables ?
Any ideas / suggestions would be really appreciated. If this means redesigning the application then I would appreciate suggestions which would allow many client to quick write processes in a parallel fashion. If this means creating a new parition in a Heap Table for each writer and direct path loading into this table then so be it.
Thanks
H
Edited by: 813640 on 19-Nov-2010 11:08

Replying to my own message in case anyone else is interested.
I have now managed to successfully load data using direct path into a global temporary table with OCI. There appears to be no reason why this approach will not work.
I loaded data into the temporary table and then issued a select count(*) on the table from within the session and from a new session. The results were as expected.
The resaon for the ORA-006000 error was due to the fact that I had enabled table level parallel loading
ie
OCIAttrSet((dvoid *) context, (ub4) OCI_HTYPE_DIRPATH_CTX, *(ub1) 1*, (ub4)0, (ub4) OCI_ATTR_DIRPATH_PARALLEL, errhp)
When loading a Global Temporary Table the OCI_ATTR_DIRPATH_PARALLEL attribute needs to be zero
This makes sense, since the temp table does not have any partitions so it would not be possible to write in parallel to multiple paritions.
Edited by: 813640 on 22-Nov-2010 08:42

Use of global temporary tables in Procedures

Hi
I am using global temporary tables in the procedures. Loading data in the same table through many procedures. I am fetching the data from the global temporary table in PRO-C by a cursor. Will this degrade performance?
Please help me..
Thanks in Advance...

Will this degrade performance?That depends... in comparison to what?
Loading data into temporary tables will generally be more efficient than loading data into permanent tables because Oracle needs to do less to protect this data since it is inherently transient. On the other hand, loading the data into a table in the first place tends to be more expensive than alternatives like using a single SQL statement, a pipelined table function, or an in memory collection.
Justin

Are global temporary tables in Oracle 10.2 behaving differently?

My procedure is creating and inserting data into a Global Temporary Table (on commit data is preserved). I am running this procedure in two different environments.
The first environment is running under Oracle 10.2 and after the procedure runs successfully I can not see any data inserted in the GTT.
When I run the very same procedure in the second environment which runs under Oracle 9.2, it works fine, runs successfully and I can see all rows inserted in the GTT.
Can someone explain this? What should I do differently in the Oracle 10.2? Any thoughts?
Thank you very much.

Hi,
The following TEMPORARY table is created with the attribute, ON COMMIT DELETE ROWS. This allows an application to load registration entries into the global temporary table and manipulate that data with SQL statements. The data is deleted upon each commit with the clause ON COMMIT DELETE ROWS.
CREATE GLOBAL TEMPORARY TABLE student_reg_entries
student_name VARCHAR2(30),
reg_entries reg_entry_varray_type
) ON COMMIT DELETE ROWS;
Replace ON COMMIT DELETE ROWS with ON COMMIT PRESERVE ROWS to retain temporary table data throughout the database session, regardless of any commits made during that session.
The following illustrates a PL/SQL block that populates this temporary table with two classes each for two students. It makes no difference how many other applications are currently using this temporary global table for similar purposes. For the code below, two rows are inserted, then a COMMIT, after which a SELECT shows that the table is empty.
DECLARE
classes_to_take reg_entry_varray_type :=
reg_entry_varray_type();
BEGIN
classes_to_take := reg_entry_varray_type(
reg_entry('CS101', 'C' ),
reg_entry('HST310', 'C' ));
INSERT INTO student_reg_entries VALUES
('John', classes_to_take);
classes_to_take := reg_entry_varray_type(
reg_entry('ENG102', 'C' ),
reg_entry('BIO201', 'C' ));
INSERT INTO student_reg_entries VALUES
('Mary', classes_to_take);
END;
This next SELECT returns two rows:
SQL> SELECT * FROM student_reg_entries;
Row 1:
John
REG_ENTRY_VARRAY_TYPE
(REG_ENTRY('CS101','C'), REG_ENTRY('HST310','C'))
Row 2:
Mary
REG_ENTRY_VARRAY_TYPE
(REG_ENTRY('ENG102','C'), REG_ENTRY('BIO201','C'))
A COMMIT automatically deletes rows making the table available for the next session transaction.
SQL> COMMIT;
SQL> SELECT * from student_reg_entries;
no rows selected
The full information about this article is in the link I post before, I'm just showing this extract of the article because some people don't like to read links....
Cheers,
Francisco Munoz Alvarez
http://www.oraclenz.com

Auditing data from global temporary table

Hi I have a process that uses a global temporary table.
What it does it serve a consolidation point to merge a lot of data.
Some the former designer decides to use a global temporary table and the row will be gone once it got commit.
However, the data is corrupted occasionally. And ideally we would like to fix the upstream source data but this is too complicated and not feasible.
So we decide to audit the data going into the global temporary table. We want to generate a report on the corrupted data.
However, whenever I commit, the data is gone from the global temporary table and we do not want to set it to commit preserve rows for the global temporary table
Even with autonomous transaction this is not working out as once it commits the data is gone.
Any idea how this can be done. Here are the prototype that I build to demo this:
drop table gt_tst1;
--this is the table its data needs to get audit
create global temporary table gt_tst1(id number); --on commit preserve rows;
drop table not_gt_tst1;
--this table is used for storign the corrupt data and generate report
create table not_gt_tst1 as select * from gt_tst1;
CREATE OR REPLACE PROCEDURE tst_gt_tst1 IS
PRAGMA AUTONOMOUS_TRANSACTION;
BEGIN
--if there is a way to do the insert and select once. but it seems it is not working for global temporay table unless change it to on commit preserve rows
INSERT
when m2 = 0 THEN
INTO not_gt_tst1(id)values(object_id)
when m3 = 0 THEN
INTO gt_tst1(id) values (object_id)
select object_id,mod(object_id,2) m2, mod(object_id,3) m3 from dba_objects where rownum < 101;
COMMIT;
END tst_gt_tst1;
select sysdate from dual;
truncate table gt_tst1;
truncate table not_gt_tst1;
select * from gt_tst1;
select * from not_gt_tst1;
execute tst_gt_tst1;
select * from gt_tst1; -- data gone
select * from not_gt_tst1;
--commit
select sysdate from dual;
spool off

The data is poor and the code is poor and the dev and QA env is also poor..
And the business asks us to fix the data..However..we do not have an environment close enough to test it out before it got put into production that is the bottom line.
Heres the dev and QA env cannot be trust to the extent that I can sign off and say it will give the same behavior as the production env
So we would like to minimize the risk as there are other process uses these table and we are not sure if changing this would lead to UN-expected behavior.
We cannot tell some other process rely on the fact that these table got empty out after commit.
Edited by: vxwo0owxv on Jan 23, 2012 12:18 PM
Edited by: vxwo0owxv on Jan 23, 2012 12:20 PM

Global Temporary Tables in active data guard.

HI Gurus,
Please help me with below query. Google confusing me a lot.
1) We have an ADG (RAC Setup) 11gr2 with ASM. Is it possible to create global temporary tables in ADG. Because Devlopers are not able to create temp tables. Its giving error as
ORA-16000: database open for read-only access
2) Do we need to create Global Temporary tables in Active node or passive node??
Please help.
Regards,
Nikhil Mehta.

Hi Meser,
thanks for your response.
We are using it for Reporting purpose only.
SQL> select open_mode from v$database;
OPEN_MODE
READ ONLY WITH APPLY
Regards,
Nikhil Mehta.

Weird issue: Partial data inserted when reading from Global temporary table

I have a complex sql query that fetches 88k records. This query uses a global temporary table which is the replica of one of our permanent tables. When I do Create table..select... using this query it inserts only fewer records (66k or lesser). But when I make the query point to the permanent table it inserts all 88k records.
1. I tried running the select query separately using temp and perm table. Both retrieves 88k records.
2. From debugging I found that this problem occurred when we were trying to perform a left outer join on an inline view.
However this problem got resolved when I used the /*+ FIRST_ROWS */ hint.
From my limited oracle knowledge I assume that it is the problem with the query and how it is processed in the memory.
Can someone clarify what is happening behind the scenes and if there is a better solution?
Thanks

user3437160 wrote:
I have a complex sql query that fetches 88k records. This query uses a global temporary table which is the replica of one of our permanent tables. When I do Create table..select... using this query it inserts only fewer records (66k or lesser). But when I make the query point to the permanent table it inserts all 88k records.
1. I tried running the select query separately using temp and perm table. Both retrieves 88k records.
2. From debugging I found that this problem occurred when we were trying to perform a left outer join on an inline view.
However this problem got resolved when I used the /*+ FIRST_ROWS */ hint.
From my limited oracle knowledge I assume that it is the problem with the query and how it is processed in the memory.
Can someone clarify what is happening behind the scenes and if there is a better solution?
Thanksmight specifics be OS & Oracle version dependent?
How to ask question
SQL and PL/SQL FAQ

Doubt with Global Temporary table

hi,
i have created a global temporary table with ON COMMIT DELETE ROWS option. in my Function in a loop i m inserting values into this Table, after that loop closes and then i m selecting some other values from DB. and in the last i am returning a ref cursor which is selecting values from temporary table i hav created.
now the thing is i m not getting any values in the cursor.
later I have created the table with ON COMMIT PRESERVE ROWS option, in this case cursor returning values,
can anyone explain me the functionality, as per my knowledge global temporary table values are session specific so why i m not getting the values in the 1st case when i used ON COMMIT DELETE ROWS (same session).
Thanks
Piyush

Ok, here's a simple example, like we'd like to see from you not working....
First create a GTT with ON COMMIT DELETE ROWS...
SQL> ed
Wrote file afiedt.buf
1* create global temporary table mytable (x number) on commit delete rows
SQL> /
Table created.Now a simple function that populates the GTT and returns a ref cursor to the data without doing any commits (hence the data should be there!)
SQL> ed
Wrote file afiedt.buf
1 create or replace function pop_table return sys_refcursor is
2    v_rc sys_refcursor;
3 begin
4    insert into mytable
5    select rownum from dual connect by rownum <= 10;
6    OPEN v_rc FOR SELECT x FROM mytable;
7    RETURN v_rc;
8* end;
SQL> /
Function created.So now we call the function and get a reference to our ref cursor...
SQL> var v_a refcursor;
SQL> exec :v_a := pop_table();
PL/SQL procedure successfully completed.So, in principle, because no commits have been issued the ref cursor should return data...
SQL> print v_a;
         X
         1
         2
         3
         4
         5
         6
         7
         8
         9
        10
10 rows selected.... which it does.
Now, what happens if we do that again...
SQL> commit;
Commit complete.
SQL> exec :v_a := pop_table();
PL/SQL procedure successfully completed.... but this time we commit before retrieving the data...
SQL> commit;
Commit complete.
SQL> print v_a;
ERROR:
ORA-00600: internal error code, arguments: [kcbz_check_objd_typ_1], [0], [0], [1], [], [], [], []
no rows selected
SQL>Oracle has (correctly) lost reference to the data because of the commit.
So show us what yours is doing.

Does Global Temporary Table help in performance?

I have a large database table that is growing daily. The application I have has a page for the past day data and another for some chosen period of time. Since I'm looking at a very large amount of data for each page (~100k rows) and having charts based on time, I have performance issues. I tried collections for each of these and found out that it is making everything slower and I think because the collection is large and it is not indexed.
Since I don't need the data to be maintained for the session and in fact for each time that I submit a page I need to get the updated data at least for the past day page, I wonder if Global Temporary Table is a good solution for me.
The only reason I want to store the data in a table is to avoid running similar queries for different charts and reports. Is this a valid reason at all?
If this is a good solution, can someone give me a hint on how to do this?
Any help is appreciated.

It all depends on how efficient your query is. You can have a billion row table and still get a fraction of a second response if the data is indexed, and the number of data blocks to be visited to retrieve the data is small. It's all about reducing the number of I/Os to find and retrieve your data with the query. Many aspects of the data, stats, table/index structure etc can influence the efficiency of your query. The SQL forum would be a better place to get into the query tuning, but if this test is fast, you can probably focus elsewhere for now. It will resolve your full resultset, and then just do a count of the result (to avoid sending 100k rows back to the client). We are trying to get an idea of how long it takes to resolve your resultset. Using litterals rather than item names in your sql should be fine for this test. Avoid using V() around item names in your SQL.
select count(*) from ( <your-query-goes-here> );

How we cn avoid the sequence in remote tables through global temporary tabl

Hi,
We have table xx_interface_qualifiers in the remote db and we are inserting the data like this and its on a loop
INSERT INTO xx_interface_qua
(interface_id,
list_line_interface_id, excluder_flag,
qualifier_context, qualifier_attribute,
qualifier_attr_value, qualifier_precedence,
comparison_operator_code, start_date_active,
end_date_active, list_header_name, list_line_no,
creation_date, created_by, last_update_date,
last_updated_by, interface_attribute1
VALUES (xx_interface_qua_s.NEXTVAL,
ttt, 'Y',
xxx, xxx2,
xxx3, xxx4,
'=', SYSDATE,
NULL, xxx4, -1,
SYSDATE, '-1', SYSDATE,
'-1', 44 );
We are trying to avoid the hitting of the database every time for a sequence and try to implement the global temporary tables,i mean to say 1st we need to insert the data to TEMP table and then from temp table we cn inseert all the data to xx_interface_qual in a single shot to improve the performance.
But how we cn avoid the sequence in this case as we do not know the sequence in remote side.
Please suggest any other way to improve the performance.
Regards
Das

797846 wrote:
We have table xx_interface_qualifiers in the remote db and we are inserting the data like this and its on a loop
We are trying to avoid the hitting of the database every time for a sequence and try to implement the global temporary tables,i mean to say 1st we need to insert the data to TEMP table and then from temp table we cn inseert all the data to xx_interface_qual in a single shot to improve the performance.
But how we cn avoid the sequence in this case as we do not know the sequence in remote side.Does not make sense. I/O is the slowest database operation.
You have an unknown performance problem (that you claim is due to a sequence, but failed to provide any evidence for). Now you want to create more I/O, by writing the data twice. Once into a temp table and then again into the destination table. And do that in order to increase performance?
I do not see how this can solve the underlying, and unknown, performance issue that you claim exists.
Any problem solution needs to start with correctly and comprehensively identifying the problem.
You cannot solve a problem without first knowing WHAT the problem is.

Problem with global temporary table in Oracle 10g

Hi All,
I face a peculiar problem in Oracle 10g with respect to Global temporary table.
Have Oracle 10g version in Production and 11g version in UAT.
Table_
create global temporary table TT_TEMPGPSMANUAL
Col_1    VARCHAR2(50),
Col_2    VARCHAR2(500),
Col_3    VARCHAR2(50),
Col_4    VARCHAR2(50),
Col_5    VARCHAR2(15),
Col_6    VARCHAR2(20),
Col_7    VARCHAR2(250),
Col_8    VARCHAR2(20),
Col_9    VARCHAR2(15),
Col_10   VARCHAR2(20),
Flag     NUMBER,
Col_11   INTEGER,
Col_12   VARCHAR2(50)
on commit preserve rows;So this should preserve the rows inserted into this table until the session ends.
Have a webpage in front-end where in turn, it opens another page (session is carried through) and a few rows will be inserted to this table from the webpage (through a function) on submit and the current page will be closed.
From the parent page, if I open the sub-page data inserted in the temporary table are held and displayed (another function to fetch the values in the Global Temp table).
The Problem in Oracle 10g (Production) is, this is not happening properly. When I close and open the sub-page, not every time I get the data stored i.e if I close and open the page 10 times, atelast 4 times the data is missed in the page (I am not getting values from temp table) randomly.
But this does not happen in UAT (which has Oracle 11g installed) as I get the data in the webpage consistently. After passing UAT, when we rolled out to Prod, getting this issue which we are unable to get what could be the reason.
It is very hard to debug using GTT dynamically in prod. It takes time to get Oracle 11g installed in Prod.
Can anyone suggest?
Regards
Deep

935195 wrote:
Also, I am opening the sub-page from the parent page (through a hyperlink). Then in this case, Would session will be changed from parent to subpage? (I am not aware exactly and have the impression that, as the second page is a child, I guess it would take the same session).I'm not sure what "sub-page" or "parent page" means to you. If you're just linking from one page to another, "parent" and "child" don't really make sense since page A links to page B and B links to A quite frequently.
Assuming that you have to log in to access the site, it is likely that the two pages share the same middle tier application session. It is unlikely that the middle tier would hold the database session from the first request open waiting to see if the user eventually requested the second page. It is theoretically possible that you could code your middle tier this way but it is extremely unlikely that you would want to do so for a variety of reasons. So, when you say "would [the] session ... be changed", it is likely that the application session would be the same for both calls but that the database session would be different.
Justin

Deadlock with CREATE GLOBAL TEMPORARY TABLE

I got this error
ORA-00604: error occurred at recursive SQL level 1
ORA-00060: deadlock detected while waiting for resource
while trying to create global temporary table.
Table creation command:
CREATE GLOBAL TEMPORARY TABLE ITUSER.T_0091FBDG ("GOD" char(4) DEFAULT (' ') NOT NULL,"UNKUM" number(10,0) DEFAULT (0) NOT NULL,[a lot of other fields]) ON COMMIT PRESERVE ROWS
There is no outer references in command. So does somebody know where does deadlock come from?
I'm using Oracle 10g.
Edited by: LeopoldStoch on Apr 13, 2010 7:04 AM

I have grabbed log files. But it make me even more curious. Here it is:
alert_itdb.log
Thread 1 advanced to log sequence 253 (LGWR switch)
Current log# 1 seq# 253 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\REDO01.LOG
Tue Apr 13 10:53:09 2010
Thread 1 advanced to log sequence 254 (LGWR switch)
Current log# 2 seq# 254 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\REDO02.LOG
Tue Apr 13 10:55:32 2010
Thread 1 advanced to log sequence 255 (LGWR switch)
Current log# 3 seq# 255 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\REDO03.LOG
Tue Apr 13 10:55:49 2010
ORA-00060: Deadlock detected. More info in file c:\oracle\product\10.2.0\admin\itdb\udump\itdb_ora_3868.trc.
Tue Apr 13 11:01:58 2010
Thread 1 advanced to log sequence 256 (LGWR switch)
Current log# 1 seq# 256 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\REDO01.LOG
Tue Apr 13 11:03:29 2010
Thread 1 advanced to log sequence 257 (LGWR switch)
Current log# 2 seq# 257 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\REDO02.LOG
Tue Apr 13 11:14:16 2010
itdb_ora_3868.trc
Dump file c:\oracle\product\10.2.0\admin\itdb\udump\itdb_ora_3868.trc
Tue Apr 13 10:55:48 2010
ORACLE V10.2.0.4.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Release 10.2.0.4.0 - Production
Windows NT Version V5.2 Service Pack 2
CPU : 2 - type 586, 1 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:3568M/8188M, Ph+PgF:7889M/12090M, VA:579M/2799M
Instance name: itdb
Redo thread mounted by this instance: 1
Oracle process number: 18
Windows thread id: 3868, image: ORACLE.EXE (SHAD)
*** 2010-04-13 10:55:48.874
*** ACTION NAME:() 2010-04-13 10:55:48.811
*** MODULE NAME:(5436,20100413105316,82100) 2010-04-13 10:55:48.811
*** SERVICE NAME:(ITDB) 2010-04-13 10:55:48.811
*** SESSION ID:(145.52602) 2010-04-13 10:55:48.811
DEADLOCK DETECTED ( ORA-00060 )
[Transaction Deadlock]
The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:
Deadlock graph:
---------Blocker(s)-------- ---------Waiter(s)---------
Resource Name process session holds waits process session holds waits
TX-00080011-0000198d 18 145 X 17 158 S
TX-0006001c-0000192d 17 158 X 18 145 S
session 145: DID 0001-0012-00000164 session 158: DID 0001-0011-000005F5
session 158: DID 0001-0011-000005F5 session 145: DID 0001-0012-00000164
Rows waited on:
Session 158: obj - rowid = 00000000 - D/////AACAAAKy6AAA
(dictionary objn - 0, file - 2, block - 44218, slot - 0)
Session 145: obj - rowid = 00000000 - D/////AACAAAABJAAA
(dictionary objn - 0, file - 2, block - 73, slot - 0)
Information on the OTHER waiting sessions:
Session 158:
pid=17 serial=2727 audsid=241067 user: 60/ITUSER
O/S info: user: VSC03\it_appsrv, term: VSC03, ospid: 2328:2640, machine: WORKGROUP\VSC03
program: AppServer.exe
client info: ELIZ-041.R#046IKSANOV.RIKSANOV.VSC03:8223.2328.5-1-2600.IT_APPSR
application name: 5436,20100413105322,82000, hash value=3107059750
Current SQL Statement:
CREATE GLOBAL TEMPORARY TABLE ITUSER.T_009EFBDN ("GOD" char(4) DEFAULT (' ') NOT NULL,"UNKUM" number(10,0) DEFAULT (0) NOT NULL,"CENA" number(15,5) DEFAULT (0) NOT NULL,"EDI" number(3,0) NULL,"EDI2" number(3,0) NULL,"KOL" number(14,5) DEFAULT (0) NOT NULL,"KOL2" number(14,5) DEFAULT (0) NOT NULL,"SUMMA" number(16,2) DEFAULT (0) NOT NULL,"KOL_N1" number(14,5) DEFAULT (0) NOT NULL,"KOL_N2" number(14,5) DEFAULT (0) NOT NULL,"KOL_N3" number(14,5) DEFAULT (0) NOT NULL,"KOL_N4" number(14,5) DEFAULT (0) NOT NULL,"KOL_N5" number(14,5) DEFAULT (0) NOT NULL,"KOL_N6" number(14,5) DEFAULT (0) NOT NULL,"KOL_N7" number(14,5) DEFAULT (0) NOT NULL,"KOL_N8" number(14,5) DEFAULT (0) NOT NULL,"KOL_N9" number(14,5) DEFAULT (0) NOT NULL,"KOL_N10" number(14,5) DEFAULT (0) NOT NULL,"KOL_N11" number(14,5) DEFAULT (0) NOT NULL,"KOL_N12" number(14,5) DEFAULT (0) NOT NULL,"KOL_N13" number(14,5) DEFAULT (0) NOT NULL,"KOL2N1" number(14,5) DEFAULT (0) NOT NULL,"KOL2N2" number(14,5) DEFAULT (0) NOT NULL,"KOL2N3" number(14,5) DEFAULT (0) NOT NULL,"KOL2N4" number(14,5) DEFAULT (0) NOT NULL,"KOL2N5" number(14,5) DEFAULT (0) NOT NULL,"KOL2N6" number(14,5) DEFAULT (0) NOT NULL,"KOL2N7" number(14,5) DEFAULT (0) NOT NULL,"KOL2N8" number(14,5) DEFAULT (0) NOT NULL,"KOL2N9" number(14,5) DEFAULT (0) NOT NULL,"KOL2N10" number(14,5) DEFAULT (0) NOT NULL,"KOL2N11" number(14,5) DEFAULT (0) NOT NULL,"KOL2N12" number(14,5) DEFAULT (0) NOT NULL,"KOL2N13" number(14,5) DEFAULT (0) NOT NULL,"SUM_N1" number(16,2) DEFAULT (0) NOT NULL,"SUM_N2" number(16,2) DEFAULT (0) NOT NULL,"SUM_N3" number(16,2) DEFAULT (0) NOT NULL,"SUM_N4" number(16,2) DEFAULT (0) NOT NULL,"SUM_N5" number(16,2) DEFAULT (0) NOT NULL,"SUM_N6" number(16,2) DEFAULT (0) NOT NULL,"SUM_N7" number(16,2) DEFAULT (0) NOT NULL,"SUM_N8" number(16,2) DEFAULT (0) NOT NULL,"SUM_N9" number(16,2) DEFAULT (0) NOT NULL,"SUM_N10" number(16,2) DEFAULT (0) NOT NULL,"SUM_N11" number(16,2) DEFAULT (0) NOT NULL,"SUM_N12" number(16,2) DEFAULT (0) NOT NULL,"SUM_N13" number(16,2) DEFAULT (0) NOT NULL,"DATE_REST" date NULL,"KOL_PRI" number(14,5) DEFAULT (0) NOT NULL,"KOL2PRI" number(14,5) DEFAULT (0) NOT NULL,"SUM_PRI" number(16,2) DEFAULT (0) NOT NULL,"DATE_FPRI" date NULL,"NDOC_FPRI" char(20) DEFAULT (' ') NOT NULL,"KOL_PRIG" number(14,5) DEFAULT (0) NOT NULL,"KOL2PRIG" number(14,5) DEFAULT (0) NOT NULL,"SUM_PRIG" number(16,2) DEFAULT (0) NOT NULL,"KOL_PRIT" number(14,5) DEFAULT (0) NOT NULL,"KOL2PRIT" number(14,5) DEFAULT (0) NOT NULL,"KOL_RAS" number(14,5) DEFAULT (0) NOT NULL,"KOL2RAS" number(14,5) DEFAULT (0) NOT NULL,"SUM_RAS" number(16,2) DEFAULT (0) NOT NULL,"DATE_LRAS" date NULL,"NDOC_LRAS" char(20) DEFAULT (' ') NOT NULL,"KOL_RASG" number(14,5) DEFAULT (0) NOT NULL,"KOL2RASG" number(14,5) DEFAULT (0) NOT NULL,"SUM_RASG" number(16,2) DEFAULT (0) NOT NULL,"KOL_RAST" number(14,5) DEFAULT (0) NOT NULL,"KOL2RAST" number(14,5) DEFAULT (0) NOT NULL,"KOL_PRIREZ" number(14,5) DEFAULT (0) NOT NULL,"KOL2PRIREZ" number(14,5) DEFAULT (0) NOT NULL,"SUM_PRIREZ" number(16,2) DEFAULT (0) NOT NULL,"KOL_RASREZ" number(14,5) DEFAULT (0) NOT NULL,"KOL2RASREZ" number(14,5) DEFAULT (0) NOT NULL,"SUM_RASREZ" number(16,2) DEFAULT (0) NOT NULL,"PRC_RAS" number(3,0) DEFAULT (0) NOT NULL,"KSSM" char(5) NULL,"COMM" char(40) DEFAULT (' ') NOT NULL,"KDM3" char(1) DEFAULT (' ') NOT NULL,"KDM4" char(1) DEFAULT (' ') NOT NULL,"KOL_INV" number(14,5) DEFAULT (0) NOT NULL,"KOL2INV" number(14,5) DEFAULT (0) NOT NULL,"CENA_INV" number(15,5) DEFAULT (0) NOT NULL,"SUM_INV" number(16,2) DEFAULT (0) NOT NULL,"DATE_INV" date NULL,"KSBG" char(3) DEFAULT (' ') NOT NULL,"KOL_C" number(14,5) DEFAULT (0) NOT NULL,"KOL2C" number(14,5) DEFAULT (0) NOT NULL,"SUM_C" number(16,2) DEFAULT (0) NOT NULL,"KBLS" char(5) DEFAULT (' ') NOT NULL,"BS_ZATR" char(10) NULL,"KAU_ZATR" char(12) DEFAULT (' ') NOT NULL,"MECEXPL" number(3,0) DEFAULT (0) NOT NULL,"SUM_IZNOS" number(14,2) DEFAULT (0) NOT NULL,"SUM_IMEC" number(14,2) DEFAULT (0) NOT NULL,"NINKAS" number(10,0) DEFAULT (0) NOT NULL,"DATE_D" date NULL,"FIO_D" char(10) DEFAULT (' ') NOT NULL,"DATE_K" date NULL,"FIO_O" char(10) DEFAULT (' ') NOT NULL,"STDCURR" char(1) DEFAULT (' ') NOT NULL) ON COMMIT PRESERVE ROWS
End of information on OTHER waiting sessions.
Current SQL statement for this session:
insert into col$(obj#,name,intcol#,segcol#,type#,length,precision#,scale,null$,offset,fixedstorage,segcollength,deflength,default$,col#,property,charsetid,charsetform,spare1,spare2,spare3)values(:1,:2,:3,:4,:5,:6,decode(:5,182/*DTYIYM*/,:7,183/*DTYIDS*/,:7,decode(:7,0,null,:7)),decode(:5,2,decode(:8,-127/*MAXSB1MINAL*/,null,:8),178,:8,179,:8,180,:8,181,:8,182,:8,183,:8,231,:8,null),:9,0,:10,:11,decode(:12,0,null,:12),:13,:14,:15,:16,:17,:18,:19,:20)
===================================================
PROCESS STATE
Process global information:
process: 5F28A1F8, call: 5F3A8E98, xact: 5DFF8B40, curses: 5F37D6A8, usrses: 5F375F38
SO: 5F28A1F8, type: 2, owner: 00000000, flag: INIT/-/-/0x00
(process) Oracle pid=18, calls cur/top: 5F3A8E98/5F3A75B8, flag: (0) -
int error: 0, call error: 0, sess error: 0, txn error 0
(post info) last post received: 0 0 117
last post received-location: kcbzww
last process to post me: 5f289c00 93 0
last post sent: 0 0 117
last post sent-location: kcbzww
last process posted by me: 5f289c00 93 0
(latch info) wait_event=0 bits=0
Process Group: DEFAULT, pseudo proc: 5F2BC4EC
O/S info: user: SYSTEM, term: VSC03, ospid: 3868
OSD pid info: Windows thread id: 3868, image: ORACLE.EXE (SHAD)
Dump of memory from 0x5F276E78 to 0x5F276FFC
5F276E70 0000000B 5E1231B8 [.....1.^]
5F276E80 00000010 000313A9 5F3A75B8 00000003 [.........u:_....]
5F276E90 000313A9 5F4B92D4 0000000B 000313A9 [......K_........]
5F276EA0 5F375F38 00000004 0003129D 5DE1FFA4 [8_7_...........]]
5F276EB0 00000007 000313A9 5DE20028 00000007 [........(..]....]
5F276EC0 000313A9 5DE200BC 00000007 000313A9 [.......]........]
5F276ED0 5DE20140 00000007 000313A9 5DE201C4 [@..]...........]]
5F276EE0 00000007 000313A9 5DE20248 00000007 [........H..]....]
5F276EF0 000313A9 5DE202CC 00000007 000313A9 [.......]........]
5F276F00 00000000 00000000 00000000 00000000 [................]
Repeat 14 times
5F276FF0 00000000 00000000 00000000 [............]
(FOB) flags=2 fib=5DEEEC98 incno=0 pending i/o cnt=0
fname=C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\UNDOTBS01.DBF
fno=2 lblksz=8192 fsiz=311040
(FOB) flags=2 fib=5DEEE608 incno=0 pending i/o cnt=0
fname=C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\CONTROL03.CTL
fno=2 lblksz=16384 fsiz=430
(FOB) flags=2 fib=5DEEE2C8 incno=0 pending i/o cnt=0
fname=C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\CONTROL02.CTL
fno=1 lblksz=16384 fsiz=430
(FOB) flags=2 fib=5DEEDF88 incno=0 pending i/o cnt=0
fname=C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\CONTROL01.CTL
fno=0 lblksz=16384 fsiz=430
(FOB) flags=2 fib=5DEEF658 incno=0 pending i/o cnt=0
fname=C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\ITDATA01.DBF
fno=5 lblksz=8192 fsiz=2109440
(FOB) flags=2 fib=5DEEE948 incno=0 pending i/o cnt=0
fname=C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\SYSTEM01.DBF
fno=1 lblksz=8192 fsiz=79360
(FOB) flags=2 fib=5DEEFCE8 incno=0 pending i/o cnt=0
fname=C:\ORACLE\PRODUCT\10.2.0\ORADATA\ITDB\TEMP01.DBF
fno=201 lblksz=8192 fsiz=43776
SO: 5F375F38, type: 4, owner: 5F28A1F8, flag: INIT/-/-/0x00
(session) sid: 145 trans: 5D06D4B0, creator: 5F28A1F8, flag: (8100041) USR/- BSY/-/-/-/-/-
DID: 0001-0012-00000164, short-term DID: 0000-0000-00000000
txn branch: 00000000
oct: 1, prv: 0, sql: 50B2BAC0, psql: 57554078, user: 60/ITUSER
service name: ITDB
O/S info: user: VSC03\it_appsrv, term: VSC03, ospid: 3668:3616, machine: WORKGROUP\VSC03
program: AppServer.exe
client info: ELIZ-041.R#046IKSANOV.RIKSANOV.VSC03:8223.3668.5-1-2600.IT_APPSR
application name: 5436,20100413105316,82100, hash value=3093400541
last wait for 'enq: TX - allocate ITL entry' blocking sess=0x5F386200 seq=4256 wait_time=2999487 seconds since wait started=2
name|mode=54580004, usn<<16 | slot=6001c, sequence=192d
Dumping Session Wait History
for 'enq: TX - allocate ITL entry' count=1 wait_time=2999487
name|mode=54580004, usn<<16 | slot=6001c, sequence=192d
for 'buffer busy waits' count=1 wait_time=10
file#=1, block#=f923, class#=1
for 'buffer busy waits' count=1 wait_time=53
file#=1, block#=d1ff, class#=1
for 'buffer busy waits' count=1 wait_time=36
file#=1, block#=19, class#=4
for 'buffer busy waits' count=1 wait_time=28
file#=1, block#=19, class#=4
for 'buffer busy waits' count=1 wait_time=27
file#=1, block#=f923, class#=1
for 'buffer busy waits' count=1 wait_time=13
file#=1, block#=ec86, class#=1
for 'buffer busy waits' count=1 wait_time=29
file#=1, block#=f923, class#=1
for 'buffer busy waits' count=1 wait_time=15
file#=1, block#=f95d, class#=1
for 'buffer busy waits' count=1 wait_time=215
file#=1, block#=d1ff, class#=1
temporary object counter: 1
UOL used : 0 locks(used=2, free=10)
KGX Atomic Operation Log 69405330
Mutex 00000000(0, 0) idn 0 oper NONE
Cursor Parent uid 145 efd 5 whr 11 slp 0
oper=NONE pt1=A4744BC4 pt2=6842B2F4 pt3=A4744B94
pt4=00000000 u41=0 stt=0
KGX Atomic Operation Log 69405358
Mutex 50B2BB74(0, 1) idn 0 oper NONE
Cursor Stat uid 145 efd 8 whr 1 slp 0
oper=NONE pt1=50B2BAC0 pt2=00000000 pt3=00000000
pt4=00000000 u41=0 stt=8
KGX Atomic Operation Log 69405380
Mutex 00000000(0, 0) idn 0 oper NONE
Library Cache uid 145 efd 0 whr 0 slp 0
SO: 5C5A6334, type: 53, owner: 5F375F38, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=5c5a6334 handle=5e9a6868 mode=N
call pin=00000000 session pin=00000000 hpc=0000 hlc=0000
htl=5C5A6384[5C76A228,5C59D1D0] htb=5C59D1D0 ssga=5C59CD04
user=5f375f38 session=5f37d6a8 count=1 flags=CBK[0020] savepoint=0x0
LIBRARY OBJECT HANDLE: handle=5e9a6868 mtx=5E9A691C(0) cdp=0
namespace=CRSR flags=RON/KGHP/PN0/EXP/[10010100]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=S latch#=1 hpc=c742 hlc=c742
lwt=5E9A68C4[5E9A68C4,5E9A68C4] ltm=5E9A68CC[5E9A68CC,5E9A68CC]
pwt=5E9A68A8[5E9A68A8,5E9A68A8] ptm=5E9A68B0[5E9A68B0,5E9A68B0]
ref=5E9A68E4[662DCE3C,662DCE3C] lnd=5E9A68F0[5E9A68F0,5E9A68F0]
LIBRARY OBJECT: object=51e6451c
type=CRSR flags=EXS[0001] pflags=[0000] status=VALD load=0
DEPENDENCIES: count=1 size=16
AUTHORIZATIONS: count=1 size=16 minimum entrysize=18
ACCESSES: count=1 size=16
TRANSLATIONS: count=1 size=16
DATA BLOCKS:
data# heap pointer status pins change whr
0 a1f966d4 51e645b4 I/P/A/-/- 0 NONE 00
6 662dcce4 a24e2534 I/P/A/-/E 0 NONE 00
KGX Atomic Operation Log 50C2014C
Mutex 662DCC54(0, 2) idn d64ee82 oper SHRD
Cursor Pin uid 145 efd 0 whr 3 slp 0
opr=4 pso=5C5A6334 flg=0
pcs=662DCC54 nxt=5B9C77F4 flg=18 cld=0 hd=5E9A6868 par=54763C50
ct=2 hsh=0 unp=00000000 unn=0 hvl=662dcff0 nhv=0 ses=00000000
hep=662DCCA0 flg=80 ld=1 ob=51E6451C ptr=A24E2534 fex=A24E16F8
SO: 5C76A1D8, type: 53, owner: 5F375F38, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=5c76a1d8 handle=5a67b168 mode=N
call pin=00000000 session pin=00000000 hpc=0000 hlc=0000
htl=5C76A228[5C59D1D0,5C5A6384] htb=5C59D1D0 ssga=5C59CD04
user=5f375f38 session=5f37d6a8 count=1 flags=[0000] savepoint=0x4bc41571
LIBRARY OBJECT HANDLE: handle=5a67b168 mtx=5A67B21C(2) cdp=2
name=
insert into col$(obj#,name,intcol#,segcol#,type#,length,precision#,scale,null$,offset,fixedstorage,segcollength,deflength,default$,col#,property,charsetid,charsetform,spare1,spare2,spare3)values(:1,:2,:3,:4,:5,:6,decode(:5,182/*DTYIYM*/,:7,183/*DTYIDS*/,:7,decode(:7,0,null,:7)),decode(:5,2,decode(:8,-127/*MAXSB1MINAL*/,null,:8),178,:8,179,:8,180,:8,181,:8,182,:8,183,:8,231,:8,null),:9,0,:10,:11,decode(:12,0,null,:12),:13,:14,:15,:16,:17,:18,:19,:20)
hash=012a6293ef607cee606b82dc0d64ee82 timestamp=04-08-2010 17:06:19
namespace=CRSR flags=RON/KGHP/TIM/PN0/LRG/KST/DBN/MTX/[100100d1]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=0 latch#=1 hpc=c298 hlc=c298
lwt=5A67B1C4[5A67B1C4,5A67B1C4] ltm=5A67B1CC[5A67B1CC,5A67B1CC]
pwt=5A67B1A8[5A67B1A8,5A67B1A8] ptm=5A67B1B0[5A67B1B0,5A67B1B0]
ref=5A67B1E4[5A67B1E4,5A67B1E4] lnd=5A67B1F0[5A67B1F0,5A67B1F0]
LIBRARY OBJECT: object=54763bb8
type=CRSR flags=EXS[0001] pflags=[0000] status=VALD load=0
CHILDREN: size=16
child# table reference handle
0 662dd020 662dce3c 5e9a6868
1 662dd020 5b9c7940 5eb1fdbc
DATA BLOCKS:
data# heap pointer status pins change whr
0 54c98590 54763c50 I/P/A/-/- 0 NONE 00
SO: 5C5AFBCC, type: 53, owner: 5F375F38, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=5c5afbcc handle=6ad6312c mode=N
call pin=00000000 session pin=00000000 hpc=0000 hlc=0000
htl=5C5AFC1C[5C61B52C,5C59D0B0] htb=5C59D0B0 ssga=5C59CD04
user=5f375f38 session=5f37d6a8 count=1 flags=[0000] savepoint=0x0
LIBRARY OBJECT HANDLE: handle=6ad6312c mtx=6AD631E0(0) cdp=0
namespace=CRSR flags=RON/KGHP/PN0/EXP/[10010100]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=0 latch#=2 hpc=b9a0 hlc=b9a0
lwt=6AD63188[6AD63188,6AD63188] ltm=6AD63190[6AD63190,6AD63190]
pwt=6AD6316C[6AD6316C,6AD6316C] ptm=6AD63174[6AD63174,6AD63174
SO: 5C5A5C34, type: 53, owner: 5F375F38, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=5c5a5c34 handle=69731e20 mode=N
call pin=00000000 session pin=00000000 hpc=0000 hlc=0000
htl=5C5A5C84[5C59D4D0,5C6074B0] htb=5C59D4D0 ssga=5C59CD04
user=5f375f38 session=5f37d6a8 count=1 flags=[0000] savepoint=0x4bc41571
LIBRARY OBJECT HANDLE: handle=69731e20 mtx=69731ED4(2) cdp=2
name=update con$ set con#=:3 where owner#=:1 and name=:2
hash=cb0043a665029adc35682cfd8f583ce2 timestamp=04-08-2010 17:10:17
namespace=CRSR flags=RON/KGHP/TIM/PN0/SML/KST/DBN/MTX/[120100d0]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=0 latch#=2 hpc=ac50 hlc=ac50
lwt=69731E7C[69731E7C,69731E7C] ltm=69731E84[69731E84,69731E84]
pwt=69731E60[69731E60,69731E60] ptm=69731E68[69731E68,69731E68]
ref=69731E9C[69731E9C,69731E9C] lnd=69731EA8[69731EA8,69731EA8]
LIBRARY OBJECT: object=66177404
type=CRSR flags=EXS[0001] pflags=[0000] status=VALD load=0
CHILDREN: size=16
child# table reference handle
0 5887c454 5887c270 69641ffc
1 5887c454 5887c400 693d29b4
DATA BLOCKS:
data# heap pointer status pins change whr
0 57178070 6617749c I/P/A/-/- 0 NONE 00
SO: 5C62D288, type: 53, owner: 5F375F38, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=5c62d288 handle=5734d800 mode=N
call pin=00000000 session pin=00000000 hpc=0000 hlc=0000
htl=5C62D2D8[5C59D590,5C59D590] htb=5C59D590 ssga=5C59CD04
user=5f375f38 session=5f375f38 count=0 flags=LRU/[4000] savepoint=0x17ee5af
LIBRARY OBJECT HANDLE: handle=5734d800 mtx=5734D8B4(0) cdp=0
name=SYS._default_auditing_options_
hash=fab1a450ca8625c88d7aa501cb042efa timestamp=03-14-2008 18:46:51
namespace=TABL flags=KGHP/TIM/SML/[02000000]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=0 latch#=1 hpc=3e1e hlc=3e1e
lwt=5734D85C[5734D85C,5734D85C] ltm=5734D864[5734D864,5734D864]
pwt=5734D840[5734D840,5734D840] ptm=5734D848[5734D848,5734D848]
ref=5734D87C[5734D87C,5734D87C] lnd=5734D888[5734D888,5734D888]
LIBRARY OBJECT: object=69e8d9e4
type=TABL flags=EXS/LOC[0005] pflags=[0000] status=VALD load=0
DATA BLOCKS:
data# heap pointer status pins change whr
0 572f55b0 69e8da7c I/-/A/-/- 0 NONE 00
SO: 5C62CA38, type: 53, owner: 5F375F38, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=5c62ca38 handle=54e2b2d0 mode=N
call pin=00000000 session pin=00000000 hpc=0000 hlc=0000
htl=5C62CA88[5C7875E0,5C59D458] htb=5C59D458 ssga=5C59CD04
user=5f375f38 session=5f37d6a8 count=1 flags=[0000] savepoint=0x0
LIBRARY OBJECT HANDLE: handle=54e2b2d0 mtx=54E2B384(0) cdp=0
namespace=CRSR flags=RON/KGHP/PN0/EXP/[10010100]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=0 latch#=1 hpc=cb1c hlc=cb1c
lwt=54E2B32C[54E2B32C,54E2B32C] ltm=54E2B334[54E2B334,54E2B334]
pwt=54E2B310[54E2B310,54E2B310] ptm=54E2B318[54E2B318,54E2B318]
ref=54E2B34C[66147E34,66147E34] lnd=54E2B358[54E2B358,54E2B358]
LIBRARY OBJECT: object=51e651ac
type=CRSR flags=EXS[0001] pflags=[0000] status=VALD load=0
DEPENDENCIES: count=1 size=16
AUTHORIZATIONS: count=1 size=16 minimum entrysize=18
ACCESSES: count=1 size=16
TRANSLATIONS: count=1 size=16
DATA BLOCKS:
data# heap pointer status pins change whr
0 6a86de6c 51e65244 I/P/A/-/- 0 NONE 00
6 66147cdc 9dabe588 I/-/A/-/E 0 NONE 00
SO: 5C787590, type: 53, owner: 5F375F38, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=5c787590 handle=57422b64 mode=N
call pin=00000000 session pin=00000000 hpc=0000 hlc=0000
htl=5C7875E0[5C59D458,5C62CA88] htb=5C59D458 ssga=5C59CD04
user=5f375f38 session=5f37d6a8 count=1 flags=[0000] savepoint=0x4bc41571
LIBRARY OBJECT HANDLE: handle=57422b64 mtx=57422C18(2) cdp=2
name=insert into obj$(owner#,name,namespace,obj#,type#,ctime,mtime,stime,status,remoteowner,linkname,subname,dataobj#,flags,oid$,spare1,spare2)values(:1,:2,:3,:4,:5,:6,:7,:8,:9,:10,:11,:12,:13,:14,:15,:16, :17)
hash=8876f3fed7222711572e6a76e623c9d3 timestamp=04-08-2010 17:06:19
namespace=CRSR flags=RON/KGHP/TIM/PN0/MED/KST/DBN/MTX/[500100d0]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=0 latch#=1 hpc=60c0 hlc=60c0
lwt=57422BC0[57422BC0,57422BC0] ltm=57422BC8[57422BC8,57422BC8]
pwt=57422BA4[57422BA4,57422BA4] ptm=57422BAC[57422BAC,57422BAC]
ref=57422BE0[57422BE0,57422BE0] lnd=57422BEC[57422BEC,57422BEC]
LIBRARY OBJECT: object=6a7276e4
type=CRSR flags=EXS[0001] pflags=[0000] status=VALD load=0
CHILDREN: size=16
child# table reference handle
0 66148018 66147e34 54e2b2d0
1 66148018 5896c0ec 6af7d37c
DATA BLOCKS:
data# heap pointer status pins change whr
0 696b76e0 6a72777c I/P/A/-/- 0 NONE 00
SO: 5C78B970, type: 53, owner: 5F375F38, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=5c78b970 handle=54fbd288 mode=N
call pin=00000000 session pin=00000000 hpc=0000 hlc=0000
htl=5C78B9C0[5C787B90,5C59D1B0] htb=5C59D1B0 ssga=5C59CD04
user=5f375f38 session=5f37d6a8 count=1 flags=[0000] savepoint=0x0
LIBRARY OBJECT HANDLE: handle=54fbd288 mtx=54FBD33C(0) cdp=0
namespace=CRSR flags=RON/KGHP/PN0/EXP/[10010100]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=0 latch#=3 hpc=f79a hlc=f79a
lwt=54FBD2E4[54FBD2E4,54FBD2E4] ltm=54FBD2EC[54FBD2EC,54FBD2EC]
pwt=54FBD2C8[54FBD2C8,54FBD2C8] ptm=54FBD2D0[54FBD2D0,54FBD2D0]
ref=54FBD304[5BF92EF0,5BF92EF0] lnd=54FBD310[54FBD310,54FBD310]
LIBRARY OBJECT: object=541e8b98
type=CRSR flags=EXS[0001] pflags=[0000] status=VALD load=0
DEPENDENCIES: count=1 size=16
AUTHORIZATIONS: count=1 size=16 minimum entrysize=16
ACCESSES: count=1 size=16
TRANSLATIONS: count=1 size=16
DATA BLOCKS:
data# heap pointer status pins change whr
0 693cb454 541e8c30 I/P/A/-/- 0 NONE 00
6 5bf92e34 a021d62c I/-/A/-/E 0 NONE 00
SO: 5C787B40, type: 53, owner: 5F375F38, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=5c787b40 handle=5eb09aec mode=N
call pin=00000000 session pin=00000000 hpc=0000 hlc=0000
htl=5C787B90[5C59D1B0,5C78B9C0] htb=5C59D1B0 ssga=5C59CD04
user=5f375f38 session=5f37d6a8 count=1 flags=[0000] savepoint=0x4bc41571
LIBRARY OBJECT HANDLE: handle=5eb09aec mtx=5EB09BA0(2) cdp=2
name=select o.owner#,o.name,o.namespace,o.remoteowner,o.linkname,o.subname,o.dataobj#,o.flags from obj$ o where o.obj#=:1
hash=ae93e4a5100360375a3ff87632f4667e timestamp=04-02-2010 10:17:58
namespace=CRSR flags=RON/KGHP/TIM/PN0/MED/KST/DBN/MTX/[500100d0]
kkkk-dddd-llll=0000-0001-0001 lock=N pin=0 latch#=3 hpc=d23e hlc=d23e
lwt=5EB09B48[5EB09B48,5EB09B48] ltm=5EB09B50[5EB09B50,5EB09B50]
pwt=5EB09B2C[5EB09B2C,5EB09B2C] ptm=5EB09B34[5EB09B34,5EB09B34]
ref=5EB09B68[5EB09B68,5EB09B68] lnd=5EB09B74[5EB09B74,5EB09B74]
LIBRARY OBJECT: object=5bf92fd4
type=CRSR flags=EXS[0001] pflags=[0000] status=VALD load=0
CHILDREN: size=16
child# table reference handle
0 5bf92f60 5bf92d7c 5eb099a8
1 5bf92f60 5bf92ef0 54fbd288
2 5bf92f60 5b9aa120 576a80c8
3 5bf92f60 5b9aa284 54f7a6d0
DATA BLOCKS:
data# heap pointer status pins change whr
0 5eb09a7c 5bf9306c I/P/A/-/- 0 NONE 00

Life time of data in a Global Temporary Table.

Similar Messages

Maybe you are looking for