Bigfile or smallfile tablespace?

Hi community,
I'd like to set up a Oracle database (Version 10.2.0.3 64-bit) on a Windows Server 2003 (64-bit).
Server Hardware:
- Dual Core AMD Opteron
- Processor 8224 SE, 3,21 GHz
- 16 GB RAM
Storage:
- HP StorageWorks MSA 1000
- 3 x 250 GB (RAID 1)
- At the moment the 250 GB drives are combined to one large 750 GB Logical Drive (RAID 0)
The data content for the new database are coming from an DB2 (will be copied to Oracle DB) and the size is about 350 GB at the moment, upward trend.
Data:
150 tables with less than 100.000 rows.
40 tables with more than 100.000 rows but less than 1.000.000 rows.
15 tables with more than 1.000.000 rows (biggest table has 125.000.000 rows)
So my questions now regarding how to size a tablespace for the new Oracle instance:
1. Should I create a bigfile tablespace with one large datafile (350 - 400 GB) or should I create a smallfile tablespace with several smaller datafiles?
2. At the moment the db_block_size is 8 kb. This means that I can create a datafile for a smallfile tablespace with a maximum of 32 GB. So for 350 GB I need at least 11 datafiles. I think this is not a good solution. So maybe I should change the db_block_size to 16 KB so I can create datafiles up to 64 GB? What effects will this change of the block size bring?
3. Is it better, for performace issues, to use the 750 GB RAID10 Array or should I use three 250 GB RAID1 Arrays and allocate different datafiles on them?
4. For the beginning should I size the tablespace as big as it really is (350GB) or should I size it bigger (400GB)?
I would really appreciated, if somebody can help me with this issue...
Thanks in advance,
Tobias Schmidt

Use standard tablespaces. You do not need the larger files with their limitations. Read more at http://tahiti.oracle.com. If performance is an issue then you should get management to invest in decent storage. Three internal drives with mirroring is totally inadequate for any serious work. Look at Pillar Data Systems or NetApp for NAS and/or SAN. Here's why:
You have a 350GB database with RAID 0 so you just used 100% of your available disk. You've no room left. No room for the operating system and no room for the Oracle binaries if one assumes a swap space. Then where are you going to put SYSTEM, SYSAUX, TEMP, and UNDO tablespaces? And they too need to be mirrored. How about your archived redo logs? backups? flashback logs?
I wouldn't consider putting a 350GB database on anything less than 6X that much space: More if, as you indicate, it is growing. And tell your storage admin that one LUN is not the right answer to just about any question.
Also I am puzzled why, with what appears to be a serious database, you are using Windows rather than Linux.

Similar Messages

Bigfile vs. smallfile tablespaces

Oracle 11g R1/ASM Single-Instance
RHEL 5
========
Hi All,
I just wanted everyones opinion about using bigfile tablespaces vs. the regular smallfile tablespaces. We have one tablespace that gets filled up pretty quick...it is loaded with images and we are trying to decide whether we should go the bigfiles tablespace route or should we just keep creating additional datafiles with the smallfile tablespace method. If I am correct the maximum a smallfile datafile can be is 65GB. And that lasts us about a couple of months. I guess my real question is how would a bigfile tablespace affect database/datafile recoverability. From common sense, I think it would take much longer to recover a 4TB datafile as compared to a 65GB datafile. Or would it?
I just wanted to know what you all think and what you have experienced.
Thanks.

Oviwan wrote:
As far as I know bigfiles are designed for ASM. I used it only once for a big temp tablespace for a migration. But I think if a block gets corrupt it's better to use several small datafiles, hence you have to restore the corrupt one datafile instead of the big one.
the limitation of a datafile is platform dependend. on linux it is 32GB...
have a look here: http://download.oracle.com/docs/cd/B28359_01/server.111/b28320/limits002.htm#i287915
But you risk a data block corruption either way you go, and if you are in archive log mode, with RMAN, you can fairly easily repair the bad block.
It sounds like to me, that the parent of this thread is a fantastic candidate for BigFile tablespaces. I'm actually looking at trying to move MOST of my stuff to them to see how it does...I'd rather let Oracle manage it and free me up to work on other things. The nice thiing with bf tablespaces is...finally the datafile and tablespace are pretty much one in the same thing now.
I wouldn't throw every thing in a database onto just one bigfile ts...but, I would have a few bigfile tablespaces out there and separate things by usage/application. But really if you have a big SAN, using ASM and all, why not just put more things together and make life siimpler on yourself?
Just my $0.02 here of late,
cayenne

