infrastructure upgrade plan for operating system ... · pdf fileinfrastructure upgrade plan...

Infrastructure Upgrade Plan for

HP Operating System Environments

For SCT's Banner Baseline Release 4.x5.x

Version HPUX 11.0 32-bit

IMPORTANT NOTES:

This is one of a set of documents needed to implement the Oracle upgrade needed for Banner 4.x5.x.

Before beginning your installation, you MUST read Infrastructure Upgrade Plan for HP Operating System Environments, which includes critical information about specifications, known issues, and bugs.

This document is current as of February 8, 2001. Warnings, changes, and tips from the workshops are being placed in the Addenda from the Installation Workshops as they take place. Please check the Addenda before you begin.

Office of Information and Instructional Technology

Enterprise Applications Systems/Technical Services

February 8, 2001

OIIT

Warnings, changes, tips, and advice from the ongoing installation workshops and campus installations are being added to the document as electronic "sticky notes." Notes have been added for the following dates: 2/15/01 For a complete list of these annotations, select "annotations" from the bookmarks.

Infrastructure Upgrade Plan OIIT-EAS for Banner 4.x5.x Technical Services

Page iii February 8, 2001

I:\Shared Documents\docwork\HP11upgplandocversion.doc

Table of Contents

Infrastructure Upgrade Plan for HP Operating System Environments for SCT Banner Baseline 5.x..................................................................................................................................... 1 Disclaimer ...................................................................................................................................... 1 Background.................................................................................................................................... 1 Media Shipments ........................................................................................................................... 1

For HPUX11 Environments: ...................................................................................................... 1 For Solaris Environments:.......................................................................................................... 1 Windows Environments: ............................................................................................................ 2

Oracle Documentation .................................................................................................................. 2 Assumptions................................................................................................................................... 2 Issues and Restrictions.................................................................................................................. 2

Vendor Dependencies and Version Synchronizations........................................................... 2 Known Bugs - Fixes and Workarounds (Oracle 8.0.5 and Oracle 8.1.6) ............................. 3

Serious potential bug in the Oracle 8.0.5 to 8.1.6 upgrade!! ............................................ 3 Oracle 8.0.5 connections to 8.1 on HPUX coredump....................................................... 3 Missing script in 8.1.5 to 8.1.6 upgrade main script (BETA SITES!!) ............................ 3 NFS Client/Server requirement for Oracle installation on HPUX ................................... 3 Oracle 8.1.6 requires execution of two installer sessions ................................................. 3 Oracle 8.1.6 install issue with /tmp................................................................................... 4 Pro*C Bug w/Oracle 8.1.6 (all platforms)........................................................................ 4 OAS4.0.8.x issue with Domain Names (FQDN)............................................................. 4 OAS4.0.8.2 issue - Jweb cartridge failure to install/configure cleanly ............................ 4 OAS 4.0.8.2 issue with sqlplus coredump........................................................................ 5

Known Requirements, Settings, etc....................................................................................... 5 Character-mode installation no longer available .............................................................. 5 Use of the DCA (Database Configuration Assistant) and the DMA (Database Migration Assistant) Tools ................................................................................................................ 5 Tablespace Sizing Issues .................................................................................................. 6 Makefile issues for Banner 3.x/4.x/5.x ............................................................................. 6 Clients that run both PeopleSoft HRMS and Banner on same desktop............................ 6 Developer 2000 1.6.1 and Forms (Developer) 6i cannot be installed on same hardware 6

Post-Install Issues .................................................................................................................. 6 Dbstart bug with Oracle 8.1.6 (all platforms)................................................................... 6 Sql*Net listener (lsnrctl) startup issue after Oracle 8.1.6 install (HPUX and Solaris)..... 6 Browser Issue: IE5 vs. Netscape..................................................................................... 7 OAS4.0.8.x tuning issue w/HPUX11 ............................................................................... 7 Notice to Voice Response Customers:.............................................................................. 7

Pre-Upgrade System Requirements for HPUX11 Operating System OIIT-TSS Release ...... 8 Specific Operating Systems Requirements ................................................................................. 8

Table 1. Minimum System Requirements for HPUX 11.............................................. 9


Page iv February 8, 2001

I:\Shared Documents\docwork\HP11upgplandocversion.doc

Current Technical Stack/SOE ..................................................................................................... 9 Table 2 - Current Technical Stack ............................................................................. 10

Targeted Technical Stack/SOE.................................................................................................. 10 Table 3 - Targeted Technical Stack/SOE................................................................... 10

Upgrade Path ............................................................................................................................... 10 Table 4 � Supported Stages of the Upgrade Path...................................................... 11

Upgrade Methodologies ........................................................................................................... 11 Preferred Upgrade Method ............................................................................................. 11 Alternate Upgrade Method ............................................................................................. 11 Time Estimates ............................................................................................................... 12

Table 5 - Steps in Upgrade to Targeted Technical Stack .......................................... 12 Table 6. Conditional Steps in Upgrade to Targeted Technical Stack....................... 13

Scenario 1 � New HPUX11 server, copied database, same filenames..................................... 14 Scenario 2 � New HPUX11 server, cloned database, new filenames ...................................... 16 Scenario 3 - Upgrading existing HPUX 10.20 server, datafile names do not change............ 18 Scenario 4 - Upgrading existing HPUX 10.20 server, datafile names do change.................. 19 Installing Oracle 8.0.5 for HPUX11......................................................................................... 21 Applying bugfix 991197 for Oracle 8.0.5 HPUX11 ................................................................ 24 Apply the Intelligent Agent Patch ............................................................................................ 25

Upgrading to Oracle 8.1.6, with 8.1.6.3 Patch .......................................................................... 26


Page 1 February 8, 2001

Infrastructure Upgrade Plan for HP Operating System Environments for SCT Banner Baseline 5.x

Disclaimer

Information included in this document is accurate to the best of our knowledge at the time of publication. Information that is discovered after publication will be made available through normal support channels.

Background

In order to maintain currency with vendor support schedules for the Oracle RDBMS and SCT Banner Baseline products, campuses will be required to upgrade the technical infrastructure associated with these products.

The Upgrade Plan describes targeted Technical Stack/Supported Operating Environment (SOE), as well as the general business practices that institutional technical personnel should follow when upgrading their environments to the targeted technical stack release. Campuses are strongly urged to meet all prerequisites and ensure that the prescribed upgrade path is followed to make the upgrade process flow as smoothly as possible.

Campuses are strongly urged to apply all parts of this release to a test server environment before applying to a production environmnet.

Media Shipments

