|
|
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. Note: You must install Oracle 32-bit client in such a way that the installation of the ENOVIA V5 code communicates with 32-bit Oracle client and not directly with 64-bit Oracle, if you are using an Oracle 64-bit database server. |
|
|
Setting Up a Database Using IBM DB2 Universal DatabaseYour 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 UtilityBefore 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". |
|
|
|
About LOGFILSIZ ParameterIf you use the database configuration parameters documented above, during an ENOVIAV5VPM 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 error 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. |
|
|
|
DB2 Performance ConsiderationsENOVIAV5VPM 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 ENOVIAV5VPM 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. |
|
|
|