Hmmm, I searched this forum and found posts today
9983755
Anyways, I'm not trying to use sql*developer, I just got this message once since installing in August:
Thread 1 advanced to log sequence 227 (LGWR switch)
Current log# 1 seq# 227 mem# 0: D:\ORACLEXE\APP\ORACLE\FAST_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_76Z8WGYF_.LOG
Fri Nov 11 22:00:00 2011
Setting Resource Manager plan SCHEDULER[0x30FB]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Fri Nov 11 22:05:02 2011
Thread 1 advanced to log sequence 228 (LGWR switch)
Current log# 2 seq# 228 mem# 0: D:\ORACLEXE\APP\ORACLE\FAST_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_76Z8WJ0N_.LOG
Setting Resource Manager plan SCHEDULER[0x30FC]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Sat Nov 12 07:34:20 2011
Thread 1 advanced to log sequence 229 (LGWR switch)
Current log# 1 seq# 229 mem# 0: D:\ORACLEXE\APP\ORACLE\FAST_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_76Z8WGYF_.LOG
Sat Nov 12 17:33:17 2011
Thread 1 advanced to log sequence 230 (LGWR switch)
Current log# 2 seq# 230 mem# 0: D:\ORACLEXE\APP\ORACLE\FAST_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_76Z8WJ0N_.LOG
Sat Nov 12 22:00:00 2011
Errors in file D:\ORACLEXE\APP\ORACLE\diag\rdbms\xe\xe\trace\xe_j000_672.trc:
ORA-12012: error on auto execute of job "SYS"."BSLN_MAINTAIN_STATS_JOB"
ORA-06550: line 1, column 807:
PLS-00201: identifier 'DBSNMP.BSLN_INTERNAL' must be declared
ORA-06550: line 1, column 807:
PL/SQL: Statement ignored
Thread 1 advanced to log sequence 231 (LGWR switch)
Current log# 1 seq# 231 mem# 0: D:\ORACLEXE\APP\ORACLE\FAST_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_76Z8WGYF_.LOG
Setting Resource Manager plan SCHEDULER[0x30FD]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Sun Nov 13 12:33:29 2011
Thread 1 advanced to log sequence 232 (LGWR switch)
Current log# 2 seq# 232 mem# 0: D:\ORACLEXE\APP\ORACLE\FAST_RECOVERY_AREA\XE\ONLINELOG\O1_MF_2_76Z8WJ0N_.LOG
Sun Nov 13 22:23:49 2011
Thread 1 advanced to log sequence 233 (LGWR switch)
Current log# 1 seq# 233 mem# 0: D:\ORACLEXE\APP\ORACLE\FAST_RECOVERY_AREA\XE\ONLINELOG\O1_MF_1_76Z8WGYF_.LOG
I've seen MOS 1329618.1 and 1323597.1. Is everyone getting this and just doing the grants, or is there something more worrisome I should be pursuing? I'd think I'd have seen this before...
select * from dba_tab_privs where table_name='DBMS_JOB'; gives no rows. I look at my test xe on my box and I see the expected privs. I don't
think anyone else with access would even know how to revoke privs, although the possibility exists, so I'll ask around, but right now this has the scary feel of privileges disappearing all by themselves. The box has been rebooted a few times due to mysterious lockups, some due to previously having insufficient memory.
The only thing going on in this database/node is a few tables being updated or created 4 dozen times a day, takes a few minutes at most, not at the top of the hour. I haven't locked the table stats because of ongoing development. Looking at the listener log, there doesn't seem to be any of that.
Edit:
Ohhhhh....
SQL> edit
Wrote file afiedt.buf
1 select log_date,status
2 from dba_scheduler_job_run_details
3 where job_name='BSLN_MAINTAIN_STATS_JOB'
4* order by log_date desc
SQL> /
LOG_DATE
---------------------------------------------------------------------------
STATUS
------------------------------
12-NOV-11 10.00.00.723000 PM -07:00
FAILED
05-NOV-11 11.00.00.609000 PM -06:00
FAILED
29-OCT-11 11.00.00.723000 PM -06:00
FAILED
LOG_DATE
---------------------------------------------------------------------------
STATUS
------------------------------
22-OCT-11 11.00.00.401000 PM -06:00
FAILED
15-OCT-11 11.00.01.921000 PM -06:00
FAILED
And I see the same thing on my test box.
So I guess the question is still, why did I only get the Subject: error now, and additionally, should I expect it to not fail?
Edited by: jgarry on Nov 14, 2011 2:58 PM