Monday Oct 07, 2013

Master Note For Database and Client Certification

For most current information refer:

Master" Note For Database and Client Certification [ID 1298096.1]

In this Document
  Purpose
  Scope and Application
  Master Note For Database and Client Certification
     Main Note
     General
     Using My Oracle Support Effectively


Applies to:

Information in this document applies to any platform. 

Purpose

This Master Note is intended to provide an index and references to the most frequently used My Oracle Support notes with respect to Oracle Certify and Oracle Database Server/Client.

Scope and Application

This note is applicable to all levels of expertise.

Master Note For Database and Client Certification

Main Note

Note 1295603.1 Locate Database Server Certification Information on My Oracle Support

General

Note 763087.5 Tips for Finding Certifications in Classic Certify

Note 161818.1 Oracle Database (RDBMS) Releases Support Status Summary

Note 207303.1 Client / Server / Interoperability Support Between Different Oracle Versions

Note 77627.1 Oracle Database Server product support Matrix for Windows 2000

Note 1062972.1 Locate Oracle Database Server Certification Information for Microsoft Windows Platforms

Note 824935.1 Where To Find Oracle Patchset/Software for Specific Server/ Hardware Model?

Note 942852.1 Oracle VM and VMWare Certification for Oracle Products

Note 750215.1 Which OS File Systems Are Certified For Single Instance Oracle Databases?

Note 403202.1 Certification of Zeta File System (Zfs) On Solaris 10 for Oracle RDBMS

Note 1075717.1 Installing 32-bit RDBMS Client software on x86_64 Linux.

Note 870253.1 32-bit Client Install on 64-bit Windows Platform

Note 753601.1 SUPPORT FOR ORACLE DATABASE ON WPARS UNDER AIX 6.1

Note 1194734.1 Where do I find that on My Oracle Support (MOS) [Video]

Note 971464.1 FAQ - 11gR2 requires Solaris 10 update 6 or greater

 

Using My Oracle Support Effectively

Note 374370.1 New Customers Start Here

Note 868955.1 My Oracle Support Health Checks Catalog

Note 166650.1 Working Effectively With Global Customer Support

Note 199389.1 Escalating Service Requests with Oracle Support Services


 

Sunday Apr 07, 2013

Oracle Support Social Media and Communities

Oracle Database support also has a Facebook page and Twitter account!

We invite you to follow / like us here and get the latest information on hot topics and database support news:

Facebook:   https://www.facebook.com/OracleDatabaseSupport

Twitter:  https://twitter.com/OracleDBsupport  @OracleDBsupport

Thursday Jul 14, 2011

Master Note for Diagnosibility

Master Note for Diagnosibility (Oracle Database)

This Master Note is intended to provide a summary, index and references on topics around diagnosibility.
This  includes:
 - What is diagnosibility ? 
 - What's new with the 11g diagnosibility concept?
 - How to gather diagnostic data for different releases? 
 - How to upload diagnostic files to Oracle support? 
 - How to verify uploads? 
 - Known Problems

 This Master Note is subdivided into categories to allow for easy access and reference to notes that are applicable to your area of interest, within diagnosibility.  

What is Diagnosibilty?

Actually diagnosibility has different meanings:
Fault diagnosibility captures diagnostic data, such as dump files or core dump files, on the OCCI client when a problem occurs. 

In pre 11g databases diagnosibilty based on single files like alert.log and process tracefiles.

With 11g 'Diagnosibility' was introduced as a feature that simplifies collecting the diagnostic information and sending this infornation to support. Diagnosibilty covers the whole process from data collection, package creation,  package upload to ORACLE and package investigation at ORACLE support. The overall view is called Diagnosibilty Framework (DFW)
RDBMS diagnostic data has been reorganized and are stored in a common directory structure named ADR (Automatic Directory Repository)  ADR contains different diagnostic files of xml format in a database-like structure.

Getting started

<<Note 1292665.1>> - Oracle Database Support Newsletter - February, 2011

