Re: URGENT: ORA-01554 upon startup

From: NetComrade <netcomrade_at_netscape.net>
Date: 18 Mar 2003 08:39:30 -0800
Message-ID: <ab810584.0303180839.30c9d2a4@posting.google.com>

the original values were

transactions                         integer 1820

transactions_per_rollback_segment integer 5

the new values were

transactions 10000
transactions_per_rollback_segment 40

I've also tried playing around with these.

The trace file
/u31/app/oracle/admin/BASE/udump/base_ora_15807.trc

contains nothing but the already mentioned errors.

Oracle support wasn't able to recover the database for us. They tried to bring it up with
_corrupted_rollback_segments= (<segment_list>) but that didn't help
they offerred to come on site and recover the data manually, starting at $10K, but that wasn't worth our time. We brought up the data in a separate instance with 20 hours of data lost. This instance is still left for my amusement. If anybody has any suggestions, I'll be more than happy to try them out. (we still would like this data back)

DA Morgan <damorgan_at_exxesolutions.com> wrote in message news:<3E765BB6.6059E162_at_exxesolutions.com>...
> NetComrade wrote:
>
> > This is really frustrating.. I can't bring up the db
> > startup force doesn't help
> > increasing transactions and transaction_per_rollback_segment doesn't
> > help either.
> > anybody seen this?
> >
> > thnx.
> > .......
> > We use Oracle 8.1.7.4 on Solaris 2.7 boxes
> > remove NSPAM to email
>
> I'm not so sure your statement "increasing transactions and
> transaction_per_rollback_segment doesn't
> help either." because you give no indication of what it was originally
> and how much you increased these parameters.
>
> My guess here is that Oracle is trying to clean-up or clean-out
> something and needs a lot more space than it has.
>
> Check the log files as Gabriel suggests and publish the original and
> modified values for us to see.
>
> Daniel Morgan
Received on Tue Mar 18 2003 - 10:39:30 CST