How Can a Bad Transaction in BTM Cause a BTM Monitor to Report the Error : DEGRADED: Service Running, But Optional Resource Not Working?
Last updated on OCTOBER 01, 2015
Applies to:APM - Application Performance Management - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
In BTM 220.127.116.11.7 the "Condition Alert" mechanism has stopped working. No alerts are being generated.
The "Status" for the BTM monitor process shows "DEGRADED: Service running, but optional resource not working."
The following error was also observed in the log files for the BTM monitor:
time="Thu Aug 06 17:54:06 EDT 2015"
com.amberpoint.util.soa.types.ServiceFaultedException: The transaction uuid:E71996F6-BBA1-11E4-8BE4-F52F9F1C83D0 has a property defined for metric gathering on endpoint uuid:48B4CBC3-A473-11E4-8A08-8DD56ABB7C03 which returned a null value or that was too long. The max key length is 1000. The key value had length 0. Please check the property and make sure it returns the correct value.
What is the remedy for this situation?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms