Flash (Alert)
Abstract
Aggregation issues could start occurring after importing of the corrupted PVU table released on 24.07. The problem will result in some VMmanagers statuses changing to 'Unknown problem' and the errors similar to following ones could be visible in <Tivoli Common Directory>/COD/logs/admin/traces/traceXX.log:
<Trace Level="MIN">
<Time Millis="*************"> date and time</Time>
<Server Format="IP">server's hostname</Server>
<ProductId>COD</ProductId>
<Component>Admin Server</Component>
<ProductInstance></ProductInstance>
<LogText><![CDATA[[LOG]: An error occurred while processing data retrieved by VM Manager https://vmmanager's_uri/sdk. The data coming from this VM manager will be discarded.]]></LogText>
<Source FileName="com.ibm.license.mgmt.core.actions.vmman.collector.MergeVmManagerDataAction" Method="doAction"/>
<Thread>LMTTimerManager3.Alarm Pool : 0</Thread>
<Principal></Principal>
</Trace>
<Trace Level="MIN">
<Time Millis="*************"> date and time</Time>
<Server Format="IP">server's hostname</Server>
<ProductId>COD</ProductId>
<Component>Admin Server</Component>
<ProductInstance></ProductInstance>
<LogText><![CDATA[[ERROR]]]></LogText>
<Source FileName="com.ibm.license.mgmt.core.actions.vmman.collector.MergeVmManagerDataAction" Method="doAction"/>
<Thread>LMTTimerManager3.Alarm Pool : 0</Thread>
<Exception><![CDATA[java.lang.NumberFormatException: null
at java.lang.Integer.parseInt(Integer.java:428)
at java.lang.Integer.parseInt(Integer.java:510)
at com.ibm.license.mgmt.core.actions.vmman.collector.X86ProcessorMatcher$ProcDescriptor.<init>(X86ProcessorMatcher.java:201)
at com.ibm.license.mgmt.core.actions.vmman.collector.X86ProcessorMatcher.initialize(X86ProcessorMatcher.java:115)
at com.ibm.license.mgmt.core.actions.vmman.collector.X86ProcessorMatcher.<init>(X86ProcessorMatcher.java:79)
at com.ibm.license.mgmt.core.actions.vmman.collector.X86ProcessorMatcher.getInstance(X86ProcessorMatcher.java:69)
at com.ibm.license.mgmt.core.actions.vmman.algorithm.MergeHostStrategy.constructProcessorMeasures(MergeHostStrategy.java:384)
at com.ibm.license.mgmt.core.actions.vmman.algorithm.MergeHostStrategy.fillNodeMeasures(MergeHostStrategy.java:289)
at com.ibm.license.mgmt.core.actions.vmman.algorithm.MergeHostStrategy.process(MergeHostStrategy.java:111)
at com.ibm.license.mgmt.core.actions.vmman.algorithm.MergeClusterStrategy.process(MergeClusterStrategy.java:73)
at com.ibm.license.mgmt.core.actions.vmman.algorithm.MergeRootStrategy.process(MergeRootStrategy.java:100)
at com.ibm.license.mgmt.core.actions.vmman.collector.MergeVmManagerDataAction.mergeData(MergeVmManagerDataAction.java:171)
at com.ibm.license.mgmt.core.actions.vmman.collector.MergeVmManagerDataAction.doAction(MergeVmManagerDataAction.java:132)
at com.ibm.license.mgmt.core.actions.AbstractAction.executeNoTransaction(AbstractAction.java:139)
at com.ibm.license.mgmt.admin.periodictasks.scheduler.tasks.VmManagerConnectorTask.doTask(Unknown Source)
at com.ibm.license.mgmt.core.scheduler.AbstractTask.timerExpired(AbstractTask.java:195)
at com.ibm.ws.asynchbeans.timer.TimerImpl.callListenerMethod(TimerImpl.java:298)
at com.ibm.ws.asynchbeans.timer.GenericTimer.run(GenericTimer.java:216)
at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java:264)
at java.security.AccessController.doPrivileged(AccessController.java:224)
at javax.security.auth.Subject.doAs(Subject.java:495)
at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:131)
at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:89)
at com.ibm.ws.asynchbeans.J2EEContext$DoAsProxy.run(J2EEContext.java:335)
at java.security.AccessController.doPrivileged(AccessController.java:251)
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:1146)
at com.ibm.ws.asynchbeans.timer.TimerImpl.runListenerAsCJWork(TimerImpl.java:425)
at com.ibm.ws.asynchbeans.am._Alarm.fireAlarm(_Alarm.java:333)
at com.ibm.ws.asynchbeans.am._Alarm.run(_Alarm.java:230)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
]]></Exception>
<Principal></Principal>
</Trace>
Content
In order to resolve the issue, the incorrect entries that were introduced with importing the corrupted PVU table of 24.07 need to be corrected. As to correct them please complete the following steps:
1. Login to the LMT database (tlma) with tlmsrv user:
db2 connect to tlma user tlmsrv using <password>
(please replace <password> with a valid password for tlmsrv user
2. invoke the following update queries against tlma database you just logged into:
update adm.processor_type set brand_int_value='UltraSparc-T2+', brand_disp_value='UltraSparc-T2+' where brand_int_value = 'UltraSparc T2+'
update adm.processor_type set type_int_value = '-1' where vendor_int_value = 'AMD' and brand_int_value = 'Opteron' and type_int_value is null
3. disconnect from the database:
disconnect current
4. wait until the aggregation process will be run again (usually starts on midnight until you set the start time differently with aggregateUsageTime parameter of setserverconf cli command)
Rate this page:
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.