ORA-03113: end-of-file in startup

Question

Hi,
on 11g R2 on Win 2008 I try to create a DB but I receive end of file error :
C:\Users\oracle>sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Fri Mar 2 10:07:45 2012
Copyright (c) 1982, 2011, Oracle.  All rights reserved.
Connected to an idle instance.
SQL> @0_createdb10.sql
SQL> spool createdb.log
SQL>
SQL> startup nomount pfile=C:\app\oracle\product\11.2.0\dbhome_2\database\initTEST.ora
ORA-03113: end-of-file on communication channel Thank for any suggestion.

Answer 1

First Set the ORACLE_SID
The SID can be set through the ORACLE_SID environment variable.
C:/../.../../>set ORACLE_SID=ORA10
Creating an Oracle Service
On Windows, each instance requires a Windows service. This service must first be created with oradim:
D:\oracle\product\11.1.0\Db_home>oradim -new -sid %ORACLE_SID% -intpwd MYSECRETPASSWORD -startmode M
Instance created.
It can be verified that a Windows service was created by typing services.msc into the console. A service named OracleServiceORA10 (ORA10 = %ORACLE_SID%) will be found. Also, the startup type is manual as was requested by -startmode M.
Creating the initialization parameter file
When an Oracle instance starts up, it requires either an initialization paramter file (init.ora) or an SPFILE.
SPFILES have binary content and must be created from init.ora files. Therefore, the init.ora file (which is an ordianary text file) is created first.
Here's a minimal init.ora (under $ORACLE_HOME/dbs if it is Unix, or %ORACLE_HOME%\database, if it is windows) just to demonstrate how the control files are found. Of course, you will add more init params into the init.ora file.
after creating an Oracle service and the init.ora file, start the instance:
connect to the instance
and
SQL> startup nomount
This created the SGA (System Global Area) and the background processes.
Creating the database
now you have to create the database:
SQL>run the Create database script....
If something goes wrong with the creation, Oracle will write an error into the alert.log. The alert log is normaly found in the directory that is specified with the background_dump_dest. If this parameter was not specified (as is the case in our minimal init.ora), the alert.log will be written into %ORACLE_HOME%/RDMBS/trace.
If an ORA-01031: insufficient privileges is returned, that means most likely, that the current user is not in the dba group (on unix), or the ORA_DBA (windows).
If the init.ora file is not at its default location or has not been found with the pfile attribute, an ORA-01078: failure in processing system parameters and an LRM-00109: could not open parameter file '/appl/oracle/product/../initadpdb.ora' error is issued.
The create database command also executes a file whose name is determined by the (hidden) init parameter initsql_file (which seems to default to sql.bsq)
After the creation of the database, it can be mounted and opened for use.
Completing the DB creation
In order to complete the db creation, the following scripts must be run as sys:
%ORACLE_HOME%/rdbms/admin/catalog.sql
%ORACLE_HOME%/rdbms/admin/catproc.sql and
SQL*Plus provides a shortcut to refer to the ORACLE_HOME directory: the question mark (?). Therefore, these scripts can be called like so:
Edited by: mBk77 on Mar 2, 2012 3:00 PM