Working with Oracle Database data files

When working with the Oracle Database DBMS, 1C:Enterprise creates the following tablespaces:

  • V81C_DATA – for data,
  • V81C_INDEX – for indexes,
  • V81C_LOB – for strings of unlimited length and ValueStorage objects,
  • V81C_TEMP – for temporary data.

Tablespaces are created during the infobase creation process only if they do not exist. This means that tablespaces are created during the creation of the first infobase that uses the Oracle Database DBMS, and all subsequent infobases will use those tablespaces.

Each tablespace has a single datafile. Since the created tablespaces have ordinary type (no bigfile option), the datafile size is limited to 32 GB (this value implies using blocks of 8 KB, which is a default value).

The table below illustrates the difference between an ordinary tablespace and a bigfile tablespace.

Ordinary tablespace Bigfile tablespace

Can consist of multiple datafiles.

Consists of a single datafile.

Each datafile is limited to 32 GB (by default).

The datafile size is limited to 32 TB (by default).

Multiple disks can be used for a single tablespace.

A single file implies using a single logical disk, therefore, allocation across several disks is impossible.

When the datafile is 85% full (it is the default value), the Oracle Database DBMS generates an alert to the alert log. At this time you need to add a data file to the tablespace. If no action is taken when the file is 97% full (it is also the default value), an error message informing that the DBMS is unable to extend the segment is generated.

A typical Oracle Database DBMS usage scenario implies that the administrator monitors the alert log status and takes all required actions to prevent any downtime in the information system operations. To add a datafile to the tablespace, run the following command:


A tablespace with the bigfile option can also be created, but in this case the administrator would not be able to manage space allocation for Oracle Database datafiles (the tablespace with the bigfile option can only have a single file). To create a tablespace with the bigfile option, run the following command:


Remember these specifics when you are loading large infobases. When the infobase to be loaded exceeds 32 GB, you have to extend the tablespaces before loading the infobase. If you create a tablespace with the bigfile option before loading the infobase, the limit of 32 GB shifts to the next limit, which is 33 TB (terabytes).