ORA-27351: conflicting values of job attributes string and string
Cause: The values of two attributes passed in to the CREATE_JOBS call or the JOB object constructor conflicted with each other. This is usually because both attributes cannot be non-NULL at the same time.
Action: Resolve the conflict by changing the value of one of the attributes and issue the call again.
What does that mean both DESTINATION_NAME and JOB_TYPE can not be non-null at the same time?
The value of JOB_TYPE can not be null obviously.
But, I tried to set DESTINATION_NAME to 'SYS.ORA'. I received an error "ORA-27476: "SYS.ORA" does not exist.
What is your suggestion next? Thanks.
I can see a problem here. You are missing a single quote at the end of job_action.
job_name => 'XYZ'
,job-type => 'PLSQL_BLOCK'
,job_action => 'BEGIN null; END; ###### where is the trailing single quote? #######
,start_date => SYSDATE
,repeat_interval => 'FREQ=DAILY;BYHOUR=4;BYMINUTE=30;BYSECOND=0'
,enabled => FALSE
,credential_name => 'SYSORA'
,destination_name => null
,comments => 'Scheduled job XYZ.');
my real job_action is not like that. I had no problem with job_action and the error message I received was "ORA-27476: "SYS.ORA" does not exist." with destination_name. Any suggestion? Thanks.
What is SYS.ORA?
Why are you using objects from the SYS schema? You shouldn't do using SYS objects at all, and this may be the root cause of the issue.
What is your DB version?
So you're trying to execute this job from your TEST database but pointing to your Production database, is that correct?
If you're just trying to run the job locally on your TEST db, then don't specifiy anything for the credential_name parameter.
It's not at all likely, but is the TEST database on the same host as the production database?
The version of our DB is 11g.
The scheduled jobs were running on our production ORA (ORA is just used for this question) but the jobs were copied onto the TEST DB when the TEST DB was replicated as I said in my question.
I just tried to set those jobs running on our production only not on both production and test.Or, Is there any way I can prevent those jobs from being copied to the TEST DB during the replication.
I will try to create the job without the credential_name to see whether it works. I will let you know.
If you want to run the job on the ORA db while the job resides in the TEST db, you need to create a database destination and specify it for the destination_name parameter. Check the documentation for the process: