Oracle Database Installation Prerequisites

• The Oracle Data Relationship Management schema account requires access to ROLE_ROLE_PRIVS for database export external connections.

• If you are using an Oracle RAC database system, you must create the tablespaces with the appropriate RDBMS software prior to installation.

• A unique repository (and hence, schema) is required for each Data Relationship Management application.

• Oracle recommends customers use dedicated tablespaces for each Data Relationship Management schema

• Regarding repository creation, the database installation scripts are initiated via the Repository Wizard in the Data Relationship Management console which provides two options:

  • The Repository Wizard can generate the Data Relationship Management Repository (tablespaces, schema user/grants, tables and other objects) if appropriate credentials are provided

  • The Repository Wizard can generate scripts that a database administrator can use to create the tablespaces, schema user/grants, tables and other objects interactively via a tool such as Oracle SQL Developer.

• Existing SYSTEM (or its equivalent) credentials are used for the first part of the script and need to be entered in the Repository Wizard.

• You will define the schema owner name and password in a later stage of the Repository Wizard.

• When specifying the account to use via the Repository Wizard where you do not intend to hand the scripts off to a database administrator to create the repository, the initial database account needs sufficient rights to create tablespaces and create and grant privileges to the schema owner that will be created. These privileges are used later in the second part of the repository creation routine to create tables, indexes, views, stored procedures, etc., and populate them with minimal configuration data for the system to start. Typically, the Oracle SYSTEM user (or an account with equivalent privileges and rights) is used for such a task. More specifically, the rights generally needed are:

  • Run a database script

  • CREATE TABLESPACE

  • CREATE SCHEMA (CREATE USER)

  • This account also must have enough privileges to perform the following Grants to the user/schema it will be creating:

    • CREATE SESSION

    • CREATE TABLE

    • CREATE VIEW

    • CREATE PROCEDURE

    • CREATE TYPE

    • CREATE SEQUENCE

    • UNLIMITED TABLESPACE for the schema owner that will be created.

    The account also needs sufficient rights to run a database script. Check with your database administrator resources regarding specific questions as many organizations choose to establish their own policies regarding account rights.

  • During this part of the Repository Creation routine, specific Repository objects and artifacts will be created using the schema owner that is used to connect to the Data Relationship Management repository by the Data Relationship Management service and application in the Data Relationship Management Console.

• When intending to create only the database scripts and hand them off to a database administrator to create the tablespaces, schema, and repository objects, the database administrator can determine the correct account(s) to use and assign the necessary privileges as part of their activity in line with the guidance above.

See Creating a Repository for more information.

Note:

The database accounts needed for repository and schema creation may differ based on how your organization chooses to manage their Oracle Database instance(s). Check with your database administrator if you have questions.

Note:

You may be able to lesson some of the Grants mentioned for the schema owner during normal service operation; however, the product is only supported and certified to be run with the default grants. If schema owner Grants are lessened, the default Grants must be re-established if at a future point a release upgrade (uninstall one release/install an updated release) and/or an "Apply Updates" is attempted.

Note:

While UNLIMITED TABLESPACE may not technically be required, it is a standard practice. This allows organizations to minimize the maintenance activity required on the database/schema. If the database is continually or periodically using resources to expand one or more of the required tablespaces and/or index growth/maintenance, application performance may suffer. Further, if any resources required are not made available within application timeout periods, the application may become temporarily unusable during this period. Therefore, the Data Relationship Management service and application(s) may need to be restarted once sufficient database resources are made available.

Note:

If you want to alter the "QUOTA UNLIMITED" directives for the schema, we suggest you first monitor Data Relationship Management usage in a non-production environment to assist with the degree of quota and database growth rates that will be necessary moving forward.