Bigfile or Smallfile?

Hi,
We're migrating a lot of databases from HP-UX(file system) to Linux with ASM.
We're trying to decide what is better for us bigfiles or smallfiles tablespaces. All databases is 11.2.0.3 and I'd like your thoughts on the subject.
Regards
933746

Helios- Gunes EROL wrote:
Hi;
I belive you got your answer.Please dont forget to change thread status to answered if it possible when u belive your thread has been answered, it pretend to lose time of other forums user while they are searching open question which is not answered,thanks for understanding
Regard
HeliosWill do.And again thanks for help guys

Smallfile or Bigfile tablespace?

Hi!
Smallfile or Bigfile tablespace?
I have 5TB DB(RAC 2 node) with bigfile + smallfile tablespace's.
I want create tablespace, but I don't know how can I choose type of tablespace?
I find some tips:
1.Using BIGFILE tablespaces on platforms that do not support large file sizes is not recommended : it limits tablespace capacity.
2.The fact that only one data file is attached to a tablespace makes it easier to manage: the tablespace becomes the unit of administration.
3.Maximum Datafile Size Limit In an Oracle Database.
4.Restore operation quicklier on smallfile than bigfile.
5.Bigfile tablespaces should be striped so that parallel operations are not adversely affected. Oracle expects bigfile tablespace to be used with Automatic Storage Management (ASM) or other logical volume managers that support striping or RAID.
6.Avoid using bigfile tablespaces if there could possibly be no free space available on a disk group, and the only way to extend a tablespace is to add a new datafile on a different disk group.
7.Bigfile tablespaces should be used with automatic storage management, or other logical volume managers that support dynamically extensible logical volumes, striping and RAID.
Sorry, if I repeat this global topic.
But, do you have more arguments to use bigfile tablespace?

duplicated post :
Bigfile or smallfile tablespace?
Question about BIGFILE vs SMALLFILE
and:
http://www.databasejournal.com/features/oracle/article.php/3646226/Bigfile-Type-Tablespaces-versus-Smallfile-Type.htm
Edited by: Fran on 13-mar-2012 2:06

Maximum size of a datafile

What is the maximum size we can give to a datafile?

user8850066 wrote:
What is the maximum size we can give to a datafile?Use this clause to determine whether the tablespace is a bigfile or smallfile tablespace. This clause overrides any default tablespace type setting for the database.
A bigfile tablespace contains only one datafile or tempfile, which can contain up to approximately 4 billion (232) blocks. The maximum size of the single datafile or tempfile is 128 terabytes (TB) for a tablespace with 32K blocks and 32TB for a tablespace with 8K blocks.
A smallfile tablespace is a traditional Oracle tablespace, which can contain 1022 datafiles or tempfiles, each of which can contain up to approximately 4 million (222) blocks.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_7003.htm#SQLRF01403
Kamran Agayev A.
Oracle ACE
My Oracle Video Tutorials - http://kamranagayev.wordpress.com/oracle-video-tutorials/

Resize datafile or add new datafile which is good?

Hi all
we have 80 GB database size and only two tablespace have space around 60 Gb
these two tablespace have one database each around 30 gb so
My question is it good to resize current datafile or
It it good to add new datafile ?

Your question is which is "best"; add datafile or resize right? If yes, then I think below links will answer you :
http://www.freelists.org/post/oracle-l/Datafile-size-Is-bigger-better,9
datafile and size
Bigfile or smallfile tablespace?
Just go through these link. I am sure answer in it.
Regards
Girish Sharma

What is different "init size 1 GB ext 1 GB" and "init size 1 GB ext 1 G

Hi all,
What is different of performance (and backup) between
"init size 1 GB ext 1 GB Max 10 GB : 10 Files "
and
"init size 2 GB ext 2 GB Max 20 GB : 5 Files "
in Oracle10 database?
Thank in advance,
Kor

Hi,
I guess you are concerned with "Bigfile Tablespaces".
Oracle lets you create bigfile tablespaces. This allows Oracle Database to contain tablespaces made up of single large files rather than numerous smaller ones. This lets Oracle Database utilize the ability of 64-bit systems to create and manage ultralarge files. The consequence of this is that Oracle Database can now scale up to 8 exabytes in size.
An Oracle database can contain both bigfile and smallfile tablespaces. Tablespaces of different types are indistinguishable in terms of execution of SQL statements that do not explicitly refer to datafiles.
Bigfile tablespaces can significantly increase the storage capacity of an Oracle database. Smallfile tablespaces can contain up to 1024 files, but bigfile tablespaces contain only one file that can be 1024 times larger than a smallfile tablespace. The total tablespace capacity is the same for smallfile tablespaces and bigfile tablespaces. However, because there is limit of 64K datafiles for each database, a database can contain 1024 times more bigfile tablespaces than smallfile tablespaces, so bigfile tablespaces increase the total database capacity by 3 orders of magnitude. In other words, 8 exabytes is the maximum size of the Oracle database when bigfile tablespaces are used with the maximum block size (32 k).
Bigfile tablespaces are intended to be used with Automatic Storage Management or other logical volume managers that support dynamically extensible logical volumes and striping or RAID.
Hope this concludes you.
Regards
Vinod

Need clarification on Bigfile Tablespaces

In the following Oracle Documentation Lirbary PDF,
    Oracle® Database
    Concepts
    10g Release 2 (10.2)
    B14220-02
    October 2005
section
    Overview of Tablespaces
    Bigfile Tablespaces (page: 3-5)
it says,
    Benefits of Bigfile Tablespaces
    * Bigfile tablespaces can significantly increase the storage capacity of an Oracle database. Smallfile tablespaces can contain up to 1024 files, but bigfile tablespaces contain only one file that can be 1024 times larger than a smallfile tablespace. The total tablespace capacity is the same for smallfile tablespaces and bigfile tablespaces. However, because there is a limit of 64K database for each database, a database can contain 1024 times more bigfile tablespaces than smallfile tablespaces, so bigfile tablespaces increase the total database capacity by 3 orders of magnitude. In other words, 8 exabytes is the maximum size of the Oracle database when bigfile tablespaces are used with the maximum block size (32k).
I need clarification on how to arrive at 8 exabytes ?
1024 x 32k x 64,000 ??
According to the exerpt above, there's no mention of maximum number of Operating System blocks per extent. Unless this was assumed knowledge ... how do I get 8 exabytes ?
And if "a database can contain 1024 times more bigfile tablespaces than smallfile tablespaces", then what's the upper limit on smallfile tablespaces ? -- was this sentence referring to the number of datafiles per smallfile tablespace ? ...
O_o
Thanks !
Message was edited by:
mvanle

