open clone database but rollbacks are wrong Forums - Powered by vBulletin
Results 1 to 2 of 2

Thread: open clone database but rollbacks are wrong

  1. #1
    Join Date
    Dec 2001


    Hello Ora-Gurus !

    On a semi regualr basis I copy PROD to TEST for our databases. The work involved ranges from 2 hours to read the tapes to 15 hours for some of the biggies.

    Using the "standard" method outlined elswhere in this forum
    I create controlfile to trace on PROD and then create a
    new controlfile on the TEST.

    So far so good.

    It has happened in the past (and I'm sure, sadly, it will happen again) that the initTEST.ora has a different number of rollback segments defined as the PROD database. Normally this is noticed before the ALTER DATABASE OPEN RESETLOGS
    gets its way.

    Now my question: IF the number of rollbacks in initTEST.ora is not compatible with the datafiles the OPEN RESET fails. At present I make a complete restore should this happen.

    Is there a way out of this "dead end" ?

    Points for me:
    My checklist should be more thorough - for instance
    1) "before OPEN RESETLOGS... remove rollback parameter from initTEST.ora.
    2) ensure TEST rollbacks come up offline - see 1) !!

    I have heard of a way to edit the traced controlfile script,
    deleting the rollback file entries and setting initTEST.ora parameters to set any (false) rollbacks offline. Then try to drop them. Tried without success -

    Do you know better ??

    Thanx in advance

  2. #2
    Join Date
    Nov 2000
    Use public rollback segments instead. That way, you don't have to have a rollback_segments= parameter in your init.ora.
    Jeff Hunter
    Get Firefox!
    "I pledge to stop eating sharks fin soup and will not do so under any circumstances."

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