Server-Side Installation, Migration and Upgrade This section describes how to install a new repository, how to migrate data from a repository installed under a previous release, and how to upgrade a repository that was installed under a recent release. The following topics are covered:. This section is intended for use by Oracle database administrators (DBAs) and requires knowledge of SQL and Oracle database management. Caution: Do not use any of the procedures in this section unless you have first installed Oracle Designer or Oracle Designer Repository at a client workstation. System Requirements The Operating Systems and Database server versions certified for use with Oracle Designer are listed on Metalink The client workstation and the database server can be on the same machine (Windows only), or on different machines.
System requirements for a client workstation are listed in the Oracle Developer Suite Installation Guide. System requirements for the database server are listed in the Oracle Database Installation Guide. 15372. These sizes are based on values for INITIAL and NEXT (see table below) of 100K. If you increase the INITIAL and NEXT values, adjust the sizes for TEMPORARYINDEXES and TEMPORARYTABLES proportionately (e.g.
Re: Can't Install Oracle Designer 10g on Windows 7 HamidHelal Jun 5, 2012 4:15 PM ( in response to RNester ) 855886 wrote: Although it's not supported, I had no trouble installing it on a different computer running Windows 7 Professional 64-bit.
If you double the value of INITIAL and NEXT, double the sizes marked.). These additional tablespaces are required only if suitable tablespaces do not exist already. For example, for rollback an Oracle9 i database using automatic undo can make use of the UNDOTBS1 tablespace installed with the database. Caution: The tablespace sizes given above are estimated to ensure completion of the installation and to provide for initial use. More free space will be required for continuing use of the repository. The minimum free space sizes given in the previous table are based on certain assumptions about the storage parameter values.
The following table shows the tablespace storage parameter values assumed for a small repository: Storage parameter Value INITIAL 100k NEXT 100k PCTINCREASE 0 MINEXTENTS 1 MAXEXTENTS unlimited For medium and large repositories you will need to adjust the storage parameter values accordingly. Datafile Details You need to decide the name and location of the datafiles to be used for the various tablespaces that are created. We recommend using a dedicated datafile for each tablespace, with a datafile name that clearly indicates the tablespace to which the file relates, e.g.
SCMCGIND.ORA for CONSTANTGROWTHINDEXES. If you use the manual method of repository installation, you can choose to set AUTOEXTEND on for each datafile when you create it. Doing so avoids the risk of running out of extents during installation, provided that you have sufficient free disk space on the drive. You can always set AUTOEXTEND on for a datafile after installation is complete, but use this option with care as it allows the size of a file to grow unchecked. 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.) Public synonyms enable you to give users repository access using just one set of synonyms, instead of creating one set for each user.
For each Oracle instance, you can only have one repository accessed using public synonyms because public database objects must be unique. We strongly recommend 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 SYNONYM and DROP PUBLIC SYNONYM. Under the script method of installation you answer a simple Yes/No prompt for this; under the manual method you must grant these privileges explicitly. For more information about repository use of private and public synonyms, look in the Repository Management online help index under 'synonyms'. 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 installation whether to enable version control, it is a good idea to consider its implications at this stage.
Unless it is enabled, 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 and its data. Installing a New Repository For new installations under Oracle9 iDS, you must install a new repository on an existing database. Because no preconfigured repository is supplied with this release, you must define the tablespace sizes and allocations as part of the installation. The installation process can take several hours to complete, depending on the speed of the server, the client and the connections between them.
There are two methods of installing a new repository:. using interactive SQL scripts. manually With the SQL script method, the installation process is semi-automated; you run a series of SQL scripts, which prompt you for any necessary input. You can also change the input parameters before you run the script that creates the repository tablespaces and other objects. With the manual method, you create everything by entering individual SQL statements.
This takes longer than the script method, but allows you a greater degree of control over the installation process. Both methods require you to execute a series of pre-installation procedures, and also involve running the Repository Administration Utility to complete the installation process. Pre-Installation Procedures Whether you will be installing by the script method or the manual method, you must perform the following steps first, at the database server: Step 1 - Log On to the Machine That Hosts the Oracle Database Log on to the machine that hosts the Oracle database you will be using for the repository. Step 2 - Ensure Correct Settings for Database Initialization Parameters Oracle9 i Databases Using a Server Parameter File With Oracle9 i the initialization parameters are typically managed by a server parameter file (SPFILE), a binary file that resides in the database Oracle home on the server in the following default location: Oraclehome database (Windows servers) $ORACLEHOME/dbs (UNIX servers) If the database is using a server parameter file that does not have the settings shown under later in this section, you will need to do the following before proceeding:. Start SQL.Plus.
Connect as SYS using the AS SYSDBA clause (for example SYS/ psw@ alias AS SYSDBA). At the SQL prompt, enter: alter system set paramname = paramvalue , paramname = paramvalue. scope = spfile; where paramname and paramvalue are the name and value of an entry in the SPFILE. Exit from SQL.Plus.
See the Oracle9i Database Administrator's Guide for full details about managing initialization parameters using a server parameter file. Oracle9 i Databases Using INIT.ORA Parameters for configuring the Oracle database at startup are contained in a file named INIT.ORA. This step checks the setting of the relevant parameters and changes them where necessary. Read later in this section.
This contains important information to help you set the parameters to the correct values for your installation. Find the INIT.ORA file, which should be at: databaseOraclehome ADMIN dbname PFILE INIT.ORA where databaseOraclehome is the location to which the Oracle database was installed, and dbname is the database name (e.g. The name portion of the name. Domain global database name). If there is more than one Oracle database instance on the server, make sure that you locate the correct file.
Using a text editor or similar program, open the INIT.ORA file, check the current settings and make any necessary changes to the file. When you have finished, save your changes and close the INIT.ORA file. Step 3 - Start or Restart the Oracle Database If Necessary If the database is not already started, start it now. If the database is already started and you changed the INIT.ORA file in the previous step, shut down and restart the database. Step 4 - Ensure That TNS Listener Is Started You need to have a TNS Listener service running. This is a utility that handles database connection requests.
Under Windows, click Start Settings Control Panel Services. In the Services dialog box, if the service named Oracle databaseOraclehomeTNSListener does not show 'Started' in the Status field, select this service and click the Start button (where databaseOraclehome is the location to which the Oracle database was installed). Under UNIX, enter the command lsnrctl status. Under the heading 'Services Summary.' , check that there is an entry reading ' databasename has 1 service handler(s).' If there is no entry for the desired database, then at the LSNRCTL prompt, enter the command start.
When this has completed successfully, enter the command status and check again. Step 5 - (Oracle 9i only) Install Oracle 9i Import and Export Utilities Before installing Designer Repository on an Oracle 9i database, you need to set up the installation workstation to use the Oracle 9i import and export utilities.
To do so, perform the following steps at the workstation from which you will be running the repository installation:. From the Oracle 9i installation media, install the Oracle 9i import and export utilities in a dedicated Oracle home. In the Windows Registry, locate the key named: For Designer 10g - 9.0.4.x HKEYLOCALMACHINE SOFTWARE ORACLE HOMEn REPOS61 Designer 10g R2 onwards HKEYLOCALMACHINE SOFTWARE ORACLE KEY HomeName REPOS61 where KEY HomeName/ HOMEn is the home name of the oracle home where Designer is installed for a multiple Oracle home environment, but is not present where the default Oracle home is being used. Change the value of the EXECUTEIMPORT and EXECUTEEXPORT variables to point to the new Oracle home. Thus, if the new Oracle home is d: des9i, the settings would be: d: des9i bin exp.exe d: des9i bin imp.exe Installing a Repository (SQL Script Method) The SQL scripts available are shown, with a brief description, in the following table: 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 continuing 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. Ckcreatemb Same as ckcreate, but for use with a multibyte character-set database. Ckreport Creates a report (in the file CKREPORT.LST) on the database objects created by ckcreate or ckcreatemb. Ckclean Removes the repository, deleting all the database objects created by ckcreate or ckcreatemb. To install a new repository using the script method:.
If you have not done so already, perform the. Open a Command Prompt window and set the current directory to the one where the scripts are stored: cd d: Oraclehome repadm61 admin where Oraclehome is the Oracle home directory where the client tools were installed. From the Command Prompt window, start SQL.Plus: d: Oraclehome bin sqlplus. At the 'Enter user-name:' prompt, enter the full connect string in the form: sys/ psw@ host as sysdba The AS SYSDBA clause is mandatory for an Oracle9 i database. At the SQL prompt, enter: @ ckqa This script creates a file named CKPARAMS.TXT (in the same directory as the script files), based on the input you supply while the script is running. The script displays a number of prompts, for which the responses are shown in the following table: Prompt Response Enter TNS connect string for server The database alias (same as the host string in step 4).
Enter password for SYS The password for the SYS user (same as psw in step 4). Enter the repository size you wish to create. S, M or L for a small, medium or large repository (see earlier in this chapter). Dropping temporary table CKRAUTEMP None needed; ignore any message of the form 'ORA-00942: table or view does not exist.'
Enter datafile location and name for tablespace The name, and optionally the location, of the datafile for the repository tablespace indicated. Use a datafile name that clearly indicates the tablespace to which the file relates, e.g. SCMCGIND.ORA for CONSTANTGROWTHINDEXES. The default location is databaseOraclehome DATABASE.
To store the datafiles in a different location, enter the full pathname and file name. 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? Y (recommended - see earlier in this chapter). Hit enter to Continue with validation process. The script then validates your input. Please verify the above values.
Edit 'ckparams.txt' to make any changes. Then run ckparams.txt. Review the values listed on the screen. These will be the input for the ckcreate script. You should not normally need to change any of these values, but if you do want to make changes (e.g.
To increase the size of a tablespace) continue with step 6, otherwise go on to step 7. (Optional) If you want to make any changes to the parameter values, edit the file CKPARAMS.TXT, then save and close it. Run CKPARAMS.TXT by entering the following in the SQL.Plus window: @ ckparams.txt Validate the changes by entering the following: @ ckvalqa. Enter the following: @ ckcreatemb where the 'mb' extension is for use only with a multibyte character-set database. Ignore any message of the form 'ORA-01919: role 'CKORACLEREPOSOWNER' does not exist'.
(Optional) Run the report to list the database objects created: @ ckreport The report output is stored in the file CKREPORT.LST in the same directory as the script files. Exit from SQL.Plus and continue with the manual method at the point where you. Note that the scripts create the repository owner with the username REPOSMANAGER and the password MANAGER. We recommend that you change the password as soon as possible after installation is complete. Installing a Repository (Manual Method) Step 1 - Perform Pre-Installation Procedures If you have not done so already, perform the at the database server. The remaining steps take place at the client workstation from which you will be running the repository installation.
The current release of Oracle Designer 10 g or Oracle Designer Repository client software must be installed at this workstation. Step 2 - Create Tablespaces for the Repository Tables and Indexes For a production repository, we recommend that you create dedicated tablespaces as indicated earlier under. Proceed as follows:. Start SQL.Plus at the client. Connect to the database as SYS (for an Oracle9 i database, use the AS SYSDBA clause, for example SYS/ psw@ alias AS SYSDBA). To create a new tablespace, enter: create tablespace tbsname datafile ‘ filespec’ size nnk default storage (initial nnnk next nnnk minextents n maxextents unlimited pctincrease n); where tbsname is the name of the tablespace, and filespec is the complete file specification for the data file (default location is databaseOraclehome DATABASE).
Step 3 - Establish an Undo Tablespace or Rollback Segment for the Installation Oracle9 i Databases Using Automatic Undo If the database is operating in automatic undo mode (UNDOMANAGEMENT initialization parameter is set to AUTO), undo operations use a dedicated undo tablespace instead of a rollback segment. In many cases, an undo tablespace is created by default (e.g. With the name UNDOTBS) when the database is created.
If so, use that tablespace. If no undo tablespace exists, proceed as follows:. In SQL.Plus, enter: create undo tablespace tbsname datafile ‘ filespec’ size 10m;. Set the UNDOTABLESPACE parameter in the database initialization file (SPFILE or INIT.ORA as appropriate) to point to the new tablespace. Oracle9 i Databases Using Manual Undo You need at least one non-SYSTEM rollback segment for the installation.
The rollback segment must be online and have 10 MB free space. During installation, the Nominate Rollback Segment listbox is disabled and the method described in this step is the only way to ensure a specific rollback segment is used.
![Oracle windows service Oracle windows service](/uploads/1/2/5/4/125424953/580341742.gif)
You should ensure that the database that will host the repository has sufficient rollback segments to avoid contention for rollback segments. Refer to your Oracle database documentation for information about tuning the database to avoid resource contention. To create a new tablespace for the rollback segment: create tablespace tbsname datafile ‘ filespec’ size 10m; where tbsname is the name of the tablespace, and filespec is the complete file specification for the data file. To create the rollback segment and put it online: create rollback segment rbsname tablespace tbsname storage (initial 1m next 1m minextents 3 optimal 4m); alter rollback segment rbsname online; where rbsname is the name of the rollback segment, and tbsname is the name of the tablespace for the rollback segment. Step 4 - Check That the SYSTEM Tablespace Has 140 MB of Free Space The repository packages, procedures and views are stored in the SYSTEM tablespace, and need 140 MB of free space. To show the size in MB of free space in all the tablespaces, including SYSTEM: select tablespacename, sum(bytes)/1024/1024 from dbafreespace group by tablespacename; If there is not enough free space in the SYSTEM tablespace, you can use one of three methods to increase its size: resize a data file, add a data file, or use AUTOEXTEND. To increase the SYSTEM tablespace size by resizing a data file: alter database datafile ’ filespec’ resize nnm; where filespec is the complete file specification for the data file; nn is the new size in megabytes.
To increase the SYSTEM tablespace size by adding a data file: alter tablespace system add datafile ’ filespec’ size nnm; To set the AUTOEXTEND option on the current data file used for the SYSTEM tablespace: alter database datafile ’ filespec’ autoextend on; where filespec is the complete file specification for the original data file used for the SYSTEM tablespace. Use the AUTOEXTEND method with care, however, as it allows a data file to grow unchecked. Step 5 - Create the Repository Owner Create an Oracle user account that will be used for the repository owner and assign a default tablespace and a temporary tablespace to this user. To see which tablespaces are online: select tablespacename, status from dbatablespaces; To create the temporary tablespace for the repository owner: create tablespace temptbsname datafile ’ filespec’ size nnk temporary; where temptbsname is the name of the tablespace; filespec is the complete file specification for the data file; nn is the size in kilobytes (4500k is recommended). To create the repository owner: create user reposowner identified by password default tablespace dflttbsname temporary tablespace temptbsname; where:. reposowner is the username you want to use for the repository owner.
This is the username under which you will install the repository, and under which the repository will subsequently be administered. You cannot use the names SYSTEM or SYS for this. The tables, views and packages of the repository will be stored in the repository owner's schema. password is the password that the repository owner will use to log on to the repository. dflttbsname is the name of the default tablespace for the repository owner. If you have chosen to partition the repository (see ), you should use the tablespace that will be used for the rapid growth instance data.
If you will not be partitioning the repository, you can use any available tablespace. temptbsname is the name of the temporary tablespace for the repository owner, and is used for sort operations.
Step 6 - Log On to Windows at the Client If you have not done so already, log on to Windows at the client workstation from which you will be running the repository installation. Step 7 - Connect to the Database As SYS To be able to create the repository owner role (as described in the next step), you need to be connected to the database as user SYS. If you are not already connected as SYS, click the Start button, then choose Programs Oracle - databaseOracle home Application Development SQL Plus. In the Log On dialog box, fill in the fields as shown in the following table: Field Enter.
Notes User Name SYS (not SYSTEM) Password The password for SYS Host String databasealias AS SYSDBA The AS SYSDBA clause is mandatory for an Oracle9 i database. Step 8 - Create and Grant the Role CKORACLEREPOSOWNER for System Privileges. Create a role named CKORACLEREPOSOWNER for system privileges (you will grant this role to the repository owner later): @ Oraclehome repadm61 utl ckrorole.sql where Oraclehome is the directory to which Oracle Designer or Oracle Designer Repository was installed on the client workstation. This command runs a SQL script that creates the role CKORACLEREPOSOWNER and grants it a set of privileges.