Is that your machine's valid hostname? If not, figure out the correct value for hostname, and adjust your local_listener parameter. Or since its the default port, try clearing the parameter. If the database won't startup because of invalid parameters, that is another, different problem to solve. Trivial with experience, on the first try fixing a bad parameter could be tricky.HOST=Client -3
sqlplus /nolog conn system ... password ... alter system reset local_listener scope=both; -- bounce it to make sure the error is gone conn /as sysdba shutdown immediate; startup;
Which hostname? The host hostname? Or the listener.ora ...HOST= <hostname> setting? Using the "any IP" value of ... HOST = 0.0.0.0 or moving the listener.ora file out of the way will usually work around most host network configuration glitches.after changing hostname
If you don't get the 'ORACLE instance started.' from the startup nomount pfile=' bit, fix what ever is incorrect with the initXE.ora file, shutdown immediate; and try the startup nomount ... again. If that last startup doesn't show the ... mounted ... opened bits, something else still isn't quite right with the init file.
sqlplus /nolog conn /as sysdba; ... Connected to an idle instance. startup nomount pfile='c:\temp\initXE.ora'; ORACLE instance started. ... SGA, redo, etc. details ... create spfile from pfile='c:\temp\initXE.ora'; ... File created. shutdown immediate; ... ORA-01507: database not mounted ... yes that is normal because the database was not open nor mounted ... ORACLE instance shut down. startup; ... ORACLE instance started. ... SGA, etc info ... ... Database mounted. ... Database opened.
Edited by: Bas de Klerk on 4-apr-2013 22:50
service oracle-xe start