Page History

...

1. In the User Name field, type a new Precise user name, or click the drop-down menu to select an existing Oracle schema user name. When using a Oracle containerized database as the PMDB, it is recommended that the PMDB is set up on a PDB and not on the root container . This can be done by using the Service Name checkbox in the database details screen of the framework installer. This is the name of the Precise user created in the Oracle instance to hold the PMDB schema. You can create a new Precise user, or select an existing user from the list.
2. Type a new Password for the new user, or an existing password if you have chosen an existing user.
3. Confirm the password.
4. Next to the Store datafiles in this location field, click the browse button (...), and then select the folder for storing datafiles. For Oracle ASM, specify the ASM disk group. (For example: +DISKGRP1/ora11asm/).
5. Click Next.

Updating the tablespaces definitions

The PMDB schema defines eight tablespaces: five tablespaces for tables and three for indexes. The tables and indexes have three different sized tablespaces: small, medium, and large. The tables also have additional sts and infra tablespaces.

Each tablespace has a corresponding datafile. Therefore, eight datafiles are created each with the following filename format: <table_space_name>.DBF

The Temporary tablespace is used for temporary calculations (storage parameters). This can be an existing temporary tablespace. The Temporary tablespace storage location is the datafile associated with the temporary tablespace (storage parameters).

To update the tablespaces definitions

Using a Microsoft SQL Server PMDB

...

1. In the PMDB Instance Parameters screen, click Advanced.
2. In the New Database Properties tab, complete the following fields:
   1. Collation
   2. Datafile Initial Size (MB)
   3. Datafile Autogrowth (MB)
   4. Log File Initial Size (MB)
   5. Log File Autogrowth (Percent)
3. Click OK.

Preview