Printer View

Browse Published Validated Configurations  >  Validated Configuration Details  >  Virtual Machine Configurations
Linux Distribution Details
OSOracle Linux 5 Update 7 x86_64
Kernelkernel-uek-2.6.32-200.13.1.el5uek or higher
Virtualization TypeParavirtualized
 
Filesystems Tested
File SystemMount OptionsDetails
ext3NoneFor single instance database files.
Configuration Files
Comments
/etc/modprobe.conf alias eth0 xennet -
 alias scsi_hostadapter xenblk -
/etc/security/limits.conforacle soft nproc 131072 -
 oracle hard nofile 131072 -
 oracle soft nofile 131072# depending on size of db, these may need to be larger
 oracle soft core unlimited -
 oracle hard core unlimited -
 oracle hard nproc 131072 -
/etc/sysctl.confnet.core.rmem_default = 262144 -
 net.core.wmem_default = 262144 -
 fs.aio-max-nr = 3145728 -
 fs.file-max = 6815744 -
 net.ipv4.ip_local_port_range = 9000 65500 -
 net.core.rmem_max = 4194304 -
 net.core.wmem_max = 262144 -
 kernel.shmmax = 16892102656 -
 kernel.shmall = 8187841 -
 kernel.shmmni = 4096 -
 kernel.sem = 250 32000 100 142 -
 kernel.msgmni = 2878 -
 kernel.msgmax = 8192 -
 kernel.msgmnb = 65536 -
 net.ipv4.tcp_syncookies = 1 -
 kernel.core_uses_pid = 1 -
 net.ipv4.conf.default.rp_filter = 2 -
 kernel.sysrq = 1 -
Miscellaneous
-
Oracle Software
OracleOracle Database 11g, Single Instance for Linux x86_64
Version11.1.0.6
PatchNone
 
Configuration Feedback
Bug No9466221
SummaryDmesg displays "Task XXXX: blocked for more than 120 seconds" under load
AffectsSystems on OEL5.5/RHEL5.5
SymptomsFollowing messages may be seen in dmesg - "Task XXXX: blocked for more than 120 seconds"
SolutionThese messages are only for information;newly added in OEL5.5/RHEL5.5. To disable this messages echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
 
Bug No10056679
Summaryunable to start X
AffectsX environment
SymptomsOn some hardware startup of X environment may fail after upgrading to Unbreakable Enterprise Kernel with following Error:#Fatal server error:#Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices.
Solutionreconfigure X using command "X -configure" and use generated configuration file to start X environment.
 
Bug No6140224
SummarySQLPLUS FAILS TO LOAD LIBNNZ11.SO WITH SELINUX ENABLED ON EL5/RHEL5
Affects11gR1 and 11gR2
Symptomssqlplus fails with the following error message "cannot restore segment prot after reloc: Permission denied"
SolutionDisable selinux
 
Bug No6501138
SummaryORA-12751: CPU TIME OR RUN TIME POLICY VIOLATION under certain type of workloads.
Affects11gR1 performance
SymptomsFollowing messages appear in the oracle trace files "Runtime exceeded 900 seconds"
SolutionReduce the load ( e.g: reduce no of users ) or enhance system configuration for that workload
 
Bug No7036544
SummaryDatabase instance startup fails when sga_target was set to multiples of 4096M
Affects11.1.0.6
SymptomsDatabase instance startup fails with the following error " ORA-12853: insufficient memory for PX buffers: current 0K, max needed 2640K and ORA-04031: unable to allocate 21544 bytes of shared memory ("large pool","unknown object","large pool","PX msg pool")"
SolutionFixed in 11.1.0.7, for 11.1.0.6 set the parameter large_pool_size in init.ora or increase the sga_target size.
 
Bug No7135702
SummaryORA-15001 when shutting down the database instance
Affects11.1.0.7 database shutdown
SymptomsErrors in database alert log "Unexpected communication failure with ASM instance: error 15001 (ORA-15001: diskgroup""does not exist or is not mounted )"
SolutionApply patch 7135702
 
Bug No7272646
SummaryDatabase instance startup fails when memory_target value is >4096M
Affects11.1.0.7 database startup
SymptomsDatabase instance startup fails with the following error in the database alert log "error 27103 detected in background process, ORA-27103: internal error" and trace log error " Linux-x86_64 Error: 11: Resource temporarily unavailable"
SolutionApply patch 7520217 or reduce memory_target value.
 
Bug No8525592
SummaryIncorrect "SGA memory leak" errors encountered during the database shutdown
Affects11gR1
SymptomsDuring database shutdown, following errors are seen in the database trace files "ERROR: SGA memory leak detected.."
SolutionWorkaround is to ignore these errors.
 
 
Copyright (c) 2007, Oracle Corporation. All Rights Reserved.