Re: ORA-03113 on startup

In article <5QoS5.219256$g6.101703319_at_news2.rdc2.tx.home.com>,   "Michael O'Neill" <mjoneill_at_email.com> wrote:
> When was your last backup? Last time I had that error it was
> a symptom of a larger problem, namely a sever corruption in the
> data dictionary caused by a hardware failure.

Well, that's a problem. This is a personal setup while I prepare for the Oracle DBA tests. I had a working database, but tried regenerating a control file to rename it. I didn't have proper backups at the time, and the DB wouldn't start, complaining that the files were inconsistent. So I can't easily avoid the charge that I "just plain screwed it all up."

However it seems strange to me that the DB would suddenly start this new problem, and I thought I could address it separately. Apparently not?

BTW I did borrow copies of the control files, redo logs, etc., from a different database which was working. When I put those in place and tried starting up, I still got the same error ORA-03113. Those were properly copied from an OS-level cold backup, so they should be fine by themselves. Any suggestion where to look? Is there a common file I probably forgot to modify? (The borrowed DB was basically identical to the one I screwed up.)

As a last resort, where might I look for instructions in producing a clean, empty instance? I.e., to create generic control files, intialize brand-new tablespaces and redo logs, etc., so as to get up and running again? The data which I lost was completely expendable. (I'd just reinstall, but the Java-based installer doesn't work under RedHat 7.)

Thanks for your reply; at least you're helping me realize the vital importance of backups!

Len.

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Tue Nov 21 2000 - 10:49:22 CST