Use Control F to search for a specific error code in each catalog. To search for any error code, select the Search button at the top right of the screen.


Code Severity Message Cause/Action
136002 ERROR Usage: $usage

Cause: Invalid arguments provided to the SAP HANA create script.

Action: Please provide appropriate arguments in the form: <Resource Tag> <SAP SID> <HDB Instance> [Switchback Type] [Virtual IP Resource Tag]

136003 ERROR END failed create of resource $tag on server $me with return value of $errcode.

Cause: Failure during SAP HANA resource creation.

Action: Verify that SAP HANA System Replication is fully configured and enabled on both the primary and secondary replication sites and reattempt the resource creation operation.

136005 ERROR An unknown error has occurred in utility rlslocks on server $me. View the LifeKeeper logs for details and retry the operation.

Cause: Failure of the LifeKeeper rlslocks utility during SAP HANA resource creation.

Action: Resolve any issues found in the LifeKeeper log file and reattempt the resource creation operation.

136006 ERROR END failed create of resource $tag on server $me with signal $sig.

Cause: Failure during SAP HANA resource creation due to a signal.

Action: Review the LifeKeeper log file for details.

136008 ERROR An unknown error has occurred in utility getlocks on server $me. View the LifeKeeper logs for details and retry the operation.

Cause: Failure of the LifeKeeper getlocks utility during SAP HANA resource creation.

Action: Resolve any issues found in the LifeKeeper log file and reattempt the resource creation operation.

136009 ERROR The SAP HANA product was not found in the directory $obj->{'hana_util_path'} on server $me. Verify that SAP HANA is correctly installed and that all necessary file systems are mounted.

Cause: Required SAP HANA binaries could not be located during resource creation.

Action: Verify that SAP HANA is correctly installed and configured on all servers in the cluster.

136010 ERROR Failed to create resource as id $id already exists on system $me.

Cause: A LifeKeeper resource with the given ID already exists on the system.

Action: Check whether the SAP HANA database is already protected by LifeKeeper.

136011 ERROR Failed to create new tag $tag for SAP HANA resource on $me.

Cause: The provided SAP HANA resource tag is already in use by another LifeKeeper resource and the LifeKeeper newtag utility failed to create a new tag.

Action: Choose a different tag name for the SAP HANA resource.

136012 ERROR Failed creation of resource with $tag on system $me.

Cause: Failed to create the given SAP HANA resource in LifeKeeper.

Action: Resolve any issues found in the LifeKeeper log file and reattempt the resource creation operation.

136014 ERROR Failed to create resource dependency for parent $tag and child $virtual_ip_tag.

Cause: Failed to create a dependency between the SAP HANA resource and its dependent virtual IP resource.

Action: Resolve any issues found in the LifeKeeper log file and reattempt the resource creation operation.

136015 ERROR The info field for resource $tag could not be successfully generated using values [SID: $info_sid, Instance: $info_instance, Replication Mode: $info_repl_mode, Site Name: $info_site_name, Operation Mode: $info_oper_mode]. If using SAP HANA System Replication, please verify that it is fully configured and enabled on both the primary and secondary systems before creating the SAP HANA resource.

Cause: An invalid value was found when creating the SAP HANA resource info field.

Action: Verify that SAP HANA is properly installed and configured and that SAP HANA System Replication is fully configured and enabled on all servers in the cluster.

136016 ERROR The selected server $me is not the primary/source system for SAP HANA System Replication for the selected SID $sid and HDB instance $instance. Please select 'Cancel' and start this action on the primary/source HANA System Replication system.

Cause: Resource creation is initiated on a secondary system in HANA System Replication.

Action: Initiate the create action on a primary system in HANA System Replication.

136031 ERROR END failed extend of resource $target_tag on server $me with return value of $err_code.

Cause: Failure during SAP HANA resource extension.

Action: Resolve any issues found in the LifeKeeper log file and reattempt the resource extension operation.

136033 ERROR Usage: $usage

Cause: Invalid arguments provided to the SAP HANA extend script.

Action: Please provide appropriate arguments in the form: <Template System> <Template Tag> <Switchback Type> <Target Tag>

136035 ERROR Template resource $template_tag on server $template_sys does not exist.

Cause: The template SAP HANA resource to be extended does not exist on the template server.

Action: Verify that the SAP HANA resource that is being extended exists on the template server.

136036 ERROR Resource with matching id $target_id already exists on server $me for App $app_type and Type $res_type.

Cause: An SAP HANA resource with the same LifeKeeper ID already exists on the target system.

Action: Check whether the SAP HANA database is already protected by LifeKeeper on the target server.

136037 ERROR Resource with matching tag $target_tag already exists on server $me for App $app_type and Type $res_type

Cause: An SAP HANA resource with the same LifeKeeper resource tag already exists on the target server.

Action: Check whether the SAP HANA database is already protected by LifeKeeper on the target server.

136039 ERROR Error creating resource $target_tag on system $me.

Cause: Failed to create an equivalent SAP HANA resource on the target server.

Action: Resolve any issues found in the LifeKeeper log file and reattempt the resource extension operation.

136040 ERROR The target tag ($target_tag) and template tag ($template_tag) must be the same.

Cause: Resource tag name used on primary system is different than resource tag name used on secondary system. Both must be same.

Action: While resource creation use same name as primary system tag and secondary system tag.

136045 ERROR Cannot extend resource $template_tag to server $me.

Cause: The SAP HANA canextend script indicates that the resource cannot be extended to the given target system.

Action: Resolve any issues found in the LifeKeeper log file and reattempt the resource extension operation.

136047 ERROR Usage: $usage

Cause: Invalid arguments provided to the SAP HANA canextend script.

Action: Please provide appropriate arguments in the form: <Template System> <Template Tag>

136048 ERROR Resource $template_tag does not exist on server $template_sys.

Cause: The template SAP HANA resource to be extended does not exist on the template server.

Action: Verify that the SAP HANA resource that is being extended exists on the template server.

136049 ERROR The system user $hana_user does not exist on server $me.

Cause: The SAP Administrative User for the SAP HANA database does not exist on the given server.

Action: Verify that SAP HANA is properly installed and configured.

136050 ERROR The user id for user $hana_user ($template_uid) on template server $template_sys is not the same as user id ($uid) on target server $me.

Cause: The user ID for the SAP Administrative User differs between the template and target servers.

Action: Verify that SAP HANA is properly installed and configured on all servers in the cluster.

136051 ERROR The group id for user $hana_user ($template_gid) on template server $template_sys is not the same as group id ($gid) on target server $me.

Cause: The group ID for the SAP Administrative User differs between the template and target servers.

Action: Verify that SAP HANA is properly installed and configured on all servers in the cluster.

136052 ERROR The home directory for user $hana_user ($template_home) on template server $template_sys is not the same as home directory ($user_home) on target server $me.

Cause: The home directory for the SAP Administrative User differs between the template and target servers.

Action: Verify that SAP HANA is properly installed and configured on all servers in the cluster.

136053 ERROR The SAP HANA instance $instance does not exist for $sid on server $me.

Cause: Installation directories for the given SAP HANA database instance could not be located.

Action: Verify that SAP HANA is properly installed and configured on all servers in the cluster.

136055 ERROR The SAP HANA site name $target_obj->{'site_name'} on server $me must be different from site name $template_obj->{'site_name'} on $template_obj->{'sys'}.

Cause: The SAP HANA System Replication site name is the same on both the primary and secondary servers.

Action: Stop the SAP HANA database on the secondary server and use the hdbnsutil utility to re-register the secondary replication site using a different site name.

136056 ERROR Unable to obtain SAP HANA System Replication parameters for database $instance on server $me. Please verify that SAP HANA System Replication is enabled and properly configured and that the database instance is running on all servers in the cluster.

Cause: SAP HANA System Replication parameters could not be determined for the database on the given system.

Action: Verify that SAP HANA System Replication is enabled and properly configured and that the database is running on all servers in the cluster.

136057 ERROR Unable to create a HANA object for database $instance on server $me. Please verify that database instance $instance is properly installed.

Cause: Unable to create an internal hana object representing the given instance on the given server.

Action: Verify that the database instance is properly installed and that all necessary file systems are mounted.

136083 ERROR Usage: $usage

Cause: Invalid arguments in the SAP HANA delete script.

Action: Provide both a valid HANA LifeKeeper resource tag name and resource ID. Usage: delete -t <tag> -i <id> [-U]

136096 ERROR One of the required parameters (server, tag, or action) was missing. Unable to set the local recovery policy.

Cause: One of the required parameters (server, tag, or action) was not provided.

Action: Provide the required parameters and reattempt the operation.

136097 ERROR Failed to $flg_action local recovery for SAP HANA resource $tag on server $node.

Cause: Failed to enable or disable local recovery for the given SAP HANA resource on the given server.

Action: Verify that LifeKeeper is running and fully initialized, then reattempt the operation.

136099 ERROR Failed start of SAP Host Agent on server $sys.

Cause: Failed to start the SAP Host Agent processes (i.e., saphostexec, saposcol) on the given server.

Action: Check SAP Host Agent process trace logs and correct any issues found, then reattempt the operation.

136100 ERROR Failed start of SAP Host Agent on server $sys.

Cause: Failed to start SAP Host Agent processes (i.e., saphostexec, saposcol) on the given server.

Action: Inspect the SAP Host Agent process trace logs and correct any issues found, then reattempt the operation.

136160 ERROR Unable to create SAP HANA object. The SID and instance for the SAP HANA database must be provided.

Cause: Either the SAP SID or the SAP HANA instance name were missing while trying to create an SAP HANA object.

Action: Inspect the LifeKeeper log file for more details.

136161 ERROR Unable to create SAP HANA object. Resource system name and tag name must be provided.