Each campus should contact the OIIT Solution Center (HelpDesk) to request new Oracle product media shipments described below according to the campus� environment. When requesting media shipments, be sure to indicate the operating system for both the Oracle Server and the Application (Web) Server. Provide a name and address for shipping.

For HPUX11 Environments:

• Oracle Server Enterprise Edition 8.0.5 for HPUX11 32-bit • Oracle Server Enterprise Edition 8.1.6 for HPUX11 32-bit • Oracle Application Server 4.0.8.2 for HPUX11 32-bit (if the Web Server platform is

HPUX) • Developer 2000 1.6.1 for HPUX11 32-bit ( if needed to generate character-mode forms,

such as Voice Response forms)

For Solaris Environments:

• Oracle Server Enterprise Edition 8.1.6 for Solaris • Oracle Application Server 4.0.8.2 for Solaris



Windows Environments:

Developer 6i w/Patch 1

Oracle Documentation

Campuses are encouraged to use Oracle�s Technet (OTN) Documentation Resource page to read Oracle documentation online. This web site requires the use of an OTN user account. Accounts may be created by the user by clicking this link: Create an OTN account. Campus personnel who prefer to receive this documentation on a CD-Rom should include the request for online documentation when submitting the media shipment request for Oracle products to the Help Desk.

Assumptions

It is assumed that campuses applying this release have already implemented the GUI environment. Campuses were urged to have completed this GUI implementation by September 2000.

Issues and Restrictions

Vendor Dependencies and Version Synchronizations

Due to vendor dependencies for Oracle products, the upgrade of Oracle Application Server to 4.0.8.2 must occur in conjunction with the HPUX11 upgrade for those campuses that run the Oracle Application Server in the HPUX environment. The current supported Version 3.0.2 of Oracle Application Server is not certified with the HPUX11 operating system. Because there is no complete migration path for the local campus' webserver PL/SQL and listener configuration information, the upgrade of the Oracle Application Server requires manual re-configuration of the PL/SQL cartridges and listeners for the Banner Web products.

While best practices indicate that the Application Server and the Oracle RDBMS should ideally be maintained on separate servers, OIIT recognizes the additional burden that acquisition of an additional server places on campuses. Therefore, OIIT will, as a part of this upgrade, acknowledge the deviation from best practices and support the installation of the Oracle RDBMS and the Oracle Application Server (4.0.8.2) on the same server in the HPUX11 environment. Campuses are, however, encouraged to plan for the separation of these two products onto separate servers in the future.

Error correction support for the 8.1.6.x versions of the Oracle Enterprise Server (RDBMS) ends on October 31, 2001. The upgrade path as prescribed by Oracle Corp. for its customers is to upgrade to version 8.1.7 of the RDBMS. Due to Oracle�s non-certification of the 8.1.7 RDBMS with Oracle Application Server (OAS) version 4.0.8.x, version 8.1.6.3 of the RDBMS is being installed initially. However, campuses should be aware that an additional point release of the Oracle Server RDBMS (patch 8.1.6.4) may need to be installed during the upgrade process.

http://technet.oracle.com/docs/index.htm

http://technet.oracle.com/membership/register.htm



Known Bugs - Fixes and Workarounds (Oracle 8.0.5 and Oracle 8.1.6)

Serious potential bug in the Oracle 8.0.5 to 8.1.6 upgrade!!

Oracle Corp has identified a rarely encountered but potentially serious bug that could manifest itself during the upgrade process. A workaround has been provided to identify whether this error has occurred prior to the upgrade of the Oracle databases from Oracle 8.0.5 to Oracle 8.1.x. This workaround has been incorporated in the Step by Step Oracle 8.1.6 upgrade instructions document as Step 18. This step is clearly marked with bolded, uppercase in the comments section of this step. This is a critical part of the upgrade. During beta testing, no database was found to have this problem, which involved corruption in the SYSTEM data structure.

Oracle 8.0.5 connections to 8.1 on HPUX coredump

An Oracle bug exists in the version of Sql*Net installed with Oracle 8.0.5.x on HPUX platforms. This bug exists in both the HPUX10.20 and the HPUX11 Oracle 8.0.5 environments. Sql*Net client connections from an HPUX Oracle 8.0.5 environment to an 8.1.x environment on any operating system platform core dumps. This bug was fixed as of Oracle 8.0.6. This is a potential problem for campuses who may have Oracle environments in both 8.0.5 and 8.1.x on HPUX platforms when attempting client connections from the 8.0.5.x databases to 8.1.x databases.

Missing script in 8.1.5 to 8.1.6 upgrade main script (BETA SITES!!)

If any of our beta site technical personnel who have already installed Oracle 8.1.5 plan to upgrade your Oracle 8.1.5 database to Oracle 8.1.6, you should be aware of an issue with the upgrade script u0801050.sql,which references another script, i0801050.sql. However, the latter script is only installed if you select the Migration Utility which should not be needed as the upgrade from 8.1.5 to 8.1.6 is an upgrade, not a true migration. This issue is Oracle Note 98162.1 available on Oracle Metalink.

NFS Client/Server requirement for Oracle installation on HPUX

The Oracle Installer for HPUX requires that both the NFS Server and NFS Client daemons be running in order to properly access Oracle installer CDs. Due to the nature of NFS, Systems Administrators should always know when NFS services have been enabled on their systems. Therefore, the OIIT-TSS Release of HPUX11 will setup the NFS Server, but will not enable this service. The Systems Administrator will therefore need to enable the NFS Client and NFS Server before the Oracle installer CDs may be accessed. This information is detailed in the Step by Step Oracle 8.1.6 upgrade instructions.

Oracle 8.1.6 requires execution of two installer sessions

The Oracle 8.1.6 software install will require that the installer be run twice. The first installer session will add the Oracle 8.1.6 server software. The installer must then be restarted to install the Oracle 8.1.6 Client software, which will add the Pre-compilers, SqlPlus, and other client software.



Oracle 8.1.6 install issue with /tmp

The Oracle 8.1.6 install writes some rather large temporary files to the /tmp directory. During the install of Oracle 8.1.6 on HPUX11, the /tmp filesystem ran out of disk space. While this may not be an issue for all campuses, technical personnel should ensure that no unnecessary files exist in /tmp before beginning the install.

Pro*C Bug w/Oracle 8.1.6 (all platforms)

SCT has identified a bug in the 8.1.6.2/8.1.6.3 version of the Oracle RDBMS which causes problems with certain uses of arrays in which null values are returned in Pro*C programs. SCT has implemented a workaround and has released patches to deal with this issue. Oracle has announced that this bug is fixed in the Oracle 8.1.6.4 patch; however this patch had not been released by Oracle Corp. at the time this document was written. Campuses should therefore be aware that the possibility exists that a point release (Oracle 8.1.6.4) may need to be installed at some point during the upgrade process. OIIT will make this information available as soon as possible.

