Orphan job during the plugin deploy

Question

Hi,
I was deploying a plugin on our em system and the plugin deployment failed. Due to experience with a plugin deployment failure before, I knew that I would have to restore. I had taken a backup of the OMS servers by creating a tar file of the entire directory structure for the Home. I copied that back over to restore the oms servers. I also then restored the repository back to about the same time. I followed the steps documented for recovering EM after a failure and everything came back up successfully. However, when I now try to deploy a plugin, I get the error message that there is already a plugin deployment running.
When I check deployment activities, I don’t see any deployment activities at all.
I looked at the job activities and did not find any. I then ran the db query and found this:
SQL> select deployment_id, deploy_progress_on, lock_date_utc from em_plugin_lock_track where deployment_id > 0 and deploy_progress_on='OMS';
DEPLOYMENT_ID DEPLOY_P LOCK_DATE
46 OMS 06-APR-13
How to fix this?
Thanks

Answer 1

Hi,
The earlier deployment was not got initiated, but the reference id was created, which was blocking the current deployment.
You can verify the issue from the following:
1. Login in to cloud control
Setup --> Extensibility --> Plugi-ns
Click on Actions --> Deployment Activities
2. Verify if No jobs created using that Deployment ID
Go to Enterprise -> Jobs -> Activity
and search for '%Plugin%'
see if any job turns up with id "ID" marked in the job name
3. Verify the command output:
$ emcli get_plugin_deployment_status -deployment_ID=<ID>
This will not return any rows.
4. But reference of this Deployment ID exists in the tables:
SQL> SELECT deployment_id,deploy_progress_on tier,lock_date_utc started_utc FROM em_plugin_lock_track l WHERE deployment_id>0 AND deploy_progress_on='OMS';
5. Running EMDIAG will list the following in Plugin Module:
verifyPLUGINS
7001. Orphan plugin deploy
Confirm the above and that would give more explanation and narrow the issue down.
Regards,
Venkat