Re: Grid Repository Database Crashed - Job Status shows Stop Pending but not able to Stop or Delete
- From: Kellyn Pot'vin <kellyn.potvin@xxxxxxxxx>
- To: "m.mudhalvan@xxxxxxxxxxxxxxxx" <m.mudhalvan@xxxxxxxxxxxxxxxx>
- Date: Sun, 5 Aug 2012 19:48:51 -0700 (PDT)
After verifying that the job is in the library and correctly stored, you also
can't delete all incidents of the job(s)?
If so- are you able to stop the running incidents of the jobs? You have also
verified that all data has uploaded from the targets, (emctl status agent)?
Thanks,
Kellyn Pot'Vin
Senior Technical Consultant
Enkitec
DBAKevlar.com
Director of Training Days 2013
Enkitec
~Tombez sept fois, se relever huit!
________________________________
From: "m.mudhalvan@xxxxxxxxxxxxxxxx" <m.mudhalvan@xxxxxxxxxxxxxxxx>
To: Kellyn Pot'vin <kellyn.potvin@xxxxxxxxx>
Cc: oracle-l <oracle-l@xxxxxxxxxxxxx>
Sent: Sunday, August 5, 2012 8:36 PM
Subject: Re: Grid Repository Database Crashed - Job Status shows Stop Pending
but not able to Stop or Delete
Hi Kellyn
Thanks for your quick reply.
I am able to see some Jobs are showing status as "Running". When I
check the detailed information about that Job it shows "Stop Pending" and
Message "Waiting for Output".
When I try to stop the job or Delete the Run it is not working.
Even I tried to use EMCLI command but no help.
Thanks & Regards
Mudhalvan M.M
Infrastructure Management Division
----------------------------------------------------------------------------------------------------
From: "Kellyn Pot'vin" <kellyn.potvin@xxxxxxxxx>
To: 1326914 MUDHALVAN.MUNISWAMY/AOZORABANK@AOZORABANK, oracle-l
<oracle-l@xxxxxxxxxxxxx>
Date: 08/06/2012 11:33 AM
Subject: Re: Grid Repository Database Crashed - Job Status shows
Stop Pending but not able to Stop or Delete
I'm assuming this is a 10g EM and that what has occurred, is that when the
jobs ended, the repository was down, so no notice of the completion was
sent to EM from the target.
Now- You should be able to filter the job results by "running", which will
show you the jobs that are still shown as active. You should be able to
then delete each of these jobs that you know to not be by when they
executed and their targets.
Are you saying that you can't find them or that you can't remove them when
you do locate them?
Kellyn Pot'Vin
Senior Technical Consultant
Enkitec
DBAKevlar.com
Director of Training Days 2013
Enkitec
~Tombez sept fois, se relever huit!
From: "m.mudhalvan@xxxxxxxxxxxxxxxx" <m.mudhalvan@xxxxxxxxxxxxxxxx>
To: oracle-l <oracle-l@xxxxxxxxxxxxx>
Sent: Sunday, August 5, 2012 7:19 PM
Subject: Grid Repository Database Crashed - Job Status shows Stop Pending
but not able to Stop or Delete
Dear DBAs
Greetings.
During the week end our production grid repository database
crashed and we recovered it.
It is up and running fine.
But we are able to see many jobs in status running on the day on
which Repository database crashed.
While check the jobs detailed it shows "Stop Pending and Waiting
for Output".
When trying to stop the Job I am getting "The job execution was
stopped successfully. Currently running steps will not be stopped."
When trying to Delete the Job I am getting following error message
and it is deleting the Job
"The specified job, job run or execution is still active.
It must finish running, or be stopped before it can be deleted. Filter on
status 'Active' to see active executions"
I tried with both options
Stop and Delete only this run of job.
Stop and Delete all runs of job
Thanks & Regards
Mudhalvan M.M
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
