You are herefmunoz


Colaboraciones y articulos de Francisco Muñoz desde Nueva Zelanda

LOGGING or NOLOGGING, that is the question - Part 2

Redo Generation and Recoverability

The purpose of redo generation is to ensure recoverability. This is the reason why, Oracle does not give the DBA a lot of control over redo generation. If the instance crashes, then all the changes within SGA will be lost. Oracle will then use the redo entries in the online redo files to bring the database to a consistent state. The cost of maintaining the redolog records is an expensive operation involving latch management operations (CPU) and frequent write access to the redolog files (I/O). You can avoid redo logging for certain operations using the NOLOGGING feature.

LOGGING oder NOLOGGING, das ist die frage - Teil 1


Die an mich meistgestellte Frage über NOLOGGING ist: Wenn ich eine Tabelle mit NOLOGGING erstelle, bedeutet das dass “Redo niemals erstellt wird” oder nur dass bei der Initialisierung kein Redo erstellt wird aber DML weiter hinten im Workflow Redo erstellt? Wie und wann kann man NOLOGGING implementieren?

LOGGING o NOLOGGING, he ahi el dilema - Parte 1


La pregunta medular sobre NOLOGGING que escucho todo el tiempo es: ¿Crear una tabla con la opción NOLOGGING significa que “jamas habra generacion de redo”, o solo la operación inicial de creación no tiene generación de redo. Otras interrogantes como: ¿Que sentencias DML generan redo? ¿Cómo y cuando se puede emplear la opción NOLOGGING?

LOGGING or NOLOGGING, that is the question - Part 1


The main question about NOLOGGING I hear all the time is: does creating a table with the NOLOGGING option means there is “no generation of redo ever”, or just that the initial creation operation has no redo generation, but that DML down the road generates redo? How and when can the NOLOGGING option be employed?


Syndicate content

Follow DatabasesLA on Twitter

Who's online

There are currently 0 users and 3 guests online.


Locations of visitors to this page

hidden hit counter