-
Title
"RAM size could not be parsed from data [/usr/lib/dld.sl: Unresolved symbol: gs_is_ipv6 (code) fr -
Description
Customer is using 5.5.8.547 on HP.UX 11.11 is seeing these errors in agent log .
2011-09-30 09:50:27.621 ECHO <DB_Oracle/5.5.8.547/DB_Oracle/DBO-mtlproh3.mtl.cbc.ca-P9H3-agent> ERROR [DB-agent-LowPriorityPool-293267] com.quest.qsi.fason.oracle.collection.processor.DBORamUnixProcessor - RAM size could not be parsed from data [/usr/lib/dld.sl: Unresolved symbol: gs_is_ipv6 (code) from /usr/sbin/stm/ui/bin/stm] on agent DBO-mtlproh3.mtl.cbc.ca-P9H3
2011-09-30 09:50:27.726 ECHO <DB_Oracle/5.5.8.547/DB_Oracle/DBO-mtlproh3.mtl.cbc.ca-P9H3-agent> ERROR [DB-agent-LowPriorityPool-293267] com.quest.qsi.fason.oracle.collection.processor.DBOInstanceProcessor - Failed to run DBOHostNameRamComplexProcessor processor of DBO_OS_General collection of DBO-mtlproh3.mtl.cbc.ca-P9H3 instance.
java.lang.RuntimeException: Failed to execute collection [DBO_OS_General], See the agent log for more details.
at com.quest.qsi.fason.core.collection.processor.AbstractQueryProcessor.handleError(AbstractQueryProcessor.java:357)
at com.quest.qsi.fason.core.collection.processor.AbstractQueryProcessor.execute(AbstractQueryProcessor.java:250)
at com.quest.qsi.fason.core.collection.processor.ComplexProcessor.execute(ComplexProcessor.java:162)
at com.quest.qsi.fason.core.collection.processor.InstanceProcessor.execute(InstanceProcessor.java:176)
at com.quest.qsi.fason.oracle.collection.processor.DBOInstanceProcessor.execute(DBOInstanceProcessor.java:204)
at com.quest.qsi.fason.oracle.collection.processor.rac.DBOGeneralProcessor.executeInstanceProcessors(DBOGeneralProcessor.java:234)
at com.quest.qsi.fason.oracle.collection.processor.rac.DBOGeneralProcessor.execute(DBOGeneralProcessor.java:206)
at com.quest.qsi.fason.core.collection.AbstractCollection.doRun(AbstractCollection.java:235)
at com.quest.qsi.fason.core.collection.AbstractCollection.run(AbstractCollection.java:278)
at com.quest. -
Resolution
For this particular issue, it looks like this has happened due to the result of upgrading some of the system packages.
You would have to do the following:1. Use SWREMOVE to remove the EMS
2. Reinstall BOTH EMS and STM (STM v66.00)