DESCRIPTION OF PROBLEM FIXED FOR APAR 'SE71452' :
-------------------------------------------------
After the migration LDAP server will not stay running which caused a company wide SSO issue for connections to this system.
My question – what migration, what changed?
Troubleshooting
Problem
Attempts to start any/all LDAP server instances fails reporting with message sequence GLD040B rc -456, GLD040A, GLD0416 and SQL0456. Both the GLD040B rc 456 and the SQL0456 pointed to QGLDRSDX already existing. Resolution is to drop the QGLDRSDX function.
Resolving The Problem
Attempts to start any or all LDAP server instances fails reporting with message sequence GLD040B rc -456, GLD040A, GLD0416 and SQL0456. Both the GLD040B rc 456 and the SQL0456 pointed to QGLDRSDX already existing. Resolution is to drop the QGLDRSDX function.
Here is an example of the error message highlighting the SQL function already exists:
SQL0456 Diagnostic 30 09/11/11 10:33:53.470978 QSQPROC QSYS *STMT
From user . . . . . . . . . : QSECOFR
From module . . . . . . . . : QSQPROC
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 45045
To module . . . . . . . . . : QSQPROC
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 45045
Message . . . . : Specific name QGLDRSDX in QDIRSRV already exists.
Resolution in this case was to drop the existing QGLDRSDX function:
Identify whether you are using SYSTEM or SQL naming.
Issue the STRSQL command, press F13, Option 1, then check Naming convention. It will be either *SYS or *SQL:
o If *SYS , press F12 to get back to the SQL statement entry screen and run the following command:
DROP SPECIFIC FUNCTION QDIRSRV/QGLDRSDX
o If *SQL, run the following command:
DROP SPECIFIC FUNCTION QDIRSRV.QGLDRSDX
Once you have done this, you should exit SQL mode (F3, Option 1) and try starting the LDAP instance again (i.e. STRTCPSVR *DIRSRV).
Dropping the existing function will either allow the LDAP instance to start or get further in the startup process to the next issue.
The following PTFs permanently resolve the issue by using "CREATE OR REPLACE FUNCTION" instead of "CREATE FUNCTION" on the SQL statement executed by the IBM Tivoli Directory Server at startup.
APAR documenting this issue: SE71452<
https://www-01.ibm.com/support/docview.wss?uid=nas2SE71452>
PTFs were generated for all current OS versions:
IBM i 7.4: 5770SS1-SI70236
IBM i 7.3: 5770SS1-SI70189
IBM i 7.2: 5770SS1-SI70235
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx<mailto:psteinmetz@xxxxxxxxxx>
http://www.pencor.com/
midrange.com
