4 Oracle Database Postinstallation Tasks

4.1.1 Downloading and Installing Patches

Check the OracleMetaLink Web site for required patches for the installation.

To download required patches:

1. Use a Web browser to view the OracleMetaLink Web site:

   https://metalink.oracle.com
   
   

2. Log in to OracleMetaLink.

   Note:

   If you are not an OracleMetaLink registered user, click Register for MetaLink! and follow the registration instructions.

3. On the main OracleMetaLink page, click Patches & Updates.

4. Select Simple Search.

5. Specify the following information, then click Go:

   • In the Search By field, choose Product or Family, then specify RDBMS Server.

   • In the Release field, specify the current release number.

   • In the Patch Type field, specify Patchset/Minipack.

   • In the Platform or Language field, select your platform.

6. Find the latest patch set for Oracle Database using OracleMetaLink.

7. From the list of available patches, select a patch to download.

   Patch sets for Oracle databases are identified as x.x.x PATCH SET FOR ORACLE DATABASE SERVER.

8. Review the README file before proceeding with the download.

   Each patch has a README file with installation requirements and instructions. Some patches install with Oracle Universal Installer; others require special procedures. Oracle recommends that you always read the README file before proceeding.

9. Download and install the patch.

4.1.2 Configuring Oracle Products

Many Oracle products and options must be configured before you use them for the first time. Before using individual Oracle products or options, refer to the appropriate manual in the product documentation library.

4.2.1 Creating a Backup of the root.sh Script

Oracle recommends that you back up the root.sh script after you complete an installation. If you install other products in the same Oracle home directory, then Oracle Universal Installer updates the contents of the existing root.sh script during the installation. If you require information contained in the original root.sh script, then you can recover it from the backed up root.sh file.

4.2.2 Configuring New or Upgraded Databases

Oracle recommends that you run the utlrp.sql script after creating or upgrading a database. This script recompiles all PL/SQL modules that might be in an invalid state, including packages, procedures, and types. This is an optional step but Oracle recommends that you do it during installation and not at a later date.

To run the utlrp.sql script, follow these steps:

1. Switch user to oracle.

2. Use the oraenv or coraenv script to set the environment for the database where you want to run the utlrp.sql script:

   • Bourne, Bash, or Korn shell:

     $ . /usr/local/bin/oraenv
     
     

   • C shell:

     % source /usr/local/bin/coraenv
     
     

   When prompted, specify the SID for the database.

3. Start SQL*Plus, as follows:

   $ sqlplus "/ AS SYSDBA"
   
   

4. If necessary, start the database:

   SQL> STARTUP
   
   

5. Run the utlrp.sql script:

   SQL> @?/rdbms/admin/utlrp.sql
   
   

4.2.3 Setting Up User Accounts

For information about setting up additional user accounts, refer to Oracle Database Administrator's Reference for Linux and UNIX.

4.2.4 Setting the NLS_LANG Environment Variable

NLS_LANG is an environment variable that specifies the locale behavior for Oracle software. This variable sets the language and territory used by the client application and the database server. It also declares the character set of the client, which is the character set of data entered or displayed by an Oracle client program, such as SQL*Plus.

4.2.5 Generating the Client Static Library

The client static library (libclntst11.a) is not generated during installation. If you want to link the applications to the client static library, you must first generate it as follows:

1. Switch user to oracle.

2. Set the ORACLE_HOME environment variable to specify the Oracle home directory used by the Oracle Database installation. For example:

   • Bourne, Bash, or Korn shell:

     $ ORACLE_HOME=/u01/app/oracle/product/11.1.0/db_1 
     $ export ORACLE_HOME
     
     

   • C shell:

     % setenv ORACLE_HOME /u01/app/oracle/product/11.1.0/db_1
     
     

3. Enter the following command:

   $ $ORACLE_HOME/bin/genclntst
   

4.2.6 Direct NFS Client

Network-attached storage (NAS) systems use NFS to access data. You can store data files on a supported NFS system.

With Oracle Database 11g, instead of using the operating system kernel NFS client, you can configure Oracle Database to access NFS V3 servers directly using an Oracle internal Direct NFS client.

If Oracle Database is unable to open an NFS server using Direct NFS, then Oracle Database uses the platform operating system kernel NFS client. In this case, the kernel NFS mount options must be set up as defined in "Checking NFS Buffer Size Parameters" . Additionally, an informational message will be logged into the Oracle alert and trace files indicating that Direct NFS could not be established.

