Creating an Oracle Schema User
This topic describes how to set up an Oracle schema user.
Oracle Schema User Overview
When you create a server configuration, StarTeam Server can automatically create the tablespace and schema user. However, if you prefer, you can create the tablespace and schema user manually.
Note: All tablespaces created using StarTeam Server automatically create locally-managed tablespaces. All tablespaces created by StarTeam Server use AUTOALLOCATE. StarTeam Server supports Oracle Universal Installer for client. Consult with your database administrator for more information.
Terminology
The terms "database instance" and "schema user" used in this section are Oracle terminology. Each database instance can manage a number of different schema users. Each StarTeam Server configuration has its own schema user. Elsewhere in the documentation you will find the terminology common to the other databases that StarTeam Server supports. For example, when you install Microsoft SQL Server on a computer, you can run several instances of it. Each instance can manage a number of different databases. Therefore, when you see the term “database” in other parts of these manuals, think “schema user”.
Tip: It is highly recommended that you use a dedicated StarTeam Server user account to run or log onto StarTeam Server schema users. System administrator accounts usually have unlimited privileges. Any anomalies or errors that occur while logged in as the system administrator may result in unrecoverable damage to the StarTeam Server schema users and other schema users managed by the same database.
Set up the environment
If you will be using an Oracle schema user, you must complete the following tasks:
- Install Oracle Server. Most customers install StarTeam Server and Oracle Server on separate computers.
- Install Oracle Client on the computer on which you plan to install StarTeam Server.
- Establish connectivity between Oracle Client and Oracle Server. For more information, see Verifying connectivity between client and server.
- Install Oracle Enterprise Manager.
- Install StarTeam Server. For more information, see StarTeam Server on Windows installation .
- Make sure that the NLS_LANG setting for Oracle Client and the character set specified for Oracle Server are correct. For more information, see Configuring NLS_LANG and Database character set and StarTeam Server.
-
Create
a
StarTeam Server configuration. For more information, see
Creating a Server configuration for an Oracle Schema User (about automatically created schema users) and
Creating the Oracle Schema User manually .
Caution: Note the following:
- Never modify the database contents other than through the StarTeam Server client or the Server Administration Tool. Direct database manipulation is not supported.
- Never modify vault files other than through the StarTeam Server client or the Server Administration Tool.
Creating a Server configuration for an Oracle Schema User
The first time you start a new server configuration, StarTeam Server creates all tables in the database you specify. This section explains how to create a StarTeam Server configuration and start it for the first time.
Before you begin, you need to know:
- The Oracle Database Server name and either the Oracle Service name or SID.
- The system password.
- The logon name and password for the schema user.
- Start the Server Administration tool. Click . The Server Administration tool opens.
- Click . The New Configuration dialog box opens.
-
Enter the new configuration data:
- Type the name of the configuration in the Configuration Name field.
- Type or click Browse to specify the Repository Path location to be used to store log files and other information. If the repository path that you enter does not exist, the application creates it for you. The Repository Path is also the location for the default hive.
- Select Oracle from the Database Type list.
- Uncheck the option to Create new StarTeam database, so that StarTeam Server will not automatically create the database for it.
-
Create an initial hive for the Native-II vault by doing one of the following:
Accept the default settings Leave the Default option selected and proceed to the next step. With the default settings, StarTeam Server:
- Creates an initial hive named DefaultHive.
- Creates subfolders on the repository path named Archives and Cache to be used by the DefaultHive.
- Stipulates that the maximum cache size is 20% of the space currently available on the drive on which the cache is located.
- Uses the default setting of 600 seconds (10 minutes) between cache cleanups.
- Uses the default setting of 95% for the storage threshold, the point at which this drive is considered full.
Specify custom values Select the Custom option and change any of the hive settings. - Click Next, and enter the Database Server name, Database name, Database login name, and password in the appropriate text boxes.
- Optionally, if you are using a port other than the default, check Edit Database Port and type the port number in the text field.
- Type the login name and password for the schema user in the appropriate field.
- Select either Service Name or SID and provide the information in the appropriate field.
- Click Verify Connection to test the connection. If the connection fails, review and change your settings.
-
Click Finish.
This action re-displays the Server Administration tool, which shows your new server configuration as a child of the Local node.
Note: In addition to creating the server configuration, StarTeam Server adds information about the new server configuration to your starteam-server-configs.xml file. For more information about this file, see the Server Administration Tool Help.
Creating the Oracle Schema User manually
This section explains how to manually create an Oracle tablespace and schema user for StarTeam Server. It also provides an overview of the tuning and maintenance SQL scripts that are provided with StarTeam Server, and explains how to use them. For detailed information on Oracle performance tuning, consult your Oracle documentation.
To configure an Oracle database instance:
- Complete the procedures described in Set up the environment.
- Create a StarTeam Server tablespace.
- Create a StarTeam Server schema user.
-
To ensure that StarTeam Server can create labels and perform other operations successfully, make sure that the schema user has the following Oracle privileges. They must be explicitly defined rather than relegated to roles. For more information, see Granting Oracle privileges .
- Create procedure
- Create sequence
- Create session
- Create table
- Create trigger
- Create type
- Create view
- Unlimited tablespace
- Create any context
- Drop any context
- Create the server configuration. For more information, see Creating a Server configuration for an Oracle Schema User.
Database character set and StarTeam Server
StarTeam Server stores UTF-8 data in Oracle schema users. StarTeam Server does not use the Oracle conversion mechanism. It performs the conversion to UTF-8 itself.
Oracle software does the conversion only when the Oracle Client’s character set (specified by NLS_LANG) does not match the database instance’s character set. Therefore, it is very important that the client and server’s settings match. StarTeam Server configurations require that Oracle database instances use the WE8MSWIN1252 character set. If your StarTeam Server database was previously Oracle 8i, then Oracle database instances use the WE8ISO8859P1 character set. StarTeam Server also supports AL32UTF8 character set.
The Server Administration tool does not allow you to create a new StarTeam Server server configuration unless the underlying database instance’s character set is the correct character set. When StarTeam Server starts, it also ensures that the database character set matches the characters set portion of NLS_LANG.
Due to the numeric setting differences between different languages and territories, StarTeam Server also does not start unless AMERICAN_AMERICA (the US numeric setting) is the setting for the language_territory portion of NLS_LANG. Failure to do so causes exceptions for StarTeam Server. This does not mean that numbers and so on will be displayed incorrectly. For example, in Germany and other countries, a decimal point is represented as a comma. Such numbers will still display correctly.
Guidelines for data files
The following are the recommended guidelines for the number of data files and their sizes, based on the number of users. Your needs may be different than those shown in the table below.
Number of Users | Number of Data Files | Size of Each Data File |
---|---|---|
Up to 15 | 3 | 50 MB |
Between 15 and 50 | 3 | 300 MB |
Between 51 and 100 | 5 | 300 MB |
Between 101 and 300 | 7 | 500 MB |
>300 | 7 | 800 MB |