| 9iR2 Database Configuration Assistant fails with "Out of Memory" error ORA-27102 [message #53098] |
Wed, 28 August 2002 05:01  |
Rick Root
Messages: 8
Registered: August 2002
|
Junior Member |
|
|
RedHat Linux 7.3 fully patched
1GB physical RAM
1GB swap
Oracle 9i Release 2 (9.2.0.1.0)
With a few minor stumbling blocks, I've managed to get Oracle installed on the above Linux server but the Database Configuration Assistant fails with an ORA-27102 "Out of Memory" error whenever it gets to the step of "Creating and starting Oracle instance".
In fact, if I have a shell open with "top" running in it, I can see that i'm nowhere near out of memory. Only about 260MB of physical RAM is used and no swap space.
I've followed all of the instructions as far as kernel parameters found in the Installation Guide *AND* the Release Notes, but just in case, here are my values:
SEMMSL 100
SEMMNS 256 (also tried 400 and the default, 32000)
SEMOPM 100
SEMMNI 100 (also tried 600)
SHMMAX 524288 (half my phsyical memory)
SHMMNI 100
SHMALL 2097152 (release notes say leave as default)
I've searched many places for the answer to this.. I've only found one message that looks like the same problem but no responses to it (in comp.database.oracle.server).
Any help is greatly appreciated.
Thanks!
Rick Root
rroot@ads.duke.edu
|
|
|
|
| Re: 9iR2 Database Configuration Assistant fails with [message #53104 is a reply to message #53098] |
Wed, 28 August 2002 05:57  |
SKS
Messages: 26
Registered: February 2002
|
Junior Member |
|
|
Solution 1:
Check whether the semaphores/shared memory released for the 9i database. The commands to check these are
ipcs -s
ipcs -m
Solution 2:
If the stack size is set to a value higher then the vmemory allocated for the process, the "out of memory" error occurs. The kernel allocates the stack in the process image address space.
Using "ulimit -a" check the per process resources in the Oracle user's environment
Set the stack size to a reasonable value that can fit into the allowed memory space for the Oracle process
For C Shell:
% limit stacksize 2048
For Korn or Bourne Shell:
$ ulimit -s 2048
|
|
|
|
| Re: 9iR2 Database Configuration Assistant fails with [message #53108 is a reply to message #53098] |
Wed, 28 August 2002 06:58 |
Rick Root
Messages: 8
Registered: August 2002
|
Junior Member |
|
|
Sushil,
Thanks for your reply. Here is the output of "ulimit -a" on my machine when i log in as the oracle user:
$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 7168
virtual memory (kbytes, -v) unlimited
I ran "ulimit -s 2048" and tried again... I got the same error.
I'm not sure what the output of those ipcs commands means though. Here is their outputs though currently.
$ ipcs -m
------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x00000000 34373632 oracle_dba777 98304 2 dest
0x00000000 36175873 oracle_dba777 98304 2 dest
0x00000000 36306946 oracle_dba777 98304 2 dest
0x00000000 35061763 oracle_dba777 98304 2 dest
0x00000000 36438020 oracle_dba777 98304 2 dest
0x00000000 42106885 oracle_dba777 98304 2 dest
$ ipcs -s
------ Semaphore Arrays --------
key semid owner perms nsems status
|
|
|
|
|
|
|
|
| Re: 9iR2 Database Configuration Assistant fails with "Out of Memory" error ORA-27102 [message #55186 is a reply to message #53098] |
Thu, 09 January 2003 07:30 |
Simon Heather
Messages: 1
Registered: January 2003
|
Junior Member |
|
|
|
Problem Description ------------------- You are attempting to create a new database using Oracle Database Configuration Assistant when your server has a very large unused memory. You pick a typical type of database creation and receive the following error: ORA-27102: out of memory The database creation fails. Solution Description -------------------- Pick Custom installation and keep on picking default values if you wish to or change them upon your requirements until you reach the page where you have to set your initialization parameters of the newly created database. Lower the numbers of shared_pool_size and block_buffers to a reasonable and appropriate number that can suit your needs as well as your hardware abilities and continue with the creation. The database will be created successfully. Here is a simple formula to assist you in calculating the size of the SGA depending on the values you will be assigning for your initialization parameters in init.ora: ( ( db_block_size * db_block_buffers ) + log_buffer + shared_pool_size + large_pool_size + java_pool_size ) / .9 Explanation ----------- The reason this problem is occuring is because when you have large memory installed on the server and a large segment of this memory is unused, the Oracle Database Configuration Assistant will pick a percentage (roughly 30%) of your unused memory and swap spaces and calculate the SGA to use those 30% of this unused space. This calculated percentage may exceed your server hardware capabilities and may even exceed your requirement on the newly created database.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