Packaging

1. Package types

Packages can be categorized as following:

Description base type DB version  file format upload target
standard OS package

Y

all

tar, gz, zip

GTCR
RDA (Remote Diagnostic Agent)

Y

all

zip

ADR Repository
IPS (11g Incident Packaging Service)

Y

11.1 
and higher

zip

ADR Repository
IPS + RDA (bundle)

N

11.2.0.2
and higher

zip

ADR Repository
OCM (Oracle Configuration Manager)

Y

8.1.7
and higher

ocmconfig.jar

Configuration repository
OCM + RDA (bundle)

N

8.1.7
and higher

zip

Configuration Repository &
ADR Repository

 

2. Incident Packaging Services (IPS)  

There are 2 options to create IPS packages:

2.1 Commandline Interface (ADRCI)

For IPS package creation in general and use of command line utility (ADRCI) refer to:

<<Note 443529.1>> - 11g Quick Steps to Package and Send Critical Error Diagnostic Information to Support [Video]

2.2. GUI (SWB)

For use of Support Workbench - the graphical user interface refer to:

<<Note 1091653.1>> - 11g Quick Steps - How to create an IPS package using Support Workbench [Video]

Upload Diagnostic Data

Diagnostic files and packages can be uploaded to ORACLE using My ORACLE Support (MOS) the graphical customer user interface. This requires a Service Request (SR). The upload should not be interrupted or stopped. Once completed you will receive a completion message and SR becomes automatically updated with different upload status details. These messages can be used by support or customers to check upload status.

Verify Uploads in MOS

In order to examine upload messages, open your SR in MOS and verify following settings:

set [Filter By] to <-- Show all Entries -->
uncheck [Hide System Messages] checkbox

Package Processing - Step 1 (virus scan)

Each incoming package or file will be processed by virus scan first. After completion you will see a message like:

Virus Scan successfully completed for RDA.RDA_dwhprod.zip.
If you see this message, this will indicate that your file was successfully uploaded and received by ORACLE.

Package Processing - Step 2 (package specific actions)

After Virus Scan package and file processing depends on package type. Different types have different processing. The following will summarize processing of base package types. Package bundles will be splited into base components and processed accordingly.

a) Standalone RDA packages will be moved and extracted to Global ADR Repository. Completion tag:

Auto generated message by RDA FUP :RDA.RDA_BBDD1.zip has been uploaded to the ADR Repository.


b) Standalone IPS packages will be moved to Global ADR Repository, extracted and processed by ADRCI. Completion tag:

Diagnostic file ORA600_20100526101903_COM_1.zip was successfully processed at Oracle by 11g Diagnostics


c) Configurations will be moved to Configuration Repository. Completion tag:

 Auto generated message by RDA-OCM FUP :ocmconfig.jar has been uploaded to Configuration repository.


d) Anything else - different from RDA, IPS or configurations - goes to Global Testcase Repository (GTCR)

Health Monitor

<<Note 466920.1>> - 11g New Feature: Health monitor
<<Note 951022.1 >> - How To Purge or Delete Health Monitor Checks After DBMS_HM.RUN_CHECK ?

Diagnostic Internals

<<Note 422893.1>> - 11g Understanding Automatic Diagnostic Repository
<<Note 750982.1>> - TRM Trace Files Getting Generated in 11g Database

FAQs

<<Note: Note 453125.1>> - 11g Diagnosability Frequently Asked Questions


Troubleshooting 

ADR - Purging and Retension

<<Note 564269.1>> - Retention Policy for ADR
<<Note 751082.1>> - Adrci Purge Does Not Clear the Text-formatted Alert.Log located in the Trace Folder
<<Note 975448.1>> - WHICH FILES ARE PART OF SHORTP_POLICY AND LONGP_POLICY IN ADR?


Tips and Tricks

1. How to create an incident for testing?
Attention: Don't use this in production systems !

<<Note 390293.1>> - Introduction to 600/7445 Internal Error Analysis