Cause: Either the system name or resource tag name were missing while trying to create an SAP HANA object.

Action: Inspect the LifeKeeper log file for more details.

136162 ERROR Could not find any information regarding resource $tag on $sys.

Cause: Failed to obtain information about the SAP HANA resource with the given tag.

Action: Verify that a SAP HANA resource with the given tag exists on the given server.

136168 ERROR Unable to check status of SAP Host Agent on server $self->{'sys'}. Command \"$curr_cmd\" returned exit code $ret.

Cause: Failed to determine the status of the SAP Host Agent processes on the given server.

Action: Inspect the SAP Host Agent trace files (e.g., dev_saphostexec) for more details.

136174 ERROR Unable to create SAP HANA object. The SID or instance value is missing.

Cause: Either the SAP SID, the SAP HANA instance name, or one of the SAP HANA System Replication values were missing while trying to create an SAP HANA object.

Action: Inspect the LifeKeeper log file for more details.

136182 ERROR Failed to $flg_action flag \"${HANA_FLAG_DATA_OUT_OF_SYNC}_$eqv_tag{$sys}\" on server $sys.

Cause: Failed to create or remove the !HANA_DATA_OUT_OF_SYNC_<tag> flag on the given server.

Action: Inspect the LifeKeeper log file for more details.

136190 ERROR Failed to start SAP Host Agent processes on server $self->{'sys'}. Command \"$hostagent_cmd\" returned $ret.

Cause: Failed to start the SAP Host Agent processes on the given server.

Action: Inspect the SAP Host Agent trace files (e.g., dev_saphostexec) for more details.

136191 ERROR Failed to start SAP OS Collector process on server $self->{'sys'}. Command \"$oscol_cmd\" returned $ret.

Cause: Failed to start the SAP OS Collector process on the given server.

Action: Inspect the SAP OS Collector trace files (e.g., dev_coll) for more details.

136193 ERROR $takeover_text of SAP HANA System Replication for SAP HANA database $self->{'instance'} failed on server $node with exit code $ret.

Cause: Failed to register the given server as primary master for the given database in SAP HANA System Replication.

Action: Inspect the SAP HANA trace files (e.g., nameserver_<hostname>.xxxxx.xxx.trc) for more details.

136197 ERROR Update of resource info field for $eqv_tag{$sys} on $sys failed with exit code $setinfo_ret. Current info: [$info]. Attempted new info: [$new_info].

Cause: Failed to update the info field for the given resource on the given server.

Action: Inspect the LifeKeeper log file for more details.

136202 EMERG Failed to disable Autostart for SAP HANA instance $self->{'instance'} on server $sys with exit code $remexec_ret. Please manually set \"Autostart = 0\" in the instance profile $profile on $sys.

Cause: The value of the Autostart parameter could not be modified in the given HDB instance profile on the given server.

Action: Edit the HDB instance profile manually and set "Autostart = 0".

136205 ERROR Failed start of SAP Start Service for SAP HANA database $instance on server $sys.

Cause: Failed to start SAP Start Service for the given SAP HANA database.

Action: Inspect the SAP Start Service trace files (e.g., sapstartsrv.log) for more details.

136208 ERROR LifeKeeper was unable to determine the SAP HANA System Replication mode for database $rem_obj->{'instance'} on server $rem_obj->{'sys'} while attempting to identify the previous primary replication site. Please resolve the issue and bring the SAP HANA resource in-service on the system where the database should be registered as primary master.

Cause: Failed to determine the SAP HANA System Replication mode on the given server. As a result, the previous primary replication site could not be identified.

Action: Inspect the LifeKeeper log file for more details.

136210 ERROR Failed start of SAP Start Service for SAP HANA database $rem_obj->{'instance'} on server $rem_obj->{'sys'}. Unable to stop the database on the server where it is currently registered as primary master.

Cause: Failed to start SAP Start Service for the given SAP HANA database on the given server. As a result, the database could not be stopped on the current primary SAP HANA System Replication site.

Action: Inspect the SAP Start Service trace files (e.g., sapstartsrv.log) for more details.

136212 ERROR Failed stop of SAP HANA database $rem_obj->{'instance'} on server $rem_obj->{'sys'} where it is currently registered as primary master.

Cause: Failed to stop the given SAP HANA database on the given server.

Action: Inspect the SAP HANA trace files and LifeKeeper log file for more details.

136217 ERROR Failed start of SAP HANA database $instance on server $sys.

Cause: Failed to start the given SAP HANA database on the given server.

Action: Inspect the SAP HANA trace files and LifeKeeper log file for more details.

136220 ERROR Unable to register $sys as a secondary SAP HANA System Replication site for database $instance. The host name of the current primary replication site was not provided.

Cause: The host name of the current primary SAP HANA System Replication site was not provided when attempting to register a secondary replication site.

Action: Inspect the LifeKeeper log file for more details.

136233 EMERG WARNING: A temporary communication failure has occurred between servers $self->{'sys'} and $sys. Manual intervention is required in order to minimize the risk of data loss. To resolve this situation, please take one of the following resource hierarchies out of service: $self->{'tag'} on $self->{'sys'} or $eqv{$sys} on $sys. The server that the resource hierarchy is taken out of service on will become the standby server for SAP HANA database $self->{'instance'}.

Cause: A temporary communication failure has caused the given equivalent HANA resources to both be brought in-service at the same time on their respective host servers.

Action: Take the entire HANA resource hierarchy out of service on the server which should become the secondary replication site. Once the database has been stopped on that server, LifeKeeper will automatically register it as a secondary replication site during the next quickCheck cycle.

136234 EMERG WARNING: SAP HANA database $self->{'instance'} is running and registered as primary master on the following servers: $primary_node_list. Manual intervention is required in order to minimize the risk of data loss. To resolve this situation, please stop database $self->{'instance'} on the standby server by running the command \'su – $self->{'sid_admin'} -c \"$SAP_CONTROL -nr $self->{'instance_number'} -function StopWait $HANA_STOP_WAIT 5\"\' on that server, allow LifeKeeper to register the standby server as a secondary replication site, then use LifeKeeper to bring resource $self->{'tag'} in-service on the intended primary replication site.

Cause: The given SAP HANA database is running and registered as primary master on two cluster servers concurrently.

Action: Use the command provided in the message to stop the database on the standby server. Once the database is stopped, LifeKeeper will automatically register the standby server as a secondary replication site.

136236 ERROR Failed to remove ${HANA_FLAG_DATA_OUT_OF_SYNC}_$tag flag on server $sys.

Cause: Failed to remove the !HANA_DATA_OUT_OF_SYNC_<HANA Tag> LifeKeeper flag on the given server. This will cause the given SAP HANA resource to fail to come in-service on the given server until it is removed.

Action: Verify that LifeKeeper is running and fully initialized. If it can be verified that SAP HANA System Replication is in-sync, the out-of-sync flag can be removed manually with the command "/opt/LifeKeeper/bin/flg_remove -f '!HANA_DATA_OUT_OF_SYNC_<HANA Tag>'".

136238 ERROR Unable to create SAP HANA object. Resource system name and tag name must be provided.

Cause: Either the server name or the resource tag name were missing while trying to create an SAP HANA object.

Action: Inspect the LifeKeeper log file for more details.

136239 ERROR Failed start of SAP Start Service for SAP HANA database $obj->{'instance'} on server $obj->{'sys'}. Unable to determine status of the database on $obj->{'sys'}.

Cause: Failed to start SAP Start Service for the given SAP HANA database on the given server. As a result, the status of the database could not be determined.

Action: Inspect the SAP Start Service trace files (e.g., sapstartsrv.log) for more details.

136242 ERROR Unable to create SAP HANA object. At least one of the SAP HANA System Replication values is missing.

Cause: SAP HANA System Replication parameters could not be determined for the database on the given system.

Action: Verify that SAP HANA System Replication is enabled and properly configured and that the database is running on all servers in the cluster.

136243 ERROR Unable to locate the pingnfs utility ($pingnfs) on server $me. Please verify that this utility exists and is executable.

Cause: Unable to locate the pingnfs utility used for testing available of exported NFS shares.

Action: Verify that the pingnfs utility exists in the given location and is executable.

136245 ERROR Critical NFS shares being exported by server $sys ($export_list) are not currently available. Please verify that the NFS server is alive and that all NFS-related services are running.

Cause: The given critical NFS shared file systems are not currently available.

Action: Verify that the NFS server exporting the file systems is alive and that all necessary NFS-related services are running.

136248 ERROR Unable to open file $crit_mount_file on server $me. Please verify that this file exists and is read-enabled.

Cause: Unable to open the file containing mount information for critical NFS shares on the given server.

Action: Verify that the file exists in the specified location and is read-enabled.

136253 ERROR The SAP HANA \"takeover with handshake\" feature is available only for SAP HANA versions 2.0 SPS04 and greater. Database $self->{'instance'} cannot be resumed.

Cause: Resuming a suspended database is not supported in SAP HANA versions earlier than 2.0 SPS04.

Action: Upgrade to SAP HANA 2.0 SPS04 or later in order to use features related to "Takeover with Handshake".

136254 ERROR Attempt to resume suspended primary database $self->{'instance'} on server $self->{'sys'} failed with exit code $ret.

Cause: The attempt to resume the suspended database instance on the given server failed.

Action: Inspect the LifeKeeper and SAP log files to determine the cause of the failure. Either reattempt the operation or bring the corresponding LifeKeeper resource in-service on a different server.

136258 ERROR Attempt to register server $node as the secondary SAP HANA System Replication site for database $self->{'instance'} failed with exit code $ret.

Cause: The attempt to register the given server as a secondary SAP HANA System Replication site for the given database instance failed.

