Installing and Configuring Oracle - Intergraph Smart Engineering Manager - 11 - Installation & Upgrade - Hexagon

Intergraph Smart Engineering Manager Installation and Upgrade

Language
English
Product
Intergraph Smart Engineering Manager
Search by Category
Installation & Upgrade
Smart Engineering Manager Version
11

Because system configurations, database software, and individual company standards vary, use this section as a checklist instead of step-by-step instructions. Consult your Oracle software documentation for information as to which versions of Oracle database can be used with which versions of the Windows operating system.

For specific questions about Oracle configurations, please contact PPM Smart Community.

Oracle Instances

If one server hosts the databases of several products, Intergraph recommends that each product's database be a separate instance, each of which can host multiple plants.

The advantage of placing each product's database in its own instance is that only the affected application will be off-line during backup, performance tuning, and other database maintenance activities. Additionally, global tuning parameters that apply to one instance can be tailored to the specific product requirements.

According to Oracle documentation, the only limit to the number of instances you can have on any machine is the availability of resources. However, the number of instances on one database server should be minimized, because each additional instance places additional load on the server.

Each instance adds redundant tablespaces, rollback segments, background processes, and memory requirements for each SGA (System Global Area). For this reason, you should start by putting the database of one product for several plants into a single instance. Then, when the number of plants increases, or a plant becomes very large, consider separating the database into new instances, adding server memory, or even adding database servers.

  • We recommend installing and configuring Oracle locally, not by remote desktop connection.

  • Path names for tablespaces in Oracle must be no greater than 60 characters.

  • Smart Engineering Manager does not support encrypted tablespaces.

  • Oracle recommends that database activity on the database server should consume no more than 50 percent of the available memory.