User Name/Password Issues:

  • If the default user name is password-protected, the create UI does not detect this until after all validation is complete

    When creating the Sybase resource, you are prompted to enter the user name. The help to front displays a message that if no user is specified, the default of ‘sa’ will be used. However, no password validation is done for the default account at this time. When LifeKeeper attempts to create the Sybase resource, the resource creation fails because the password has not been validated or entered. The password validation occurs on the user/password dialog, but only when a valid user is actually entered on the user prompt. Even if using the default user name, it must be specified during the create action.

  • Password prompt skipped if no user name specified

    User/password dialog skips the password prompt if you do not enter a user name. When updating the user/password via the UI option, if you do not enter the Sybase user name, the default of ‘sa’ will be used and no password validation is done for the account. This causes the monitoring of the database to fail with invalid credential errors. Even if using the default user name, it must be specified during the update action. To fix this failure, perform the following steps:

  1. Verify that the required Sybase data files are currently accessible from the intended server. In most instances, this will be the backup server due to the monitoring and local recovery failure on the primary.

  2. Start the Sybase database instance from the command line on this server (see the Sybase product documentation for information on starting the database manually).

  3. From the command line, change directory (cd) to the LKROOT/bin directory (/opt/LifeKeeper/bin).

  4. Once in the bin directory, execute the following:
    ./ins_setstate –t <SYBASE_TAG> -S ISP

    where <SYBASE_TAG> is the tag name of the Sybase resource

  5. When the command completes, immediately execute the Update User/Password Wizard from the UI and enter a valid user name, even if planning to use the Sybase default of ‘sa’. Note: The Update User/Password Wizard can be accessed by right-clicking on the Sybase resource instance and selecting Change Username/Password.

  6. When the hierarchy has been updated on the local server, verify that the resource can be brought in service on all nodes.

  7. Protecting backup server fails when Sybase local user name >= eight characters

    The Sybase user name must consist of less than eight characters. If the Sybase local user name is greater than eight characters, the process and user identification checks used for resource creation and monitoring will fail. This will also prevent the protection of a valid Sybase Backup Server instance from being selected for protection. This problem is caused by the operating system translation of user names that are >= eight characters from the name to the UID in various commands (for example, ps). You must use a user name that is less than eight characters long.

Resource Create Issue:

  • Default Sybase install prompt is based on ASE 16.0 SP02 (/opt/sybase). During the LifeKeeper resource creation, the default prompt for the location of the Sybase installation shows up relative to Sybase Version 16.0 SP02 (/opt/sybase). You must manually enter or browse to the correct Sybase install location during the resource create prompt.
Extend Issues:

  • The Sybase tag prompt on extend is editable but should not be changed. The Sybase tag can be changed during extend, but this is not recommended. Using different tags on each server can lead to issues with remote administration via the command line.
Properties Page Issues:

  • Image appears missing for the Properties pane update user/password. Instead of the proper image, a small square appears on the toolbar. Selecting this square will launch the User/Password Update Wizard.
Sybase Monitor server is not supported in 15.7 or later with LifeKeeper. If the Sybase Monitor server process is configured in Sybase 15.7 or later, you must use a Generic Application (gen/app) resource to protect this server process.
Cannot create a resource using the Sybase RK OR experiencing issues on a LifeKeeper upgrade when using SLES 15

When setting up SLES 15 (this includes SLES 15 SP1 or SP2), the Sybase RK may not work on an upgrade or on a fresh install of LifeKeeper.

During a fresh install of LifeKeeper you won’t be able to create the Sybase resource, or during a LifeKeeper upgrade there could be issues in controlling the resource from LifeKeeper. The underlying error is “An error occurred when attempting to allocate localization-related structures”.

There are 2 possible solutions:

  1. Add a line in the [Linux] section of the file /sybase/<SID>/locales/locales.dat
    locale = POSIX, us_english, utf8


  2. Add this line to the Sybase profile for the syb<SID> user profile.
    This profile is typically located in /sybase//
    export LANG=en_US.UTF-8

    <SID> is the 3 letter system ID.

    These changes force the correct language to be used and is appropriate for US English locale. If another locale is used for Japan or China, please consult the local country and the system locale.

    You can also su to the syb<SID> user and run the command echo $LANG. The cshell parameter will point to the correct language for the appropriate locale.

    Which change is appropriate to make? It depends on the comfort level of the Sybase (SAP ASE) database administrator. One is changing the shell script, the other will add the POSIX support to the locales.

Unable to detect that Sybase ARK is running

Symptom: Unable to detect that Sybase ARK is running.

Cause: The Sybase ARK uses the default sql interface tool (isql). On some 64 bit systems, the isql tool is installed as isql64 and not isql.

Solution: The isql64 tool can be copied, in the same path, to isql. Or a link can be created between the isql64 executable and isql.


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