이미 Oracle PartnerNetwork 멤버인 경우 파트너 혜택 표 액세스

OPN 혜택 및 리소스 Silver Gold Platinum Diamond 파트너 환영 키트 안전한 OPN 파트너 웹 사이트 액세스  자료실 컨텐츠의 제한적 이용 Cloud Services, 1-Click 및 Oracle Database Appliance 자료실 파트너 뉴스레터 Oracle Partner Business Center Global Diamond Desk 전화를 통한 파트너 관리 지원1   전담 오라클 파트너 비즈니스 컨설턴트     Oracle OpenWorld에서 파트너 포럼 및/또는 라운지에 참가하여 솔루션 소개2 세일즈 부문 부사장/경영진 후원자와의 미팅에 초대     파트너 자문 위원회 참가2     경영진 파트너 포럼 참가2 Partner Award 수상 자격1 Global Alliance Manager 지정       오라클 경영진 후원     지역별 글로벌 역량 강화 혜택 및 툴 Silver Gold Platinum Diamond 파트너 전용 온라인 세미나, 선별된 이벤트와 워크숍 참석2 Oracle University의 e러닝 컨텐츠 라이브러리 액세스 Competency Center에서 제공하는 지침 학습 과정(GLP)을 통한 파트너별 교육 이용1 Cloud Services, 1-Click 제품 및 Oracle Database Appliance Enablement 2.0 Boot Camp1 Cloud Services, 1-Click 제품 및 Oracle Database Appliance Oracle University 제품 및 서비스에 대한 할인1 20% 25% 25% 25% OPN 멤버쉽 가입 또는 갱신 후 처음 30일 이내에 구입하는 Oracle University 학습 크레딧에 대한 할인 35% 35% 35% 35% OPN 멤버쉽 가입 또는 갱신 후 처음 30일 이내에 구입하는 SSCD(Self-Study CD)에 대한 할인 35% 35% 35% 35% 라이브 가상 강의(LVC)에 대한 할인1 20% 25% 30% 30% 시험 바우처에 대한 할인 20% 25% 25% 25% 무료 평가/시험 바우처1   2 6 6 -100(Worldwide 파트너) 개발 혜택 및 툴 Silver Gold Platinum Diamond 테크놀로지 프로그램에 대한 개발 라이센스5 1-Click 제품 및 Oracle Database Appliance OPN 정책 에 나와 았음 OPN 정책 에 나와 았음 OPN 정책 에 나와 았음 Oracle Validated Integration   수수료 방식 할인 할인 SOA 기반의 Oracle Validated Integration1   수수료 방식 1개 포함 1개 포함 오라클 제품으로의 마이그레이션을 지원하기 위한 리소스(툴 키트, 워크벤치 및 타사 마이그레이션 제공업체)1   사전에 베타 프로그램 신청 가능   마케팅 혜택 및 툴 Silver Gold Platinum Diamond Oracle.com/events에 파트너 이벤트 게시 가능   전문화된 기술력과 솔루션을 갖춘 경우 오라클 파트너 브랜드 및 로고 사용1 Oracle.com에 소개1     Oracle Cloud Marketplace에 게시 신청4 우선 홍보 기회 우선 홍보 기회 마케팅 키트1 Cloud Services, 1-Click 제품 및 Oracle Database Appliance 오라클 출판물 광고비 할인(인쇄 및 디지털) 25% 35% 40% 50% 오라클 관련 정보를 심층적으로 다룬 뉴스레터 후원에 대한 할인 혜택 25% 35% 40% 50% 마케팅 캠페인을 위한 연락처 목록 액세스1     MDF(Marketing Development Funds) 신청1     전담 글로벌 파트너 마케팅 관리자       공동 고객 성공 사례에 대한 전문적인 개발1   Oracle Magazine의 파트너 뉴스 섹션에서 홍보1     홍보(PR) 지원 및 가이드라인1 공동 보도 자료 공동 보도 자료 Oracle Cloud Marketplace 또는 AppCloud Marketplace에 승인된 통합에 대한 보도 자료 게시4 Google 애드워즈 캠페인의 오라클 상표 JavaONE 및 Oracle OpenWorld에서 솔루션 소개1 오라클 고객을 직접 만나는 자리에서 연설1     오라클 내부용 활동에서 연설할 수 있는 기회4     판매 혜택 및 툴 Silver Gold Platinum Diamond 각 자료실에 나와 있는 멤버쉽 레벨 및 리셀러 자격 조건 달성에 따라 공인된 오라클 제품 및 서비스 판매1 1-Click 제품 및 Oracle Database Appliance 오라클 프로그램 및 서비스 판매를 위한 OPN 멤버 할인 가격1 1-Click 제품 및 Oracle Database Appliance 세일즈 키트1 Cloud Services, 1-Click 제품 및 Oracle Database Appliance OMM 정책에 따라 결정되는 Oracle Open Market Model(OMM) Resale Initiative를 통해 순 신규 영업 기회 등록1 OMM 정책에 따라 결정되는 OMM Referral Initiative를 통해 오라클 비즈니스를 추천하는 경우 보상1 Oracle OMM Non-commission Co-Sell Initiative를 통해 오라클 영업 기회를 등록하는 경우 인지도 강화1 고객에게 Oracle Financing 제공1 테크놀로지 및 애플리케이션 프로그램을 위한 데모 라이센스5 1-Click 제품 및 Oracle Database Appliance OPN 정책 에 나와 았음 OPN 정책 에 나와 았음 OPN 정책 에 나와 았음 Oracle PartnerNetwork Solutions Catalog를 통해 가시성 확보1 우선 배치 및 홍보 우선 배치 및 홍보 Oracle PartnerNetwork Solutions Catalog를 통해 영업 기회 창출1 내부용으로 사용할 오라클 프로그램 라이센스 구입 시 할인1   내부용으로 사용할 CRM On-Demand 프로그램 라이센스 구입 시 할인1   비즈니스 실무 및 가격 정보 교육1 국제적인 부패 방지 교육1 지원 혜택 및 툴 Silver Gold Platinum Diamond Oracle Solaris, Solaris Cluster 및 Solaris Studio 업데이트 및 패치 이용5   OPN SI(Support IdentifierI)를 통해 "My Oracle Support" 이용5 1-Click 제품 및 Oracle Database Appliance 소프트웨어 업그레이드 및 패치 (테크놀로지 및 애플리케이션 제품만 해당) - 현 오라클 지원 제품 및 릴리스5 1-Click 제품 및 Oracle Database Appliance Partner Business Center의 지원 서비스 1-Click 제품 및 Oracle Database Appliance 특별 파트너 할인 가격으로 SR(Service Request) 패키지 구입1 (테크놀로지 및 애플리케이션 제품만 해당)   개발, 데모 및 통합 라이센스와 함께 사용할 무료 SR(Service Request)1     Enterprise Linux Basic Support 서비스 및 Oracle VM Premier Support 서비스를 통해 무료 SR을 사용하여 파트너의 Linux 및 Oracle VM 개발 시스템 지원1     Linux Basic Support 서비스 및 Oracle VM Premier Support 서비스를 위한 패치/업데이트를 다운로드하여 OPN 멤버의 Linux 및 Oracle VM 개발 시스템 지원   파트너의 Linux 및 Oracle VM 개발 시스템을 위한 Linux 및 Oracle VM 지원 서비스 가격 할인1 OCVS(Oracle Collaborative Vendor Support) 프로그램 이용1   파트너 내부용으로 사용할 ACS(Advanced Customer Services)에 대한 할인1 Linux 및 VM 전용 ACS(Advanced Customer Services) 파트너 팀에 대한 개별적 액세스1     ACS의 혜택에 대한 보완적 컨설팅1     ACS(Advanced Customer Services) 내부 웹 페이지에 대한 OPN 멤버 노출1     공동 캠페인을 위한 ACS(Advanced Customer Services)의 공동 마케팅 및 영업 기회 창출 지원1     유효한 ASFU/ESL 협약을 체결한 OPN 멤버를 위한 기술 지원 SR(Service Request) 및 확장된 지원 패키지8   전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready 및 Oracle Exastack Optimized와 관련된 혜택 및 툴 Silver Gold Platinum Diamond 새로운 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready 및 Oracle Exastack Optimized 알림 및 오리엔테이션 통지1   전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 안전한 OPN 전문화 리소스 센터 이용   전문화 프로그램 전문화 프로그램 전문화 프로그램 Oracle Exastack Optimized 로고   Oracle Exastack Optimized Oracle Exastack Optimized Oracle Exastack Optimized OPN 전문화(Specialized) 로고1   전문화 프로그램 전문화 프로그램 전문화 프로그램 Oracle Exastack Ready 로고   Oracle Exastack Ready Oracle Exastack Ready Oracle Exastack Ready Oracle Validated Integration 로고   Oracle Validated Integration Oracle Validated Integration Oracle Validated Integration OPN 고급 전문화 프로그램 로고   고급 전문화 프로그램 고급 전문화 프로그램 고급 전문화 프로그램 뉴스레터, 웹 사이트, 광고 등으로 홍보1   전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized OPN Solutions Catalog에 우선 배치   전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 오라클의 내부 파트너 찾기 시스템에 우선 배치1   전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 내부 뉴스레터에 발표1   전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 무료 시험 바우처1   전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 보도 자료에 오라클 경영진의 인용구 사용1   전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 오라클 회의실 시설 이용1   전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 데모 서비스 이용1, 4   전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized  / 우선 이용 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized  / 우선 이용 무료 지원 SR(Service Request) (테크놀로지 및 애플리케이션 제품만 해당)1, 3   전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized Enterprise Linux Basic Support 서비스 및 Oracle VM Premier Support 서비스를 통해 무료 지원 SR(Service Request)로 파트너의 Linux 및 Oracle VM 개발 시스템 지원1, 3   전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 제품 릴리스 준비 자료1   전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 구현 방법 이용1   전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized 전문화 프로그램, Oracle Validated Integration, Oracle Exastack Ready, Oracle Exastack Optimized

