OME - SQL errors in Application log and Incorrect time showing

Hi,

Thanks for your post. Not all errors logged in OME will have an impact on functionality. Many times errors logs are created for additional debugging. Can you elaborate a little more on the issues you have in OME functionality?

Some of the messages above are information logs which state discovery/inventory/status poll operations are overlapping. As you mentioned it can happen if the manual discovery/inventory/status poll collides with the scheduled cycles. It should not have any funtional impact.

Some of the deadlocks reported are generated due to triggers and complex queries. Most of these operations like compliance assessment happen in the background and OME will try those again later if deadlock is reported.

Regarding the incorrect time, can you tell us which page is reporting that?

Regards

Abhijit

Hi Abhijit,

This error it would seem when we perform a discovery and inventory scan on a device or range we are seeing the SQL errors

Inventory Manager Exception; Device: -1271450037 , Exception: An internal database error occurred. : Error executing the SQL Statement:INSERT INTO Firmware (FirmwareVersion,FirmwareType,FirmwareChassisIndex,FirmwareName,DeviceId,FirmwareIndex) VALUES(?,?,?,?,?,?) Error: SQL_ERROR results: SQL Error State: 40001, Native Error Code: 4B5, ODBC Error Text: [Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID 54) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. ODBC_DatabaseConnection::AddTableRow()

And we have had our applications guys check this out and can not see any deadlocks onthe DB.

As this is a primary monitoring system for hardware a quick resolution would be great.

Kind Regard's

Jody

In addition the incorrect time is being reported on the tools > Application Logs > the logs were showing as 1 day and 1 hr ahead of the present time.

at time of posting it was 12:40 on the 18/09/2012 and infact the time was showing 19/09/2012 and 16:00 hrs

Hi Jody,

Look for OME 1.1 in Q4 of 2012 (early rather than later).

Thanks much,

Rob

Hi Abhijit,

When can we expect the new release of OME and what are some of the updated fixes and features.

Regard's

Jody

Hi Jody,

Thanks for the updates. We looked at this reported error and as I mentioned earlier, it should not have an impact on functionality. The insert operation will be retried during the next inventory cycle. This is not a SQL deadlock. It is deadlock between internal processes used in OME as they are sharing the ODBC connectivity. We have updated the algorithm in the upcoming version so that this error will not be seen.

This error will not have any impact on the monitoring functionality and you can keep using OME as primary monitoring tool.

We will also look at the time logged in the logs. It may be related to time conversion routine used in the logging section. We have updated all the routines to use UTC in the coming version and this issue should also be addressed as part of that change.

Regards

Abhijit

Hi Jody,

The only feature that we've been pre-announcing is the OOB system update.  That is the ability to patch a system via the Lifecycle Controller (iDrac).  For the rest, we'll be posting on launch day.  So stay tuned.

Thanks!

Rob