T.R | Title | User | Personal Name | Date | Lines |
---|
5101.1 | | M5::LWILCOX | Chocolate in January!! | Wed Mar 05 1997 08:25 | 1 |
| Could note 3183 apply or 4141?
|
5101.2 | | NOVA::FISHER | | Wed Mar 05 1997 09:48 | 12 |
| The important problem here is how'd you do that? If you can
figure out what was done to get the area defined more than once
then please bug it, especially if we can determine that it hasn't
been fixed. We think we've seen this before and fixed the bug that
allowed the multiple definition.
That said, it appears we never did anything that allows fixing the
db once it gets bollixed. Not only can you not drop the offending
area, you can't drop any area. This problem has been corrected in a
future update.
ed
|
5101.3 | Simple Alter ... add storage | ORAREP::KYOSS1::WALKER | Clarke Walker, NJ NISI, DTN:323-4040 | Wed Mar 05 1997 10:23 | 22 |
| I looked at 3183 and 4141, and the result seems to be same but maybe
not the cause. In this database we do not have "multithread areas" at
least I do not see any line to this effect in the dump of the header.
The database was created 3 1/2 years ago.
The problem was created by executing:
Alter Database filename CRIS$DB
Add storage area PAGE_IMAGE_AREA54A
filename 'CRIS_IMGA:[CRIS.PAGEDB]PAGE_IMAGE_AREA54A.RDA'
page format is MIXED
page size is 32 blocks
allocation is 99986 pages
... and so on ...
;
from two processes. (The boss decided to help out!) Because of
the size of the database area it takes awhile for them to be created.
So the second job was actually started 10 minutes later.
This database has about 10 gbytes of read/write data and 80 Gbytes of
data on optical storage.
|
5101.4 | note 4398 and Rdb70 qar 1896 | 12293::ALLEMEERSCH | In Flanders fields ... | Thu Mar 06 1997 11:35 | 3 |
| See also note 4398 in this conference and Rdb70 qar 1896.
_Luc
|