ORA-31223: DBMS_LDAP: cannot open more than string LDAP
server connections

Answer Posted / guest

Cause: An attempt was made to open more than the maximum
allowed LDAP server connections.

Action: Free unused connections.

Please add more information about this Error

Is This Answer Correct ?    1 Yes 1 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

IMP-00060: Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier

2733


IMG-02003: 2FF03 - incorrect color histogram feature specification

1309


How to resolve QSM-01108 error. I have no OR conditions in my query, but do have 9 IN conditions. The error says the max limit is 2 while I have 257 number of disjuncts. However, if I remove even a single IN condition, the query is rewritten. I cannot change my query. How can I resolve this issue?

2401


IMP-00096: Warning: Skipping table "string"."string" because type synonym "string"."string" cannot be created

1324


ORA-26029: index string.string partition string initially in unusable state

1817






RMAN-05017: no copy of datafile number found to recover

1999


IMP-00070: Lob definitions in dump file are inconsistent with database.

1391


ORA-26032: index string.string loading aborted after string keys

1739


ORA-16516: The current state is invalid for the attempted operation.

8259


ORA-26094: stream format error: input column overflow

2353


ORA-26095: unprocessed stream data exists

3052


In my project I am using star schema and only diimension tables are loaded and not fact tables any one can help me why it is happening? Plase guide me.

2438


ORA-26084: direct path context already finished

1589


NZE-28890: Entrust Login Failed

1488


[ERROR] [main 11:01:20] (JCLLoggerAdapter.java:error:454) Unsuccessful: alter table user.CEN_USER_MASTER add constraint FKF4EDEDC3D0BAAE75 foreign key (ROLE_ID) references user.CEN_ROLE_MASTER [ERROR] [main 11:01:20] (JCLLoggerAdapter.java:error:454) ORA-02275: such a referential constraint already exists in the table

2407