NOLOGGING Option on Create Table

I included the NOLOGGING option on a "create table ..." statement, but it is not having the desired affect. Updates to the table are still being logged and archived.

The problem is that a vendor product is using an Oracle table as a "process queue" which is generating too many redo log entries, and subsequently too many archived redo logs. During our tests, we are archiving 30MB per minute for a 100 person simulation. There will be over 500 persons on the system in production. I want to reduce this archiving to minimize logger overhead and to conserve disk space.

Should this option have the affect I'm looking for? We have also thought of moving the table to its own database with noarchivelog, but that seems like overkill. Seems there should be dsome way to do this. The rows in this table are transitory and I will never need to recover them. Received on Sat Apr 06 2002 - 10:27:58 CST