OAS4.0.8.x issue with Domain Names (FQDN)

Beta testing also revealed an issue with installing Oracle Application Server 4.0.8.2 on servers whose fully qualified domain name (FQDN) exceeds 24 characters OR with systems in which the �domainname� command does not return the machine�s domain name. One workaround is to define an alias or service name for the server that is less than 24 characters OR to set the domainname to the correct DNS domain name of the machine, then reinstall OAS. However, consideration should be given to whether setting the domainname may cause issues with other applications that assume that YP or NIS is being used if the domainname is set for the machine. For example, installation of OAS4.0.8.2 on a machine whose FQDN is odysseus.rath.peachnet.edu failed to install properly. This error manifested itself as the inability to connect to the OAS Node Manager Admin page with the error �Invalid virtual host�� message and the appearance of �mydomain.com� specified as the domainname in the OAS configuration files. Re-installing OAS using a shortened machine alias, implementing the workaround specified in Oracle Note 111847.1 , and manually editing configuration files for OAS corrected this. OIIT has filed a Technical Assistance Request with Oracle Corp. to address this issue.

OAS4.0.8.2 issue - Jweb cartridge failure to install/configure cleanly

Beta testing revealed a bug that occurs during the installation of OAS4.0.8.2 on HPUX11 and the failure of the Jweb Cartridge to install properly. This error occurs during the install because of an issue with the way in which hostname is chosen by the Oracle Universal Installer(OUI) and case-sensitivity. If during the install, a value for hostname other than the value chosen by the OUI is entered by the user, the OUI will still create the node directory based on the value the OUI proposed for hostname and the error �OWS-09150: Web listener configuration file '$ORACLE_HOME/ows/admin/<site_name>/httpd_<hostname>/node/svnode.cfg' � is returned. A workaround is to create a symbolic link named "httpd_<desired host name>" pointing to the existing "httpd_<OUI-selected hostname>" directory. For example, using an



install session in which the hostname is oiit and you entered OIIT, you would enter the following commands:

cd $ORACLE_HOME/ows/admin/<site_name> (where $ORACLE_HOME is the OAS Oracle_Home and site_name is your OAS site name)

ln -s httpd_oiit httpd_OIIT

Then, re-focus to your OUI installer window, select the JWEB Cartridge Configuration line in the OUI window and click on "Retry." This time the configuration will run successfully.

OAS 4.0.8.2 issue with sqlplus coredump

OAS4.0.8.2 software was written based on Oracle 8.1.6.0.0 version of the RDBMS. This version of the RDBMS/client software had a bug that caused sqlplus to coredump. Bugfix 1194937 must be applied to ONLY the sqlplus that is installed as a part of the OAS4.0.8.2 install. This bugfix will be available on the ftp server in the banner/prod/oracle/hpux11 directory.

Known Requirements, Settings, etc.

Character-mode installation no longer available

The character-mode installation process for Oracle Unix products no longer exists for Oracle for Unix products. Personnel performing the installation of Oracle for Unix products are required to have access to an X-station or to install X-emulation software on the workstation/desktop. OIIT's database administrators used Hummingbird's Exceed product to provide this functionality. Additionally, the Xwin32 demo product available from http://www.starnet.com/ was used in initial testing of X-emulation software and found to be adequate for use in performing the Oracle products for Unix installations. Some beta sites also used Reflection-X.

Use of the DCA (Database Configuration Assistant) and the DMA (Database Migration Assistant) Tools

The Oracle 8.1 installer has two new X-tools that will allow the migration of an Oracle database via the Database Migration Assistant tool or the creation of a new Oracle database via the Database Configuration Assistant. Beta testing has proven these tools to be extremely slow. Additionally, SCT�s prescribed upgrade methodology recommends that the Database Migration Assistant tool not be used to upgrade the database during the Oracle server installation process. Use of this tool during and after the upgrade process revealed that the tool will create the Oracle �admin� directory in a directory other than the location specified by the user at the time of installation. The installer, during testing, created $ORACLE_HOME/admin/<SID> directory even though �/oracle/admin� was specified as the location for the creation of the �admin� files. This has been reported to Oracle Corp. While this tool makes the creation of databases more interactive for the DBA, for reasons revealed during beta testing, it is recommended that the Database Configuration Assistant and the Database Migration Assistant not be used for the creation of Banner databases.

http://www.starnet.com/



Tablespace Sizing Issues

During beta testing, the SYSTEM tablespace was required to be increased in size by 50% at some sites. Additionally, some sites required that the TOOLS tablespace be increased by as much as 50% as well.

Makefile issues for Banner 3.x/4.x/5.x

New Pro*C and Pro*Cobol makefiles will be required for use with HPUX11. There are separate new makefiles for Banner 3.x and Banner 4.x/5.x on HPUX11. These makefiles are available in the banner/prod/oracle/hpux11 directory on the ftp server (ftp.usg.edu).

Clients that run both PeopleSoft HRMS and Banner on same desktop

The Oracle Developer 6i product that will be installed at the time the Banner 5.x GUI environment is created will update the Sql*Net product installed on the client. While the Banner 5.x/Developer 6i software has not yet been installed and tested at campus beta sites, OIIT test clients have successfully tested with this version of Sql*net using other Oracle products on the same client with PeopleSoft and Banner. Testing continues at this time. No problems are expected. However, OIIT will notify clients should problems arise.

Developer 2000 1.6.1 and Forms (Developer) 6i cannot be installed on same hardware

Banner 5.x requires the use of the Oracle Forms (Developer) 6i product to generate and run the Banner GUI forms. Banner 3.x/4.x requires the use of the Oracle Developer 2000 1.6.1 product to generate and run the Banner GUI forms. These two Oracle products cannot be installed on the same hardware due to the products� use of the Windows Registry entries and because the older Developer 2000 1.6.1 product is not multi-home aware in the Windows environment. This has implications for campuses having concurrent Banner 3.x/4.x and Banner 5.x as they transition from Banner 3.x/4.x to Banner 5.x, as separate hardware will be needed to install and use the new Oracle product.

Post-Install Issues

Dbstart bug with Oracle 8.1.6 (all platforms)

There is a specific bug that exists with Oracle 8.1.6 that will cause dbstart to erroneously report successful database startup. This is Oracle Bug #1154931. This bug has been corrected in Oracle 8.1.7 Enterprise Edition. A workaround has been provided for Oracle 8.1.6.x and is available from the ftp server in location banner/prod/oracle/hpux11 or banner /prod/oracle/sol26. See the installation instructions for documentation regarding implementing this workaround.

