Applies to:
Oracle Net Services - Version 9.2.0.6 and laterInformation in this document applies to any platform.
Symptoms
On Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production:
Oracle continuously (every 1 minute) generate 'ORA-07445: exception encountered: core dump [nttexp()+0] [SIGSEGV] [Address not mapped to object] [0x000000000] [] []' errors and trace file in Default Background Dump Destination folder, /opt/oracle/product/9.2.0.6/rdbms/log directory
------------------
Errors in file /opt/oracle/product/9.2.0.6/rdbms/log/prod1_ora_24310.trc:
ORA-07445: exception encountered: core dump [nttexp()+0] [SIGSEGV] [Address not mapped to object] [0x000000000] [] []
Fri Aug 31 01:54:52 2012
Errors in file /opt/oracle/product/9.2.0.6/rdbms/log/prod1_ora_24509.trc:
ORA-07445: exception encountered: core dump [nttexp()+0] [SIGSEGV] [Address not mapped to object] [0x000000000] [] []
Fri Aug 31 01:55:52 2012
Errors in file /opt/oracle/product/9.2.0.6/rdbms/log/prod1_ora_24887.trc:
ORA-07445: exception encountered: core dump [nttexp()+0] [SIGSEGV] [Address not mapped to object] [0x000000000] [] []
...
...
------------------
Errors in file /opt/oracle/product/9.2.0.6/rdbms/log/prod1_ora_24310.trc:
ORA-07445: exception encountered: core dump [nttexp()+0] [SIGSEGV] [Address not mapped to object] [0x000000000] [] []
Fri Aug 31 01:54:52 2012
Errors in file /opt/oracle/product/9.2.0.6/rdbms/log/prod1_ora_24509.trc:
ORA-07445: exception encountered: core dump [nttexp()+0] [SIGSEGV] [Address not mapped to object] [0x000000000] [] []
Fri Aug 31 01:55:52 2012
Errors in file /opt/oracle/product/9.2.0.6/rdbms/log/prod1_ora_24887.trc:
ORA-07445: exception encountered: core dump [nttexp()+0] [SIGSEGV] [Address not mapped to object] [0x000000000] [] []
...
...
------------------
We need to stop this error ORA-7445 since it is filling up file system
Changes
No known changes.
Cause
Issue was related to the 9iR2 Instance/Service registration with 11gR2 Listener running on the default port, 1521.
Verified from the Listener Control (LSNRCTL) STATUS/SERVICES command outputs against the 11gR2 Listener.
Solution
1. Disable the Service Registration for the 9iR2 instance with the 11gR2 Listener by setting the LOCAL_LISTENER initialization parameter for the 9iR2 database instance(s) to point to the 10gR2 Listener's port.
For example:
SQL> ALTER SYSTEM SET LOCAL_LISTENER = '(ADDRESS = (PROTOCOL = TCP)(HOST =hostname)(PORT = 1526))' SCOPE=BOTH;
2. Or if the Service registration for the 9iR2 instance(s) are no needed, then set the LOCAL_LISTENER initialization parameter for the 9iR2 database instance(s) to point to an unused port, such as 1528:
For example:
SQL> ALTER SYSTEM SET LOCAL_LISTENER = '(ADDRESS = (PROTOCOL = TCP)(HOST = hostname)(PORT = 1528))' SCOPE=BOTH;
3. Then check the alert log and Default Background Dump Destination folder to ensure the trace files are no longer being written.
For example:
SQL> ALTER SYSTEM SET LOCAL_LISTENER = '(ADDRESS = (PROTOCOL = TCP)(HOST =hostname)(PORT = 1526))' SCOPE=BOTH;
2. Or if the Service registration for the 9iR2 instance(s) are no needed, then set the LOCAL_LISTENER initialization parameter for the 9iR2 database instance(s) to point to an unused port, such as 1528:
For example:
SQL> ALTER SYSTEM SET LOCAL_LISTENER = '(ADDRESS = (PROTOCOL = TCP)(HOST = hostname)(PORT = 1528))' SCOPE=BOTH;
3. Then check the alert log and Default Background Dump Destination folder to ensure the trace files are no longer being written.
Niciun comentariu:
Trimiteți un comentariu