Install database software on the database server - SmartPlant Foundation - IM Update 47 - Installation & Upgrade

Installation and Setup for SmartPlant Foundation Application Server

Language
English
Product
SmartPlant Foundation
Search by Category
Installation & Upgrade
SmartPlant Foundation / SDx Version
10

When setting up a dedicated database server, see the documentation delivered with your database software for instructions on installing and setting up the database.

Oracle notes

  • For important internationalization information, see the Oracle encoding instructions in Create the database instance.

  • On Oracle database servers, use Oracle Net Configuration Assistant to create a database alias that SmartPlant Foundation can use to communicate with the database.

  • When installing Oracle on a Windows server, you must manually register the data access DLL to the .NET Global Assembly Cache (GAC). Run the following two commands from a "Run as administrator" command prompt, replacing <ORACLE_HOME> with the Oracle installation folder, usually C:\app\<oracle_user>.

    SET ORACLE_HOME=<ORACLE HOME>\product\<Oracle version>\x64

    <ORACLE_HOME>\product\<Oracle version>\dbhome_1\odp.net\bin\4\OraProvCfg.exe /action:gac /providerpath:<ORACLE_HOME>\product\<Oracle version>\dbhome_1\odp.net\bin\4\Oracle.DataAccess.dll

Beginning with Windows 10 and Oracle 12.1.0.2, Microsoft and Oracle will enforce the Internet Host Table Specification RFC 952 which mandates that component hostname labels may contain only alphanumeric characters. Hostnames using underscores (‘_’) are not allowed. For more information, refer to Oracle Support Articles 1603775.1 and 1957895.1 and Microsoft KB 101785.

All domain verified user names and passwords must use ASCII7/English characters. Oracle does not support non-ASCII / English characters in domain user names or passwords and will not work. In addition, do not use the @ character in an Oracle password. This limitation applies only to Oracle, not Hexagon.

Microsoft SQL Server notes

  • The READ_COMMITTED_SNAPSHOT database option should be set to ON.

    To set this option, ensure there are no user connections to the database and then run the following SQL command, replacing Databasename with the name of your database:
    ALTER DATABASE Databasename SET READ_COMMITTED_SNAPSHOT ON WITH NO_WAIT;

  • The following is a list of recommendations for the TEMPDB system database:

    • TEMPDB should be set up on a dedicated disk, not shared with the user or system databases; if it is not, it may need to be moved to a dedicated disk to reduce I/O contention.

    • The total number of datafiles allocated to TEMPDB should equal the number of CPUs on the server and should not exceed 8.

    • The datafile size is recommended to be set to at least 250 MB.

    • The auto-growth option should be switched off for datafiles.

    • TEMPDB should be monitored on a regular basis to check the space usage of datafiles.

  • For SQL Server databases, there are internationalization considerations concerning the collation settings you specify. All databases participating in the SmartPlant Foundation environment must use the same collation settings to ensure proper functioning between SmartPlant Foundation components.

  • It is suggested to use SQL_Latin1_General_CP1_CI_AS as the standard collation setting for SmartPlant Enterprise Integration environments.

  • The default case sensitivity setting for SQL Server databases must be set to insensitive. All SmartPlant Foundation product databases are supplied and certified in this format.

    If the default case sensitivity is changed from case insensitive, you cannot import databases using Server Manager.