Oracle® Database

Silent Installations that Use Automatic Storage Management

You cannot use the silent installation method to install Oracle Database 10g and create a database that uses Automatic Storage Management (ASM) for database storage during the same installation. This is because the root.sh script must run before the Database Configuration Assistant (DBCA) can start an ASM instance.

If you want to use the silent installation method to install Oracle Database 10g and create a database that uses ASM, follow these steps:

1. Use the enterprise.rsp response file to complete a software-only installation.

2. Run $ORACLE_HOME/root.sh after the installation completes.

3. Use the dbca.rsp response file to run DBCA in silent mode, using a command similar to the following:

   $ $ORACLE_HOME/bin/dbca -silent -responseFile /full_path/dbca.rsp
   

Automatic Storage Management Library Driver

On Linux Itanium systems, the ASM library driver is currently supported only on SuSE Linux Enterprise Server (SLES) 8.

Oracle CRS Installation on an Oracle9i RAC Cluster

If you install Oracle CRS on a system that also contains an Oracle9i Real Application Clusters (RAC) cluster, you must reboot all of the Oracle CRS nodes. You can reboot the nodes one at a time to avoid affecting any Oracle9i databases that may be in use.

Oracle assumes that when you install Oracle CRS 10g software, you will also install Oracle Real Application Clusters 10g. If there will be a significant delay before you perform phase two of the RAC installation to install Oracle Real Application Clusters 10g, then run the /crs_home/bin/gsdctl start command to start the GSD manually to service the 9.2 SRVCTL tool and assistants. Then before installing Oracle Real Application Clusters 10g, run the /crs_home/bin/gsdctl stop command to stop the GSD.

Oracle CRS Silent Installation

If you perform a silent installation of Oracle CRS on multiple nodes, on a system that does not have other Oracle installations, the Installer does not set up the Oracle Inventory correctly. In this case, after the installation is complete, follow these steps:

1. Run the orainstRoot.sh script on a local node.

2. Copy the oraInventory directory from the local node to each of the remote nodes.

3. Log in as the root user and run the following script on each remote node:

   oraInventory/orainstRoot.sh
   

Oracle CRS Installation Errors Caused by stty Commands

During an Oracle CRS installation, the Installer uses SSH (if available) to run commands and copy files to the other nodes. During the installation, you might see errors similar to the following if a "dot" file on the system (for example, .bashrc or .cshrc) contains stty commands:

 stty: standard input: Invalid argument 
 stty: standard input: Invalid argument 

To avoid this problem, Oracle recommends that you modify these files to suppress all output on STDERR, as follows:

• Bourne, Bash, or Korn shell:

  if [ -t 0 ]; then
     stty intr ^C
  fi
  
  

• C shell:

  test -t 0
  if ($status == 0) then
     stty intr ^C
  endif
  

This issue is tracked through Oracle bug 3414362.

ASM Instance Clean Up Procedures for Node Deletion

To remove the ASM instances, the delete node procedure requires the following additional steps on UNIX-based systems:

1. If this is the Oracle home from which the per-node listener named LISTENER_nodename runs, then use NetCA to remove this listener and its CRS resources. If necessary, re-create this listener in another Oracle home.

2. If this is the Oracle home from which the ASM instance runs, then enter the following commands to remove the ASM configuration:

   $ srvctl stop asm -n node
   $ remove asm -n node
   
   

