DB host name is incorrect

[Former Member]

  Dear experts,

  We have cluster environment, CI & DB are on different nodes:

1.In RZ10, under default.pfl we have configured parameter SAPDBHOST value to <DB host_name>

2, But , when we check from SAP level under 'system' tab->'status'-> 'database data'-> 'host': it shows value set to <DB host_name1>. Means we are getting 2 different  database host name. Is something fishy??

3.  while executing job in DB13, We found no database server in GO TO-> Backend configuration->Background server, except CI & Application server

Message was edited by: Sumit Jain

[Former Member · Accepted solution]

Dear team,

1.we have configured RFC connection succesfully. Please find details:

SAPXPG_DBDEST_<physical db host name>

Previous:  Activation Type-> start on explicit type

Correction: Activation Type-> start on application server

Previous:  Gateway host: <physical db host name>(as per sap note 980266,under 'solution' tab point 2)

Correction: Gateway host: <host name of productionserver>

SAPXPG_DBDEST_<virtual db host name>

Previous:  Activation Type-> start on explicit type

Correction: Activation Type-> start on application server

Previous:  Gateway host: <physical db host name> (as per sap note 980266,under 'solution' tab point 2)

Correction: Gateway host:  <host name of production server>

2. Update BRTOOLS

3. Change permission as per SAP NOTE 113747(point 4& 5)

[Former Member]

I dont think there is anything wrong.

As long as the parameter SAPDBHOST points to the virtual hostname.

The system status will show physical hostname.

Regrading your other question, DB13 jobs, in a cluster environment when we schedule a DB13 job. There are 2 ways in which the task is executed. The older systems use RFC method. the new SAP systems use SAPXPG. ie external program.

When the job starts it will check to see if the DB is in the same host, else it will take the value of SAPDBHOST & execute the br* command through the gateway.

You need to make sure that the parameter gw/remsh is set to rsh/ssh , which ever you use & that you can execute the following command from the CI server to the DB server.

rsh <db server> -l <sid>adm df

or

ssh <db server> -l <sid>adm df

This should return the df output of the DB server. With this setup, you should be able to get the DB13 jobs to run.

Let me know how it went.

Regards,

Shanser

[Former Member]

Hi,

Thanks very much!!!1

Hi,

Thanks very much!!!1

We are analysing your suggestion.

Please find my reply to Mauricio

[Former Member]

Hi Sumit,

Went through the logs... the issue is exactly the one i highlighted in my previous post.

So check the parameter gw/remsh ... default should be /usr/bin/rsh

based on whether ssh or rsh, try executing the below commands from the CI server

ssh <db server> -l <sid>adm df

or

rsh <db server> -l <sid>adm df

It should give you the 'df' output of the db node. Note:- it should work without giving <sid>adm password.

Let me know if you face further issues.

Regards,

Shanser

[Former Member]

Thanks a lot Mr.Mohammed

We have both rsh/ssh shell in gateway parameters:

gw/remsh	: /usr/bin/rsh
gw/ssh	: /usr/bin/ssh

but we use ssh shell in our environment.As you suggested,we tried executing the below commands from the CI server. Please find output below:

1.SIDadm> ssh <Physical db host name> -l SIDadm df

Password:

2.SIDadm> ssh <Virtual db host name> -l SIDadm df

The authenticity of host '[Virtual db host name]:5522 ([121.244.234.139]:5522)' can't be established.

RSA key fingerprint is 86:81:7b:8d:33:56:b2:c7:75:45:79:7e:f2:fc:9d:84.

Are you sure you want to continue connecting (yes/no)?

Please suggest!!!!!!!!!

[Former Member]

Hi Sumit,

What happens when you give the password for <sid>adm?

Does it show the "df" output of the DB node?

If yes, (then your very close to resolving the issue) please ask your platform engineer to make it work without prompting for the password. They do it usually in a few mins.

Also can we try with rsh?, because seems like gw/remsh is using rsh...

PS: give yes for the RSA finger print prompt!

Let me know how it goes...

Regards,

Shanser

[Former Member]

Dear Mohammed

As you know, we have 2 nodes CI & DB

CI-> we found command brtools,brbackup,brconnect runs under ora<SID>, rest of Br* under <SID>adm in /sapmnt/PRD/exe

DB-> All Br* tools under <SID>adm  in /sapmnt/PRD/exe.

This difference is worrying us. so, first we are resolving this issue thinking this might be issue.

Please be in touch,i'll display the result

[Former Member]

Sure Sumit, i get email alerts

btw, regarding your concern ... as long as you have br* utilities in the <sid>adm environment you should be fine. To test, what you can do is... say for brconnect stats... just login to the DB node... switch to <sid>adm & try running the stats manually... & try command 'brtools' there... If they work , then you should be set!

Hope you get to resolve the issue soon...

Regards,

Shanser

[Former Member]

Hi,

