Failure on attempt to Declare Global Temporary Table

I am working with SAP and I am seeing the following error on the REAL TIME STATISTICS DATABASE on any attempt to declare a global temporary table by any process:
On the following attempt
DECLARE GLOBAL TEMPORARY TABLE SESSION.FILL_STAT_TAB_TMP
AS ( SELECT IXNAME, IXCREATOR,
FAROFFPOSF, NEAROFFPOSF, LEAFDIST FROM SYSIBM.SYSINDEXPART )
DEFINITION ONLY CCSID UNICODE ON COMMIT DROP TABLE
I get the following error
DSNT408I SQLCODE = -904, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY AN
UNAVAILABLE RESOURCE. REASON 00C90081, TYPE OF RESOURCE 00000100, AND
RESOURCE NAME DSNRTSDB
DSNRTSDB appears to be started. I have EXPLICITLY started it. I have dropped and recreated the RTS tables, starting the database again. We have a temp database created, and 2 tablespaces created in the temp database, one of page size 4k and the other of pagesize 8k.
I am able to query the RTS tables with no problem.
We have 8 other subsystems that we migrated to v8 that have no problems. This particular subsystem was an install, but what that might have to do with anything I don't know.
What am I missing?
Thanks.

Hi,
sorry, i've no answer only another question.
I'm searching with google on 'FILL_STAT_TAB_TMP' and this post is all i get ;-(
My problem is a little bit different.
I'm doing a RUNSTATS with DB20 or DB13 and it works. But in the SM21 appears this:
ST04: [IBM][CLI Driver][DB2] DSNT408I SQLCODE = -204, ERROR: SESSION.FILL_STAT_TAB_TMP IS AN UNDEFINED NAME
But if i put the statement from Steve above into spufi, it works without error.
The dis database(dsnrtsdb) shows this:
NAME     TYPE PART STATUS
DSNRTSTS TS         RW
INDEXSPA IX         RW
TABLESPA IX         RW
Kay

Similar Messages

Cannot create Global Temporary Table

Hi,
i'm trying to create a Global Temporary Table. However I receive a missing or invalid options specified error.
This should be one of the most simple ways to create a Global Temporary Table right?
DECLARE GLOBAL TEMPORARY TABLE SESSION.T_MECHANIC_ALLOCATION
START_TIME DATE
,SYSUR_AUTO_KEY NUMBER
,EPP_AUTO_KEY NUMBER
,STOP_TIME DATE
,WOK_AUTO_KEY NUMBER
ON COMMIT DELETE ROWS

No, you create a Global Temporary Table in the same way as any other table: beginning with the CREATE keyword:
CREATE GLOBAL TEMPORARY TABLE T_MECHANIC_ALLOCATION
START_TIME DATE
,SYSUR_AUTO_KEY NUMBER
,EPP_AUTO_KEY NUMBER
,STOP_TIME DATE
,WOK_AUTO_KEY NUMBER
ON COMMIT DELETE ROWS

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

How Create a Global Temporary Table inside a Stored Procedure?

Hi...
I need to create a Global Temporary Table inside a Stored
Procedure....
I have no idea how to do that....
Please....if u can send me a sample, send to me....
Thanks a lot

