SAP Note 16454 - RSINFINI: Please check TCP/IP destination DBSERVER

Symptom:

During the execution of Report RSINFINI or in transaction st04 (database monitor) you get the messages:

'Please check TCP/IP destination DBSERVER with transaction sm59'
or
'Please check whether user adm can execute $INFORMIXDIR/bin/onstat'

Reason and Prerequisites

The onstat interface doesn't work properly.
No error in RSINFINI.

Solution
If you get the message

Please check whether user adm can execute $INFORMIXDIR/bin/onstat

check if user adm's environment variable $INFORMIXDIR on the database server contains the correct path. Please contact your R/3 or database administrator.

If you get the message

'Please check TCP/IP destination DBSERVER with transaction sm59'

call transaction sm59 and check TCP/IP destination DBSERVER. It should already exist. If not please run Report RSINFINI using transaction se38.
If destination DBSERVER exists execute "ping" and change this destination until it works. Please contact your R/3 and network administrators. Maybe there is a gateway or you have unsufficient permissions.

It is necessary that a file .rhosts with an entry for each application server exists in the home directory for the adm user on the database server.

It's not necessary to execute RSINFINI a second time.

The R/3 versions 2.1I and 2.2C contain a bug. Please see also note 16390.
Up to 2.2D this problem can occur just due an error in the connection check part of RSINFINI. This means that the connection works properly and the test function is wrong. You can find it out using the interface for the INFORMIX tool onstat inside of transaction st04: Please call st04 and call via the menu Goto => Activity => Current statistics => Sysmaster database. You will see a screen which has among other things a function called onstat command. It should be already chosen. Please press the key and you'll get a list of options for onstat. With double click you can execute onstat with the chosen option. If you will get a regular list, the interface is ok.

If you use ksh as login shell for adm user, please rename /usr/sap//SYS/exe/run/infstrfc to infstrfc.orig on your database server and create a shell script called infstrfc with the following content: #!/bin/ksh
if [ "`basename $SHELL`" = "csh" ]
then
if [ -f $HOME/.cshrc ]
then
source $HOME/.cshrc
fi
else
if [ -f $HOME/.profile ]
then
. $HOME/.profile
fi
fi
`dirname $0`/infstrfc.orig "$@"

Set the file rights to "755" (chmod 755 infstrfc).