shasta123
asked on
Diasable redo log for the table
I have a table which is heavily inserted with data periodically and goes to the order of 5G over the period of 20days and then it is cleaned by trigger. So given point of time it holds only last 20days worth of data.
Question is I want to disable the redo log for this table so that when I recover the database I can skip this table as the data is not critical to recover and we can improve the recovery time by skipping it.
What is the best way to do it, I know there is NOARCHIVELOG option I can set, but according to ORacle documentation that one still generates logs and not reliable.
Any ideas?
Question is I want to disable the redo log for this table so that when I recover the database I can skip this table as the data is not critical to recover and we can improve the recovery time by skipping it.
What is the best way to do it, I know there is NOARCHIVELOG option I can set, but according to ORacle documentation that one still generates logs and not reliable.
Any ideas?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have not forgotten your replies, trying to digest them all.
ASKER
Sorry for the late reply, but our table is not loaded once in bulk so that i could use the direct path serial load.
It is a table which is inserted by a server process periodically? How do i skip the redo for this table so that for recovery i can skip this table ?
It is a table which is inserted by a server process periodically? How do i skip the redo for this table so that for recovery i can skip this table ?
Does your "server process" that does the inserts use this syntax: "insert into [table_name] ... select ... from [some other table(s) or view(s)]"?
If not, and you can't use a direct path load either, then no, you cannot disable redo logiing for this table.
What does your "server process" look like? Is it a stored procedure?
If not, and you can't use a direct path load either, then no, you cannot disable redo logiing for this table.
What does your "server process" look like? Is it a stored procedure?
Also, if you are only inserting one or two records, you wouldn't want to use direct path. It only makes sense if you are really doing a bulk insert.
NOARCHIVELOG only avoids dumping out the redo log into .arc files (for recovery), but that's all.
the only thing you can do is ensure that the redo logs are big enough, that you have a couple of them, and that they are located on the fastest disks on your sever.