solaris system kernel parameters | with dataguard
- From: "Vincent verpoort" <vincent.verpoort@xxxxxxxxx>
- To: "Oracle-L Freelists" <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 17 Aug 2006 13:52:17 +0200
Hi Oracle gods ;)
Question 9.2.0 on solaris 9
I have a database running on the machine with the next ora file
# The basics ...
db_name =
control_files =
db_block_size = 8192 # Should match OS/Veritas
block size...
compatible = 9.2.0.6.0
# rollback
undo_management = auto # turn AUM on
undo_retention = 1200 # default setting
undo_suppress_errors = true # avoid rollback (not AUM)
error messages
undo_tablespace = aum01 # AUM tablespace
# tuning parameters
db_files = 100 # < 50 and checkpoint
process not enabled !!
db_file_multiblock_read_count = 16 # 16*8=128 - the logical
volume strip size...
db_cache_size = 150M # Downsized for
multi-instance machine spec
shared_pool_size = 300M # Downsized for
multi-instance machine spec
shared_pool_reserved_size = 30M # 10% of Shared Pool
java_pool_size = 1M # 1 meg minimum if not using
Java
cursor_sharing = force # Force optimizer to reuse
similar sql stmts
session_cached_cursors = 50 # Starting value, reduce
load on library cache
pga_aggregate_target = 256M # superceeds sort_area_size,
hash_area_size ...
workarea_size_policy = auto # can only specify auto when
pga_aggregate_target is set
statistics_level = typical # this is the default
sga_max_size = 1024M # max size SGA can grow to
#large_pool_size = xx # need to set when using
rman, PQO and so on
# Optimizer parameters
optimizer_mode = choose
query_rewrite_enabled = true
query_rewrite_integrity = trusted
optimizer_index_caching = 90 # %age of idx blocks
expected to be found in the BC
optimizer_index_cost_adj = 20 # cost of idx IO to FTS IO
(20% as costly)
# Redo/Archive Logs - 2 mandatory, 1 optional (can have up to 5)
archive_lag_target = 900 # switch logfiles every 15
minutes!
log_buffer = 1048576 # In 8i, LGWR will kick in
at 1m limits (not 1/3rd!)
log_archive_start = true # if you want automatic
archiving
log_archive_dest_1 = "
log_archive_dest_2 = "
log_archive_min_succeed_dest = 1
log_archive_format = vodp1_%s.arc
log_archive_trace = 0 # disable archive trace
output
# Resource/system monitoring
resource_limit = true
audit_trail = false # OK this is mostly a
chocolate teapot -
timed_statistics = true # Turn on and off as needed
# OS File I/O
#utl_file_dir =
# Parallel Query
parallel_max_servers = 0
parallel_automatic_tuning = true # oracle to tune PQO, mem
alloc from large_pool
# General
processes = 100 # medium
max_dump_file_size = 10240 # limit trace file size to 5
Meg each
global_names = false # Pain in the ass thing,
this is
max_enabled_roles = 100
open_cursors = 500
open_links = 50
# Dump destinations
background_dump_dest =
core_dump_dest =
user_dump_dest =
audit_file_dest =
Now i want to start a other sid with the smal ora file ( well the same
setting )
when i do a startup nomount i get
Thu Aug 17 13:36:32 2006
Starting ORACLE instance (normal)
Thu Aug 17 13:36:32 2006
Errors in file /applogs/oracle/dbase/vodp1/user/vodp1_ora_4981.trc:
ORA-27154: post/wait create failed
ORA-27300: OS system dependent operation:semget failed with status: 28
ORA-27301: OS failure message: No space left on device
ORA-27302: failure occurred at: sskgpbitsper
and
Dump file /applogs/oracle/dbase/vodp1/user/vodp1_ora_4981.trc
Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
With the Partitioning and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production
ORACLE_HOME = /opt/app/oracle/product/9.2.0
System name: SunOS
Node name: vasdbp1
Release: 5.9
Version: Generic_118558-24
Machine: sun4u
Instance name: vodp1
Redo thread mounted by this instance: 0 <none>
Oracle process number: 0
4981
*** 2006-08-17 13:36:32.863
ksedmp: internal or fatal error
ORA-27154: post/wait create failed
ORA-27300: OS system dependent operation:semget failed with status: 28
ORA-27301: OS failure message: No space left on device
ORA-27302: failure occurred at: sskgpbitsper
I did a reboot thinking the /etc/system file was edited but no system reboot
was dunn
but i still get the error
stoped the already running started the new db, no problem starts like a
dream and then i get the error on the old db that i try to start.
Really looks like a memory segement problem. But as you can see below enough
space
sessions parameter is 225
set shmsys:shminfo_shmmax=4294967285
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=10
set semsys:seminfo_semmni=8
set semsys:seminfo_semmsl=512
set semsys:seminfo_semmns=4096
set semsys:seminfo_semopm=100
set semsys:seminfo_semvmx=32767
I looked alle over the internet en metalink can't find any handels all
memory or os things see to be correct
Anyone got a handel i can use to go on with finding the awser
--
Vincent Verpoort
,.-~`"'~-.,_,.-~`"'~-.,_,.-~`"'~-.,_,.-~`"'~-.,_,.-~`"'~-.,_
Communiceren is begrepen worden
^*<-._,.->*^*<-._,.->*^*<-._,.->*^*<-._,.->*^*<-._,.->*^*<-.
Other related posts:
