solving ORA-27102 by configuring the DB-parameters

[Former Member]

Solving ORA-27102 with startup nomount

Hello!

I am facing with ORA-27102 and would like to know, whether it is possible to solve the problem as follows

Can the following commandos be executed in order to set and use the values of sga_max_size immediately in order to avoid ORA-27102?

Variant 1)

>sqlplus /nolog

>connect / as sysdba

> startup nomout

> ALTER SYSTEM SET SGA_MAX_SIZE= ’value’ SCOPE=pfile;

> shutdown immediate

> startup

Variant 2)

Changing the values of sga_max_size, etc. in init<DBSID>.ora

>sqlplus /nolog

>connect / as sysdba

> startup from pfile = /oracle/<SID>/dbs/ init<DBSID>.ora;

Variant 3)

Set the value shmmax to 4GB in etc/system

Thank you very much!

regards

Thom

[Former Member]

why don't you set SGA in init<SID>.ora and then start the database with pfile?

You can rename the spfile and you can startup the database or

like that:

sqlplus /nolog

<b><i>SQL> connect / as sysdba

SQL> startup pfile='/oracle/<sid>/102_64/dbs/init<sid>.ora'

SQL> create spfile from pfile

SQL> shutdown immediate;</i></b>

<b><i>SQL> startup</i></b>

or if you rename the spfile, it is enough, if you just startup the database with startup and then create a new spfile from pfile and then restart the database so that the database is started with spfile:

Oracle searches for the parameter file in the following order:

1. spfile<SID>.ora

2. spfile.ora

3. init<SID>.ora

see also please the SAP note.

601157 - Oracle9i: Server Parameter File

see please this thread:

Best regards