5.2.1. Adding a new infobase

5.2.1.1. General information

To add a new infobase to the list, click Add…. A dialog box will be displayed.

Fig. 25. Choosing the infobase adding mode

Select Create infobase to create an infobase based on the template, or create an empty infobase.

Click Next>. A dialog box will be displayed.

Fig. 26. Selecting the configuration to add

If you choose to create an infobase from a template, select the source template from the list.

Click Next> to specify the infobase name and location type.

Type in the infobase name. This name will be displayed in your infobase list. Maximum infobase name length is 255 characters. You are free to provide a long descriptive name for your infobase. The infobase name must be unique in the infobase list.

NOTE. Creating multiple infobases with the same database connection string is allowed. This might be required when you need to access an infobase using different clients without changing properties of the infobase.

Creation of an infobase in file mode is described in the next section.

5.2.1.2. Creating an infobase in file mode

To create an infobase in file mode, select the infobase location type as shown in fig. 27.

Fig. 27. Selecting file mode for an infobase

Specify the directory where the infobase will be located. If a non-existent directory is specified, it will be created automatically when 1C:Enterprise starts.

Fig. 28. Specifying infobase directory and language

Click Select to open the standard dialog box for selecting an existing directory.

NOTE. The directory name must meet the RFC 2396 requirements described in section 2.4.3 Excluded US-ASCII Characters (https://datatracker.ietf.org/doc/html/rfc2396.html). You cannot use the following characters in the directory name: <, >, #, %, ", {, }, [, ], |, \, ^, `, and characters with codes: 0-31 and 127.

If you choose to create an empty infobase, select the infobase language in the Language field. Language rules will regulate storing and sorting of data in the infobase. If you have selected a template, the language field might not be displayed.

Click Next > to display the startup settings page (see article Infobase startup parameters).

If an empty infobase was created and configuration files are not found in the specified directory, the window for selecting the infobase creation mode will also be displayed when you select 1C:Enterprise run mode. If you choose to create an infobase from a template, the infobase is created based on this template.

You can create a database in different version formats: 8.2.14 and 8.3.8. By default, the database is created in 8.3.8 version format. To change the default format, edit the conf.cfg file. For more information, see article conf.cfg. To convert the 1Cv8.1CD file between formats, use the cnvdbfl utility. For more information, see article Conversion utility cnvdbfl.

5.2.1.3. Creating an infobase in client/server mode

5.2.1.3.1. General information

To create an infobase in client/server mode, select the type of infobase location as shown in fig. 29.

Fig. 29. Creating an infobase on server

An infobase in client/server mode is described by two parameters:

Address of 1C:Enterprise server cluster
Infobase name

As noted above, the 1C:Enterprise server cluster address consists of the main server name and the number of the network port used by the cluster manager (for example, Test_Server:1541). If the cluster manager uses the default network port (1541), you can skip it and specify the server name only. The infobase name is unique within the 1C:Enterprise server cluster.

Fig. 30. Creating a new infobase

The infobase name in a cluster is not case-sensitive (it is also true for all technical operations, including functionality assignment rules).

NOTE 1. If a cluster with several main servers is used, the list of the main servers can be specified directly in the 1C:Enterprise server cluster field as Server1,Server2:Port,Server3 (no spaces are allowed). This format is convenient, for example, when creating a list of shared infobases.

NOTE 2. The database name must meet the RFC 2396 requirements described in section 2.4.3 Excluded US-ASCII Characters (https://datatracker.ietf.org/doc/html/rfc2396.html). You cannot use the following characters in the database name: <, >, #, %, ", {, }, [, ], |, \, ^, `, and characters with codes: 0-31 and 127. There might be additional requirements depending on the used DBMS.

Information characteristics entered in this window and required for infobase creation depend on the DBMS used. Requirements by DBMS are provided in the following sections.

5.2.1.3.2. Microsoft SQL Server

DBMS type: Microsoft SQL Server.
Database server: server name. It can be specified based on the computer name if a single instance of the server is installed on the computer or based on the name of the specific instance if multiple server instances are installed on the computer. For example, Server/instance.
If 1C:Enterprise server and Microsoft SQL Server are installed on one computer and Native Client is installed for the Microsoft SQL Server, you can use the SHARED MEMORY protocol to establish connection between the servers. To do this, add lpc: prefix before the Microsoft SQL Server name. The DBMS server name will look as follows: lpc:Server/instance.
Database name: the database name begins with a Latin letter or an underscore (_). The database name may contain Latin letters, digits, as well as _ and $ characters. Maximum length of the name is 63 characters. No spaces are allowed in the name. The database name cannot match any reserved word of server database query language.
Database user: name of the database server user on whose behalf the database is accessed. To be able to edit structure of the selected database, the user must be the database server administrator (sa) or database owner. In the latter case, the user must have permission to read master database as well as full access to tempdb database. Moreover, the user must have the fixed server role assigned (processadmin or sysadmin).

IMPORTANT! When using Microsoft SQL Server 2014, you need to set TRACE FLAG 4199 for the database in use. If TRACE FLAG is not set for the entire database, it is attempted to set TRACE FLAG for each connection to the DBMS on behalf of the Database user. If the user does not have sufficient rights for this action, an error will be displayed. In this case, specify a user with database server administrator rights (sa) as the database user or manually set TRACE FLAG 4199 for the database.

User password: password of the user on whose behalf the database is accessed.
Date offset: 0 or 2000. Determines the number of years that is added to dates when storing them to Microsoft SQL Server database and subtracted when retrieving the dates. This parameter depends on the specifics of date storing procedure implemented in Microsoft SQL Server. DATETIME type used in Microsoft SQL Server allows you to store dates from January 1, 1753, to December 31, 9999. If you need to store the dates that are earlier than that, set Date offset to 2000. If you do not expect to store such dates, set Date offset to 0. This value cannot be changed after the infobase is created.

IMPORTANT! If an application uses accumulation registers or accounting registers, set Date offset to 2000. If you have already set Date offset to 0 when creating the infobase, export it into a file (see article Exporting infobase to file), create another infobase with Date offset set to 2000, and import the content of the exported infobase into it (see article Importing infobases from file).

5.2.1.3.3. PostgreSQL

DBMS type: PostrgeSQL.
Database server: server instance name. If you specify a network port that differs from the default port, specify it using the port keyword: <instance_name> port=<port_number>;. For example: localhost port=6432;.
Database name: the database name begins with a Unicode 3.2 character or an underscore (_). The database name can contain Unicode 3.2 characters, an underscore (_), and a dollar sign ($). Maximum length of the name is 63 characters. No spaces are allowed in the name. The database name cannot match any reserved word of server database query language.
Database user: name of the database server user on whose behalf 1C:Enterprise accesses the database. The user must have the SUPERUSER privileges.

5.2.1.3.4. IBM Db2

DBMS type: IBM Db2.
Database server: server instance name. If any non-default database server instances are installed on the computer, specify the name of the installed IBM DB2 instance after a slash. Example: computer/db2name.
Database name: the database name must be unique within its location in the directory. In the DB2 database manager for Linux, this location is a directory, and in Windows, this is a logical drive. The database name must begin with a Latin letter. Further, it can contain Latin letters and digits. Maximum length of the name is 8 characters.
Database user: name of the database server user on whose behalf 1C:Enterprise accesses the database. The user needs to have the CREATEDB or SUPERUSER privileges, or to be the database owner. Maximum length of the username is 8 characters.

After creating a new infobase, we recommend that you configure the database settings using Configuration Advisor:

5.2.1.3.5. Oracle Database

DBMS type: Oracle Database.
Database server: server instance name. When creating an infobase, specify TNS name as the database server name. Enter the database server name in format //DB_server_name/service_name (or similar).
Database name: database in 1C:Enterprise terms matches data schema in Oracle Database terms. When you create an infobase in 1C:Enterprise, an infobase user and their data schema are created in Oracle Database. Name of the data schema must only contain the Latin letters, digits, and underscore(_). The database name must begin with a Latin letter. Maximum name length is 30 characters.
Database user: when creating an infobase in 1C:Enterprise, specify the user on whose behalf the database will be accessed. Specify a user that has DBA rights (for example, SYSTEM) if the data schema is created by the system. Starting from version 12.2, this user must be granted the CREATE ANY TABLE and EXECUTE ANY PROCEDURE privileges. Specify another user if the data schema is already created by the Oracle Database administrator. This can be the user whose data schema is used for 1C:Enterprise, meaning the Database name and Database user can be identical.

Notes on rights required

If an existing data schema is used, the user on whose behalf the database will be accessed does not need the DBA right. The user may have the following rights instead of DBA:

CREATE SESSION
CREATE PROCEDURE
CREATE TRIGGER
CREATE SEQUENCE
CREATE TABLE

Instead of granting each right to the user, you can assign the following roles to them:

CONNECT
RESOURCE

If you plan to terminate sessions from the management console of the 1C:Enterprise server cluster, the user on whose behalf the database is accessed needs the ALTER SYSTEM access right.

Besides, the following tablespace quotas must be granted to the user: V81C_DATA, V81C_INDEX, V81C_LOB, and V81C_INDEX_BIG (if available).

To grant access rights, you can use the following example:

create user <username> identified "<password>";
grant create session to <username>;
grant create table to <username>;
grant create trigger to <username>;
grant create sequence to <username>;
grant create procedure to <username>;
grant alter system to <username>;

alter user <username> quota UNLIMITED on v81c_data;
alter user <username> quota UNLIMITED on v81c_index;
alter user <username> quota UNLIMITED on v81c_lob;

Notes on password expiration

When using Oracle Database 11 with the default settings, the password expires in 180 days. In 180 days, the following error might occur: No database server is found. DBMS error: ORA-28002: password expires in 7 days. In this case, change the password using DBMS functionality:

Run the SQL*Plus utility.
Connect to the database.
Execute the ALTER USER <UserName> IDENTIFIED BY <Password> command.

Remember that 1C:Enterprise server stores passwords in the settings file and the next authentication attempt will use the old password. To avoid this, you can specify the old password when executing ALTER USER command, meaning the password will not be changed but only prolonged.

To disable password expiration, refer to documentation for the relevant version of Oracle Database.

5.2.1.3.6. General parameters

User password: password of the user on whose behalf the database is accessed.
If the Create database if none present check box is selected, the database will be created if the specified database server does not contain the database with the specified name. If this check box is not selected, the database will not be created.
Value of Language (Country) parameter is selected from the list and determines the set of regional settings that will be applied to the infobase. Later, it can be changed in Designer. If an infobase is created based on a template that includes the infobase dump file (*.dt), the Language parameter is not displayed because the language information is already present in the infobase dump file.
If the Disable execution of scheduled jobs check box is selected, execution of scheduled jobs will be disabled in the created infobase. If this check box is not selected, any scheduled jobs will be started immediately upon establishing server connection.

5.2.1.3.7. Creating a database

If all parameters are specified correctly, the following actions are performed:

Attempt to connect to the specified database on the specified database server using the specified user parameters is made.
If the database is unavailable and the Create database if none present check box is selected, an attempt to create the database is made. When creating an infobase in Oracle Database, the user is created with the same username and password. When the user is created, their account is locked. When connecting to the Oracle Database, the 1C:Enterprise server uses username and password specified during creation of the infobase.
If an existing 1C:Enterprise infobase is found in the database, an attempt to connect to this infobase is made. If no such infobase is detected, a new infobase is created. If a template was specified in parameters while creating the new infobase, the template will be applied upon initialization.

For more information on setting infobase startup parameters, see article Infobase startup parameters.

5.2.1.3.8. Simultaneous use of a database by several infobases

When creating an infobase on the 1C:Enterprise server, the same database can be assigned for several infobases. However, the structure of internal cluster data implies that one set of internal data corresponds to one database. Simultaneous use of several internal data instances with one database breaks their logical integrity.

When several infobases use the same database simultaneously, the following is disabled:

Infobase locks (in particular, running two instances of Designer may lead to irreparable configuration damage).
Object locks.
Lock manager.
Getting timestamps in real time.
Other tools that use separated data stored by the cluster manager.

Simultaneous data modification in such conditions might lead to irreparable data damage. Data read from the database might also be unreliable.

That is why it is not recommended that you use one database with several infobases.

At the same time, simultaneous connection of several infobases to one database might be useful for configuration debugging and error analysis in configuration and platform. That is why connecting several infobases to one database is not directly prohibited in 1C:Enterprise. However, when you use this feature, use the following precautions:

Parallel editing of a database from several infobases might lead to irreparable database damage.
When several infobases read the same data simultaneously, results might be unreliable for all infobases if at least one infobase modifies or locks the data in any way.