Sql*Net listener (lsnrctl) startup issue after Oracle 8.1.6 install (HPUX and Solaris)

Once campuses have completed the Oracle 8.1.6.3 software install and have upgraded at least one database to the 8.1.6.x environment, the Sql*Net listeners must be started from the Oracle 8.1.6 ORACLE_HOME lsnrctl binary. The lsnrctl process can listen for connections from older

ftp://ftp.usg.edu/



versions down to Oracle 7.3.4/Sql*Net 2.3.4, however the older versions of the process do not accept connections from newer versions of the process.

Additionally, when starting the lsrnctl process, the environment variables SHLIB_PATH (HPUX) and LD_LIBRARY_PATH (Solaris) must be unset prior to starting the Sql*Net listeners in the Oracle 8.1.6 environment, to avoid errors with unsatisfied library symbols.

Browser Issue: IE5 vs. Netscape

During the installation of the PL/SQL Toolkit, Microsoft Internet Explorer (IE5.0 w/SP1) could not be used to install the PL/SQL Toolkit. Attempts to install the Toolkit returned �OWS-28200: Oracle Database Error: 972, ORA:00942: indentifier is too long.� This error did not occur when Netscape 4.7+ was used to install the Toolkit. Oracle Support stated that Netscape is recommended over IE as the browser to be used with Oracle Application Server web interface page (Node Manager). Additionally, do not use Netscape 6; it will not work.

OAS4.0.8.x tuning issue w/HPUX11

Beta testing revealed problems with priority-based tuning using the Oracle Application Server in the HPUX11 environment. This is a known issue with Oracle Corp. A workaround is to change the setting for tuning from �priority-based� to �min/max based� has been prescribed by Oracle Support Services and has been successfully tested by several of our betas.

Error when stopping OAS from Node Manager or from the server command line

When the command is issued to stop the Oracle Application Server, either via the Node Manager or via the command line prompt on the Unix server, the following error message is displayed:

UNHANDLED EXCEPTION: IDL:omg.org/CORBA/BAD_PARAM:1.0 in owsctl BAD_PARAM:1.0 in owsctl at line 948of yocorb.c

This issue has been reported as a bug to Oracle Support Services and has been referred to Oracle's development group.

Notice to Voice Response Customers:

Voice Response 5.0 will require that Voice Response 4.1 be installed first. The correct upgrade path would be from 3.x directly to VR 4.1. There is a technology shift from VR3.x to VR4.1. The screen-scraping technology that VR3.x uses will no longer be used. The Banner2000 VR system has been rewritten to use a socket-based technology to interface the Banner2000 database with the Voice Response Unit (VRU). This is made possible through the use of the Oracle Application Server, and a series of Oracle stored procedures. The architecture for VR 5.0 is the same as the 4.1 release. Additional information regarding the Voice Response upgrade to 4.1/5.0 is available in the Voice Response FAQ.



Pre-Upgrade System Requirements for HPUX11 Operating System OIIT-TSS Release

Campuses are strongly urged to apply the HPUX11 OIIT-TSS release of the operating system. This release has been updated with the list of operating system patches and kernel configuration parameters defined in the Oracle 8.1.6 Installation Guide for HPUX11, the Oracle 8.l.6 for HPUX11 Release Notes and the Oracle Application Server 4.0.8.x Installation Guide and Release Notes for HPUX11. Arrangements to have this release applied to campus servers may be made by contacting the OIIT Solution Center at 1-888-875-3697 or by sending email to mailto://[email protected] and requesting to receive the HPUX11 OIIT-TSS release of the operating system.

Listed below are the requirements that must be met prior to installing the HPUX11 OIIT-TSS release.

A recent, complete, full system backup must be performed by the campus.

A 4-Gigabyte usable disk drive is required to install the new release.

Oracle for Unix 8.1.x installation requirement:

The character-mode installation process for Oracle Unix products no longer exists for Oracle 8.1.x and OAS4.0.8.2 for Unix products. Personnel performing the installation of Oracle 8.1 and OAS4.0.8.2 for Unix products are required to have access to an X-station or to install X-emulation software on the workstation/desktop. OIIT's database administrators used Hummingbird's Exceed product to provide this functionality. Additionally, the Xwin32 demo product available from http://www.starnet.com/ was used in initial testing of X-emulation software and found to be adequate for use in performing the Oracle products for Unix installations. Some beta sites also used Reflection-X.

Specific Operating Systems Requirements

The HPUX11 OIIT-TSS Release of the operating system has been pre-configured to support the Oracle RDBMS as well as the Oracle Application Server. Additionally, recommended kernel parameter changes and patch sets have been applied to this release of the operating system. Campuses who do not apply the OIIT-TSS Release of the operating system should be aware of the following minimum requirements to ensure that they are operating in an environment that is supported by OIIT, SCT, and Oracle. Table 1 shows the operating systems and software requirements. Please note that these are minimum requirements and that local configurations may require additional tuning. Additional requirements regarding specific patches may be obtained by using the software distribution services available from OIIT-TSS operating systems support via the OIIT Solution Center.

mailto://[email protected]

http://www.starnet.com/



Table 1. Minimum System Requirements for HPUX 11

Hardware MINIMUM for Database Server

MINIMUM for Application Server

Memory 256 MB 512 MB

Disk space 1.4 Gigabytes (for Oracle Server and precompilers)

750 MB

Swap space Twice the amount of RAM Twice the amount of RAM

Software and Kernel Requirements Minimum for Database Server

Minimum for Application Server

Operating System HPUX11 HPUX11 Kernel Parameter Settings Maxfiles 2048 2048 Maxfiles_lim 2048 2048 Max_thread_proc 1024 1024 SHMMAX (This setting does not affect how much shared memory is needed or used by Oracle or the operating system. It is used only to indicate the maximum allowable size).

1GB

SHMMIN 1 Software and Kernel Requirements (cont.)

Minimum for Database Server

Minimum for Application Server

SHMMNI 100 SHMSEG 10 Umask is set to 022 for the �oracle� Unix account

JDK (installed prior to installation of Oracle products)

1.22

MF Cobol 4.1 Rev 10 ANSI C B.11.01.20 B.11.01.20

Current Technical Stack/SOE

Table 2 details the technical aspects of the current supported Technical Stack/SOE. All campuses' current technical environment for Banner 3.x should be reflective of this technical stack prior to beginning the HPUX11 operating system upgrade/migration.



Table 2 - Current Technical Stack

