[385] in Tooltime
Scopus/Oracle upgrade
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Fri Feb 14 08:26:51 1997
Date: Fri, 14 Feb 1997 08:27:21 -0500
To: ds-ask@MIT.EDU
From: Steven Wade Neiterman <wade@MIT.EDU>
Here is the information from Scopus on support of their product with
Oracle. When you read about Scopus version numbers, MIT is at release
3.6.2.1 of Scopus.
It appears that we need a patch for Oracle 3.6.2.1. If we implement the
patch, then I feel it's fine to move to this release on the test machine.
..Steve
----------
From: Jill Smolen
Sent: Thursday, February 13, 1997 7:02 PM
To: Dennis Dallin
Subject: RE: Oracle question with Scopus 3.6.2.1
7.2.3 is certified as per tan 495. However, it requires an Oracle patch.
Oracle 7.3 is not yet certified.
TAN 495
Problem
-------
Release 3.6.1 and 3.6.2.1 of the Scopus application has been tested and
certified on a 7.1.3 Oracle database. Although we have tested Scopus
applications on Oracle versions 7.1.4, 7.1.6 and 7.2.x, an Oracle bug (Bug
ID:
318811, tar# 10171222.61) prevents certification of Scopus applications with
this version.
The problem identifies itself to Scopus users with the following error
message:
ORA-00600 internal error code arguments [13012]
When the porblem occurs
-----------------------
The problem occurs when the triggers that update Scopus long description
fields
are activated. Disabling the update triggers avoids the problem, but Scopus
applications need the triggers for updating.
Solution
--------
Oracle has created a patch which fixes this problem. Please contact
Oracle and
request the patch for Bug ID: 318811.
The following tables include the tested and supported platforms, operating
systems and database configurations supported by Scopus Technology:
Platforms
3.5 3.6.1 3.6.2.1
-------
HP-UX 9.00 & 9.01 9.05 9.05 & 10.x
SunOS 4.1.2 & 4.1.3 4.1.3 4.1.3
Sun Solaris 2.3 & 2.4 2.4 2.4 & 2.51*
IBM AIX 3.2 3.2 3.2 & 4.1
Windows NT 3.5 3.5.1 3.5.1, 4.0
Windows 95 n/a 4.0 4.0 Windows for
Workgroups 3.11 3.11 3.11
Mac 7.1 7.1 7.1
*(A problem was discovered with Soalris 2.5 that caused the first connections
from a PC to any database running on Solaris 2.5 to crash the database server
the first time after performing a Scopus Setup. Subsequent PC connections are
fine. The problem is solved by upgrading Solaris to 2.5.1. For Sybase, EBF
6329 is also required.)
(Windows shell under OS/2 Warp is supported because executables are tested on
compatible platforms. Tests are not done for each release. We did test the
configuration with Scopus 3.6.1.)
Databases
3.0.1 3.5 3.6.1 3.6.2.1
-------
Sybase 4.9.1 & 4.9.2 4.9.2 4.9.2, 10.02 4.9.2, 10.02*, 11**
Oracle n/a 7.1.3 7.1.3, 7.1.6 7.1.3, 7.1.6*, 7.2.3**
*(Oracle patches are required for Oracle 7.1.6 and 7.2.3 releases to work with
Scopus. Please call Oracle corporation at 415-506-1500 and request the patch
for bug 318811. This patch is platform, operating system, and Oracle version
specific. Different versions of this patch are available from Oracle. The
bug
prevents updates to long text fields when the data being updated is in the 2nd
page of memory. When it fails the user gets an unable to update message from
Scopus and an ORA-600 error.)
**(Oracle 7.3 has a bug that prevents setup of Scopus applications.
ORA-600 is
the error message that is received. This problem is referenced by Oracle TAR
9462143.6 and 9458501.6 Bug 371254). The bugs described in TARs 9462143.6
and 9458501.6 (bug 371254 (ora-600) and bug 372475 (validation of trigger if
dependent object is also invald). will be fixed in patch release 7.3.2.3.
This
is with the EXCEPTION of the sequencecs cache value "jump" problem described
in TAR 9462143.6.
Oracle 7.3.2.3 seems to resolve the problems described above however a major
new problem was discovered that impacts setup of Scopus add-on products. This
problem is referenced by Oracle TAR 9839913.6.
Oracle 7.3x does not supports V1 connections so ScopusWorks cannot be used to
administrate WorldTEAM.)
