Axional Studiouses several databases where store the configuration and the applications. This guide shows how to install these catalog databases.
Axional Studio application server requires a database server where store the startup databases (configuration data and application metadata).
The configuration data includes the information regarding the application environment.
The applications metadata are the programming repository.
On the database server, it must exists the following dbspaces where allocate the configuration databases:
|wic_conf||d_conf||data-dbspace specific for data of the wic_conf database||d_conf_00||512MB|
|s_conf||smart-blobspace specific for the clobs and blobs of the wic_conf database||s_conf_00||512MB|
|wics||d_wics||data-dbspace for the data of any other dictionary of databases (even wic_admin)||d_wics_00||1024MB|
|s_wics||smart-blobspace for the clobs and blobs of any other dictionary of databases (even wic_admin)||s_wics_00||1024MB|
The name of chunks and its size can be different from this definition. The name of chunks is not relevant and the size will depend on the intended content.
2 Application database dictionaries
Axional Studio web applications you need to load the appropriate dictionary database,
according to application natures, into the database server.
|wic||System database for dictionaries (wics)||32MB|
|wic_admin||System database for wic_conf||25MB|
|wic_iges||Purchases, sales and distribution.||280MB|
|wic_icrm||Customer relationship management||32MB|
|wic_itra||Transportation management system||15MB|
|wic_iman||Computerized maintenance management system||12MB|
The next schema shows the dictionaries relationship.
- The metadata to handle the wic_conf database forms is defined in a database dictionary called wic_admin.
- The wic database stores the metadata for the whole set of other dictionaries.
- The rest of wics databases store the metadata and programs to handle the application forms.
2.2 The wic_conf database
This database contains critical information needed by the server to operate, including users and their properties, database servers, database users definition... Many servers sharing the same configuration are considered a cluster.
Within the wic_conf database resides the environment configuration, logical topology and the definitions of rights granted for each user. Key definitions are the users and their roles, the company databases and their permissions. The database wic_conf is not imported. It is created from the setup utility. In order to this step, it is necessary to have already installed the wic and the wic_admin databases on your server.
3 Import databases
Your provider will provide you with the databases corresponding to your implementation.
Before using the setup tool, a minimum preparation is needed in your database server. This will include the creation of the appropriate dbspaces and loading the database dictionaries.
- Select your primary database server.
- Ensure that exists a bts VP.
- Import the wic dictionary database.
- Import the wic_admin dictionary database.
A bts VP is needed to import the catalog databases. You can check it executing the command:
onstat -g sch | grep bts
If there is not the VP then edit the $ONCONFIG file and add the following line (close to the another VPCLASS definition):
This actions requires a restart of database service.
To import each database use the command
dbimport. The dictionaries wics will be allocated at the d_wics dbspace.
It is necessary to set the environment variables values:
CLIENT_LOCALE=en_us.UTF8 DB_LOCALE=en_us.UTF8 DBMONEY=.
To import the required databases execute the following commands:
dbimport -ci wic -d d_wics
dbimport -ci wic_admin -d d_wics
Execute the update statistics.
echo "update statistics low drop distributions" | dbaccess wic
echo "update statistics low drop distributions" | dbaccess wic_admin
Execute this command to change to unbuffered logging the databases.
ontape -s -U wic -t /dev/null
ontape -s -U wic_admin -t /dev/null
To import the rest of dictionaries iterate the same command by replacing the argument dbname with the corresponding name of database:
dbimport dbname -d d_wics
3.1 Database renaming
If in your database server already exists a databases named wic or wic_admin it is necessary to rename the new databases. Naming must be unique. For example you can rename the wic database to wic17 and wic_admin database to wic17_admin.
The following example shows a way to change the database name. In this example, assume that the dbexport unloaded the database wic_admin into the directory /work/exports/wic_admin.exp. Thus, the data files (the .unl files) are stored inside the /work/exports/wic_admin.exp, and the schema file is /work/exports/wic_admin.exp/wic_admin.sql.
- Change the name of the .exp directory. That is, change /work/exports/wic_admin.exp to /work/exports/wic17_admin.exp.
- Change the name of the schema file. That is, change /work/exports/wic_admin.exp/wic_admin.sql to /work/exports/wic17_admin.exp/wic17_admin.sql. Do not change the names of the .unl files.
- Import the database with the following command:
dbimport -i /work/exports wic17_admin
Please notice that the schema of the wic_conf database assumes the standard names for wic and wic_admin. Thus, changing their names will also involve declaring the new ones inside the wic_conf database.
Here the table [wic_dbms_objects] indexes the set of available database. For wic or wic_admin it is necessary to populate their new names in the field obj_physname.
|Importing a catalog database||9799 - User Defines Routine (bts_createstorage) VP context switch failed||It is needed to configure a bts VP. Edit the $ONCONFIG file and add the following line (close to the another VPCLASS definition):
This actions requires a restart of database service.