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

Similar Messages

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

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

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.

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.

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

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

Clearing out global temporary tables in a session.

I have a global temporary table that is used within one stored procedure. Another procedure calls it twice in succession and the second time the child SP is called, the temp table is retaining the values from the first call. I want to clear the contents of the temp table before the child SP completes, but am getting an "invalid table name" error when I try to truncate it or delete the contents. Any thoughts?
By the way, when I created the global temp table, I used 'on commit delete rows'
Thanks
Matt

I have a global temporary table that is used within
one stored procedure. Another procedure calls it
twice in succession and the second time the child SP
is called, the temp table is retaining the values
from the first call. I want to clear the contents of
the temp table before the child SP completes, but am
getting an "invalid table name" error when I try to
truncate it or delete the contents. Any thoughts?
By the way, when I created the global temp table, I
used 'on commit delete rows'
Thanks
MattCan you paste the create table script of the table?

ORA-00955 reports when I try to "create global temporary table" in windows

Hi,
When I try to run the sql in my oracle 9i server which is installed in a windows2000 machine,
Create global temporary table test ...;
For the first time, I can create table successfully.
But I cannot access this table any more:
drop table test;
desc test;
select * from test;
In addition, if I try to create the table again, I got the error:
ORA-00955: name is already used by an existing object
While the same table can be created and dropped in another oracle9i server which is installed in Solaris 9 machine.
So I suspect that this sould be a bug of window oracle server.
Is there anyone who can confirm this?
Or who can tell me how to report this bug to oracle?
Thanks in advance.
Please also refer the message at:
http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:1046974576560
If you search the text: "create global temporary table sess_event", you can see for the first time, the table is created successfully.
But the ORA-00955 reports when the author try to create table for the second time.
This problem is exactly the same as my problem.
I have also made a search both in Google and in Oracle website and I cannot find any solution of it.

Read Metalink Note:68098.1 Subject: Overview of Temporary Tables
How did you difine the temporary tables? on commit delete rows are reserv rows?
http://download-west.oracle.com/docs/cd/B10501_01/appdev.920/a96590/adg03sch.htm#7794
Jaffar
Message was edited by:
The Human Fly

When to use global temporary tables?

which are the probable situations when one can think of using global temporary tables?

In my experience, most often GTTs are used by developers from other RDBMSs who have become used to needing 'intermediate tables' created on the fly to hold data while they 'loop and commit to free locks'.
These developer may not have had enough exposure to Oracle's concurrency model and therefore use the 'other' concurrency model as the basis for an application port - usually followed up by a call to the forum for assistance in performance tuning. <g>
That said, legitimate uses for GTTs include staging or scrubbing table for data transport or preparation, eg: ETL into a warehouse, when the intermediate data is
a) reproducible (therefore does not need to be logged); and
b) the results of the intermediate operation, but not the source, are stored in permanent tables.
Some developers also use GTTs to hold the equivalent to a 'temporary materialized view' specifically for complex reporting purposes.

Global Temporary Table not deleting Rows

why is my Global temp table not deleting the rows after commit see below,
CREATE GLOBAL TEMPORARY T_CHG
TBE VARCHAR2(7),
ABC VARCHAR2(8),
EFDA VARCHAR2(6),
ABD VARCHAR2(9),
A_ID VARCHAR2(128),
C_DATE,
ON COMMIT DELETE ROWS;

Quite a few syntax issues with your create statement. It would have helped if you had posted a SQL*Plus session showing your results. Here is mine which works just fine:
sql>create global temporary table t_chg
2 (
3 tbe varchar2(7),
4 abc varchar2(8),
5 efda varchar2(6),
6 abd varchar2(9),
7 a_id varchar2(128),
8 c_date date
9 )
10 on commit delete rows;
Table created.
sql>insert into t_chg values ('1', '2', '3', '4', '5', sysdate);
1 row created.
sql>select count(*) from t_chg;
COUNT(*)
1
1 row selected.
sql>commit;
Commit complete.
sql>select count(*) from t_chg;
COUNT(*)
0
1 row selected.

Problem ! Calling report6 from forms6(run_product()) using global temporary table.

Requirement :
To generate stock movement report for certain selected items.
Background :
A Form is created with data block (tmp_item_master - a global temporary table)
when_new_form_instance :
inserting into tmp_item_master from item_master and then execute_query on tmp_item_master block.
User selects certain items using check box provided.
Now tmp_item_master is updated for ch_select_flag_yn = 'Y' for selected items
and commit.
Calling report from form(using run_product()).
Now the main query in report, is joined with tmp_item_master where ch_select_flag_yn = 'Y'
Here, we are unable to see the report for any item. As the global temporary table data is not visible in the report session.
How to resolve this problem ?
Note : global temporary table created with ON COMMIT PRESERVE ROWS
Thanking you,
From praful.
null

Hi,
You are using 'ON Commit Delete Rows' . Instead of Use ' ON COMMIT PRESERVE ROWS'
The ON COMMIT DELETE ROWS clause indicates that the data should be deleted at the end of the transaction.
CREATE GLOBAL TEMPORARY TABLE my_temp_table (
column1 NUMBER,
column2 NUMBER
) ON COMMIT DELETE ROWS;
In contrast, the ON COMMIT PRESERVE ROWS clause indicates that rows should be preserved until the end of the session.
CREATE GLOBAL TEMPORARY TABLE my_temp_table (
column1 NUMBER,
column2 NUMBER
) ON COMMIT PRESERVE ROWS;
Edited by: Mrucha on Nov 26, 2012 6:06 AM

Create global temporary table in delete trigger

Hi to all, I am triyng to create a global temporary table in trigger so i can hold all the deleted rows and do some stuff after the statement which uses the table that fires the trigger.
In this way I am trying to avod mutating table error. but the following trigger gives error.
create or replace
TRIGGER TD_EKSINAVLAR
FOR DELETE ON DERSSECIMI_EKSINAVLAR
COMPOUND TRIGGER
BEFORE STATEMENT IS
BEGIN
CREATE GLOBAL TEMPORARY TABLE DELETED_ROWS
AS ( SELECT * FROM DERSSECIMI_EKSINAVLAR WHERE 1 = 2 )
ON COMMIT DELETE ROWS;
END BEFORE STATEMENT;
BEFORE EACH ROW IS
BEGIN
NULL;
END BEFORE EACH ROW;
AFTER EACH ROW IS
BEGIN
NULL;
END AFTER EACH ROW;
AFTER STATEMENT IS
BEGIN
NULL;
END AFTER STATEMENT;
END TD_EKSINAVLAR;
the error is
Error(12,5): PLS-00103: Encountered the symbol "CREATE" when expecting one of the following: ( begin case declare exit for goto if loop mod null pragma raise return select update while with <an identifier> <a double-quoted delimited-identifier> <a bind variable> << continue close current delete fetch lock insert open rollback savepoint set sql execute commit forall merge pipe purge
Please help me about the situation.
Thanks in advance.
Gokhan

Karthick you are absolutly right
Our main process is to migrate sql server 2000 database to oracle 11g and I am stuck with the triggers that reference to table that fires the trigger itself.
Can you help me about how i can overcome mutating table errors using compund triggers? Espacially for the situation that one statement tries to update or delete multiple rows on a table.
You can understand my logic from the above code. I want to hold all the affected rows in a table and in after statement body using a cursor on that table I want to do required changes on the table. How can I do that or how should I do ?
regards.

Global temporary table in PL/SQL called from APEX page

I have a global temporary table in a PL/SQL procedure that is called from an APEX page.
The global temp table is populated with data as the procedure runs and then at the end of the procedure I do a create_collection_from_query_b to populate a collection with the data from the temp table. (I do this b/c it is much faster than creating the collection and doing an add_member for each row.)
The problem is that there are no commits in my procedure but I cannot get the bulk insert to work unless I define the temp table as on commit preserve rows.
Can anyone shed any light on this issue.
Thanks,
Andrew

alamantia wrote:
My PL/SQL procedure is called from an after submit page process. Does that imply that there is a commit happening after that process is successful?Ultimately, yes.
If the process calls the PL/SQL procedure and the temp table is in the procedure, wouldn't the commit fire after all the PL/SQL code is complete which would be after the bulk insert from the temp table to my collection?Yes, but at any point in the procedure containing code like
:APEX_ITEM := ...or
select ... into :APEX_ITEM from ...or
my_procedure(p_in => ..., p_out => :APEX_ITEM, ...);or
apex_util.set_session_state(...);then APEX will commit whilst maintaining session state.
If you don't have any of these events in the procedure, then test to see if the commit is occurring in <tt>apex_collection.create_collection_from_query_b</tt> prior to creation of the collection.

Performance slow on DELETE command on global temporary table!

Hi,
I have a delete on a global temporary table that is taking long time!.
Anyone have a clue about how to improve delete command's against global temporary table??
Tks,
Paulo Portugal

Same problem here!
<QUOTE>
SELECT DISTINCT PDT_CHILD.SUP_ID, PDT_CHILD.SUB_ID,
PDT_CHILD.SUB_LEAF_FLAG_ID
FROM
PJI_FP_AGGR_RBS_T PDT_CHILD WHERE 1=1 AND PDT_CHILD.SUP_ID = :B2 AND
PDT_CHILD.SUP_ID <> PDT_CHILD.SUB_ID AND PDT_CHILD.WORKER_ID = :B1
call count cpu elapsed disk query current rows
Parse 1 0.00 0.00 0 0 0 0
Execute 88561 20.71 20.23 0 0 0 0
Fetch 90269 926.19 906.80 45 45164134 0 176545
total 178831 946.91 927.03 45 45164134 0 176545
Misses in library cache during parse: 0
Optimizer mode: ALL_ROWS
Parsing user id: 173 (APPS) (recursive depth: 1)
Rows Execution Plan
0 SELECT STATEMENT MODE: ALL_ROWS
0 HASH (UNIQUE)
0 TABLE ACCESS (FULL) OF 'PJI_FP_AGGR_RBS_T' (TABLE (TEMP))
Elapsed times include waiting on following events:
Event waited on Times Max. Wait Total Waited
---------------------------------------- Waited ---------- ------------
latch: row cache objects 1 0.00 0.00
direct path write temp 3 0.00 0.00
direct path read temp 3 0.00 0.00
</QUOTE>
The fetch is too high for TEMP table... Any help would be much appreciated!
Note: Please teach me on how we can format the above in my future posts in OTN forums.
===

Datas deletion from Global Temporary table when clear command is given

Similar Messages

Maybe you are looking for