Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Newbie - help on dbstart

Re: Newbie - help on dbstart

From: Howard J. Rogers <howardjr_at_www.com>
Date: 2000/07/31
Message-ID: <398553b3@news.iprimus.com.au>#1/1

"Prime" <primea_at_okara.com> wrote in message news:39844E27.1C45B111_at_okara.com...
> Hi
>
> We have Oracle 8.1.5.0.2 installed on Red Hat 6.2
> When we issue the command 'dbstart' the following comes up...
>
>
> Oracle Server Manager Release 3.1.5.0.0 - Production
>
> (c) Copyright 1997, Oracle Corporation. All Rights Reserved.
>
> Oracle8i Release 8.1.5.0.2 - Production
> With the Java option
> PL/SQL Release 8.1.5.0.0 - Production
>
> SVRMGR> Connected.
> SVRMGR> LRM-00105: 'log' er ikke en gyldig boolsk værdi for
> 'log_archive_start'
> ORA-01078: failure in processing system parameters
> SVRMGR>
> Server Manager complete.
>
> Database "v8i815" warm started.
>
>
> Problem....
> when we go to sqlplus, its giving us an error:
> ORA-01034: ORACLE not available
>
> It is as if the database has not startted. Please help. What am I doing
> wrong.
>

No dramas. The clue is in the error message (surprising enough!) Your init.ora (parameter file) has got something in it that Oracle doesn't understand. Accordingly, the startup sequence terminates, and you end up not even creating an Instance -so you are perfectly correct that the 'database has not started' (though, technically, you only start Instances. Databases get *opened*).

The problem is that there is a parameter called LOG_ARCHIVE_START that should either be set to TRUE or FALSE. If you've got it set to anything else, you'll have trouble. LOG_ARCHIVE_START switches on the ARCH process for automatic archival of the on-line redo logs. It only makes sense to switch it on if you've actually put your database into ARCHIVELOG mode.

Either set it to true or false, or comment out the entire line (with a "#" at the start of it), and then try again.

The problem would only arise when you re-start your Instance -because the parameter file is only read at startup. The thing could have read a good parameter file ages ago, someone then stuff around with the file -no dramas. Then you try and re-start, requiring fresh read of parameter file.... bong! Troubles abound!!

Regards
HJR
> Note. There was no problem after installation. everything worked fine
> until after I rebooted!
>
> Prime
> primea_at_okara.com
>
Received on Mon Jul 31 2000 - 00:00:00 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US