Installing OSSO 10.1.4 Against an Oracle Database Server 11.2 Fails with ORA-24247 (Doc ID 1280356.1)

Last updated on MARCH 09, 2017

Applies to:

Oracle Application Server Single Sign-On - Version 10.1.4.0.1 to 10.1.4.3 [Release 10gR3]
Oracle Fusion Middleware - Version 10.1.4.0.1 to 10.1.4.3.0 [Release AS10gR2 to AS10gR3]
Information in this document applies to any platform.

Symptoms

Environment:


During installation OC4J_SECURITY will not start at the 'OC4J Instance Configuration Assistant'. This is because the 'Single Sign-On Configuration Assistant' fails during installation.


This error can be seen in the INVENTORY_HOME/logs/installActions<datestamp>.log The command that failed can also be found in the $ORACLE_HOME/cfgtoollog/configtools<datestamp>.log:

ACTION by SSOConfigAssistant :
/u01/product/osso_10.1.4/bin/sqlplus orasso/*****@"cn=idm11g,cn=oraclecontext"
 @/u01/product/osso_10.1.4/sso/admin/plsql/sso/ssooidd.sql oid.au.oracle.com 3131 "cn=orcladmin" ***** Y

SQL*Plus: Release 10.1.0.5.0 - Production on Thu Jan 6 19:41:23 2011

Copyright (c) 1982, 2005, Oracle. All rights reserved.

SQL> Connected.
SQL> Creating OID entries for SSO
Error code : 1
Error message: User-Defined Exception
LDAP error : ORA-24247: network access denied by access control list (ACL)
ERROR: deleting application entry
Error code: 1
Error message: User-Defined Exception
ERROR: creating SSO users and groups in OID

PL/SQL procedure successfully completed.

*** Refreshing WWC OID cache....***
declare
*
ERROR at line 1:
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "ORASSO.WWSEC_OID", line 1199
ORA-06512: at "ORASSO.WWSEC_OID", line 1328
ORA-06512: at "ORASSO.WWSEC_OID", line 2498
ORA-06512: at "ORASSO.WWSEC_OID", line 2528
ORA-06512: at "ORASSO.WWSEC_OID", line 1606
ORA-06512: at "ORASSO.WWSEC_OID", line 1755
ORA-06512: at "ORASSO.WWSEC_OID", line 2133
ORA-06512: at line 8


No errors.

 

This is an "unhandled user-defined exception" and no error is passed back to the SSOCA. Therefore the installer continues but later configuration assistants fail because the OID seed data has not been configured. The first symptom noticed in the installer is that the 'OC4J Instance Configuration Assistant' fails.
OC4J_SECURITY will not start at the 'OC4J Instance Configuration Assistant'.

The following error may also be seen when SSOCA fails:

Oracle.Security.Sso.Server.Conf.Configurationexception: Ldap

 

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