Action: Inspect the LifeKeeper and SAP log files to determine the cause of the failure and manually correct any issues found. While the SAP HANA resource is in-service, LifeKeeper will automatically continue attempting to register the backup server in a secondary HSR role.

136263 ERROR Usage: $usage

Cause: Invalid arguments in the SAP HANA resource restore script.

Action: Please provide appropriate arguments in the form: -t <Resource Tag> -i <Resource ID>

136265 ERROR Error getting resource information for $tag on server $me.

Cause: Failed to obtain information about the given SAP HANA resource on the given server.

Action: Verify that a SAP HANA resource with the given tag exists on the given server.

136266 ERROR The resource $tag protecting SAP HANA database $instance is not in sync. To protect the data LifeKeeper will not restore the resource on $me. Please restore the resource on the previous source server to allow the resync to complete.

Cause: SAP HANA System Replication was not in sync before attempting to bring the database resource in-service on the backup server.

Action: Bring the SAP HANA resource in-service on the previous primary server and allow the resynchronization to complete.

136275 ERROR Failed to determine SAP HANA System Replication mode for database $instance on server $me.

Cause: Failed to determine the SAP HANA System Replication mode for the given database on the given server.

Action: Inspect the SAP HANA trace files (e.g., nameserver_<hostname>.xxxxx.xxx.trc) and the LifeKeeper log file for more details.

136351 ERROR Usage: $usage

Cause: Invalid arguments in the SAP HANA resource quickCheck script.

Action: Please provide appropriate arguments in the form: -t <Resource Tag> -i <Resource ID>

136353 ERROR Error getting resource information for $tag.

Cause: Failed to obtain information about the given SAP HANA resource.

Action: Verify that a SAP HANA resource with the given tag exists on the given server.

136354 EMERG The replication mode of the SAP HANA database $instance corresponding to resource $tag was modified outside of LifeKeeper and is no longer registered as primary master on server $me. Please bring the SAP HANA resource in-service on the server where the database should be registered as primary master. Resource monitoring for $tag will be suspended until the issue is resolved.

Cause: The SAP HANA System Replication mode for the given database was modified outside of LifeKeeper.

Action: Bring the SAP HANA resource in-service on the server where it should be registered as primary master.

136363 EMERG LifeKeeper was unable to determine the SAP HANA System Replication mode for database $instance corresponding to resource $tag on server $me. Resource monitoring for $tag will be suspended until the issue is resolved.

Cause: Failed to determine the SAP HANA System Replication mode on the given server.

Action: Inspect the LifeKeeper log file for more details.

136375 EMERG An NFS server exporting a critical shared file system for resource $tag is currently unavailable. Resource monitoring for $tag will be suspended until the issue is resolved.

Cause: A critical NFS shared file system is currently unavailable.

Action: Verify that the NFS server is alive and that all necessary NFS-related services are running.

136376 EMERG WARNING: LifeKeeper resource $tag is designed for use in situations where SAP HANA System Replication (HSR) is disabled, but HSR was found to be enabled on server $me. Please ensure that the correct LifeKeeper resource type is being used for your current SAP HANA configuration.

Cause: The given LifeKeeper resource is designed to protect a SAP HANA database environment where HANA System Replication (HSR) is disabled, but HSR is currently enabled on the given server.

Action: Verify that the correct LifeKeeper resource type is being used based for your SAP HANA configuration. If you have migrated from a SAP HANA configuration where HSR was disabled to one where it is enabled, the corresponding SAP HANA resource must be recreated in LifeKeeper.

136377 EMERG SAP HANA database $instance corresponding to resource $tag is currently suspended on server $me due to actions performed outside of LifeKeeper. Please take the SAP HANA resource out of service on server $me and bring it in-service on the server where the database should be registered as primary master. Bringing resource $tag back in-service on $me will resume the suspended database. Resource monitoring for $tag will be suspended until the issue is resolved.

Cause: The given SAP HANA database instance has been suspended on the given server due to actions performed outside of LifeKeeper.

Action: If you would like to resume the suspended database on the server where the corresponding LifeKeeper resource is currently in-service (Active), execute the command given in the message. Otherwise, bring the LifeKeeper SAP HANA resource in-service on the intended primary replication site.

136450 ERROR Usage: $usage

Cause: Invalid arguments provided to the SAP HANA remove script.

Action: Please provide appropriate arguments in the form: <Template Tag> <Template Id>

136454 ERROR Error getting resource information for $tag.

Cause: Failed to obtain information about the given SAP HANA resource.

Action: Verify that a SAP HANA resource with the given tag exists on the given server.

136456 ERROR Failed start of SAP Start Service for SAP HANA database $instance on server $me.

Cause: Failed to start SAP Start Service for the given SAP HANA database.

Action: Inspect the SAP Start Service trace files (e.g., sapstartsrv.log) for more details.

136459 EMERG WARNING: LifeKeeper resource $tag is designed for use in situations where SAP HANA System Replication (HSR) is disabled, but HSR was found to be enabled on server $me. Please ensure that the correct LifeKeeper resource type is being used for your current SAP HANA configuration.

