Credentials
To be able run jobs on a remote agent, we have to add the credential_name attribute to the jobs specification. To do this, we must create one first. We can create credentials using DBMS_SCHEDULER.create_credential and remove them with DBMS_SCHEDULER.drop_credential. At the moment, it is not mandatory to use credentials for local external jobs, but Oracle advises us to use them instead of falling back on the (soon to be deprecated) defaults. Using credentials also has documentation benefits. The operating system account that is involved becomes much more obvious, so the advice is to go and start using credentials. I created a normal user jobs, with the password employed, who has to run the jobs.
The attributes for credentials are as follows:
|
Attributes |
Description |
|---|---|
|
username |
The username to execute the job |
|
password |
Password to authenticate the user, which is stored as unreadable |
|
comments |
An optional comment. It can describe what the credential is intended for |
|
database_role... |
