| Grid Control metric collection error [message #400692] |
Wed, 29 April 2009 05:20  |
rsreddy28
Messages: 295
Registered: May 2007
|
Senior Member |
|
|
Hello,
Of late we were getting frequent errors of the dbsnmp account getting locked daily and as a result the database is not getting monitored on the grid. What we used to do is unlock the dbsnmp user so that again the target database is available for monitoring in the grid. So as per the Metalink : 352585.1 , we followed but we ended up with a a lot of errors as below from the agent trace file :
2009-04-29 02:51:25 Thread-4066368416 ERROR fetchlets.sql: Missing DB user name
2009-04-29 02:51:25 Thread-4066368416 ERROR engine: [oracle_database,EPICMSP_EPICMSP2,secureOSAuditLevel] : nmeegd_GetMetricData failed : Missing DB user name
2009-04-29 02:51:25 Thread-4066368416 WARN collector: <nmecmc.c> Error exit. Error message: Missing DB user name
2009-04-29 02:51:25 Thread-4072668064 WARN collector: Metric{oracle_database:EPICMSP_EPICMSP2:health_check:health_check} Evaluation completed at 19 seconds,
collection interval = 15
2009-04-29 02:51:25 Thread-4084161440 ERROR fetchlets.oslinetok: Process stderr = ORA-01017: invalid username/password; logon denied (DBD ERROR: OCISessionBegin)
2009-04-29 02:51:25 Thread-4084161440 ERROR engine: [oracle_database,EPICMSP_EPICMSP2,Response] : nmeegd_GetMetricData failed : ORA-01017: invalid username/p
assword; logon denied (DBD ERROR: OCISessionBegin)
2009-04-29 02:51:25 Thread-4084161440 WARN collector: <nmecmc.c> Error exit. Error message: ORA-01017: invalid username/password; logon denied (DBD ERROR: O
CISessionBegin)
2009-04-29 02:51:25 Thread-4072668064 DEBUG TargetManager: nmeetm.c : nmeetm_saveTarget : Removing target Address 0x82369f0
2009-04-29 02:51:25 Thread-4072668064 ERROR TargetManager: Skipping target {EPICMSP, rac_database}: Missing properties - ClusterName
2009-04-29 02:51:25 Thread-4072668064 INFO TargetManager: save to targets.xml success
2009-04-29 02:51:25 Thread-4072668064 INFO TargetManager: nmeetm.c : nmeetm_signalReloadMgrOnTgtChange : Category change for target type rac_database, name
EPICMSP
2009-04-29 02:51:25 Thread-4072668064 INFO TargetManager: nmeetm_setDynPropReComputeParam: Values have been retrieved dynamicPropReComputeInterval = 120 dyn
amicPropReComputeMaxTries = 4
2009-04-29 02:51:25 Thread-4072668064 DEBUG TargetManager: No change in metadata/targets.xml/emd.properties: No op reload
2009-04-29 02:51:25 Thread-4072668064 INFO TargetManager: Trying to set the Thread cap based on number of targets
2009-04-29 02:51:25 Thread-4072668064 DEBUG TargetManager: In getTypeAndNameForHostTarget
2009-04-29 02:51:25 Thread-4072668064 DEBUG TargetManager: getTypeAndNameForHostTarget found host, usfldbg1
2009-04-29 02:51:25 Thread-4066368416 ERROR fetchlets.oslinetok: Process stderr = em_error=Could not connect to @(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=us
fldba-vip)(Port=1521))(CONNECT_DATA=(SID=EPICMSP2)))
: ORA-01017: invalid username/password; logon denied (DBD ERROR: OCISessionBegin)
2009-04-29 02:51:25 Thread-4066368416 ERROR engine: [oracle_database,EPICMSP_EPICMSP2,logArchiveDest] : nmeegd_GetMetricData failed : em_error=Could not conn
ect to @(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=usfldba2-vip)(Port=1521))(CONNECT_DATA=(SID=EPICMSP2)))
: ORA-01017: invalid username/password; logon denied (DBD ERROR: OCISessionBegin)
Can somebody help me on this . Now we got an notification email which has message as below
Metric evaluation error start - Target is in broken state. Reason - Missing Properties,Get dynamic property error
Kindly help me out .
Regards,
Raj
|
|
|
|
|
|
| Re: Grid Control metric collection error [message #400701 is a reply to message #400696] |
Wed, 29 April 2009 05:40  |
rsreddy28
Messages: 295
Registered: May 2007
|
Senior Member |
|
|
Hi ,
The thing is we have databases on grid control getting monitored . of late automatically the database is showing as down from the grid but the database is up. so what we used to do is unlock the dbsnmp account and then the datbase is up from the grid, so what happens is again we keep getting notofications from the OEM .
to avoid this daily account getting locked automatically and we unlocking it , we followed as per the Metalink id: 352585.1.
But we ended with lots of errors.
Hope its little clear now.
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