Application Version HPUX Operating System 10.20 OIIT-TSS Release ORACLE RDBMS 8.0.5.2 w/setuid patch DEVELOPER 2000 1.6.1 w/Patch 9 for HPUX10.20

1.6.1 w/Patch 9 for Windows 95/NT (Banner GUI implementation)

ORACLE APPLICATION SERVER (HPUX 10.20 or Solaris 2.6) 3.0.2

MicroFocus COBOL 4.0.5 Rev 5 or 4.1 ANSI C B.10.20.03 HP C/ANSI C

Targeted Technical Stack/SOE

Table 3 details the technical aspects of the targeted Technical Stack/SOE. All campuses are expected to upgrade to this technical stack before implementing the Baseline Banner 4.x/5.x release. Additionally, campuses are required to apply an interim release of Oracle 8.0.5 and Developer 2000 1.6.1 (where needed to generate character-mode form for Voice Response) in the new HPUX11 environment to facilitate the upgrade of the Oracle RDBMS to the targeted version (8.1.6) as a part of the upgrade path. Campuses may elect and are urged to apply the upgrade in stages. See Upgrade Path for details regarding the upgrade process.

Table 3 - Targeted Technical Stack/SOE

Application Version HPUX Operating System 11.0 OIIT-TSS Release Oracle Rdbms 8.1.6 Oracle Developer Developer (Forms) 6i Oracle Application Server 4.0.8.2 for HPUX11 or Solaris 2.6 Java Developer's Kit (JDK) Version 1.2.2(for OAS4.0.8.2) MicroFocus COBOL 4.1 Rev 10 or 4.1 w/Pro*Cobol 1.8.50 ANSI C B.11.01.20

Upgrade Path

Table 4 describes the various possible supported staged environments in the upgrade path. OIIT will maintain support environments at each of these stages to provide support to the campuses until the production implementation date of December 31, 2001 has passed. After that date, the supported environment will be the "targeted technical stacks" defined in Table 3.



Table 4 � Supported Stages of the Upgrade Path

Operating System RDBMS Application Server Banner HPUX11 8.0.5 3.0.2* (HPUX 10.20) 3.x HPUX11 8.0.5 4.0.8.2 3.x HPUX11 8.1.6 4.0.8.2 3.x HPUX11 8.1.6 4.0.8.2 4.x/5.x * Version 3.0.2 is supported for this upgrade process on HPUX 10.20 servers that are separate from the database server being used for the upgrade. Version 3.0.2 is not supported on HPUX11 servers.

Upgrade Methodologies

There are two supported methodologies for upgrading Oracle 8.0.5.x on HPUX-10.20 to Oracle 8.1.6 on HPUX11. Both methods are described here with the preferred method being listed first. The preferred method has been tested and re-tested and is the method prescribed by Oracle. The alternate method has been tested, though less extensively and is the second method prescribed by Oracle.

Preferred Upgrade Method

The preferred upgrade method is to apply the HPUX11 operating system and then follow the necessary steps to bring the Oracle database up in the new operating system environment using an interim install of the same version of the Oracle RDBMS for the new operating system as was used in the HPUX 10.20 operating system environment. While this method requires an interim install of all the Oracle products that were previously used in the HPUX10.20 environment (with the exception of the Oracle Application Server which must be upgraded to OAS4.0.8.2 in conjunction with the HPUX11 upgrade), it is a preferred method because it follows the �Change one factor at a time� business practice. Using this method would change one (1) and possibly two(2) factors of the technical environment (the operating system and, possibly, the application server) Additionally, this method provided a shorter window of downtime than the export/import method during testing.

Alternate Upgrade Method

This alternate upgrade method is to apply the HPUX11 operating system upgrade, install the new Oracle software and patches in the new operating system environment, setup the database for use with Banner, and then import a copy of the production data into the new versioned database. The drawback to this method is the amount of time required to perform the export/import, but of greater risk is the fact that this method would be changing no less than 2, and possibly 3, factors of the technical environment simultaneously (i.e., operating system, RDBMS, and possibly application server). However, this method is useful if the DBA has a need to de-fragment the database.

OIIT

2/15/01 While OIIT has been successful in configuring OAS 4.0.8.2 to work with 8.0.5.2.1 Banner databases on HPUX11, please understand that we are working in a pristine environment. However, Oracle no longer supports this specific infrastructure combination. Should campuses choose to operate in this environment, and unknown issues/errors arise, the only option available is to upgrade the RDBMS to 8.1.6.3



Time Estimates

Estimates of time required to perform the upgrade are being provided at the request of campus technical personnel. Our best estimates are detailed below. These estimates are from our internal testing and from our beta sites. Please remember that time required will vary, possibly greatly so, depending upon each campus� environment, preparation, and method chosen for performing the upgrade.

• HPUX11 migration � 1 full working day • Oracle 8.0.5 for HPUX11 install/Banner 3.x reconfiguration - 2 full working days • Oracle 8.0.5 to 8.1.6 upgrade/Banner 3.x reconfiguration � 2 full working days using the

preferred method. This includes overnight recompilation of processes. This time estimate increased by several hours using the alternate method, due to the need to create the database, pre-create tablespaces and Banner users, and then import the Banner data.

• Banner 4.x upgrades � 3 to 5 working days (dependent upon length of working day) • Banner 5 Upgrade � No estimate, but it is a logical assumption that this upgrade would

require the same amount of time as the 4.x upgrades.

The steps to be taken to reach the targeted technical stack depend on which of several scenarios apply to the campus� environments. The following matrix shows the relevant section to be considered when moving from HPUX 10.20 to HPUX11 on new servers.

Table 5 describes the steps that campuses should follow to reach the targeted Technical Stack using the preferred update method. Instructions for both installing on new servers and migrating on existing servers are included. Several scenarios are presented based on the source-to-target environments.

Table 5 - Steps in Upgrade to Targeted Technical Stack

Source Environment Target Environment Upgrade Path Comments HPUX 10.20, Oracle 8.0.5 database to be cloned

New HPUX 11 server, datafile pathnames to be same as on source 10.20 system (copied database)

Scenario1-HPUX11 New Server, old pathnames.p

New install, use copied database

HPUX 10.20, Oracle 8.0.5

New HPUX11 server, datafile pathnames to be different than on source 10.20 system (cloned database)

Scenario 2-HPUX11 New server, new pathnames

New install, use cloned database

HPUX 10.20 server, Oracle 8.0.5

Same HPUX server, migrated to HPUX 11, datafile location does not change

Scenario 3 � Migrate to HPUX11, old pathnames

Migration for HPUX 10.20 to 11.0, database files do not change



Source Environment Target Environment Upgrade Path Comments HPUX 10.20, Oracle 8.0.5 database to be cloned

New HPUX 11 server, datafile pathnames to be same as on source 10.20 system (copied database)

Scenario1-HPUX11 New Server, old pathnames.p

New install, use copied database

HPUX 10.20 server, Oracle 8.0.5

Same HPUX server, migrated to HPUX 11, datafile pathnames to be different than on source 10.20 system

Scenario 4 � Migrate to HPUX11, changed pathnames

Migration for HPUX 10.20 to 11.0, database files do change

Table 6 describes the conditional steps that campuses should follow to reach the targeted Technical Stack.

Table 6. Conditional Steps in Upgrade to Targeted Technical Stack

Step/Instructions Completion Condition Comments Install Developer 2000 1.6.1 for HPUX11 on target system

Complete this step if you need to generate and use character-mode forms (e.g., Voice Response 3.x forms).

NOTE: Oracle has separate releases of Developer 2000 1.6.1 for HPUX10.20 and HPUX11. These separate releases are NOT interchangeable. Installer must ensure that the proper version of this product is being installed.

Installation instructions may be accessed at the following link:

Developer 2000 1.6.1 Server Install

Install Developer 2000 Patchset 9 for HPUX11 on target system

Complete this step only after installing Developer 2000 1.6.1 for HPUX11 (previous step) for character mode forms support (e.g, Voice Response).

This patchset may be downloaded from the following location on ftp.usg.edu bnner/prod/oracle/hpux11/ dev2000r161_hpux11_32bit.tar.gz using the campus sw-dist account.

Installation instructions may be viewed here and are also included with the patchset distribution.

ftp://ftp.usg.edu/



Step/Instructions Completion Condition Comments Install Oracle Application Server (OAS4.0.8.2) for HPUX11 on target system

Complete this step when your webserver platform is upgraded to HPUX11.

Review Prerequisites for OAS4.0.8.2 and OAS 4.0.8.2 for HPUX11 Installation prior to installing.

Copy tnsnames.ora files into the $ORACLE_HOME/network/admin directory for the Oracle Application Server 4.0.8.2 product.

Complete this step immediately after installing Oracle Application Server 4.0.8.2 servlet patch.

Alternately, you may edit the script/environment used to startup the application server and set the TNS_ADMIN variable to point to the directory where the correct copy of the tnsnames.ora file resides.

Start the OAS4.0.8.2 nodemanager

Complete this step once you�ve upgraded to OAS4.0.8.2

On HPUX11 server, execute the script that sets up the OAS environment prior to starting up the Application Server.

Scenario 1 � New HPUX11 server, copied database, same filenames

Step Comments Verify that HPUX11 OIIT-TSS Release is installed on target system

A 4-gig disk drive will be required. Arrangements to receive the OIIT-TSS release of HPUX11 may be made by contacting the OIIT Solution Center at 1-888-875-3697.

Install Oracle 8.0.5 for HPUX11 32-bit on target system

Instructions for installation may be accessed at the following links:

Overview of install procedure

Oracle Server EE 8.0.5 Installation Guide Apply Patchset 8.0.5.2.1 for HPUX11 32-bit on target system

This patch may be downloaded from ftp.usg.edu in location banner/prod/oracle/hpux11/hpux_110_32bit_80521patchset.tar.gz. Follow the instructions for installing Patch 80521 for HPUX11-32 link for installation instructions.

Apply pre-compiler bugfix 991197 This patch may be downloaded from ftp.usg.edu in location banner/prod/oracle/hpux11/hpux_11_32bit_bug991197.tar.gz. Instructions for applying bugfix 991197 may be viewed here and are also included in the patchset distribution file.

Apply the Intelligent Agent patch. Oracle Intelligent Agent Patch

ftp://ftp.usg.edu/

ftp://ftp.usg.edu/



Step Comments Obtain list of files to be transferred from source database on HPUX 10.20 system

Invoke svrmgrl, connect internal, spool output to a file, enter the following svrmgrl commands:

>>select name from v$datafile;

>>select name from v$controlfile;

>>select member from v$logfile; Perform a shutdown normal on the source database (10.20) system

Copy all the associated database files from the 10.20 source machine to the same pathname structure on the HPUX11 machine.Be sure to include the .ora and miscellaneous files (init.ora, config.ora, listener.ora, sqlnet.ora, tnsnames.ora, coraenv, oraenv, and entries for the oratab file).

Create symbolic links from the /oracle/admin/<SID>/pfile/init<SID>.ora file to the $ORACLE_HOME/dbs directory on the new system

Verify entries in the /etc/oratab for the target database on the HPUX11 machine

Add any needed local changes to the oraenv/coraenv files on the HPUX11 machine

Startup the database Edit the listener.ora and remove any entries for databases not present on the HPUX11 server

Startup the sqlnet listener Shutdown the database and restart it to make sure that shutdown/startup is successful

Re-configure Banner 3.x if needed (re-compile Pro*C and Pro*Cobol processes)

New makefiles for HPUX11 are located on the ftp server in the banner/prod/oracle/hpux11 directory. Also, a new guastdf.h and guastdf.o are required for HPUX11.

Make a backup copy of $ORACLE_HOME/bin/dbshut

Edit $ORACLE_HOME/bin/dbshut and change the command that perform �shutdown� to �shutdown immediate�

This will help to ensure a more timely shutdown of the database. This is an OPTIONAL step. OIIT uses this step in beta testing and in our internal production support environments.



Step Comments Verify prerequisite settings for installing Oracle Application Server 4.0.8.2

OAS4.0.8.2 PreReqs

Install OAS4.0.8.2 OAS4.0.8.2 Installation

Scenario 2 � New HPUX11 server, cloned database, new filenames

Step Comments Verify that HPUX11 OIIT-TSS Release is installed on target system








Apply the Intelligent Agent patch. Oracle Intelligent Agent Patch Backup current database controlfile Invoke svrmgrl, connect internal, spool output

to a file, enter the following svrmgrl commands:

>>alter database backup controlfile to trace;

>>select name from v$datafile


>>select member from v$logfile; Locate the trace file from the �alter database� command, copy it to the /oracle/admin/<SID>/create directory on the target HPUX11 machine, edit the file to remove unnecessary lines and to reflect the new filenames.

This is the same procedure we�ve used in the past to clone databases.

ftp://ftp.usg.edu/

ftp://ftp.usg.edu/



Step Comments Perform a shutdown normal on the source database (10.20) system

Copy all the associated database files from the 10.20 source machine to the same pathname structure on the HPUX11 machine. Be sure to include the .ora and miscellaneous files (init.ora, config.ora, listener.ora, sqlnet.ora, tnsnames.ora, coraenv, oraenv, and entries for the oratab file).