OK.... it's fine....... For abovementioned Br* tools issue, we are co-ordinating with database team.

Meanwhile, would you please help us resolving below given issues. I am here pasted links:

http://scn.sap.com/thread/3144232

http://scn.sap.com/thread/3146428

Please help !!!!!

[Former Member]

Hi,

I tried both commands as you said. But it's asking again & again for password. I put SID<adm> password everytime. but no use.. Please find output.

SIDadm> ssh <Virtual db host name>  -l SIDadm df

The authenticity of host '[Virtual db host name]:5522 ([121.244.234.139]:5522)' can't be est ablished.

RSA key fingerprint is 86:81:7b:8d:33:56:b2:c7:75:45:79:7e:f2:fc:9d:84.

Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added '[Virtual db host name]:5522,[121.244.234.139]:5522' (RSA) to the list of known hosts.

Password:

Password:

Password:

SIDadm> ssh <Physical db host name> -l SIDadm df

Password:

Password:

[Former Member]

Dont you know the password? its the same as the master password you set during the install.

If you need to check the user if its expired ...  give command "chage -l <sid>adm" as root user

Also ask you platform engineer to make this work withour password prompt, Only then will it work.

Regards,

Shanser

[Former Member]

Hi,

Since, we don't have root user ID,we are from SAP team, system team don't share root passwd with us. But i executed below command with same SID<adm>. Below is output

SIDadm> chage -l SIDadm

Password:

output is:

Minimum:        0

Maximum:        60

Warning:        5

Inactive:       -1

Last Change:            Feb 20, 2012

Password Expires:       Apr 20, 2012

Password Inactive:      Never

Account Expires:        Never

[Former Member]

Dear Mohammed,

we have configured RFC connection succesfully. Please find details:

Previously in RFC's, we hadn't configured Gateway host;Gateway service. after passing appropriate values in both option, please find log detail:

  Old Configuration:

SAPXPG_DBDEST_<physical db host name>

Activation Type-> start on explicit type

Program:sapxpg

Target Host: <physical db host name>  [ Please check target host is correct or not, I think CI host name should come here]

save as: IP address of physical db host

Start Type of external program:Deafult Gateway value

CPI_C Timeout-> Default Gateway value

Gateway host:<physical db host name>

Gateway service: sapgw<instance number>

Click on execution:

Logon    Connection Error

Error Details    Error when opening an RFC connection

Error Details    ERROR: SAP gateway connection failed. Is SAP gateway started?

Error Details    LOCATION: SAP-Server <server name> on host <host name of Ci> (wp 1)

Error Details    COMPONENT: CPIC

Error Details    COUNTER: 2467

Error Details    MODULE:

Error Details    LINE:

Error Details    RETURN CODE: 236

Error Details    SUBRC: 0

Error Details    RELEASE: 701

Error Details    TIME: Sun Mar 18 15:05:25 2012

Error Details    VERSION:

SAPXPG_DBDEST_<virtual db host name>

Activation Type-> start on explicit type

Program:sapxpg

Target Host: <virtual db host name>  [ Please check target host is correct or not, I think CI host name should come here]

save as: IP address of virtual db host

Start Type of external program:Deafult Gateway value

CPI_C Timeout-> Default Gateway value

Gateway host:<virtual db host name>

Gateway service: sapgw<instance number>

click on execution:

Logon    Connection Error

Error Details    Error when opening an RFC connection

Error Details    ERROR: SAP gateway connection failed. Is SAP gateway started?

Error Details    LOCATION: SAP-Server <server name> on host <host name of Ci> (wp 0)

Error Details    COMPONENT: CPIC

Error Details    COUNTER: 2467

Error Details    MODULE:

Error Details    LINE:

Error Details    RETURN CODE: 236

Error Details    SUBRC: 0

Error Details    RELEASE: 701

Error Details    TIME: Sun Mar 18 15:23:41 2012

Error Details    VERSION:

Latest configuration

SAPXPG_DBDEST_<physical db host name>

Previous:  Activation Type-> start on explicit type

Correction: Activation Type-> start on application server

Previous:  Gateway host: <physical db host name>(as per sap note 980266,under 'solution' tab point 2)

Correction: Gateway host: <host name of productionserver>

SAPXPG_DBDEST_<virtual db host name>

Previous:  Activation Type-> start on explicit type

Correction: Activation Type-> start on application server

Previous:  Gateway host: <physical db host name> (as per sap note 980266,under 'solution' tab point 2)

Correction: Gateway host:  <host name of production server>

Points which need to be adressed:

1. sap note 980266 suggest put 'gateway host' as db host name, but it didn't work.

2. If we put 'Deafult Gateway value'  for Start Type of external program & CPI_C Timeout. then why we have to set value under gateway host & service

[Former Member]

  Dear Mohammed

  Any update!!!!!!!!!!!!!

[Former Member]

i think i already told you what needs to be done.

