Clarification on the Oracle XE 4Gb limit [message #468254] |
Thu, 29 July 2010 05:53 |
aidi-h
Messages: 45 Registered: November 2005
|
Member |
|
|
In regard to the Oracle 4GB limit, what exactly is this limit?
Is this the total size of the datafiles of the user defined tablespaces (excluding SYSTEM and UNDO) so if, for example, we have a 2.8Gb datafile, can we only add another 1.2Gb datafile.
or is it the total size of extents/segments in the user defined tablespace i.e. if we have a 2.8Gb datafile but the database data comes to only 1.7Gb, can we add another tablespace with a new 2.8Gb datafile to allow for another 1.7Gb schema.
Any clarification would be appreciated.
|
|
|
|
|
|
|
|
Re: Clarification on the Oracle XE 4Gb limit [message #468335 is a reply to message #468334] |
Thu, 29 July 2010 14:31 |
aidi-h
Messages: 45 Registered: November 2005
|
Member |
|
|
Many thanks for the replies guys!!! I presume that the limitation is on the data itself i.e. I could have, for example a datafile at 100Gb (using a daft example I know) but the total sum of the extents/segments on the datafile comes to only 1.7Gb so XE will still operate. I could then add another tablespace with another 100Gb datafile and import 1.7Gb of data there and XE will still operate fine as we still only have a total of 3.4Gb of data there.
Many thanks again
|
|
|
Re: Clarification on the Oracle XE 4Gb limit [message #468338 is a reply to message #468335] |
Thu, 29 July 2010 14:48 |
mkounalis
Messages: 147 Registered: October 2009 Location: Dallas, TX
|
Senior Member |
|
|
You REALLY need to read the fine documentation that you can get to from the link I posted above. You can NOT have a tablespace that is over 4gb is size, so that means you can NOT have a 100gb datafile in use. The GUI for OracleXE controls your world quite strictly in XE land. What is it that you are trying to do exactly?
|
|
|
|
Re: Clarification on the Oracle XE 4Gb limit [message #468341 is a reply to message #468338] |
Thu, 29 July 2010 15:00 |
aidi-h
Messages: 45 Registered: November 2005
|
Member |
|
|
ok to summarise, I have a tablespace with a single 2.7Gb datafile. one schema owns the objects therein and the total size of the extents comes to 1.7Gb. We want to export these objects and import them back onto the database but under a new schema name (and probably a new, different tablespace). This means that over both old and new tablespaces, we will have a total of 5.4Gb (2*2.7Gb) in datafiles and a total of 3.4Gb (2*1.7Gb worth of extents) in actual data.
The question is, will the proposed increase to 5.4Gb for our datafiles be a problem or will the XE database only hit issues when the 3.4Gb in actual data exceeds 4Gb.
|
|
|
|