The following error messages may be encountered while using the SAP MaxDB Recovery Kit.
|The tunable MAXDB_ILB_ENABLED is set in the LifeKeeper defaults file for Internal Load Balancer support. Protecting multiple SAP MaxDB resources in this configuration requires all SAP MaxDB resource hierarchies to share a common resource.|| Create a dependency with a common resource for each SAP MaxDB resource or disable internal Load Balancer support. Some Internal Load Balancers (ILB) like Azure’s require X server ports to be active on one server at a time. The LifeKeeper in-service operation for the SAP MaxDB resource will start the X server processes. The normal out-of-service operation of a SAP MaxDB resource will not stop the X server processes. The tunable MAX_ILB_ENABLED can be set in the LifeKeeper defaults file (/etc/default/LifeKeeper) to change the out-of-service behavior so it will stop X server processes when the last SAP MaxDB resource is removed on a system. This requires that all SAP MaxDB resources must be in the same hierarchy to allow LifeKeeper to keep the X Server active on only one server. To place multiple SAP MaxDB resources in a single hierarchy create a gen/app resource as a root node at the top of the hierarchy:
|Unable to create pipe /usr/spool/sql/fifo/<db instance>||The directory /usr/spool/sql must have proper permissions to allow access for system user that owns the database instance.|
|Open device space <dev> permission denied||The device spaces on the backup and primary must have the same owner as well as the same user and group permissions.|
|Unable to set uid on startup||The setuid bit on <DependPath>/pgm/dbmsrv must be set and the owner of the file must be the SAP MaxDB system user.|
|runtime environment error|| There are several possible causes with different solutions:
|open Registry: Permission denied||The directory /usr/spool/sql/ini should be owned by the system user and group that owns the SAP MaxDB software. In addition, the user and group must also have read/write permissions on the directory.|
|ERR_USRREAD: could not read user data||The config files from <IndepDataPath>/config/<db instance> do not exist on the server or do not have the correct permissions. Verify that the files exist with the correct permissions for the system user that owns the database instance.|