cancel
Showing results for 
Search instead for 
Did you mean: 

SAP to External Oracle DB returns ORA-03135

Former Member
0 Kudos

Hi,

We have a CRM 7.0 / NW 7.01 system running with a local Oracle 11.2.0.3 patch 10 database that pulls data from an external non-SAP Oracle Database. The data that is pulled from this external database is used to update SAP CRM objects and this is performed nightly. The external Oracle database is owned and controlled by our customer and they recently cloned the system and upgraded it to Oracle 11.2.0.1 (previously 10.2). After configuring the local tnsnames.ora to point to the upgraded external database (new IP address), the test program ADBC_TEST_CONNECTION returns ORA-03135: connection lost contact.

So far we have verified the following:

- latest patch on client side

- tnsnames.ora is correctly configured (our connection to the old database still works, and the only change was the IP address)

- TNSping to the external DB is successful

- connection to external database using sqlplus works (using the same login information as entered in the DB Connection in SAP t-code DBCO)

- the CRM system and the host for the external DB are on the same internal corporate network, so there should not be firewall issues

- latest DBSL installed on client side

- followed SAP Note 1261329 and verified that the configuration of the client side is correct

- if the wrong password is entered in the DB Connection in t-code DBCO, ADBC_TEST_CONNECTION will return "incorrect password" from the Oracle server

- the response from the external Oracle database with the ORA-03135 error was instantaneous, so there's not wait time and then a timeout

Has anyone encountered this issue before and know how to resolve it? ORA-03135 usually means it's a firewall issue or a timeout issue but we believe we've eliminated those possibilities. We believe that the SAP system is able to connect to the DB but we are getting kicked out immediately.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

The issue was resolved by installing the Full version of the Oracle Instant Client. We did not know that the customer changed the NLS_CHARACTERSET to one that is not supported by the Lite client.

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Douglas,

Could you check alert_SID.log to see more information about the error. This issue might be caused by a rule on the network component such a switch between two hosts.

Additionally, check the SQLNET.EXPIRE_TIME parameter on the host.

Best regards,

Orkun Gedik

Former Member
0 Kudos

Hi Orkun,

Could you please elaborate on whether you want me to look for the alert_SID.log file on the CRM host or the external DB host?

Just for completeness, I ran ADBC_TEST_CONNECTION to the new database and the alert_SID.log on the CRM host did not write any information to it.

Regards,
Doug

Former Member
0 Kudos

It could be logged in the alert log when the error occured. So, did you increase the expire time in SQLNET?

Former Member
0 Kudos

I will have to ask the customer whether they received anything in the alert_SID.log file on the external Oracle database. That is being arranged by a colleague of mine and the customer has not replied back yet.

Regarding the value for the SQLNET.EXPIRE_TIME parameter, it is set to the value of 10 on the client side, and I will ask the customer to check for the value on the server side.