Hi,
According to [url http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14237/limits002.htm#i287915]Physical Database Limits page, a bigfile tablespace contains only one datafile or tempfile, which can contain up to approximately 4 billion ( 232 ) blocks. The maximum size of the single datafile or tempfile is 128 terabytes (TB) for a tablespace with 32K blocks and 32TB for a tablespace with 8K blocks. In resume, A bigfile tablespace is a tablespace containing a single datafile that can be as large as 128 terabytes (TB), depending on the block size of the tablespace. In conjunction with setting the initialization parameter DB_FILES to the maximum value of 65,635 the total size of the database can be more than 8 exabytes (EB)
>>how do I get 8 exabytes ?
You can calculate the maximum amount of space (M) in a single Oracle database as the maximum number of datafiles (D) multiplied by the maximum number of blocks per datafile (F) multiplied by the tablespace block size (B):
M = D * F * B. Therefore, the maximum database size, given the maximum block size and the maximum number of datafiles, is:
65,535 datafiles * 4,294,967,296 blocks per datafile * 32,768 block size = 9,223,231,299,366,420,480 = 8EB.Cheers
Legatti

Bigfile Temporary Tablespaces

In most RAC environments, you use multiple tempfiles in a temp tablespace to avoid contention yet in the Exadata OLTP best practices guide it stats that you should start out by using a bigfile tablespace for temporarty tablespaces. This seemed odd to me since bigfile tablespaces can only have one tempfile. Understanding that OLTP may not have much parallelism, so multiple tempfiles may not be needed but it still seemed odd to use bigfile instead of smallfile tablespaces for something like temp. Does anyone have any experience with using bigfile tablespaces on RAC for temporary tablespaces.

I have used bigfile temporary tablespaces for some intensively parallelized operations and never encountered any contention problems. If I were you, since we are talking about temporary stuff, I would make the change and run some tests.

Maximum number of blocks for a bigfile datafile?

Hello,
In 10g, when using bigfile tablespaces, the maximum size of a datafile can be between 8TB to 128TB depending on the block size (2K to 32K). The formula given to calculate the max size of a bigfile datafile is:
Maximum datafile size = db_block_size * maximum number of blocks
So my question is how do you calculate the max number of blocks? Oracle documentation states that the max number of blocks is 4,294,967,296 (4 billion) 2^32. But where do they get this number from? I read, on a different site (not Oracle), that it is the addressing scheme used in ROWID that changed permitting the possibility of addressing 4 billion blocks instead of 4 million:
This is due to a new addressing scheme Oracle uses internally. Oracle ROWID, addressing a database object stored in a traditional SMALLFILE tablespace, divides the 12 bytes thusly: 3 bytes for the Relative File#, 6 bytes for the Block# and 3 bytes for the object. The same rowid addressing an object stored in a new BIGFILE tablespace uses the 9 bytes to store the Block# within the unique file, as there is no reason to use the 3 bytes for the Relative File# since there is only one file in that tablespace. Thus the new addressing scheme permits up to 4Gblocks (4,294,967,296) in a single data file and the maximum file size can reach 8 TB for a blocksize of 2K and 128 TB for a blocksize of 32K.
But, even with this explanation, 4 billion still makes no sense because using 9 bytes equates to 2^72 addressable blocks, not 2^32. Am I missing something?
Thanks,
Mark

Thanks for the answer.
I'm almost tempted to accept the explanation that the 4,294,967,296 addressable blocks is a 32bit platform limitation... Do you or anyone know of any official Oracle documentation explaining where they get this magic number from?

BigFile Issue

I need Basic help regarding this.
A bigfile tablespace is a tablespace with a single, but very large (up to 4G blocks) datafile. Traditional smallfile tablespaces, in contrast, can contain multiple datafiles, but the files cannot be as large. The benefits of bigfile tablespaces are the following:
A bigfile tablespace with 8K blocks can contain a 32 terabyte datafile. A bigfile tablespace with 32K blocks can contain a 128 terabyte datafile. The maximum number of datafiles in an Oracle Database is limited (usually to 64K files). Therefore, bigfile tablespaces can significantly enhance the storage capacity of an Oracle Database.
my question is are there no of blocks are 4G or this is the size of datablock
or more specifically
8K blocks can contain a 32 terabyte datafile.
here 8k blocks are total no of blocks or Blocksize=8k
pls mv my doubt.
manish

We are talking about 4G units of size 8k.
The size of the block is what you have defined for the database (or tablespace). In your case, the bigfile tablespace will have 4 G units, each of size 8k.

ORA-01251 on system tablespace

hi folks,
(of course we didn't have any backup)
when we try to open our DB we get:
SVRMGR> alter database open;
alter database open
ORA-01122: database file 19 failed verification check
ORA-01110: data file 19: '/tecdata/oradata/INVSID/system08.dbf'
ORA-01251: Unknown File Header Version read for file number 19
SVRMGR>
We find some recovery solution but not in case of system tablespace datafile
we cannot drop the datafile 'couse we are not able to open the database.
there is any solution?
thanks everyone!

Hello,
in dba_temp_files, it shows MAXBYTES as 34359721984, so UNLIMITED apparently does mean 32GB??As Sybrand posted, it depends on your Block Size.
If you use Smallfile Tablespace (the default) then, each of its Datafile is limited to *4 MBlock* (so 4x1024x1024 blocks). So, for a Block Size of 8 Ko it gives (8x1024)x(4x1024x1024) Bytes = *32 GB*. But, you may have up to *1022* Datafiles for your Tablespace.
So, if you want your Tablespace to extend more than 32 GB you may add other datafiles, up to *1022*. So in fact the maximum size for your Tablespace can reach almost *32 TB* (for a block size of 8 Ko). Of course, in this case, you'll have so many datafiles that it won't be easy to manage them.
This is the reason why, starting with Oracle 10.1 you may create Bigfile Tablespace. They have just one datafile but, it can reach *4 GBlock*, so 32 TB for a Block Size of 8 Ko.
Before using Bigfile Tablespace, you should ensure that your OS can support such large file else, the capacity of the Tablespace could be really limited.
Hope this help.
Best regards,
Jean-Valentin

Tablespaces : 2 Questions

hello,
im a informatik student from hamburg,
we have the course databasedesign with focus on oracle dbms.
in the past i worked 2 years a bit at oracle 8i and 9i databases as administrator, therfor i have some little konwledge.
our professor told us:
1.
oracle recommend that a tablespace shoudnt greater than 10 gb, i ask him if he mean that the tablespace files shouldnt be greate, he told me that he means the real tablespace, not the tablespace files.
2.
my professor also told us that we can create a single table over more than 1 tablespace, i never heard something about that option. i asked him and he told me he never did it but it shoud really be possible, mybe create table option.
at both pionts i never heard about it, and at my search at the internet i dindt found some relevant information.
maybe i get some answers at this forum :o)
thanks
Andreas

Hi,
Oracle 10g now supports Bigfile Tablespace whcih can contain even very big datafile. See the following abstract from Oracle Document:
Bigfile Tablespaces
A bigfile tablespace is a tablespace with a single, but very large (up to 4G blocks) datafile. Traditional smallfile tablespaces, in contrast, can contain multiple datafiles, but the files cannot be as large. The benefits of bigfile tablespaces are the following:
A bigfile tablespace with 8K blocks can contain a 32 terabyte datafile. A bigfile tablespace with 32K blocks can contain a 128 terabyte datafile. The maximum number of datafiles in an Oracle Database is limited (usually to 64K files). Therefore, bigfile tablespaces can significantly enhance the storage capacity of an Oracle Database.
Bigfile tablespaces can reduce the number of datafiles needed for a database. An additional benefit is that the DB_FILES initialization parameter and MAXDATAFILES parameter of the CREATE DATABASE and CREATE CONTROLFILE statements can be adjusted to reduce the amount of SGA space required for datafile information and the size of the control file.
Bigfile tablespaces simplify database management by providing datafile transparency. SQL syntax for the ALTER TABLESPACE statement lets you perform operations on tablespaces, rather than the underlying individual datafiles.
Bigfile tablespaces are supported only for locally managed tablespaces with automatic segment-space management, with three exceptions: locally managed undo tablespaces, temporary tablespaces, and the SYSTEM tablespace can be bigfile tablespaces even if their segments are manually managed.

Creating new Tablespace in 10g XE using Database Home Page

How can I add a Tablespace using the "Database home Page" GUI? I've done this before, but now do not see a link for "Create Tablespace" under the Administration -> Storage icon. I'm logged in as sys.

use sqlplus to create a new tablespace
(set your XE environment first)
(for Linux)
the environment file envOraXEclient for example) -- modify for your env and different shell, and source the file
export ORACLE_HOME=/usr/lib/oracle/xe/app/oracle/product/10.2.0/server
export TNS_ADMIN=/home/mytnsdirectory
export TWO_TASK=XE
export LD_LIBRARY_PATH=/usr/lib/oracle/xe/app/oracle/product/10.2.0/server/lib
export PATH=$ORACLE_HOME/bin:${PATH}
by using sqlplus, create the tablespace (use different size if you want, up to 4gb, you can create smaller, more than one tablespace, etc - this is just an example)
CREATE SMALLFILE
TABLESPACE "MYTBLSPC1"
DATAFILE '/usr/lib/oracle/xe/oradata/XE/mytblspc1.dbf'
SIZE 2G REUSE AUTOEXTEND ON NEXT 10M MAXSIZE UNLIMITED
LOGGING EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO
if you want, create a dedicated temporary tablespace for your user/s as well (here is an example)
CREATE SMALLFILE TEMPORARY TABLESPACE "MYTEMP"
TEMPFILE '/usr/lib/oracle/xe/oradata/XE/mytemp.dbf'
SIZE 100M REUSE EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1024K
turn the recyclebin off if you want/need to (I do ;)
alter system set recyclebin=off;
change the open_cursors if you want/need to (I do ;)
ALTER SYSTEM SET open_cursors = 5000 SCOPE=MEMORY;
ALTER SYSTEM SET open_cursors = 5000 SCOPE=SPFILE;
ALTER SYSTEM SET session_cached_cursors = 50 SCOPE=SPFILE;
create a specific user utilizing the tablespaces you created earlier
CREATE USER "ZAFER" PROFILE "DEFAULT"
IDENTIFIED BY "zafer" DEFAULT TABLESPACE "MYTBLSPC1"
TEMPORARY TABLESPACE "MYTEMP"
ACCOUNT UNLOCK;
(grants are up to you - and your development / deployment environment)
GRANT UNLIMITED TABLESPACE TO "ZAFER";
GRANT "CONNECT" TO "ZAFER";
GRANT "RESOURCE" TO "ZAFER";
Edited by: zaferaktan on Sep 4, 2009 10:09 AM

