Answer Posted / sreemanth reddy

hi
You can not specify a tablespace with global temporary
tables. GTT's are built in the TEMP tablespace.
Global temporary tables have three major benefits:

1. Non-interference between private sets of data.

2. Ease of getting rid of 'scratch' data. In a heap table
you either rollback, or delete it. But in a GTT, you can
truncate explicitly, without affecting anyone else (or allow
the implicit "truncate on commit / exit" effect to do
the same thing).

3. Decreased redo generation as, by definition, they are
non-logging.

However:

Mixing temporary tables (GTTs) with permanent tables usually
causes some grief to the CBO. It has no information
about the number of rows in the GTT, and therefore guesses
(badly).

Even if you analyze table .. or
dbms_stats.gather_table_stats() you don't get stats on the
temporary table.

Set the init parameter dynamic_sampling to at least 2 for
GTTs to be sampled at run-time.

Note: All DDL includes two implicit commits so any rows in a
GTT specified with ON COMMIT DELETE ROWS will empty the
table.

What are sql indexes?

1040

---

Are left and right joins the same?

1154

---

what is row? : Sql dba

1274

---

Is not equal in sql?

1056

---

What are sql triggers used for?

1031

---

What is orm in sql?

1096

---

what is a control file ? : Sql dba

1084

---

What is group function in sql?

1058

---

What is sqlerrd?

1011

---

Explain the purpose of %type and %rowtype data types with the example?

1043

---

What do you mean by dbms? What are its different types?

1058

---

What do you mean by field in sql?

1121

---

Define select, insert, create, delete, update, drop keywords

1088

---

What is meant by user defined function?

1094

---

What is an oracle stored procedure?

1110

---