Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: ORA-01034 error during database creation
Stephan
thanks for this. If I connect CONNECT INTERNAL and then STARTUP NOMOUNT
I get:-
LRM-00109: could not open parameter file '/data/Ora8i/dbs/initilsmast.ora'
ORA-01078: failure in processing system parameters
I guess this file needs to be created, and I would have expected configuration manager to create it. There is an init.ora and initdw.ora in that directory which look like templates, but I'm reluctant to tamper with things I don't really understand.
Chloe
"Stephan Bressler" <stephan.bressler_at_siemens.com> wrote in message
news:b69fqt$3u$1_at_news.mch.sbs.de...
> Hi,
>
> seems your instance is not running --- or with a different sid, maybe
> ILSMAST (upper case)?
>
> Stephan
>
> "Chloe Crowder" <chloe.crowder_at_bl.uk> wrote in message
> news:b69evp$lml$1_at_south.jnrs.ja.net...
> > Having installed 8.1.7 on Solaris I attempted to create a database using
> > DCA. This started creating the database and then gave:-
> > ORA-01034: ORACLE not available.
> >
> > Looking in /data/Ora8i/admin/ilsmast/create I found a log file and
script.
> I
> > assume the script is what was created and the log file the result. The
> > script starts off:-
> >
> > #!/bin/sh
> > ORACLE_SID=ilsmast
> > export ORACLE_SID
> >
> > /data/Ora8i/bin/svrmgrl << EOF
> > spool /data/Ora8i/admin/ilsmast/create/crdb2.log
> > connect internal
> > @/data/Ora8i/rdbms/admin/catalog.sql;
> >
> > REM ********** ALTER SYSTEM TABLESPACE *********
> > ALTER TABLESPACE SYSTEM
> > DEFAULT STORAGE ( INITIAL 64K NEXT 64K MINEXTENTS 1 MAXEXTENTS UNLIMITED
> > PCTINCR
> > EASE 50);
> > ALTER TABLESPACE SYSTEM
> > MINIMUM EXTENT 64K;
> >
> > and the log file:-
> >
> > Connected.
> > create or replace
> > *
> > ORA-01034: ORACLE not available
> > create or replace
> > *
> > ORA-01034: ORACLE not available
> > grant execute on STANDARD to public
> > *
> > ORA-01034: ORACLE not available
> > create or replace view v_$dlm_misc as select * from v$dlm_misc
> >
> >
> > The documentation on the error message implies that there should be
other
> > error messages to help identify the cause, but no. Can anyone offer any
> > insight?
> >
> > Chloe Crowder
> >
> >
>
>
Received on Mon Mar 31 2003 - 07:57:52 CST