Cause: The given LifeKeeper resource is designed to protect a SAP HANA database environment where HANA System Replication (HSR) is disabled, but HSR is currently enabled on the given server.

Action: Verify that the correct LifeKeeper resource type is being used based for your SAP HANA configuration. If you have migrated from a SAP HANA configuration where HSR was disabled to one where it is enabled, the corresponding SAP HANA resource must be recreated in LifeKeeper.

136462 ERROR Failed to remove flag \"${hana::HANA_FLAG_LEAVE_DB_RUNNING}_$tag\" on server $me. This may cause subsequent remove actions for resource $tag on server $me to unintentionally fail to stop the database.

Cause: Failed to remove the LifeKeeper !volatile!hana_leave_db_running_<tag> flag on the given server.

Action: Manually remove the flag with the command "/opt/LifeKeeper/bin/flg_remove -f '!volatile!hana_leave_db_running_<tag>'" on the given server. While the flag exists, out-of-service operations for the SAP HANA resource on the given server will leave the protected database instance running.

136550 ERROR Usage: $usage

Cause: Invalid arguments in the HANA resource recover script.

Action: Provide both a valid HANA LifeKeeper resource tag name and resource ID. Usage: recover -d <tag> -n <id>

136555 ERROR Error getting resource information for $tag on server $me.

Cause: Failed to obtain information about the given HANA resource on the given server.

Action: Verify that the server is online, LifeKeeper is running, and the HANA resource exists.

136556 EMERG The replication mode of the SAP HANA database $instance corresponding to resource $tag was modified outside of LifeKeeper and is no longer registered as primary master on server $me. Please bring the SAP HANA resource in-service on the server where the database should be registered as primary master. Resource monitoring for $tag will be suspended until the issue is resolved.

Cause: The SAP HANA System Replication mode for the given database was modified outside of LifeKeeper.

Action: Bring the SAP HANA resource in-service on the server where it should be registered as primary master.

136558 EMERG LifeKeeper was unable to determine the SAP HANA System Replication mode for database $instance corresponding to resource $tag on server $me. Resource monitoring for $tag will be suspended until the issue is resolved.

Cause: The SAP HANA System Replication mode could not be determined for the given database on the given server.

Action: Inspect the SAP HANA trace files and LifeKeeper log file for more details.

136559 ERROR Resource $tag is no longer ISP on server $me. Exiting $cmd for $tag.

Cause: The given SAP HANA resource is no longer ISP on the given server.

Action: Inspect the LifeKeeper log file for more details.

136650 ERROR Usage: $usage

Cause: Invalid arguments provided to the SAP HANA hana_stop_all_dbs script.

Action: Please provide appropriate arguments in the form: hana_stop_all_dbs -t <tag>

136654 ERROR Error getting resource information for $tag.

Cause: Failed to obtain information about the given SAP HANA resource.

Action: Verify that a SAP HANA resource with the given tag exists on the given server.

136658 ERROR Failed start of SAP Start Service for SAP HANA database $x->{'instance'} on server $x->{'sys'}. Could not determine status of SAP HANA DB on $x->{'sys'}.

Cause: Failed to start SAP Start Service for the given SAP HANA database.

Action: Inspect the SAP Start Service trace files (e.g., sapstartsrv.log) for more details.

136661 ERROR Failed stop of SAP HANA database $x->{'instance'} on server $x->{'sys'}.

Cause: Failed to stop the given SAP HANA database on the given server.

Action: Inspect the SAP HANA trace files and LifeKeeper log file for more details.

136673 ERROR Usage: $usage

Cause: Invalid arguments provided to the SAP HANA hana_takeover_with_handshake script.

Action: Please provide appropriate arguments in the form: -t <tag> [-s <target server>] [-b]

136674 ERROR Unable to remove the \"${hana::HANA_FLAG_LEAVE_DB_RUNNING}_$tag\" flag on server $isp_node. This may cause subsequent remove actions for resource $tag on server $isp_node to unexpectedly fail to stop the database.

Cause: Failed to remove the LifeKeeper !volatile!hana_leave_db_running_<tag> flag on the given server.

Action: Manually remove the flag with the command "/opt/LifeKeeper/bin/flg_remove -f '!volatile!hana_leave_db_running_<tag>'" on the given server. While the flag exists, out-of-service operations for the SAP HANA resource on the given server will leave the protected database instance running.

136675 ERROR Script $cmd exited unexpectedly due to signal \"$sig\" on server $me. This may leave the $tag resource hierarchy as well as SAP HANA System Replication in an unexpected state. Please verify that the cluster resources are in the expected state.

Cause: The hana_takeover_with_handshake script exited unexpectedly due to the given signal on the given server.

Action: Verify that the SAP HANA cluster resources are in the expected state. If not, fix any issues that are found and bring the SAP HANA resource hierarchy in-service on the intended primary server.

