Documaker DMKR_ASLINE Tablespace Continuing To Extend
(Doc ID 2527611.1)
Last updated on DECEMBER 04, 2019
Applies to:Oracle Documaker - Version 12.5 and later
Information in this document applies to any platform.
This may be a more appropriate question for Oracle Database, however I thought I would ask if there are any database settings we may be missing for Oracle Documaker.
Our situation is that we had 16 BDF's defined to the dmkr_asline tablespace totaling 512 GB, with 358 GB free. All of the BDFs have gone to their Maximum Size of 32 GB, since auto extend is turned on. Last evening, the factory started failing due to not being able to go for any more extents. We do not understand why this happened, since the tablespace shows that there is 358 GB available.
Looking at the BDF's, #1, #2, #4, #5, and #16 shows as 100% used, while the 11 BDF's show at less than .01% used. We are also confused why the space used is not evenly distributed across the BDF's.
We were able to get around the problem by adding a 17th BDF, but we are concerned it will continue to extend until it reaches it 32 GB limit and we will be in the same situation again.
How can we get the freed space to be used in the other BDF's and to evenly distribute the used spaced across all BDF's.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document