Previous Topic  Next Topic

Initializing the Database System as a Non-admin Database User

Logi Report Server needs to connect to a server database and fetch and write data from the database tables at runtime. Database initialization is to create the required tables in the database. Usually, Logi Report Server automatically creates database tables the first time it is started. The database information that Logi Report Server uses is defined in the dbconfig.xml file. However, if the user ID defined in this file does not have the permission to create tables in the database, Logi Report Server will fail to complete the operation. In this case, you will need another user, such as the database administrator who has the relevant permissions, to create a set of empty tables in the user's schema using the provided SQL files in <install_root>\script_files.

In the case when a database administrator (DBA) does not want to assign an admin database user to Logi Report Server for connecting to the database, Logi Report has to use a non-admin database user to initialize the database system. The database initialization will then have to be divided into three phases:

1. The DBA creates new database tables using script files stored in <install_root>\script_files\create_new_tables.
2. Customer starts Logi Report Server using a non-admin database user. In this phase, the data in the old version's database tables if they exist will be migrated to the new tables created in the first step. If the data migration happens, you will be able to see a record of it in the debug file.
3. The DBA deletes tables of the old version in the database using script files stored in <install_root>\script_files\delete_old_tables.

If it is a newly installed Logi Report Server connecting to a database that does not already contain the required tables, only the first step is required.

The following table lists the script files used for different purposes:

Previous Topic  Next Topic