reference : http://www.oracle.com/partners/campaign/specialized-benefits-036151-ko.html

• V$Option의 내용 

  PARAMETER	VALUE
  Partitioning	TRUE
  Objects	TRUE
  Real Application Clusters	FALSE
  Advanced replication	TRUE
  Bit-mapped indexes	TRUE
  Connection multiplexing	TRUE
  Connection pooling	TRUE
  Database queuing	TRUE
  Incremental backup and recovery	TRUE
  Instead-of triggers	TRUE
  Parallel backup and recovery	TRUE
  Parallel execution	TRUE
  Parallel load	TRUE
  Point-in-time tablespace recovery	TRUE
  Fine-grained access control	TRUE
  Proxy authentication/authorization	TRUE
  Change Data Capture	TRUE
  Plan Stability	TRUE
  Online Index Build	TRUE
  Coalesce Index	TRUE
  Managed Standby	TRUE
  Materialized view rewrite	TRUE
  Database resource manager	TRUE
  Spatial	TRUE
  Automatic Storage Management	FALSE
  Export transportable tablespaces	TRUE
  Transparent Application Failover	TRUE
  Fast-Start Fault Recovery	TRUE
  Sample Scan	TRUE
  Duplexed backups	TRUE
  Java	TRUE
  OLAP Window Functions	TRUE
  Block Media Recovery	TRUE
  Fine-grained Auditing	TRUE
  Application Role	TRUE
  Enterprise User Security	TRUE
  Oracle Data Guard	TRUE
  Oracle Label Security	FALSE
  OLAP	TRUE
  Basic Compression	TRUE
  Join index	TRUE
  Trial Recovery	TRUE
  Data Mining	TRUE
  Online Redefinition	TRUE
  Streams Capture	TRUE
  File Mapping	TRUE
  Block Change Tracking	TRUE
  Flashback Table	TRUE
  Flashback Database	TRUE
  Transparent Data Encryption	TRUE
  Backup Encryption	TRUE
  Unused Block Compression	TRUE
  Oracle Database Vault	FALSE
  Result Cache	TRUE
  SQL Plan Management	TRUE
  SecureFiles Encryption	TRUE
  Real Application Testing	TRUE
  Flashback Data Archive	TRUE
  DICOM	TRUE
  Active Data Guard	TRUE
  Server Flash Cache	TRUE
  Advanced Compression	TRUE
  XStream	TRUE
  Deferred Segment Creation	TRUE

TRIM

Syntax

Description of the illustration trim.gif

Purpose

TRIM enables you to trim leading or trailing characters (or both) from a character string. If trim_character or trim_source is a character literal, then you must enclose it in single quotation marks.

• If you specify LEADING, then Oracle Database removes any leading characters equal to trim_character.

• If you specify TRAILING, then Oracle removes any trailing characters equal to trim_character.

• If you specify BOTH or none of the three, then Oracle removes leading and trailing characters equal to trim_character.

• If you do not specify trim_character, then the default value is a blank space.

• If you specify only trim_source, then Oracle removes leading and trailing blank spaces.

• The function returns a value with datatype VARCHAR2. The maximum length of the value is the length of trim_source.

• If either trim_source or trim_character is null, then the TRIM function returns null.

Both trim_character and trim_source can be VARCHAR2 or any datatype that can be implicitly converted to VARCHAR2. The string returned is of VARCHAR2 datatype if trim_source is a character datatype and a LOB if trim_source is a LOB datatype. The return string is in the same character set as trim_source.

Examples

This example trims leading zeros from the hire date of the employees in the hr schema:

SELECT employee_id,
      TO_CHAR(TRIM(LEADING 0 FROM hire_date))
      FROM employees
      WHERE department_id = 60
      ORDER BY employee_id;

