Oracle & OpenVMS Delta-Time Restriction and 19-May-1997

From: Greg Scholey <Greg.Scholey_at_pipe.nova.ca>
Date: 1997/05/13
Message-ID: <3378A3DA.1D42@pipe.nova.ca>#1/1

FYI... For those using Oracle on openVMS platforms. You may also need to
refer to the TAR# 904221 (Canada) depending on your platform.

Just passing on the info, credit goes to: ORACLE Worldwide Customer Support

Greg...

Oracle Notes

Conference : platform.digital.alpha.openvms Topic : ALERTS/Known Problems
Note : Delta Time Issue (MAY19)
Date Created : 22-APR-97
Date Modified : 22-APR-97
Note ID : 45438

Title:                  OpenVMS Delta-Time Restriction and 19-May-1997 
Author:                 Peter P. Shih 
Department:             Midrange WorldWide Support 
Creation Date:          07 Mar 1997 
Last Revision Date:     16 Apr 1997   (Dave Hayter)
Expiration Date:        31 December 1998 
Revision Number:        3 
Distribution Code:      EXTERNAL 
Category:               MIDRANGE 
Product:                RDBMS 
Product Version:        V7 (and V6)
Platform:               VAX/VMS and ALPHA/OPENVMS
Information Type:       ADVISORY 
Impact:                 HIGH 
Abstract:               This bulletin describes what must be done with 
                        ORACLE after applying the Digital Delta-Time
ECO. 
Keywords:               ALPHA; VAX; OPENVMS; VMS; ECO; DELTA; TIME; 
                        ALPLIBR05_070; VAXLIBR05_070; VAXLIBR06_070 
 
----------------------------------------------------------------------------

The following Oracle Worldwide Customer Support bulletin is Oracle's response to DIGITAL's mandatory ECO which corrects the documented OpenVMS
Delta-Time Limit problem. This bulletin describes the steps that Oracle customers must perform after applying the DIGITAL ECO.

Background of Problem:

DIGITAL Engineering has discovered that OpenVMS customers may experience serious application errors beginning on or around 19-MAY-1997 at 00:00 time. A set of Engineering Change Orders (ECOs) are available to resolve
this problem.

All customers running the affected the versions of O penVMS MUST install the appropriate ECO as follows:

For OpenVMS Alpha Version 6.1 through Version 7.0: ALPLIBR05_070 For OpenVMS VAX Version 5.5 through Version 7.0: VAXLIBR06_070

Systems running OpenVMS Alpha Version 7.1 and OpenVMS VAX Version 7.1 ARE NOT AFFECTED and do not need to install the ECO.

If you are running VAX OpenVMS V5.5-2 and have previously applied the VAXLIBR05_070 ECO, you MUST apply the VAXLIBR06_070 ECO. Failure to do so may result in system crashes under certain circumstances.

FAILURE TO INSTALL THE APPROPRIATE ECO WILL CAUSE OPENVMS TO FAIL ***

DIGITAL proactively communicated this problem and solution to the OpenVMS
user community in February 1997. For more information about these DIGITAL
ECOs, please see DIGITAL's OpenVMS Systems Web page at the URL http://www.openvms.digital.com or use DSNLINK's Interactive Text Search using the ECO name as a keyword.

Ramifications to ORACLE:

In order for the above ECO's to be incorporated into the Oracle RDBMS software, it is necessary for ALL Oracle software to be relinked where it is resident on (Open)VMS platforms. The reasons for this requirement are that both the NETCONFIG and RDBMS products are linked against STARLET.OLB and all other products are linked with NETCONFIG and RDBMS.

Action to be taken

Shut down all Oracle databases and SQL*Net listeners.
Remove all ORACLE shareable images (REMORACLE, REMUTILITY).
Use ORACLEINS to relink NETCONFIG and RDBMS products. (the remaining products shown in the menues will be relinked automatically)
Relink all applications software (e.g. Precompiled programs, OCI programs, and Oracle Applications software).
Restart databases and SQL*Net listeners.
Test as required.
Release systems to users.

NOTE:
If running Oracle 7.3 on OpenVMS 7.0, upgrade to OpenVMS V7.1 if feasible.
Otherwise rebuild ORACLE as above. Received on Tue May 13 1997 - 00:00:00 CDT