R3trans

[Former Member]

Hi,

I completed Oracle upgrade (8.1.7 to 9.2.0.7)

while executing R3trans -x, trans.log showing the following error .If any idea, please tell me to troubleshoot this issue.

Regards

Srinivas

4 ETW000 [dev trc ,00000] -->oci_initialize 23 0.022824

4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call 'OCIInitialize' failed: rc = -1

4 ETW000 1471 0.024295

4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call 'OCIErrorGet' failed: rc = -2

4 ETW000 97 0.024392

4 ETW000 [dblink ,00419] ***LOG BY2=>sql error -1 performing CON [dblink#1 @ 419]

4 ETW000 179 0.024571

4 ETW000 [dblink ,00419] ***LOG BY0=>Can't get error text from Oracle [dblink#1 @ 419]

4 ETW000 28 0.024599

2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname = 'E02'"

[Former Member]

Hi,

Did u followed the oracle upgarde guide for 920..

Regards

Umesh K

[Former Member]

Hi Srinivas,

you probably run R3trans with ORACLE_HOME variable set to the wrong Oracle software. If you updated the rc files, may be you only have to open a new terminal or command line. If you get an error message "Can't get error text from Oracle" this is most likely your problem.

The other possible problem is that you run the wrong SAP kernel. If you use the same kernel as before, you have to run with the same Oracle client. Otherwise you have to use an EXT kernel for Oracle 9.2.0.

Best regards

Ralph Ganszky

[Former Member]

> Hi,

>

> I completed Oracle upgrade (8.1.7 to 9.2.0.7)

>

> while executing R3trans -x, trans.log showing the

> following error .If any idea, please tell me to

> troubleshoot this issue.

>

> Regards

> Srinivas

>

>

> 4 ETW000 [dev trc ,00000] -->oci_initialize

> 23 0.022824

> ERROR => OCI-call 'OCIInitialize' failed: rc = -1

> 4 ETW000

>

> 471 0.024295

> 4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call

> 'OCIErrorGet' failed: rc = -2

> 4 ETW000

>

> 7 0.024392

> 4 ETW000 [dblink ,00419] ***LOG BY2=>sql error

> -1 performing CON [dblink#1 @ 419]

> 4 ETW000

>

> 79 0.024571

> 4 ETW000 [dblink ,00419] ***LOG BY0=><b>Can't get

> error text from Oracle </b>[dblink#1 @ 419]

> 4 ETW000

>

> 8 0.024599

> 2EETW169 no connect possible: "DBMS = ORACLE

> --- dbs_ora_tnsname = 'E02'"

Hi,

what is your OS?

What is your kernel version?

Is this error happening on the CI or an AS?

Pleasen check your environment variables, they are not properly set, the message:

<b>> 4 ETW000 [dblink ,00419] ***LOG BY0=>Can't get

> error text from Oracle [dblink#1 @ 419]</b>

indicates that Oracle is not able to find the msg files to provide a description of the error.

This is not a "critical" error per se, but if oracle is not able to find this files ( located on the ORACLE_HOME ) perhaps this variable is not properly set.

The -1 seem to be related to the oracle client. If it is UNIX, the client depends on the kernel. If you have upgrade Oracle and changed ALL environment variables without thinking on the client to be used, then the connection could fail.

But there is a total <u>lack </u>of information to tell you for sure what is the <b>root cause</b> of the problem.

[Former Member]

Hi Srinivas,

Can you try applying oracle security and check if R3trans -d is working fine,

also apply sapdata role as follows

su - ora<sid>

cdexe

sqlplus '/assysdba' @sapdba_role <SID> UNIX

and

sqlplus '/assysdba' @orasid

reply sid in lower case

with this R3trans error will be resolved. Try

Murali.

[Former Member]

Hello,

Follow SAPNote 403004 - Database connect using R3trans fails. It says as under:

Symptom

When you start the system with startsap, startdb reports the following despite the fact that the database started successfully:

Connect to the database to verify, that the database is now open

R3trans check finished with return code: 12

• ERROR: Startup of database failed

Notify Database Administrator.

/usr/sap/<sid>/SYS/exe/run/startdb: Terminating with error code 2

Manually calling R3trans causes one of the following errors:

2EETW169 no connect possible: "DBMS = ORACLE --- ORACLE_SID = '<sid>'"

2EETW169 no connect possible: "DBMS = ORACLE --- dbs_ora_tnsname =

'<sid>'"

2EETW169 no connect possible: "invalid values set for DIR_LIBRARY

'/usr/sap/<sid>/SYS/exe/run' or dbms_type 'ora'"

R3trans finished (0012).

Reason and Prerequisites

The R/3 R3trans tool cannot connect to the database and therefore returns the return code 12. The error messages above are not particularly informative because there may be a multitude of different reasons for the error, for example:

Incorrectly configured OPS$ user

Problems with the shared libraries

Incorrectly set environment

Problems with the Net8 Connect

Solution

To analyze the problem, proceed as follows:

1. Log on as a <sid>adm user.

2. Switch to a directory where <sid>adm has write privileges (or stay in the Home directory).

3. Execute "R3trans -x" to check the database connect.

4. R3trans will probably still terminate now with return code 12. However, the trans.log file is simultaneously written in the current directory, in which additional information about the actual error is located.Therefore, check the contents of this file, preferably from bottom to top.

If you find the following type of lines, then you have more than likely come across the error:

• ERROR => OCI-call 'olog' failed: rc = <ora_nr>

• ERROR => CONNECT failed with sql error '<ora_nr>'

The <ora_no> placeholder stands for the returned Oracle error number (for example, 12500, in 1017, in 1034, and so on).

Important:Sometimes, the lines mentioned above with error number "1017" are not errors. Refer to note 400241 in this regard.

In individual cases, however, the termination also occurs with other error messages, for example:

DlLoadLib: load /usr/sap/<sid>/SYS/exe/run/dboraslib.o ->

DLENOACCESS

• ERROR => Couldn't load library

'/usr/sap/KM3/SYS/exe/run/dboraslib.o'

• ERROR => version mismatch between kernel (46D.00) and

DBSL shared library (46C.00)

Checking the client software installation in accordance with note 180430 (or the sub-notes referred to there) is often helpful in this case.

5. With the information acquired in the last step, you can now try to solve the link problems.You can find more information about the Oracle <ora_no> error number using the Oracle oerr tool.To do this, execute "oerr ora <ora_no>" at operating system level.

In many cases, searching for an SAP note using the error number or error message received will also provide relevant hits.

Hope this helps.

Pl dont forget to award points if resolved.

Regards