The Oracle files resident on the NFS server that are served by the Direct NFS Client are also accessible through the operating system kernel NFS client. The usual considerations for maintaining integrity of the Oracle files apply in this situation.

Some NFS file servers require NFS clients to connect using reserved ports. If your filer is running with reserved port checking, then you must disable it for Direct NFS to operate. To disable reserved port checking, consult your NFS file server documentation.

Direct NFS can use up to four network paths defined for an NFS server. The Direct NFS client performs load balancing across all specified paths. If a specified path fails, then Direct NFS reissues I/Os over any remaining paths.

Use the following views for Direct NFS management:

• v$dnfs_servers: Shows a table of servers accessed using Direct NFS.

• v$dnfs_files: Shows a table of files currently open using Direct NFS.

• v$dnfs_channels: Shows a table of open network paths (or channels) to servers for which Direct NFS is providing files.

• v$dnfs_stats: Shows a table of performance statistics for Direct NFS.

The following sections elaborate on enabling, disabling, checking the buffer size for a Direct NFS Client:

• Enabling Direct NFS Client

• Disabling Direct NFS Client

• Checking NFS Buffer Size Parameters

nfs_server:/vol/DATA/oradata /home/oracle/netapp nfs\
rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp,actimeo=0,vers=3,timeo=600

4.3.1 Configuring Oracle Net Services

If you have an earlier release of Oracle software installed on this system, you might want to copy information from the Oracle Net tnsnames.ora and listener.ora configuration files from the earlier release to the corresponding files for the new release. The following sections describe about how to configure the Oracle Net Services:

• Modifying the listener.ora File

• Modifying the tnsnames.ora File

Modifying the listener.ora File

If you are upgrading from a earlier release of Oracle Database, Oracle recommends that you use the current release of Oracle Net listener instead of the listener from the earlier release.

To use the listener from the current release, you may need to copy static service information from the listener.ora file from the earlier release to the version of that file used by the new release.

For any database instances earlier than release 8.0.3, add static service information to the listener.ora file. Oracle Database releases later than release 8.0.3 do not require static service information.

Modifying the tnsnames.ora File

Unless you are using a central tnsnames.ora file, copy Oracle Net service names and connect descriptors from the earlier release tnsnames.ora file to the version of that file used by the new release.

If necessary, you can also add connection information for additional database instances to the new file.

4.3.2 Configuring Oracle Label Security

If you installed Oracle Label Security, you must configure it in a database before you use it. You can configure Oracle Label Security in two ways; with Oracle Internet Directory integration and without Oracle Internet Directory integration. If you configure Oracle Label Security without Oracle Internet Directory integration, you cannot configure it to use Oracle Internet Directory at a later stage.

4.3.3 Configuring Oracle Messaging Gateway

To configure Oracle Messaging Gateway, refer to the section about Messaging Gateway in Oracle Streams Advanced Queuing User's Guide. When following the instructions listed in that manual, refer to this section for additional instructions about configuring the listener.ora, tnsnames.ora, and mgw.ora files.

4.3.4 Configuring Oracle Precompilers

This section describes postinstallation tasks for Oracle precompilers:

• Configuring Pro*C/C++

• Configuring Pro*FORTRAN

4.3.5 Configuring Secure Sockets Layer

Oracle highly recommends you configure and use a Secure Sockets Layer (SSL) to ensure that passwords and other sensitive data are not transmitted in clear text in HTTP requests.

4.3.6 Installing Oracle Text Supplied Knowledge Bases

An Oracle Text knowledge base is a hierarchical tree of concepts used for theme indexing, ABOUT queries, and deriving themes for document services. If you plan to use any of these Oracle Text features, then you can install two supplied knowledge bases (English and French).

4.4.1 Migrating User Settings from Release 1.0

The first time you start SQL Developer after installing it or after adding any extensions, you are asked if you want to migrate your user settings from a previous release. (This occurs regardless of whether there was a previous release on your system.)

These settings refer to database connections, reports, and certain SQL Developer user preferences that you set in a previous version by clicking Tools and then Preferences. However, some user preferences are not saved, and you must re-specify these using the new release.

To migrate user settings from SQL Developer release 1.0:

1. Unzip the release 1.1 kit into an empty directory (folder). Do not delete or overwrite the directory into which you unzipped the release 1.0 kit.

2. When you start SQL Developer release 1.1, click Yes when asked if you want to migrate settings from a previous release.