136677 ERROR Unable to find equivalent SAP HANA resource corresponding to $tag on server $target_node.

Cause: Unable to find an equivalent SAP HANA resource corresponding to the given resource on the given server.

Action: Verify that the given resource tag is correct, the resource has been extended to the given target server, and that LifeKeeper is running and fully initialized on the target server.

136678 ERROR Unable to obtain information about equivalent SAP HANA resource $tag on server $target_node. Verify that LifeKeeper is running and fully initialized.

Cause: Unable to find an equivalent SAP HANA resource corresponding to the given resource on the given server.

Action: Verify that the given resource tag is correct, the resource has been extended to the given target server, and that LifeKeeper is running and fully initialized on the target server.

136679 ERROR Resource $tag is not a SAP HANA resource.

Cause: The given resource is not a SAP HANA (database/hana) resource.

Action: Verify that the resource tag is correct.

136680 ERROR Resource $tag is designed for use in an environment where SAP HANA System Replication is disabled. Takeover with handshake cannot be performed for this resource type. Please use the standard \"In Service…\" command instead.

Cause: Features related to "Takeover with Handshake" may only be used in environments where SAP HANA System Replication is enabled.

Action: Use the standard "In Service…" option to bring the SAP HANA resource in-service.

136681 ERROR SAP HANA resource $tag is not currently in-service on any server in the cluster. The resource must be in-service and SAP HANA System Replication must be in-sync before performing a takeover with handshake.

Cause: The given SAP HANA resource is not in-service on any server in the cluster while attempting "Takeover with Handshake".

Action: Bring the SAP HANA resource in-service on the intended primary server.

136682 ERROR SAP HANA resource $tag is currently in-service on multiple servers: $isp_node_list. The resource must be in-service on only one server and SAP HANA System Replication must be in-sync before performing a takeover with handshake.

Cause: The given SAP HANA resource is in-service on multiple servers in the cluster while attempting a "Takeover with Handshake".

Action: Take the resource out of service on every server except the one where it is intended to be registered as primary master.

136684 ERROR Unable to create internal SAP HANA object for resource $tag on server $target_node. Verify that all necessary file systems are mounted and that LifeKeeper is running and fully initialized on $target_node.

Cause: Unable to create an internal hana object representing the given instance on the given server.

Action: Verify that the database instance is properly installed and that all necessary file systems are mounted.

136685 ERROR Takeover with handshake is only supported in SAP HANA versions 2.0 SPS04 and greater. The SAP HANA software must be upgraded in order to use this feature. Please use the standard \"In Service…\" command instead.

Cause: The "Takeover with Handshake" feature cannot be used when the underlying SAP HANA database version is less than 2.0 SPS04.

Action: Upgrade to SAP HANA 2.0 SPS04 or later in order to use the "Takeover with Handshake" feature.

136686 ERROR Takeover with handshake cannot be performed for database $target_obj->{'instance'} on server $target_node because the database is not currently running and registered as primary on any other server in the cluster.

Cause: The given SAP HANA database instance is not running and registered as primary master on any server in the cluster during an attempted "Takeover with Handshake".

Action: Bring the corresponding SAP HANA resource in-service on the intended primary server.

136687 ERROR SAP HANA database $target_obj->{'instance'} is running and registered as primary on more than one server in the cluster. Please resolve this situation and reattempt the takeover.

Cause: The given SAP HANA database instance is running and registered as primary on multiple servers during an attempted "Takeover with Handshake".

Action: If the database instance is already running and registered as primary on the intended primary server, bring the corresponding LifeKeeper resource in-service on that server. If not, stop the database instance on every server except the one where it is currently in-service on LifeKeeper, allow LifeKeeper to resume system replication, then reattempt the takeover.

136689 ERROR Unable to create internal SAP HANA object for resource $tag on server $isp_node. Verify that all necessary file systems are mounted and that LifeKeeper is running and fully initialized on $isp_node.

Cause: Unable to create an internal hana object representing the given instance on the given server.

Action: Verify that the database instance is properly installed and that all necessary file systems are mounted.

136690 ERROR Unable to set the ${hana::HANA_FLAG_LEAVE_DB_RUNNING}_$tag flag on server $isp_node. Aborting takeover with handshake attempt for database $target_obj->{'instance'} on server $target_node.

Cause: Failed to set the !volatile!hana_leave_db_running_<tag> LifeKeeper flag on the given server during an attempted "Takeover with Handshake".

Action: Inspect the LifeKeeper log file for more information. Correct any issues found and reattempt the takeover.

136692 ERROR Takeover with handshake for database $target_obj->{'instance'} failed on server $target_node.

Cause: The "Takeover with Handshake" attempt failed for the given SAP HANA database instance on the given target server.

Action: If HANA_HANDSHAKE_TAKEOVER_FAILBACK=true in /etc/default/LifeKeeper, the SAP HANA resource hierarchy will automatically be brought back in-service on the previous database host server. Otherwise, the SAP HANA resource hierarchy must be manually brought in-service on the intended primary server.