EMPLOYEE_ID TO_CHAR(T
----------- ---------
        103 3-JAN-90
        104 21-MAY-91
        105 25-JUN-97
        106 5-FEB-98
        107 7-FEB-99

LTRIM

Syntax

Description of the illustration ltrim.gif

Purpose

LTRIM removes from the left end of char all of the characters contained in set. If you do not specify set, then it defaults to a single blank. If char is a character literal, then you must enclose it in single quotation marks. Oracle Database begins scanning char from its first character and removes all characters that appear in set until reaching a character not in set and then returns the result.

Both char and set can be any of the datatypes CHAR, VARCHAR2, NCHAR, NVARCHAR2, CLOB, or NCLOB. The string returned is of VARCHAR2 datatype if char is a character datatype, NVARCHAR2 if char is a national character datatype, and a LOB if char is a LOB datatype.

The following example trims the redundant first word from a group of product names in the oe.products table:

SELECT product_name, LTRIM(product_name, 'Monitor ') "Short Name"
   FROM products
   WHERE product_name LIKE 'Monitor%';

PRODUCT_NAME         Short Name
-------------------- ---------------
Monitor 17/HR        17/HR
Monitor 17/HR/F      17/HR/F
Monitor 17/SD        17/SD
Monitor 19/SD        19/SD
Monitor 19/SD/M      19/SD/M
Monitor 21/D         21/D
Monitor 21/HR        21/HR
Monitor 21/HR/M      21/HR/M
Monitor 21/SD        21/SD
Monitor Hinge - HD   Hinge - HD
Monitor Hinge - STD  Hinge - STD

RTRIM

Syntax

Description of the illustration rtrim.gif

Purpose

RTRIM removes from the right end of char all of the characters that appear in set. This function is useful for formatting the output of a query.

If you do not specify set, then it defaults to a single blank. If char is a character literal, then you must enclose it in single quotation marks. RTRIM works similarly to LTRIM.

Both char and set can be any of the datatypes CHAR, VARCHAR2, NCHAR, NVARCHAR2, CLOB, or NCLOB. The string returned is of VARCHAR2 datatype if char is a character datatype, NVARCHAR2 if expr1 is a national character datatype, and a LOB if char is a LOB datatype.

The following example trims all the right-most occurrences of period, slash, and equal sign from a string:

SELECT RTRIM('BROWNING: ./=./=./=./=./=.=','/=.') "RTRIM example" FROM DUAL;
 
RTRIM exam
----------
BROWNING:

reference : Oracle® Database SQL Language Reference - Oracle11gR1

그동안 너무 RTRM과 LTRIM만 사용한듯.... 

Oracle DBMS의 Version별 OS Platform Certification 정보입니다.

Oracle 12c는 Windows 2003이 아예 빠져 버렸네요. 아무래도 Windows 2003의 지원 정책 때문인 것으로 사료됩니다.

12.1

• OS versions and minimum levels:
  • Windows 2008
  • Windows 2008 R2
  • Windows 2012 (single instance only)
    • Also certified as a guest under Window 2012 under Hyper-V (single instance only) -  see Supported Virtualization and Partitioning Technologies for Oracle Database and RAC Product Releases
  • Windows 7
  • Windows 8
• Client certifications:
  • Oracle provides both a 64-bit and 32-bit Windows client with Oracle Database 12.1 for Windows x64 releases 
  • 32-bit client is certified with all certified 64-bit versions of Windows
  • 32-bit client is also certified on Windows x86 (32-bit) 7, 8, and 2008
• For complete details of OS versions supported, minimum levels, and other installation requirements see Oracle Database Installation Guide 12c Release 1 (12.1) for Windows.

11.2

• OS versions and minimum levels:
  • Windows XP
  • Windows 7
  • Windows Vista
  • Windows 2003
  • Windows 2003 R2
  • Windows 2008
  • Windows 2008 R2
• See Oracle Database Installation Guide 11g Release 2 (11.2) for Microsoft Windows for the Minimum Operating System Requirements.
  • All 11.2 Windows Installation Guides
• RAC:
  • 11.2 RAC is certified on Windows 64, is NOT certified to run on Windows 32
  • RAC Technologies Compatibility Matrix (RTCM) for Windows x86-64
  • Microsoft Windows is ONLY certified on Oracle Clusterware

11.1

• OS versions and minimum levels
  • Windows XP
  • Windows Vista
  • Windows 2003
  • Windows 2003 R2
  • Windows 2008 (11.1.0.7 or higher required) -- use the 11.1.0.7 database install created specifically for Windows 2008
• See Oracle Database Installation Guide 11g Release 1 (11.1) for Microsoft Windows for the Minimum Operating System Requirements.
  • All 11.1 Windows Installation Guides
• RAC:
  • RAC Technologies Compatibility Matrix (RTCM) for Windows x86-64
  • Microsoft Windows is ONLY certified on Oracle Clusterware.

10.2

• OS versions and minimum levels
  • Windows XP
  • Windows 7 (see note below)
  • Windows Vista (see note below)
  • Windows 2003
  • Windows 2003 R2 (<10.2.0.2 or higher)
    • iSQL*Plus version 10.2.0.3.0 and higher is certified 2003 and 2003 R2.
  • Windows 2008 (See note below)
  • Windows 2008 R2 (see note below)
• See Database Installation Guide for Microsoft Windows (64-bit) for the Minimum Operating System Requirements.
  • All 10.2 Installation Guides
• RAC:
  • 10.2 RAC is NOT certified on XP or Vista
  • RAC Technologies Compatibility Matrix (RTCM) for Windows x86-64
  • Microsoft Windows is ONLY certified on Oracle Clusterware
• Windows Vista, 7, Server 2008, and Server 2008 R2: 

• Do not install Oracle Database 10g Release 2 on Windows Server 2008, Server 2008 R2, 7, nor Vista using the 10.2.0.1 version. You must use the 10.2.0.4 (64-bit) x64 version specifically created for these operating systems. After installation, for Windows 7 and Windows Server 2008 R2, patchset 10.2.0.5 or higher must be applied.  For more information on installation see the release notes sections on the installation media:
  
  • 32-bit
  • 64 bit

출처 : Oracle Support - 문서 ID 1307195.1 발췌

Current Interoperability Support Situation

The matrix below summarizes client and server combinations that are supported for the most commonly used product versions. A full matrix appears at the end of this document.

New interoperability problems will only be investigated if BOTH releases involved are covered by a valid support contract at the time that the issue is reported .
eg:

A 11.1.0 client to an 11.2.0 server issue requires the customer to have a valid Extended Support contract for the 11.1.0 client in order for Oracle to investigate it.

Client Version	Server Version
	12.1.0	11.2.0	11.1.0	10.2.0	10.1.0	9.2.0
12.1.0	Yes	Yes	ES	ES #7	No #3	No #3
11.2.0	Yes	Yes	ES	ES #7	No	Was #5
11.1.0	ES	ES	ES	ES #7	Was #6	Was #5
10.2.0	ES #7	ES #7	ES #7	Was	Was	Was #5
10.1.0(#4)	No	Was #6	Was #6	Was	Was	Was
9.2.0	No#8	Was #5	Was #5	Was #5	Was	Was

Key:

Yes	Supported
LES	Limited extended support previously applied to 9.2 releases but has now ended.
ES	Supported but fixes only possible for customers with Extended Support .
Was	Was a supported combination but one of the releases is no longer covered by any of Premier Support , Primary Error Correct support , Extended Support nor Extended Maintenance Support so fixes are no longer possible.
No	Has never been Supported

Specific Notes:

• #1 - See Note:207319.1
• #2 - An ORA-3134 error is incorrectly reported if a 10g client tries to connect to an 8.1.7.3 or lower server. See Note:3437884.8 .
• #3 - An ORA-3134 error is correctly reported when attempting to connect to this version.
• #4 - There are problems connecting from a 10g client to 8i/9i where one is EBCDIC based. See Note:3564573.8
• #5 - For connections between 10.2 (or higher) and 9.2 the 9.2 end MUST be at 9.2.0.4 or higher. Connections between 10.2 (or higher) and 9.2.0.1, 9.2.0.2 or 9.2.0.3 have never been supported.
• #6 - For connections between 11.1 (or higher) database server and 10.1 / 10.2 database server across a database link the 10g end MUST be at 10.1.0.5 / 10.2.0.2 (or higher) respectively in order to use PLSQL between those versions. (This does not apply to normal 11g clients to 10g database server only server to server and a few very specific client products, such as Oracle Forms). See Note:4511371.8 for more details.
• #7 - For database link connections between 11.1 (or higher) and 10.2 the 10g end MUST be at 10.2.0.2 (or higher) in order to use PLSQL between those versions. See Note:4511371.8 for more details.
• #8 - Attempting to connect from 9.2 to 12.1 will fail with an "ORA-28040: No matching authentication protocol" error.

General Notes:

1. For database links between different Oracle versions connections must be supported in BOTH directions in the matrix above.
   eg: As 11.2 -> 10.1 is not supported then database links between these version are not supported in either direction.
   
2. Unsupported combinations may appear to work but can encounter errors for particular operations. The fact that they appear to work should not be relied upon - issues on unsupported combinations will not be investigated.
3. Since new database servers are compatible with a limited set of older OCI clients, it may not be necessary to upgrade the client software when upgrading the database. However, some new features may not work without upgrading the client software. For example, an Oracle 10.2 client is able to connect to an 11.2 database, but is not able to take advantage of newer features such as Client Result Cache (introduced in 11.1).
4. Oracle Applications , or other Oracle products, may have supported configurations not listed in the matrix above.
5. The matrix above also applies between different platforms and between 32/64 bit releases of Oracle client / server except where any Oracle platform desupport notice indicates otherwise .
6. Unix BEQUEATH (BEQ) connections are NOT supported between different releases. eg: Client 10.2 is not supported to make an Oracle Net connection to a 11.2 server using the BEQ protocol adapter regardless of the interoperability support listed above. See Note:364252.1 for more details.

Oracle Client Version별로 Oracle DB Server Version에 Support하는데 있어서 상호 호환성 여부를 정리한 자료입니다.

출처 : Oracle Support

Oracle Database 12c : Tom’s Top 12 Things About the Latest Generation of Database Technology

By James Koopmann

SQL> SELECT TO_CHAR(date1,'MM/DD/YYYY HH24:MI:SS') "Date" FROM date_table;
Date
---------------------------
06/20/2003 16:55:14
06/26/2003 11:16:36

  1         SELECT TO_CHAR(date1,'MMDDYYYY:HH24:MI:SS') date1,
  2         TO_CHAR(date2,'MMDDYYYY:HH24:MI:SS') date2,
  3         trunc(86400*(date2-date1))-
  4         60*(trunc((86400*(date2-date1))/60)) seconds,
  5         trunc((86400*(date2-date1))/60)-
  6         60*(trunc(((86400*(date2-date1))/60)/60)) minutes,
  7         trunc(((86400*(date2-date1))/60)/60)-
  8         24*(trunc((((86400*(date2-date1))/60)/60)/24)) hours,
  9         trunc((((86400*(date2-date1))/60)/60)/24) days,
 10         trunc(((((86400*(date2-date1))/60)/60)/24)/7) weeks
 11*        FROM date_table
DATE1             DATE2                SECONDS    MINUTES      HOURS       DAYS      WEEKS
----------------- ----------------- ---------- ---------- ---------- ---------- ----------
06202003:16:55:14 07082003:11:22:57         43         27         18         17          2
06262003:11:16:36 07082003:11:22:57         21          6          0         12          1

SQL> SELECT CAST(date1 AS TIMESTAMP) "Date" FROM t;
Date
-----------------------------------------------------
20-JUN-03 04.55.14.000000 PM
26-JUN-03 11.16.36.000000 AM

  1  SELECT TO_CHAR(time1,'MM/DD/YYYY HH24:MI:SS') "Date" FROM date_table
Date
-------------------
06/20/2003 16:55:14
06/26/2003 11:16:36

 1  SELECT TO_CHAR(time1,'MM/DD/YYYY HH24:MI:SS:FF3') "Date" FROM date_table
Date
-----------------------
06/20/2003 16:55:14:000
06/26/2003 11:16:36:000

1  SELECT time1,  time2,  (time2-time1)
  2*   FROM date_table
TIME1                          TIME2                          (TIME2-TIME1)
------------------------------ ----------------------------   ----------------------
06/20/2003:16:55:14:000000     07/08/2003:11:22:57:000000     +000000017 18:27:43.000000
06/26/2003:11:16:36:000000     07/08/2003:11:22:57:000000     +000000012 00:06:21.000000

  1  SELECT time1,
  2         time2,
  3         substr((time2-time1),instr((time2-time1),' ')+7,2)                 seconds,
  4         substr((time2-time1),instr((time2-time1),' ')+4,2)                 minutes,
  5         substr((time2-time1),instr((time2-time1),' ')+1,2)                 hours,
  6         trunc(to_number(substr((time2-time1),1,instr(time2-time1,' '))))   days,
  7         trunc(to_number(substr((time2-time1),1,instr(time2-time1,' ')))/7) weeks
  8*   FROM date_table
TIME1                       TIME2                      SECONDS MINUTES HOURS DAYS WEEKS
-------------------------   -------------------------- ------- ------- ----- ---- -----
06/20/2003:16:55:14:000000  07/08/2003:11:22:57:000000  43     27      18    17    2
06/26/2003:11:16:36:000000  07/08/2003:11:22:57:000000  21     06      00    12    1

SQL> ALTER SYSTEM SET fixed_date = '2003-01-01-10:00:00';
System altered.

SQL> select sysdate from dual;
SYSDATE
---------
01-JAN-03

SQL> select systimestamp from dual;
SYSTIMESTAMP
---------------------------------------------------------
09-JUL-03 11.05.02.519000 AM -06:00

Michael -- Thanks for the question regarding "Timestamp vs. Date - is Date still appropriate for new systems?", version 10.2 Submitted on 26-Nov-2006 2:49 UTC Tom's latest followup | Bookmark | Bottom Last updated 18-Feb-2010 9:54 You Asked The new Timestamp datatypes are described as extensions of the Date datatype in Oracle's documentation. They are clearly more powerful and include capabilities such as tracking times down to milliseconds, incorporating time zones, etc. It's also generally accepted that you should minimize the complexity of a system where possible, and that one way of doing this is not to use redundant entities (in the general sense, not the ER diagram sense). Given these points, is there any reason to still use Dates in new system development? Are there issues with performance, compatibility, etc? Or is this like the switch from LONG and LONG RAW to LOBs where all new development should use the LOB? Oracle's decision not to extend Date to also include Date With Timezone and Date With Local Timezone suggests that Oracle doesn't see the point in extending Date... presumably because it will be deprecated and replaced with Timestamp. ----------------------- BTW, on a closely related topic, I don't understand the logic behind making Timestamp With Time Zone and Timestamp With Local Time Zone datatypes. Seems to be that a database (or any other system) should store all Date / Times in a canonical form - presumably seconds since an agreed on starting second. Then all of this Time Zone stuff is just a matter of Locale and client settings - my client should specify its Timezone to the Server and then all dates / times should be converted to the canonical form using that timezone unless I specify another time zone together with the date / time. The With Local Timezone and With Timezone datatypes seem to describe how to present the information to clients more than what the datatype is. and we said... I think dates will be here for a long time to come. Timestamp is an ANSI thing, for compliance. The choice is yours. And you cannot really store things in a canonical format - there are too many variations. Dates are 7 bytes always Timestamps are also 7 (no fractional seconds) or 11 (fractional seconds) or 13 (fractional seconds with timezone) Probably - just using timestamp would be good going forward (there might be tools that cannot "deal" correctly with a timestamp yet - they would cause it to convert to a date - you'll use to_timestamp and such with them). But in reality, date is just coming out of my fingers still :) I typically have no need for the fractional seconds nor timezone. Reviews      What about variations?   November 26, 2006 - 10am UTC Bookmark | Bottom | Top Reviewer: Mike Friedman from Shenzhen, China Mind explaining this a bit more? "And you cannot really store things in a canonical format - there are too many variations." Does this mean that Oracle doesn't store dates internally as seconds since a reference date / time? I know Windows does... and they have to deal with as many variations as Oracle, don't they? Followup   November 26, 2006 - 11am UTC: The date datatype does, but not a "seconds since something". (windows cannot do a wide range of dates? hmmm, you might not be entirely accurate on that seconds thing, I'll bet windows uses more than one format to store dates, or they cannot store dates that fall outside a very very very small range!) <quote src=Expert Oracle Database Architecture> DATE Type The DATE type is a fixed-width 7-byte date/time datatype. It will always contain the seven attributes of the century, the year within the century, the month, the day of the month, the hour, the minute, and the second. Oracle uses an internal format to represent that information, so it is not really storing 20, 05, 06, 25, 12, 01, 00 for June 25, 2005, at 12:01:00. Using the built-in DUMP function, we can see what Oracle really stores: ops$tkyte@ORA10G> create table t ( x date ); Table created. ops$tkyte@ORA10G> insert into t (x) values 2 ( to_date( '25-jun-2005 12:01:00', 3 'dd-mon-yyyy hh24:mi:ss' ) ); 1 row created. ops$tkyte@ORA10G> select x, dump(x,10) d from t; X D --------- ----------------------------------- 25-JUN-05 Typ=12 Len=7: 120,105,6,25,13,2,1 The century and year bytes (the 120,105 in the DUMP output) are stored in an excess-100 notation. You would have to subtract 100 from them to determine the correct century and year. The reason for the excess-100 notation is support of BC and AD dates. If you subtract 100 from the century byte and get a negative number, it is a BC date, for example: ops$tkyte@ORA10G> insert into t (x) values 2 ( to_date( '01-jan-4712bc', 3 'dd-mon-yyyybc hh24:mi:ss' ) ); 1 row created. ops$tkyte@ORA10G> select x, dump(x,10) d from t; X D --------- ----------------------------------- 25-JUN-05 Typ=12 Len=7: 120,105,6,25,13,2,1 01-JAN-12 Typ=12 Len=7: 53,88,1,1,1,1,1 So, when we insert 01-JAN-4712BC, the century byte is 53 and 53 – 100 = –47, the century we inserted. Because it is negative, we know that it is a BC date. This storage format also allows the dates to be naturally sortable in a binary sense. Since 4712 BC is “less than” 4710 BC, we’d like a binary representation that supports that. By dumping those two dates, we can see that 01-JAN-4710BC is “larger” than the same day in 4712 BC, so they will sort and compare nicely: ops$tkyte@ORA10G> insert into t (x) values 2 ( to_date( '01-jan-4710bc', 3 'dd-mon-yyyybc hh24:mi:ss' ) ); 1 row created. ops$tkyte@ORA10G> select x, dump(x,10) d from t; X D --------- ----------------------------------- 25-JUN-05 Typ=12 Len=7: 120,105,6,25,13,2,1 01-JAN-12 Typ=12 Len=7: 53,88,1,1,1,1,1 01-JAN-10 Typ=12 Len=7: 53,90,1,1,1,1,1 The month and day bytes, the next two fields, are stored naturally, without any modification. So, June 25 used a month byte of 6 and a day byte of 25. The hour, minute, and second fields are stored in excess-1 notation, meaning we must subtract 1 from each component to see what time it really was. Hence midnight is represented as 1,1,1 in the date field. This 7-byte format is naturally sortable, as you have seen—it is a 7 byte field that can be sorted in a binary fashion from small to larger (or vice versa) very efficiently. Additionally, its structure allows for easy truncation, without converting the date into some other format. For example, truncating the date we just stored, 25-JUN-2005 12:01:00, to the day (remove the hours, minutes, seconds) is very straightforward. Just set the trailing three bytes to 1,1,1 and the time component is as good as erased. </quote> Timestamps get more complicated - there are timestamps without timezones, with local timezones - you cannot store those in "one fashion" - one preserves the original timezone for example (so you cannot put it into UTC, you need to remember what timezone it used to be) and the other puts it into the database timezone.  Thanks   November 26, 2006 - 12pm UTC Bookmark | Bottom | Top Reviewer: Michael Friedman from Shenzhen, China  to_timestamp   September 10, 2008 - 8pm UTC Bookmark | Bottom | Top Reviewer: Paras Bansal from Milpitas, CA Can you explain this - SELECT cast(to_timestamp('01-may-2005 23:59:59.501','dd-mon-yyyy hh24:mi:ss:ff') AS DATE) FROM dual; It returns me 2nd may as DATE. Can we do something so that it truncs the millisec portion and we get only 1st May. regards, Paras Bansal Followup   September 16, 2008 - 11am UTC: substr the string you are trying to convert and just use to_date.  ops$tkyte%ORA10GR2> SELECT to_date(substr( '01-may-2005 23:59:59.501', 1, 20),'dd-mon-yyyy hh24:mi:ss') from dual; TO_DATE(SUBSTR('01-M -------------------- 01-may-2005 23:59:59  curious TO_TIMESTAMPing around   September 16, 2008 - 2pm UTC Bookmark | Bottom | Top Reviewer: Duke Ganote from Amelia, Ohio USA SQL*Plus: Release 10.2.0.1.0 - Production on Tue Sep 16 13:35:17 2008 Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production With the OLAP and Data Mining Scoring Engine options [glogin.sql includes: alter session set nls_date_format='yyyy-mm-dd HH24:MI:SS'; alter session set nls_timestamp_format = 'yyyy-mm-dd HH24:MI:SS.FF'; ] select cast(ts1 as date) dt1 , ts1 , cast(ts2 as date) dt2 , ts2 from ( select to_timestamp('01-may-2005 23:59:59.501' ,'dd-mon-yyyy hh24:mi:ss:ff') ts1 , systimestamp ts2 from dual ) / DT1 TS1 DT2 TS2 -------------------------------------------------- 2005-05-02 00:00:00 2005-05-01 23:59:59.501000000 2008-09-16 13:33:39 16-SEP-08 01.33.38.512485 PM -04:00 Followup   September 16, 2008 - 11pm UTC: do you have access to support to file a bug?   where is the bug ?   September 17, 2008 - 4am UTC Bookmark | Bottom | Top Reviewer: Sokrates  sorry, I don't see it. Can you please explain ? What was expected output ? Followup   September 17, 2008 - 9am UTC: when you cast a to_timestamp value as a date - the time component disappeared.  when you cast a timestamp value as a date - the time component did NOT disappear.   Isn't it just rounding   February 16, 2010 - 8pm UTC Bookmark | Bottom | Top Reviewer: Warwick from Sydney, Australia Hi Tom,  Isn't this due to rounding? I tried this using both 9i and 11r1  alter session set nls_date_format='yyyy-mm-dd HH24:MI:SS'; alter session set nls_timestamp_format = 'yyyy-mm-dd HH24:MI:SS.FF'; Running the original query returned the results above. Changing it to  select cast(ts1 as date) dt1 , ts1 , cast(ts2 as date) dt2 , ts2 from ( select to_timestamp('01-may-2005 23:59:58.501' ,'dd-mon-yyyy hh24:mi:ss:ff') ts1 , systimestamp ts2 from dual ) / DT1 TS1 DT2 TS2 --------------------- 2005-05-01 23:59:59 2005-05-01 23:59:58.501000000 2010-02-17 12:49:57 17-FEB-10 12.49.56.986028 PM +11:00 Cheers  Warwick  Followup   February 17, 2010 - 8am UTC: 9i and 10g (and 11gr1) all lose the time component:  ops$tkyte%ORA9IR2> select * from v$version; BANNER ---------------------------------------------------------------- Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production PL/SQL Release 9.2.0.8.0 - Production CORE 9.2.0.8.0 Production TNS for Linux: Version 9.2.0.8.0 - Production NLSRTL Version 9.2.0.8.0 - Production ops$tkyte%ORA9IR2> alter session set nls_date_format='yyyy-mm-dd HH24:MI:SS'; Session altered. ops$tkyte%ORA9IR2> alter session set nls_timestamp_format = 'yyyy-mm-dd HH24:MI:SS.FF'; Session altered. ops$tkyte%ORA9IR2> ops$tkyte%ORA9IR2> select cast(ts1 as date) dt1 2 , ts1 3 , cast(ts2 as date) dt2 4 , ts2 5 from 6 ( 7 select to_timestamp('01-may-2005 23:59:59.501' 8 ,'dd-mon-yyyy hh24:mi:ss:ff') ts1 9 , systimestamp ts2 10 from dual 11 ) 12 / DT1 ------------------- TS1 --------------------------------------------------------------------------- DT2 ------------------- TS2 --------------------------------------------------------------------------- 2005-05-02 00:00:00 2005-05-01 23:59:59.501000000 2010-02-17 09:54:28 17-FEB-10 09.54.27.579168 AM -05:00 10g:  ops$tkyte%ORA10GR2> select * from v$version; BANNER ---------------------------------------------------------------- Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Prod PL/SQL Release 10.2.0.4.0 - Production CORE 10.2.0.4.0 Production TNS for Linux: Version 10.2.0.4.0 - Production NLSRTL Version 10.2.0.4.0 - Production ops$tkyte%ORA10GR2> select cast(ts1 as date) dt1 2 , ts1 3 , cast(ts2 as date) dt2 4 , ts2 5 from 6 ( 7 select to_timestamp('01-may-2005 23:59:59.501' 8 ,'dd-mon-yyyy hh24:mi:ss:ff') ts1 9 , systimestamp ts2 10 from dual 11 ) 12 / DT1 ------------------- TS1 --------------------------------------------------------------------------- DT2 ------------------- TS2 --------------------------------------------------------------------------- 2005-05-02 00:00:00 2005-05-01 23:59:59.501000000 2010-02-17 09:55:29 17-FEB-10 09.55.28.592716 AM -05:00 and 11gR1:  ops$tkyte%ORA11GR1> select * from v$version; BANNER ------------------------------------------------------------------------------- Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production PL/SQL Release 11.1.0.7.0 - Production CORE 11.1.0.7.0 Production TNS for Linux: Version 11.1.0.7.0 - Production NLSRTL Version 11.1.0.7.0 - Production ops$tkyte%ORA11GR1> alter session set nls_date_format='yyyy-mm-dd HH24:MI:SS'; Session altered. ops$tkyte%ORA11GR1> alter session set nls_timestamp_format = 'yyyy-mm-dd HH24:MI:SS.FF'; Session altered. ops$tkyte%ORA11GR1> ops$tkyte%ORA11GR1> select cast(ts1 as date) dt1 2 , ts1 3 , cast(ts2 as date) dt2 4 , ts2 5 from 6 ( 7 select to_timestamp('01-may-2005 23:59:59.501' 8 ,'dd-mon-yyyy hh24:mi:ss:ff') ts1 9 , systimestamp ts2 10 from dual 11 ) 12 / DT1 ------------------- TS1 --------------------------------------------------------------------------- DT2 ------------------- TS2 --------------------------------------------------------------------------- 2005-05-02 00:00:00 2005-05-01 23:59:59.501000000 2010-02-17 09:56:01 17-FEB-10 09.56.01.087210 AM -05:00 but 11gr2:  ops$tkyte%ORA11GR2> select * from v$version; BANNER ------------------------------------------------------------------------------- Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production PL/SQL Release 11.2.0.1.0 - Production CORE 11.2.0.1.0 Production TNS for Linux: Version 11.2.0.1.0 - Production NLSRTL Version 11.2.0.1.0 - Production ops$tkyte%ORA11GR2> alter session set nls_date_format='yyyy-mm-dd HH24:MI:SS'; Session altered. ops$tkyte%ORA11GR2> alter session set nls_timestamp_format = 'yyyy-mm-dd HH24:MI:SS.FF'; Session altered. ops$tkyte%ORA11GR2> ops$tkyte%ORA11GR2> select cast(ts1 as date) dt1 2 , ts1 3 , cast(ts2 as date) dt2 4 , ts2 5 from 6 ( 7 select to_timestamp('01-may-2005 23:59:59.501' 8 ,'dd-mon-yyyy hh24:mi:ss:ff') ts1 9 , systimestamp ts2 10 from dual 11 ) 12 / DT1 ------------------- TS1 --------------------------------------------------------------------------- DT2 ------------------- TS2 --------------------------------------------------------------------------- 2005-05-01 23:59:59 2005-05-01 23:59:59.501000000 2010-02-17 09:57:22 17-FEB-10 09.57.22.406995 AM -05:00  Isn't it rounding to nearest second?   February 18, 2010 - 9am UTC Bookmark | Bottom | Top Reviewer: John Abate from Missouri, USA It looks to me that it is rounding the .501 fraction of a second to the nearest whole second 01-may-2005 23:59:59.501 rounds to 02-may-2005 00:00:00 Or am I missing something? Followup   February 18, 2010 - 9am UTC: doh, you are correct, I didn't notice the DATE flipped!  and I now do vaguely recall that the behavior changed - in that the timestamp would trunc() not round in 11g.  You are correct - I did not see the forest for all of the trees. I was so concentrated on the time going to 00:00:00, that I did not even really look at what the time was beforehand...

Reference : http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:77562635789106

Oracle Club에서 작성된 Oracle PL/SQL 기초 교육 문서입니다.

자세한 내용은 첨부파일의 내용을 확인해보세요.

pl_sql.doc