Prepare Your DBMS Environment

Install and Configure an Oracle Mart › How to Install and Configure an Oracle Mart › Create the Mart Database and Perform the Additional Tasks

Create the Mart Database and Perform the Additional Tasks

Perform the following setup tasks in your DBMS environment before you can install and use the software:

Install the DBMS on the server where you plan to store the Mart.
Help ensure that you can create tables, indexes, stored procedures, and public synonyms. For more information about memory and disk space requirements, see the system requirements for each DBMS (Microsoft SQL Server, Sybase, PostgreSQL, and Oracle).
Create a database that you want to use as the Mart. To use a pluggable database, see the Use a Pluggable Database topic.
Use the DBMS features to create or identify the required storage objects and the mart. The specific requirements vary depending on your DBMS type.

Note: To create, update, or delete a Mart in CA ERwin Data Modeler Workgroup Edition, you must be the database schema owner and you must have the DBA role.

Additional Tasks

The DBA and the system administrator responsible for installing the software on an Oracle database management system performs these tasks.

Use graphical tools or SQL *Plus (all versions), SQL*DBA, or the Oracle Enterprise Management Console to perform these tasks. Some SQL commands are included where appropriate. The Data file paths, data file sizes, role names, and user names are included as examples only.

Check the SYSTEM tablespace.
The installation creates several stored procedures. All triggers, stored procedures, and packages are kept in the Oracle SYSTEM tablespace. The standard size of the SYSTEM tablespace assumes that you are not using procedural options, so the SYSTEM tablespace must be often expanded. If other Oracle applications are not using procedural code, then expand the SYSTEM tablespace to 32 MB. If other Oracle applications also use procedural code, expand the SYSTEM tablespace to at least 32 MB.
Check the Rollback Segment tablespace.
If your instance uses UNDO tablespace, do not create rollback segments.

Significant rollback space is required for installing and use. The rollback segments must be in their own separate tablespace and each have at least 16 MB of available space. There must be one rollback segment for every four concurrent users, with a maximum of 50 rollback segments. The available space must scale upward with increasing numbers of rollback segments. Finally, the rollback segment optimal parameter must be set to control rollback segment growth and space consumption.

Note: For Steps 3, 4, and 5, use the Dictionary-managed tablespaces.

Create a data tablespace of at least 32 MB.

For example:

CREATE TABLESPACE MyMart

DATAFILE '/db01/oracle/rdbms9i/data/mymart.ora' SIZE 100M;

Or For Locally Managed extents:

CREATE TABLESPACE Mymart

DATAFILE '/db01/oracle/rdbms9i/data/mymart.ora' SIZE 100M

EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO;

Create an index tablespace of at least 32 MB.

For example:

CREATE TABLESPACE MMARTINDEX

DATAFILE '/db02/oracle/rdbms9i/data/mmartindex.ora' SIZE 75M;

Or For Locally Managed extents:

CREATE TABLESPACE MMARTINDEX

DATAFILE '/db02/oracle/rdbms9i/data/mmartindex.ora' SIZE 75M

EXTENT MANAGEMENT LOCAL SEGMENT SPACE MANAGEMENT AUTO;

Create a temporary tablespace.

For example:

CREATE TEMPORARY TABLESPACE MMTEMP TEMPFILE '/db03/oracle/rdbms9i/data/mmarttemp.ora' SIZE 50M;

Or For Locally Managed extents:

CREATE TEMPORARY TABLESPACE MMTEMP TEMPFILE '/db03/oracle/rdbms9i/data/mmarttemp.ora' SIZE 50M

EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M;

Note: For more details about syntax and options regarding tablespace creation, see the appropriate Oracle documentation.

Create an Oracle user with DBA privileges for use by the CA ERwin Data Modeler Workgroup Edition Installer or designated schema owner.
Assign the data tablespace to this user as the default tablespace, and the temporary tablespace as the temporary tablespace to the user.

For example:
```
CREATE USER STEVE IDENTIFIED BY STEVE
```
```
DEFAULT TABLESPACE MyMart
```
```
TEMPORARY TABLESPACE MMTEMP
```
```
QUOTA UNLIMITED ON MyMart
```
```
QUOTA UNLIMITED ON MMARTINDEX;
```
Create the CA ERwin Data Modeler Workgroup Edition Installer role.
The following example is the role that the Oracle user requires to install CA ERwin Data Modeler Workgroup Edition.
```
CREATE ROLE MMINSTALL;
```
Grant the Oracle privileges to the Installer role.
The following example shows the Oracle privileges that the CA ERwin Data Modeler Workgroup Edition Installer must install on Oracle. For the last command, log in as sys with the sysdba role in the user-name or the command will fail.
```
grant create sequence to MMINSTALL;
```
```
grant create table to MMINSTALL;
```
```
grant create view to MMINSTALL;
```
```
grant drop public synonym to MMINSTALL;
```
```
grant create public synonym to MMINSTALL;
```
```
grant create procedure to MMINSTALL;
```
```
grant select on dba_data_files to MMINSTALL;
```
Create the CA ERwin Data Modeler Workgroup Edition User role.
For example:
```
CREATE ROLE MMUSER;
```
When you select this role as the CA ERwin Data Modeler Workgroup Edition User role during Step 4 of the installation procedure, the Setup program generates grant statements. These statements grant the object level privileges to this role.
Grant the create session Oracle privilege to the User role.
For example:
```
grant create session to MMUSER;
```
Note: To use the database, an Oracle user needs only the create session privilege.
Grant the CA ERwin Data Modeler Workgroup Edition User role to the Installer role.
For example:
```
grant MMUSER to MMINSTALL;
```
Select the CA ERwin Data Modeler Workgroup Edition tablespaces and User role.

When prompted for tablespace and role information, select the Workgroup Edition data tablespace, the Workgroup Edition index tablespace, and the Workgroup Edition User role (the role created in Step 9).