6045759 |
Applications using random numbers may hang or report errors if there is insufficient random data in the system |
Oracle applications tools (e.g: java apps) requesting random data |
Oracle applications tools (e.g: java apps) requesting random data from /dev/random either hang or print out the following information message: Not enough random bytes available. Please do some other work to give the OS a chance to collect more entropy! |
If using e1000 or bnx2 network drivers on OEL5 the entropy=1 module option can be set for either of these drivers in /etc/modprobe.conf. Fixed in 2.6.18-8.0.0.4.1.el5 kernel or higher |
|
6075960 |
If an ORACLE_HOME resides on an nfs partition, a reboot while Oracle is running may cause a panic |
Oracle deployments with Oracle_home on an nfs partition |
If the ORACLE_HOME resides on an nfs partition and the system is rebooted while an Oracle instance is still running, the system may panic. This does not cause a data corruption, but the system will need to be restarted |
Fixed in 2.6.18-53.0.0.0.1.el5 kernel or higher. For other kernel versions lower than this, please shutdown the database instance before reboot of the server. |
|
6081490 |
With selinux enabled, ocfs2 fails to startup via /etc/init.d/o2cb start |
Automated startup of ocfs2 via /etc/init.d/o2cb start |
With selinux enabled, starting ocfs2 via "/etc/init.d/o2cb start" fails with the following error: "mount: block device ocfs2_dlmfs is write-protected mounting read-only. mount: cannot mount block device ocfs2_dlmfs read-only.
Unable to mount ocfs2_dlmfs filesystem Failed" |
For OEL5U3, Manually mount OCFS2_DLMFS using the command mount -t ocfs2_dlmfs ocfs2_dlmfs /dlm. Fixed in OEL5U4. |
|
6219364 |
Systems using kexec/kdump with Broadcom Tigon3 NICs will not be able to dump vmcore. |
Troubleshooting of systems via kexec/kdump with Broadcom Tigon3 NICs. |
When troubleshooting with kexec/kdump, the system throws errors when trying to bring up the ethernet interface when trying to connect to the system on to which the vmcore should be dumped. This does not affect normal operations. |
Fixed in 2.6.18-53.0.0.0.1.el5 kernel |
|
6241862 |
Using sysrq+t with netconsole/tg3 configured causes the system to panic. |
Troubleshooting of systems via "alt sysrq t" with netconsole/tg3 configured. |
When troubleshooting system, usage of "alt + sysrq + t" with netconsole/tg3 configured to take a system stack trace may cause the system to panic . This does not affect the normal operation of the system. |
Fixed in 2.6.18-92.0.0.0.1.el5 kernel or higher |
|
6140224 |
SQLPLUS FAILS TO LOAD LIBNNZ11.SO WITH SELINUX ENABLED ON EL5/RHEL5 |
11gR1 and 11gR2 |
sqlplus fails with the following error message "cannot restore segment prot after reloc: Permission denied" |
Disable selinux |
|
7036544 |
Database instance startup fails when sga_target was set to multiples of 4096M |
11.1.0.6 |
Database 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")" |
Fixed 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. |
|
7135702 |
ORA-15001 when shutting down the database instance |
11.1.0.7 database shutdown |
Errors in database alert log "Unexpected communication failure with ASM instance: error 15001 (ORA-15001: diskgroup""does not exist or is not mounted )" |
Apply patch 7135702 |
|
7272646 |
Database instance startup fails when memory_target value is >4096M |
11.1.0.7 database startup |
Database 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" |
Apply patch 7520217 or reduce memory_target value. |
|
8451866 |
Incorrect multipath.conf setting affects RAC node failover. Settings(features = "1 queue_if_no_path") and/or (no_path_retry = queue) causes the node hang if io path fails. no_path_retry has to be set to the numeric value explicitly. |
All applications using device mapper multipath devices which have contingency plan in case of io path failure. |
RAC node hangs if io path fails. |
In configuration file /etc/multipath.conf,set no_path_retry and polling_interval to the numeric values, for example, "no_path_retry=5" and "polling_interval=10" so as to disable queuing. These values depend on system workload. |
|