E-LDAP Schema Caching Does Not Work Through Port 636 Over SSL

(Doc ID 620168.1)

Last updated on DECEMBER 07, 2016

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.2 and later
Information in this document applies to any platform.
***Checked for relevance on 5-JUN-2015***

Symptoms


The entire directory authentication occurs through port 636 (secure). Port 389 (non-secure) has been shut off during normal operations. When the need to re-cache the schema, we are not able to do this through the non-secure port. How can we do the re-caching process using port 636? The LDAP directory authentication occurs through port 636 (secure). Port 389 (non-secure) has been shut off during normal operations. When there is a need to re-cache the schema, the re-caching process fails when using port 636.

As of PT 8.50 customers may also see the following error when the AE process is run:

Failed to find a LDAP server to load schema (140,1004)

Process ABENDED at Step LDAPSCHEMA.MAIN.Step02 (PeopleCode) -- RC = 4 (108,524)

Process %s ABENDED at Step %s.%s.%s (Action %s) -- RC = %s
PSJNI: ERROR: Could not unload the Java VM

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms