| 5593995 |
| Using Pro*C causes the system to run out of memory |
| Caused the system to hang. |
| The system hangs. |
| For OEL5U3, Remove references to pathnames that do not exist on your system in pcscfg.cfg. Fixed in OEL5U4. |
| |
| 5593995 |
| Using Pro*C causes the system to run out of memory |
| Caused the system to hang. |
| The system hangs. |
| For OEL5U3, Remove references to pathnames that do not exist on your system in pcscfg.cfg. Fixed in OEL5U4. |
| |
| 5593995 |
| Using Pro*C causes the system to run out of memory |
| Caused the system to hang. |
| The system hangs. |
| For OEL5U3, Remove references to pathnames that do not exist on your system in pcscfg.cfg. Fixed in OEL5U4. |
| |
| 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 |
| |
| 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 |
| |
| 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 |
| |
| 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. |
| |
| 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. |
| |
| 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. |
| |
| 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 |
| |
| 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 |
| |
| 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 |
| |
| 7689332 |
| ORACLE REPORTS I/O ERRORS FOR DB FILES RESIDING ON NFS DURING TEMPORARY NETWORK FAILURE |
| ORACLE INSTANCE WITH DB FILES ON NFS |
| If the nfs server becomes unavailable (due to a network
partition or server crash) and after major timeout (timeo*(retrans+1), specified in nfs mount options ), Oracle may report ORA-27072 in database alert logs which may results in an instance crash |
| Fixed in 2.6.18-128.0.0.0.2.EL5 kernel or higher |
| |
| 7689332 |
| ORACLE REPORTS I/O ERRORS FOR DB FILES RESIDING ON NFS DURING TEMPORARY NETWORK FAILURE |
| ORACLE INSTANCE WITH DB FILES ON NFS |
| If the nfs server becomes unavailable (due to a network
partition or server crash) and after major timeout (timeo*(retrans+1), specified in nfs mount options ), Oracle may report ORA-27072 in database alert logs which may results in an instance crash |
| Fixed in 2.6.18-128.0.0.0.2.EL5 kernel or higher |
| |
| 7689332 |
| ORACLE REPORTS I/O ERRORS FOR DB FILES RESIDING ON NFS DURING TEMPORARY NETWORK FAILURE |
| ORACLE INSTANCE WITH DB FILES ON NFS |
| If the nfs server becomes unavailable (due to a network
partition or server crash) and after major timeout (timeo*(retrans+1), specified in nfs mount options ), Oracle may report ORA-27072 in database alert logs which may results in an instance crash |
| Fixed in 2.6.18-128.0.0.0.2.EL5 kernel or higher |
| |
| 8253185 |
| Machine becomes unresponsive during swap pressure, due to direct reclaim threads |
| Systems with heavy memory and I/O load |
| During periods of heavy memory or I/O load that forces the system to swap, the machine becomes unresponsive. In the case of Oracle RAC deployments, this could result in RAC evictions. |
| Fixed in 2.6.18-92.1.17.0.1.el5 kernel or higher |
| |
| 8253185 |
| Machine becomes unresponsive during swap pressure, due to direct reclaim threads |
| Systems with heavy memory and I/O load |
| During periods of heavy memory or I/O load that forces the system to swap, the machine becomes unresponsive. In the case of Oracle RAC deployments, this could result in RAC evictions. |
| Fixed in 2.6.18-92.1.17.0.1.el5 kernel or higher |
| |
| 8253185 |
| Machine becomes unresponsive during swap pressure, due to direct reclaim threads |
| Systems with heavy memory and I/O load |
| During periods of heavy memory or I/O load that forces the system to swap, the machine becomes unresponsive. In the case of Oracle RAC deployments, this could result in RAC evictions. |
| Fixed in 2.6.18-92.1.17.0.1.el5 kernel or higher |
| |
| 8277913 |
| Netconsole module insertion fails with bonding on el5.3 |
| netconsole with bonding. |
| With bonding enabled, "/etc/init.d/netconsole start" fails with the following error Initializing netconsole FATAL: Error inserting netconsole (/lib/modules//kernel/drivers/net/netconsole.ko): Invalid argument [FAILED] |
| Fixed in 2.6.18-92.1.17.0.2.el5 kernel or higher |
| |
| 8277913 |
| Netconsole module insertion fails with bonding on el5.3 |
| netconsole with bonding. |
| With bonding enabled, "/etc/init.d/netconsole start" fails with the following error Initializing netconsole FATAL: Error inserting netconsole (/lib/modules//kernel/drivers/net/netconsole.ko): Invalid argument [FAILED] |
| Fixed in 2.6.18-92.1.17.0.2.el5 kernel or higher |
| |
| 8277913 |
| Netconsole module insertion fails with bonding on el5.3 |
| netconsole with bonding. |
| With bonding enabled, "/etc/init.d/netconsole start" fails with the following error Initializing netconsole FATAL: Error inserting netconsole (/lib/modules//kernel/drivers/net/netconsole.ko): Invalid argument [FAILED] |
| Fixed in 2.6.18-92.1.17.0.2.el5 kernel or higher |
| |
| 8451369 |
| If oracle-validated rpm is installed from CD, it fails to update the numa settings in /boot/grub/menu.lst |
| x86_64 AMD processor based systems |
| Recommended settings for numa will not be set on AMD processor based systems |
| After install, bring up the system. Append numa=off to the lines "kernel " in /boot/grub/menu.lst. Reboot the system for changes to take effect.Fixed in OEL5U4. |
| |
| 8451369 |
| If oracle-validated rpm is installed from CD, it fails to update the numa settings in /boot/grub/menu.lst |
| x86_64 AMD processor based systems |
| Recommended settings for numa will not be set on AMD processor based systems |
| After install, bring up the system. Append numa=off to the lines "kernel " in /boot/grub/menu.lst. Reboot the system for changes to take effect.Fixed in OEL5U4. |
| |
| 8451369 |
| If oracle-validated rpm is installed from CD, it fails to update the numa settings in /boot/grub/menu.lst |
| x86_64 AMD processor based systems |
| Recommended settings for numa will not be set on AMD processor based systems |
| After install, bring up the system. Append numa=off to the lines "kernel " in /boot/grub/menu.lst. Reboot the system for changes to take effect.Fixed in OEL5U4. |
| |
| 8499326 |
| Startup of multipathd results in cannot open /sbin/dasd_id and /sbin/gnbd_import |
| None so far |
| When starting multipathd, you see the following errors:multipathd: cannot open /sbin/dasd_id : No such file or directory,multipathd: cannot open /sbin/gnbd_import : No such file or directory |
| Fixed in OVM 2.2. For OEL5U3 and OEL5U4, contact Oracle support |
| |
| 8499326 |
| Startup of multipathd results in cannot open /sbin/dasd_id and /sbin/gnbd_import |
| None so far |
| When starting multipathd, you see the following errors:multipathd: cannot open /sbin/dasd_id : No such file or directory,multipathd: cannot open /sbin/gnbd_import : No such file or directory |
| Fixed in OVM 2.2. For OEL5U3 and OEL5U4, contact Oracle support |
| |
| 8499326 |
| Startup of multipathd results in cannot open /sbin/dasd_id and /sbin/gnbd_import |
| None so far |
| When starting multipathd, you see the following errors:multipathd: cannot open /sbin/dasd_id : No such file or directory,multipathd: cannot open /sbin/gnbd_import : No such file or directory |
| Fixed in OVM 2.2. For OEL5U3 and OEL5U4, contact Oracle support |
| |
| 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 |
| |
| 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 |
| |
| 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 |
| |
| 6501138 |
| ORA-12751: CPU TIME OR RUN TIME POLICY VIOLATION under certain type of workloads. |
| 11gR1 performance |
| Following messages appear in the oracle trace files "Runtime exceeded 900 seconds" |
| Reduce the load ( e.g: reduce no of users ) or enhance system configuration for that workload |
| |
| 6501138 |
| ORA-12751: CPU TIME OR RUN TIME POLICY VIOLATION under certain type of workloads. |
| 11gR1 performance |
| Following messages appear in the oracle trace files "Runtime exceeded 900 seconds" |
| Reduce the load ( e.g: reduce no of users ) or enhance system configuration for that workload |
| |
| 6501138 |
| ORA-12751: CPU TIME OR RUN TIME POLICY VIOLATION under certain type of workloads. |
| 11gR1 performance |
| Following messages appear in the oracle trace files "Runtime exceeded 900 seconds" |
| Reduce the load ( e.g: reduce no of users ) or enhance system configuration for that workload |
| |
| 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. |
| |
| 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. |
| |
| 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 |
| |
| 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 |
| |
| 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. |
| |
| 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. |
| |
| 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. |
| |
| 8525592 |
| Incorrect "SGA memory leak" errors encountered during the database shutdown |
| 11gR1 |
| During database shutdown, following errors are seen in the database trace files "ERROR: SGA memory leak detected.." |
| Workaround is to ignore these errors. |
| |
| 8525592 |
| Incorrect "SGA memory leak" errors encountered during the database shutdown |
| 11gR1 |
| During database shutdown, following errors are seen in the database trace files "ERROR: SGA memory leak detected.." |
| Workaround is to ignore these errors. |
| |
| 8525592 |
| Incorrect "SGA memory leak" errors encountered during the database shutdown |
| 11gR1 |
| During database shutdown, following errors are seen in the database trace files "ERROR: SGA memory leak detected.." |
| Workaround is to ignore these errors. |
| |