Diagnostic Tools

<<Note 559339.1>> - Diagnostic Tools Catalog
<<Note 153788.1>>  - ORA-600/ORA-7445 Error Look-up Tool





Sunday Jul 03, 2011

Master Note for Partitioning [ID 1312352.1]

++++++++++++++++++++++++++++++++++++++++++++++++++++
The complete and the most recent version of this article can be viewed
from My Oracle Support Knowledge Section.

Master Note for Partitioning [ID 1312352.1]
++++++++++++++++++++++++++++++++++++++++++++++++++++

In this Document
Purpose
Scope and Application
Master Note for Partitioning
Concepts/Definitions Section
How-To Section
Troubleshooting Section
Known issues
Additional Resources

References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Applies to:

Oracle Database Products > Oracle Database > Data Warehousing
Information in this document applies to any platform.

Purpose

This article is intended to give you a single reference point and to assist in quickly finding various information about partitioning.

Scope and Application

The document will cover the following topics:

Concepts/Definitions
How-To Section
Troubleshooting Section
Known issues
Additional Resources

Master Note for Partitioning

Concepts/Definitions Section

Overview of Partitioning
Partitioning enables you to decompose very large tables and indexes into smaller and more manageable pieces called partitions. Each partition is an independent object with its own name and optionally its own storage characteristics.

Partitioning offers these advantages:
  • Increased availability of mission-critical databases if critical tables and indexes are divided into partitions to reduce the maintenance windows, recovery times, and impact of failures.
  • Easier administration of schema objects reducing the impact of scheduled downtime for maintenance operations.
  • Reduced contention for shared resources in OLTP systems
  • Enhanced query performance: Often the results of a query can be achieved by accessing a subset of partitions, rather than the entire table. For some queries, this technique (called partition pruning) can provide order-of-magnitude gains in performance.

Relevant Links

Overview of Partitioning:

Oracle® Database Concepts 11g Release 2 (11.2) Part Number E16508-05 Chapter 4
Oracle® Database VLDB and Partitioning Guide 11g Release 2 (11.2) Part Number E16541-08

Relevant articles regarding partitions creation and maintenance:

Document   69715.1 Creating & Adding Table and Index Partitions
Document 165303.1  Examples about Insert into Range Partitioned Tables
Document 164874.1 Example of Script to Create a Range Partition Table
Document 166652.1 Example of Script to Maintain Range Partitioned Table

Document 149116.1 Oracle9i Partitioning Enhancements, LIST Partitioning
Document 209368.1 Range List Partitioning - Oracle 9.2 Enhancement

Document 276158.1 Partitioning Enhancements in Oracle 10g

Relevant articles regarding latest features:

Document 452447.1 11g Partitioning Enhancements
Document 785462.1 11g New Features:System Partitioning
Document 805976.1 11g New Features:INTERVAL PARTITIONING
Document 943567.1 11g new feature: Extended Composite Partitioning (Overview, Example and Use)
Document 761251.1 Oracle 11G Reference Partitioning examples
Document 466352.1 11g Feature: Interval Partitioning Example
Document 757754.1 Interval Partitioning By Week

Relevant articles regarding partition pruning:

Document 179518.1 Partition Pruning and Joins
Document 166118.1 Partition Pruning/Elimination (This article provide a very detailed example of how to identify which partitions/subpartitions were accessed during an execution of a statement using event 10128)

How-To Section

How to Partition a Non-partitioned Table

Document 1070693.6 How to Partition a Non-partitioned Table
Document 472449.1   How To Partition Existing Table Using DBMS_Redefinition

'How to' relevant articles for partitioning types

Document 854332.1 How To Introduce Interval Parititioning into a Range Partitioned Table
Document 165701.1 How to Implement Hash Partitioning on IOT Tables in 9i & Above
Document 1266993.1 How To Use Multicolumn Partitioning Keys

Document 74181.1 Partitioning Tables with User-Defined Types and LOBs

