Home » SQL & PL/SQL » SQL & PL/SQL » Logging vs. Nologging
Logging vs. Nologging [message #1377] Wed, 24 April 2002 11:01 Go to next message
bill
Messages: 75
Registered: November 1999
Member
I have a procedure which preforms an archiving process on two tables. It processes about 15 million records. First finding the eligible records ... Inserting them into archive tables ... and if the insert is successful ... deletes the original records.

Huge log files are produced durring execution. Is there a way to prevent these log files from being written without altering the Table or Tablespace?

Thanks

Report message to a moderator

Re: Logging vs. Nologging [message #1378 is a reply to message #1377] Thu, 25 April 2002 00:02 Go to previous messageGo to next message
sai sreenivas jeedigunta
Messages: 370
Registered: November 2001
Senior Member
Your Question itself is containing the answer..just use the option Nologgin along with the insert statement..then Data Logs will not be used...

i think this will solve u r problem..
SAI

Report message to a moderator

Re: Logging vs. Nologging [message #1385 is a reply to message #1377] Thu, 25 April 2002 04:29 Go to previous message
bill
Messages: 75
Registered: November 1999
Member
DO you mean /*+ NOLOGGING */ when you refer to the Nologging option? Can I use this in my delete statements as well?

Thanks again.

Report message to a moderator

Previous Topic: Need help
Next Topic: what is the rowid type ?
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ]

Current Time: Tue Apr 23 21:30:53 CDT 2024
.:: Forum Home :: Blogger Home :: Wiki Home :: Contact :: Privacy ::.