there are many ways to do this..
one u can use dbms_utility package to run ddl statements like
for ex:
declare
t varchar2(200):='order_no';
v number;
begin
--dbms_utility.exec_ddl_statement('select '||t||' into '||v||'
from
--ordermaster where rownum=1');
dbms_utility.exec_ddl_statement('create table cvt(t number)');
dbms_output.put_line(v);
end;
but the actual method(recommended) involves a bit coding using
dbms_sql package you will find examples on technet or metalink
to use this package..
I hope this helps
Narendra

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.

Dropping global temporary table

Hi: I am on 10.2.0.3.
I have an interesting problem with global temporary tables.
I created a few and was using them for awhile.
Now I am trying to drop one (it has a couple indexes as well) and here is what I am getting:
SQL> drop table sysadm.PS_BPA_RATES_TA011;
drop table sysadm.PS_BPA_RATES_TA011
ERROR at line 1:
ORA-14452: attempt to create, alter or drop an index on temporary table already in use
Needless to say I checked the active sessions (using v$session) but there is none which locks this table.
I truncated it (although it had 0 rows but I was trying to free up space), also tried to flush shared_pool & buffer_cache (it's a test DB) - which were successful but did not help - I am getting the same error.
Someone suggested checking V$TEMPSEG_USAGE where segtype='DATA'. This view shows 3 rows with session# & sql_id but both does not show any session:
SQL> select * from V$TEMPSEG_USAGE where segtype='DATA';
USERNAME USER SESSION_ADDR SESSION_NUM SQLADDR SQLHASH SQL_ID
TABLESPACE CONTENTS SEGTYPE SEGFILE# SEGBLK# EXTENTS BLOCKS SEGRFNO#
SYSADM SYSADM C00000021C1D2318 123 C0000002DB467ED0 146923226 0ahnqxh4c3rqu
TEMP TEMPORARY DATA 204 465289 1 128 4
SYSADM SYSADM C00000021C1CE508 32644 C00000021B6D3F58 2784120300 0c5411akz4mgc
TEMP TEMPORARY DATA 204 506761 14 1792 4
SYSADM SYSADM C00000021C1CE508 32644 C00000021B6D3F58 2784120300 0c5411akz4mgc
TEMP TEMPORARY DATA 204 505993 1 128 4
SYSADM SYSADM C00000021C1CE508 32644 C00000021B6D3F58 2784120300 0c5411akz4mgc
TEMP TEMPORARY DATA 204 505865 1 128 4
SQL> select session_num,sql_id from V$TEMPSEG_USAGE where segtype='DATA';
SESSION_NUM SQL_ID
123 0ahnqxh4c3rqu
32644 0c5411akz4mgc
32644 0c5411akz4mgc
32644 0c5411akz4mgc
SQL> select sid,serial#,process from v$session where sql_id='0ahnqxh4c3rqu';
no rows selected
SQL> select sid,serial#,process from v$session where sid=32644;
no rows selected
I know that recycling the database should help but I can not do it right now - and I am sure there should be a solution.
Any help appreciated. TIA,
GregX

I found a solution to this.
You have to use V$TEMPSEG_USAGE where segtype='DATA'.
Column session_num corresponds to serial#. The job was canceled from the front end but this session was still hanging in there. After I killed it the drop worked.
Lots of people are saying that truncate should help with this problem. That's not true.

Global Temporary Table - Nulls Returned.

Hello,
I have written a search, which has one text box and scans across many different fields in a table. If you have multiple search terms separated by commas, I look for the results to have BOTH. The same would apply for even more search terms.
To accomplish this I do the following:
-- 1.) split the string with function, receive array of search terms.
-- 2.) LOOP: Open Loop and move to first element of Array.
-- 3.) find individual term (array element) in table (fields in question use CONTEXT indexing).
-- 4.) Place list of results (PK) into Global Temporary table.
-- 5.) Move to next array position.
-- 6.) Repeat steps 3,4,5 until array is exhausted
-- 7.) END LOOP:
-- 8.) select PK list having COUNT(*) = # of terms in array.
-- 9.) Select data from main table where pk in (list of terms from temp table).
The procedure works fine in PL/SQL Developer and Toad. The results are reliable and accurate.
When we try to run this through JDeveloper - we have problems. Either we get a return set of "NULL", or we get odd results that imply that the search has run through only one term of the two.
We have researched this and setAutoCommit off.
I am reaching out for suggestions on additional things which might be interfering with the Java connection, before I attempt to place a support call to Oracle.

Not sure were can help you as this its a complicated use case which can't be rebuild easily by us.
Still, you should medium your jdev version and how you call the pl /sql function which produces three results in the global Temp table.
Can you please explain when exactly you get null or funny results?
I have worked with temp take a while back and had no such issues.
Timo

Problem with Create global temporary table command

Hi,
Following is the query i am using in one of my pl/sql report..
EXECUTE IMMEDIATE 'CREATE GLOBAL TEMPORARY TABLE Billing_Report_Table ON COMMIT PRESERVE ROWS as select * from (Vc_Sql_Statement)';
Error message i am getting when i run the report is "missing SELECT keyword"
The variable Vc_Sql_statement contains a complex query retrieving data from different tables.
Please help me out.
Thanks in advance
Shanthi

Hi,
SCOTT@soti_9> DECLARE
2    Vc_Sql_Statement VARCHAR2(30) := 'DUAL';
3 BEGIN
4    EXECUTE IMMEDIATE
5      'CREATE GLOBAL TEMPORARY TABLE Billing_Report_Table ON COMMIT PRESERVE ROWS AS ' ||
6      ' select * from ' || Vc_Sql_Statement;
7 END;
8 /
PL/SQL procedure successfully completed.
SCOTT@soti_9> select * from Billing_Report_Table;
D
XRegards,
Dima

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

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.

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