Document 1304370.1 How to use Partition Names for ref partitioning tables when Split is used
Document 854332.1 How To Introduce Interval Partitioning into a Range Partitioned Table

Document 846405.1 How To Change the Partition Column Of A Partitioned Table Using DBMS_Redefinition

'How to' relevant articles for partitioned indexes:

Document 69374.1 Partitioned Indexes: Global, Local, Prefixed and Non-Prefixed
Document 74224.1 How to Create Primary Key Partitioned Indexes 
Document 795854.1 How To Update Both Global and Local Indexes when Moving Table Partition?

'How to' relevant articles for statistics collection when partitions are used:

Document 175258.1 How to Compute Statistics on Partitioned Tables and Indexes
Document 237538.1 How to Move from ANALYZE to DBMS_STATS on Partitioned Tables - Some Examples
Document 111990.1 ORA-14508: ANALYZE PARTITION TABLE VALIDATE STRUCTURE CASCADE
Document 1050294.1 STALE_STATS OF SUB PARTITION INDEX REPORTED INCORRECTLY IN DBA_TAB_STATISTICS
Document 1302628.1 Collect statistics for a large partitioned table takes a lot when incremental is used
Document 1319225.1 Collect incremental statistics for a large partitioned table in versions 10.2 and 11

Troubleshooting Section

Relevant bulletin articles for partitioning related issues:

Document 209070.1 Partition Pruning based on Joins to Partitioning Criteria Stored in Dimension Tables

Document 378138.1 What to check when the fast split partitioning does not appear as working?
Document 232628.1 Fast Split partitioning in 9iR2


Relevant articles for troubleshooting import slow issues with partitioning

Document 1073195.1 Data Pump Import (Impdp) slow when importing partitioned table 
Document 752904.1 DataPump Export of Partitioned Table is Very Slow and Apparently Hangs 
Document 1224663.1 IMPDP Raises ORA-39001, ORA-39203 When Importing A Partition Of A Partitioned Table Over A Network Link


Others
Document 1281826.1 What Types of Partitioning Are Eligible for Partition Change Tracking (PCT) Fast Refresh?

Known issues


Document 165599.1 Top Partitioned Tables Issues
Document 199623.1 Top Issues Encountered Regarding Split Partition
Document 166215.1 Top Partition Performance Issues
Document 372357.1 Fast Split Partitioning Not Ocurring When It Was Expected
Document 272312.1 How to Recreate a Table Partition After Having Dropped the Datafile?
Document 959116.1 Interval Partitioning Does Not Inherit Logging
Document 198120.1 Exchange Partitions - Common Problems

Document 1077819.1 PARTITIONED TABLE: CHANGE IN BUFFER_POOL FOR A PARTITION NEEDS A REBOUNCE

Relevant article to handle various errors:

Document 887659.1 Getting ORA-01410 for Partitioned Tables Without Any Apparent DDL On The Partitions.
Document 1081230.1 INTERVAL RANGE Partition Giving ORA-14400
Document 389804.1 Range Partition Splitting Fails with ORA-01882
Document 405922.1 ORA-07445 [evaopn2] Query With Bit Mapped Indexes And Partitioning
Document 1084542.1 Ora-600 Internal Error Code, Arguments: [Kkedsamp: Bad Partitioning Info.], [1290], [663],
Document 1050966.1 ORA-14652 When Using Reference Partitioning
Document 784989.1 ORA-600 [kdblGetRDBA] During Create Table with Compression and Partitioning
Document 790630.1 ORA-600 [Kkpamdgspam1] When Joining Partitioned Tables at Different Partitioning Levels
Document 727306.1 Ora-14074 When Trying To Add Partition

Dictionary issues introduced with partitioning

Document 1289275.1 OBJ$-PARTOBJ$-TABPART$ mismatch - Dictionary Inconsistency reported for Interval Range Partition Tables

Relevant article to handle size for partitioning

