Who faced such errors in Oracle (10.2.0.4)?

  1. ORA-07445: exception: core dump [ACCESS_VIOLATION] [_intel_fast_memset.A + 44] [PC: 0x66D4AEC] [ADDR: 0x0] [UNABLE_TO_WRITE] []

  2. ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [clsdcxini + 62] [PC: 0x66A5EF8] [ADDR: 0x18] [UNABLE_TO_READ] []

  • I did not come across! Sorry, is this a poll? - 0-Level UNIX Monk
  • @Dillinger è morto, this is not a poll, just maybe someone came across what kind of crap it is! - Yaroslav
  • In these examples, not one rubbish, but several. Now it is not very convenient for me to sort out the errors in parts, telling what each of them means. How come from work, I can answer. In the meantime, add a fav. - 0-Level UNIX Monk
  • @Dillinger è morto, ok, thanks) - Yaroslav
  • Here, I quickly googled you: support.oracle.com/knowledge/Oracle%20Database%20Products/… - In general, there is a 64-bit Vendo, there is not enough RAM, and, respectively, a DB memory error. How to fix - there is oracle on the site, but I did not register there, and I can not see. If you already have such a database, then surely there is a reg on the oracle, so you can fix it. I delete the question from the favorites, since I answered it in this comment. Good luck in fixing) - 0-Level UNIX Monk

2 answers 2

See what actions are needed:

$ oerr ora 7445

07445, 00000, "exception encountered: core dump [% s] [% s] [% s] [% s] [% s] [% s]"
// * Cause: An operating system
// creation of a core file. This is an internal error.
// * Action: ORA-07445 Lookup tool
// (reference Note 7445.1)
// ORA-07445 error encountered.
//
// An Incident has been created
// Diagnostic Repository (ADR). When logging a service request, use
// the Incident Packaging Service (IPS) from the Support Workbench
// or the ADR Command Interpreter (ADRCI) to automatically package the
// relevant trace information (reference My Oracle Support Note 411.1).

The process, server or background, died as a result of an exception at the system level and a core dump was created. There is no single cause for the error.

This is an internal error, in case of which it is necessary to turn in support. In this particular case, it no longer makes sense, since 10g has long been out of support .

Further actions depend on where this error occurred and what preceded it. For starters, you can see the ALERT.LOG alarm log in the directory:

 SQL> show parameter background_dump_dest NAME TYPE VALUE ------------------------------------ ----------- ------------------------------------------ background_dump_dest string /app/oracle/diag/rdbms/o10gr2/o10gr2/trace

Perhaps installing patches will help (an account on My Oracle Support is required):

BUG: 5205552 - EXCEPTIONAL HIG VM SIZE USAGE FOR ORACLE.EXE ON 64 BIT X86 WINDOWS PLATFORM

On a Windows 64-bit system, a log of the following has been reported:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [clsdcxini + 62] [PC: 0x6515858] [ADDR: 0x18] [UNABLE_TO_READ] []
or
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_ intel_fast_memset.A + 44] [PC: 0x6544028] [ADDR: 0x0] [UNABLE_TO_WRITE] []
or
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC: 0x6515858] [ADDR: 0x18] [UNABLE_TO_READ] []

SOLUTION
If you are having any problems, install Patch Set Bundle 23 or above (available as Patch 7353785).

  • the investigation led to the Oracle Trace File Analyzer (TFA) utility, just where to get it? - Yaroslav
  • And why do you need him? TFA was introduced from 11.02. - 0xdb
  • to parse the trace. - Yaroslav
  • Try tkprof. - 0xdb
  • one
    Well, yes, I already gave an example . - 0xdb

In addition to the answer from @ 0xdb , any analysis of any ORA-????? worth starting with ORA-????? errors, I want to add a description of the analysis of critical errors ...

On the Oracle DB support page, there is a document 153788.1 to help in case of critical errors ( ORA-600 , ORA-7445 , ORA-700 ) - in it you can specify the version of Oracle DB and the first argument ( _intel_fast_memset - in your case) errors in the search form .

MOS (My Oracle Support) found one suitable document - ORA-7445 [memset] (Doc ID 1359594.1) , which in turn refers to Bug 20847534 - ORA-7445 Dump with Tag [Application data integrity disrupting] and Called from kgh * Routines on Solaris Sparc Platforms (Doc ID 20847534.8)