| 10g DBCA: ASM Instance won't start - Out of Memory [message #62127] |
Mon, 28 June 2004 14:52  |
MSD
Messages: 2
Registered: June 2004
|
Junior Member |
|
|
No ASM instance is running on the machine.
Using DBCA to create an ASM instance it fails with:
ORA-27102: out of memory
Details...
Solaris 8 SPARC
/etc/system configured as such:
set noexec_user_stack=1
set semsys:seminfo_shmmax=0xffffffff
set semsys:seminfo_shmmin=1
set semsys:seminfo_shmmni=100
set semsys:seminfo_shmseg=10
set semsys:seminfo_semmni=100
set semsys:seminfo_semmsl=1000
set semsys:seminfo_semmns=2000
set semsys:seminfo_semopm=100
set semsys:seminfo_semvmx=32767
System has been rebooted.
prtconf | grep size
Memory size: 1536 Megabytes
swap space 3G
shell is csh with:
ulimit -Sa
ulimit -Ha
Veritas 3.1.1 VM installed but not managing the disk being used for ASM.
Tried the default settings and also tried to increase these values in the ASM Parameters. Neither worked.
large_pool_size=113165824
shared_pool_size=113165824
Your help is appreciated in trying to figure out why I keep getting this out of memory error.
Thank you,
MSD
|
|
|
|
|
|
| Re: 10g DBCA: ASM Instance won't start - Out of Memory [message #62302 is a reply to message #62127] |
Tue, 13 July 2004 11:04  |
Frank Naude
Messages: 4587
Registered: April 1998
|
Senior Member |
|
|
Hi,
You should only specify the following parameters for your ASM instance:
INSTANCE_TYPE=ASM
DB_UNIQUE_NAME=+ASM
ASM_POWER_LIMIT=1
ASM_DISKSTRING=...
ASM_DISKGROUPS=...
LARGE_POOL_SIZE=8M
Thus, remove the SHARED_POOL_SIZE parameter from your parameter file and reduce your LARGE_POOL_SIZE to about 8MB.
Best regards.
Frank
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
