Multisession and multiuser login issue...

Question

Hi ,
I am having below database objects like below.
CREATE TABLE test_table_1
(id      NUMBER,
col1 VARCHAR2(20 BYTE)
CREATE OR REPLACE PACKAGE pack1
IS
TYPE global_cursor IS REF CURSOR;
END;
CREATE OR REPLACE PROCEDURE test_proc (out_cursor OUT pack1.global_cursor)
IS
BEGIN
EXECUTE IMMEDIATE 'TRUNCATE TABLE TEST_TABLE_1';
INSERT INTO test_table_1
SELECT 1, 'test' FROM DUAL; /* this value is coming dynamically and its different for every user */
COMMIT;
OPEN out_cursor FOR SELECT * FROM test_table_1;
END;
Above procedure is used in multisession. I have doubt if someone truncate the table just after the commit because
I am returning table dataset using cursor out_cursor. Basically i want to open cursor always after commit.
Please suggest me in this.

Answer 1

Rajiv-883452 wrote:
I am inserting data just because of intermediate data which comes dynamically. I don't understand what this means.
I can not use global temporary table because of the amount of data insert in table. That doesn't make sense. What resource does a temporary table use that a permanent table does not use that you are concerned that you'll run out of?
If I will use global table then it may create performance issue. I don't understand. What performance issue are you concerned about? Why would a temporary table create a performance issue that a permanent table would not?
I am having same scenario in production database for reporting. I don't understand what you are trying to say here.
Justin