The below command needs to work without asking for a password

rsh <db server> -l <sid>adm df

[Former Member]

Yes, Check my reply, RFC is working fine...

we mentioned correction...

Please check my reply again...

Points which need to be adressed:

1. sap note 980266 suggest put 'gateway host' as db host name, but it didn't work.

2. If we put 'Deafult Gateway value'  for Start Type of external program & CPI_C Timeout. then why we have to set value under gateway host & service

[Former Member]

Dear Sumith

check wheather you have install 2 sap or database instances on the same server.

reg

[Former Member]

Sumit,

Is your cluster is in MSCS or Unix ? If MSCS, you have to set DBHOSTNAME in profile as SAP<SID>ORA instead of physical DB hostname.

Are you able to failover DB using Virtual hostname between nodes ? What is the name of  your MSG server, DB and Physical hostnames ?

[Former Member]

Hi Arjun,

Our cluster is on Unix.

Yes. Fail over is happening successfully.

 What is the name of  your MSG server, DB and Physical hostnames ?

all the three are different.

Regards,

Sumit

[Former Member]

Hi Sumit,

The entry from System>Status will be returned due to the OS call hostname on the database host and it doesn't matter much if it's the same value as SAPDBHOST or not. The SAPDBHOST parameter is important to know in which hostname your instances should connect to the db, but the screen that you are seeing is only informative.

Cheers,

Maurício

[Former Member]

System status showing physical DBhostname is correct . As long as you able to failover the DB using virtual hostname and profiles are using virtual hostname you should be good.

[Former Member]

Mauricio Wecker wrote:
The SAPDBHOST parameter is important to know in which hostname your instances should connect to the db, 

Hi

Hi,

It is clear Parameter SAPDBHOST-> Virtual DB host name & system>status-> Physical DB host name.

While analyzing database, we found command brtools,brbackup,brconnect runs under ora<SID>, rest of Br* under <SID>adm.

Please find logs error given error;

LOGS from SM21

04:00:30 BTC  035 300 <username>   LC  2 Error 1003 when executing external command brconnect on (xpgid=0,convid=.)

06:49:54 DP Q0  I Operating system call recv failed (error no. 104 )

LOgs from SM37

Job started

Step 001 started (program RSDBAJOB, variant &0000000000125, user ID <user name>)

Execute logical command BRCONNECT On host <Virtual DB host name>

Parameters: -u / -jid CHECK20120314040000 -c -f check

SXPG_STEP_XPG_START: is_local_host: rc = 403

SXPG_STEP_XPG_START: host = <Virtual DB host name>

SXPG_STEP_XPG_START: is_local_r3_host: rc = 802

SXPG_STEP_XPG_START: RFC_TCPIP_CONNECTION_OPEN: rc = 1003

SXPG_STEP_COMMAND_START: SXPG_STEP_XPG_START returned: 1,003

SXPG_COMMAND_EXECUTE(LONG)

<timestamp> = 20120314040029

COMMANDNAME = BRCONNECT

ADDITIONAL_PARAMETERS = -u / -jid CHECK20120314040000 -c -f check

LONG_PARAMS

OPERATINGSYSTEM = ANYOS

TARGETSYSTEM = <Virtual DB host name>

DESTINATION

SY-SUBRC = 1003

SXPG_COMMAND_EXECUTE failed for BRCONNECT - Reason: program_start_error: For More Information, See SYS

SAPXPG_DBDEST_<Virtual DB host name>

Logon    Connection Error

Error Details    Error when opening an RFC connection

Error Details    ERROR: timeout during allocate

Error Details    LOCATION: SAP-Gateway on host <host name of CI server> / sapgw00

Error Details    DETAIL: no connect of TP sapxpg from host <Virtual DB host name> after 20 sec

Error Details    COMPONENT: SAP-Gateway

Error Details    COUNTER: 179197

Error Details    MODULE: gwr3cpic.c

Error Details    LINE: 1973

Error Details    RETURN CODE: 242

Error Details    SUBRC: 0

Error Details    RELEASE: 701

Error Details    TIME: Wed Mar 14 18:49:37 2012

Error Details    VERSION: 2

SAPXPG_DBDEST_<Physical DB host name>

Logon    Connection Error

Error Details    Error when opening an RFC connection

Error Details    ERROR: timeout during allocate

Error Details    LOCATION: SAP-Gateway on host <host name of CI server> / sapgw00

Error Details    DETAIL: no connect of TP sapxpg from host <Physical DB host name> after 20 sec

Error Details    COMPONENT: SAP-Gateway

Error Details    COUNTER: 179202

Error Details    MODULE: gwr3cpic.c

Error Details    LINE: 1973

Error Details    RETURN CODE: 242

Error Details    SUBRC: 0

Error Details    RELEASE: 701

Error Details    TIME: Wed Mar 14 18:53:17 2012

Error Details    VERSION: 2