on 2018 Oct 15 1:27 PM
I guess the answer is "yes" but are not sure how to check that...
Running 16.0.0.2704, I have added a dbspace (*) to store blob data on that separate dbspace. Now it looks like the system dbspace has unexpectedly grown, too.
However, according to SYSTAB and SYSIDX, the freshly created tables and their indexes are stored on the dbspace, as desired.
Because most rows are stored in extension pages, I'm unsure whether they are stored in the dbspace, too.
Is there a system procedure to check that?
(*) I usually do not use separate dbspaces but in that case, it's quite likely the blob data will be purged lateron, and I do not want to have the main database file grown too much.
Request clarification before answering.
The extension pages are stored in the same dbspace as the other table pages.
Are you updating or deleting blobs? If so, perhaps the increased file size you are seeing is the checkpoint log. The checkpoint log at the end of the system dbspace is used for saving images from all dbspaces. You can use db_property('CheckpointLogSize') to find how many pages in the system dbpsace file are being used for the checkpoint log.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Insertion doesn't usually generate many checkpoint log pages since newly allocated pages don't get a preimage stored in the checkpoint log (there is no preimage for a newly allocated page). That's why I asked if you were updating or deleting. Index pages will get modified for inserts though.
User | Count |
---|---|
52 | |
10 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.