03-08-2010 03:16 AM
Hi,
I use LMS2.5 & RME 4.0.4.
From 3 month ago the cwcli job that exports inventory to xml files takes too long (about 3 minutes for 1 export).
For example I did this command below,
cwcli export inventory -device AAA -f "C:\temp\AAA.xml" -l AAA.log
this was the AAA.log
[ lun mar 08 10:24:26 CET 2010 ],INFO ,[main],com.cisco.nm.rmeng.util.db.DatabaseConnectionPool,getConnection,59,Inside ICSDatabaseConnection, MAX_COUNT =20
[ lun mar 08 10:24:26 CET 2010 ],INFO ,[main],com.cisco.nm.rmeng.util.db.DatabaseConnectionPool,getConnection,59,Inside ICSDatabaseConnection, MAX_COUNT =20
[ lun mar 08 10:24:26 CET 2010 ],INFO ,[main],com.cisco.nm.rmeng.util.db.DatabaseConnectionPool,getConnection,59,Inside ICSDatabaseConnection, MAX_COUNT =20
[ lun mar 08 10:24:26 CET 2010 ],INFO ,[main],com.cisco.nm.rmeng.util.db.DatabaseConnectionPool,getConnection,59,Inside ICSDatabaseConnection, MAX_COUNT =20
[ lun mar 08 10:24:26 CET 2010 ],INFO ,[main],com.cisco.nm.rmeng.util.db.DatabaseConnectionPool,getConnection,59,Inside ICSDatabaseConnection, MAX_COUNT =20
[ lun mar 08 10:24:26 CET 2010 ],INFO ,[main],com.cisco.nm.rmeng.util.db.DatabaseConnectionPool,getConnection,59,Inside ICSDatabaseConnection, MAX_COUNT =20
[ lun mar 08 10:24:26 CET 2010 ],INFO ,[main],com.cisco.nm.rmeng.util.db.DatabaseConnectionPool,getConnection,59,Inside ICSDatabaseConnection, MAX_COUNT =20
[ lun mar 08 10:24:26 CET 2010 ],INFO ,[main],com.cisco.nm.rmeng.util.db.DatabaseConnectionPool,getConnection,59,Inside ICSDatabaseConnection, MAX_COUNT =20
[ lun mar 08 10:27:36 CET 2010 ],INFO ,[main],com.cisco.nm.rmeng.cli.export_inventory$1,info,123,
Took 3782 ms (3 sec) with hop 1
[ lun mar 08 10:27:36 CET 2010 ],INFO ,[main],com.cisco.nm.rmeng.cli.export_inventory$1,info,123,
Took 3782 ms (3 sec) with hop 1
[ lun mar 08 10:27:36 CET 2010 ],INFO ,[main],com.cisco.nm.rmeng.cli.export_inventory$1,info,123,
Took 3782 ms (3 sec) with hop 1
[ lun mar 08 10:27:36 CET 2010 ],INFO ,[main],com.cisco.nm.rmeng.cli.export_inventory$1,info,123,
Took 3782 ms (3 sec) with hop 1
[ lun mar 08 10:27:36 CET 2010 ],INFO ,[main],com.cisco.nm.rmeng.cli.export_inventory$1,info,123,
Took 3782 ms (3 sec) with hop 1
[ lun mar 08 10:27:36 CET 2010 ],INFO ,[main],com.cisco.nm.rmeng.cli.export_inventory$1,info,123,
Took 3782 ms (3 sec) with hop 1
[ lun mar 08 10:27:36 CET 2010 ],INFO ,[main],com.cisco.nm.rmeng.cli.export_inventory$1,info,123,
Took 3782 ms (3 sec) with hop 1
[ lun mar 08 10:27:36 CET 2010 ],INFO ,[main],com.cisco.nm.rmeng.cli.export_inventory$1,info,123,
Took 3782 ms (3 sec) with hop 1
[ lun mar 08 10:27:36 CET 2010 ],INFO ,[main],com.cisco.nm.rmeng.cli.export_inventory$1,info,123,
Took 3782 ms (3 sec) with hop 1
The export job creats an xml-file correctly but it takes too long.
I have no idea what I can do to fix this problem. help
03-08-2010 11:12 AM
You are using a very old version of RME. LMS 2.5 and 2.5.1 will be end of support this June. You really need to upgrade to at least LMS 2.6.
The problem you are seeing is CSCse14096 which is fixed in LMS 2.6 (RME 4.0.5).
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide