DB13 error for BRconnect

[Former Member]

Hello Experts,

We are scheduling the check database and update statistics job from DB13. the job finishes (completed status) within seconds. The job log shows that the DB instance is shutdown. However the DB instance is fine and application is up and running.

We get this error only when we schedule it through DB13. Hence we are forced to run the jobs from OS level using ora<sid> user. It works fine with ora<sid> user.

We are getting the following error while scheduling a job from DB13.:

Job started

Step 001 started (program RSDBAJOB, variant &0000000000015, user ID IBCRSK100162)

Execute logical command BRCONNECT On host impp16

Parameters: -u / -c -f stats -t PSAPPSRUSR

BR0801I BRCONNECT 6.40 (25)

BR0805I Start of BRCONNECT processing: ceacynss.sta 2009-03-14 10.52.34

BR0613E Database instance PSR is shut down

BR0806I End of BRCONNECT processing: ceacynss.sta2009-03-14 10.52.35

BR0280I BRCONNECT time stamp: 2009-03-14 10.52.35

BR0804I BRCONNECT terminated with errors

External program terminated with exit code 3

BRCONNECT returned error status E

Job finished

Hoping for a quick response.

[Former Member]

Hi

Can you make a quick check that OPS$<SID>ADM is logging in sql level?

command prompt>sqlplus /

Regards

Babu

[Former Member]

Hi Fidel,

1. I checked the shell for sidadm user. It was /bin/sh. We have 3 more similar setups (DB and CI seperate). In those the shell for sidadm is /usr/bin/ksh. So we changed the shell for sidadm to ksh in this system as well.

2. I am not sure how to check the gateway. I spoke to OS guy and he said the gateway is added between the DB server and CI server. (netstat -nr and the routing table). Is this the same gateway which you are referring?

Does the system need a restart after changes that we have made? (change of shell from sh to ksh, re-creation of sapdba role and assigning to OPS$SIDADM user, correction of ownership for brconnect to orasid:saysys)?

Hi Babu,

Yes I am able to login with OPS$SIDADM user

psradm> sqlplus /

SQL*Plus: Release 9.2.0.5.0 - Production on Tue Mar 17 09:57:23 2009

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Connected to:

Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production

With the Partitioning, OLAP and Oracle Data Mining options

JServer Release 9.2.0.5.0 - Production

SQL> show user

USER is "OPS$PSRADM"

Regards,

Anup Thatte

[fidel_vales]

Hi,

> In those the shell for sidadm is /usr/bin/ksh.

> So we changed the shell for sidadm to ksh in this system as well.

What <sid>adm are you talking about?

• The one in the CI server?

• The one in the DB server?

Note that the only properly supported shell is csh (202227), so you should start setting this shell for ALL SAP users. Once everything is working with this shell, you can try to change to other (ksh) and see if it also works

well, if you do not know if the gateway is installed ....

Try the following as <sid>adm on the CI:

• rsh <DB server> -l <sid>adm env

• rsh <DB server> -l <sid>adm sapxpg

Also check SAP Note 446172.

[Former Member]

Hi Fidel,

I was referring to sidadm on DB server.

Regarding checking the gateway, we tried the commands which you mentioned on the CI server but we are getting the following error:

psradm> rsh impp16db -l psradm env

rshd: 0826-813 Permission is denied.

psradm> rsh impp16db -l psradm sapxpg

rshd: 0826-813 Permission is denied.

I have asked the OS team to add the entry for sidadm in rhosts file on CI server. I will update the message again after checking rsh once the entry is done.

Regards,

Anup..

[fidel_vales]

can you show the environment variables for the <sid>adm in the DB server?

[Former Member]

Hi,

The env variables for DB server for sidadm are as follows:

psradm> env

_=/usr/bin/env

LANG=en_US

THREAD=NOPS

LOGIN=psradm

ORACLE_PSRV=PSR

PATH=/oracle/PSR/920_64/bin:/usr/sap/psradm:/usr/sap/PSR/SYS/exe/runU:/usr/sap/PSR/SYS/exe/run:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/sap/psradm/bin:/usr/bin/X11:/sbin:.

