cancel
Showing results for 
Search instead for 
Did you mean: 

DBCO fails to Oracle Ver of 7.3.4.4.0 from ECC 6.0 of DB 11.2.0.2.0

pr_srinivas
Contributor
0 Kudos

Hi Experts.....

Our ECC 6.0 Ehp4 System is with Oracle 11.2.0.2.0

We are trying to make a cocnnection to DB of oracle Version 7.3.4.4.0.

We entered the required info in /sapmnt/<SID>/profile/oracle/tnanames.ora

as <sid>adm - when i give command tnsping for Oracle DB 7.3.4.4.0 - Ping is successful

but when i try to test connection from program

"ADBC_TEST_CONNECTION" - ( To test the DBCO's)

it is giving error as below

============================================

Testing a Database Connection Defined in DBCON

Could not open connection LABC21 .

sql error 3,134 occured:

ORA-03134: Connections to this server version are no longer supported.

=============================================

The above message is self explanatory, like from 11.2.0.2.0 database we can not connect to 7.3.4.4.0

My query is

01 ) is it not possible to make DBCO to a lower Version DB like 11.2.0.2.0 to 7.3.4.4.0? - A Confirmation please !!

02) When integration demand is DBCO from ECC6.0 11.2.0.2.0 to Oracle Ver 7.3.4.4.0 - What is the workaround ?

Rgds

PR

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Oracle Support Note : 207303.1 clearly mention there is no support for 11.2.0 to 7.x.x verison.

Oracle Note

-


Oracle Client / Server Interoperability Support

Use this note to understand Oracle client versions are supported to work with which versions of the Oracle Database.

Introduction

This note gives a summary of the support for interoperability between Oracle client and server versions. This includes support for connections over database links between Oracle versions. Note that this relates to support for investigation of defects / ability to obtain bug fixes.

Note that this is a general guide for interoperability only - certain products or utilities may impose additional restrictions on supported combinations specific to the product / utility. eg: Precompilers, Export / Import utilities etc..

For a summary of the support status of each Oracle release see Note:161818.1

General Policy

Oracle's general policy is to test and support each new Oracle release for compatibility with older releases thus:

u2022Test the NEW client to each OLDER server release where the OLDER release is still covered by Premier Support (formerly Primary Error Correction support) at the time that the NEW version is released.

u2022Test OLDER clients to the NEW server release where the OLDER release is still covered by Premier Support (formerly Primary Error Correction support) OR is in the first two years of Extended Support (formerly Extended Maintenance support).

u2022Tests between the NEW version and other OLDER releases may be added where Oracle deems it sensible to support interoperability between those releases.

Current Interoperability Support Situation

The matrix below summarizes client and server combinations that are supported.

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 10.1.0 client to an 11.1.0 server issue requires the customer to have a valid Extended Support contract for the 10.1.0 client in order for Oracle to investigate it.

Server Version

Client Version 11.2.0 11.1.0 10.2.0 10.1.0 9.2.0 9.0.1 8.1.7 8.1.6 8.1.5 8.0.6 8.0.5 7.3.4

11.2.0 Yes Yes ES #7 No LES #5 No #3 No #3 No #3 No #3 No #3 No #3 No #3

11.1.0 Yes Yes ES #7 ES #6 LES #5 No #3 No #3 No #3 No #3 No #3 No #3 No #3

10.2.0 ES #7 ES #7 ES ES LES #5 No Was No #3 No #3 No #3 No #3 No #3

10.1.0(#4) ES #6 ES #6 ES ES LES Was Was #2 No #3 No #3 No #3 No #3 No #3

9.2.0 LES #5 LES #5 LES #5 LES LES Was Was No No Was No No #1

9.0.1 No No No Was Was Was Was Was No Was No Was

8.1.7 No No Was Was Was Was Was Was Was Was Was Was

8.1.6 No No No No No Was Was Was Was Was Was Was

8.1.5 No No No No No No Was Was Was Was Was Was

8.0.6 No No No No Was Was Was Was Was Was Was Was

8.0.5 No No No No No No Was Was Was Was Was Was

7.3.4 No No No No Was Was Was Was Was Was Was Was

Key:

Yes Supported

LES Supported but fixes only possible for severity 1 issues for customers with Extended Support . Limitations apply - see click here for policy details for 9.2.

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: u2022#1 - See Note:207319.1

u2022#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 .

u2022#3 - An ORA-3134 error is correctly reported when attempting to connect to this version.

u2022#4 - There are problems connecting from a 10g client to 8i/9i where one is EBCDIC based. See Note:3564573.8

u2022#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 are not supported.

u2022#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.

u2022#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.

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. So, 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.

Regards

Sivakumar.R

pr_srinivas
Contributor
0 Kudos

Siva............Thank you very much.

Oracle Note : Client_Server_Interoperability_Support_Between_Different_Oracle_Versions_ID_207303.1

confirmed

the Database Connection is not possible from our ECC-Oracle 11.2.0.2.0 to LABC21 7.3.4.4.0.

Thank you very much

Rgds

PR

pr_srinivas
Contributor
0 Kudos

HI...

for Metalink login we can use credentials avaialble in following note as we all aware

Note 758563 - Oracle Metalink access for SAP customers

Rgds

PR

Answers (0)