136695 ERROR Resource $tag does not exist on server $me.

Cause: The given resource does not exist on the given server.

Action: Verify that the resource tag is correct.

136696 ERROR Unable to verify the status of resource $tag on server $target_node. Assuming that it is not in-service.

Cause: Failed to determine the status of the given resource on the given server while checking whether the "Takeover with Handshake" was successful.

Action: Verify that LifeKeeper is running and fully initialized on the given server and that the communication path between the local and target servers is active. If HANA_HANDSHAKE_TAKEOVER_FAILBACK=true in /etc/default/LifeKeeper, the SAP HANA resource hierarchy will automatically be brought back in-service on the previous database host server. Otherwise, the SAP HANA resource hierarchy must be manually brought in-service on the intended primary server.

136697 ERROR Resource $res was not successfully brought in-service on server $target_node.

Cause: The given resource failed to come in-service on the given server during an attempted "Takeover with Handshake".

Action: If HANA_HANDSHAKE_TAKEOVER_FAILBACK=true in /etc/default/LifeKeeper, the SAP HANA resource hierarchy will automatically be brought back in-service on the previous database host server. Otherwise, the SAP HANA resource hierarchy must be manually brought in-service on the intended primary server.

136698 ERROR LifeKeeper is not running or is not fully initialized on server $me.

Cause: LifeKeeper is either not running or not fully initialized on the given server during an attempted "Takeover with Handshake".

Action: Either start LifeKeeper with /opt/LifeKeeper/bin/lkstart or allow it to fully initialize, then reattempt the takeover.

136699 ERROR Unknown server $target_node.

Cause: The given server host name is not recognized.

Action: Verify that the server host name is correct and that communication paths have been created between the local server and the target server.

136700 ERROR Usage: $usage

Cause: Invalid arguments provided to the SAP HANA remoteregisterdb script.

Action: Please provide appropriate arguments in the form: remoteregisterdb -d <tag> -n <id>

136705 ERROR Unable to obtain information about resource $tag on server $me. Exiting $cmd for $tag.

Cause: Failed to determine information about the given SAP HANA resource on the given server.

Action: Verify that the given resource tag is correct, the resource exists on the given server, all necessary file systems are mounted, and that LifeKeeper is running and fully initialized on the given server.

136706 ERROR Resource $tag is no longer ISP on server $me. Exiting $cmd for $tag.

Cause: The SAP HANA remoteregisterdb script is exiting because the SAP HANA resource is no longer in service (ISP) on the given server.

Action: No action is required.

136707 ERROR The $cmd event is intended for use only in environments in which SAP HANA System Replication is enabled. Exiting $cmd for $tag.

Cause: The SAP HANA remoteregisterdb event detected that SAP HANA System Replication is disabled for the database protected by the given SAP HANA resource.

Action: Verify that SAP HANA System Replication is enabled on the server where the remoteregisterdb script was running. If necessary, System Replication may be enabled by executing the command 'hdbnsutil -sr_enable —name=<Site Name>' as the SAP HANA administrative user.

136708 ERROR Error getting resource information for $tag on server $me. Exiting $cmd for $tag.

Cause: Failed to obtain information about the given SAP HANA resource on the given server.

Action: Verify that a SAP HANA resource with the given tag exists on the given server.

136709 EMERG LifeKeeper was unable to determine the SAP HANA System Replication mode for database $instance corresponding to resource $tag on server $me. Resource monitoring for $tag will be suspended until the issue is resolved.

Cause: The SAP HANA System Replication mode could not be determined for the given database on the given server.

Action: Inspect the SAP HANA trace files and LifeKeeper log file for more details.

136710 EMERG The replication mode of the SAP HANA database $instance corresponding to resource $tag was modified outside of LifeKeeper and is no longer registered as primary master on server $me. Please bring the SAP HANA resource in-service on the server where the database should be registered as primary master. Resource monitoring for $tag will be suspended until the issue is resolved.

Cause: The SAP HANA System Replication mode for the given database was modified outside of LifeKeeper.

Action: Bring the SAP HANA resource in-service on the server where it should be registered as primary master.

136711 EMERG SAP HANA database $instance corresponding to resource $tag is currently suspended on server $me due to actions performed outside of LifeKeeper. Please take the SAP HANA resource out of service on server $me and bring it in-service on the server where the database should be registered as primary master. Bringing resource $tag back in-service on $me will resume the suspended database. Resource monitoring for $tag will be suspended until the issue is resolved.

Cause: The given SAP HANA database instance has been suspended on the given server due to actions performed outside of LifeKeeper.

Action: If you would like to resume the suspended database on the server where the corresponding LifeKeeper resource is currently in-service (Active), execute the command given in the message. Otherwise, bring the LifeKeeper SAP HANA resource in-service on the intended primary replication site.

Feedback

Thanks for your feedback.

Post your comment on this topic.

Post Comment