I fixed this as follows:
1. On one node of the cluster, install the SAP DB software.
Perform a standard configuration of SAPDB as described in the SAP
manual.
2. Create the .XUSER.62 file in the home directory of the operating
system (OS) user who administers the SAPDB instance - <lcsid>adm.
a. Create a plain text file that contains information about the database
user who administers the SAPDB database instance with the following
contents:
DEFAULT
control
control
LP1
usushrscl006
<blank_line>
<blank_line>
-1
-1
<blank_line>
This example specifies the following information about a
database user who administers an SAP DB instance:
 The user key that is used to address this combination of XUSER data
is named DEFAULT.
 The user name and password of the database user are control
 The name of the SAP DB instance is LP1.
 The logical hostname for the SAP DB resource is usushrscl006
 No structured query language (SQL) mode is specified.
 The default time-out value of the SAP DB instance is used.
 The default isolation level of the SAP DB instance is used.
b. Generate the .XUSER.62 file from the plain text file that you created
in step a using the SAPDB command xuser for this purpose:
xuser -b user-info-file
Where user-info-file specifies the plain text file from which
you are generating the .XUSER.62 file
3. Copy the /usr/spool/sql directory and its contents from the node on
which you installed SAPDB to all nodes where resources for SAP DB and SAP
xserver will run.
Note: If you have a second LiveCache instance running on the failover node
you donât want to overwrite the /usr/spool/sql directory on the second
node. Instead use softlinks to preserve this directory hierarchy on the
failover server
Chris
Hough/UK/[EMAIL PROTECTED] To: [EMAIL PROTECTED]
B cc:
Subject: Error! Connection failed to
node (local) for database LP1: protocol error
16-08-04 18:53
Hi,
The command
dbmcli -d LP1 -u control,control db_state
(or any dbmcli command) produces the following error:
Error! Connection failed to node (local) for database LP1: protocol error
This occurs in an HA configuration when I am trying to start the database
LP1 on the failover server.
There is a second SAPDB database installed on the failover server, however,
this is shutdown prior to starting the LP1 database.
Has anyone seen this error before?
Thanks,
Chris
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]
