ORA-31410: change set string is not an existing change set
Cause: Could not find an existing change set by this name.
Action: Check the spelling of the change set name. Call the procedure again, passing the correct change set name.

This query shows all invalid objects in the Oracle database:

SELECT owner, object_name, object_type, STATUS
FROM dba_objects WHERE STATUS=’INVALID’ ORDER BY owner DESC;

Next is a metaquery that generates all statements to recompile invalid objects:

SELECT ‘ALTER ‘||decode(owner,’PUBLIC’,'PUBLIC’)||’ ‘||
decode(object_type,’PACKAGE BODY’,'PACKAGE’,'TYPE BODY’,'TYPE’,object_type)||’ ‘||
decode(owner,’PUBLIC’,NULL,owner||’.')||’”‘||object_name||’” COMPILE ‘||
decode(object_type,’PACKAGE BODY’,'BODY;’,'TYPE BODY’,'BODY;’,';’)
FROM dba_objects WHERE STATUS=’INVALID’ ORDER BY owner DESC;

ORA-31220: DBMS_LDAP: PL/SQL – Invalid LDAP SSL wallet location.
Cause: There has been an error in the DBMS_LDAP operation.
Action: Please check the LDAP sslwrl value that you use for LDAP operation, or report the error number and description to Oracle Support.

ORA-31225: DBMS_LDAP: invalid BER_ELEMENT
Cause: An attempt was made by a PL/SQL module to use a BER_ELEMENT which is not valid and might have already been freed.
Action: Check the BER_ELEMENT in PL/SQL module involving DBMS_LDAP.

ORA-31230: DBMS_LDAP: unable to dynamically allocate additional memory
Cause: An error occured during dynamic memory allocation from session heap.
Action: Verify that adequate memory resources are available.

ORA-31401: change source string is not an existing change source
Cause: The caller did not use the name of an existing change source. The name given does not match the name of any existing change source.
Action: Check the spelling of the change source name. Choose an existing change source.