nologging

When we create table we use nologging attribute.
Could you please explain why we use that?
nobleitAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
0
 
nobleitAuthor Commented:
Could you explain in a simple way..
Thanks..
0
 
Guy Hengel [angelIII / a3]Billing EngineerCommented:
it means that IF you have the table in NOLOGGING mode AND you run the INSERT in "APPEND" mode (hint /*+APPEND*/, then the insert (data) is not logged in the redo log, but only the statement as such.
normally, all DML statements are logged along with the data they modify. this can, escecially for large data updates/deletes/insert result in big archive logs.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
fhsyedCommented:
There are many uses in verity of different ways for LOGGING/NOLOGGING
Exert is from Tom .

<quote>
LOGGING|NOLOGGING

LOGGING|NOLOGGING specifies that subsequent Direct Loader (SQL*Loader) and direct-load
INSERT operations against a nonpartitioned index, a range or hash index partition, or
all partitions or subpartitions of a composite-partitioned index will be logged (LOGGING)
or not logged (NOLOGGING) in the redo log file.

In NOLOGGING mode, data is modified with minimal logging (to mark new extents invalid
and to record dictionary changes). When applied during media recovery, the extent
invalidation records mark a range of blocks as logically corrupt, because the redo data
is not logged. Therefore, if you cannot afford to lose this index, you must take a backup
after the operation in NOLOGGING mode.

If the database is run in ARCHIVELOG mode, media recovery from a backup taken before an
operation in LOGGING mode will re-create the index. However, media recovery from a backup
taken before an operation in NOLOGGING mode will not re-create the index.
An index segment can have logging attributes different from those of the base table and
different from those of other index segments for the same base table.
</quote>

0

Experts Exchange Solution brought to you by ConnectWise

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
 
AnandCommented:
DBA's tend to look at nologging options for tables to reduce the overhaed on archive logging process.
In environments like bulk data loading, dataware house environments, because of the huge data pumped in to the database, check point tuning and archiver tuning will always be a challenge to the DBA's. If business can afford to reload the data to certain hot tables incase of crash/failure, then it is wonderful opportunity for DBA's to enable no logging on those tables.So data will not flow through the redologs/archive logs, burden on archiver writing will be reduced which will improve the response time of the database. Majority of the times, log file sync, log file parallel write are the top events wainting in the databases where high data loading takes places.
NoLogging is one quick/calculated risk method to quickly tackle the CheckPoint/Archiver tuning.
0
 
nobleitAuthor Commented:
Sorry for the delay. The issue is solved. Thank you for all your support..
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.