In this chapter, we investigated how to measure redo. We also looked at the impact that NOLOGGING has on redo Read More
In the last chapter, we briefly investigated the ORA-01555 error and looked at one cause of it: committing too frequently. Read More
In regard to undo generation, private temporary tables behave similar to global temporary tables. We can see that by running Read More
This behavior will most affect you after a large INSERT (as just demonstrated), UPDATE, or DELETE—one that affects many blocks Read More
There are two ways to use the NOLOGGING option. You have already seen one method— embedding the NOLOGGING keyword in Read More
Upon startup, Oracle would read the redo log files and find some redo log entries for our transaction. Given the Read More
You can instruct Oracle to store the undo for a temporary table in a temporary tablespace via the TEMP_UNDO_ENABLED parameter. Read More
Surprisingly to many people, the SELECT will have generated redo. Not only that, but it will also have “dirtied” these Read More
Now, earlier I mentioned that we were using a Java program and not PL/SQL for a reason—and that reason is Read More
This question is often asked. The simple short answer is no, since redo logging is crucial for the database; it Read More