Database [build] has reached or exceeded the threshold size
Hi,
We use buildforge to do daily build, we meet an database issue which is as below:
8/1/11 4:22 PM System WarningCRRBF0570I: Database has reached or exceeded the threshold size of , currently .
I find that projects' status are "waiting", evenif I restart them, how can I fix this issue?
Could anyone help me? Thank you!!
We use buildforge to do daily build, we meet an database issue which is as below:
8/1/11 4:22 PM System WarningCRRBF0570I: Database has reached or exceeded the threshold size of , currently .
I find that projects' status are "waiting", evenif I restart them, how can I fix this issue?
Could anyone help me? Thank you!!
5 answers
Hi,
We use buildforge to do daily build, we meet an database issue which is as below:
8/1/11 4:22 PM System WarningCRRBF0570I: Database has reached or exceeded the threshold size of , currently .
I find that projects' status are "waiting", evenif I restart them, how can I fix this issue?
Could anyone help me? Thank you!!
Hi,
The database threshold check just results in a warning message and possibly email if that has been configured. It will not have any effects on the running of jobs. You can increase the threshold size at which the warning occurs by navigating in the UI to Administration -> System -> 'Database Size Threshold'.
I think something else must be going on that is causing jobs to remain in waiting state, although database performance due to its size might be a factor. Other things to check might be server max jobs, project run limits, run queue size, and max console procs.
Brent Ulbricht
RTC Build Lead
server max jobs: 100
I think other things will not affect the project, because I just have 3 projects running, where's the log I can see to check why projects' status are always be "waiting"????
It's curious, my projects are running well before....
The "waiting" job can not be cancel.... I don't know how to delete them.
If jobs are always waiting verify that the buildforge process is running. There also should be a bfproject process for each running build. If you do not have the bfproject processes they may be left over builds from a start of build forge. Run the following query to cancel the builds:
UPDATE BF_BUILDS SET BF_STATE='C' WHERE BF_TAG='build_tag_of_job';
COMMIT:
UPDATE BF_BUILDS SET BF_STATE='C' WHERE BF_TAG='build_tag_of_job';
COMMIT:
If jobs are always waiting verify that the buildforge process is running. There also should be a bfproject process for each running build. If you do not have the bfproject processes they may be left over builds from a start of build forge. Run the following query to cancel the builds:
UPDATE BF_BUILDS SET BF_STATE='C' WHERE BF_TAG='build_tag_of_job';
COMMIT:
I think this is a bug, isn't it? Hope you will fix that.
I restart buildforge and db2 then the waiting projects can be canceled.