DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: Physical standby - nologging operation

  1. #1
    Join Date
    Oct 2002
    Posts
    807

    Physical standby - nologging operation

    I've got a physical standby (9.2.0.1). I created a test table and a nologging index on it (the underlying tablespace is NOT in a force logging mode). Then pushed some data. Then did a "select name, unrecoverable_change# from v$datafile;" on both primary and standby. Surprisingly, I didn't see any difference in the change# and the standby was infact caughtup. I, then opened the standby in readonly mode. The index does seem to exist there. Am not sure if it is getting populated though. I tried forcing a hint to use the index etc. But I can't tell if it's actually using it, since I can't explain plans on a read-only. I suppose I can run traces etc..but before I go down the path, can someone explain this phenomenon? What might be going on?

  2. #2
    Join Date
    Jun 2001
    Location
    Helsinki. Finland
    Posts
    3,938

    Re: Physical standby - nologging operation

    The index is created and logged but the population of the index is not done and after recovery the blocks occupied by the index are marked as corrupted.

    If you try to access the index, you will get an error.
    Oracle Certified Master
    Oracle Certified Professional 6i,8i,9i,10g,11g,12c
    email: ocp_9i@yahoo.com

  3. #3
    Join Date
    Oct 2002
    Posts
    807
    Thanks. Yeah, I guessed as much that the index most likely wasn't getting populated. What stumps me is a hint to use the index on the standby (when in read only mode), doesn't throw errors in the alertlog saying block# is corrupt since nologging operations were performed on primary.

  4. #4
    Join Date
    Oct 2002
    Posts
    807
    Nevermind. My fault. I wasn't direct-path inserting into the table.

Posting Permissions

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


Click Here to Expand Forum to Full Width