ORA-27100

[Former Member]

Hi!

We are having the error ORA-01034 and ORA-27100 during the installation of SAP ERP 2005.

SQL> connect / as sysdba

Connected to an idle instance.

SQL> startup

ORA-27102: out of memory

OSD-00022: additional error information

O/S-Error: (OS 😎 Not enough storage is available to process this command.

SQL> startup force

ORA-27100: shared memory realm already exists

SQL>

<b>Can someone give some recommendations?</b>

Thank you!

regards

[markus_doehr2]

What operating system are you using? How big did you set your SGA?

--

Markus

[Former Member]

Hi!

Thank you for the response!

We are using Windows 2003 and we have the value sga_max_size of 0932420710 and have increased it and decrease it in init<SID>.ora manually (by 12 GB of RAM)

But it does not help...

<b>Can you help out please?</b>

Thank you!

Regards

[markus_doehr2]

> Hi!

> Thank you for the response!

>

> We are using Windows 2003 and we have the value

> sga_max_size of 0932420710 and have increased it and

> decrease it in init<SID>.ora manually (by 12 GB of

> RAM)

are you on 32bit windows?

--

Markus

[Former Member]

Hi!

Yes, we have 32 bit.

[markus_doehr2]

A 32bit operating system is (by default) only able to address 2 GB of memory, if you configure windows with the /3GB boot.ini switch you will be able to address 3 GB. With some special configuration you can get even higher but I recommend putting the SGA to 2 GB, install and then go on configuring.

SAP does not recommend using 32bit operating systems for production use for Netweaver 2004s based products (which is ERP 2005).

--

Markus

[Former Member]

Thank you Markus!

We have the following information in our boot.in.

[boot loader]

timeout=30

default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

[operating systems]

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect

<b>How can we proceed the installation?

Which settings do you recommend?</b>

Thank you

regards

[former_member204746]

change

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect

to

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /noexecute=optout /fastdetect /3GB /PAE

...and reboot

[markus_doehr2]

I would recommend (to go with the installation) to set the SGA to 2 GB (or less, 1.5 GB) and go on with the installation. After you finished installing use "Note 441663 - More than 3 GB of memory for Oracle on WINDOWS 2000 / 2003" but I would not do that now because the database is stopped and started some times during installation and you will run into the problem mention in that note above

[...]

Please note, that when using this functionality, the mechanism for releasing memory slightly changes. When shutting down the database, the memory would still be allocated within the oracle process. Therefore the oracleService<SID> needs to be stopped and restarted in order to startup the database again.

If the database is shutdown, and restarted without stopping and restarting the database, the following error will occur in most cases:

ORA-27102: out of memory

OSD-00007: Message 7 not found; product=RDBMS; facility=SOSD

[...]

So - put the SGA to 1.5 GB (to be safe) and go on with the installation.

--

Markus

[markus_doehr2]

> change

> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows

> Server 2003, Enterprise" /noexecute=optout

> /fastdetect

>

>

> to

>

> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows

> Server 2003, Enterprise" /noexecute=optout

> /fastdetect /3GB /PAE

>

> ...and reboot

This is not enough (see note)

--

Markus

[Former Member]

HI!

Now we have set the value and implemeted the note 441663.

We have still the error

<b>ORA-00385: cannot enable Very Large Memory with new buffer cache parameters

Disconnected</b>

Can you recommend something?

Thank's again!

regards

[markus_doehr2]

&#1613;Set

use_indirect_data_buffers = FALSE

and try to startup the database.

--

Markus

[markus_doehr2]

Forget my last post, I was too fast

You need to change your db_cache_size to use db_block_buffers because you NEED the parameter use_indirect_data_buffers=true, otherwise AWE won't work.

Sorry for confusion...

--

Markus