This discussion is archived
0 Replies Latest reply: May 11, 2012 9:49 AM by 917894 RSS

ha_backup metric is not sync with latest Backup Report(3 days lag!)

917894 Newbie
Currently Being Moderated
Hi Knowledge ones!

I think this is an "All Over the Web" problem already answered for many situations so, what am I missing!?

EM Grid Control : 10.2.0.5.0 ( Solaris 10 )
Oracle instance: 11.2.0.3.0 ( RHEL 5.6 )

Facing the issue presented in the subject, I already ran throught the following:

Test Upload Sequence*
0 - Confirm that the agent was not blocked inside GRID
1- Stop the agent in the affected target;
2 - Clean directories related to sysman upload(*)
3 - Enable upload debug on emd.properties
4 - Start the agent
6 - "Last successful upload" is up to date
5 - Check no errors on emctl.log & emagent.trc (**)
6 - Confirm the correct status in mgmt_ha_backup.dat(***)
7 - Got connection success with "wget --no-check-certificate [REP URL](****)"

Doc ID 849722.1*
Last Backup Information on Database Home Page is Incorrect in Grid Control Console [ID 849722.1]
Although not needed since the base query executed on the target returns correct results

Queries inside Repository and Instance*
SELECT
collection_timestamp
FROM
sysman.MGMT_TARGET_PROPERTIES sid,
sysman.MGMT_HA_BACKUP backup
WHERE
sid.target_guid = backup.TARGET_GUID
and sid.property_name = 'SID'
and sid.property_value= [SID]

+2012-05-08+
          
SELECT     end_time
FROM     (SELECT end_time FROM v$rman_backup_job_details ORDER BY end_time DESC     )
WHERE     rownum = 1;

+2012-05-11+


Any hint would be very appreciated, so ask me for more info!

Thank you in advance,
Rui Rodrigues

(*)
cd $AGENT_HOME/sysman/emd
rm lastupld.xml agntstmp.txt
cd $AGENT_HOME/sysman/emd/upload
rm *.*
cd $AGENT_HOME/sysman/emd/state
rm *.*

(**)
5790 :: Fri May 11 15:58:45 2012::AgentStatus.pm:Processing upload
5790 :: Fri May 11 15:58:45 2012::AgentStatus.pm:emdctl status agent returned 3
5790 :: Fri May 11 15:58:47 2012::AgentStatus.pm: emdctl upload returned with exit code 0


2012-05-11 15:57:32,267 Thread-4060081040 DEBUG upload: Rowset file closed : mgmt_ha_backup.dat, 0
2012-05-11 15:57:32,267 Thread-4060081040 DEBUG upload: file #10 - mgmt_ha_backup.dat: length = 826
2012-05-11 15:57:32,267 Thread-4060081040 DEBUG upload: file #10 - mgmt_ha_backup.dat - has a length of 826
2012-05-11 15:57:32,267 Thread-4060081040 DEBUG upload: nmehum_mergeLFIFiles Opened file mgmt_ha_backup.dat : 0
2012-05-11 15:57:32,267 Thread-4060081040 DEBUG upload: nmehum_mergeLFIFiles close file[9] mgmt_ha_backup.dat, ret = 0
2012-05-11 15:57:32,267 Thread-4060081040 DEBUG upload: nmehum_mergeLFIFiles Closing file D0000012.tmp, ret = 0
2012-05-11 15:57:32,267 Thread-4060081040 DEBUG upload: New XML File created named D0000012.xml. NumXMLFiles = 2, bytesXMLFiles = 14335
2012-05-11 15:57:32,267 Thread-4060081040 INFO upload: Uploading now: total xml files = 2, bytes = 14335
[...]
2012-05-11 15:57:32,532 Thread-4056931216 DEBUG upload: nmehum_uploadOneXMLFile Closed file D0000012.xml, ret = 0
2012-05-11 15:57:32,532 Thread-4056931216 INFO upload: Successfully upload to [REP URL]: D0000012.xml, size = 10643, time(milliseconds) = 61, rate(kilobytes/second) = 170.386142


(***)
<ROWSET OMS_PROTOCOL_VERSION="10.2.0.5.0" TABLE="mgmt_ha_backup">
<ROW>
<TARGET_GUID>C2AEF75D0E19ACCA507A49F4DFF959EC</TARGET_GUID>
<COLLECTION_TIMESTAMP>*2012-05-11 09:43:58*</COLLECTION_TIMESTAMP>
<END_TIME>*2012-05-11 00:12:41*</END_TIME>
<STATUS>COMPLETED</STATUS>
[...]
</ROW>


(****)
Resolving [REP URL].......
Connecting to [REP URL]....... connected.
WARNING: cannot verify [REP URL] certificate, issued by ....................
Self-signed certificate encountered.
HTTP request sent, awaiting response... No data received.
Retrying.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points