Tips and general rambling about Oracle JDeveloper, SCM, user interfaces, and other miscellaneous stuff.

Oracle SCM Installation Cheat Sheet


This cheat sheet provides a quick-start guide to getting Oracle SCM installed on an Oracle 9.2 database.

Before Installing

  • Install the Oracle server software

    The instructions here should work for Oracle9i release 2 (9.2.0.1.0). I'm using Gentoo linux as the repository server.
  • Install the Oracle SCM client software

    You can download Oracle SCM from OTN. It needs to be installed on a Windows machine, even if your server is on another operating system (e.g. Linux). If your database is on Windows, it's OK to install Oracle SCM on the same machine, but you should use a separate Oracle home.

Creating the database

The first step is to create a database for Oracle SCM. The easiest way to do this is to agree to run the database configuration assistant automatically after installing the server using Oracle Universal Installer. If you choose not to do this, you can manually run the configuration assistant like this:

$ORACLE_HOME/bin/dbca

Run through the Database Configuration Assistant using these screen shots as a guide:

In step 6, click on the All Initialization Parameters.. to change some parameters from their default values. It's important to do this, otherwise you'll encounter errors when using Oracle SCM later.

Click on the Name column header to sort the parameters by name. This makes it far easier to find specific parameters. Change the open_cursors parameter to 3000.

Change the hash_area_size to 1048576, then click Close.

For the remaining steps of the wizard, accept the defaults and then click Finish on the last page. Make a cup of coffee and catch up on some Oracle blogs ;)

Preparing the database