Document 729149.1 Table/Index (partition) Growth Is Far More Than Expected

Install partitioning option


Document 434743.1 Can The Partitioning Option Be Deinstalled When System Partitioned Objects Are Used
Document 430239.1 How To De-install Partitioning Option From Enterprise Edition?

Additional Resources

Community: Database DataWarehousing

This community has been set up for My Oracle Support (MOS) users, and is being moderated by Oracle. The goal of this community is to exchange database related Data Warehousing knowledge and concepts including Partitioning.

White Papers

Partitioning with Oracle Database 11g Release 2 (September 2009)
Partitioning in Oracle Database 11g (June 2007) 

Partitioning White papers are also accessible via Note 1329441.1

References

NOTE:1329441.1 - White Papers for Data Warehousing Components in the Oracle Database

Monday May 16, 2011

Troubleshooting ORA-1555 (Doc ID 1307334.1)

This article is intended to assist in finding tips and techniques to assist with finding solutions to ORA-1555 errors. The document will cover the following topics:

Concepts/Definitions
Diagnosing
Common Causes/Solutions

Concepts/Definitions

The ORA-1555 errors can happen when a query is unable to access enough undo to build
a copy of the data at the time the query started. Committed “versions” of blocks are
maintained along with newer uncommitted “versions” of those blocks so that queries can
access data as it existed in the database at the time of the query. These are referred to as
“consistent read” blocks and are maintained using Oracle undo management.

See Note 40689.1 - ORA-1555 "Snapshot too old" - Detailed Explanation for more about
these errors.

Diagnosing

Due to space limitations, it is not always feasible to keep undo blocks on hand for the life of the instance. Oracle Automatic Undo Management (AUM) helps to manage the time frame that undo blocks are stored. The time frame is the “retention” time for those blocks.

There are several ways to investigate the ORA-1555 error. In most cases, the error is a legitimate problem with getting to an undo block that has been overwritten due to the undo “retention” period having passed.

AUM will automatically tune up and down the “retention” period, but often space limitations or configuration of the undo tablespace will throttle back continuous increases to the “retention” period.

The error message is reported in the user session and often is not captured in the alert log. The user could see a message like

Using rollback segment functionality:
ORA-1555: snapshot too old (rollback segment too small)

or

Using AUM:
ORA-01555: snapshot too old: rollback segment number 9 with name "_SYSSMU9$" too small

If the error is captured in the alert.log, you would see something like

Tue May 26 16:16:57 2009
ORA-01555 caused by SQL statement below (SQL ID: 54yn3n36w24ft, Query Duration=922 sec, SCN: 0x0007.8a55f4e3)

Initial Investigation

Rollback Segments:
With Oracle 10g and later versions of Oracle, you can still use a Rollback Segments configuration. ORA-1555 errors in that environment still follow older guidelines as described in

Note 10579.1 - How many Rollback Segments to Have
Note 107085.1 - Tuning Rollback Segments
Note 69464.1 - Rollback Segment Configuration & Tips
Automatic Undo Management:
The database will be self tuning for undo when using Automatic Undo Management. This does not eliminate ORA-1555 completely, but does minimize ORA-1555 as long as there is adequate space in the undo tablespace and workloads tend to follow repeatable patterns. In some cases with periodic changes to workload (large data updates particularly with LOB data) the self tuning of undo can become aggressive and lead to undo issues.

Note 461480.1 - FAQ Automatic Undo Management (AUM) / System Managed Undo (SMU)
Note 135053.1 -How to Create a Database with Automatic Undo Management
Note 268870.1 - How to Shrink the datafile of Undo Tablespace
Note 231776.1 - How to switch a Database from Automatic Undo Management (AUM) back to using Rollback Segments
Note 296863.1 - How to Keep All UNDO Segments from Being Offlined in Oracle 10g - Fast Ramp-Up
LOB Issues:
Out-of-row LOB undo is maintained in the LOB segment. So the UNDO tablespace and undo retention is not associated with most LOB ORA-1555 issues. Instead the LOB column is created using either PCT_VERSION or RETENTION to manage how much space within blocks or time transpires before the LOB undo is overwritten. In environments with high updates, deletes on rows including LOBs, the chances of ORA-1555 on LOB undo is very high.

PCT_VERSION and RETENTION are not auto-tuned. To “tune” those configuration settings, you must change the values for PCT_VERSION or RETENTION. Changes to UNDO_RETENTION does not change LOB retention time frames.

Note 162345.1 - LOBS - Storage, Read-consistency and Rollback
Note 386341.1 - How to determine the actual size of the LOB segments and how to free the deleted/unused space above/below the HWM
Note 563470.1 – Lob retention not changing when undo_retention is changed
Note 422826.1 – How to identify LOB Segment Use PCTVERSION or RETENTION from Data Dictionary

Error Tracing

Undo error tracing can be done for normal undo operations using the following events:

NOTE: Normal undo operations will be indicated in the error message in that the error message includes a segment name like

…. name "_SYSSMU1$" too small

If the error doesn’t show a segment name

… name "" too small

the problem is often related to LOB undo
If using pfile:

event="10442 trace name context forever, level 10"

If using spfile:

Alter system set events '10442 trace name context forever, level 10';

Reproduce the ORA-1555 error and upload the trace file to Oracle Support.

LOB undo error tracing is more difficult. Set additional tracing events as follows:

Start Session 1
Alter session set events '10046 trace name context forever, level 12';
Reproduce the error
Exit Session 1

Start Session 2
Alter session set events '10051 trace name context forever, level 1';
Reproduce the error
Exit Session 2

Start Session
Alter session set events '1555 trace name errorstack forever, level 3';
Reproduce the error
Exit Session 3

Additional resources to review:
Note 846079.1 – LOBs and ORA-1555 troubleshooting
Note 253131.1 –Concurrent Writes May Corrupt LOB Segment When Using Auto Segment Space Management
Note 467872.1 – TROUBLESHOOTING GUIDE (TSG) – ORA-1555

V$UNDOSTAT Analysis

The V$UNDOSTAT view holds undo statistics for 10 minute intervals. This view
represents statistics across instances, thus each begin time, end time, and
statistics value will be a unique interval per instance.

This does not track undo related to LOB
Note 262066.1 – How To Size UNDO Tablespace For Automatic Undo Management
Note 1112363.1 – When Does Undo Used Space Become Available?
Note 240746.1 – 10g NEW FEATURE on AUTOMATIC UNDO RETENTION

Diagnostics Scripts

Refer to Note 746173.1 : Common Diagnostic Scripts for AUM problems
and Note 877613.1 : AUM Common Analysis/Diagnostic Scripts

Common Causes/Solutions

Using Rollback Segments functionality:

* Problem happening on SYSTEM tablespace that still uses old Rollback Segment functionality even when configured for Automatic Undo Management (AUM).

* There are not enough rollback segments to manage the undo needed for long running queries.

* Rollback Segments are too small and undo is overwritten before long running queries complete.
Reference:
Note 69464.1 – Rollback Segment Configuration & Tips
Note 10630.1 – ORA-1555: “Snapshot too old” – Overview
Note 862469.1 – ORA-604 & ORA-1555 Rollback Segment 0 with Name “System” Too Small

Using Automatic Undo Management (AUM):

* TUNED_UNDORETENTION in V$UNDOSTAT around the time of the error is lower than the QUERY DURATION indicated in the error message. This is a legitimate ORA-1555 and if queries are going to run for very long time frames, UNDO_RETENTION may need to be larger. Auto-tuned retention may not be able to keep up with the undo workload and staying within space limitations on the UNDO tablespace.

* LOB updates and/or deletes are frequent and a higher PCT_VERSION is required to provide enough space in the LOB Segment to accommodate the LOB undo. RETENTION on LOBs that are updated or deleted frequently can run into problems holding UNDO long enough for queries.