Do I need multiple DATA/INDX tablespaces for a DB on a SAN?

Is there any advantage to creating multiple DATA and INDEX tablespaces for databases that are on a SAN? Database size is probably going to be around 1TB per year.
Our databases are normally smaller and perform well with a single DATA tablespace and single INDEX tablespace. I would like to see if we need to use a different approach with a larger db and a SAN in place.
Thanks

Justin
As a follow up to my previous post, yes I can confirm that extent allocation is round robin across all files in a TS. The test outline I gave mentioned rowid but as I reconstructed the test that turned out to be irrelevant.
Here is the results:
SQL> drop tablespace bubba_ts
2      INCLUDING CONTENTS AND DATAFILES;
Tablespace dropped.
SQL> create SMALLFILE tablespace bubba_ts
2      datafile 'c:\oradata\edst\bubbatbs_01.dbf'
3           size 1m
4           autoextend off,
5           'c:\oradata\edst\bubbatbs_02.dbf'
6           size 1m
7           autoextend off,
8           'c:\oradata\edst\bubbatbs_03.dbf'
9           size 1m
10           autoextend off
11      EXTENT MANAGEMENT LOCAL UNIFORM SIZE 64K;
Tablespace created.
SQL> drop user bubba;
User dropped.
SQL> create user bubba
2      identified by bubbapw
3      default tablespace bubba_ts
4      temporary tablespace temp
5      quota unlimited on bubba_ts;
User created.
SQL> grant create session,
2      create table
3 to bubba;
Grant succeeded.
SQL> create table bubba.rowid_test
2      (
3      key_col number,
4      big_col1 char(2000),
5      big_col2 char(2000),
6      big_col3 char(2000)
7      );
Table created.
SQL> BEGIN
2      for i in 1..100 loop
3      insert into bubba.rowid_test
4      values (i,
5           'xxxxx',
6           'xxxxx',
7           'xxxxx'
8           );
9      end loop;
10 END;
11 /
PL/SQL procedure successfully completed.
SQL> col file_name for a35
SQL> select e.extent_id,
2      e.file_id,
3      f.file_name
4 from dba_extents e,
5      dba_data_files f
6 where e.owner = 'BUBBA'
7 and e.segment_name = 'ROWID_TEST'
8 and e.file_id = f.file_id
9 order by e.extent_id
10 ;
EXTENT_ID FILE_ID FILE_NAME
0 10 C:\ORADATA\EDST\BUBBATBS_03.DBF
1 8 C:\ORADATA\EDST\BUBBATBS_01.DBF
2 9 C:\ORADATA\EDST\BUBBATBS_02.DBF
3 10 C:\ORADATA\EDST\BUBBATBS_03.DBF
4 8 C:\ORADATA\EDST\BUBBATBS_01.DBF
5 9 C:\ORADATA\EDST\BUBBATBS_02.DBF
6 10 C:\ORADATA\EDST\BUBBATBS_03.DBF
7 8 C:\ORADATA\EDST\BUBBATBS_01.DBF
8 9 C:\ORADATA\EDST\BUBBATBS_02.DBF
9 10 C:\ORADATA\EDST\BUBBATBS_03.DBF
10 8 C:\ORADATA\EDST\BUBBATBS_01.DBF
11 9 C:\ORADATA\EDST\BUBBATBS_02.DBF
12 10 C:\ORADATA\EDST\BUBBATBS_03.DBF
13 8 C:\ORADATA\EDST\BUBBATBS_01.DBF

Bigfile or smallfile tablespace?

Similar Messages

Maybe you are looking for