3. In the dialog box that is displayed, do not accept the default location for the settings. Instead, specify the location of your release 1.0 settings, which might be a folder whose path ends with sqldeveloper/jdev/system.

See also "Migrating Information from Previous Releases".

4.4.2 Migrating Information from Previous Releases

If you have used a previous release of SQL Developer or a pre-release version of the current release, you may want to preserve database connections that you have been using. To preserve database connections, save your existing database connections in an XML file. To save the connections, right-click the Connections node in the Connections Navigator and select Export Connections. After you complete the installation described in this guide, you can use those connections by right-clicking the Connections node in the Connections Navigator and selecting Import Connections

If you want to use any user-defined reports or the SQL history from a previous version, see "Location of User-Related Information" for information about where these are located. If you want to use any user-defined reports or the SQL history from release 1.0 with both releases 1.0 and 1.1, you must save them before using release 1.1, because release 1.1 modifies the files to a format that is incompatible with release 1.0.

SQL Developer preferences (specified by clicking Tools and then Preferences) from a pre-release version of the current release cannot currently be saved and reused; you must re-specify any desired preferences.

4.4.3 Location of User-Related Information

SQL Developer stores user-related information in several places, with the specific location depending on the operating system and certain environment specifications. User-related information includes user-defined reports, user-defined snippets, SQL Worksheet history, and SQL Developer user preferences.

The user-related information is stored outside the SQL Developer installation directory hierarchy, so that it is preserved if you delete that directory and install a new version. This information is stored in or under the SQLDEVELOPER_USER_DIR location, if defined; otherwise as indicated in the following table.

The table shows the typical default locations (under a directory or in a file) for specific types of resources on different operating systems. (Note the period in the name of any directory or folder named .sqldeveloper.)

SQL Worksheet archive files contain SQL statements that you have entered. These files begin with sqldev and then have a random number (for example, sqldev14356.sql). If you close SQL Developer with a SQL Worksheet open that contains statements, then you will be prompted to save these files.

To specify a nondefault SQLDEVELOPER_USER_DIR location, do either of the following:

• Set the SQLDEVELOPER_USER_DIR environment variable to specify another directory path.

• Edit the sqldeveloper_install\sqldeveloper\sqldeveloper\bin\sqldeveloper.conf file and substitute the desired directory path for SQLDEVELOPER_USER_DIR in the following line:

  SetUserHomeVariable SQLDEVELOPER_USER_DIR
  
  

If you want to prevent other users from accessing your user-specific SQL Developer information, you must ensure that the appropriate permissions are set on the directory where that information is stored or on a directory preceding it in the path hierarchy. For example, you may want to ensure that the ~/.sqldeveloper directory is not world-readable.

4.5.1 Restarting Processes

After you install Oracle Application Express, you need to restart the processes that you stopped before you began the installation, such as listener and other processes. In addition, restart Oracle HTTP Server.

4.5.2 Choosing a HTTP Server

In order to run, Oracle Application Express must have access to either the embedded PL/SQL gateway or Oracle HTTP Server and mod_plsql.

Topics in this section include:

• About the Embedded PL/SQL Gateway

• About Oracle HTTP Server and mod_plsql

• About Password Security

4.5.3 Configuring the Embedded PL/SQL Gateway

Although the embedded PL/SQL gateway installs with the Oracle database, you must configure it before you can use it with Oracle Application Express. To accomplish, you run a configuration file and unlock the ANONYMOUS account.

Topics in this section include:

• Configuring the Embedded PL/SQL Gateway in New Installation or When Upgrading Database

• Disabling and Enabling the Oracle XML DB HTTP Server

4.5.4 Copying the Images Directory

Whether you are loading a new installation or upgrading from a previous release, you must copy the images directory from the top level of the $ORACLE_HOME/apex directory to the location on the file system containing the Oracle home for Oracle HTTP Server.

Topics in this section include:

• Copying the Images Directory After an Upgrade

• Copying the Images Directory After a New Installation

cp -rf $ORACLE_HOME/apex/images ORACLE_HTTPSERVER_HOME/ohs

4.5.5 Configuring Oracle HTTP Server in a New Installation

This section describes how to configure Oracle HTTP Server with mod_plsql in a new installation.

Topics in this section include:

• Configuring Oracle HTTP Server Release 9.0.3 in a New Installation

• Configuring Oracle HTTP Server distributed with Oracle Database 11g or Oracle Application Server 10g in a New Installation

ORACLE_HTTPSERVER_HOME/opmn/bin/opmnctl stopproc ias-component=HTTP_Server
ORACLE_HTTPSERVER_HOME/opmn/bin/opmnctl startproc ias-component=HTTP_Server

4.5.6 Enabling Network Services in Oracle Database 11g

By default, the ability to interact with network services is disabled in Oracle Database 11g release 1 (11.1). Therefore, if you are running Oracle Application Express with Oracle Database 11g release 1 (11.1), you need to use the new DBMS_NETWORK_ACL_ADMIN package to grant connect privilege to any host for the FLOWS_030000 database user. Failing to grant these privileges results in issues with the following:

• Sending outbound mail in Oracle Application Express.

  Users can call methods from the APEX_MAIL package, but issues arise when sending outbound email.

• Using Web services in Oracle Application Express.

• PDF/report printing.

• Searching for content in online Help (that is, using the Find link).

This section contains the following topics:

• Granting Connect Privileges

• Troubleshooting an Invalid ACL Error

Granting Connect Privileges

The following example demonstrates how to grant connect privileges to any host for the FLOWS_030000 database user.

DECLARE
ACL_PATH VARCHAR2(4000);
ACL_ID RAW(16);
BEGIN
-- Look for the ACL currently assigned to '*' and give FLOWS_030000
-- the "connect" privilege if FLOWS_030000 does not have the privilege yet.
SELECT ACL INTO ACL_PATH FROM DBA_NETWORK_ACLS
WHERE HOST = '*' AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL;
 
-- Before checking the privilege, make sure that the ACL is valid
-- (for example, does not contain stale references to dropped users).
-- If it does, the following exception will be raised:
--
-- ORA-44416: Invalid ACL: Unresolved principal 'FLOWS_030000'
-- ORA-06512: at "XDB.DBMS_XDBZ", line ...
--
SELECT SYS_OP_R2O(extractValue(P.RES, '/Resource/XMLRef')) INTO ACL_ID
FROM XDB.XDB$ACL A, PATH_VIEW P
WHERE extractValue(P.RES, '/Resource/XMLRef') = REF(A) AND
EQUALS_PATH(P.RES, ACL_PATH) = 1;
 
DBMS_XDBZ.ValidateACL(ACL_ID);
 
IF DBMS_NETWORK_ACL_ADMIN.CHECK_PRIVILEGE(ACL_PATH, 'FLOWS_030000', 'connect')
IS NULL THEN
DBMS_NETWORK_ACL_ADMIN.ADD_PRIVILEGE(ACL_PATH,
'FLOWS_030000', TRUE, 'connect');
END IF;
 
EXCEPTION
-- When no ACL has been assigned to '*'.
WHEN NO_DATA_FOUND THEN
DBMS_NETWORK_ACL_ADMIN.CREATE_ACL('power_users.xml',
'ACL that lets power users to connect to everywhere',
'FLOWS_030000', TRUE, 'connect');
DBMS_NETWORK_ACL_ADMIN.ASSIGN_ACL('power_users.xml','*');
END;
/
COMMIT;

Troubleshooting an Invalid ACL Error

If you receive an ORA-44416: Invalid ACL error after running the previous script, use the following query to identify the invalid ACL:

REM Show the dangling references to dropped users in the ACL that is assigned
REM to '*'.

SELECT ACL, PRINCIPAL
FROM DBA_NETWORK_ACLS NACL, XDS_ACE ACE
WHERE HOST = '*' AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL AND
NACL.ACLID = ACE.ACLID AND
NOT EXISTS (SELECT NULL FROM ALL_USERS WHERE USERNAME = PRINCIPAL);
 

Next, run the following code to fix ACL:

DECLARE
  ACL_ID   RAW(16);
  CNT      NUMBER;
BEGIN
 
-- LOOK FOR THE OBJECT ID OF THE ACL CURRENTLY ASSIGNED TO '*'
SELECT ACLID INTO ACL_ID FROM DBA_NETWORK_ACLS
WHERE HOST = '*' AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL;
 
-- IF JUST SOME USERS REFERENCED IN THE ACL ARE INVALID, REMOVE JUST THOSE
-- USERS IN THE ACL. OTHERWISE, DROP THE ACL COMPLETELY.
SELECT COUNT(PRINCIPAL) INTO CNT FROM XDS_ACE
WHERE ACLID = ACL_ID AND
EXISTS (SELECT NULL FROM ALL_USERS WHERE USERNAME = PRINCIPAL);
 
  IF (CNT > 0) THEN

    FOR R IN (SELECT PRINCIPAL FROM XDS_ACE
               WHERE ACLID = ACL_ID AND
                     NOT EXISTS (SELECT NULL FROM ALL_USERS
                                  WHERE USERNAME = PRINCIPAL)) LOOP
      UPDATE XDB.XDB$ACL
         SET OBJECT_VALUE =
               DELETEXML(OBJECT_VALUE,
                         '/ACL/ACE[PRINCIPAL="'||R.PRINCIPAL||'"]')
       WHERE OBJECT_ID = ACL_ID;
    END LOOP;

  ELSE
    DELETE FROM XDB.XDB$ACL WHERE OBJECT_ID = ACL_ID;
  END IF;

END;
/
 
REM Commit the changes.
 
COMMIT;

Once the ACL has been fixed, you need to run the first script in this section to apply the ACL to the FLOWS_030000 user. See "Granting Connect Privileges".

4.5.7 Installing Oracle Application Express in Other Languages

The Oracle Application Express interface is translated into German, Spanish, French, Italian, Japanese, Korean, Brazilian Portuguese, Simplified Chinese, and Traditional Chinese. A single instance of Oracle Application Express can be installed with one or more of these translated versions. At runtime, each user's Web browser language settings determine the specific language version.

The translated version of Oracle Application Express should be loaded into a database that has a character set that can support the specific language. If you attempt to install a translated version of Oracle Application Express into a database that does support the character encoding of the language, the installation may fail or the translated Oracle Application Express instance may appear corrupt when run. The database character set AL32UTF8 supports all the translated versions of Oracle Application Express.

You can manually install translated versions of Oracle Application Express using SQL*Plus. The installation files are encoded in AL32UTF8.

The following examples illustrate valid NLS_LANG settings for loading Oracle Application Express translations:

American_America.AL32UTF8
Japanese_Japan.AL32UTF8 

To install a translated version of Oracle Application Express:

1. Set the NLS_LANG environment variable, making sure that the character set is AL32UTF8. For example:

   • Bourne or Korn shell:

     $ NLS_LANG=American_America.AL32UTF8
     $ export NLS_LANG
     
     

   • C shell:

     % setenv NLS_LANG American_America.AL32UTF8
     
     

2. Start SQL*Plus and connect to the target database as SYS.

3. Execute the following statement:

   SQL> ALTER SESSION SET CURRENT_SCHEMA = FLOWS_030000;
   
   

4. Execute the appropriate language specific script. For example:

   SQL> @load_de.sql
   
   

   The installation scripts are located in subdirectories identified by a language code in the unzipped distribution $ORACLE_HOME/apex/builder. For example, the German version is located in $ORACLE_HOME/apex/builder/de and the Japanese version is located in $ORACLE_HOME/apex/builder/ja. Within each of these directories, there is a language loading script identified by the language code (for example, load_de.sql or load_ja.sql).

4.5.8 Managing JOB_QUEUE_PROCESSES

JOB_QUEUE_PROCESSES determine the maximum number of concurrently running jobs. In Oracle Application Express release 3.0, transactional support and SQL scripts require jobs. If JOB_QUEUE_PROCESSES is not enabled and working properly, you cannot successfully execute a script.

Topics in this section include:

• Viewing the Number of JOB_QUEUE_PROCESSES

• Changing the Number of JOB_QUEUE_PROCESSES

> SELECT VALUE FROM v$parameter WHERE NAME = 'job_queue_processes'

4.5.9 Obfuscating PlsqlDatabasePassword Parameter

The PlsqlDatabasePassword parameter specifies the password for logging in to the database. You can use the dadTool.pl utility to obfuscate passwords in the dads.conf file.

You can find the dadTool.pl utility in the following directory:

ORACLE_HTTPSERVER_HOME/ohs/modplsql/conf

4.5.10 Logging In to Oracle Application Express

You access the Oracle Application Express home page in a Web browser. To view or develop Oracle Application Express applications, the Web browser must support JavaScript and the HTML 4.0 and CSS 1.0 standards. See "Browser Requirements".

Topics in this section include:

• Application Express User Roles

• Setting Up Your Local Environment

4.5.11 Patching Oracle Application Express 3.0

If you are already running Oracle Application Express 3.0, then check the Oracle Application Express page on the Oracle Technology Network (OTN) at (http://www.oracle.com/technology/products/database/application_express/index.html) URL for information about patch set releases or later versions of Oracle Application Express:

Upgrading to Oracle Database 11g will not patch an Application Express 3.0 instance to Application Express 3.0.1.

4.6.1 Preparing Pre-9.2 Databases

Before running the installCCRSQL.sh script to prepare the database for configuration collection, you must perform the following steps for pre 9.2 databases:

1. Edit the initsid.ora file where sid is the database system identifier, and set the UTL_FILE_DIR parameter to include $ORACLE_HOME/ccr/state as one of the directories.

   If a server parameter file (spfile) is used, alter the UTL_FILE_DIR parameter using the following SQL*Plus command:

   SQL>alter system set utl_file_dir=value scope=spfile 
   
   

   where value is equal to $ORACLE_HOME/ccr/state

2. Restart the database.

4.6.2 Instrumenting the Database for Configuration Collections

To configure the database for configuration collection, run the following script:

• Run the following command to create the admin directory

  $ORACLE_HOME/ccr/bin/setupCCR
  
  

• Run the following script, to configure the database for configuration collection:

  $ORACLE_HOME/ccr/admin/scripts/installCCRSQL.sh collectconfig -s SID -r SYSDBA-USER -p SYSDBA-PASSWORD
  
  

However, only to configure the database for configuration collection, run the following script:

$ORACLE_HOME/ccr/admin/scripts/installCCRSQL.sh collectconfig -s SID -r SYSDBA-USER -p SYSDBA-PASSWORD

The installCCRSQL.sh script creates an Oracle Configuration Manager user and loads the PL/SQL procedure into the database defined by the ORACLE_SID. You can also specify the database SID by using the -s option in the command line as in the following example where the SID is orcl:

$ORACLE_HOME/ccr/admin/scripts/installCCRSQL.sh collectconfig -s orcl

By default, the connection to the database is through operating system authentication, "/as sysdba." To specify a different SYSDBA user and password, you can use these options:

-r SYSDBA-USER: The login name of the SYSDBA user

-p SYSDBA-PASSWORD: The password for the SYSDBA user

4.6.3 Additional Step for E-Business Suites

If the database is used as a repository for an Oracle E-Business Suite, you must also run the following script from the ORACLE_HOME in which the E-Business database has been hosted:

$ORACLE_HOME/ccr/admin/scripts/installCCRSQL.sh ebs_collectconfig -u Oracle_Applications_User 

The -u parameter is mandatory. If you do not specify this parameter, the application prompts you for the Oracle Applications User. If the -u parameter is specified, you will be prompted for the Oracle Applications Password.

If you want to automate the install, you can run the installCCRSQL.sh script with an additional -w option to specify the Oracle Applications Password. For example:

$ORACLE_HOME/ccr/admin/scripts/installCCRSQL.sh ebs_collectconfig -u Oracle_Applications_User -w Oracle_Applications_Password

You can add the -s SID command to specify the SID of the Oracle Applications Database instance.

If you are not using operating system authentication to connect to the database, you must use the -r and -p parameters to specify the following:

-r SYSDBA-USER: The login name of the SYSDBA user

-p SYSDBA-PASSWORD: The password for the SYSDBA user

If the -r parameter is specified, the -p parameter is optional and will be prompted for.

4.6.4 Additional Step for Oracle Enterprise Manager Grid Control

If the database is used as a repository for Oracle Enterprise Manager Grid Control, you must also run the following script:

$ORACLE_HOME/ccr/admin/scripts/installCCRSQL.sh collectemrep

When you run this command, then the application prompts you for the SYSMAN password. If you want to automate the install, you can run the installCCRSQL.sh script to specify the SYSMAN password. For example:

$ORACLE_HOME/ccr/admin/scripts/installCCRSQL.sh collectemrep -e SYSMAN PASSWORD

You can add the -s SID command to specify the SID of the Oracle Enterprise Manager Grid Control Database instance. You must run this script from the ORACLE_HOME in which the Oracle Enterprise Manager Grid Control database has been hosted.

If you are not using operating system authentication to connect to the database, you must use the -r and -p parameters to specify the following:

-r SYSDBA-USER: The login name of the SYSDBA user

-p SYSDBA-PASSWORD: The password for the SYSDBA user

If the -r parameter is specified, the -p parameter is optional and will be prompted for.