The eG manager
failed to start. The error_log revealed the following error:
Issue : ERROR UploadServlet Failed to insert measurements. The
tablespaces used for the eG database could be full ...
INFO DbInfo:insertToDbTableFromUpload java.sql.sqlexception: could not
allocate space for object 'dbo.processtest'.'idx_processtest' in database
'egmonitor' because the 'primary' filegroup is full. create disk space by
deleting unneeded files, dropping objects in the filegroup, adding additional
files to the filegroup, or setting autogrowth on for existing files in the
filegroup. Query is INSERT into ProcessTest WITH (ROWLOCK)
(TRGT_HOST,PORT_NO,SITE_NAME,INFO,MSMT_HOST,MSMT_TIME,NUM_PROC,NUM_PROC_ST,CPU_UTIL,CPU_UTIL_ST,MEM_UTIL,MEM_UTIL_ST)
values ('MHCALBESXP06','NULL','NULL','+vcagent','MHCALBESXP06',convert(datetime,'06/01/2009
01:27:56',103),'2','GOOD','0.7','GOOD','1.4','GOOD')
What does this
mean, and how do I resolve this error?
Best Answer
A
Administrator
said
over 8 years ago
This error occurs when the database runs out of space and is not able to insert any more data in to the database tables.
Solution:
Stop the eG manager, allocate more space to the database, and then start the eG manager.
Best practices:
1. eG recommends monitoring the database size of the eG backend to avoid these issues.
2. Fragmented indexes can occupy more space than actually required. This can be minimized by performing periodic database maintenance operations like re-indexing / de-fragmenting tables periodically.
Online indexing can be automated using the steps below,
Go to <eg_installed_dir>\manager\config and edit the file eg_services.ini.
Search for the word “IndexRebuild” and set the flag from No to Yes, then save the file.
This enables the automatic re-indexing.
1 Comment
A
Administrator
said
over 8 years ago
Answer
This error occurs when the database runs out of space and is not able to insert any more data in to the database tables.
Solution:
Stop the eG manager, allocate more space to the database, and then start the eG manager.
Best practices:
1. eG recommends monitoring the database size of the eG backend to avoid these issues.
2. Fragmented indexes can occupy more space than actually required. This can be minimized by performing periodic database maintenance operations like re-indexing / de-fragmenting tables periodically.
Online indexing can be automated using the steps below,
Go to <eg_installed_dir>\manager\config and edit the file eg_services.ini.
Search for the word “IndexRebuild” and set the flag from No to Yes, then save the file.
Bill Parker
The eG manager failed to start. The error_log revealed the following error:
Issue : ERROR UploadServlet Failed to insert measurements. The tablespaces used for the eG database could be full ...
INFO DbInfo:insertToDbTableFromUpload java.sql.sqlexception: could not allocate space for object 'dbo.processtest'.'idx_processtest' in database 'egmonitor' because the 'primary' filegroup is full. create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. Query is INSERT into ProcessTest WITH (ROWLOCK) (TRGT_HOST,PORT_NO,SITE_NAME,INFO,MSMT_HOST,MSMT_TIME,NUM_PROC,NUM_PROC_ST,CPU_UTIL,CPU_UTIL_ST,MEM_UTIL,MEM_UTIL_ST) values ('MHCALBESXP06','NULL','NULL','+vcagent','MHCALBESXP06',convert(datetime,'06/01/2009 01:27:56',103),'2','GOOD','0.7','GOOD','1.4','GOOD')
What does this mean, and how do I resolve this error?
This error occurs when the database runs out of space and is not able to insert any more data in to the database tables.
Solution:
Stop the eG manager, allocate more space to the database, and then start the eG manager.
Best practices:
1. eG recommends monitoring the database size of the eG backend to avoid these issues.
2. Fragmented indexes can occupy more space than actually required. This can be minimized by performing periodic database maintenance operations like re-indexing / de-fragmenting tables periodically.
Online indexing can be automated using the steps below,
Go to <eg_installed_dir>\manager\config and edit the file eg_services.ini.
Search for the word “IndexRebuild” and set the flag from No to Yes, then save the file.
This enables the automatic re-indexing.
Administrator
This error occurs when the database runs out of space and is not able to insert any more data in to the database tables.
Solution:
Stop the eG manager, allocate more space to the database, and then start the eG manager.
Best practices:
1. eG recommends monitoring the database size of the eG backend to avoid these issues.
2. Fragmented indexes can occupy more space than actually required. This can be minimized by performing periodic database maintenance operations like re-indexing / de-fragmenting tables periodically.
Online indexing can be automated using the steps below,
Go to <eg_installed_dir>\manager\config and edit the file eg_services.ini.
Search for the word “IndexRebuild” and set the flag from No to Yes, then save the file.
This enables the automatic re-indexing.
-
Finding eG Agent version
-
Delete and Acknowledge alarms
-
Updating nick names
-
Changing IP address of a monitored component
-
Changing IP address of remote agent and external agent
-
Inside view metrics are not collected by eG
-
Error 1067
-
Agent stopped running
-
eG agent auto-startup
-
Remote agent connection issue
See all 77 topics