The next step is to carry out some initialization of the database so that the main installation can proceed. By far the easiest way to do this is to use the SQL utility scripts ckqa.sql and ckcreate.sql located in the ${Oracle_home}repadm61admin directory (where ${Oracle_home} is the directory in which you installed the Oracle SCM client software.

To run these scripts, you need to open a sqlplus connection to the database you created in the previous step. If the Oracle SCM client software is installed on a different machine from the database server, you'll need to set up your tnsnames.ora file on the client at this point. The quickest way to do this is using the Net Configuration Assistant, which you can find in the Windows Start menu:

On the welcome page of the wizard, choose Local Net Service Name configuration and follow the instructions on the other pages.

You should now connect to the database as the sysdba user (usually called sys), e.g.:

D:\>oracle\repos904211b\bin\sqlplus.exe
SQL*Plus: Release 9.0.1.4.0 - Production on Tue Oct 21 18:49:33 2003
(c) Copyright 2001 Oracle Corporation. All rights reserved.
Enter user-name: sys/yoursyspassword@ukp15583.uk.oracle.com as sysdba
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
JServer Release 9.2.0.1.0 - Production

Now run the ckqa script. Below is an example session; text in bold is entered by the user:

SQL> @oracle\repos904211b\repadm61\admin\ckqa
Enter TNS connect String for server
Enter TNS : ukp15583.uk.oracle.com
Enter password for SYS ....'
Enter password:
Connected.

Enter the Repository size you wish to create. Small(S),Medium(M),Large(L) ... Enter S/M/L : L Dropping temporary table CKRAU_TEMP

drop table CKRAU_TEMP * ERROR at line 1: ORA-00942: table or view does not exist

Creating temporary table CKRAU_TEMP

Table created.

Enter datafile location and name for CONSTANT_GROW_INDEXES... Enter datafile : constant_grow_indexes.dbf

Enter datafile location and name for CONSTANT_GROW_TABLES... Enter datafile : constant_grow_tables.dbf

Enter datafile location and name for DEPENDENCY_INDEXES... Enter datafile : dependency_indexes.dbf

Enter datafile location and name for DEPENDENCY_TABLES... Enter datafile : dependency_tables.dbf

Enter datafile location and name for DIAGRAM_INDEXES... Enter datafile : diagram_indexes.dbf

Enter datafile location and name for DIAGRAM_TABLES... Enter datafile : diagram_tables.dbf

Enter datafile location and name for LOB_DATA... Enter datafile : lob_data.dbf

Enter datafile location and name for RAPID_GROW_INDEXES... Enter datafile : rapid_grow_indexes.dbf

Enter datafile location and name for RAPID_GROW_TABLES... Enter datafile : rapid_grow_tables.dbf

Enter datafile location and name for SYSTEM_META_INDEXES... Enter datafile : system_meta_indexes.dbf

Enter datafile location and name for SYSTEM_META_TABLES... Enter datafile : system_meta_tables.dbf

Enter datafile location and name for TEMPORARY_INDEXES... Enter datafile : temporary_indexes.dbf

Enter datafile location and name for TEMPORARY_TABLES... Enter datafile : temporary_tables.dbf

Enter datafile location and name for VERSION_INDEXES... Enter datafile : version_indexes.dbf

Enter datafile location and name for VERSION_TABLES... Enter datafile : version_tables.dbf

Enter datafile location and name for REPOS_RBS tablespace... Enter datafile : repos_rbs.dbf

Enter datafile location and name for REPOS_TEMP tablespace... Enter datafile : repos_temp.dbf

For ten or more subordinate users, we recommend giving access using public synonyms. Do you wish to grant create/drop public synonym privilege to Repository Owner ? Enter Choice (Y/N) : Y

At this point, ckqa will create a script which you should install using ckcreate:

SQL> @oracle\repos904211b\repadm61\admin\ckcreate

This will create the repository owner user, required roles and tablespaces necessary to proceed with the next step.

One final task: to avoid running out of space during installation and day-to-day use of repository, it's advisable to turn on autoextend for all the datafiles created by the ckcreate script. Paste the SQL commands below into SQL*Plus to do this:

alter database datafile 'constant_grow_indexes.dbf' autoextend on next 1M;
alter database datafile 'constant_grow_tables.dbf' autoextend on next 1M;
alter database datafile 'dependency_indexes.dbf' autoextend on next 1M;
alter database datafile 'dependency_tables.dbf' autoextend on next 1M;
alter database datafile 'diagram_indexes.dbf' autoextend on next 1M; alter database datafile 'diagram_tables.dbf' autoextend on next 1M;
alter database datafile 'lob_data.dbf' autoextend on next 1M;
alter database datafile 'rapid_grow_indexes.dbf' autoextend on next 1M;
alter database datafile 'rapid_grow_tables.dbf' autoextend on next 1M; alter database datafile 'system_meta_indexes.dbf' autoextend on next 1M;
alter database datafile 'system_meta_tables.dbf' autoextend on next 1M;
alter database datafile 'temporary_indexes.dbf' autoextend on next 1M;
alter database datafile 'temporary_tables.dbf' autoextend on next 1M;
alter database datafile 'version_indexes.dbf' autoextend on next 1M; alter database datafile 'version_tables.dbf' autoextend on next 1M;

Installing the Repository

The Repository Administration Utility (RAU) is used to install and maintain the repository. Launch the RAU from the Windows Start menu:

On startup, the RAU will display a Connect dialog. You should log in as the repository administrator user, which was created automatically by the ckcreate script. The default username and password is repos_manager/manager. After connecting, click the Install button to begin installation:

When prompted Do you want to use Public Synonyms?, click Yes. This makes creation of new users much quicker.

In the Install a Repository instance dialog, you need to set all the drop down lists to the correct values. This is a bit tedious. The quickest way to do this is to tab to each drop down list in turn and type the first letter of the correct tablespace. You should also set the Repository Size to Large. The dialog should look like this when you're done:

Now click Start, and repository installation will begin. This will take some time. When installation is complete, click Cancel in the Install a Repository instance dialog.

Next, enable support for versioning. Click the Enable Version Support... item in the RAU's Options menu. After doing this, you'll need to restart the RAU and reconnect to the repository.

Finally, set a couple of options that are recommended for using Oracle SCM with JDeveloper. Click the Edit Policies... menu item in the Options menu, and ensure your settings match those in the screenshot below.

That's it! Oracle SCM is installed. You should be able to connect to the repos_manager user using either the Repository Object Navigator (RON) or JDeveloper.

Adding Users

You probably want to add a few other users to the repository before using it. Each repository user is a database user, which you should create in the normal way via SQL*Plus, e.g.:

SQL> create user brian identified by brianpassword;
User created.
SQL> grant connect, resource to brian;
Grant succeeded.

Using the RAU, you should install the repository schema for this user. Click the Maintain Users button on the RAU's main screen, select the Users node in the tree and click the small Add button to the left of the tree:

In the Oracle User Name dropdown, select the Oracle user to create a repository user for. You can then customize the privileges this user has. For a typical JDeveloper Oracle SCM user, you will want to allow management of everything except Users.

Click OK, and the user will be created.

weblog   |   articles
© Copyright 2003 Brian Duff. Last Updated 22/10/2003; 14:20:16. Java is a trademark or registered trademark of Sun Microsystems, Inc. in the United States and other countries.