Shulou(Shulou.com)06/01 Report--

In this issue, the editor will bring you about how to use dbms_scheduler.create_job to report ORA-27452/ORA-06512 errors. The article is rich in content and analyzes and narrates it from a professional point of view. I hope you can get something after reading this article.

Today, I received an email from a developer using plsql develop to create a job Times ORA-01031, so I granted the right to create job to the corresponding user, and the error remained the same. Then I asked the developer to send me the corresponding sql, and the sql is as follows:

Begin

Sys.dbms_scheduler.create_job (job_name = > 'DBEC.J_FRESHBASEDATA'

Job_type = > 'STORED_PROCEDURE'

Job_action = > 'playing FreshBaseData'

Start_date = > to_date ('15-07-2013 dd-mm-yyyy hh34:mi:ss')

Repeat_interval = > 'sysdate+ (1Comp1440) * 10'

End_date = >''

Job_class = >''

Enabled = > true

Auto_drop = > false

Comments = >'')

End

The following error is reported after running the above sql:

ERROR at line 1:

ORA-27452: is an invalid name for a database object.

ORA-06512: at "SYS.DBMS_ISCHED", line 99

ORA-06512: at "SYS.DBMS_SCHEDULER", line 262

ORA-06512: at line 2

At first, I removed some special characters by modifying job_name, only to find that the error remains the same. The final problem location is to assign a null value here in job_class, and the solution is to enter the default value, or remove this parameter!

The above is the editor for you to share the use of dbms_scheduler.create_job to report ORA-27452/ORA-06512 errors how to do, if there happen to be similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.