Creating the Database Schemas

To create the empty database schemas (with tables to be populated during installation):

1. Set up the required data, index, and CLOB tablespaces for the PPM database schema.

   Tip: Even though a fresh installation of PPM typically requires less than 1 GB of database space, its size could sharply increase with time, especially if you choose to store attachments in the database. For an accurate estimation of your DB space requirement on the long term, contact Micro Focus Software Support.

   Use locally-managed SYSTEM tablespaces with automatic segment-space management.

   Note: Locally-managed tablespaces eliminate extent fragmentation and provide better performance than dictionary-managed tablespaces.

2. Create each tablespace as shown in the following example for a data tablespace.

   CREATE TABLESPACE <PPM_Data>

   datafile <'/u0/oracle/oradata/G1120/ppm_data01.dbf'>

   size <1024m>

   AUTOEXTEND ON MAXSIZE <4096m>

   EXTENT MANAGEMENT LOCAL AUTOALLOCATE

   SEGMENT SPACE MANAGEMENT AUTO;

   Note: Oracle has the default TEMP tablespace, which you can resize to improve performance.

The PPM Server requires two separate database schemas to store application data. A DBA can create these schemas before installation. Creating database schemas requires privileges that a DBA might not want to grant to a PPM administrator. Either create the database schemas before installation or make sure that a DBA is available during installation.

To create the database schemas and grant the permissions between them:

1. Unpack the PPM installation bundle as outlined in Install PPM with Oracle.

   The <PPM_Extract>/ppm<version> directory is created. The <PPM_Extract>/ppm<version>/sys and <PPM_Extract>/ppm<version>/system directories contain the scripts required to create the database schemas.

2. Run the script CreateKintanaUser.sql against the database into which you plan to install PPM

   The script is located in <PPM_Extract>/ppm<version>/system. It prompts for a user name and password, and the tablespaces that the PPM database schema are to use.

   sh> sqlplus system/<Password>@<SID> \

   @CreateKintanaUser.sql \

   <PPM_Username> \

   <Password> \

   <Data_Tablespace> \

   <Index_Tablespace> \

   <CLOB_Tablespace>

3. To enable the PPM database user to create views and synonyms in the RML schema, connect to the database that contains the RML schema, and then issue the following SQL statements:

   grant create any synonym to &KNTA_USERNAME;

   grant create any view to &KNTA_USERNAME;

   grant drop any synonym to &KNTA_USERNAME;

   grant drop any view to &KNTA_USERNAME;

   grant comment any table to &KNTA_USERNAME;

4. Run the CreateRMLUser.sql script, which is located in the /system directory.

   The script prompts for a user name and password for the Reporting Meta Layer (RML) schema, tablespace information, and the PPM database schema user name. The script creates the RML schema and establishes the permissions between the RML and the PPM database schema.

   Note: Because the RML schema contains only views (and no physical objects), it does not require a separate tablespace.

   sh> sqlplus system/<Password>@<SID> \

   @CreateRMLUser.sql \ 

   <RML_Username> \

   <RML_Password> \

   <Data_Tablespace> \

5. As the SYS DBA user, run the GrantSysPrivs.sql script, which is located in the <PPM_Extract>/ppm<version>/sys directory.

   This script grants the privileges that the PPM Server requires.

If you created the schemas before installation, select Please use existing schemas when prompted during installation. Supply the same values as those used in this procedure (that is, the values <PPM_Username> and <RML_Username>).