Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.
Solved
nologging
Posted on 2010-11-28
When we create table we use nologging attribute.
Could you please explain why we use that?
Could you please explain why we use that?
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2-
2
- +1
6 Comments
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.
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.
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>
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>
Active 7 days ago
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.
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.
Featured Post
Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Working with Network Access Control Lists in Oracle 11g (part 2)
Part 1: http://www.e-e.com/A_8429.html
Previously, I introduced the basics of network ACL's including how to create, delete and modify entries to allow and deny access. For many…
I remember the day when someone asked me to create a user for an application developement. The user should be able to create views and materialized views and, so, I used the following syntax:
(CODE)
This way, I guessed, I would ensure that use…
This video shows how to copy a database user from one database to another user DBMS_METADATA. It also shows how to copy a user's permissions and discusses password hash differences between Oracle 10g and 11g.
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function
Suggested Courses
Course of the Month5 days, 1 hour left to enroll
670 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.