Hi Folks, Answering my own question here. Finally got some time to investigate this one and it looks like the rebuild is needing more space in tmpDB.
It looks like when tmpDB runs out of space, the rebuild has not identified this. Instead it keep trying over and over again using 100% CPU and not doing anything with the insufficient disk space errors that are being returned. I've increased the memory allocated to tmpDB now. Would it be possible to have the rebuild process do a periodic check on the tmpDB for free space? This check would be able to return an error to the rebuild log and possibly even raise a notification somewhere. Even simpler could be a process at the end of the rebuild run that adds a line saying "X amount of space was required in tmpDB for this rebuild run to complete." That would enable us to keep an eye on out for patterns in the usage and see quickly if the usage is increasing or approaching the size of the tmpDB. All the best, Colin Waring. ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
