Control F を使用して、各カタログの特定のエラーコードを検索します。エラーコードの検索には、画面右上の検索ボックスをご利用ください。
| コード | 重大度 | メッセージ | 原因/処置 |
|---|---|---|---|
| 111000 | ERROR | Usage: primary server was null | |
| 111001 | ERROR | Usage: independent program path was null | |
| 111002 | ERROR | Usage: db_instance was null | |
| 111003 | ERROR | Usage: system_user was null | |
| 111004 | ERROR | Usage: user_key was null | |
| 111005 | ERROR | Usage: tag was null | |
| 111007 | ERROR | END failed hierarchy “create” of resource “$tag” on server “$primarysys” with return value of “$ret” | 原因: LifeKeeper was unable to create the MaxDB resource 処置: Check the cause of the failure and retry operation |
| 111009 | ERROR | A LifeKeeper internal error occurred in utility rlslocks. Retry operation. | 原因: There was an unexpected error running “rlslocks”. 処置: Check the logs for related errors and try to resolve the reported problem. |
| 111010 | ERROR | END failed “create” of “$tag” on server “$primarysys” due to a “$sig” signal | 原因: LifeKeeper was unable to create the resource 処置: Check the logs for related errors and try to resolve the reported problem. |
| 111012 | ERROR | A LifeKeeper internal error occured in utility getlocks. Retry operation. | 原因: There was an unexpected error running “getlocks”. 処置: Check the logs for related errors and try to resolve the reported problem. |
| 111013 | ERROR | A LifeKeeper internal error occurred in utility newid. Retry operation. | 原因: There was an unexpected error running “newid”. 処置: Check the logs for related errors and try to resolve the reported problem. |
| 111025 | ERROR | Unable to create raw resource hierarchy for $tmpdep | 原因: LifeKeeper was unable to create a raw resource hierarchy for the MaxDB dev space dependency 処置: Check the LifeKeeper logs for more information. |
| 111026 | ERROR | The path “$tmpdep” is not on a shared filesystem. | 原因: The MaxDB instance dev spaces should be on a shared filesystem 処置: Ensure the path is on a shared filesystem and retry the create operation. |
| 111027 | ERROR | Unable to create filesystem resource hierarchy for “$tmpdep” | 原因: LifeKeeper was unable to create the filesystem resource 処置: Check the LifeKeeper logs for more information. |
| 111028 | ERROR | Unable to determine the type of the dev space or install path “$tmpdep”. Valid dev space types include file system and/or raw devices. | 原因: The dev space for $tmpdep was not determined to be filesystem or raw 処置: Ensure the path is on a filesystem or raw device |
| 111029 | ERROR | Unable to create resource dependency for parent “$tag” and child “$tmptag” | 原因: LifeKeeper was unable to create a dependency between the given resources 処置: Check the LifeKeeper logs for more information. |
| 111032 | ERROR | Unable to create filesystem resource hierarchy for \”$depres\” | 原因: LifeKeeper was unable to create the filesystem resource 処置: Check the LifeKeeper logs for more information. |
| 111033 | ERROR | Unable to create resource dependency for parent “$tag” and child “$tmptag” | 原因: LifeKeeper was unable to create a dependency between the given resources 処置: Check the LifeKeeper logs for more information. |
| 111035 | ERROR | Cannot extend resource “$templatetag” to server “$targetsys”. | 原因: The given resource cannot be extended to the given server. 処置: Verify that the MaxDB software is properly installed on the target server and that any necessary shared file systems are accessible from the target system. |
| 111036 | ERROR | Usage: canextend <template server> <template tag> | |
| 111037 | ERROR | The values specified for the target and template servers are the same. Please specify the correct values for the target and template servers. | 原因: The values specified for the target and the template servers are the same. 処置: Perform the steps listed in the message text. |
| 111038 | ERROR | Error getting resource information for resource "$templatetag" on server "$templatesys" | 原因: LifeKeeper was unable to find the resource on the given server. 処置: Check your LifeKeeper configuration. |
| 111039 | ERROR | Error getting resource information for resource “$templatetag” on server “$templatesys” | 原因: LifeKeeper was unable to find the resource on the given server. 処置: Check your LifeKeeper configuration. |
| 111040 | ERROR | The SAP DB instance "$sid" is not running on server "$templatesys" | 原因: A process check for the MaxDB instance did not find any processes running. 処置: The MaxDB instance must be started |
| 111044 | ERROR | The SAP DB file "$reg_file" was not found on server "$targetsys". Verify that SAP DB is installed correctly on the specified server. | 原因: The file /etc/opt/sdb could not be found. 処置: Verify that the MaxDB software is properly installed and that all necessary file systems are mounted. |
| 111045 | ERROR | One or more of the SAP DB service file entries do not exist on server "$templatesys" | 原因: None of the MaxDB service ports were found on server $templatesys 処置: Verify that the MaxDB software is properly installed and that all necessary file systems are mounted |
| 111046 | ERROR | One or more of the SAP DB service file entries do not exist on server "$targetsys" | 原因: None of the MaxDB service ports were found on server $templatesys. 処置: Verify that the MaxDB software is properly installed and that all necessary file systems are mounted. |
| 111047 | ERROR | The service file entries are not the same on server "$templatesys" and "$targetsys" | 原因: The MaxDB service ports were not the same on $templatesys and $targetsys 処置: Ensure that the MaxDB software was installed the same on both servers |
| 111048 | ERROR | The user "$sysuser" does not exist on the server "$targetsys" | 原因: User name is not in the /etc/passwd file. 処置: Ensure the user name exists in the /etc/passwd file and retry the operation. |
| 111049 | ERROR | The user id for user "$sysuser" is not the same on server "$templatesys" and "$targetsys". | 原因: The MaxDB OS User ID should be the same on both servers. 処置: Set the MaxDB OS User ID to be the same on both servers. |
| 111050 | ERROR | The group id for user "$sysuser" is not the same on server "$templatesys" and "$targetsys". | 原因: The MaxDB OS User Group ID should be the same on both servers. 処置: Set the MaxDB OS User’s Group ID to be the same on both servers. |
| 111051 | ERROR | Unable to determine the owner of the SAP DB x_server utility on server "$templatesys" or "$targetsys". Verify the owner of the x_server utility exists with a valid login. | 原因: LifeKeeper could not determine the owner of the x_server utility on $templatesys or $targetsys. 処置: Ensure the x_server utility is owned by the user that is registered with LifeKeeper. |
| 111052 | ERROR | The owner of the SAP DB x_server utility is not the same on servers "$templatesys" and "$targetsys". | 原因: The owner of the MaxDB x_server utility should be the same on both systems. 処置: Ensure the owner of the x_server utility is the same on both systems. |
| 111053 | ERROR | The owner of the SAP DB x_server utility, "$o_xowner", does not exist on the server "$targetsys". | 原因: The owner of the MaxDB x_server utility on $templatesys does not exist on the server $targetsys 処置: Ensure the MaxDB OS user exists on both systems. |
| 111054 | ERROR | The user id for user "$o_xowner" is not the same on server "$templatesys" and "$targetsys". | 原因: User ID for the owner of the x_server utility should be the same on both servers. 処置: Set user ID to be the same on both servers. |
| 111055 | ERROR | The group id for user "$o_xowner" is not the same on server "$templatesys" and "$targetsys". | 原因: Group ID for the owner of the x_server utility should be the same on both servers. 処置: Set group ID to be the same on both servers. |
| 111058 | ERROR | No valid scsi/raw or gen/filesys dependents were found for resource "$templatetag" on server "$templatesys". The hierarchy does not contain valid dependents, you must delete and recreate the hierarchy. | 原因: LifeKeeper did not find any valid dependents while checking if the MaxDB resource could be extended 処置: Recreate the MaxDB hierarchy. |
| 111060 | ERROR | Cannot access canextend script "$childscript" on server "$targetsys". | 原因: LifeKeeper was unable to run pre-extend checks because it was unable to find the "/opt/LifeKeeper/lkadm/subsys/database/sapdb/bin/canextend" script on $targetsys. 処置: Check your LifeKeeper installation. |
| 111061 | ERROR | Usage: $cmd $usage \nUsage: template server was null | |
| 111062 | ERROR | Usage: $cmd $usage \nUsage: template tag was null | |
| 111063 | ERROR | Usage: $cmd $usage \nUsage: switchback must be ‘AUTOMATIC’ or ‘INTELLIGENT’ | |
| 111064 | ERROR | Usage: $cmd $usage \nUsage: independent_program_path was null | |
| 111065 | ERROR | Usage: $cmd $usage \nUsage: user_key was null | |
| 111066 | ERROR | Usage: $cmd $usage \nUsage: target tag was null | |
| 111067 | ERROR | Error getting resource information for resource "$templatetag" on server "$templatesys" | 原因: Unable to find information about the given resource on the given server. 処置: Verify that the given resource exists and that all necessary file systems are mounted on the given server. |
| 111068 | ERROR | Resource with either matching tag "$targettag" or id "$targetid" already exists on server "$targetsys" for App "$targetapp" and Type "$targettype" | 原因: A resource with the given resource tag or ID and the same app and type already exists on the given server. 処置: Verify that the MaxDB instance is not already under LifeKeeper protection on the given server. If it is not already protected, choose a different resource tag name. |
| 111069 | ERROR | Error getting resource information for resource "$templatetag" on server "$templatesys" | 原因: Unable to find information about the given resource on the given server. 処置: Verify that the given resource exists and that all necessary file systems are mounted on the given server. |
| 111071 | ERROR | No valid scsi/raw or gen/filesys dependents were found for resource "$templatetag" on server "$templatesys". The hierarchy does not contain valid dependents, you must delete and recreate the hierarchy. | 原因: LifeKeeper did not find any valid dependents while checking if the MaxDB resource could be extended 処置: Recreate the MaxDB hierarchy |
| 111072 | ERROR | Cannot access extend script "$childextend" on server "$targetsys" | 原因: The given extend script does not exist or is not executable on the given server. 処置: Verify that all necessary recovery kits are installed and that the given extend script is executable. |
| 111073 | ERROR | Cannot extend resource "$targettag" to server "$targetsys" | 原因: The given resource cannot be extended to the given server. 処置: Verify that the MaxDB software is properly installed on the target server and that any necessary shared file systems are accessible from the target system. |
| 111074 | ERROR | Usage: $cmd $usage | |
| 111076 | ERROR | parseInfo Usage: $usage | |
| 111077 | ERROR | Error getting resource information for $tag on $sysname, ins_list returned $ret | 原因: Unable to find information about the given resource on the given server. 処置: Verify that the given resource exists and that all necessary file systems are mounted on the given server. |
| 111079 | ERROR | Given program path is not valid $dbpath is not valid | 原因: The path $dbpath is invalid. 処置: Ensure $dbpath exists and retry the operation. |
| 111080 | ERROR | SID missing from arguments, USAGE: $cmd $usage | |
| 111081 | ERROR | Sysuser missing from arguments, USAGE: $cmd $usage | |
| 111082 | ERROR | Xuser missing from arguments, USAGE: $cmd $usage | |
| 111083 | ERROR | Could not start X Server | 原因: LifeKeeper was unable to start the X Server. 処置: Ensure that the x_server utility is available to the MaxDB user and that it can be started manually. |
| 111087 | ERROR | Given program path is not valid $dbpath is not valid. | 原因:The path $dbpath is invalid. 処置: Ensure $dbpath exists and retry the operation. |
| 111088 | ERROR | SID missing from arguments, USAGE: $cmd $usage | |
| 111089 | ERROR | Sysuser missing from arguments, USAGE: $cmd $usage | |
| 111090 | ERROR | Xuser missing from arguments, USAGE: $cmd $usage | |
| 111091 | ERROR | Registry file $reg_file does not exist on $server | 原因:The registry file $reg_file was not found on $server. 処置: Ensure $reg_file exists and retry the operation. |
| 111093 | ERROR | XServer could not be started on $server | 原因:LifeKeeper was unable to start the X Server. 処置: Ensure that the x_server utility is available to the MaxDB user and that it can be started manually. |
| 111094 | ERROR | Unable to start DB $sid on $server | 原因:LifeKeeper was unable to start the DB $sid. 処置: Ensure that DB $sid can be started manually. |
| 111098 | ERROR | XServer could not be started on $server | 原因:LifeKeeper was unable to start the X Server. 処置: Ensure that the x_server utility is available to the MaxDB user and that it can be started manually. |
| 111099 | ERROR | Unable to start DB $sid on $server, retrying… | 原因:LifeKeeper was unable to start the DB $sid and is going to retry the operation. 処置: Allow time for LifeKeeper to try to start the DB $sid again. |
| 111102 | ERROR | Given program path is not valid $dbpath is not valid | 原因:The path $dbpath is invalid. 処置: Ensure $dbpath exists and retry the operation. |
| 111103 | ERROR | SID missing from arguments, USAGE: $cmd $usage | |
| 111104 | ERROR | Sysuser missing from arguments, USAGE: $cmd $usage | |
| 111105 | ERROR | Xuser missing from arguments, USAGE: $cmd $usage | |
| 111110 | ERROR | Given program path is not valid $dbpath is not valid | 原因: The path $dbpath is invalid. 処置: Ensure $dbpath exists and retry the operation. |
| 111111 | ERROR | SID missing from arguments, USAGE: $cmd $usage | |
| 111112 | ERROR | Sysuser missing from arguments, USAGE: $cmd $usage | |
| 111113 | ERROR | Xuser missing from arguments, USAGE: $cmd $usage | |
| 111114 | ERROR | Registry file $reg_file does not exist on $server | 原因: The registry file $reg_file was not found on $server. 処置: Ensure $reg_file exists and retry the operation. |
| 111118 | ERROR | $stop_cmd of DB $sid failed on $server | 原因: LifeKeeper was unable to stop the DB $sid with the command $stop_cmd 処置: Ensure that DB $sid can be stopped manually. |
| 111120 | ERROR | X_server issue detected when running $stop_cmd on $server | 原因: LifeKeeper ran into an issue checking the X_server. 処置: Check for additional errors. |
| 111121 | ERROR | X_server could not be started on $server during the $stop_cmd operation | 原因: LifeKeeper was unable to start the X_Server while trying to stop the DB. 処置: Ensure that the X_server utility is available to the MaxDB user and that it can be started manually. |
| 111131 | ERROR | cleanInstance Usage: $usage | |
| 111136 | ERROR | Unable to kill orphaned processes for database instance $sid on server $me | 原因: There are orphaned processes for the database instance that LifeKeeper was unable to kill. 処置: Manually find and kill any processes related to the old DB instance. |
| 111137 | ERROR | isXserverRunning Usage: $cmd $usage | |
| 111138 | ERROR | isXserverRunning Usage: $cmd $usage | |
| 111141 | ERROR | startXserver Usage: $cmd $usage | |
| 111142 | ERROR | startXserver Usage: $cmd $usage | |
| 111147 | ERROR | Start xserver attempt $try for port $port failed, retrying… | 原因: LifeKeeper was unable to start the xserver and is going to retry the operation. 処置: Allow time for LifeKeeper to try to start the xserver again. |
| 111148 | ERROR | Failed all tries to start xserver for port $port | 原因: LifeKeeper was unable to start the xserver for port $port after exhausting all retries. 処置: Ensure the xserver can be started for port $port on the server. |
| 111150 | ERROR | Unable to start SAPDB x_server on server $server | 原因: LifeKeeper was unable to start the x_server on server $server. 処置: Check logs for any additional errors. |
| 111152 | ERROR | stopXserver usage: $cmd $usage | |
| 111153 | ERROR | stopXserver usage: $cmd $usage | |
| 111156 | ERROR | Unable to stop xserver for port $port, retrying… | 原因: LifeKeeper was unable to stop the xserver and is going to retry the operation. 処置: Allow time for LifeKeeper to try to stop the xserver again. |
| 111157 | ERROR | Failed all tries to stop xserver for port $port | 原因: LifeKeeper was unable to stop the xserver for port $port after exhausting all retries. 処置: Ensure the xserver can be stopped for port $port on the server. |
| 111158 | ERROR | Unable to stop SAPDB x_server on server $server | 原因: LifeKeeper was unable to stop the x_server on server $server. 処置: Check logs for any additional errors. |
| 111160 | ERROR | getVersion Usage: $cmd $usage | |
| 111163 | ERROR | getXserverOwner Usage: $cmd $usage | |
| 111164 | ERROR | Unable to determine owner of SAPDB x_server utility on $sys. Verify the owner of x_server exists with a valid login | 原因: LifeKeeper could not determine the owner of the x_server utility on $sys. 処置: Ensure the x_server utility is owned by the user that is registered with LifeKeeper. |
| 111165 | ERROR | SAPDB Database Management Utilities not found in the specified path $dbpath on server $server | 原因: The dbmcli or x_server utility either could not be found or is not executable. 処置: Verify that the MaxDB software is installed correctly, that all necessary file systems are mounted, and that the dbmcli executable has the proper permissions |
| 111170 | ERROR | SAPDB ARK restore Usage: restore $usage | |
| 111171 | ERROR | The command $cmd with process ID $$ has hung. Forcibly terminating the command $cmd on $sysname | 原因: The MaxDB restore script reached its timeout value. 処置: Check logs for additional errors. |
| 111172 | ERROR | Skipping child process cleanup for hung command $cmd (PID $$). Manual cleanup of processes and the database may be required before you are able to bring the database into an operational state. | 原因: The MAXDB_PID_CLEANUP value in the /etc/default/LifeKeeper file is not set to ‘y’ so LifeKeeper will not automatically clean up any child processes. 処置: No action needed. To change this behavior set MAXDB_PID_CLEANUP=y in the /etc/default/LifeKeeper file. |
| 111177 | ERROR | Error getting Resource Info Field for $tag on $sysname. | 原因: Unable to find information about the given resource on the given server. 処置: Verify that the given resource exists and that all necessary file systems are mounted on the given server. |
| 111178 | ERROR | At least one required value from $tag info field is empty: SID=$sid PATH=$dbpath USER=$sysuser XUSER=$xuser. | 原因: LifeKeeper was unable to get some information for the resource $tag. 処置: This is an internal error. Please submit an issue report to SIOS customer support. |
| 111180 | ERROR | SAPDB ARK remove Usage: remove $usage | |
| 111184 | ERROR | Error getting Resource Info Field for $tag on $sysname | 原因: Unable to find information about the given resource on the given server. 処置: Verify that the given resource exists and that all necessary file systems are mounted on the given server. |
| 111185 | ERROR | At least one required value from $tag info field is empty: SID=$sid PATH=$dbpath USER=$sysuser XUSER=$xuser | 原因: LifeKeeper was unable to get some information for the resource $tag. 処置: This is an internal error. Please submit an issue report to SIOS customer support. |
| 111186 | ERROR | $time $cmd: Script has hung checking \"$tag\". Forcibly terminating | 原因: The MaxDB quickCheck process reached its timeout value. 処置: Check logs for additional errors. |
| 111187 | ERROR | SAPDB ARK quickCheck Usage: quickCheck $usage | |
| 111188 | ERROR | Error getting resource information with tag $tag on system $sysname: Returned $ret | 原因: Unable to find information about the given resource on the given server. 処置: Verify that the given resource exists and that all necessary file systems are mounted on the given server. |
| 111189 | ERROR | Error getting Resource Info Field for $tag on $sysname | 原因: Unable to find information about the given resource on the given server. 処置: Verify that the given resource exists and that all necessary file systems are mounted on the given server. |
| 111193 | ERROR | SAPDB ARK dbfail Usage: dbfail $usage | |
| 111194 | ERROR | Cannot find tag for resource with id $id | 原因: LifeKeeper was unable to find the tag for the resource with id $id. 処置: Verify that the given resource exists and that all necessary file systems are mounted on the given server. |
| 111198 | ERROR | Error getting Resource Info Field for $tag on $sysname | 原因: Unable to find information about the given resource on the given server. 処置: Verify that the given resource exists and that all necessary file systems are mounted on the given server. |
| 111199 | ERROR | At least one required value from $tag info field is empty: SID=$sid PATH=$dbpath USER=$sysuser XUSER=$xuser | 原因: LifeKeeper was unable to get some information for the resource $tag. 処置: This is an internal error. Please submit an issue report to SIOS customer support. |
| 111200 | ERROR | SAPDB ARK delete Usage: delete $usage | |
| 111203 | ERROR | Start xserver attempt $try for port $port failed | 原因: LifeKeeper was unable to start the xserver after trying $try times. 処置: Ensure the xserver can be started for port $port on the server. |
| 111204 | ERROR | Unable to stop xserver for port $port | 原因: LifeKeeper was unable to stop the xserver for port $port after exhausting all retries. 処置: Ensure the xserver can be stopped for port $port on the server. |
このトピックへフィードバック