Re: ONDBSPACEDOWN config parameter

At 08:30 AM 1/22/97 -0500, you wrote: >Recently, I discovered the importance of the ONDBSPACEDOWN parameter in >ver 7.1. When performing a warm restore on a non-critical down chunk, >our users began complaining of problems. We found the hard way that our >ONDBSPACEDOWN was set to 2 which is "wait". The system hung with a >blocked checkpoint. We had to bring the system down and change the >parameter to 0 so that we could re-start the warm restore. This cost a >couple of hours of down time. > >Questions - >1. What is the ramification of having ONDBSPACEDOWN = 0 when using >fragmented tables? >2. If a chunk containing a table fragment goes down, could users still >query the fragmented table and get unpredictable query results? Yes and no. You also need to have DATASKIP set, to take full advantage. With these params set, a user could query a partitioned table, and skip the down fragment. The obvious down side to this, is the user will likely get unpredictable results back. Setting ONDBSPACEDOWN alone, does have the advantage of not crashing the whole server, if a chunk goes down. However, anyone trying to access the down chunk, will obviously have problems. Whether you set these, depends on your application, and business. We use ONDBSPACEDOWN, but can not use DATASKIP (which would likely be used in DSS/DW environments), for the obvious reason. Jon ---------------------------------------------------------------------------- --- Jon C. Vemo "Life is like a dogsled team, if you ain't the jvemo@cyberspace.com lead dog the scenery never changes." ---------------------------------------------------------------------------- ---