K,
Good detective work. Following up on the correct observations/suggestions from dbtoo2001:
1) The oratab file is aware of an Oracle instance named "orcl". It is not aware of and instance named DUNBAR. You can use "vi" or other favourite editor to specify the DUNBAR instance. The oratab format:
<SID-name>:<Oracle Home>:<Startup on reboot Y/N>
2) Yes, the reaction to the "startup" command confirms that whatever instance you were connecting to was down, and you started it up.
3) In "svrmgrl", issue the command:
Code:
SELECT * FROM V$INSTANCE;
This will confirm important information about the instance including whether you are connected to "ORCL" or "DUNBAR".
4) In the first place, to anticipate which instance you will be connecting to when you issue the "svrmgrl" command, issue the Unix command: "echo $ORACLE_SID" whatever the results, that is the name of the instance Oracle connects you to when running "svrmgrl".
5) To change instances (i.e., "ORCL" to "DUNBAR"), issue the command ". oraenv". You can then enter any instance name that appears in your oratab file. The results of running oraenv are: $ORACLE_SID and $ORACLE_HOME contain the respective values from the oratab file that match your response to oratab's prompt "ORACLE_SID = [<current SID>] ? "
Let us know if this offers some order to you new life as an Oracle administrator.
![[santa] [santa] [santa]](/data/assets/smilies/santa.gif)
Mufasa
(aka Dave of Sandy, Utah, USA @ 20:43 (14Jun04) UTC (aka "GMT" and "Zulu"), 13:43 (14Jun04) Mountain Time)