Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Oracle Support Experiences

Re: Oracle Support Experiences

From: Hemant K Chitale <hkchital_nospam_at_singnet_nospam.com.sg>
Date: Mon, 11 Mar 2002 22:47:20 +0800
Message-ID: <a6ig15$b2l$1@coco.singnet.com.sg>

Yes, generally the level of support when you log an iTAR isn't impressive. Occassionally I do get surprised and find a quite competent analyst at the other end ---- but it is like playing the lottery and you can't afford to say to your boss "oh ... I'll just log a TAR and hope a good Analyst picks it up this time" when you hit a critical issue.

On the other hand, however, the number of technical notes and details available is quite high --- a careful search can quite well yield you the result [but it's not so easy when you are under pressure].

A suggestion:
"Personalise" your profile to include the "Product Lifecycle" Headlines section to be displayed at every login. Under "Lifecycle" settings include "Product Availablity" for at least "Oracle Server" and at least your major platform (Tru64, Solaris, AIX, HPUX whatever) if not "All Platforms". Also you MUST include "Product Alerts" for "Oracle Server" for "All Platforms" and Desupport Notices for "Oracle Server" for "All Platforms". Set your preferences to email you the Headlines every week or 14 days. My "Headlines" section includes "1. News & Notes", "2. Product Lifecycle" and "3. TAR".
You would find that the LifeCycle Headlines now include alerts like [the current set of 5 which are automatically shown to me whenever I login].
 ALERT: Oracle9i (9.0.1) Support Status and Alerts 11-MAR-2002 U  ALERT: Oracle8i Release 3 (8.1.7) Support Status and Alerts 11-MAR-2002 U  ALTER DATABASE CHECK DATAFILES does not work 08-MAR-2002 U  ALERT: Import with invalid TOUSER Clause can Drop Tables 08-MAR-2002 U  ALERT: "CONNECT INTERNAL" Syntax to be DeSupported 07-MAR-2002 U

The "Support Status and Alerts" alert is quite useful -- it has a collection of links on PatchSets, Release-specific alerts and "serious server issues".
e.g. the current 8.1.7 "Support Status and Alerts" list is : Support Status and Alerts for Oracle8i Release 3 (8.1.7.X) This note contains a list of the main issues affecting RDBMS release/s 8.1.7.X. 8.1.7 is also known as "Oracle8i Release 3" and is the terminal Oracle8i release. The first part of this note gives generic information - platform specific issues and differences can be found in the Platform Specific Addenda section at the end of the note. For other Server versions see <Note:161818.1>.
"*" against a line means the information is NEW since the last update.

Base Release Information
Information in this section is relevant for the 8.1.7.0 Base Release and for all Patch Sets which may be applied on top of 8.1.7.   Support Status

    Details of 8.1.7 desupport dates                       <Note:148054.1>

  Readme
    Oracle 8.1.7 README as shipped with 8.1.7.0            <Note:120608.1>

  Upgrade Information / Alerts
    Important checks before upgrading to 8.1.7            <Note:96117.1>
    Set _SYSTEM_TRIG_ENABLED=FALSE before upgrading        <Note:149948.1>
    Steps for MIGRATING from Oracle7 to Oracle8i           <Note:76460.1>
    Warning: NLS_DATE_FORMAT default values have changed   <Note:93924.1>
    Running CATALOG invalidates Queues (AQ)                <Note:151613.1>

  Notification of Changes in Future Releases     Advance warning of planned changes to support for the EURO

                           beginning in Oracle9i Release 2 <Note:152935.1>
    Advance warning of NCHAR issues with Oracle8i to 9i    <Note:140014.1>
    Advance notification of CONNECT INTERNAL desupport     <Note:50508.1>
    Advance notification of Server Manager desupport       <Note:74943.1>
Patch Sets
This section gives a summary of the patch sets available for 8.1.7. See <Note:120613.1> for a list of the GENERIC bug fixes included in the 817X Patch Sets. See the Platform Specific Addenda section to see if a Patch Set is available for a particular platform and for platform specific notes. Release Patch Set specific Issues
8.1.7.3 Current Patch Set - includes Java & interMedia fixes.  Corrupt data from Fast Refresh of Oracle7 mastered Snapshots <Note:175872.1>
 ORA-600 [729] possible with 8.1.7.3 (low impact) <Note:177527.1>  False ORA-1791 possible using duplicate binds <Bug:2216959> 8.1.7.2 Includes Java & interMedia fixes.
 XML scripts need to be run to complete upgrade      <Note:165463.1>
 Crash / Dump possible in kqr* under heavy load      <Bug:1951929>
8.1.7.1B Patch set with Java & interMedia fixes.
 8171 may not Startup / not allow lots of SESSIONS  <Note:153041.1>
 Missing Upgrade Instructions for interMedia Text   <Note:144947.1>
 8171 Patch Set causes Oracle Label Security errors <Note:148384.1>
 8171 Patch Set Install can cause iAS to Fail       <Note:143368.1>
8.1.7.1 Patch set without Java & interMedia fixes.
 8171 may not Startup / not allow lots of SESSIONS  <Note:153041.1>
 8171 Patch Set causes Oracle Label Security errors <Note:148384.1>
 8171 Patch Set Install can cause iAS to Fail       <Note:143368.1>
8.1.7.0 Oracle8i Release 3 Base Release.
 8170 Install Problem due to Multiple CD's          <Note:120801.1>


Alerts
The alerts listed here are those which affect Oracle 8.1.7.X releases. Entries in bold affect the current patch set (8.1.7.3).

    Serious Server Issues:

    Miscellaneous:

     Warning: UNLIMITED Extents / TEMPORARY tablespaces    <Note:50380.1>
     Listener Vulnerability Issues                         <Note:151318.1>
Platform Specific Addenda
This section lists the Patch Sets available for each platform, along with the Bug number against which the patch set is loaded. The Patch Set can be found in the Metalink Patches section using the Bug number as the "Patch ID" in the patch query screen.
Platform specific alerts and notices are included where relevant. The "ReadMe" links point to the README for the patch set. Ensure this is read in combination with any notices from the generic Patch Sets section above. Compaq OpenVMS (Alpha)
8.1.7.3 <Bug:2189751>  ReadMe Patch Set includes the fix for <Bug:2220356>
8.1.7.2.0 There are no plans to release 8.1.7.2 on Alpha VMS
8.1.7.1.0B <Bug:1746764>  ReadMe

Compaq Tru64 Unix
8.1.7.3 <Bug:2189751>  ReadMe
8.1.7.2.1 <Bug:1909158>  ReadMe
8.1.7.2.0 Obsoleted. See <Note:153172.1>
8.1.7.1.0B <Bug:1746764>  ReadMe
8.1.7.1.0 <Bug:1650103>  ReadMe

Data General AViiON Series [IX86] UNIX
8.1.7.3 There are no plans to release 8.1.7.3 on DGUX 8.1.7.2.0 <Bug:1882450> ReadMe
HPUX-11 (64-bit Oracle)
8.1.7.3 <Bug:2189751>  ReadMe
8.1.7.2.1 <Bug:1909158>  ReadMe
8.1.7.2.0 Obsoleted. See <Note:153172.1>
8.1.7.1.0B <Bug:1746764>  ReadMe
8.1.7.1.0 <Bug:1650103>  ReadMe

HPUX-11 (32-bit Oracle)
8.1.7.3 <Bug:2189751>  ReadMe
8.1.7.2.1 <Bug:1909158>  ReadMe
8.1.7.2.0 Obsoleted. See <Note:153172.1>
8.1.7.1.0B <Bug:1746764>  ReadMe
8.1.7.1.0 <Bug:1650103>  ReadMe

IBM AIX 64-bit
8.1.7.3 <Bug:2189751>  ReadMe
8.1.7.2.0 <Bug:1882450>  ReadMe
8.1.7.1.0B <Bug:1746764>  ReadMe
8.1.7.1.0 <Bug:1650103>  ReadMe

IBM AIX 32-bit
8.1.7.3 <Bug:2189751>  ReadMe
8.1.7.2.0 <Bug:1882450>  ReadMe
8.1.7.1.0B <Bug:1746764>  ReadMe
8.1.7.1.0 <Bug:1650103>  ReadMe

IBM NUMA-Q DYNIX/ptx
8.1.7.3 <Bug:2189751>  ReadMe Patch Set includes the fix for <Bug:2220356>
8.1.7.2.0 <Bug:1882450>  ReadMe
8.1.7.1.0 <Bug:1650103>  ReadMe

IBM OS/390 (MVS)
8.1.7.X » Loop in OSDI database address space possible. See <Note:174378.1>
8.1.7.3 <Bug:2189751>  ReadMe Patch Set includes the fix for <Bug:2220356>
8.1.7.2.0 <Bug:1882450>  ReadMe

Linux
8.1.7.X » Install problems on Red Hat Linux 7.1 <Note:159994.1>
8.1.7.3 <Bug:2189751>  ReadMe
8.1.7.2.0 <Bug:1882450>  ReadMe
8.1.7.1.0B <Bug:1746764>  ReadMe
8.1.7.1.0 <Bug:1650103>  ReadMe

SGI 64-bit UNIX
8.1.7.3 There are no plans to release 8173 on SGI64 8.1.7.2.0 <Bug:1882450> ReadMe
Siemens RM200-RM600
8.1.7.3 There are no plans to release 8173 on Siemens 64bit 8.1.7.2.0 <Bug:1882450> ReadMe
Siemens MPP RM1000 Reliant Unix (DC/OSX) 8.1.7.3 There are no plans to release 8173 on Siemens 64bit 8.1.7.2.0 <Bug:1882450> ReadMe
Sun Solaris V2 Intel
8.1.7.3 There are no plans to release 8.1.7.3 on Intel Solaris
8.1.7.2.1 <Bug:1909158>  ReadMe
8.1.7.2.0 Obsoleted. See <Note:153172.1>
8.1.7.1.0B <Bug:1746764>  ReadMe
8.1.7.1.0 <Bug:1650103>  ReadMe

Sun SPARC Solaris 32-bit
8.1.7.3 <Bug:2189751>  ReadMe
8.1.7.2.0 <Bug:1882450>  ReadMe
8.1.7.1.0B <Bug:1746764>  ReadMe
8.1.7.1.0 <Bug:1650103>  ReadMe

Sun SPARC Solaris 64-bit
8.1.7.3 <Bug:2189751> ReadMe
8.1.7.2.0 <Bug:1882450> ReadMe
UnixWare
8.1.7.3 There are no plans to release 8173 on Unixware 8.1.7.2.0 <Bug:1882450> ReadMe
Windows NT / Windows 2000
8.X » Server Patches on Microsoft Platforms <Note:161549.1>
8.1.7.3 <Bug:2189751>  ReadMe
8.1.7.2.0 <Bug:1882450>  ReadMe Patch Set can cause Oracle Enterprise
Manager errors <Note:155437.1>
8.1.7.1.1 <Bug:1711240> ReadMe
8.1.7.1.0B There is no 8.1.7.1.0B on NT

[e.g. Niall's problem is immediately visible in the list above -- Note 148894.1]

Another useful area is the "Top Tech Docs" Keep visiting it frequently. Articles are quite well categorised there.

A third suggestion is to view "Desupport Notices" and "Alerts" from the "Product Lifecyle" Tab

Remove the "_nospam" from my email-ID and domain name hkchital_nospam_at_singnet_nospam.com.sg

Hemant K Chitale
http://hkchital.tripod.com
"Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote in message news:3c8c7afd$0$8511$ed9e5944_at_reading.news.pipex.net...
> What are peoples experiences of Oracle support like? The reason I ask is
> that whilst I have had a number of good experiences over the years the
last
> two calls I have logged have not been quite up to the standard I'd expect.

>

> In the first case we hit a known intermedia bug in 8.1.6 which is fixed in
> the 8.1.6.1 patchset for intermedia. It turns out that this patchset is
just
> not available for windows platforms. We therefore had to reinstall
> intermedia and recreate all of our text indices. We would have to do this
> every time we hit the error. Naturally two days later we hit the error on
a
> second instance. This time I phoned support thinking perhaps that the
> patchset was available on cd just not for download. This was not the case
> but the analyst did some investigating and found that the bug could be
fixed
> by applying some scripts from the solaris patchset. This fix is (according
> to the analyst) noted in hidden text in the original bug report and
> resolution!

>
> In the second case we hit the bug pointed out by Herman in his reply on
this
> newsgroup last week. There are evidently similar bugs in some Oracle
> versions on *nix. This bug was not noted by oracle support despite my
asking
> for an explanation of the problems we had. To say the least I consider a
bug
> that results in dataloss because of hitting arbitrary datafile sizes
serious
> enough to be imprinted on the minds of support analysts and also really
> ought to come up in a search of the bug database.
>

> I think what I am saying is common is that known bugs and fixes exist and
> are documented but appear not to be being given as answers to TARs. This
> concerns me somewhat.
>

> --
> Niall Litchfield
> Oracle DBA
> Audit Commission UK
> *****************************************
> Please include version and platform
> and SQL where applicable
> It makes life easier and increases the
> likelihood of a good answer
>

> ******************************************
> >
Received on Mon Mar 11 2002 - 08:47:20 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US