Oracle Error Code 49
you could encounter while running or installing Oracle Internet Directory. It contains these sections: Problems and Solutions Need More Help? J.1 Problems and Solutions This section describes common Oracle Internet Directory error messages, problems and solutions. It contains the following topics: Installation Errors TCP/IP Problems Directory Server Error Messages and Causes Troubleshooting Password Policies Troubleshooting Directory Performance Troubleshooting Starting, Stopping, and Restarting of the Directory Server Troubleshooting Oracle Internet Directory Replication Troubleshooting SSL Setup Troubleshooting Change Log Garbage Collection Troubleshooting Dynamic Password Verifiers Troubleshooting Oracle Internet Directory Password Wallets Troubleshooting bulkload J.1.1 Installation Errors During installation and configuration of the Oracle Database, Oracle recommends that you select the character set UTF-8 to avoid possible problems with multibyte characters. J.1.2 TCP/IP Problems TCP/IP bugs in the operating system can interfere with Oracle Internet Directory service. J.1.2.1 Do Not Use TCP-Based Monitoring of Oracle Internet Directory Server Availability on Microsoft Windows 2003 Server If you use the F5 load balancer for monitoring Oracle Internet Directory server availability, configure the load balancer to use LDAP- or HTTP-based monitoring, as described in the Oracle Application Server High Availability Guide section "Configuring A Load Balancer For OracleAS Cluster (Identity Management)." Using TCP-based monitoring might cause the service to become unavailable, due to an operating system bug on Windows 2003 Server. J.1.2.2 Do Not Install DaimondCS Port Explorer Oracle Internet Directory will not work if DaimondCS Port Explorer is installed on the system. J.1.3 Directory Server Error Messages and Causes This section contains a list of all the Oracle directory server error messages that you can encounter. Each message is followed by its most probable causes. J.1.3.1 Oracle Database Server Error Due to Schema Modifications You get error ORA-1562 Problem If you attempt to add more schema
API How LDAP Operations Map to JNDI APIs How LDAP Error Codes Map to JNDI Exceptions Security Modes of Authenticating to LDAP Authentication Mechanisms Anonymous Simple SASL Digest-MD5 SSL and Custom Sockets More LDAP Operations LDAP Compare Search Results LDAP Unsolicited Notifications Connection Management Creation Closing Pooling Configuration Frequently Asked Questions Trail: Java Naming and Directory Interface Lesson: Advanced Topics for LDAP Users Section: JNDI as an LDAP API Home Page > Java Naming and Directory Interface > Advanced Topics for LDAP Users «Previous•Trail•Next» http://docs.oracle.com/cd/B14099_19/idmanage.1012/b14082/trblsht.htm How LDAP Error Codes Map to JNDI Exceptions The LDAP defines a set of status codes that are returned with LDAP responses sent by the LDAP server (see RFC 2251). In the JNDI, error conditions are indicated as checked exceptions that are subclasses of NamingException. See the Naming Exceptions section for an overview of the JNDI exception classes. The LDAP service http://docs.oracle.com/javase/tutorial/jndi/ldap/exceptions.html provider translates the LDAP status code it receives from the LDAP server to the appropriate subclass of NamingException. The following table shows the mapping between LDAP status codes and JNDI exceptions. LDAP Status Code Meaning Exception or Action 0 Success Report success. 1 Operations error NamingException 2 Protocol error CommunicationException 3 Time limit exceeded. TimeLimitExceededException 4 Size limit exceeded. SizeLimitExceededException 5 Compared false. Used by DirContext.search(). Does not generate an exception. 6 Compared true. Used by DirContext.search(). Does not generate an exception. 7 Authentication method not supported. AuthenticationNotSupportedException 8 Strong authentication required. AuthenticationNotSupportedException 9 Partial results being returned. If the environment property "java.naming.referral" is set to "ignore" or the contents of the error do not contain a referral, throw a PartialResultException. Otherwise, use contents to build a referral. 10 Referral encountered. If the environment property "java.naming.referral" is set to "ignore", then ignore. If the property is set to "throw", throw ReferralException. If the property is set to "follow", then the LDAP provider processes the referral. If the "java.naming.ldap.referral.limit" property has been exceeded, throw LimitExceededException. 11 Administrative limit exceeded. LimitExceed
CommunityOracle User Group CommunityTopliners CommunityOTN Speaker BureauJava CommunityError: You don't have JavaScript https://community.oracle.com/thread/2015615 enabled. This tool uses JavaScript and https://docs.oracle.com/cd/E10773_01/doc/oim.1014/e10528/trouble_int.htm much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter a title. You can not post oracle error a blank message. Please type your message and try again. More discussions in Oracle Unified Directory (OUD) & Oracle Directory Server Enterprise Edition/Sun DSEE All PlacesFusion MiddlewareIdentity ManagementOracle Unified Directory (OUD) & Oracle Directory oracle error code Server Enterprise Edition/Sun DSEE This discussion is archived 1 Reply Latest reply on Mar 7, 2006 4:15 AM by 807573 LDAP: error code 49 - 80090308 807573 Mar 6, 2006 6:45 PM I recently saw my log files as we were experiencing slowness in our application and found the follwoing error message : javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C09030B, comment: AcceptSecurityContext error, data 52e, v893]; remaining name 'dc=hess,dc=pri,dc=com' at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:2988) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2934) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2735) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2649) at com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2549) at com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2523) at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1904) at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1809) at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1734) at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:368) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:328) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:313) at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:238) at com.retek.
common problems that you might encounter when using the Oracle Directory Integration Platform and explains how to solve them. It contains these topics: Troubleshooting Oracle Directory Integration Platform Problems Problems and Solutions Troubleshooting Provisioning Troubleshooting Synchronization Troubleshooting Integration with Microsoft Active Directory Need More Help? See Also: Oracle by Example for Oracle Identity Management, available from the Oracle Technology Network at http://www.oracle.com/technology/index.html Oracle Identity Management User Reference Troubleshooting Oracle Directory Integration Platform Problems This section includes general approaches for diagnosing problems with the Oracle directory integration server. It contains these topics: Diagnosing the Oracle Directory Integration Platform in an Infrastructure Installation Diagnosing the Oracle Directory Integration Platform in an Oracle Directory Integration Platform Installation Troubleshooting Utilities Diagnosing the Oracle Directory Integration Platform in an Infrastructure Installation After you start the Oracle directory integration server, you can verify that it is running by following these steps: On UNIX/Linux, use the following command to verify that the odisrv process is running: ps -ef | grep odisrv For Windows operating systems, obtain the value of the process ID (PID) for the odisrv process from $ORACLE_HOME/ldap/log/oidmon.log. Then, start Task Manager and click the Processes tab to verify that the process is running. If the Oracle directory integration server is not running, then examine the $ORACLE_HOME/ldap/log/oidmon.log file to determine the reason why the server did not start. If the log file shows any database related errors: Verify that a value is set for ORACLE_