Oracle Database inspection found that the database's alert Log in a lot of the following errors: ORA-07445: predictionencountered: coredump [$ cold_qerf
Oracle Database inspection found that the database's alert Log in a lot of the following errors: ORA-07445: exception encountered: core dump [$ cold_qerf
During Oracle Database inspection, many alert logs of the database were found to report the following errors:
Wed Jun 10 10:06:35 2015
Errors in file/oracle/CQP/saptrace/usertrace/cqp_ora_11958.trc:
ORA-07445: exception encountered: core dump [$ cold_qerfxArrayMaxSize () + 12496] [SIGBUS] [Invalid address alignment] [0x000000029] [] []
Wed Jun 10 10:06:42 2015
Errors in file/oracle/CQP/saptrace/usertrace/cqp_ora_11958.trc:
ORA-00081: address range [0x600000000009C3B0, 0x6000000000000009c3b4) is not readable
ORA-07445: exception encountered: core dump [$ cold_qerfxArrayMaxSize () + 12496] [SIGBUS] [Invalid address alignment] [0x000000029] [] []
The trace file is as follows:
Ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [$ cold_qerfxArrayMaxSize () + 7456] [SIGBUS] [Invalid address alignment] [0x00000002C] [] []
Current SQL statement for this session:
SELECT 'oracleconnectsessionnum', count (*) "SessionCount" FROM v $ session
----- Call Stack Trace -----
Calling call entry argument values in hex
Location type point (? Means dubious value)
----------------------------------------------------------------------------
Ksedst () + 64 call _ etext_f () + 23058430 000000001? 000000001?
09029022096
Ksedmp () + 1680 call _ etext_f () + 23058430 000000001?
09029022096 C000000000000D20?
4001000000518e470?
ORA-07445 this is an error with the name of the ORA-00600, MOS especially for the ORA-600, ORA-7445, ORA-700 set the retrieval entrance, see MOS 153788.1, but this 7445 error failed to be found at this entrance. This error is an oracle Version 10.2 BUG on the HP Itanium platform, BUG no.: 5382798, because an exception occurred when compiling oracle 10.2 code using the C compiler of the HP Itanium platform, for more information, see MOS 386727.1. Oracle has released a patch for this BUG. If the above error occurs, we recommend that you install the corresponding patch and upgrade the database to 10.2.0.3 or later.
This article permanently updates the link address: