Answer / 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.

Can we create non-clustured index on a clustered index ?

4 Answers   TCS,

---

What are pl sql data types?

0 Answers  

---

Explain architecture of sql server notification services?

0 Answers  

---

Explain mutating table error.

0 Answers  

---

What is the need of a partition key?

0 Answers  

---

What are all ddl commands?

0 Answers  

---

What is recursive stored procedure?

0 Answers  

---

What is a data manipulation language?

0 Answers  

---

What is type and rowtype in pl sql?

0 Answers  

---

What is multiple columns?

0 Answers  

---

Explain some predefined exceptions.

0 Answers  

---

What is the difference between an inner and outer join?

0 Answers  

---