ORA-07445: [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x5A1113A] [ADDR:0xFFFFFFFFFFFFFFFF] [UNABLE_TO_READ]一般是Windows平台上常见的内存不足问题引起，在64 bit 或 32bit 平台均可能发生，一般建议通过增加SGA_MAX_SIZE和SGA_TARGET(ASMM)来解决该问题，同时增加SHARED_POOL_SIZE、 JAVA_POOL_SIZE、 STREAMS_POOL_SIZE到200M以上。
也可能是由于Windows平台感染了计算机病毒引起的，建议同时也要查杀病毒。
ORA-07445 [ACCESS_VIOLATION] [unable_to_trans_pc] on Windows Platforms Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.3 and later [Release: 10.2 and later ] Information in this document applies to any platform. ***Checked for relevance on 06-Oct-2011*** RDBMS 9.2 or greater on Windows platforms Symptoms ORA-07445: exception trouvee : image memoire [ACCESS_VIOLATION] [kpudcr2c+89] [PC:0x100CD3D1] [ADDR:0x19EC0000] [UNABLE_TO_WRITE] [] ORA-07445: Message 7445 not found; product=RDBMS; facility=ORA ; arguments: [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x5A1113A] [ADDR:0xFFFFFFFFFFFFFFFF] [UNABLE_TO_READ] ORA-27300: OS system dependent operation:WaitForSingleObject failed with status: 0 ORA-27301: OS failure message: The operation completed successfully. ORA-27302: failure occurred at: sssxcpttcs5 Changes none known Cause This error ORA-07445: Message 7445 not found; product=RDBMS; facility=ORA ; arguments: [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x5A1113A] [ADDR:0xFFFFFFFFFFFFFFFF] [UNABLE_TO_READ] is typical for WIN out of memory and is commonly seen when INIT.ORA parameters are set to that of the DBCA starter DB. This problem appears as likely on 64 bit platforms as on 32 bit Solution Please refer to Note 342443.1 and apply latest minipack. Have sufficient physical memory on Server so that you can allocate more SGA/PGA to the database. 1) Increase SGA_MAX_SIZE and SGA_TARGET so that you can accommodate following pools. 2) Restart the instance. 3) Increase INIT.ORA memory parameters and make sure following pools are set to recommended value i.e. 200M. a) SHARED_POOL_SIZE b) JAVA_POOL_SIZE c) STREAMS_POOL_SIZE ORA-07445: [ACCESS_VIOLATION] [unable_to_trans_pc]...[UNABLE_TO_READ] on Windows Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.1 and later [Release: 10.2 and later ] Microsoft Windows (32-bit) ***Checked for relevance on 06-Oct-2011*** Symptoms Session aborted on a select statement and a trace file is created with : ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x7C34538C] [ADDR:0xFFFFFFFF] [UNABLE_TO_READ] [] Cause Such arguments often highlight a resource failure where memory is the most common cause of this problem. Two hidden processes on the server were generating error messages and consuming all of the CPU : LSASS and SCCHOST These are often due to virus. (A later case was discovered due to a third party software named Quest Intrust Agent. ) Solution Problem was fixed after these two actions were performed: 1. Both processes were killed. 2. Antivirus software found some viruses and eliminated them. ORA-7445 [ACCESS_VIOLATION] [unable_to_trans_pc] [UNABLE_TO_WRITE] ORA-27301: OS failure message: Not enough storage ORA-27300 ORA-27302 Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.3 and later [Release: 10.2 and later ] Information in this document applies to any platform. ***Checked for relevance on 22-Oct-2010*** Symptoms These errors were encountered and the DB crashed.: ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x7C34126B] [ADDR:0x0] [UNABLE_TO_WRITE] [] ORA-27300: OS system dependent operation:CreateThread failed with status: 8 ORA-27301: OS failure message: Not enough storage is available to process this command. ORA-27302: failure occurred at: ssthrddcr. You may observe this in the trace file.: "Current SQL information unavailable - no SGA." Changes This could be triggered by hardware issues or an increase in volume or by day to day operations. Cause Insufficient memory. Solution Ensure that the existing memory is functioning properly. Verify you have enough memory available to support the configuration implemented. Another option is to decrease the size of the SGA. Check your OS log for hardware errors. ORA-07445: [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x609C6FA2] [ADDR:0x79A0040] [UNABLE_TO_READ] Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.2 and later [Release: 10.2 and later ] Information in this document applies to any platform. Symptoms ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x609C6FA2] [ADDR:0x79A0040] [UNABLE_TO_READ] [] occuring on a select with bind variables. The call stack will be exact or similar to: _clscugblmterm -> _clsc_term -> _clscterm -> _prom_terminate AND/OR malloc -> _malloc_unlocked -> cleanfree -> realfree --clscugblmterm is a RAC function, however in the case of this bug, the instances ARE NOT RAC. Cause The cause of this problem has been identified and verified in an unpublished Bug 4723824. This bug was introduced in 10.2.0.2. Solution Your options are: 1) Verify the patch you are on for 10.2.0.2 on windows is at least at patch least 8 as this bug is fixed in windows 10.2.0.2 patch 8. Please see Note:161549.1 for further information about windows patching OR 2) If on UNIX, determine from MOS if there is a one-off patch available on your database/OS version combination OR 3) RECOMMENDED: Upgrade to 11g as this bug is fixed in the 11g database version. Ora-7445 [ACCESS_VIOLATION] [unable_to_trans_pc] After Applying Windows 10.2.0.4 Patch Bundle 10 Applies to: Oracle Server - Standard Edition - Version: 10.2.0.4 to 10.2.0.4 - Release: 10.2 to 10.2 z*OBSOLETE: Microsoft Windows XP Microsoft Windows XP Symptoms On Windows, using Oracle 10.2.0.4, getting the following error in the alert.log: ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x7C911669] [ADDR:0x0] [UNABLE_TO_READ] [] --- Call Stack ---- _sldmGetHostName _sldmInit _ldmInit _keltnfy _kscnfy _ksucrp _opiino _opiodr _opidrv _sou2o _opimai_real _opimai Cause High CPU usage Solution Install KB 951312 from Microsoft to overcome this problem of high CPU usage. http://support.microsoft.com Drop User Cascade Results In ORA-03113 and ORA-7445 [ACCESS_VIOLATION] [unable_to_trans_pc] Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.5 - Release: 10.2 to 10.2 Information in this document applies to any platform. Checked for relevance on 4-Nov-2011 Symptoms Drop user cascade fails with ORA-3113 error: SQL> drop user vipr cascade; drop user vipr cascade * ERROR at line 1: ORA-03113: end-of-file on communication channel The alert.log shows: ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc] [PC:0x61FF2728] [ADDR:0x4] [UNABLE_TO_READ] [] In the trace we see: Current SQL statement for this session: drop java source "VIPR"."HOST" ----- Call Stack Trace ----- joxdrp opiexe opiosq0 opiosq opiodr rpidrus rpidru rpiswu2 rpidrv rpisplu rpispl kzdukl kzudrp opiexe opiosq0 kpooprx kpoal8 opiodr ttcpip opitsk opiino opiodr opidrv sou2o It is failing when trying to drop java source. Cause JVM is in REMOVING status. COMP_NAME VERSION STATUS Oracle Enterprise Manager 10.2.0.3.0 VALID Oracle Workspace Manager 10.2.0.1.0 VALID Oracle Database Catalog Views 10.2.0.3.0 VALID Oracle Database Packages and Types 10.2.0.3.0 VALID JServer JAVA Virtual Machine 10.2.0.3.0 REMOVING Solution Follow Note 276554.1 How to Reload the JVM in 10.1.0.X and 10.2.0.X to remove or reload JVM.
Leave a Reply