|This section explains how to create a database for ENOVIA V5 VPM using DB2 and Oracle.|
A DB2 server needs to be active, and you need to create at least one database before starting the installation.
To start the DB2 server, enter the commands:
where "db2adm" is the DB2 administrator logon, then:
To check whether a DB2 server is already running, enter the command:
To create a simple database, enter the command:
By default, the database is created in the home directory of user "db2adm".
To stop the DB2 server, enter the command:
where "db2adm" is the DB2 administrator logon, then:
Setting Up Databases on DB2
Using the Control Center
You can create databases using the DB2 Control Center which works the same way as already illustrated on Windows as described in Setting Up Databases for the ENOVIA Version 5 Server on Windows. To start the Control Center, export your display then, still logged on as database administrator, enter the command:
Using a Shell Script
Experienced administrators may prefer to use a shell script to create databases. The default installation illustrated in this guide was based on a DB2 database created using the shell script illustrated below.
Pay particular attention to the end of the shell which contains an example of how to set up database parameters properly for the new instance you are creating:
These values are the minimum recommended values which will allow normal use of ENOVIA V5 VPM at installation. For example, STMTHEAP is set to 16000.
This is the whole shell:
Note about the LOGFILSIZ Parameter
If you use the database configuration parameters documented above, during an ENOVIA V5 VPM installation, the ENOVIA database will be set up correctly, and the default security mask will be imported. However, if you neglect to set the LOGFILESIZ parameter correctly, the default security mask import step may fail.
If a problem with the default mask is detected, the following error message:
means that the mask was not created, but no problem occurred during the commit phase. It may be because the database was not created using the LOGFILSIZ parameter. In this case, update the database configuration using the correct LOGFILSIZ parameter value and reimport the mask using the command VPMPeopleUpdate -m as explained in "People, Organization and Security Tools" in your Enterprise Architecture Administration Guide.
Running a Database and Vault Server on the Same Workstation on AIX
When you have a vault server and a DB2 database running on the same workstation on AIX, the number of connections for the vault server database connection pool (connections between the java vault server process and the database) is limited. To bypass this problem, you must catalog your database using the following commands:
If you already cataloged your database, but not exactly as above, uncatalog it then catalog it again as above.
Solaris server - Kernel Parameters
The DB2 server may crash while ENOVIA V5 VPM is running, if the Solaris kernel parameters are not updated as per the DB2 installation instructions.
Please refer to the DB2 Quick Beginnings for Unix for the complete list of parameters to modify, as the required settings depend on the amount of memory available on your server.
DB2 Performance Considerations
ENOVIA V5 VPM has been developed to work optimally with DB2. However to take full advantage of the hardware available, a minimum amount of configuration may be necessary.
The most important considerations consist in allocating enough BUFFERPOOL space, and in updating the database statistics by running the db2 RUNSTATS command.
Note: each ENOVIA V5 VPM installation may be unique due to a specific hardware configuration and system load (and that is no universal configuration that will be optimal). However, it is recommended to start with a simple configuration and tune it over time, using the input provided by the System Monitor tool.
Refer to the DB2 System Monitor Guide and Reference for information on monitoring the performance of a DB2 database.
Note: to avoid errors occurring when saving parts, we recommend that you increase DB2 database APP_CTL_HEAP_SZ. The default is 128. Increase it to 512 to avoid the problem.
This section explains how to create a database for ENOVIA V5 VPM using Oracle. An Oracle server needs to be active, and you need to create at least one database before starting the installation.
Before launching the ENOVIA V5 VPM installation process on Oracle, the following operations must be performed:
Note: because the installation on a remote database does not allow the creation of a new ENOTBS tablespace for storing ENOVIA V5 VPM tables, create it beforehand using the following procedure:
Oracle Library Error
The following error may occur:
This error will occur with the ENOVIA VPM Product Editor (VPC product) installed on Oracle 10 level database unless certain steps are taken before ENOVIA V5 VPM is activated. The installation of ENOVIA V5 VPM will work but both the ENOVIA VPM Product Editor client and VPMPeopleEdit will fail.
The following steps are to be taken to correct a bug in Oracle 10:
Your workstation needs to be an Oracle server, and the Oracle server must be running.
For reasons of general query performance (response time improvements of up to 70 %), it is important to regularly perform an analysis of the database. Due to the naming convention adopted by ENOVIA (differentiation by capital and lowercase letters) the procedure DBMS_UTILITY.ANALYZE_SCHEMA() cannot be used. The following routine should be used in its place and should be executed in the VPM schema (the variable <schema> found in the below script):
The above script should be added to a file, for example creana.sql, and executed in an SQLPLUS session corresponding to a user having access to the database schema to be analyzed. The frequency with which the above code should be executed depends on the volume of updates to the database (commands INSERT, UPDATE, DELETE).
For more information about Oracle administration, see the Oracle10 Server Administrator's Guide.
The way DB2 and Oracle databases are configured may cause problems with some ENOVIA V5 VPM functionalities (for example, fetched query).
This is due to the fact that the databases are configured to sort data according to the locale. The problem is that the result obtained after a sort from DB2 is different from a sort with Oracle which is different from a sort in the server. The only combination that actually works is to have everybody do a binary sort.
Therefore we strongly recommend configuring the database as explained below.
NOTE: There is no absolute emergency to do it. The only impact is weird behavior of the fetch-query when using characters out of the "a-z 0-9" range.
When creating the database, add the "COLLATE USING IDENTITY" option to your CREATE DATABASE statement.
With DB2, it is not possible to modify this parameter once the database has been created. This means that the only way to change it afterward is to do a full export, drop the DB, recreate it with the proper parameters and do a full import.
Note : A backup/restore won't work as the old parameters will be restored as well.
With your own database, you need to go through the export/import process. We recommend the following:
Add the two following parameters to the initSID.ora configuration file (SID stands for the Oracle instance name):