Results 1 to 3 of 3
  1. #1
    Join Date
    Aug 2004

    Unanswered: SQL user making Mass Changes

    I have an SQL user making mass changes that is causing so many archive logs to be created that it fills up all the disk space and oracle halts. Is there a way to turn off logging only for this users' execution of the SQL? thanks

  2. #2
    Join Date
    Mar 2002
    Reading, UK
    No not really you can reduce logging using sql loader and using create table as... (using nologging option). Another possibility is if you carrying out multiple operations on the same dataset then copy the dataset into a global temp table, do the operations and then copy it back to the original table.

    A last resort possibility would be to chuck everyone off the database, put it into noarchivelog mode, do the updates and then bring the database back up in archivelog mode.

    The other alternative is to run your archivelog backup when the archive disk is nearly full as this should delete the archivelogs when it finishes. We have a script which automatically runs an archivelog backup when the disk is 70% full.


  3. #3
    Join Date
    Jul 2003
    gzip all the archivelogs (not the current one being written to tho!)

    do a hot full backup with RMAN, then issue: delete obsolete
    rman will then delete all archivelogs that are no longer needed
    due to the backup.
    - The_Duck
    you can lead someone to something but they will never learn anything ...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts