Oracle Enterprise Manager Jobs Failing Initialization

oracleoracle-rac

The Enterprise Manager jobs on our RAC system recently started intermittently failing initialization with the following error:

Error evaluating parameter sources/security checks/locks ORA-06508:
PL/SQL: could not find program unit being called

We have tried bouncing DBConsole, re-submitting the job from the library and even recompiling the package being referenced. This is happening to multiple jobs with about one execution in every ten scheduled succeeding. Any ideas on what can be tried or checked?

Update: I've opened a SR with Oracle.

Best Answer

Oracle support has been no help. After about a week of the jobs sometimes running they stopped running completely. Every single job got an initialization error every time it ran and every time it was retried. We are in the process of re-creating the repository and migrating to dbms_scheduler jobs.

Related Solutions

Oracle Enterprise Manager (OEM) locking SYSMAN account

Benoit, you actually had a partial answer, everything you said was correct, but after next reboot, the account locked. After several hours of more research, the following issue was discovered, with the appropriate resolution.

Enterprise Manager had the default SYSMAN password stored for its credentials, and was trying to lock in with that password in rapid succession (300 times a minute or so according to the Event Log). Hence, after several rapid tries with the same wrong password, Oracle locks the account.

Setting a new password in SQL*PLUS or SQL Developer doesn't reset the password used to login to Enterprise Manager, to reset the password in enterprise manager, you need to open a command prompt and do the following:

emctl config oms sso -remove
emctl stop oms
emctl start oms

During the above commands, it'll prompt you for the current SYSMAN password, which you can enter, and it should remove the SYSMAN password used by your Enterprise Manager Console, replacing it with the one you just entered.

Oracle Enterprise Manager Installation

Why do you use the -cluster - option ?
Is you database repository part of a cluster ?

Make sure first that you can connect to the database using the tns names.

Example :

sqlplus system/password@'tns_identified'

Then to deconfig you em repo :
Try using this syntax :

 emca -deconfig dbcontrol db -repos drop -SYS_PWD oracle -SYSMAN_PWD oracle

For some nice articles on how you can prepare you Oracle Enterprise Grid Control Monitoring environment check the link

Best Answer

Related Solutions

Oracle Enterprise Manager (OEM) locking SYSMAN account

Oracle Enterprise Manager Installation

Related Question