STARTUP Command not working with Oracle 8.0.6. - Instance could not be created

[Engo Bokoko]

Hi there!

Trying to create DataBase with the following message :
cyb_hpux [ /cyborg/app/oracle/product/806/bin ] $ sqlplus /nolog
SQL*Plus: Release 8.0.6.0.0 - Production on Thu Mar 7 13:15:49 2002
(c) Copyright 1999 Oracle Corporation. All rights reserved.
SQL> conn system/manager as sysdba
Connected.
SQL> startup nomount
unknown command beginning "startup no..." - rest of line ignored.
SQL>
If you can assist me, I'll highly appreciate it!
Thanks!
Best regards,

Engo.

[Alexander M. Ermes]

Hi there.
You should go for the svrmgr ( ORACLE_HOME/bin ) command.
Run this one, do the connect and then try to start the database.
Rgds
Alexander M. Ermes

[Volker Borowski]

As Alexander suggests,

go by svrmgrl
and
connect internal

Be sure to have appropriate init.ora file created, so the memory required can be allocated.

BTW, bette you apply some patches before you start. 8.0.6.0.0 might be way too low.

Do not know what was the last deliverd patch, but I think 8.0.6.4.something should be minimum.

Volker

[Andreas D. Skjervold]

Hi

You can't use SQL*Plus for Starting up databases and shutdown down on Oracle 8.x.

Only as of 9.x

use svrmgrl as suggested.

Andreas

[Engo Bokoko]

Hi there.

Thanks for your assistance!

Unfortunately, I used the Server Manager for starting up the Database without success.

Let you know that I'd like to use SQLPLUS /NOLOG regarding to the future version of Oracle 9i.

This the latest process :

[/cyborg/app/oracle/product/806/bin ] $ svrmgrl

Oracle Server Manager Release 3.0.6.0.0 - Production

(c) Copyright 1999, Oracle Corporation. All Rights Reserved.

Oracle8 Enterprise Edition Release 8.0.6.0.0 - Production
PL/SQL Release 8.0.6.0.0 - Production

SVRMGR> connect system/manager as sysdba
Connected.
SVRMGR> startup nomount
LRM-00101: unknown parameter name 'lock_shared_memory'
ORA-01078: failure in processing system parameters
SVRMGR>


Thanks1

Best regards,

Engo.

[Andreas D. Skjervold]

Hi

Remove the parameter "lock_shared_memory"
and try again.

Believe you'll need special privilieges to lock memory.
(setprivgrp dba MLOCK)

Andreas