NLS_LANG=AMERICAN_AMERICA.WE8DEC

ORACLE_BASE=/oracle

LC__FASTMSG=true

LOGNAME=psradm

MAIL=/usr/spool/mail/psradm

dbs_ora_tnsname=PSR

ORACLE_SID=PSR

LOCPATH=/usr/lib/nls/loc

PS1=

psradm>

DB_SID=PSR

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

USER=psradm

AUTHSTATE=compat

dbs_ora_schema=SAPPSR

SHELL=/usr/bin/ksh

ODMDIR=/etc/objrepos

SAPDATA_HOME=/oracle/PSR

ORA_NLS33=/oracle/client/92x_64/ocommon/nls/admin/data

HOME=/usr/sap/psradm

TERM=xterm

MAILMSG=[YOU HAVE NEW MAIL]

ORACLE_HOME=/oracle/PSR/920_64

PWD=/usr/sap/psradm

TZ=IST-05:30

dbms_type=ORA

SAPSYSTEMNAME=PSR

A__z=! LOGNAME

NLSPATH=/usr/lib/nls/msg/%L/%N:/usr/lib/nls/msg/%L/%N.cat

LIBPATH=/usr/lib:/lib:/usr/sap/PSR/SYS/exe/run:/usr/sap/PSR/SYS/exe/runU

Regards,

Anup

[fidel_vales]

Hi,

Running out of ideas ....

The env variables seem to be OK.

last check

is impp16db and impp16 the same phisical server? same node in a cluster?

Problem could be that BRCONNECT connects to impp16, and you are using impp16db

[Former Member]

Hi Fidel,

Really appreciate your help!

impp16db and impp16 are two separate physical servers. There is no clustering involved.

Regards,

Anup..

[fidel_vales]

And the DB is located in which one?

Because the BRCONNECT tries to execute in the impp16

But may be your DB is on the impp16db

And that would be your problem. Starting BRCONNECT on the wrong system.

Take a look at the note 446772. I think the parameter profile SAPDBHOST is not correct.

Can you check also if this works:

rsh impp16 -l psradm env

[Former Member]

Hi,

Yes I think we are on the right track!

impp16db is the database server

impp16 is the CI server

I tried brconnect on OS level with psradm on the CI server. It gave the same error as i get from DB13.

I checked the SAPDBHOST parameter value in CI server and found out that it was wrongly put as impp16 instead of the impp16db.

I have modified that. Hopefully this solves our problem.

Unfortunately, we cannot take a restart of SAP application now since this is a production server. We have a scheduled offline backup on Thursday and only then we will be able to check it.

I will update the message after that. Thanks a ton!

Regards,

Anup..

[Former Member]

Hi,

The issue is not sorted out even after system restart. Getting the same error when running DB13 and even on OS level.

We are raising th issue on SAP marketplace.

Following are the Default profile parameters as shown from tx RZ10

Database host: impp16db

Update (server): impp16_PSR_00

Enqueue (server): impp16_PSR_00

Events (server): impp16_PSR_00

Mssg. srv. (host): impp16

Mssg. srv. (service): sapmsPSR

SNA Gateway (host): impp16

SNA Gateway (service): sapgw00

Regards,

Anup..

[Former Member]

Hi Fidel,

The sidadm user on the CI server is not able to connect to the database.

When I tried logging into sqlplus it says "Connected to an idle instance"

Even R3trans -d fails with foll error:

psradm> R3trans -d

This is R3trans version 6.13 (release 640 - 12.12.05 - 14:24:42).

2EETW152 Cannot open file "trans.log".

Permission denied

R3trans finished (0012).

Hopefully this gives us any lead to resolve the main issue.

Regards,

Anup

[former_member603052]

Hi Anup,

Download the SQL script sapdba_role.sql for creating the SAPDBA role from service market place. Execute this script as follows (sapdba_role.sql in the current directory) based on your scenerio run the command.

Unix Oracle 8.1: sqlplus internal @sapdba_role <SAPSCHEMA_ID> UNIX

