重庆思庄Oracle、KingBase、PostgreSQL、Redhat认证学习论坛

 找回密码
 注册

QQ登录

只需一步,快速开始

搜索
查看: 289|回复: 0
打印 上一主题 下一主题

[参考文档] APEX Upgrade Failed While Creating JOBS, ORA-20001: FAILED Existence check fo...

[复制链接]
跳转到指定楼层
楼主
发表于 2025-11-2 18:50:35 | 只看该作者 回帖奖励 |倒序浏览 |阅读模式
现象:
On : APEX19.2 version or higher up to 23.2, Admin

A new install or upgrade failed at the end while creating/checking the jobs


Oracle Application Express in dba_registry shows
19.2.0.00.18 INVALID

ERROR
-----------------------
ORA-20001: FAILED Existence check for APEX_190200.ORACLE_APEX_WS_NOTIFICATIONS
ORA-20001: FAILED Existence check for APEX_190200.ORACLE_APEX_MAIL_QUEUE
ORA-20001: FAILED Existence check for APEX_190200.ORACLE_APEX_PURGE_SESSIONS
ORA-20001: FAILED Existence check for APEX_190200.ORACLE_APEX_DAILY_MAINTENANCE
...(12:09:16) Setting DBMS registry for APEX to INVALID
...(12:09:17) Exiting validate_apex




STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Install APEX running the apexins.sql script (with or without a previous APEX version)
2. When the install failed check the logs



改动:
Installing or Upgrading APEX

原因:
There are at least 2 potential causes:

A) DBA have set  job_queue_processes to 0 (zero)

Or

B) There are missing packages or privileges

If the install<date-time>.log is showing:

# Error: ORA-27476: "SYS"."DEFAULT_JOB_CLASS" does not exist  <<<<<<<<<<# Statement: begin
  sys.dbms_scheduler.create_job
...
ORA-06512: at "SYS.DBMS_ISCHED", line 146
ORA-06512: at "SYS.DBMS_SCHEDULER", line 288
ORA-06512: at line 2
ORA-06512: at "SYS.DBMS_SQL", line 1707
ORA-06512: at "APEX_190200.WWV_FLOW_UPGRADE", line 1075
...

(<time>) Key object existence check
ORA-20001: FAILED Existence check for APEX_190200.ORACLE_APEX_WS_NOTIFICATIONS
ORA-20001: FAILED Existence check for APEX_190200.ORACLE_APEX_MAIL_QUEUE
ORA-20001: FAILED Existence check for APEX_190200.ORACLE_APEX_PURGE_SESSIONS
ORA-20001: FAILED Existence check for APEX_190200.ORACLE_APEX_DAILY_MAINTENANCE
...(<time>) Setting DBMS registry for APEX to INVALID

处理方法:
A) Before the installation make sure that job_queue_processes is at least to the maximum number of concurrently running jobs

Or

B) After the failed installation do the following:

- Connect in sql*plus to the DB where APEX was installed as SYS and do:

SQL> grant EXECUTE ANY CLASS to APEX_190200;                     
SQL>  begin sys.validate_apex; end;
-- Confirm the Jobs are created and enabled now

SQL> select JOB_NAME,STATE,ENABLED  from dba_scheduler_jobs where owner = 'APEX_190200'

JOB_NAME                       STATE           ENABLED
------------------------------ --------------- -------
ORACLE_APEX_AUTO_APPROVAL      DISABLED        FALSE
ORACLE_APEX_DAILY_MAINTENANCE  SCHEDULED       TRUE
ORACLE_APEX_DICTIONARY_CACHE   SCHEDULED       TRUE
ORACLE_APEX_ISSUE_EMAILS       SCHEDULED       TRUE
ORACLE_APEX_MAIL_QUEUE         SCHEDULED       TRUE
ORACLE_APEX_PURGE_SESSIONS     SCHEDULED       TRUE
ORACLE_APEX_WS_NOTIFICATIONS   SCHEDULED       TRUE

-- you can also see that apex is valid in dba_registry

分享到:  QQ好友和群QQ好友和群 QQ空间QQ空间 腾讯微博腾讯微博 腾讯朋友腾讯朋友
收藏收藏 支持支持 反对反对
回复

使用道具 举报

您需要登录后才可以回帖 登录 | 注册

本版积分规则

QQ|手机版|小黑屋|重庆思庄Oracle、Redhat认证学习论坛 ( 渝ICP备12004239号-4 )

GMT+8, 2026-4-17 20:57 , Processed in 0.220748 second(s), 20 queries .

重庆思庄学习中心论坛-重庆思庄科技有限公司论坛

© 2001-2020

快速回复 返回顶部 返回列表