3. If you are using a cluster file system for your ASM Oracle home, then run the following commands on the local node:

   $ rm -r $ORACLE_BASE/admin/+ASM
   $ rm -f $ORACLE_HOME/dbs/*ASM*
   
   

4. If you are not using a cluster file system for your ASM Oracle home, then run the rm commands listed in the previous step on each node on which the Oracle home exists.

5. Remove oratab entries beginning with +ASM.

Backing Up the Voting Disk after Installing RAC

After installing Oracle RAC 10g and after ensuring that the system is functioning properly, make a backup of the voting disk. In addition, make a backup of the voting disk contents after you complete any node additions or node deletions and after running any de-installation procedures.

Remote Undo Tablespaces Do Not Autoexetend in RAC Seed Databases

If you create a RAC database with two or more instances and you choose to create General Purpose, Transaction Processing, or Data Warehouse databases, and if you use a shared cluster file system or Automatic Storage Management (ASM) for database files, then the Database Configuration Assistant (DBCA) creates undo tablespace datafiles with an initial size of 25 MB and AUTOEXTEND ON for the local instance but AUTOEXTEND OFF for remote instances.

You can set AUTOEXTEND ON for undo tablespace datafiles for remote instances after creating a RAC database using DBCA as follows:

1. Connect to the database instance on the node from which you ran DBCA:

   $ sqlplus "/ AS SYSDBA"
   
   

2. Enter the following command to find the datafile names for UNDOTBS tablespaces for remote instances:

   SQL> SELECT file_name FROM SYS.DBA_DATA_FILES
        WHERE tablespace_name LIKE 'UNDOTBS%' AND AUTOEXTENSIBLE='NO';
   
   

3. Set AUTOEXTEND ON for the datafiles that you found in the previous step:

   SQL> ALTER DATABASE DATAFILE datafile_name AUTOEXTEND ON;
   
   

Oracle RAC 10g Installed on an OCFS

If you installed RAC on an Oracle Cluster File System (OCFS), after installation perform the following steps on each node of the cluster:

1. Stop the Oracle instance.

2. Move the $ORACLE_HOME/dbs/hc_*.dat files to a directory on a local file system.

3. Create symbolic links from the $ORACLE_HOME/dbs directory to the hc_*.dat files on the local file system.

4. Restart the Oracle instance.

Upgrading a Database

If you choose the Custom installation path and have previous versions of Oracle databases installed, then the Oracle Universal Installer gives you the option of upgrading the existing databases. If you choose to upgrade an existing database, the Oracle Universal Installer displays another screen asking whether you want to create a starter database.If you choose to create a starter database, the DBCA upgrades the older version of the database to Oracle Database 10g release 1 (10.1), but does not create a starter database.

Upgrading OPS Release 8.1.7 to Oracle RAC 10g

To upgrade Oracle Parallel Server (OPS) release 8.1.7 to Oracle RAC 10g:

1. Upgrade the OPS release 8.1.7 database to Oracle9i RAC release 2 (9.2).

2. Upgrade the Oracle9i RAC database to Oracle RAC 10g.

   
   

   Note: You cannot use the DBCA to upgrade an OPS release 8.1.7 database to Oracle RAC 10g.

   
   
   
   

   See Also: For information on upgrading an Oracle database, see the Oracle Database Upgrade Guide.

   
   

Using Shared CRS Home or Oracle Home Directories

For this release, Oracle supports shared CRS home and Oracle home directories on Linux only if they are located on a certified NAS device. This configuration is supported only if you also use the NAS device to store the Oracle database files.

Deinstalling CRS

After you deinstall CRS, enter the following command to delete the CRS scripts from the system runlevel directories:

$ rm -rf /etc/rc.d/rc*.d/*96init.crs

Running Oracle9i RAC with Oracle RAC 10g

If you are running Oracle9i RAC on the same cluster nodes as Oracle RAC 10g, complete the following steps:

1. Create the following directory:

   $ mkdir -p /etc/ORCLcluster/oracm/lib
   
   

2. Change directory to this directory:

   $ cd /etc/ORCLcluster/oracm/lib
   
   

3. Copy the /oracle9i_home/lib/libcmdll.so file to the current directory:

   $ cp /oracle9i_home/lib/libcmdll.so .
   
   

4. On any cluster node, enter commands similar to the following to restart the node applications on all cluster nodes:

   $ORACLE_HOME/bin/svrctl stop nodeapps -n nodename
   $ORACLE_HOME/bin/svrctl start nodeapps -n nodename
   
   

   In this example, $ORACLE_HOME is the Oracle RAC 10g Oracle home and nodename is the name of the node. Repeat the commands for each node in the cluster.

Using Network Attached Storage for RAC Installations

On Linux, you can use an NFS file system on a certified NAS device for storing Oracle software or database files. The file system that you use must have the same mount point path on all cluster nodes. In addition, you must use the following mount options when mounting the NFS file systems:

• Use the noac option to disable attribute caching.

• Use the tcp option to specify the TCP protocol.

• Verify that the NFS file system and the correct mount options are specified in the /etc/fstab file on every node to ensure that the file system is mounted when each node boots.

For more information about using NAS devices and NFS file systems:

• See OracleMetalink for information about certified NAS devices

• Contact your NAS vendor for specific recommendations about using the device with Oracle Real Application Clusters

• See Appendix C in the Oracle Database Installation Guide for UNIX Systems for general guidelines about using NAS devices for Oracle Database installations

Net Configuration Assistant Help

In the Net Configuration Assistant (NetCA) help, the link to the Select Oracle Context help topic is broken. The text for this topic is as follows:

Directory Usage Configuration, Select Oracle Context

Oracle administrative content has been found in more than one location in the directory. Oracle administrative content is stored in an Oracle Context, a subtree in the directory that stores Oracle entries.

From the list, select or enter the location you want to use as the default Oracle Context location from which this computer will access Oracle entries, such as connect identifiers.

Flashback Table or Flashback Analysis

If a user invokes the Flashback Table or Flashback Analysis operation, and that user has FLASHBACK ANY TABLE privileges but does not have specific flashback privileges on the objects that flashback is invoked on and does not have DBA privileges, then the following errors may occur:

ORA-02002: error while writing to audit trail 
ORA-00600: internal error code, arguments: [kzasps1], [4], [47], [],[],  

To fix this problem, as SYSDBA, grant the user FLASHBACK privilege on the objects that are referred to in the FLASHBACK TABLE statement and then invoke the flashback operation. For example:

SQL> GRANT FLASHBACK ON SCOTT.EMP_1 TO user1;

This issue is tracked through Oracle bug 3403666.

Oracle Workflow

Although Oracle Workflow is listed on the Companion CD installation screens, it is not included on the Companion CD for this release.

Enabling Automated Backups

While installing Oracle Database, the Specify Backup and Recovery Options screen may appear truncated if your system does not have the required fonts installed. If your system has only fixed-width fonts, you may not be able to fully specify the required information in the Backup Job Credentials area of the screen. To work around this issue, do not select Enable Automated Backups on this screen. After the installation is complete, use the Oracle Enterprise Manager 10g Database Control to enable automated backups.

Oracle Internet Directory

This release includes the Oracle Internet Directory (OID) client tools, but it does not include OID server components. OID server components are included with Oracle Application Server 10g. If you require the OID server tools for Oracle Database components, then run them from an Oracle Application Server 10g installation.

The OID client tools include:

• LDAP command-line tools

• Oracle Internet Directory SDK

• Oracle Directory Manager

The OID server components include the following servers and tools for starting and stopping them:

• Directory server

• Directory replication server

• Directory integration server

Error When Viewing Period SQL Execution Plan in Korean

Viewing the execution plan of a Period SQL in Korean causes an internal server error. This problem is unique to Korean; it does not reproduce in Japanese or Chinese. The only workaround currently available is to run the product in a language other than Korean when you need to view this page.

Quick Tour Not Available in Oracle Change Management Pack

Quick Tour is not available in Oracle Change Management Pack. If you try to run it, then an error results.

extjob Executable Required Directory Permissions

To enable the extjob executable to locate required libraries, the /oracle_home/lib directory and all of its parent directories must have execute permissions for group and other.

Grid Features

Oracle Database New Features for Oracle Database 10g release 1 (10.1) lists two Grid features that are not available in the first release of Oracle Database 10g; Resonance and Transparent Session Migration. These features will be available in a future release.

Removing Cloned Oracle Homes

If you use the Installer to remove a cloned Oracle home, and the cloned Oracle home is on the same system as the source Oracle home, the Installer removes essential files from the source Oracle home. To avoid this issue, remove the cloned Oracle home as follows:

1. Remove the cloned Oracle home manually by deleting the cloned Oracle home directory.

2. Start the Installer from the source Oracle home directory:

   $ source_oracle_home/oui/bin/runInstaller
   
   

3. In the Welcome window, click Deinstall Products.

   The Inventory window appears, listing all of the Oracle homes on the system.

4. In the Inventory window, select the cloned Oracle home, then click Remove.

This issue is tracked through Oracle bug 3417663.

Network Utilization Metrics Not Displayed

The Oracle Enterprise Manager Grid Control or Database Control should display the following network utilization metrics for each network interface:

• Network Interface Combined Utilization (%)

• Network Interface Read Utilization (%)

• Network Interface Write Utilization (%)

If these metrics are not displayed for a particular network interface, create the $ORACLE_HOME/sysman/config/network_speed file and enter the network interface name and speed in the file as follows. In this example, interface is the network interface name and speed is the speed of the interface in megabits per second (Mbps):

interface_name speed

For example, if the eth0 network interface does not display metrics, create the $ORACLE_HOME/sysman/config/network_speed file and enter the following, where 100 is the network speed in Mbps:

eth0 100

Generic Connectivity

Oracle Database 10g supports generic connectivity (hsodbc) only on Linux x86 systems.

Oracle Transparent Gateway for DRDA

Oracle Transparent Gateway for DRDA is available on Linux systems.

Using the Intel C++ Compiler for PL/SQL Native Compilation

By default, PL/SQL native compilation is configured to use the Gnu gcc compiler. To use the Intel C++ compiler (ecc) instead of the gcc compiler, make the following changes in the $ORACLE_HOME/plsql/spnc_commands file:

• Comment out the commands for gcc.

• Uncomment the commands for ecc.

Building Pro*C Applications if PostgreSQL is Installed

If the postgresql-devel package is installed on the system, add the following directory to the beginning of the sys_include parameter in the $ORACLE_HOME/precomp/admin/pcscfg.cfg file before building Pro*C applications:

$ORACLE_HOME/precomp/public

If you do not make this change, you may encounter errors similar to the following when linking the applications:

/tmp/ccbXd7v6.o(.text+0xc0): In function `drop_tables': 
: undefined reference to `sqlca' 

Linking Applications With Oracle Client Libraries

If your client application is compiled using a version of glibc other than version 2.2.4, you must link it with the client shared library. The use of the client static library is not supported.

$ORACLE_HOME/lib/stubs

OCCI Applications on Red Hat Enterprise Linux AS 2.1

On Red Hat Enterprise Linux AS 2.1, Oracle C++ Call Interface (OCCI) requires the gcc-c++-2.96-124.7.2 package. This package supersedes the version listed in the installation documentation.

OCCI Applications on Red Hat Enterprise Linux 3

There is a problem using Oracle C++ Call Interface (OCCI) with gcc version 2.96.122. This problem will be fixed in gcc version 2.96.124. Contact Red Hat for information on how to obtain gcc version 2.96.124. This problem is tracked through Oracle bug 2648903.

OCCI Support for SuSE Linux Enterprise Server 8

For this release, OCCI is not supported on SuSE Linux Enterprise Server (SLES) 8. This issue is tracked through Oracle bug 3426344.

Java VM Natively Compiled Libraries Tool

The client side Java VM natively compiled libraries tool is not supported on Red Hat Enterprise Linux 3 on Linux Itanium.

Installing Oracle HTTP Server on Red Hat Enterprise Linux 3

If you are installing Oracle HTTP Server (Apache Standalone) from the Companion CD on Red Hat Enterprise Linux 3 systems, the following package is required in addition to the packages listed in the Oracle Database Companion CD Installation Guide for UNIX Systems, part numbers B10886- 01 and B10886- 02:

gnome-libs-1.4.1.2.90-34.1

XDK Demonstrations

For this release, you cannot dynamically link XDK demonstrations on Linux systems.

Pro*COBOL Precompiler Support

The Pro*COBOL precompiler is not supported.

gensyslib Script

If requested by Oracle Support Services to run the gensyslib script, you must set the value of the BUILD_CC environment variable to TRUE before you run the script. This issue is tracked through Oracle bug 3496185.

Installing Enterprise Security Manager

To install Enterprise Security Manager (ESM), install Oracle Client and choose the Administrator installation type.

Updates for Real Application Clusters Documentation

The following sections describe corrections and supplemental information for the Oracle Real Application Clusters 10g documentation for UNIX platforms:

• Installing Oracle CRS

• De-Installation Procedure Change for UNIX-Based Systems

• Adding Nodes

• Deleting Nodes

• OCFS Requirement for RAC on Linux Systems

• Real Application Clusters Services Deployment Example

• Pre-Installation Tasks for Installing RAC on Linux-Based Systems

• Running DBCA on RAC

ORACLE_HOME/bin/localconfig delete

SRV_PRECONNECT VERSION=1.0 service=db_unique_name.db_domain 
database=database_name instance instance_name host=host_name 
status=preconn_up reason=timestamp=27-Jan-2004 16:53:58 
reported=Tue Jan 27 16:53:59 PST 2004 

SRV_PRECONNECT VERSION=1.0 service=db_unique_name.db_domain
database=database_name instance=instance_name host=host_name
status=preconn_down reason=timestamp=27-Jan-2004 16:58:01
reported=Tue Jan 27 16:58:02 PST 2004

@ SRV_PRECONNECT VERSION=1.0 service=MYSERV.us.oracle.com 
database=RACEY instance=RACEY1 host=sun880-1 
status=preconn_up reason=timestamp=27-Jan-2004 16:53:58
reported=Tue Jan 27 16:53:59 PST 2004 

@ SRV_PRECONNECT VERSION=1.0 service=MYSERV.us.oracle.com
database=RACEY instance=RACEY1 host=sun880-1 
status=preconn_down reason=timestamp=27-Jan-2004 16:58:01
reported=Tue Jan 27 16:58:02 PST 2004

sys_context('userenv', 'instance_name');
sys_context('userenv', 'server_host');
sys_context('userenv', 'service_name');
sys_context('userenv', 'db_unique_name');

Updates for Other Documentation

The following sections contain updates to the Oracle Database 10g documentation:

• Installing Oracle HTML DB

• Globalization Support

• Full-Text Searching with Oracle Text

• View Descriptions

• Configuring Management Service Processes

• Monolingual Linguistic Sorting

• XDK Error Messages

• Support for Hearing and Speech Impaired Customers

CREATE TABLE PurchaseOrder of XMLTYPE
  XMLSCHEMA http://localhost:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd
  ELEMENT "PurchaseOrder"
  VARRAY "XMLDATA"."ACTIONS"."ACTION"
    STORE AS TABLE ACTION_TABLE ((PRIMARY KEY 
       (NESTED_TABLE_ID, ARRAY_INDEX)))
  VARRAY "XMLDATA"."LINEITEMS"."LINEITEM"
     STORE AS TABLE LINEITEM_TABLE ((PRIMARY KEY 
       (NESTED_TABLE_ID, ARRAY_INDEX)));

http://otn.oracle.com/tech/xml/doc/production10g/Javaerrormsgs.html