This is the same database that I've spoken about in recent threads that has required a server reboot two weeks in a row and may be going on a third.
I was told by the previous DBA that this was not an issue, but I can't find any documentation as to why or what it even means that the database sits in an "oninit -r" mode.
Does this mean my database is looped in fast recovery???
Please help, this database may go back down again tomorrow night and I'm starting to grasp at straws here...
oninit -r is the option you should use to switch between primary-secondary and reverse modes if you are using a High Availability Data Replication pair. But you must not use it if your server is a single one.
Use oninit (to initialize shared memory and leave it on-line) or oninit -s (to initialize shared memory and leave it quiescent, quite like administration mode -> followed by onmode -m to bing it on-line).