Windows Oracle 8.1: sqlplus internal @sapdba_role <SAPSCHEMA_ID> NT

Oracle 9.2: sqlplus /nolog @sapdba_role <SAPSCHEMA_ID>

Oracle 10g: sqlplus /nolog @sapdba_role <SAPSCHEMA_ID>

Where <SAPSCHEMA_ID> is the schema ID of the SAP database user:

Regards,

Kalyan

[Former Member]

Hi,

It seems permission issue through DB13.

Execute sapdba_role.sql script. it will resolve the problem.

Regards,

Sachin Rane.

[Former Member]

Hi Sachin,

Thans for the response.

SAPDBA role is already granted to OPS$SIDADM user in the database. So I think there is some other issue. We have granted the sapdba role to the user again. But the error persists.

We also checked the brconnect permissions using SAP note 113747.

We can run the stats from OSlevel with orasid user successfully. Does DB13 use sidadm user in the background? Should we check running the command on OSlevel using sidadm user? Or should the BRconnect should be run with orasid user only?

Please help!

Regards,

Anup Thatte

[former_member185031]

>

> Hi Sachin,

>

> Thans for the response.

>

> SAPDBA role is already granted to OPS$SIDADM user in the database. So I think there is some other issue. We have granted the sapdba role to the user again. But the error persists.

>

> We also checked the brconnect permissions using SAP note 113747.

>

> We can run the stats from OSlevel with orasid user successfully. Does DB13 use sidadm user in the background? Should we check running the command on OSlevel using sidadm user? Or should the BRconnect should be run with orasid user only?

>

In SAP br* calls by sidadm user sidadm user in background so you should check the permission of sidadm user and try to execute with sidadm user.

Regards,

Subhash

[Former Member]

Hi Anup,

Please revisit the permission of brtools again. DB13 operations are always started with SIDADM in background, thats brconnect has sticky bit permission 4775 with owner orasid.

Also check SAP note 437648.

Regards,

Sachin Rane.

[Former Member]

Hi Sachin,

1. Yes the permissions for brconnect are correct:

-rwsrwxr-x 1 orapsr sapsys 4903548 Mar 26 2005 brconnect

2. We re-created sapdba role as per script sapdba_role.sql and granted the role to OPS$PSRADM

But this has not resolved the issue.

Best Regards,

Anup Thatte.

[fidel_vales]

Hi,

• Can you tell us if you have a standalone database server?

• Can you tell us if you can execute the brconnect command as <sid>adm?

[Former Member]

Hi Fidel,

1. It is a distributed architecture. i.e. DB server is different and CI (central instance) server is different

2. We are scuccessfully able to run the brconnect DBcheck via sidadm on OS level.

Regards,

Anup Thatte

[Former Member]

Hi Anup,

Are you able to perform other DB13 operation. you need gateway on DB server.

Regards,

Sachin

[Former Member]

Hi Sachin,

Any job that we schedule via DB13 is failing. And I think the relay should be in place other wise the application on CI will not work.

We heard that if you have DB and CI seperate then DB13 does't work in older versions SAP and it needs a kernal upgrade. However we could not find any relevant SAP Note for this.

Any idea on this? Does it need kernel upgrade to resolve the issue?

Our system info is as follows:

SAP System: SRM 4.00

Kernel release : 640

Patch Level: 112

Oracle DB: 9.2.0.5

Regards,

Anup..

[Former Member]

Hi Anup,

You need to install standalone gateway on DB server. Refer SAP note 927508.

Regards,

Sachin Rane.

[fidel_vales]

Hi,

> You need to install standalone gateway on DB server. Refer SAP note 927508.

That is not 100% true. There is another method. And it is to configure "rsh"

So, now that is clear that you have a standalone DB server. We need to know if you have configured a gateway.

My "guess" is that you are using "rsh" and that your <sid>adm user environment are not being taken properly because you are not using the correct shell.

could you confirm my "guesses":

1) no gateway on the DB server

2) shell of <sid>adm is, probably, kshell