Results 1 to 4 of 4

Thread: Nologging

  1. #1
    Join Date
    Nov 2003
    Posts
    2

    Unanswered: Nologging

    Hi,

    I've got two tables that have two indexes that as far as the application is concerned, is just a look up. They are re-populated each night via a job that is running SQL-Loader.

    As this is going to be a production system shortly, I've recently turned on archive logging, but this job is creating redo like there's no tomorrow. As the tables would be easily recoverable from exports, I've opted to set the tables and the indexes to NOLOGGING.

    The job ran last night for the first time, but still lots of redo was created. Has anyone any idea why?

    Thanks.

  2. #2
    Join Date
    Dec 2002
    Location
    Netherlands
    Posts
    118
    Hi

    Please verify that;

    + The associated indexes are also set in nologging (verify dba_indexes.logging)

    + SQL*Loader uses the DIRECT path, direct=true


    Hope this helps.


    Remi
    Remi Visser

    Oracle Database Administrator
    (OCP certified 8i)

    Homepage: http://home.remidian.com/

  3. #3
    Join Date
    Nov 2003
    Posts
    2
    The tables and indexes both were switched to nologging.

    However, they weren't using the option of DIRECT=TRUE on the SqlLoader command line. However, I've added it on, retested it, and got the same results, loads of redo.

    They have also set the ROWS=100, is this likely to have an effect?

    Thanks again.

  4. #4
    Join Date
    Aug 2001
    Posts
    66
    Go here...

    http://asktom.oracle.com

    ...and search for (include quotes)...

    "Why is there so much logging for insert"
    Padderz
    SYSOP, Quest Software / RevealNet Labs PL/SQL Pipeline

Posting Permissions

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