How can i create a Global Temporary Table inside a Stored Procedure....

Hi...
I need to create a Global Temporary Table inside a Stored
Procedure....
I have no idea how to do that....
Please....if u can send me a sample, send to me....
Thanks a lot

To create a global temporary table inside a stored procedure,
the minimal syntax would be:
CREATE OR REPLACE PROCEDURE procedure_name
AS
BEGIN
EXECUTE IMMEDIATE 'CREATE GLOBAL TEMPORARY TABLE table_name'
|| '(column_name NUMBER)';
END procedure_name;
As Todd stated, it would probably be better to create the global
temporary table outside of the procedure:
SQL> CREATE GLOBAL TEMPORARY TABLE table_name
2 (column_name NUMBER);
Table created.
You can also specify things like ON COMMIT PRESERVE ROWS or ON
COMMIT DELETE ROWS.
It may be that there is something else, like a PL/SQL table of
records or a cursor, that would suit your needs better. It is
difficult to guess without knowing what you want to do with it.

Creating a Global Temporary Table on non-default TEMP tablespace.

Hello ,
I am using Oracle 11g.
I have a procedure which create global temporary tables for its functionality. As the data which is going in the global temporary table , mean the data which is going in the default TEMP tablesapce is too huge ..... billions of rows..
So what i want to do is , I want to create the global temporary table in another TEMP2 tablespace ( which is not the default one) so the load of billions of rows of data will be shifted to TEMP2. The default TEMP tablespace will not be affected and it can be used for other transactions.
Is this possible. Can i shift the global temporary table from TEMP( Default temp tablespace) to TEMP2 ( the non-default temp tablespace) ????
Please guide me with proper solutions and examples ....
Thanks in advance ..

DBA4 wrote:
Hello ,
I am using Oracle 11g.
I have a procedure which create global temporary tables for its functionality. As the data which is going in the global temporary table , mean the data which is going in the default TEMP tablesapce is too huge ..... billions of rows..
So what i want to do is , I want to create the global temporary table in another TEMP2 tablespace ( which is not the default one) so the load of billions of rows of data will be shifted to TEMP2. The default TEMP tablespace will not be affected and it can be used for other transactions.
Is this possible. Can i shift the global temporary table from TEMP( Default temp tablespace) to TEMP2 ( the non-default temp tablespace) ????
Global temporary tables are instantiated in the temporary tablespace of the schema that inserts the data - not into "the default" temporary tablespace.
Assume Schema1 creates a GTT and grants all on that table to schema2
Assume schema1 also creates a procedure (authid owner, the default) to insert data into the GTT and grants execute on the procedure to schema2
If schema2 executes: insert into schema1.gtt, the data will appear in the temporary tablespace of schema2
If schema2 executes: execute schema1.procedure, the data will appear in the temporary tablespace of schema1
So if you want to protect the "normal" temporary tablespace, you could just create a special temporary tablespace for the owner of the procedure.
Regards
Jonathan Lewis

Transaction with Global Temporary Table

Problem:
Transaction starts with few DML statements and in the middle we are calling a JAVA method which creates the dynamic global temporary table and proceeding with few DML statements, if one of the statement fails, in the exception clause we are trying to rollback and transactions after the DDL (create global temp table) are rolled back and transactions before the DDL (create global temp table) are committed.
We cannot pre-create the global temporary table, since we do not know the number of temp table to be pre-created.
How we can resolve this issue? The same concept works for SQL server.
Example of our issue:
--drop table table1 purge;
--drop table t_id purge;
Create table table1 (col1 number, col2 varchar2(20));
Insert into table1 values (1, 'Test1');
Create global temporary table t_id (id number);
Insert into table1 values (2, 'Test2');
Rollback;
After the rollback you can see only the 'Test1' record.

> We cannot pre-create the global temporary table, since we do not know the number of temp table to be pre-created.
I don't see how one procedure could need to create an unknown number of temporary tables. Do they all have different (and unknown) column lists? Couldn't you combine them into a single table with a key to distinguish betweeen the different sets of rows?

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.

Failure on attempt to Declare Global Temporary Table

Similar Messages

Maybe you are looking for