Using database link via dbms_scheduler

Question

Hello out there,
I have a problem calling a stored procedure via dbms_scheduler that pulls some rows over a public database link.
The setup is the following:
create public database link mediabase using 'mediabase';
create or replace procedure hole_kurse as
mdatum date;
begin
   select max(datum) into mdatum
   from dt_wechselkurs;
   insert into dt_wechselkurs l
      (waehrung,
       datum,
       wechselkurs)
   (select
       r.waehrung,
       r.datum,
       r.wechselkurs
    from
       dt_wechselkurs@mediabase r
    where
       datum>mdatum);
    commit;
end hole_kurse;
begin
   dbms_scheduler.create_job(job_name          =>  'wechselkurse',
                             job_type          =>  'STORED_PROCEDURE',
                             job_action        =>  'hole_kurse',
                             start_date        =>  sysdate,
                             repeat_interval   =>  'FREQ=DAILY; BYHOUR=7; BYMINUTE=0; BYSECOND=0');
   dbms_scheduler.enable(name => 'wechselkurse');
   commit;
end;
/I can access the database link in SQL and I can call the procedure hole_kurse from SQL without any errors. But the job fails writing "ORA-01017: invalid username/password; logon denied" into alert.log. I also tried using dbms_job which used to work with Oracle 10g but now fails with the same error.
My Oracle version is 11.2.0.2 64bit on Window Server 2008R2.
So what do I have to change that my job will run?
Many thanks in advance,
dhalek

Answer 1

I'm not completely sure, but here is a possibility:
The [url http://docs.oracle.com/cd/E11882_01/server.112/e26088/statements_5005.htm#i2061505]docs have this to say:
>
If you specify CONNECT TO user IDENTIFIED BY password, then the database link connects with the specified user and password.
If you specify CONNECT TO CURRENT_USER, then the database link connects with the user in effect based on the scope in which the link is used.
If you omit both of those clauses, then the database link connects to the remote database as the locally connected user.
>
Your dblink is like this:
create public database link mediabase using 'mediabase';That is the third case described, so the link connects as "the locally connected user", which in the scheduler session is probably not your user.
You may try it with the second case described in the docs:
create public database link mediabase CONNECT TO CURRENT_USER using 'mediabase';If I understand the docs correct, then within the procedure the dblink will use the schema that the procedure is owned by (unless the procedure is using invoker-rights, then it will be the invoking user.)
It is just a guess, but you can try it and see ;-)