Re: svrmgrl errors. help.

In article <75h65j$74j$1_at_netnews.upenn.edu>, manuk_at_gradin.cis.upenn.edu says...
>
> I am getting the following when I try to "startup" a database. Any
> help in deciphering it would be awesome:
>
> ----
> Total System Global Area 4398880 bytes
> Fixed Size 39732 bytes
> Variable Size 3863532 bytes
> Database Buffers 102400 bytes
> Redo Buffers 393216 bytes
> ORA-00205: error in identifying control file '?/dbs/cntrl@.dbf'
> ORA-07360: sfifi: stat error, unable to obtain information about file.
> SVR4 Error: 2: No such file or directory
>
> ----
>
> Thanks!
> Manu.
>
> --
>

Basically it's telling you just what it says: that it can't find the control file for your database in the specified directory. Mind you, '?/dbs/cntrl@.dbf' seems a somewhat strange name for a control file, but right now I can't recall if it's legal. I'd expected something like a SID name instead of the @ symbol -- unless the '@' translates to the SID name (?comment anyone?).

Can you actually find the file in the directory? The '?' symbol of course refers to the directory pointed to by your ORACLE_HOME variable. All control files used by the database will be listed in either your parameter file ('init<SID>.ora') file, or any other file that it includes with the 'ifile =' parameter.

It's only small, but it's so important that you don't want to lose it and it really should be mirrored for that very reason. It contains the location of every data file comprising the database and also the System Change Number which is needed for consistency checking and recovery.

Are there two files listed in your init.ora file? For example:   control_files = ('?/dbs/cntrl@.dbf', '/u01/oracle/DEV1/cntrl_at_2.dbf')

If there are two files, they are identical and you can copy the second to the place where the first used to be, and retry starting the DB.

If there's only one listed and the file is truly lost, but your database shut down cleanly last time, you may be able to manually locate all datafiles and logfiles on the system to reconstruct a new one. This could be done with a
 'startup nomount' (doesn't try opening a non-existent control file). And then: (I have no manuals at home, so don't expect this to be right)  'alter database recover control file ...'

It's a lengthy command, you'll definitely need to have manuals open with you and the manuals admonish that if you get it wrong, eg. forget a datafile etc., kiss it goodbye. Look at the chapter on DB recovery scenarios and also the SQL Command Reference. Some DBAs maintain an up- to-date SQL script which does this very thing, just in case...

The worst case, if you can't get a working control file, is to recover the entire database from your last backup.

If your control file IS there, then I don't know. Are the ORACLE_SID and ORACLE_HOME environment variables correct, matching the case of the database name and as listed in /etc/oratab?

BOL (Best of luck)

        Brian.
--
"Strictly UNIX" To dance is to live. belliot_at_gil.com.au Received on Tue Dec 22 1998 - 07:48:43 CST