After applying 10.2.0.4, using LDAP causes ORA-07445 [unable_to_trans_pc]
(Doc ID 829513.1)
Last updated on SEPTEMBER 14, 2021
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.4 to 10.2.0.4 [Release 10.2]Information in this document applies to any platform.
Microsoft Windows XP (64-bit AMD64 and Intel EM64T)Microsoft Windows Server 2003 (64-bit AMD64 and Intel EM64T)Microsoft Windows Server 2003 R2 (64-bit AMD64 and Intel EM64T)
Symptoms
After applying the 10.2.0.4 patchset (on 64-bit Windows platforms), when using DBMS_LDAP, the following errors are observed in the alert log:
ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [unable_to_trans_pc]
often accompanied by:
ORA-00600: internal error code, arguments : [gslcsq_free], [Invalid input pointer], [], [], [], [], [], []
The trace file includes:
000007FFCCF41510 722 package body SYS.DBMS_LDAP_API_FFI
000007FFCC7E7500 1229 package body SYS.DBMS_LDAP
000007FFCC7E7500 1229 package body SYS.DBMS_LDAP
and the errorstack:
gslcsq_open_ssl <- spefcifa <- spefmccallstd <- pextproc <- PGOSF439_peftrust
<- PGOSF462_psdexsp <- 291 <- rpiswu2 <- psdextp <- pefccal
<- pefcal <- pevm_FCAL <- pfrinstr_FCAL <- pfrrun_no_tool <- pfrrun
<- plsql_run <- peicnt <- kkxexe <- opiexe <- kpoal8
<- opiodr <- ttcpip <- opitsk <- opiino <- opiodr
<- opidrv <- sou2o <- opimai_real <- opimai <- OracleThreadStart
<- PGOSF462_psdexsp <- 291 <- rpiswu2 <- psdextp <- pefccal
<- pefcal <- pevm_FCAL <- pfrinstr_FCAL <- pfrrun_no_tool <- pfrrun
<- plsql_run <- peicnt <- kkxexe <- opiexe <- kpoal8
<- opiodr <- ttcpip <- opitsk <- opiino <- opiodr
<- opidrv <- sou2o <- opimai_real <- opimai <- OracleThreadStart
Changes
The 10.2.0.4 patchset was applied on x64 Windows.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |