SIOS TECHNOLOGY CORP.

SAP MaxDB Troubleshooting

General Tips

The following error messages may be encountered while using the SAP MaxDB Recovery Kit.

Error Message Solution
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:

  • On the Edit menu, select Server, then Create Resource Hierarchy. The Create Resource Wizard dialog will appear.

  • Select Generic Application from the drop-down list and click Enter.

  • Follow the instruction in Creating a Generic Application Resource Hierarchy where the restore/remove scripts can be “/bin/true”.
    • Once the root resource is created, create a dependency between the root resource with each SAP MaxDB resource.
    • On the Edit menu, select Resource, then Create Dependency.
    • Select the Server where the resources are in-service.
    • Select the Parent Resource Tag for the root resource created above in the drop-down list.
    • Select the Child Resource Tag for the SAP MaxDB resource.

    It is also recommended to have a terminal leaf node. Once the single root resource is created above, the utility create_terminal_leaf can be used to create the gen/app resource on each branch of the hierarchy. If the tag for the root resource created above is “MaxDB_root” then to create the leaf nodes run, “create_terminal_leaf MaxDB_root”. New SAP MaxDB resources will need to be added to the hierarchy by creating dependencies with the root resource and the terminal leaf resource.
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:

  • The database instance parameter and configuration files do not exist. Create the database parameter files or copy the files from the template server.

  • The database has encountered a library problem. The server and software installation combination may require the use of the library libpthread-0.8.so. Consult the SAP MaxDB documentation for instructions.

  • The database instance environment has been corrupted. The processes must be manually killed. Then attempt to restore the resource to the in-service state.
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.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment