Skip Headers

Oracle8i Release Notes
Release 3 (8.1.7) for Sun SPARC Solaris (64-bit)

Part Number A90156-01

Oracle is a registered trademark, and Oracle Express, Oracle8i, Oracle8, Oracle7 and Net8 are trademarks or registered

trademarks of Oracle Corporation. Other names may be trademarks of their respective owners.

Copyright © 2001, Oracle Corporation.

All Rights Reserved.

Oracle8i

Release Notes

Release 3 (8.1.7) for Sun SPARC Solaris (64-bit)

May 2001

Part No. A90156-01

These Release Notes contain important last-minute information not included in the documentation library of your Oracle8i for Sun SPARC Solaris Online Documentation CD-ROM.

This document describes these topics:

Hardware Requirements

The following hardware is required to install Oracle8i Release 3 (8.1.7) on Sun SPARC Solaris systems.

System Requirements

Hardware  Requirements 

Architecture 

sun4u (determined by entering uname -a

Memory 

A minimum of 128 MB RAM is required to install Oracle8i products. Oracle8i Client products require 64 MB of RAM 

Swap Space 

Twice the amount of RAM or at least 400 MB, whichever is greater, is recommended for most systems. 

CD-ROM Device  

A CD-ROM drive supported by Solaris is required. Oracle uses ISO 9660 format CD-ROM disks with RockRidge extensions. 

Disk Space Requirements

Disk space requirements differ depending on which products included with Oracle8i Release 3 (8.1.7) you choose to install on your system. See the Oracle8i Installation Guide Release 3 (8.1.7) for Sun SPARC Solaris for complete details. Disk space requirements do not account for the size of your database. A production Oracle database server supporting many users requires significantly greater disk space and memory.

Oracle8i Enterprise Edition

Installation Type  Required Disk Space 

Typical 

1160 MB 

Minimal 

900 MB 

Custom 

Up to a maximum of 1355 MB 

Oracle8i Management Infrastructure

Installation Type  Required Disk Space 

Oracle Management Server 

490 MB 

Oracle Internet Directory 

810 MB 

Oracle Integration Server 

930 MB 

Custom 

Up to a maximum of 1245 MB 

Oracle8i Client

Installation Type  Required Disk Space 

Administrator 

550 MB 

Programmer 

450 MB 

Application User 

390 MB 

Custom 

Up to a maximum of 500 MB 

Operating System Requirements

To install Oracle8i products included with this release, your Sun SPARC Solaris system must meet the operating system requirements listed in the following table.

OS Software  Requirements 

Operating System 

Solaris 8 

Operating System Patches 

Use the Sun Microsystems "Solaris 8 Recommended Patch cluster." at http://sunsolve.sun.com

Operating System Packages 

SUNWarc, SUNWarcx, SUNWbtool, SUNWhea, SUNWlibm, SUNWlibms, SUNWsprot, SUNWtoo, SUNWtoox

After you install these packages, the following executables are present in the /usr/ccs/bin directory: make, ar, ld, and nm

Window Manager 

X-windows must be installed on the system from where the Installer is run. Use a Sun-supported Motif window manager.

Character mode installs are not supported for Release 3 (8.1.7). See Chapter 3 of the Oracle8i Installation Guide for information on non-interactive installation. 

Required Operating System

You can determine the version of your operating system by entering:

% uname -a

SunOS 5.8 is the core operating system within the Solaris 8 package.

Although you can install Solaris 8 as 32-bit, you must install it as 64-bit (which will also run 32-bit executables). If you try to run 64-bit executables on a 32-bit machine, errors similar to the following appear:

./oracle: Exec format error. Wrong Architecture.

You can determine which version of the Solaris operating system you are running by entering:

% isainfo -v
64-bit sparcv9 applications
32-bit sparc applications

If the 32-bit operating system is running, it does not list the required 64-bit SPARC version 9 applications.

Java Runtime Environment (JRE)

The JRE shipped with Oracle8i is used by Oracle Java applications such as Oracle Universal Installer (OUI) and is the only one supported to run with these applications. Customers should not modify this JRE, unless it is done through a patch provided by Oracle Support Services.

The Solaris patches can be obtained from http://sunsolve.sun.com.

Java Development Kit (JDK)

With Oracle8i Release 3 (8.1.7) Oracle ships a version of Sun Microsystems Java Development Kit (JDK) for use with the Oracle HTTP Server powered by Apache. This JDK is the only one supported to run with the Oracle HTTP Server. Customers should not modify this JDK unless it is done through a patch provided by Oracle Support Services.

The Solaris patches can be obtained from http://sunsolve.sun.com.

Documentation

This section describes these topics:

Oracle Applications InterConnect Installation

The Oracle8i Installation Guide Release 3 (8.1.7) for Sun SPARC Solaris contains only basic information pertaining to the Oracle Applications InterConnect (OAI) install. OAI is a new feature in Release 3 (8.1.7) that is being packaged as part of the Oracle Integration Server, a suite of products designed to integrate and facilitate communication among various applications comprising an e-business (including CRM, ERP, business-to-business Internet marketplaces, and auction sites).To access more specific information regarding the OAI installation, see the OAI Installation Guide, located off the root of the installation media in:

/doc/oai/oaiig313.pdf

Important: Additional READMEs

Additional product README files are located in the product subdirectories under the ORACLE_HOME directory or in the /ORACLE_HOME/relnotes directory.

Platform-Specific Documentation

The Oracle8i Administrator's Reference Release 3 (8.1.7) for Sun SPARC Solaris and the Oracle8i Installation Guide Release 3 (8.1.7) for Sun SPARC Solaris Guide are available online on the Oracle8i software CD-ROM. To access the documentation in HTML and PDF formats, use a web browser to open the index.htm file at the top level of the Oracle8i CD-ROM. This file contains links to product and Solaris-specific documentation.

Online Support

The following websites have the most current information about products included with this release:

Revised, New, and Obsoleted Documentation for Release 8.1.7

The Oracle8i for Sun SPARC Solaris Online Documentation CD-ROM contains guides listed as release 8.1.6 and 8.1.7. Only guides listed as release 8.1.7 have been updated since release 8.1.6. Guides listed as release 8.1.6 have not been revised, however, updates to some of these 8.1.6 guides may be included in:

Product Notes

Check the README.doc file in the $ORACLE_HOME/rdbms/doc directory before using Oracle8i. README files for other products on the Oracle8i distribution are in the doc directories of their respective products.

The following issues and restrictions might affect the installation or use of Oracle8i on Sun SPARC Solaris.

64-bit Files and Directories

In Oracle8i, the following directories contain 64-bit executables and libraries:

The following executables in $ORACLE_HOME are 64-bit; the remainder are 32-bit:

Building 64-bit Pro*C Customer Applications

This release supports building 64-bit Pro*C customer applications. The standard proc executable will generate precompiler code.

The 64-bit client shared library is:

$ORACLE_HOME/lib64/libclntsh.so

To generate 64-bit demos, call the 64-bit targets documented in:

$ORACLE_HOME/precomp/demo/proc/demo_proc.mk

Execute the following command to generate the 64-bit client shared library:

$ORACLE_HOME/bin/genclntsh64
Building 64-bit OCI Customer Applications
This release supports building 64-bit Oracle Call Interface (OCI) 
customer applications. Refer to the 
$ORACLE_HOME/rdbms/demo/demo_rdbms.mk file for more information.
Dynamic OCI User Callbacks

32-bit clients can use dynamic OCI user callbacks only when connecting to Oracle8i through the Net8 Listener. 64-bit OCI clients can use dynamic OCI user callbacks with or without connecting to Oracle8i through the Net8 listener.

For further details on OCI user callbacks, refer to:

 $ORACLE_HOME/rdbms/demo/ociucb.mk

For information on listener configuration, refer to the Net8 Administrator's Guide.


LD_LIB_PATH_64

Instructions for setting the environment variable LD_LIB_PATH_64 is discussed in the platform-specific documentation. Append the following path to the ones listed in the documentation:

$ORACLE_HOME/lib64


Large SGA Sizes

This 64-bit release supports System Global Area (SGA) sizes larger than 4 GB. Only the amount of available system memory limits the SGA size. Therefore, set the Solaris SHMMAX parameter in your /etc/system file to a value high enough to accommodate larger SGA sizes.

The default SGA attach address is set to 14 GB (0x38000000), which you do not need to change under normal circumstances. However, if you need to change it, follow the directions found in the Oracle8i Administrator's Reference for Sun SPARC Solaris 2.x.


Very Large Files

Oracle8i includes native support for files greater than 4 GB. Solaris also supports large files; however, you should verify that your file system and volume manager do not impose file size limits.

Check your shell to determine whether it will impose a limit. To check shell limits, enter:

ulimit -Sa.

To check hard limits, enter:

ulimit -Ha.

For example, if file (blocks) is set to 2097148, the maximum size of a file, that you can create will be 1 GB.

On Solaris 8, file (blocks) is set to unlimited by default.

Products Not Supported

The following products are part of but not supported by Oracle8i Release 3 (8.1.7) for Sun SPARC Solaris:

Running Servers and Clients on Different Word Size Systems

Oracle provides support for 64-bit clients and servers. This support eliminates the 2GB addressing limitation of 32-bit releases. Therefore, the physical memory on the computer system limits SGAs (System Global Areas) and PGAs (Program Global Areas).

Using 64-bit addressing can improve performance by allowing the configuration of large buffer caches, thereby reducing I/Os. By eliminating the limit on the maximum size of the shared pool, 64-bit addressing allows more users to log into Oracle.

The following combinations can run and link successfully:

Preinstallation Steps for Net8

Before installing an Oracle8i server, stop all pre-existing Net8 or SQL*Net listeners from any earlier release of Oracle. A pre-existing and running listener might prevent the Net8 8.1 listener from starting during the Oracle8i install because of endpoint conflicts.

Once you install Oracle8i, Oracle recommends that you use a single Net8 8.1 listener for all of your Oracle databases on the same computer. This includes Oracle8i release 8.1 databases and previous Oracle release databases (such as Oracle8 release 8.0).

After you complete the Oracle8i install, if you want to continue to use multiple listeners on the same computer, verify that there are no listener endpoint conflicts before starting the listeners. If there are conflicts, resolve them and start the listeners.

For more information on listener endpoint configuration, see the listener configuration section in the Net8 Administrator's Guide, included on the Oracle Online Generic Documentation CD-ROM.


Configuration Tools

If a configuration tool (such as netca, dbassist, netec, or odma) fails, continue your installation and run the tool from the command line. For example:

$ netca

To run DBCA from the command line enter:

$ dbassist

Enter a sid that is not assigned to an Oracle instance.

Default JDBC Driver Behavior

In Oracle8i Release 3 (8.1.7) the default behavior for the ResultSet::getXXXStream() APIs have been modified to comply with the JDBC specification so that they return null values for database null LONG/LONG RAW values. In earlier versions of the 8.1.x JDBC drivers, the default behavior was to return the empty stream for database null values. To restore the earlier JDBC default behavior when using the 8.1.7 drivers, you must use the Java property jdbc.backward_compatible_to_8.1.6. For example, if this Java property is set at the virtual machine runtime, the command

java -Djdbc.backward_compatible_to_8.1.6 myJavaProgram


will cause the 8.1.7 JDBC drivers to return empty streams from calls to ResultSet::getXXXStream().

The jdbc.backward_compatible_to_8.1.6 Java property applies to 8.1.7 JDBC Thin driver and OCI driver.

Installation Issues

This section describes the following:

Using VNC or Hummingbird Exceed

You can use Virtual Network Computing (VNC) while installing and using Oracle8i. VNC is described at http://www.uk.research.att.com/vnc.

If you do not use VNC, you can use the Hummingbird Exceed X windows emulator while installing and using Oracle8i. To use Exceed, set the window manager to run in "Native" mode so that Microsoft Windows functions as the window manager. See your Exceed documentation for instructions on configuring the window manager.

While Oracle supports the use of Exceed for installing and configuring products, users should be aware of the following common problems with using this X Windows Emulator for installation:

  1. There is a bug in the way Exceed handles screen coordinates. The installer window and related installer dialogs or configuration assistants may encounter display problems when run through the emulator. These display problems may include the sudden truncation of the main window when clicking the [Next] button during the install, rendering the screen unreadable, or the expansion of an installer window such that the dialog buttons are displayed off the screen and are thus not selectable with a mouse. In such cases, users must exit the entire X Windows session and start a new session to fix the problem. Opening a new shell and re-running the installer from the shell does not fix the problem.

  2. There are consistent display problems with the AQ Database Information dialog which is part of the Oracle Applications InterConnect installation. The last text field on this dialog which prompts for "Consumer Name:" appears truncated when viewed through Exceed. This dialog displays as expected when viewed through native X Windows on Sun SPARC Solaris.

To correct any problems with hidden dialog fields such as that indicated in (2) above, try the following:

  1. Select the xconfig application under the Exceed Program Group from the Windows Start Menu.

  2. Select the "Fonts" Applet.

  3. Click the [Font Database] button in the "Font Settings" dialog box.

  4. Uncheck the "Automatic Font Substitution" option in the "Font Database" dialog box.

  5. Click the [Add...] button. The "Add Font Directory" dialog box is displayed.

  6. Click the [Server] radio button in the "Add Font Directory" dialog box.

  7. Enter the hostname for your machine in the "Host Name" field in the "Add Font Server" dialog box. Leave all the other entries at their default settings.

  8. Click [OK] and [Close] on all dialogs to save the settings.

New ORACLE_HOME

Oracle Corporation recommends that you install Oracle8i Release 3 (8.1.7) products into a new ORACLE_HOME. Do not install Oracle8i Release 3 (8.1.7) into an ORACLE_HOME directory that already contains Oracle products.

If you must install Oracle8i Release 3 (8.1.7) into an ORACLE_HOME that contains 8.1.5 or 8.1.6 products, remove these products with OUI.

Backing Up the root.sh Script

If you install another product category, such as Oracle8i Management Infrastructure, after the successful installation of Oracle8i Server into the same ORACLE_HOME, OUI deletes the content of the root.sh script during the course of the installation. Before beginning the installation, backup the root.sh script.

$ cp root.sh root.sh.save

If you require the original root.sh script, you can recover it from the root.sh.save file.

Non-Interactive Installation

Be aware of the following issues when running OUI in non-interactive mode.

Character Mode

Installation can no longer be performed using character mode. However, you can configure OUI to perform a non-interactive installation of Oracle products. The Installer can be run in non-interactive mode directly from your system's X-windows console or via an X-terminal or PC X-terminal on a remote system. For more information on the non-interactive installation of Oracle products, see "Non-Interactive Installation and Configuration" in the Oracle8i Installation Guide.

First Time Installation in Silent Mode

If you will perform the first installation of Oracle products on a system with OUI running in silent mode, you must run a script to create the oraInst.loc file. The script to create this file is /tmp/orainstRoot.sh. This script will be created when you try to run the Installer for the first time.

See /tmp/silentInstall.log for information about running orainstRoot.sh. Before creating this file, read and complete the tasks detailed in Chapter 1 and Chapter 2 of the Oracle8i Installation Guide.

Required Support Files Drop-In Compatibility

In Oracle8i Release 3 (8.1.7), Oracle is supporting drop-in compatibility of the 8.1.7 client-side libraries on top of the 8.1.6 client-side libraries. This means that applications and tools running in the same ORACLE_HOME as these 8.1.6 client-side libraries will not encounter runtime errors if the libraries are upgraded to 8.1.7 during an install. However, drop-in compatibility is not supported for client-side libraries being used by a database or listener. If an attempt to upgrade the 8.1.6 client-side libraries is made in the same ORACLE_HOME as an Oracle8i Release 2 (8.1.6) database or listener, and the database or listener is not also upgraded to 8.1.7, the 8.1.6 versions of the database or listener will be broken. If you want to keep the older versions of the database or listener intact, you must install Oracle8i Release 3 (8.1.7) in a new ORACLE_HOME.

Known Issue with 64-bit Listener

A known issue exists with dynamic registration between a 32-bit client and a 64-bit listener. Apply the patch for bug 1786292 after installing Oracle8i Release 3 (8.1.7).

Known Upgrade Issues
Bug 1344446

An attempt to upgrade an Oracle8i Release 2 (8.1.6) database to a Release 3 (8.1.7) database in the same ORACLE_HOME produces ignorable installation runtime errors that occur during the deinstallation of the 8.1.6 software.

OUI treats a software upgrade as a deinstall of the old software followed by an install of the new software. The errors that occur during upgrade in the same ORACLE_HOME appear as relinking errors in the RDBMS and Net8 Server. Since these errors are relinking errors that occur during the deinstall of the 8.1.6 software and since the affected files will be replaced and relinked again when the 8.1.7 software is installed, these errors can be safely ignored.

During upgrade of the software, OUI displays error dialogs with the following messages:

  1. Error in invoking target ioracle of make file <ORACLE_HOME>/rdbms/lib/ins_rdbms.mk

  2. Error in invoking target install of makefile <ORACLE_HOME>/network/lib/ins_net_server.mk

Clicking the [Ignore] button on each of these dialogs will allow the installation to continue.

Avoid these errors by installing the Release 3 (8.1.7) software into a new ORACLE_HOME, then performing the data upgrade as usual.

Enabling and disabling system triggers

Before performing either a manual database upgrade or an automated database upgrade using Oracle Data Migration Assistant, you must first set _SYSTEM_TRIG_ENABLED = FALSE in the initialization parameter file. After completing the database portion of the upgrade, you must either remove the _SYSTEM_TRIG_ENABLED from the initialization parameter file or explicitly set it to TRUE before attempting any other upgrade steps, such as upgrading Oracle JServer. Refer to the Oracle8i Migration Book for more information about upgrade and migration.

Multi-CD Issues
Oracle8i Management and Integration Custom Installation

It is not possible to install and configure Oracle Internet Directory (OiD) and Oracle Workflow in the same installation session during a custom install of Oracle8i Management and Integration. If you perform such an installation and choose to install both OiD and Oracle Workflow, the OiD Configuration Assistant will be launched during post-installation to configure OiD in the database, and Oracle Workflow configuration will not be performed.

To configure Oracle Workflow after completion of the installation session, perform the following steps:

  1. Exit OUI at the end of the installation.

  2. Run the Oracle Workflow configuration script manually. To do this, change directories to $ORACLE_HOME/wf/install, and enter the following:

    $ inst252 <wf_acct> <wf_pwd> <wf_home> <sys_pwd> <system_pwd> 
    INSTALL
    

where:

wf_acct = workflow account. Use OWF_MGR

wf_pwd = password@db for workflow account. Use OWF_MGR

wf_home = workflow top level directory, e.g. $ORACLE_HOME/wf

sys_pwd = password@db for SYS account, e.g. change_on_install@wfdb

system_pwd = password@db for SYSTEM account, e.g. manager@wfdb

OUI: Known Problems, Restrictions, and Workarounds
Ejecting the Software CD-ROM

In X-windowing environments, you can launch OUI by clicking on runInstaller from the File Manager window. You can also launch OUI by executing the script from a shell. If you launch OUI by clicking on runInstaller, you will not be able to eject the CD until you kill the installation session. You need to eject the CD to continue with the multi-CD installation required by Oracle8i Release 3 (8.1.7). To successfully install products that require the insertion of multiple CDs, you must execute runInstaller from a shell.

Installing the Pro*COBOL v8.1.7 Precompiler

In Oracle8i Release 3 (8.1.7) you must set the $COBDIR environment variable to a valid path before OUI will allow you to select and install the Pro*COBOL v8.1.7 precompiler.

The Oracle8i Installation Guide for Sun SPARC Solaris indicates that you must set the $COBDIR environment variable prior to installing this precompiler to avoid any relinking errors. However, if you do not set this environment variable prior to starting the installation session, the Pro*COBOL v8.1.7 precompiler will not be available for selection.

Deinstallation

You cannot deinstall Oracle JServer separately from other products installed with Oracle8i Release 3 (8.1.7).

Deinstalling Oracle JServer causes OUI to remove Oracle8i and other products dependent on Oracle JServer from your system.

System Management Products

This section contains these topics:

Oracle Intelligent Agent

The installation model of Oracle Intelligent Agent has been modified as of release 8.1.7. The Oracle Intelligent Agent extensions (Oracle Applications Extensions, Oracle HTTP Server Extensions, Oracle EBusiness Management Tool Extensions, and so on) that allow management of the corresponding areas, can now be installed separately.

This means that during installation, users can select the basic Oracle Intelligent Agent and separately select any of the Oracle Intelligent Agent extensions. Note that Oracle Data Gatherer is installed as part of the basic Oracle Intelligent Agent.

OEM_MONITOR Database Role

The OEM _MONITOR role can be granted to any database user being used as a "preferred credential" when registering advanced (database) events available with the Oracle Enterprise Manager Diagnostics Pack.

This role is defined in /$ORACLE_HOME/rdbms/admin/catsnmp.sql which is called by the catalog scripts at database creation time. In addition to the OEM_MONITOR role, the database user requires quota on their default tablespace within the monitored database, in order to have some of the advanced events evaluated. Failure to do so will result in an insufficient privilege message.

Reinstalling Oracle8i Server

If you reinstall Oracle8i Server into an ORACLE_HOME where Oracle8i Server Release 8.1.7 is already installed, you must also reinstall any product options, such as Oracle Partitioning, that were enabled before you began the reinstallation.

Oracle Internet Directory

Several products included with Oracle8i Release 3 (8.1.7) are now directory-enabled and can take advantage of an LDAP version 3 directory server such as Oracle Internet Directory. Purchase of Oracle8i Release 3 (8.1.7) includes a restricted-use version of Oracle Internet Directory release 2.1.1 for Sun SPARC Solaris that can only be used in conjunction with Oracle directory-enabled components and products such as Net8, Oracle Advanced Security, Oracle8i, and all future directory-enabled Oracle products.

Oracle Database Configuration Assistant

When you use Oracle Database Configuration Assistant to create a Custom database that includes Oracle JServer, be aware that it can take over an hour to finish loading Oracle JServer into the database depending on your system's hardware configuration.

Net8 Configuration Assistant

In a Typical, silent installation of Oracle8i Release 3 (8.1.7), Net8 Configuration Assistant does not configure an IIOP listening end point to provide access to Oracle JServer. After installation, start the Net8 Configuration Assistant from the command line and configure an IIOP end point for the listener called "LISTENER." For more information, see the Net8 Administrator's Guide.

Oracle Parallel Server

This section describes the following:

Creating Raw Devices and the SYSTEM Tablespace

When creating a database for use with Oracle Parallel Server, you must set the SYSTEM tablespace size to at least 274 MB. If you are creating a custom database with the Oracle Database Configuration Assistant, you will need to change the SYSTEM tablespace size from the default of 260 MB to 274 MB before creating the database. In addition, the size of the raw device that you create for the SYSTEM tablespace must also be at least 275 MB. This requirement supersedes the corresponding file size requirement listed in Oracle8i Parallel Server Setup and Configuration Guide. For more information on creating raw devices on Sun SPARC Solaris systems, see Oracle8i Administrator's Reference.

Parallel Server Manager and Parallel Server Management

Be aware of the difference between Oracle Parallel Server Manager and Oracle Parallel Server Management:

Starting Listeners on Remote Nodes

When running in Cluster mode and creating new listeners, the Net8 Configuration Assistant sometimes fails to start the newly created listeners on all nodes of the cluster. To work around this problem, log in to each node and enter the command: lsnrctl start <listenername>.

Heterogeneous Services Agent Control Utility

The Heterogeneous Services Agent Control Utility (agtctl) incorrectly reports its version as 8.1.0.0.0. The correct version of this utility is 8.1.7.0.0.

Legato Storage Manager

This section describes the following:

Installing Legato Storage Manager Manually

The usual procedure for installing Legato Storage Manager is to select Legato Storage Manager installation when you use the Oracle Universal Installer to install your Oracle software.

The Installer asks if you want Legato Storage Manager installed. If you answer no, you can follow the steps below to install Legato Storage Manager manually at a later time.


Caution:

If you are updating Legato Storage Manager, perform a partial removal of Legato Storage Manager, using the procedure in the section, "Removing an Existing Legato Storage Manager Installation," in Appendix B of Oracle8i Installation Guide Release 3 (8.1.7) for Sun SPARC Solaris.

Do not remove any existing Legato Storage Manager files in the /nsr directory. For more information on updating, refer to the section "Updating Legato Storage Manager" in Appendix B of Oracle8i Installation Guide Release 3 (8.1.7) for Sun SPARC Solaris


To install Legato Storage Manager manually on a 64-bit system, perform the following steps:

  1. Make sure no Legato Storage Manager or NetWorker software is on your system. The Legato Storage Manager installer, lsminst (step 3 below), attempts to detect existing Legato software. If Legato software exists but is not detected, both the existing Legato software and the Legato Storage Manager might not function properly.

  2. From the CD-ROM mount point, go to the directory:

    stage/Components/lsm
    
    

    on the Oracle CD-ROM that contains the Legato Storage Manager software and the installer file, lsminst.

  3. As root user, install the Legato Storage Manager software using the following lsminst command:

    # ./lsminst 
    
    

    When prompted for a directory to use for client and server information, you can accept the default or enter another directory name. Make sure the directory has sufficient disk space, as listed for the indexes in the "Legato Storage Manager Software Requirements" table in Appendix B of Oracle8i Installation Guide Release 3 (8.1.7) for Sun SPARC Solaris.

    When prompted for a device name, you can enter either a carriage return (ENTER) or a proper no-rewind, BSD-semantics tape device name. The device is used by Legato Storage Manager for backups after it is configured in the LSM Administrator GUI. For details on device configuration, see the Legato Storage Manager Administrator's Guide.

    For all other prompts displayed by lsminst, press [ENTER] to accept the default response.

  4. Update the MANPATH and PATH environment variables as required. MANPATH must include the path name of the directory containing the Legato Storage Manager man pages, /usr/share/man. PATH must include path names of the directories containing the Legato Storage Manager binaries, /usr/bin and /usr/sbin by default.

  5. For each ORACLE_HOME to be enabled for Legato Storage Manager backups, follow these steps:


    Caution:

    If you later install another ORACLE_HOME on your system, you must follow these steps to enable Legato Storage Manager backups from that ORACLE_HOME. 


    1. Log in as the ORACLE_HOME owner.

    2. Copy the file liblsm.so from the directory,
      cdrom_mount_point/stage/Components/lsm/lib, on the Oracle CD-ROM to the file, $ORACLE_HOME/lib64/liblsm.so, as follows:

      cp cdrom_mount_point/stage/Components/lsm/lib/liblsm.so
      $ORACLE_HOME/lib64/liblsm.so
    3. Shut down all Oracle instances that use this ORACLE_HOME.

    4. Remove the symbolic link $ORACLE_HOME/lib64/libobk.so and replace it with a symbolic link to the file,
      $ORACLE_HOME/lib64/liblsm.so, as follows:

      cd $ORACLE_HOME/lib64
      rm libobk.so
      ln -s liblsm.so libobk.so
      
    5. Restart all Oracle instances that use this ORACLE_HOME.

Removing Legato Storage Manager


Note:

You cannot remove Legato Storage Manager using the Oracle Universal Installer. You must use the following steps to remove Legato Storage Manager version 5.5. 


To remove Legato Storage Manager version 5.5 on a 64-bit system, perform the following steps:

  1. For each ORACLE_HOME on your system enabled for backups, follow these steps to remove the Media Management API of Legato Storage Manager version 5.5:

    1. Shut down all Oracle instances that use this ORACLE_HOME.

    2. Remove $ORACLE_HOME/lib64/liblsm.so and create a symbolic link from $ORACLE_HOME/lib64/libobk.so to
      $ORACLE_HOME/lib64/libdsbtsh8.so by entering:

      cd $ORACLE_HOME/lib64
      rm liblsm.so
      rm libobk.so
      ln -s libdsbtsh8.so libobk.so
      
      
    3. Restart all Oracle instances that use this ORACLE_HOME.

  2. As root user, stop the Legato Storage Manager daemons by entering:

    #nsr_shutdown
    

    You can see a list of all packages installed with the pkginfo command.


    Note:

    This procedure does not remove the /nsr directory containing the Legato Storage Manager client and media index files and resource configuration files. 



    Caution:

    If you remove the /nsr directory containing the index and configuration information, you will not be able to restore from the Legato Storage Manager backups. If you later re-install the Legato Storage Manager or install another Legato product, you will need to rebuild the configuration. 


  3. To remove the Legato Storage Manager index and resource configuration files, remove the /nsr directory by running the following as root user:

    #rm -rf/nsr/*/nsr
    
    
Deinstalling Legato Storage Manager

The deinstallation of Legato Storage Manager does not work correctly. In particular, the installation of LSM creates a symbolic link libobk.so that points to the library liblsm.so. During deinstall, the library liblsm.so is removed. However, the symbolic link is not redirected to point to the library libdsbtsh8.so.

If libobk.so is not correctly recreated to point to libdsbtsh8.so after the removal of LSM, Oracle will not work properly. To correctly remove LSM, delete and recreate the symbolic link libobk.so to point to libdsbtsh8.so after the completion of the deinstall of LSM.


Oracle
Copyright © 2001 Oracle Corporation.

All Rights Reserved.