ORACLE - DBA Tips Corner

DBA Tips Archive for Oracle

Installing Oracle SCM - (9.0.2.4)

by Jeff Hunter, Sr. Database Administrator

Introduction

Navigate to the Oracle Technology Web Site (http://otn.oracle.com) to download a zipped version of Oracle SCM 9i (9.0.2.4):
http://otn.oracle.com/software/products/repository/index.html
The file is named SCM9024_cd.zip and should be around a 175MB download.

Installing the Client

From a Windows client machine, unzip the file SCM9024_cd.zip to a temporary directory.
Run setup.exe from the temporary directory to invoke the Oracle Universal Installer. This will allow you to install the Oracle SCM 9.0.2.4 client on your workstation. Here are some of the attribute parameters to supply to the installer:
File Locations
Name:   OraHomeSCM9024
Value:  C:\oracle\orascm9024
Installation Types
__X__    Complete
_____    Core SCM
Configuration Tools
When the Oracle Net Configuration Assistant comes up, it is safe to ignore (or cancel) this assistant. The only purpose of this the Net Configuration Assistant is to configure a tnsnames.ora and sqlnet.ora file for a connection to the server-side Oracle repository. If you already have a tnsnames.ora and sqlnet.ora file available, you can simply put these files in the %ORACLE_HOME%/network/admin folder.
Post Installation
After exiting the Oracle Universal Installer, you will be left with two new folders in your Start menu: "Oracle - OraHomeSCM9024" and "Oracle9i Developer Suite - OraHomeSCM9024". You should only need to access the Oracle9i Developer Suite option for the following applications:

Repository Administration Utility
Repository Command Line Tool
Repository Object Navigator
Follow the server-side installation instructions given in the Repository Installation Guide to create a new repository or upgrade an existing repository. Instructions are given in the next section as well.

Installing the Server-Side Repository

NOTE: Do not use any of the procedures in this section unless you have first installed Oracle9i Designer or Oracle9i SCM at a client workstation. For a new installation you must install a new repository on an existing database.
The client workstation and the database server can be on the same machine, or on different machines.
You will be prompted for the following information:

Repository Size
Small, Medium or Large.

Tablespace Details
There are two methods for create tablespace for the repository; "SQL Script Method" and "Manual Method". The SQL script method (which should always be used), creates tablespaces with the default names and sizes. You can, however, modify these details before you run the CKCREATE script, as described later in the section on installing using the script method. There are 17 tables used for the default install.

Datafile Details
The biggest decision here is the name of each datafile and if AUTOEXTEND will be on or not.

Use of Public Synonyms
Users can access the repository through either private or public synonyms, and you are prompted to choose the access method during installation. (You can change it later using the Repository Administration Utility).
Oracle STRONGLY recommends using public synonyms. Only use private synonyms for a maximum of 10 users. Using public synonyms maintains repository performance, for example by reducing the time it takes to complete tasks such as reconciling grants for all repository users.
If you choose to use public synonyms, you will need to grant the repository owner the database privileges CREATE PUBLIC SYNONYMS and DROP PUBLIC SYNONYM. Under the script method of the installation you answer a simple Yes/No prompt for this; user the manual method you must grant these privileges explicitly.

Use of Version Control
Version control is the process of maintaining multiple versions of software development objects and is a fundamental requirement if you are using the repository for software configuration management.

Although you do not need to specify during the installation whether to enable version control, it is a good idea to consider its implications at this stage. Unless it is enable, you cannot use the software configuration management features of the repository, such as Workareas, Configurations, Check In, Check Out and Merge. However, once version control is enabled you cannot disable it, so you should carefully consider whether it is really necessary for a particular repository.
This section will use the "Interactive SQL Script Method" for installing the new repository. Ensure that the database and TNS listener are up and operational.
The following is a list of the SQL scripts required for installing the new repository:

SQL Script Description

ckqa Collects input from you for passing on to subsequent scripts. Input is placed in a file named CKPARAMS.TXT, which you can edit before configuring with further scripts.

ckvalqa Validates the user input collected during the ckqa stage. You need to run this script only if you have modified the CKPARAMS.TXT file since you last ran ckqa.

ckcreate Creates the database objects required by the repository. Also creates the repository owner with the necessary privileges.

ckreport Creates a report (in the file CKREPORT.LST) on the database objected create ckcreate.

ckclean Removes the repository, deleting all the database objects created by ckcreate.
Run the following to create the database structure and users:
If using Oracle9i SCM use:
cd %ORACLE_HOME%\REPADM61\admin
If using Oracle9iDS use:
cd %ORACLE_HOME%\repadmin61\admin
Then continue with:
sqlplus "sys/change_on_install@host as sysdba"

SQL> @ckqa
This script creates a file named CKPARAMS.TXT (in the same directory as the scrip files), based on the input you supply while the script is running. Check this script out before running the next command.
SQL> @ckcreate
Exit from SQL*Plus and continue with the following steps.
NOTE: The scripts that where just run (above) create the repository owner:
REPOSITORY OWNER
Username:      REPOS_MANAGER
Password:      MANAGER
Change this after completing all steps in the installation.
Go to the Client Workstation where you installed Oracle9iDS (or Oracle SCM Client) and click the Start button and choose:
If using Oracle9iDS use:
Programs >
  Oracle9i Developer Suite - OraHomeSCM9024 >
  Software Configuration Manager >
  Repository Administration Utility
If using Oracle9i SCM use:
Programs >
  Oracle product - 9iDS_home >
  Oracle 9i Software Configuration Management >
  Repository Administration Utility
In the Connect dialog box, login with the following:
User Name: The Repository Owner. REPOS_MANAGER if you used the SQL script method for installing the repository.
Password: The password for the repository Owner. MANAGER if you used the SQL script method for installing the repository.
Connect String: The database service name.
In the Repository Administration Utility, click the "Check Requirements button". In this case, everything should be setup correctly. Especially if you used the SQL scripts method for installing the repository. You should also check that privileges have been set. Again, this should all be OK to continue.

On the Repository Administration Utility windows click the "Install" button.

On the "Repository Installation Options" dialog box, the Support for Repository (Core) Objects box is checked by default. In addition, ensure that the Support for Oracle Designer Objects box is checked (if you will be using Oracle9i Designer) or not checked (if you will be using Oracle9i SCM).

Click OK, then respond to the prompt concerning the privilege CREATE PUBLIC SYNONYM if it appears. If the repository is to have ten or more subordinate users, we recommend giving access through public synonyms.

In the "Install a Repository Instance" dialog box, choose the Small, Medium or Large option button.

Choosing Medium or Large will increase the initial extents and next extents values for all tablespaces except SYSTEM and TEMPORARY.

Repository tables and indexes are stored by default in the tablespace defined as the default tablespace for the Repository Owner. If you used the SQL script method, this is the TEMPORARY_TABLES tablespace. If you used the manual method, it is the default tablespace defined when you create the repository owner.

You can refine the tablespace assignments by selecting different tablespaces for different categories of repository data.
It is now time to START the installation.
The installation consists of a number of stages. For each stage, a log file is written to the log directory. These log files are named stage.LIS, where stage identifies a particular stage, for example, CKCONST for the constraint installation stage. You can examine or monitor the log files while the installation is in progress, but do not delete them.
NOTE: You might find it useful to view the log directory files in date order so that you can see which ones were created most recently.
To start the installation:
On the "Install a Repository Instance" dialog box, click the Start button.
Click Yes at the "Do you wish to proceed?" message.
If you see the message:
  Insufficient database grant privileges to perform operation.
click the Check Requirements button, proceed as described earlier under "Check Privileges, Tablespaces and Parameters", and then try the installation again.
From this point, the installation process continues automatically, and normally needs no intervention.
If you need to interrupt the process at any point after the Control Status dialog box is displayed, click the (Pause) button.
When you see the message "Operation Complete", click OK followed by Cancel to return to the Repository Administration Utility window.
If the installation appears to complete successfully, examine the log files referred to above to ensure that Oracle errors and warnings were not issued during object creation and compilation. In the Repository Administration Utility, click the "View Objects" button and make sure that you do not have any invalid, disabled or missing objects in the repository.
Post-Installation Steps
Version Control:
If you will be using version control for repository objects, you must enable this feature in the repository. In the Repository Administration Utility, choose "Options > Enable Version Support".
Turning Off Broadcasting:
When using some of the tools, you may see the message "Unable to register notification service". To stop the message appearing, choose Options > Broadcast Options in the tool and select Disabled.
Test Basic Repository Operations:
To test the repository, proceed as follows:
If you have enabled version control, create a new default workarea:

Start the Repository Object Navigator by clicking Start and choosing Programs > Oracle product - 9iDS_home > Oracle 9i Software Configuration Management > Repository Object Navigator.
Use the same connection details that you used earlier for starting the Repository Administration Utility.
Click OK to acknowledge the message about statistics.
At the Welcome screen, choose "Invoke Workarea Wizard" and click OK.
Create a default Workarea using the wizard.
To see the new Workarea, you will need to open a new Navigator window at the level of Private Workareas or above.

Create a test container in a Workarea. (If you have not enabled version control, only one Workarea is available.)
Create some test element definitions in the new container. Try using different tools to create the definitions.
If you have enabled version control:

Check in one of the new objects to add it to source control.
Check out the object and update some of its properties.
Check in the object, ensuring that the version label property is updated (e.g. from 1.0 to 1.1).
With the object selected, start the Version History Viewer (choose Version > View Version History) and check that the expected version history displays.
In the Version History Viewer, select an object version and compare it (e.g. by Version > Compare Other Version) with another version with known differences.
With the object version still selected, merge the version with another (e.g. by Tools > Merge Wizard).

Detailed instructions for carrying out these tasks are in the Repository Management online help.
When using some tools, you may see a message beginning:
  Statistics have not been computed for this repository...
You can ignore this message during repository setup or, if you want to stop the message from appearing:
In the Repository Administration Utility, click the (Compute Statistics) button.
Click Compute (the operation takes a few minutes to complete).
Create Subordinate Users:
If other users at your site are to have access to the repository, you will need to create subordinate users. This is the term given to repository users other than the Repository Owner. Any usernames you want to use for subordinate users must already have been created as Oracle usernames via a CREATE USER statement in SQL*Plus.
You create subordinate users from the Repository Administration Utility. Creating subordinate users requires particular care to ensure that the users have the correct:

System privileges (see the next section)
Repository privileges (e.g., whether they can create configurations or purge object versions)
Access rights (see "Grant Access Rights to Users")

NOTE: For full details of the procedure to create subordinate users, see the topic "Granting repository access to an Oracle user" in the Repository Management help system.
Subordinate users must be assigned the CONNECT and RESOURCE database roles. To do so, start SQL*Plus, connect as SYS and issue the following command for each user:
SQL> grant connect, resource to username;
Grant System Privileges to Users:
Various system privileges are required by a repository owner and subordinate users to perform certain repository operations. The following table lists various system privileges (Database System Privileges), and indicates the operations for which the repository owner or subordinate user will need them:

System Privilege Repository Owner Subordinate User

CREATE SESSION Connection Connection *

ALTER SESSION Diagnostics Diagnostics *

CREATE TABLE Installation, Migration *

CREATE VIEW Installation *

CREATE SEQUENCE Installation *

CREATE PROCEDURE Installation *

CREATE TRIGGER Installation *

CREATE ANY SYNONYM Reconcile user

DROP ANY SYNONYM Reconcile user

CREATE PUBLIC SYNONYM Reconcile user

DROP PUBLIC SYNONYM Reconcile user

CREATE DATABASE LINK Migration *

CREATE ROLE Reconcile user

CREATE SYNONYM Migration *

CREATE ANY TABLE Registration

CREATE ANY VIEW Registration

CREATE ANY SNAPSHOT Registration

CREATE ANY SYNONYM Registration

CREATE ANY PROCEDURE Registration

CREATE ANY SEQUENCE Registration

CREATE ANY TRIGGER Registration

CREATE ANY INDEX Registration

CREATE ANY TYPE Registration

CREATE ANY CLUSTER Registration

SELECT ANY SEQUENCE Registration

SELECT ANY TABLE Registration

(*) These privileges are granted to subordinate users when they are assigned the CONNECT and RESOURCE roles
Diagnostics privileges are required if, for example, you wish to enable SQL TRACE.
Registration privileges are required for registration of Oracle schemas in the repository. See the online help for Repository Management.
Reconcile user privileges allow subordinate users to be enabled or disabled (synonyms created or dropped) via the Reconcile button on the Maintain Users dialog box of the Repository Administration Utility.
Some subordinate users may need additional privileges depending on which utilities they will be running (e.g. Import/Export from the Repository Object Navigator). To grant these, connect as SYS and enter any or all of the following as appropriate:
grant create table to subordinate_user;
grant create view to subordinate_user;
grant create procedure to subordinate_user;
grant create synonym to subordinate_user;
grant create sequence to subordinate_user;
grant select on dba_rollback_segs to subordinate_user;
grant select on dba_segments to subordinate_user;
Grant Access Rights to Users:
The user who owns a Workarea, container or configuration can grant access rights on that item to other users, or revoke them from those users.
If you have created subordinate users, test the access rights mechanism as follows:

In the Repository Object Navigator, choose File > Access Rights > View Access Rights.
Check the current access rights on the test Workarea and container that you created earlier.
Grant (at least) the Select access right on the Workarea and container to one of the subordinate users.
Change the connection to that user.
Check that the user can see the Workarea (under Shared Workareas) and the container.
Change the connection back to the repository owner and revoke the access rights.

To grant an access right to all subordinate users (present or future), grant it to PUBLIC.
NOTE: If you have enabled version control, remember to grant the "Version Access Right" on an object to any users who will be using version control with that object.

All articles, scripts and material located at the Internet address of http://www.idevelopment.info is the copyright of Jeffrey M. Hunter and is protected under copyright laws of the United States. This document may not be hosted on any other site without my express, prior, written permission. Application to host any of the material elsewhere can be made by contacting me at jhunter@idevelopment.info.

I have made every effort and taken great care in making sure that the material included on my web site is technically accurate, but I disclaim any and all responsibility for any loss, damage or destruction of data or any other property which may arise from relying on it. I will in no case be liable for any monetary damages arising from such loss, damage or destruction.

Last modified on
Sunday, 11-Aug-2002 00:00:00 EDT
Page Count: 30563

SQL Script	Description
`ckqa`	Collects input from you for passing on to subsequent scripts. Input is placed in a file named `CKPARAMS.TXT`, which you can edit before configuring with further scripts.
`ckvalqa`	Validates the user input collected during the ckqa stage. You need to run this script only if you have modified the `CKPARAMS.TXT` file since you last ran ckqa.
`ckcreate`	Creates the database objects required by the repository. Also creates the repository owner with the necessary privileges.
`ckreport`	Creates a report (in the file `CKREPORT.LST`) on the database objected create ckcreate.
`ckclean`	Removes the repository, deleting all the database objects created by ckcreate.

System Privilege	Repository Owner	Subordinate User
`CREATE SESSION`	Connection	Connection *
`ALTER SESSION`	Diagnostics	Diagnostics *
`CREATE TABLE`	Installation, Migration	*
`CREATE VIEW`	Installation	*
`CREATE SEQUENCE`	Installation	*
`CREATE PROCEDURE`	Installation	*
`CREATE TRIGGER`	Installation	*
`CREATE ANY SYNONYM`	Reconcile user
`DROP ANY SYNONYM`	Reconcile user
`CREATE PUBLIC SYNONYM`	Reconcile user
`DROP PUBLIC SYNONYM`	Reconcile user
`CREATE DATABASE LINK`	Migration	*
`CREATE ROLE`	Reconcile user
`CREATE SYNONYM`	Migration	*
`CREATE ANY TABLE`	Registration
`CREATE ANY VIEW`	Registration
`CREATE ANY SNAPSHOT`	Registration
`CREATE ANY SYNONYM`	Registration
`CREATE ANY PROCEDURE`	Registration
`CREATE ANY SEQUENCE`	Registration
`CREATE ANY TRIGGER`	Registration
`CREATE ANY INDEX`	Registration
`CREATE ANY TYPE`	Registration
`CREATE ANY CLUSTER`	Registration
`SELECT ANY SEQUENCE`	Registration
`SELECT ANY TABLE`	Registration