(imported topic written by Steve91)
Hi Chaps
We have an issue with filldb and the files being written to the database.
The DB Admin has done a little investigation and can’t see any particular problems.
The FillDB log has the following recent entries:
Mon, 27 Oct 2008 16:24:53 +0000 – FillDB version 7.0.7.96 starting…
Mon, 27 Oct 2008 16:49:31 +0000 – Encountered error during action results update: Database Error:
Microsoft
ODBC SQL Server Driver
SQL Server
There is insufficient system memory to run this query. (37000:701) (RESULTS LOST)
Mon, 27 Oct 2008 16:49:33 +0000 – Unexpected exception: Database Error:
Microsoft
ODBC SQL Server Driver
SQL Server
There is insufficient system memory to run this query. (37000:701)
Mon, 27 Oct 2008 16:49:33 +0000 – FillDB version 7.0.7.96 starting…
Mon, 27 Oct 2008 16:53:46 +0000 – Unexpected exception encountered parsing file D:\Program Files\BigFix Enterprise\BES Server\FillDBData\BufferDir\000000000000CB49; discarding: Database Error:
Microsoft
ODBC SQL Server Driver
TCP/IP Sockets
ConnectionRead (recv()).
Mon, 27 Oct 2008 16:53:46 +0000 – Unable to connect to database: Database Error:
Microsoft
ODBC SQL Server Driver
Communication link failure
Mon, 27 Oct 2008 17:00:30 +0000 – FillDB version 7.0.7.96 starting…
Mon, 27 Oct 2008 17:00:44 +0000 – Unable to connect to database: Database Error:
Microsoft
ODBC SQL Server Driver
SQL Server
Cannot open database “BFEnterprise” requested by the login. The login failed.
Mon, 27 Oct 2008 17:04:34 +0000 – FillDB version 7.0.7.96 starting…
Mon, 27 Oct 2008 17:32:33 +0000 – Encountered error during action results update: Database Error:
Microsoft
ODBC SQL Server Driver
SQL Server
There is insufficient system memory to run this query. (37000:701) (RESULTS LOST)
Mon, 27 Oct 2008 17:32:35 +0000 – Unexpected exception: Database Error:
Microsoft
ODBC SQL Server Driver
SQL Server
There is insufficient system memory to run this query. (37000:701)
Mon, 27 Oct 2008 17:49:44 +0000 – Encountered error during action results update: Database Error:
Microsoft
ODBC SQL Server Driver
SQL Server
There is insufficient system memory to run this query. (37000:701) (RESULTS LOST)
Mon, 27 Oct 2008 17:49:44 +0000 – Unexpected exception: Database Error:
Microsoft
ODBC SQL Server Driver
SQL Server
There is insufficient system memory to run this query. (37000:701)
Mon, 27 Oct 2008 18:13:33 +0000 – Encountered error during action results update: Database Error:
Microsoft
ODBC SQL Server Driver
TCP/IP Sockets
ConnectionWrite (send()). (RESULTS LOST)
Mon, 27 Oct 2008 18:13:33 +0000 – Unable to connect to database: Database Error:
Microsoft
ODBC SQL Server Driver
TCP/IP Sockets
ConnectionWrite (send()).
Mon, 27 Oct 2008 18:32:45 +0000 – Encountered error during action results update: Database Error:
Microsoft
ODBC SQL Server Driver
TCP/IP Sockets
ConnectionWrite (send()). (RESULTS LOST)
Mon, 27 Oct 2008 18:32:45 +0000 – Unable to connect to database: Database Error:
Microsoft
ODBC SQL Server Driver
TCP/IP Sockets
ConnectionWrite (send()).
Mon, 27 Oct 2008 18:52:09 +0000 – Encountered error during action results update: Database Error:
Microsoft
ODBC SQL Server Driver
TCP/IP Sockets
ConnectionWrite (send()). (RESULTS LOST)
Mon, 27 Oct 2008 18:52:09 +0000 – Unable to connect to database: Database Error:
Microsoft
ODBC SQL Server Driver
TCP/IP Sockets
ConnectionWrite (send()).
We’ve restarted the FillDB service and also rebooted the server but no luck at the moment.
When looking in SQL manager we can see the FillDB service attempting to write but it’s also showing a PAGEIOLATCH_SH error
Our BES deployment is 15,000 clients and our server has 8 cpu’s, 8gb RAM and an 8gb pagefile. The disk is SAN attached.
We’ve not come across this issue before so was wondering if these FillDB errors point to something we can look into?
My next step is to get the storage team involved.
Cheers
Steve