On 5/1/06, Tomi Wijanto <[EMAIL PROTECTED]> wrote:
> Kalau kamu baca2 asktom.oracle.com, akan ketemu 2 hal
> berikut:
> - Pemisahan data dan index tidak memiliki alasan yg
> kuat, karena dari satu session index dan data tdk
> pernah diakses bareng.
> - Mengeset NOLOGGING mesti hati2 karena setelah
> operasi nologging (operasi yg miminimalkan redo),
> datafile yg terlibat seharusnya dibackup. Atribut
> nologging pada index hanya mempunyai efek pada waktu
> create/rebuild.

Nice info, thanks. Sudah lama tidak jalan2 ke asktom, dan ternyata ada
info update
http://asktom.oracle.com/pls/ask/f?p=4950:8:12808088269233738862::NO::F4950_P8_DISPLAYID,F4950_P8_CRITERIA:901906930328

----
I believe some of the confusion comes from Oracle's own training material.

If you look at the current books for 9i on page 3-4 of the Performance & Tuning
Training Manual, it states the following:

Tables and indexes should be split into separate tablespaces, because indexes
and tables are often inserted into and read from simultaneously.

I would definitely think this to mean, put data and indexes in separate
tablespaces.

Regards,
Doug

Followup:

yes, that finally got corrected in the current docs.
---

Di link tsb jg disebutkan, index dan data dipisah, lebih karena
administratif. Jika index datafile rusak, lebih mudah rebuild daripada
restore nya.


--
-----------I.N.D.O - O.R.A.C.L.E---------------
Keluar: [EMAIL PROTECTED]
Website: http://indo-oracle.lizt.org (NEW)
-----------------------------------------------

Bergabung dengan Indonesia Thin Client User Groups,
Terminal Server, Citrix, New Moon Caneveral, di:
http://indo-thin.vze.com




SPONSORED LINKS
Membership database software Database mortgage software Pda database software
Database management software Oracle database administration Oracle database management


YAHOO! GROUPS LINKS




Kirim email ke