R3trans -x alternatively returns code 0012

[Former Member]

Hello.

After the upgrade to Oracle 10 (RAC) of a test system, the R/3 Instance starts but several wps die with db connect error ora 01034. Anyway some wps are alive and connected to the database. Running the R3Trans -x we have one run with return code 0000 and the next run with return code 0012, alternatively: even in this case the error is ora-01034.

4 ETW000 [dboci.c ,00000] *** ERROR => OCI-call 'olog' failed: rc = 1034 66916 0.281057

4 ETW000 [dbsloci. ,00000] *** ERROR => CONNECT failed with sql error '1034'

4 ETW000 104 0.281161

4 ETW000 [dblink ,00627] ***LOG BY2=>sql error 1034 performing CON 219 0.281380

I cannot find the reason of this behaviour, which occurs on both the instances of the RAC. Has anybody met this problem and found the reason?

Thanks a lot, ciao

Dino

[Former Member · Accepted solution]

Check your environment variables

Thanks

Prince

[Former Member · Accepted solution]

Hello.

The SAP Notes are not helpful, already checked. On the other hand the system starts, and only a number of Workprocesses cannot connect to the DB.

My env is

TERM=vt100

HOME=/home/aetadm

SHELL=/bin/csh

USER=aetadm

LOGNAME=aetadm

PATH=/oracle/SAP/920_64/bin:.:/home/aetadm:/usr/sap/AET/SYS/exe/run:/usr/kerberos/bin:/bin:/usr/bin:/usr/local/bin:/usr/bin/X11:/usr/X11R6/bin

HOSTTYPE=i386-linux

VENDOR=intel

OSTYPE=linux

MACHTYPE=i386

SHLVL=1

PWD=/home/aetadm

GROUP=sapsys

HOST=sapaet01

REMOTEHOST=192.168.0.101

LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=01;32:.cmd=01;32:.exe=01;32:.com=01;32:.btm=01;32:.bat=01;32:.sh=01;32:.csh=01;32:.tar=01;31:.tgz=01;31:.arj=01;31:.taz=01;31:.lzh=01;31:.zip=01;31:.z=01;31:.Z=01;31:.gz=01;31:.bz2=01;31:.bz=01;31:.tz=01;31:.rpm=01;31:.cpio=01;31:.jpg=01;35:.gif=01;35:.bmp=01;35:.xbm=01;35:.xpm=01;35:.png=01;35:.tif=01;35:

G_BROKEN_FILENAMES=1

SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass

LANG=en_US.UTF-8

SUPPORTED=en_US.UTF-8:en_US:en

LESSOPEN=|/usr/bin/lesspipe.sh %s

LANGVAR=en_US.UTF-8

HOSTNAME=sapaet01

SAPSYSTEMNAME=AET

DIR_LIBRARY=/usr/sap/AET/SYS/exe/run

LD_LIBRARY_PATH=/usr/sap/AET/SYS/exe/run

THREAD=1

dbms_type=ORA

dbs_ora_tnsname=AET

dbs_ora_schema=SAPR3

ORACLE_PSRV=AET

ORACLE_SID=AET

ORACLE_HOME=/oracle/SAP/920_64

ORACLE_BASE=/oracle/SAP

ORA_NLS33=/oracle/client/10x_32/ocommon/nls/admin/data

NLS_LANG=AMERICAN_AMERICA.US7ASCII

SAPDATA_HOME=/datafiles/AET

LD_ASSUME_KERNEL=2.4.1

Does anybody see anything wrong or missing?

the client is 32 bits, the database is 64 bits.

Thanks a lot

Dino

[Former Member · Accepted solution]

Hi,

I'm not much into RAC, didn't know RAC in 10g was available.

several notes ( perhaps they have nothing to do )

1) NLS_LANG=AMERICAN_AMERICA.<b>US7ASCII</b>

SAP does not support this characterset in 10g

2) If you upgraded to 10g why you have 9i as oracle home?

ORACLE_HOME=/oracle/SAP/<b>920_64</b>

3) Same in the Path

PATH=/oracle/SAP/<b>920_64</b>/bin...

4) This is wrong:

ORA_NLS33=/oracle/client/10x_32/ocommon/nls/admin/data

Oracle 10g does not uses ORA_NLS33, not important as you are in US7ASCII.

but, as mentioned before, you will have to change this to a supported characterset and then you will be getting other errors if you do not correct this.

I can also see that you have not installed the oracle instantclient 10g. Not important for this error, but necessary if you want to execute BR*

Regards

Fidel

[Former Member · Accepted solution]

Hello.

Thank you for your observations.

You are right regarding ORA_NLS33, the correct path is ORA_NLS33=/oracle/client/10x_32/instantclient

It points to the instant client folder, which is installed.

However correcting it doesn't change things, maybe because it is not used.

Regarding the PATH 920_64, the Central instance is on a standalone node, and the SAP guide for upgrade to Oracle 10 says that you don't need to change the client as the SAP instance will still use the 920 client. On the database server of course we have the 102_64 Oracle Home.

The fact that the db-connect sometimes works and sometimes not, let me think that the issue could be a time out or some similar issue between the listener on the db server and the tnsnames on the application server. In fact if it was an environment or a library problem I would expect that the R3trans always fail and SAP never starts.

Any idea about this issue is welcome.

Thanks a lot.

Dino

[Former Member · Accepted solution]

Hi Dino,

do you know the whitepaper written by Oracle (for SAP) teams?

http://www.oracle.com/newsletters/sap/products/rac/rac4sap_howto.html --> Configuration of SAP NetWeaver for Oracle Database 10g Real Application Clusters

It is vitally important to read this paper

regards

Barthez

[Former Member]

Hello. The problem was the wrong set up of the listener.

[Former Member]

Hello Dino,

I found the following notes that reference the issue in which may help you troubleshoot the issue:

Note 491174 - Composite SAP note for ORA-01034

https://service.sap.com/sap/support/notes/491174

Note 403004 - Database connect using R3trans fails

https://service.sap.com/sap/support/notes/403004

Both of these notes reference the same 1034 error that you are receiving.

Thank you,

Thomas