Results 1 to 8 of 8
  1. #1
    Join Date
    Aug 2003
    Posts
    23

    Unanswered: 8i Rollback Segents error - ORA-00376

    On a test database, we keep getting an ORA-00376 error "file 5 cannot be read at this time". File 5 is the rollback segment tablespace. This occurred once last week and then again today. To correct, we did a recovery on the datafile and then reset the rollback segments online.

    recover tablespace rollback;
    alter tablespace rollback online;
    alter rollback segment rb0 online;
    alter rollback segment rb1 online; etc etc.

    This corrects the problem but I am not convinced that it will not occur again. What could be causing this to occur? The test instance is set up identical to production, on a different server. This has never happened on production.

    Ideas?

    THANKS

  2. #2
    Join Date
    Jul 2003
    Posts
    2,296
    are the RB segs on both servers the same size?
    - The_Duck
    you can lead someone to something but they will never learn anything ...

  3. #3
    Join Date
    Aug 2003
    Posts
    23
    Originally posted by The_Duck
    are the RB segs on both servers the same size?
    I just checked and they are sized incorrectly on test. 4MB initial on prod, 300K initial on test. I'll resize them and see if that helps.

    BTW, is there a good online resource covering rollback segments someplace?

  4. #4
    Join Date
    Aug 2003
    Posts
    23
    Oops, I meant 400k on test (if that matters!).

  5. #5
    Join Date
    Aug 2003
    Location
    SW Ohio
    Posts
    198

    Re: 8i Rollback Segents error - ORA-00376

    Originally posted by jayharper
    On a test database, we keep getting an ORA-00376 error "file 5 cannot be read at this time". File 5 is the rollback segment tablespace. This occurred once last week and then again today. To correct, we did a recovery on the datafile and then reset the rollback segments online.

    recover tablespace rollback;
    alter tablespace rollback online;
    alter rollback segment rb0 online;
    alter rollback segment rb1 online; etc etc.

    This corrects the problem but I am not convinced that it will not occur again. What could be causing this to occur? The test instance is set up identical to production, on a different server. This has never happened on production.

    Ideas?

    THANKS
    From Note:183327.1 on http://metalink.oracle.com/

    Possible causes and solutions summary:
    =====================================
    [list=A][*] Tablespace or Datafile offline. [*] Datafile does not exist at the OS level. [*] Datafile locked by Backup Software. [*] Incorrectly set ULIMIT on UNIX. [*] Rollback Segment with active transactions is unavailable [*] Possible Other Causes. [/list=A]
    On possible other causes....
    Have you eyeballed the server and made sure its drives are not corrupt /failing. As in a RAID 5 with a bad drive.
    What kind of speed are you getting out of your SCSI card.
    Are the disks severely fragmented.
    Jim P.

    Supoorting Oracle, MSSQL7, Sybase 8, & Pervasive. Confusion Reigns

  6. #6
    Join Date
    Aug 2003
    Posts
    23
    > Datafile locked by Backup Software.

    This sounds like the culprit. We recently began testing online backups with backup exec on this server. I'll check with our Ops guys.

    THANKS

  7. #7
    Join Date
    Aug 2003
    Posts
    23
    Originally posted by jayharper
    > Datafile locked by Backup Software.

    This sounds like the culprit. We recently began testing online backups with backup exec on this server. I'll check with our Ops guys.

    THANKS
    Indeed it was!

    Thanks for the help and info

  8. #8
    Join Date
    Aug 2003
    Location
    SW Ohio
    Posts
    198
    Originally posted by jayharper
    Indeed it was!

    Thanks for the help and info
    Glad to be of help. Go slap your Ops guys for me.
    Jim P.

    Supoorting Oracle, MSSQL7, Sybase 8, & Pervasive. Confusion Reigns

Posting Permissions

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