My Oracle Support Banner

Siebel Application Crashes on 64 Bit Platforms when LDAP Naming Resolution Used (Doc ID 736139.1)

Last updated on OCTOBER 24, 2008

Applies to:

Oracle Net Services - Version: 10.1.0.3.0 to 10.2.0.1.0
This problem can occur on any platform.

Symptoms

Siebel application process crashes when using LDAP naming resolution on 64 bit platforms
That is NAMES.DIRECTORY_PATH=(LDAP) in the SQLNET.ORA file.
Running local naming resolution NAMES.DIRECTORY_PATH=(TNSNAMES), works fine.
Stack from the crash will be similar to following :

_SigBusSegvIotHandler (4, 794f5dd0, 794f5b18, 7f70ab9c, 7ddcb9d4, 7f70ab70) + 118
 __sighndlr (4, 794f5dd0, 794f5b18, 7f6eade8, 0, 0) + c
 call_user_handler (4, 3962b, c, 0, 7d482400, 794f5b18) + 3b8
 ???????? (329ff30, 174e08, 794f5f1c, 0, 743cc644, ffffff6c)
 nzty1as_algstart (329ff30, 794f61dc, 7, 794f6234, 20, 0) + 174
 nztysgs_genseed (100, 20, 794f62ac, 2c00, 753566b8, 0) + a0
 nztysi0_init (329ff30, 1, 0, afd9a0, 743cc644, 3247b80) + 64
 nzdsi_init (794f633c, 794f642c, 753566b8, 0, 329ff30, 329ff88) + 178
 nzdsi_initialize (3255e60, 794f642c, 1c00, 14800, 747ede14, 14ba8) + 28
 gsluinit (3254248, 794f64d4, 0, 753043c8, 0, 319fb70) + 65c
 gsluizgcGetContext (5174, 5000, 0, 752d1eb4, ae8024, 0) + 60
 ora_create_discov_hdl (0, 3, 0, 2, 6, 753094c4) + 4
 nnfloiddisco (794f65fc, 75282480, 1, 794f679c, 794f6798, 0) + 4f4
 nnflgcp  (753566b8, 75282480, 64, 794f679c, 794f6798, 753094c4) + 140
 nnflobc  (753566b8, f, 753094c4, 6, 578, 5) + 310
 nnflcgc  (753566b8, 0, 2f7dcd4, 0, 6, 75282690) + 108
 nnflboot (753566b8, 324a410, 0, 97225c, 0, 752d1eb4) + ec
 nnfgrne  (753566b8, 74977b30, 2fc083c, 0, 2fa5338, 752d1eb4) + 254
 nlolgobj (753566b8, 794fb5f0, 16, 794f822c, 794f8228, 75280fc0) + 730
 nnfun2a  (753566b8, 794f9420, 32521a8, 2, 8, 1000) + 188
 nnfsn2a  (794f9318, ff, 794f931c, 794fa490, 794f9420, 794f941c) + 38
 niqname  (0, 1001, 794fb5f0, 8, 0, 752d1eb4) + 778
 kwfnran  (3480c90, 4, 794fb5f0, 794fd720, 324740c, 3247410) + 24c
 kwfcinit (32413cc, 3480c90, 8, 794fd724, 794fd720, 32280c8) + 218
 kpuatch  (80, 322dc14, 3480c90, 8, 0, 0) + 894
 OCIServerAttach (323d1c4, 322dc14, 3480c90, 8, 0, 323d1c4) + 74

Oracle Net client trace of the failure ends :

(1) [30-JAN-2008 17:07:47:514] nzdcpgd_get_default_oracle_data: exit
(1) [30-JAN-2008 17:07:47:514] nzdcpig_init_global: exit
(1) [30-JAN-2008 17:07:47:515] nzgblinitialize: exit
(1) [30-JAN-2008 17:07:47:515] nzumalloc: entry
(1) [30-JAN-2008 17:07:47:515] nzumalloc: entry
(1) [30-JAN-2008 17:07:47:515] nzumalloc: entry
(1) [30-JAN-2008 17:07:47:515] nzumalloc: entry
(1) [30-JAN-2008 17:07:47:515] nzumalloc: entry
(1) [30-JAN-2008 17:07:47:516] nzumalloc: entry
(1) [30-JAN-2008 17:07:47:516] nzumalloc: entry



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
  Cause
  Solution
  References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.