Source:Troubleshooting SAP ERP

From SEPsesam
Revision as of 17:34, 29 March 2022 by Unknown (talk | contribs) (Updating to match new version of source page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Other languages:

Template:Copyright SEP AG en

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3 Beefalo/5.0.0 Jaglion. For previous documentation version(s), check documentation archive.


SAP ERP

Using XUSER MaxDB tool for authentication during backup fails with the error XUser not found!

Problem

  • The SAP MaxDB XUSER command-line tool can be used to store user log-on data thus simplifying logon to databases. When using XUSER and the script runs as command event, the backup script reports the following error: XUser not found!

Cause

  • The SAP MaxDB XUSER tool creates a file .XUSER.62 in the home drive of the corresponding user. If the script runs as command event, no environment is set and thus also not the HOME variable. If the HOME variable is not set, the DB cannot find the .XUSER.62 file belonging to the user and cannot map and verify the key to the user, therefore the command event fails.

Solution

    Export the HOME variable for the root user in the backup script (command event script) as follows: #!/bin/bash HOME=/root export HOME /.../dbmcli .... -U <key> .... .....

See also

Analyzing SEP sesam Log FilesSAP ERP with MaxDB