Database Server Installation

Create the APM Oracle Schema on the APM Database Server.

1. On the APM Server machine, in the APM distribution package, navigate to the Database folder.
2. Open the file MI_DB_MASTER_<version>.zip, and then extract the contents of the file <version>.zip to a folder on the C: drive.
3. Open the file <version>.zip, and then open the subfolder _Setup\NewInstall\Oracle.

   This folder contains the extracted files that will need to be run by the database administrator (via the remaining steps). The database administrator will need the following three files, as well as access to the remaining instructions in this topic:

   • CRT_MI_CONNECT_ROLE.SQL
   • CRT_MI_USER.SQL
   • MI_V4030070.DMP.ZIP
   1. Locate and run the script CRT_MI_CONNECT_ROLE.SQL.
      This script creates the APM role (MI_CONNECT_ROLE), which contains several of the Oracle privileges that are necessary to run the APM applications. This script does not require any parameters. You will need to run this script one time per database.
   2. Locate and run the script CRT_MI_USER.SQL.
      This script creates the Oracle user, and then grants to the user the role MI_CONNECT_ROLE that you created in the preceding step.

      The schema is created. For example, if you were to define the parameters through the command SQL> @CRT_MI_USER MERIDIUM_PROD MERIDIUM_PROD 1000M Meridium_DATA, it would automatically:

      • Create a user named MERIDIUM_PROD.
      • Set the password for the user to MERIDIUM_PROD.
      • Set the default tablespace for the user to MERIDIUM_DATA.
      • Grant 1GB of quota on the default tablespace.

      Note: This example assumes that the MERIDIUM_DATA tablespace already exists.
4. Import the Oracle schema that you created in the preceding steps. To do so:
   1. On the APM Database Server machine, locate the file MI_V4030070.DMP.ZIP, and then extract and import the contents.
   2. Update the schema statistics.
5. Log in to SQL*Plus (or equivalent) as the schema owner, and then run the following command: SQL> EXEC MI_DDL.CRT_SIDX_SI_MI_GEOD_GD
   The spatial/geo index for the database is imported.

1. APM requires mixed-mode authentication for SQL Server installations. The documentation and scripts supplied by GE Vernova assume that the SQL Server instance allows mixed-mode authentication.
2. The APM database must be owned by the SQL Server login referenced in the APM data source. Being a member of the SQL Server db_owner role is not sufficient. GE Vernova provides a script to properly configure the SQL Server database for use with APM.
3. The database supplied by GE Vernova (via a .bak file) was created with the SQL Server collation Latin1_General_CI_AS.

1. Open a SQL Server Management Studio query window that is connected via a privileged login.
2. Open the file MI_SQL_DB_Configure.sql, and then copy its contents into the SQL Server Management Studio query window.
3. Set the @dbname variable to the name of the APM SQL Server database that you created.
4. Execute the edited script.
5. As needed, use SQL Server Management Studio to modify the password. These are the same login credentials that will be used when you create the APM data source that will connect to this database.
6. Create the custom server-level error messages, which are required by the APM system. These error messages must be created at the instance level. Creating them requires a privileged login assigned to either the System Administrator (sysadmin) or Server Administrator (serveradmin) fixed server roles. To create the APM error messages:
   1. Make sure that you are connected to the Database Server with SQL Server Management Studio as a System Administrator or Server Administrator user
   2. Execute the stored procedure MI_ERRORS_CRT_ALL_MSGS. This procedure was supplied with the APM database and can be executed by using the command exec <databasename>..MI_ERRORS_CRT_ALL_MSGS, where <databasename> is the name of the database you created in the preceding steps.