* QUERY DURATION shown in the error message is 30+ years and therefore, no amount of undo will satisfy the consistent read blocks.

Note 750195.1 – ORA-1555 Shows Unrealistic Query Duration (billions of seconds)

* QUERY DURATION shown in the error message is 0. NOTE: This has been filed as a bug on many release levels and has been very difficult to narrow down to a specific problem.

Note 761128.1 – ORA-1555 Error when Query Duration as 0 Seconds

* QUERY DURATION is lower than TUNED_UNDRETENTION. Undo header information can sometimes get overwritten or you could be seeing a bug.

* TUNED_UNDORETENTION stays very high and UNDO tablepsace continues to grow continuously or getting space errors.

Note 1112431.1 – Undo Remains Unexpired When Using Non-autoextensible Datafiles for Undo Tablespace.

Additional Reference:

Database Administration Community

Tuesday May 10, 2011

Oracle Database Machine and Exadata Storage Server Information Center

Direct link to: Oracle Database Machine and Exadata Storage Server Information Center (Doc ID 1306791.1)

Purpose: The purpose of this bulletin is to have a consolidated site for Database Machine and Exadata Storage Server, to cover support, training and proactive information for customers. Scope and Application: This document is intended for Database Machine and Exadata Storage Server customers. It provides time critical information and highlights related to Database Machine and Exadata Storage Server support and services.

Wednesday Feb 23, 2011

Master Note For Database and Client Certification

For most current information refer:

Master" Note For Database and Client Certification [ID 1298096.1]

In this Document
  Purpose
  Scope and Application
  Master Note For Database and Client Certification
     Main Note
     General
     Using My Oracle Support Effectively


Applies to:

Information in this document applies to any platform.

Purpose

This Master Note is intended to provide an index and references to the most frequently used My Oracle Support notes with respect to Oracle Certify and Oracle Database Server/Client.

Scope and Application

This note is applicable to all levels of expertise.

Master Note For Database and Client Certification

Main Note

Note 1295603.1 Locate Database Server Certification Information on My Oracle Support

General

Note 763087.5 Tips for Finding Certifications in Classic Certify

Note 161818.1 Oracle Database (RDBMS) Releases Support Status Summary

Note 207303.1 Client / Server / Interoperability Support Between Different Oracle Versions

Note 77627.1 Oracle Database Server product support Matrix for Windows 2000

Note 1062972.1 Locate Oracle Database Server Certification Information for Microsoft Windows Platforms

Note 824935.1 Where To Find Oracle Patchset/Software for Specific Server/ Hardware Model?

Note 942852.1 Oracle VM and VMWare Certification for Oracle Products

Note 750215.1 Which OS File Systems Are Certified For Single Instance Oracle Databases?

Note 403202.1 Certification of Zeta File System (Zfs) On Solaris 10 for Oracle RDBMS

Note 1075717.1 Installing 32-bit RDBMS Client software on x86_64 Linux.

Note 870253.1 32-bit Client Install on 64-bit Windows Platform

Note 753601.1 SUPPORT FOR ORACLE DATABASE ON WPARS UNDER AIX 6.1

Note 1194734.1 Where do I find that on My Oracle Support (MOS) [Video]

Note 971464.1 FAQ - 11gR2 requires Solaris 10 update 6 or greater

 

Using My Oracle Support Effectively

Note 374370.1 New Customers Start Here

Note 868955.1 My Oracle Support Health Checks Catalog

Note 166650.1 Working Effectively With Global Customer Support

Note 199389.1 Escalating Service Requests with Oracle Support Services


 

Monday Jan 17, 2011

Master Note for Generic Data Warehousing

[Read More]
About

News and Troubleshooting tips for Oracle Database and Enterprise Manager

Search

Categories
Archives
« May 2015
SunMonTueWedThuFriSat
     
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
18
19
20
21
22
23
24
25
26
27
28
29
30
31
      
Today