Oracle® Database

1.1 Oracle Real Application Clusters Installation and Configuration Guide

The Oracle Real Application Clusters Installation and Configuration Guide has been revised. You can download a copy of the revised book, part number B10766-08, from the Documentation section of the OTN Web site:

http://oracle.com/technology/documentation

1.2 Creating Raw Logical Volumes

If you are using raw logical volumes to store Oracle datafiles, Oracle recommends that you use a command similar to the following to create logical volumes with a zero offset:

/usr/sbin/mklv -y LVname -T O -w n -s n -r n VGname NumPPs

Using a zero offset improves database performance and fixes the issues described in Oracle bug 2620053.

1.3 Installing Oracle CRS on a System with More Than Three Network Interfaces

When you install Oracle Database on a system with more than 3 network interfaces, not all of the interfaces are displayed in the menu used to select the public and private interconnects. To work around this problem:

1. Select public and private interconnects from the three interfaces which are listed in the menu.

2. Complete the installation.

3. After the installation, you can change the interconnects by entering the following commands as root, if necessary:

   # oifcfg delif -global
   # oifcfg setif -global interface/subnet:public
   # oifcfg setif -global interface/subnet:cluster_interconnect
   
   

   For example:

   # oifcfg delif -global
   # oifcfg setif -global en0/144.25.68.0:public
   # oifcfg setif -global en5/192.168.100.0:cluster_interconnect
   
   

4. Enter the following command to verify the new settings:

   $ oifcfg getif
   
   

1.4 Installing Oracle CRS

When you install Oracle CRS on your system, the private interconnects may not be defined correctly. After installation, enter the following command to verify the public and private interconnects:

$ oifcfg getif

This command should return values for global public and global cluster_interconnect, for example:

en0 144.25.68.0 global public
en5 192.168.100.0 global cluster_interconnect

If the command does not return a value for global cluster_interconnect, enter the following commands:

# oifcfg delif -global
# oifcfg setif -global interface/subnet:public
# oifcfg setif -global interface/subnet:cluster_interconnect

For example:

# oifcfg delif -global
# oifcfg setif -global en0/144.25.68.0:public
# oifcfg setif -global en5/192.168.100.0:cluster_interconnect

Enter the following command to verify the new settings:

$ oifcfg getif

1.5 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 restart all of the Oracle CRS nodes. You can restart 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.

1.6 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
   

1.7 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.

1.8 Using ASM on Your System

You must apply Program Technical Fix (PTF) U496549 or higher to your system before you use ASM.

1.9 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
   

1.10 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 listener for each node 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.

1.11 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.

1.12 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;
   

1.13 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.

1.14 Upgrading an Oracle9i Database to Oracle Database 10g

If you upgrade an Oracle9i database to Oracle Database 10g release 1, Oracle Flashback features using a timestamp may fail. To work around this problem, enter the following SQL script from the Oracle Database 10g database:

SQL> DELETE FROM smon_scn_time WHERE orig_thread <> 0;
SQL> COMMIT;

This issue is tracked with Oracle bug 3994270.

1.15 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.

1.16 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.

1.17 Oracle Workflow

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

1.18 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.

1.19 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

1.20 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.

1.21 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.

1.22 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.

1.23 Setting the AIXTHREAD_SCOPE Environment Variable

Threads in AIX can run with process-wide contention scope (M:N) or with systemwide contention scope (1:1). The AIXTHREAD_SCOPE environment variable controls which contention scope is used.

The default value of the AIXTHREAD_SCOPE environment variable is P which specifies process-wide contention scope. When using process-wide contention scope, Oracle threads are mapped to a pool of kernel threads. When Oracle is waiting on an event and its thread is swapped out, it may return on a different kernel thread with a different thread ID. Oracle uses the thread ID to post waiting processes so it is important for the thread ID to remain the same. When using systemwide contention scope, Oracle threads are mapped to kernel threads statically, one to one. For this reason Oracle recommends using systemwide contention. The use of systemwide contention is especially critical for Oracle Real Application Clusters (RAC) instances.Additionally, on AIX 5L version 5.2 or higher, if you set systemwide contention scope, significantly less memory is allocated to each Oracle process.

Oracle recommends that you set the value of the AIXTHREAD_SCOPE environment variable to S in the environment script that you use to set the ORACLE_HOME or ORACLE_SID environment variables for an Oracle database instance or an Oracle Net listener process, as follows:

• Bourne, Bash, or Korn shell:

  Add the following line to the ~/.profile or /usr/local/bin/oraenv script:

  AIXTHREAD_SCOPE=S; export AIXTHREAD_SCOPE
  
  

• C shell:

  Add the following line to the ~/.login or /usr/local/bin/coraenv script:

  setenv AIXTHREAD_SCOPE S
  
  

Doing this enables systemwide thread scope for running all Oracle processes.

1.24 Required Patch for Concurrent I/O

Authorized Problem Analysis Report (APAR) IY56024 is required to prevent concurrent I/O writes returning an incorrect length on AIX 5L systems.

http://www-912.ibm.com/eserver/support/fixes/

1.25 Oracle Transparent Gateway for Sybase

Oracle Transparent Gateways for Sybase does not currently work with Sybase Open Client V12.0. A patch to correct this problem is available from the Download area of the OracleMetalink Web site:

http://metalink.oracle.com/

This issue is tracked through Oracle bug 3398064.

1.26 Problems Starting Oracle Enterprise Manager Database Control

If you choose to configure Oracle Enterprise Manager Database Control during an Oracle Database installation on AIX 5L version 5.3, Database Control might not start. This problem occurs because the Installer cannot obtain a free port in the default range 1830 to 1849.

To work around this problem, before installation edit the /etc/services file to remove or comment out the port assignments for ports in the range 1830 to 1849.

If you do not edit the /etc/services file before installation, perform the following steps after installation:

1. Open the following file in a text editor:

   $ORACLE_HOME/hostname_sid/sysman/config/emd.properties
   
   

2. Add an available TCP port to the value of the EMD_URL parameter as follows:

   EMD_URL=http://hostname:available_tcp_port/emd/main
   
   

3. Open the following file in a text editor:

   $ORACLE_HOME/hostname_sid/sysman/emd/targets.xml
   
   

4. Edit the port number in the oracle_emd target type to match the port number that you specified in step 2.

5. Restart Database Control as follows:

   $ emctl start dbconsole
   
   

1.27 Starting Oracle Enterprise Manager Database Control

Before installing Oracle Database or before starting Oracle Enterprise Manager Database Control, you must set the DISPLAY environment variable to specify a valid X server as follows, where workstation_name is the name of a valid X server:

• Bourne, Bash, or Korn shell:

  $ DISPLAY=workstation_name:0.0 ; export DISPLAY
  
  

• C shell:

  % setenv DISPLAY workstation_name:0.0
  
  

If the DISPLAY environment variable specifies a server that is not an X server, the Installer fails or Oracle Enterprise Manager Database Control produces Java core files and users will not be able to connect to it from the browser.

1.28 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.

1.29 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.

1.30 JDBC Driver and the Just-In-Time Java Compiler

If you use the JDBC driver, and the JAVA_COMPILER environment variable is set to any value other than NONE, Jserver will not start. This problem is fixed by setting JAVA_COMPILER to NONE. For example:

• Set the JAVA_COMPILER environment variable.

  • Bourne, Bash, or Korn shell:

    $ JAVA_COMPILER=NONE ; export JAVA_COMPILER
    
    

  • C shell:

    % setenv JAVA_COMPILER NONE
    
    

• Specify the following option with the java command:

  -Djava.compiler=none
  

1.31 Oracle Scheduler

You cannot use Oracle Scheduler to run jobs external to the database on your system.

1.32 Installing Enterprise Security Manager

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

1.33 Using org.w3c.dom.ls Package with IBM JDK 1.4.2

When using IBM JDK 1.4.2 to build an application that uses the org.w3c.dom.ls package, the following errors might be thrown:

cannot resolve symbol
symbol  : method getConfig ()
location: interface org.w3c.dom.ls.LSParser

or

cannot resolve symbol
symbol  : method getConfig ()
location: interface org.w3c.dom.ls.LSSerializer

This issue is being tracked with Oracle bug 4286338.

1.34 Adding Node to Database on Automatic Storage Management

Adding a node to database on automatic storage management fails if $ORACLE_HOME is not shared.

Workaround: Do Custom install in single node and select ifile instead of pfile for ASM parameter file.

2.1 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

• Configuring Raw Disk Devices for CRS or Database File Storage for RAC Installations Without HACMP or GPFS

• Adding Nodes

• Deleting Nodes

• Real Application Clusters Services Deployment Example

• Configuring Disks for ASM

• Running DBCA on RAC

• srvctl is Spelled Incorrectly

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');

# /usr/sbin/chdev -l hdiskn -a pv=clear

# chown oracle:dba /dev/rhdiskn 
# chmod 660 /dev/rhdiskn

2.2 Updates for Other Documentation

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

• Building Pro*C/C++ Precompiler Demonstrations

• 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

$ make -r -f demo_proc.mk sample1

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)));