Let me expand: My concern is that if we define an
area like "customer" and load the customer.d into that
area - if the customer file were to grow - and the
area is full - what will happen with the data? Do
we need to consider growth of the files and allocate
growth space to the area? If an area were to fill up
what happens to the DB? does it crash? Is there
a way to monitor and build in some checks to make
sure that the area doesn't fill up?
An AREA in Progress is a LOGICAL partion (if I can use that expression).. Each Area contains multiple extents, so think of an Area as a V8 multi volume database, except that there is no .bi per area, just one for the database as a whole. All of the utilities have been updated to include Area information
"Stephanie" wrote:
>
>Let me expand: My concern is that if we define an
>area like "customer" and load the customer.d into that
>
>area - if the customer file were to grow - and the
>area is full - what will happen with the data? Do
>we need to consider growth of the files and allocate
>growth space to the area? If an area were to fill up
>what happens to the DB? does it crash? Is there
>a way to monitor and build in some checks to make
>sure that the area doesn't fill up?