Troubleshooting SySAM

Identify and troubleshoot SySAM issues.

Description	Action
Cannot find license type during the Adaptive Server installation.	The Adaptive Server installation program displays only the most commonly used license types. If you are using a legacy license or a new license type, your license may not be listed. If you do not find the license type you need, select Unknown and complete the installation. After the installation is complete, use sp_lmconfig to change the license type. See the Reference Manual:Procedures for sp_lmconfig usage information. Note: If you set the license type value to Unknown, Adaptive Server uses the first available license. If you have licenses for more than one type, Adaptive Server may pick the incorrect license. Set the correct license type. See If the Installation Program Cannot Find a Suitable License if you select a served license model that the program cannot find.
The license server executables and scripts are not installed.	The sysam wrapper script and the executables for the license server (lmgrd and SYBASE) are not installed or found in the SYSAM-2_0 bin directory. By default, the license server component is not selected for installation. To install the license server, choose the custom installation option and select the license server component. Alternatively, download a standalone SySAM license server installation program from http://www.sybase.com/products/allproductsa-z/sysam.
The license server does not start.	For a license server to start, there must be at least one served license in the licenses directory. When you install a new license server, there are no served licenses in the licenses directory and the license server does not start until you activate a license from the Sybase Product Download Center (SPDC) or SAP Service Marketplace (SMP) and copy it into the licenses directory. Other causes for license server not to start include: The license activated from SPDC or SMP was an unserved license. Examine the license files. Served licenses always start with a `SERVER` header. If you do not see this header, you are using an unserved license, which does not work with the license server. If you are using a specific port number for the license, that port number may already be in use. Use `"netstat -a"` to verify that the port number is free. If not, free the port or use a different port number for the license server. The host name recorded in the `SERVER` header does not match the actual host name. The host name is recorded next to the `SERVER` keyword. If it does not match, correct the host name in the license file or set it to `"this_host"`, which is a keyword that works with any host name. The licenses copied may be activated for a different machine. The host ID next to the host name in the `SERVER` header must match the host ID for the machine where the license server is running.
The license server does not recognize the license files.	If the license server refuses to serve the licenses, it may be because: The license was activated for a different machine or activated using an incorrect host ID. Compare the host ID recorded in the license with the host ID assigned to the machine. If they do not match, check in and regenerate the license with the correct host ID. The license has been altered. If the license is being created by typing from a paper copy, verify if there are any errors entering the license. You can also download a new copy of the activated license from SPDC or SMP. If the host ID for your platform is based on the network adapter identification, verify that you have used an ID associated with a valid NIC. IDs associated with loopback adapters are invalid. If the ID associated with a removable network adapter has been used, ensure that the adapter is attached to the computer.
Adaptive Server does not start, and generates a license checkout failure error.	If Adaptive Server cannot check out the required license, it determines whether the license can be issued in grace mode. If a grace period cannot be given, the license is not granted. If the base license for Adaptive Server (ASE_CORE) has been running in a grace period, and the issue is not fixed by the end of the grace period, Adaptive Server fails to start. See "Adaptive Server cannot check out a license and starts with graced license instead."
Adaptive Server shows graced licenses even after the issue has been fixed.	Adaptive Server periodically performs license checks, and the license status is not immediately updated. It is updated only after the next heartbeat cycle is completed, which may take a few hours.
Adaptive Server cannot find license for an optional feature, even though the license exists.	Execute `sysam diag feature_name` to ensure that the license for the optional feature exists and can be checked out from the machine where Adaptive Server is running. If the feature exists, but cannot be checked out from Adaptive Server, this could be because: The optional feature is for a different edition. The status field in the license, which indicates whether a license is active or not, does not match between Adaptive Server and the optional feature. Execute sp_lmconfig to determine the edition, and active and standby (that is, inactive) configuration values. The information is located in the Property Name/Property Value table. The edition value is in the PE row and active and standby value is in the AS row. The values of PE and AS for the Adaptive Server must match the values of the VENDOR_STRING and ISSUER fields for the optional feature license. Some features, such as high availability (ASE_HA), are not offered with standby pricing, so there is no `"AS=A\|S"` flag in the license for this feature. This field is not considered when searching for a license without active and standby capability.
Adaptive Server does not start with the expected edition or license type.	If the edition and license type configuration parameters are not set, Adaptive Server uses the first available `ASE_CORE` license. If you have multiple `ASE_CORE` licenses with different editions and license types, the license that is the first available depends on many factors, such as license file directory sort order, available licenses on the license server, and so on. Sybase recommends that you set the edition and license type configuration parameters. When these parameters are set, you are assured that Adaptive Server starts with that configuration. If a matching license is unavailable, Adaptive Server starts under grace (if available) to allow you to resolve the licensing issue.
Adaptive Server picks an incorrect license.	Adaptive Server looks for licenses in these locations: Any saved values in the registry on Windows platforms, or the .flexlmrc file on UNIX platforms. Use `"lmpath -status"` to view the saved values. The values set for SYBASE_LICENSE_FILE and LM_LICENSE_FILE environment variables. All license files (any file with a .lic extension) in the licenses directory under the SYSAM-2_0 directory. All of the above locations are searched in the order specified until a suitable license is found. When a directory is specified, license files in that directory are loaded in the directory sort order. The first license that matches the feature name, version, edition, and license type filter is used. This license may not be what you were expecting to use. Adjust the above locations to control this.