Create symbolic links from the /oracle/admin/<SID>/pfile/init<SID>.ora file to the $ORACLE_HOME/dbs directory


Add any needed local changes to the oraenv/coraenv files on the new HPUX11 machine

Use the modified trace file on the HPUX11 machine to recreate the control file for the new database.

This is basically the same procedure as cloning a database.

Open the database. Reset the global name for the new database.

Edit the listener.ora and remove any entries for databases not present on the HPUX11 server.

Edit the listener.ora, tnsnames.ora, and sqlnet.ora file and make any needed changes.

Startup the sqlnet listener Re-configure Banner 3.x if needed (re-compile Pro*C and Pro*Cobol processes)

New makefiles for HPUX11 are located on the ftpserver in the banner/prod/oracle/hpux11 directory. Also, a new guastdf.h and guastdf.o are required for HPUX11.






Scenario 3 - Upgrading existing HPUX 10.20 server, datafile names do not change

Step Comments Perform a cold backup of all existing databases. Leave the databases down.

This MUST be a backup performed following a successful shutdown normal of ALL databases that use the Oracle 8.0.5 home.

Save copies of .ora and parameter files (init.oras, config.oras, sqlnet.ora, tnsnames.ora, listener.ora, coraenv, oraenv, oratab)

Migrate to HPUX11 OIIT-TSS Release on target system


De-install Oracle 8.0.5 for 10.20.

Be sure that ALL 10.20 databases are shutdown normal before performing this step!!!

This is essentially a remove of the entire $ORACLE_HOME directory for Oracle 8.0.5 install. If you have Oracle products other than the Oracle RDBMS software installed into the same ORACLE_HOME, you will have to create a new ORACLE_HOME when you prepare to install the Oracle8.0.5 for 32-bit HPUX11 later.







Apply the Intelligent Agent patch. Oracle Intelligent Agent Patch Reinstate the .ora files, recreate the symbolic links in the $ORACLE_HOME/dbs directory to the /oracle/admin/<SID>/pfile/init<SID>.ora files.

Restore the oraenv/coraenv files

ftp://ftp.usg.edu/

ftp://ftp.usg.edu/



Step Comments Startup the databases Restore the listener.ora, sqlnet.ora and tnsnames.ora files

Startup the sqlnet listeners Re-configure Banner environment New makefiles are available on the ftp server Make a backup copy of $ORACLE_HOME/bin/dbshut



Scenario 4 - Upgrading existing HPUX 10.20 server, datafile names do change

Step Comments Perform a cold backup of all existing databases. Leave the databases shutdown.

This MUST be a backup performed following a successful shutdown normal of ALL databases that use the Oracle 8.0.5 home.

Save copies of .ora and parameter files (init.oras, config.oras, sqlnet.ora, tnsnames.ora, listener.ora, coraenv, oraenv, oratab)

Shutdown the sql*net listeners. De-install Oracle 8.0.5 for 10.20

Be sure that ALL 10.20 databases are shutdown normal before performing this step.

This is essentially a remove of the entire $ORACLE_HOME directory for Oracle 8.0.5 install. If you have Oracle products other than the Oracle RDBMS software installed into the same ORACLE_HOME, you will have to create a new ORACLE_HOME when you prepare to install the Oracle8.0.5 for 32-bit HPUX11 later.

Migrate to HPUX11 OIIT-TSS Release on target system

A 4-gig disk drive will be required to receive the OIIT-TSS Release. Arrangements to receive the OIIT-TSS release of HPUX11 may be made by contacting the OIIT Solution Center at 1-888-875-3697.




Oracle Server EE 8.0.5 Installation Guide



Step Comments Apply Patchset 8.0.5.2.1 for HPUX11 32-bit on target system


Apply pre-compiler bugfix 991197 This patch may be downloaded from ftp.usg.edu in location banner/prod/oracle/hpux11/hpux_11_32bit_bug991197.tar.gz. Instructions for applying bugfix 991197 may be viewed here are also included in the patchset distribution file.

Apply the Intelligent Agent patch. Oracle Intelligent Agent Patch Backup current database controlfile Invoke svrmgrl, connect internal, spool output to

a file, enter the following svrmgrl commands:

>>alter database backup controlfile to trace;

>>select name from v$datafile


>>select member from v$logfile; Locate the trace file from the �alter database� command, copy it to the /oracle/admin/<SID>/create directory for the target database in the newly upgraded HPUX11 environment, edit the file to remove unnecessary lines and to reflect the new filenames.

This is the same procedure we�ve used in the past to clone databases.

Copy all the associated database files from the 10.20 source database to the new pathname structure on the newly upgraded HPUX11 machine. Be sure to include the .ora and miscellaneous files (init.ora, config.ora, listener.ora, sqlnet.ora, tnsnames.ora, coraenv, oraenv, and entries for the oratab file).

Create symbolic links from the /oracle/admin/<SID>/pfile/init<SID>.ora file to the $ORACLE_HOME/dbs directory


Add any needed local changes to the oraenv/coraenv files on the new HPUX11 machine

ftp://ftp.usg.edu/

ftp://ftp.usg.edu/



Step Comments Use the modified trace file on the HPUX11 machine to recreate the controlfile for the new database.

This is basically the same procedure as cloning a database

Open the database Reset the global name for the new database

Edit the listener.ora and remove any entries for databases not present on the HPUX11 server

Edit the listener.ora, tnsnames.ora, and sqlnet.ora file and make any needed changes.

Startup the sqlnet listener Re-configure Banner 3.x if needed (re-compile Pro*C and Pro*Cobol processes)

New makefiles for HPUX11 are located on the ftp server in the banner/prod/oracle/hpux11 directory. Also, a new guastdf.h and guastdf.o are required for HPUX11.




Startup the databases Restore the listener.ora, sqlnet.ora and tnsnames.ora files

Startup the sqlnet listeners

Installing Oracle 8.0.5 for HPUX11

Use these instructions in conjunction with Scenarios 1 � 4 for installing Oracle 8.0.5 in the new HPUX11 environment.

Oracle Installation Instructions - Running Orainst

IMPORTANT -- Prior to running the install make a copy of /etc/oraenv and coraenv. Or do not run root.sh when complete. Ensure that the environment variables for TERM and ORACLE_TERM are both set to vt220. This setting has worked best for keystroke functionality when using the installer.



Oracle Installation Process: Mounting an Oracle CD

As the root user at the Unix command prompt, enter the following:

ps -fe|grep pfsd

If the grep returns a row indicating that the pfsd process is running, go to step 4.

The Oracle Product Installation media is in the RockRidge format.

1. Use a system editor to add the following line to the /etc/pfs_fstab file

Syntax <device_file<mount_point<filesystem_type<translation_method

Example: /dev/dsk/c5t2d0 /SD_CDROM pfs-rrip xlat=unix 0 0

Perform the following as root:

2. # nohup /usr/sbin/pfs_mountd & 3. # nohup /usr/sbin/pfsd & 4. Insert the CD-DROM into the tray and run the following to mount the CD-ROM. The command assumes that a link exists to actual cdrom device name. # /usr/sbin/pfs_mount /dev/cdrom /SD_CDROM 5. # exit

Verify the correct mounting by:

cd /SD_CDROM/orainst ls All files and sub directories should be listed in lower case.

Run the installer: ./orainst

WARNING: Do not run the installer as root. (Oracle will give you a nasty warning and abruptly end)

Installer prompts:

Installation Type: choose �custom� Read the new features screen. Read the README screen. Installation Activity: choose �Install, Upgrade, or De-install Software' Installation Options: choose �Install New Product do not create DB objects�

Enter the mount point for your Oracle CD Verify values for ORACLE_HOME AND ORACLE_BASE



Verify the location of the log files. Select the CD-ROM as the installation source. Choose American-English as the NLS language to install. Verify your request to re-link after the installation � default is NO. Verify the location of root.sh.

WARNING: Do not load the documentation on to the Unix Server from this CD-ROM. The vendor did not include all the files necessary to install and thus causes the install to abruptly end.

Software Manager Selections: CLIENT SOFTWARE 8.0.5.0.0 NET8 8.0.5.0.0 ORACLE INTELLIGENT AGENT 8.0 ORACLE ONLINE TEXT VIEWER

ORACLE UNIX INSTALLER 4.0.3 ORACLE ENTERPRISE (RDBMS) ORACLE JDBC DRIVERS +PRECOMPILERS PROC/C++ 8.0.5.0.0 PROCOBOL 8.0.5.0.0 PROCOBOL 1.8.27 SQLPLUS 8.0.5 +NET8 PROTOCOLS TCP/IP PROTOCOL ADAPTER PL/SQL 8.0.5

Although these are not all the install choices, these are the ones tested during the product installation beta tests. If you need other options, select them during this phase of the installation process.

Select 'install' from the menu items.

Applying the 8.0.5.2 Patch

You must now install the upgrade to 8.0.5.2 for HPUX 11. You need to install the precompiler component after the other components. During the install of the patch, you see 3 options on the available product screen:

• Oracle Enterprise • PL/SQL • Precompilers

First, select Oracle Enterprise and PL/SQL and proceed to install. When prompted, select "Yes" to relink.



Once that installation is complete, then go back and install the precompilers. When prompted, select "Yes" to relink.

WARNING: It is not necessary to run root.sh and you should not do so. If you run root.sh, it will overwrite your oraenv and your coraenv files.

You must now install the upgrade to 8.0.5.2.1 for HPUX 32-bit.

Applying bugfix 991197 for Oracle 8.0.5 HPUX11

Use the following instructions for applying the fix for Oracle bug 991197. This bugfix should be applied after the Oracle 8.0.5 for HPUX11 and the Oracle 8.0.5.2.1 Patch for HPUX11 have been applied.

Instructions to apply patch for bug 991197

-------------------------------------------

This patch must be applied to Precompiler 8.0.5.2.1 on HPUX 11.00 .

This patch consists of following files:

README.991197

shrept.lst

Steps to apply the patch:

------------------------

1. Save old version of shrept.lst:

%cd $ORACLE_HOME/precomp/admin

# save existing libraries in new files with bug no. as suffix.

%cp -p shrept.lst shrept.lst_pre991197

2. Copy the new version of shrept.lst to the precomp/admin directory

%cp <patchlocation>/shrept.lst $ORACLE_HOME/precomp/admin

3. Shutdown all the databases



4. Rebuild libclntsh.sl

% $ORACLE_HOME/bin/genclntsh

5. Rebuild all applications affected by the client shared library.

How to Re-link Oracle Executables

Shutdown the instance that you are relinking.

Start orainst from $ORACLE_HOME/orainst

Select "Custom Install." Skip the "Welcome to the New Oracle Installer" page. Skip the "ORACLE8 Release 8.0.5.0.0 Important Pre-Install Information page. On the "Select the Installer activity screen," select Perform Administrative Tasks. Enter or Verify the $ORACLE_HOME variable. Correct or take the default Log File Locations. From the "Select one or more maintenance tasks" screen, select Relink Product Executables.

From the Software Asset Manager, select the Oracle Product that you want to relink (the precompilers). Tab to the Install option.

The system will ask you the following questions:

1. What group is the Oracle user in? (dba) 2. What group is osoper? (dba)

The relink should run to completion. After it completes, exit the orainst utility.

6. Start up the databases.

Note: For client-only installs, steps 3 can be omitted.

Apply the Intelligent Agent Patch

Use the steps defined below to install the Oracle Intelligent Agent patch. This patch may be applied to any Oracle 8/8i environment.



1. Get the setuid.tar file from the ftp server in banner/prod/oracle/hpux11.

2. Unzip and untar the file in the staging directory.

3. Run - sh setuid-patch.shl

This will reset the sticky bit on the file permissions to stop unwanted access to the system.

You should get 8 to 10 files that are corrected.

Upgrading to Oracle 8.1.6, with 8.1.6.3 Patch

Once the HPUX11 /Oracle 8.0.5.2.1 has been successfully applied to your system, you should plan and then execute the upgrade to Oracle 8.1.6 in test environment. Review the Step by Step Oracle 8.1.6 upgrade instructions prior to beginning the upgrade process. This document lists very specific step by step instructions for the upgrade process.

Annotations from HP11upgplan.pdf

Page 1

Annotation 1; Label: OIIT; Date: 4/23/2001 3:20:31 PMWarnings, changes, tips, and advice from the ongoing installation workshops and campusinstallations are being added to the document as electronic "sticky notes."

Notes have been added for the following dates:2/15/01

For a complete list of these annotations, select "annotations" from the bookmarks.

Page 15

Annotation 1; Label: OIIT; Date: 4/23/2001 3:22:01 PM2/15/01

While OIIT has been successful in configuring OAS 4.0.8.2 to work with 8.0.5.2.1 Banner databaseson HPUX11, please understand that we are working in a pristine environment. However, Oracle nolonger supports this specific infrastructure combination. Should campuses choose to operate in thisenvironment, and unknown issues/errors arise, the only option available is to upgrade the RDBMS to8.1.6.3