Hi

Have been reading almost every thread there is on this subject and also tried proposed solutions but still I'm stuck.

I have a File watcher created, using a Credential, that normally would trigger a job through the event created.
In short this is what we have:

Linux 2.6.18, x86_64 (times 3)
pam links created in lib64
Oracle 11g r2

jssu verifed by manually su from root to Ora-user, then using the file watcher credential (user/pwd) and I get my ls or echo things done (providing wrong pwd give those dummy chars => seems ok)
I also verify in the Linux Audit log that there is an exe='...../jssu' run with res = 'success', this is to me an indication of the Job Schedule SU to Credential works ok (account in the audit log is the name of credential)
I've even tried putting the credential in the wheel group so that credential should have no problem reading the directories/file needed (also verified by su to cred and accessing relevant dirs/files)
Now, the job is never triggered at all (no record in job_log nor job_run_detail tables)
The program (having metadata_argument created) is referring a Stored procedure, and all objects are enabled.

As with the Audit log, I also see traces in Ora trace files (<ORA_INST_NAME__j00X.trc name patterns) right after each time I touch the file in watched directory...
The trace file contains below extract:

Code:
*** 2012-11-14 18:43:54.074
*** SESSION ID:(27.5) 2012-11-14 18:43:54.074
*** CLIENT ID:() 2012-11-14 18:43:54.074
*** SERVICE NAME:(SYS$USERS) 2012-11-14 18:43:54.074
*** MODULE NAME:(DBMS_SCHEDULER) 2012-11-14 18:43:54.074
*** ACTION NAME:(FILE_WATCHER) 2012-11-14 18:43:54.074

FILE_TRANSFER error is:
And nothing more (besides the usual header block of trace files)

Find below scripts used to create Scheduler objects:

Code:
BEGIN
        dbms_scheduler.create_credential('<credential-name>','<CRED-OS-USER>','<credential-password>');
END;

BEGIN
        DBMS_SCHEDULER.create_file_watcher(
                file_watcher_name => 'USER_FILEWATCHER',
                directory_path => '/home/<CRED-OS-USER>/bs/in',
                file_name => '*',
                credential_name => '<credential-name>',
                destination => NULL,
                enabled => FALSE
        );
END;
/

BEGIN
        DBMS_SCHEDULER.create_program(
                program_name => 'USER_NEW_FILE',
                program_type => 'STORED_PROCEDURE',
                program_action => 'user_l_load.new_file',
                number_of_arguments => 1,
                enabled => FALSE
        );
END;
/

BEGIN
        DBMS_SCHEDULER.define_metadata_argument(
                program_name => 'USER_NEW_FILE',
                metadata_attribute => 'event_message',
                argument_position => 1
        );
END;
/

BEGIN
        DBMS_SCHEDULER.create_job(
                job_name => 'USER_FILE_JOB',
                program_name => 'USER_NEW_FILE',
                event_condition => 'tab.user_data.file_size > 0',
                queue_spec => 'USER_FILEWATCHER',
                auto_drop => FALSE,
                enabled => FALSE
        );
END;
/

BEGIN
    dbms_scheduler.ENABLE('USER_FILEWATCHER');
    dbms_scheduler.ENABLE('USER_NEW_FILE');
    dbms_scheduler.ENABLE('USER_FILE_JOB');
END;
/

Right now, I'm out of ideas on how to test/verify more...
Anhyone have a clue on what might casue this?

/R