Crashing Metadata Repository?

Question

Hi,
Realize this may be more suited for the General Database forum, but since it involves the OID metadata repository and the DBMS_LDAP APIs, thought I would try this board first.
I am trying to load 1400+ users into Oracle Internet Directory from an existing database.
I have written a small PL/SQL procedure that queries the database for the users info and then loads it into OID using the DBMS_LDAP APIs. I am using SQL*Developer to write and debug the procedure.
The procedure loads 1131 users, but then halts, returning a "No more data to read from socket" error. All users before this point are loaded correctly into OID.
Running this procedure from SQL*Plus results in a "ORA-03113: end-of-file on communication channel"
Researching the OTN and MetaLink forums leads me to believe that either the source database or the OID metadata repostitory is crashing, causing the connection to be lost. Perhaps this is a memory issue. . .?
I checked the logs for both the source database and the OID metadata repository - I can't find anything related to this problem (i.e. messages occuring at the same time I run the procedure.)
Can anyone give me any hints on how to troubleshoot this problem?
TIA
Jim
Here's the procedure. . .
CREATE OR REPLACE
PROCEDURE upload_users_oid AS
GN$Errcode NUMBER ;
GC$ErrLib VARCHAR2(2000) ;
GC$ldap_host VARCHAR2(256) := 'something.com'; -- your LDAP Host url
GC$ldap_port VARCHAR2(256) := '389'; -- your LDAP Port
GC$ldap_user VARCHAR2(256) := 'cn=orcladmin';
GC$ldap_passwd VARCHAR2(256) := 'somepassword';
GC$ldap_base VARCHAR2(256) := 'cn=users,dc=something,dc=com';
my_session DBMS_LDAP.SESSION;
emp_dn VARCHAR2(256);
emp_array DBMS_LDAP.MOD_ARRAY;
emp_vals DBMS_LDAP.STRING_COLLECTION;
cursor user_cur is
select username, lname, fname from usertable
where username IS NOT NULL AND status = 'A';
retval PLS_INTEGER;
user_username varchar2(30);
user_lname varchar2(32);
user_fname varchar2(32);
user_passwd varchar2(12);
BEGIN
retval := -1;
user_passwd := 'Passwd01';
open user_cur;
DBMS_OUTPUT.ENABLE(1000000);
DBMS_LDAP.USE_EXCEPTION := TRUE;
my_session := DBMS_LDAP.init(GC$ldap_host,GC$ldap_port);
retval := DBMS_LDAP.simple_bind_s(my_session, GC$ldap_user,GC$ldap_passwd);
LOOP
emp_array := DBMS_LDAP.create_mod_array(6);
FETCH user_cur into user_username, user_lname, user_fname;
EXIT WHEN user_cur%NOTFOUND;
emp_vals(1) := user_username;
DBMS_LDAP.populate_mod_array(emp_array,DBMS_LDAP.MOD_ADD, 'uid',emp_vals);
DBMS_LDAP.populate_mod_array(emp_array,DBMS_LDAP.MOD_ADD, 'cn',emp_vals);
emp_vals(1) := user_lname;
DBMS_LDAP.populate_mod_array(emp_array,DBMS_LDAP.MOD_ADD, 'sn',emp_vals);
emp_vals(1) := user_fname;
DBMS_LDAP.populate_mod_array(emp_array,DBMS_LDAP.MOD_ADD, 'givenname',emp_vals);
emp_vals.delete;
emp_vals(1) := user_passwd;
DBMS_LDAP.populate_mod_array(emp_array,DBMS_LDAP.MOD_ADD, 'userpassword',emp_vals);
emp_vals(1) := 'top';
emp_vals(2) := 'person';
emp_vals(3) := 'organizationalPerson';
emp_vals(4) := 'inetOrgPerson';
emp_vals(5) := 'orcluser';
emp_vals(6) := 'orcluserv2';
DBMS_LDAP.populate_mod_array(emp_array,DBMS_LDAP.MOD_ADD, 'objectclass',emp_vals);
emp_dn := 'cn=' || user_username || ', ' || GC$ldap_base;
DBMS_OUTPUT.PUT_LINE(RPAD('Adding Entry for DN ',25,' ') ||': [' || emp_dn || ']');
retval := DBMS_LDAP.add_s(my_session,emp_dn,emp_array);
DBMS_LDAP.free_mod_array(emp_array);
emp_vals.delete;
END LOOP;
Close user_cur;
retval := DBMS_LDAP.unbind_s(my_session);
EXCEPTION
WHEN OTHERS THEN
raise_application_error(-20001,'An error was encountered - '||SQLCODE||' -ERROR- '||SQLERRM);
END;

Answer 1

Because your stored procedure executes on the source database, I would look there thoroughly first.
Have you checked with your DBA for any resource limits on the userid that owns the session. Limits can be expressed in a number of ways, typically are defined in a user profile and can definitely manifest themselves as unexpected aborts out of nowhere for long running processes.
Of course a DBA can manually whack it, as well.
regards,
tt