-f tscreate 
This BRSPACE function creates a new tablespace with up to five files. For more information, see Creating a Tablespace with BR*Tools.
Function options:
-a|-autoextend: sets autoextend mode for the data file so that Oracle automatically extends the tablespace as it grows
Syntax: -a|-autoextend[1|2|3|4|5]
[1|2|3|4|5] specifies the sequence number of the file for the new tablespace
Default: as for the last data file added to the database
-c|-contents: defines the contents of the new tablespace
Syntax: -c|-contents data|temp|undo
data: normal data contents
temp: temporary tablespace for certain large-scale actions (for example, sorts)
undo: undo tablespace
For more information about temp and undo, see the Oracle documentation.
Default: data
-d|-data: defines the type of data in the new tablespace, according to SAP convention
Syntax: -d|-data table|index|both
table: table data
index: index data
both: both table and index data - this is the current SAP recommendation
Default: both
-f|-file: defines the first data file of the new tablespace
Syntax: -f|-file[1|2|3|4|5] <file>|<sapdata_dir>|
sapdata<N>|<N>|sapraw
[1|2|3|4|5] specifies the sequence number of the file for the new tablespace
<file> specifies the full name of the data file
<sapdata_dir> specifies the path name to the sapdata directory where the new file is located
sapdata<N>|<N> specifies the name or number of the sapdata directory where the new file is located
sapraw specifies the directory for a softlink to raw disks
BRSPACE automatically extends the incomplete file name to the full name using the SAP naming conventions.
Default: generated automatically according to SAP naming conventions recommended in the sapdata directory used by the last file added to the database
-i|-incrsize: Defines the increment by which the file is extended if autoextend is set
Syntax: -i|-incrsize[1|2|3|4|5] <size>
[1|2|3|4|5] specifies the sequence number of the file for the new tablespace
<size> specifies the size of the increment in MB
Default: as for the last data file added to the database
-j|-join: defines the tablespace joined to the tablespace already defined with the above parameters, if option -d|-data was set to table or index. For example, PSAPSTABD and PSAPSTABI are, according to the old tablespace naming conventions, a pair of joined tablespaces.
Syntax:-j|-join <tablespace>
<tablespace> specifies the joined tablespace name
Default: follows SAP conventions
-l|-class: specifies the table data class for the tablespace
Syntax:-l|-class all|<tab_class>|<tab_class_list>|
<old_tsp>|<old_tsp_list>|none
all specifes that the tablespace has the standard SAP table data classes except class USER
<tab_class> specifies that the tablespace has the new customer table data class. The name must start with “Y” or “Z”.
<tab_class_list> as tab_class but for multiple classes
<old_tsp> specifies that the new tablespace has the same table data class as an existing tablespace, which is later dropped
<old_tsp_list> as old_tsp but for multiple classes
none specifies that no table data class is assigned
You must specify data classes beginning with the letters “Y” or “Z” (these are customer data classes) and with a maximum length of five characters. You use these data classes for customer development or when moving tables. If you do not set this option, BRSPACE automatically generates a customer data classes beginning with “U”.
-m|-maxsize: defines the maximum file size to which the file can be extended if autoextend is set
Syntax: -m|-maxsize[1|2|3|4|5] <size>
[1|2|3|4|5] specifies the sequence number of the file for the new tablespace
<size> specifies the maximum file size in MB. 0 sets the maximum database size to unlimited (maximum 32 GB for SAP standard of 8 KB database block size).
Default: as for the last data file added to the database
-o|-owner: defines the SAP owner of the tables or indexes that are located in the new tablespace – required in Multiple Components in One Database (MCOD) configurations
Syntax:-o|-owner <owner>|none
<owner> specifies the name of the SAP owner
none specifies that there is no owner
Default: no default in MCOD, otherwise the single SAP owner
-p|-space: defines the type of Oracle segment space management in the tablespace
Syntax: -p|-space auto|manual
auto: bitmap management
manual: freelist management
Default: auto
-r|-rawlink: defines the destination of a raw disk or a link to a non-sapdata directory. This is defined as follows:
For a raw disk, the SAP convention is to specify a softlink in the directory /oracle/<DBSID>/sapraw
For a link to a destination outside sapdata, such as to /oracle/temp, the new file is added as a symbolic link
Syntax: -r|-rawlink[1|2|3|4|5] <link target>
[1|2|3|4|5] specifies the sequence number of the file for the new tablespace
<link target>specifies the link target
Default: no raw link
-s|-size: defines the tablespace file size
Syntax: -s|-size[1|2|3|4|5] <size>
[1|2|3|4|5] specifies the sequence number of the file for the new tablespace
<size> specifies the data file size in MB
Default: as for the last data file added to the database
-t|-tablespace: defines the tablespace to be created
Syntax: -t|-tablespace <tablespace>
<tablespace> specifies the tablespace name
Default: none, since you must always define the tablespace name
-u|-uniform: defines tablespaces with a uniform size, where the space is not automatically allocated
Syntax: -u|-uniform <size>
<size> specifies the uniform tablespace size in MB
Default: none
NoteThe options below all refer to the joined index tablespace.
End of the note.-xa|-xautoextend: refers to the joined index tablespace – see -a|-autoextend above
-xf|-xfile: refers to the joined index tablespace – see -f|-file above
-xi|-xincrsize: refers to the joined index tablespace – see -i|-incrsize above
-xm|-xmaxsize: refers to the joined index tablespace – see -m|-maxsize above
-xr|-xrawlink: refers to the joined index tablespace – see -r|-rawlink above
-xs|-xsize: refers to the joined index tablespace – see -s|-size above