0750-0752 | Oracle Development Unleashed (3rd Edition)

Previous Table of Contents Next

Page 750

the progress while files are copied . After the progress indicator reaches 100 percent, the installation of Designer/2000 for the client is complete. Proceed to the section "Server Installation," later in this chapter, to complete the necessary steps on the Designer/2000 server.

Custom Installation/Deinstallation

During a complete install, you can install or deinstall a list of selectable Designer/2000 components. A window on the left indicates components that can be installed, and a window on the right indicates components of Designer/2000 that can be deinstalled.

Installing Designer/2000 on a client is a fairly simple process. Using Oracle Installer is an intuitive process; it automatically determines which components of Designer/2000 are dependent on others and gathers necessary information quickly and easily.

Server Installation

After you install the client portion of Designer/2000, a series of steps must be performed to set up the server side of Designer/2000. An Oracle DBA with specific privileges to the system areas of your Oracle server must perform these steps.

WARNING

Designer/2000 needs the Oracle server Procedural option to be installed. Your DBA can supply this by executing the CATPROC script.

During this setup process, the DBA creates additional tablespaces on your Oracle server and allocates space to these tablespaces. The DBA also creates a repository owner and grants that owner special Oracle system privileges needed by Designer/2000. The DBA also confirms that your Oracle server meets the minimum requirements in several areas, including system tablespace, SGA shared pool size , and other parameters. Here are the steps for the DBA to follow:

Start the server process by creating a new tablespace and an accompanying tablespace for the Designer/2000 indexes.

CAUTION

Do not install the Designer/2000 tables in the system tablespace. Designer/2000 enables you to specify another tablespace, so do so. Keep your system tablespace as clean and clutter-free as possible.

It is recommended that the tablespace be called DES2 and that the tablespace for the indexes be called DES2_I. The size of these tablespaces should be 13MB and 11MB,

Page 751

respectively. As the Oracle DBA, don't forget to assign quota limits (or an unlimited quota) to these newly created tablespaces.

Large rollback segments are a necessity for proper use of Designer/2000. Although most roll back segments within an Oracle installation are often the same size, you might need to increase their sizes if you are receiving errors because of insufficient rollback segment size. Designer/2000 does not commit the changes made to the Oracle instance frequently, so it requires large rollback segments. These large rollback segments are needed only during the installation of Designer/2000. After it's installed successfully, you can alter the size of the rollback segments.

TIP

You can create a very large, single rollback segment. Take all other rollback segments offline so that the installation process is forced to use the large rollback segment. After Designer/2000 is installed successfully, you can drop the large rollback segment and return your system to its normal state.

In addition to adding data in the previously created DES and DES_I tablespaces, the installation process adds data to the system tablespace. Designer/2000 needs a minimum of 35MB of additional space in the system tablespace. Although this is the minimum, about 60MB of space generally is needed.

TIP

The space available should be as contiguous as possible. Fragmentation within the system tablespace can lead to extremely poor performance.

Create a repository owner/user for the installation process. Define the DES tablespace as the default and temporary tablespace. Also, allow the user an unlimited quota on DES and DES_I tablespaces. You will need to assign special system privileges to the user :

 CREATE SESSION ALTER SESSION CREATE TABLE CREATE VIEW CREATE SEQUENCE CREATE PROCEDURE CREATE TRIGGER CREATE CLUSTER CREATE SYNONYM CREATE ANY SYNONYM DROP ANY SYNONYM CREATE DATABASE LINK CREATE ROLE CREATE SNAPSHOT

Page 752

Create a role, possibly called DES2000_OWNER, that contains the privileges listed in step 4. A script is available for performing these actions; it is located in <OracleHome>\
REPADM10\UTL. This SQL script, CKROROLE.SQL, can be run from the SYS (not the SYSTEM) account. After the role is created, you can assign the created role to the owner.
Some parameters within the Oracle server INIT.ORA file might need modification. Table 30.2 lists the parameters that might need to be modified and their minimum values (or required values).

Table 30.2. Modifiable parameters in the INIT.ORA file.

Parameter	Minimum/Proper Setting
shared_pool_size	18000000
db_block_buffers	1000
open_cursors	200
processes	20
global_names	False

Remember that these are minimum settings. If your Oracle instance contains larger values than the references in Table 30.2, no changes are necessary. If changes are made to any of these parameters, you must shut down your Oracle database and then restart your database in order for the new parameters to take effect.

During the installation process, you'll need the Import utility. For the Import utility to function properly, your ORACLE.INI file must contain a LOCAL parameter setting. This specifies to which Oracle server and database to connect. If a TCP/IP connection is being used, the connect string might look like this:
```
 LOCAL=t:server:database 
```
where server is the name of the Oracle server, and database is the name of the database to which to connect. Use an ASCII text editor to add this LOCAL parameter to your ORACLE.INI file.
You now are ready to start the Repository Administration utility and install a new Repository instance. From Windows, open the Designer/2000 program group if it is not already open. Start the process by double-clicking the Repository Administration utility icon. A connection prompt appears, asking for a username and password. As the DBA, you probably set these up as OWNER1. Enter the information, and choose Connect to continue.
Select the proper tablespaces where the Designer/2000 Repository information will reside. As the DBA, you probably defined these tablespaces as DES for the table tablespace and DES_I for the indexes tablespace.

Previous Table of Contents Next