|This section explains how to
create a database for the ENOVIA V5 server using the IBM DB2 Universal Database
and Oracle products.
For DB2 and Oracle databases, you must have at least 150 Megabytes of free disk space to successfully install the ENOVIA V5 tablespaces and data files. Whatever additional disk space you will need depends on the size of your database.
Setting Up a Database Using IBM DB2 Universal Database
Your computer needs to be a DB2 server.
To find out whether the DB2 software on your computer is configured as a client or a server:
Modifying the Stack Reserve Using the db2hdr Utility
Before proceeding, make sure the DB2 server is not running. To
check if it is already running, select
If the DB2 server is running, stop it, then make sure that there is no
db2sysc process running. Then, increase the default stack size for
the db2syscs.exe using the db2hdr utility as follows by,
for example, selecting
You must then restart the DB2 server and create at least one database before starting the installation.
To get help for db2hdr, run the utility without arguments:
To check the current values of the db2 stacks, run the utility with one argument (full path for db2syscs.exe):
Once you have modified the stack reserve, start the above-mentioned DB2 services before proceeding. You can also configure the services to make sure that they are always running. To do so, select a service then right-click and choose "Properties" on the contextual menu, then set the "Startup type" to "Automatic".
A progress dialog box informs you that the database is being created:
You can ignore any prompt which may appear prompting you to catalog the database once created.
A message informs you that the database has been successfully created, and prompts you to run the Configuration Advisor to tune the database:
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 there 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 256 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.
For Oracle databases, you must have at least 150 Megabytes of free disk space to successfully install the ENOVIA V5 VPM tablespaces and data files. Whatever additional disk space you will need depends on the size of your database.
For more information about Oracle administration, see the Oracle10 Server Administrator's Guide.
|Your computer needs to be an Oracle server, and the Oracle
server must be running.
One way of finding out whether the Oracle server is running on your computer (if you have already created a database) is to:
If not, start them before proceeding.
You can also configure the services to make sure that they are always running. To do so, a service then right-click and choose "Properties" on the contextual menu, then set the "Startup type" to "Automatic".
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:
If you select
You are now ready to install the ENOVIA V5 VPM server software.
Problems with Fetched Query Function in ENOVIA V5 VPM
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
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):