6.4 Messages

This section explains the messages that are output by PFM - RM for Virtual Machine and the action to be taken by the user. The list of PFM - RM for Virtual Machine messages follows.

• KAVL20000-I

  Remote Monitor Collector has stopped. (host=<host-name>, service=<service-ID>)

  The Remote Monitor Collector service terminated normally.

  (S)

  Terminates processing of the Remote Monitor Collector service.

• KAVL20001-E

  Remote Monitor Collector failed to start.

  The Remote Monitor Collector service failed to start.

  (S)

  Terminates processing of the Remote Monitor Collector service.

  (O)

  Check the previous message that was output to the common message log, and take the action indicated in that message.

• KAVL20002-I

  Remote Monitor Collector started. (host=<host-name>, service=<service-ID>)

  Startup of the Remote Monitor Collector service is complete.

  (S)

  Starts the performance data collection process of the Remote Monitor Collector service.

• KAVL20004-E

  An attempt to read the service startup information file has failed.

  During startup processing of the Remote Monitor Collector service, the service startup initialization file could not be loaded.

  (S)

  Terminates processing of the Remote Monitor Collector service.

  (O)

  If this message is output repeatedly, delete the instance environment and then re-create the instance. If the cause cannot be determined, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20005-E

  Remote Monitor Collector will now stop because an error occurred.

  The Remote Monitor Collector service is about to stop because an error has occurred.

  (S)

  Terminates processing of the Remote Monitor Collector service.

  (O)

  Check the previous message that was output to the common message log, and take the action indicated in that message. If the cause cannot be determined, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20006-E

  Memory allocation failed.

  Memory allocation failed.

  (S)

  Terminates processing of the Remote Monitor Collector service.

  (O)

  Increase the amount of free memory.

• KAVL20007-W

  Memory allocation failed. (RecordType=<record-type>)

  Memory allocation failed. If UNKNOWN is output in record-type, this means that memory allocation failed for multiple record IDs.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Increase the amount of free memory.

• KAVL20008-W

  An attempt to collect the record failed. (Instance=<instance-name>, Target=<monitoring-target-name>, RecordType=<record-type>)

  The record indicated by record-type could not be collected.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20009-W

  An invalid value or a value outside the range was specified for the property of the Remote Monitor Collector service. (Instance=<instance-name>, Target=<monitoring-target-name>, property=<property-name>, value=<range-value>)

  An invalid value or a value outside the range was specified for a property of the Remote Monitor Collector service.

  (S)

  Invalidates the specified value and continues processing of the Remote Monitor Collector service. The item value remains unchanged.

  (O)

  Check whether the value that is specified is acceptable. If not, specify an appropriate value.

• KAVL20010-E

  An error occurred in the function. (function=<function-name>, en=<error-code>, arg1=<argument-1>, arg2=<argument-2>, arg3=<argument-3>)

  An error occurred during execution of the function indicated by function-name.

  (S)

  Terminates processing of the Remote Monitor Collector service.

  (O)

  Collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20011-W

  The collector process failed to start.

  A collection process failed to start.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20013-W

  A performance data file is invalid. (Instance=<instance-name>, Target=<monitoring-target-name>)

  The content of a performance data storage file is invalid.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20014-W

  A collector process was forcefully terminated because performance data collection did not end in the specified period of time. (Instance=<instance-name>, Target=<monitoring-target-name>)

  A collection process was forcibly terminated because performance data collection did not end within the specified period of time.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Check the following items:

  • Whether the monitoring-target host has started

  • Whether the connection settings on the virtualization system side are correct

  • Whether the PFM - RM host and the virtualization system are in a temporary high load state

  • Whether the following settings (specified during setup of the monitoring target) are correct

    If the monitoring target uses VMware:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether a certificate has been installed (if Security = 1)

    - Whether the Port value is correct

    - Whether the UserID and Password values are correct

    - Set Security = 1, and if the default certificate of VMware is used, confirm whether the Update Root Certificate functions affect the operation. For details, see 2.5.1 For VMware.

    If the monitoring target uses Hyper-V:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether the WMI service has started on the monitoring-target host

    - Whether the WMI connection setup procedure has been performed correctly

    - Whether the UserID, Password, and Domain values are correct

    If the monitoring target uses KVM:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether the SSH server is started on the monitoring-target host

    - Whether the SSH connection setup procedure has been performed correctly

    - Whether the Port value is correct

    - Whether the UserID and Private_Key_File values are correct

  If the cause cannot be determined, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20015-I

  The records were successfully saved onto the Store database. (Instance=<instance-name>, RecordType=<record-type>, count=<record-count>)

  The process of saving the record(s) indicated by record-type in the Store database is complete.

  (S)

  Continues processing of the Remote Monitor Collector service.

• KAVL20016-W

  The initialization of interprocess communication failed. (Instance=<instance-name>)

  Initialization of communications between the Remote Monitor Collector service and a collection process failed.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Opening of or writing to a work file may have failed. Check to make sure that there is no disk space shortage.

  If disk space is not a problem, collect maintenance data and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20017-W

  An error occurred during collection of the record. (Instance=<instance-name>, Target=<monitoring-target-name>)

  An error occurred during collection of the record.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20018-W

  Account authentication failed. (Instance=<instance-name>)

  Account authentication failed.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Check whether the following items that were specified during setup of the instance environment are correct:

  • HostUserID

  • HostPassword

  • HostDomain

• KAVL20201-W

  The system could not connect to the monitored virtual environment. (Instance=<instance-name>, Target=<monitoring-target-name>, datetime=<date-time>, message=<message>)

  The system could not connect to the monitored virtual environment.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Check the following items:

  • Whether the monitoring-target host has started

  • Whether the connection settings on the virtualization system side are correct

  • Whether the PFM - RM host and the virtualization system are in a temporary high load state

  • (If there is a firewall between PFM - RM for Virtual Machine and the monitoring-target host) Whether the ports used for communication are properly set in the firewall

  • Whether the following settings (specified during setup of the monitoring target) are correct

    If the monitoring target uses VMware:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether a certificate has been installed (if Security = 1)

    - Whether the Port value is correct

    - Whether the UserID and Password values are correct

    If the monitoring target uses Hyper-V:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether the WMI service has started on the monitoring-target host

    - Whether the WMI connection setup procedure has been performed correctly

    - Whether the UserID, Password, and Domain values are correct

    If the monitoring target uses KVM:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether the SSH server is started on the monitoring-target host

    - Whether the SSH connection setup procedure has been performed correctly

    - Whether the Port value is correct

    - Whether the UserID and Private_Key_File values are correct

  If the cause cannot be determined, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20202-W

  An attempt to authenticate the monitored virtual environment has failed. (Instance=<instance-name>, Target=<monitoring-target-name>, datetime=<date-time>, message=<message>)

  The monitored virtual environment could not be authenticated.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Make sure that the host of the virtual environment is active. Furthermore, make sure that the following items, which were specified during setup of the monitoring-target, are correct:

  • UserID

  • Password

• KAVL20203-W

  Initialization of the collector process log file failed. (Instance=<instance-name>, Target=<monitoring-target-name>, datetime=<date-time>, message=<message>)

  Initialization of a collection process log failed.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Opening of or writing to a work file may have failed. Check to make sure there is no disk space shortage.

  If disk space is not a problem, collect maintenance data and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20204-W

  Initialization of the collector process failed. (Instance=<instance-name>, Target=<monitoring-target-name>, datetime=<date-time>, message=<message>)

  Initialization of a collection process failed.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20205-W

  A certificate is not installed or a certificate is not correct. (Instance=<instance-name>, Target=<monitoring-target-name>, datetime=<date-time>, message=<message>)

  No certificate is installed or an incorrect certificate is installed.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Install a CA-signed certificate.

  If the problem is not resolved even after a CA-signed certificate is installed, check the following items in the installed certificate:

  • Effective period

  • Issuing destination (whether it is the same as the host name)

  • Validity of the certificate (has verification been completed successfully?)

  If there is a problem with the certificate, re-create a certificate and then re-install it. For details about how to create a certificate, see the VMware documentation.

  If the default certificate of VMware is used for operation, ignore this message.

  For details about a certificate, see 2.5.1 For VMware.

• KAVL20300-W

  It failed to occur JP1 system event or Agent event.

  A JP1 system event or agent event could not be issued.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Collect maintenance data and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20301-W

  It failed to issue JP1 system event or Agent event, because Memory is insufficient.

  A JP1 system event or agent event could not be issued.

  (S)

  Continues processing of the Remote Monitor Collector.

  (O)

  Increase the amount of free memory.

• KAVL20400-I

  The instance was successfully transitioned. (<PFM-Agent-for-Virtual-Machine-instance-name>-><PFM-RM-for-Virtual-Machine-instance-name> / <PFM-RM-for-Virtual-Machine-target-name>)

  Migration terminated normally.

  (S)

  Terminates migration.

• KAVL20401-I

  If you are changing location of the performance data, JP1 Event and PFM service automatic restart in the source environment, please review the target environment.

  Migration terminated normally. If the performance data storage location, JP1 event, and PFM service automatic restart settings have been changed from the default settings in the migration source environment, review these settings in the destination environment.

  (S)

  Terminates migration.

• KAVL20402-I

  If you set the some targets to one instance, please review the value of 'Collection Interval'.

  If you set multiple monitoring targets for one instance, review the value of the Collection Interval property.

  (S)

  Terminates migration.

• KAVL20403-I

  Start the migration process.

  Migration started.

  (S)

  Performs migration.

• KAVL20404-I

  Be calculating of the size of post-migration Store database (<PFM-Agent-for-Virtual-Machine-instance-name>-><PFM-RM-for-Virtual-Machine-instance-name>)

  The command is calculating the size that the Store database will have after migration.

  (S)

  The command is calculating the size that the Store database will be after migration.

• KAVL20405-I

  You can do the migration because the specified instance is a new one.

  Migration is possible because the specified PFM - RM for Virtual Machine instance is a new instance.

  (S)

  Stops calculating the size that the Store database will be after migration.

• KAVL20406-I

  Finished to calculate size of the Store database. You can do the migration because Store database capacity after migration is less than maximum migration capacity.

  Calculation of the size that the Store database will be after migration finished. Migration is possible because the calculated size does not exceed the upper limit.

  (S)

  Terminates calculating the size of post-migration Store database.

• KAVL20407-I

  Finished to calculate size of the Store database. You cannot do the migration because Store database capacity after migration is more than maximum migration capacity. As destination, please specify a new instance or another instance with spare Store database.

  Calculation of the size of that the Store database will be after migration finished. Migration is impossible because the calculated size exceeds the upper limit. Specify a new instance as the migration destination, or another instance whose Store database has sufficient free space.

  (S)

  Terminates calculating the size of post-migration Store database.

  (O)

  Specify a new instance as the migration destination, or another instance whose Store database has sufficient free space.

• KAVL20409-E

  The migration operation failed, because the error occurred.

  Migration failed due to an error.

  (S)

  Stops command execution.

  (O)

  Check the error details, and then re-execute the command.

• KAVL20410-E

  Specified arguments are incorrect.

  Invalid arguments are specified.

  (S)

  Stops command execution.

  (O)

  Review the format of the command line, and then re-execute the command.

• KAVL20411-E

  The instance name specified by the -rminst option is incorrect.

  The PFM - RM for Virtual Machine instance name specified by the -rminst option is incorrect.

  (S)

  Stops command execution.

  (O)

  Make sure that, for the -rminst option, you specify a PFM - RM for Virtual Machine instance name that is 1 through 32 bytes long and consists of single-byte alphanumeric characters.

• KAVL20412-E

  The target name specified by the -target option is incorrect.

  The PFM - RM for Virtual Machine target name specified by the -target option is incorrect.

  (S)

  Stops command execution.

  (O)

  Make sure that, for the -target option, you specify a PFM - RM for Virtual Machine target name that is 1 through 32 bytes long and consists of single-byte alphanumeric characters and/or hyphens (-). You cannot specify a string that begins with a hyphen (-) or the string ALL.

• KAVL20413-E

  The logical hostname specified by the -aolhost option is incorrect.

  The PFM - Agent for Virtual Machine logical host name specified by the -aolhost option is incorrect.

  (S)

  Stops command execution.

  (O)

  Make sure that, for the -aolhost option, you specify a PFM - Agent for Virtual Machine logical host name that is 1 through 32 bytes long and consists of single-byte alphanumeric characters without spaces or periods (.). You cannot specify the string localhost, an IP address, or a host name that begins with a hyphen (-).

• KAVL20414-E

  The logical hostname specified by the -rmlhost option is incorrect.

  The PFM - RM for Virtual Machine logical host name specified by the -rmlhost option is incorrect.

  (S)

  Stops command execution.

  (O)

  Make sure that, for the -rmlhost option, you specify a PFM - RM for Virtual Machine logical host name that is 1 through 32 bytes long and consists of single-byte alphanumeric characters without spaces or periods (.). You cannot specify the string localhost, an IP address, or a host name that begins with a hyphen (-).

• KAVL20415-E

  You do not have permission to execute the command.

  You do not have permission to execute the migration command.

  (S)

  Stops command execution.

  (O)

  Execute the command as a member of the Administrators group.

• KAVL20416-E

  The specified PFM - Agent for Virtual Machine service is running.

  The service of the specified PFM - Agent for Virtual Machine instance is running.

  (S)

  Stops command execution.

  (O)

  Stop the service of the migration-source PFM - Agent for Virtual Machine instance.

• KAVL20417-E

  PFM - Agent for Virtual Machine service or PFM - RM for Virtual Machine service is not installed or is not set up.

  The PFM - Agent for Virtual Machine service or the PFM - RM for Virtual Machine service has not been installed or set up.

  (S)

  Stops command execution.

  (O)

  Make sure that the PFM - Agent for Virtual Machine service or the PFM - RM for Virtual Machine service has been installed and set up.

• KAVL20418-E

  The PFM - Manager environment is invalid.

  The PFM - Manager environment is invalid.

  (S)

  Stops command execution.

  (O)

  Collect the information about PFM - Manager, and then contact the system administrator or the support service.

• KAVL20419-E

  Specified logical hostname is not set up. (lhost=<logical-host-name>)

  The specified logical host has not been set up.

  (S)

  Stops command execution.

  (O)

  The logical host name specified by the -aolhost or -rmlhost option is incorrect. Alternatively, the specified logical host has not been set up. If the -rmlhost option is omitted, the logical host name specified by the -aolhost option is used. When you re-execute the command, make sure that you specify a correct logical host name.

• KAVL20421-E

  An attempt to notify to Remote Monitor service was failed. (inst=<instance-name>)

  An attempt to notify the Remote Monitor service that a monitoring target was created failed. It might take time for the changes to be applied to the Remote Monitor service.

  (S)

  Stops command execution.

  (O)

  Confirm that the changes have been applied by checking the properties of the Remote Monitor service of the relevant instance from PFM - Web Console.

• KAVL20422-E

  The number of monitoring targets had already reached the maximum limit. (inst=<instance-name>)

  The number of monitoring targets that have been set in the instance has already reached the maximum.

  (S)

  Stops command execution.

  (O)

  Delete unnecessary monitoring targets from the instance or specify another instance as the migration destination. Then, re-execute the command.

• KAVL20423-E

  Memory is insufficient.

  Memory could not be secured because available memory was insufficient.

  (S)

  Stops command execution.

  (O)

  Terminate any unnecessary applications or increase the amount of memory.

• KAVL20424-E

  The disk capacity is insufficient.

  File access failed because the amount of free disk space was insufficient.

  (S)

  Stops command execution.

  (O)

  Delete unnecessary files or increase the disk capacity.

• KAVL20425-E

  An attempt to access the file failed. (file=<file-name>)

  An attempt to access the specified file failed.

  (S)

  Stops command execution.

  (O)

  Remove the cause of the error, and then re-execute the command. Possible causes are as follows:

  • Memory is insufficient.

  • Disk space is insufficient.

  • Permission to access files or directories is insufficient.

  • A conflict occurred when an attempt was made to access a file (for example, a database file).

  • Files such as database files are corrupted.

  If this error occurs again after the cause of the error is removed, collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20426-E

  An internal command cannot be executed. (<command-line>)

  A command internally called by the migration command could not be executed. There are problems with the system environment.

  (S)

  Stops command execution.

  (O)

  Make sure that the executable file of the command indicated by command-line exists and that you have permission to execute the command. Report the string indicated by command-line to the system administrator or the support service.

• KAVL20427-E

  An attempt to register a Windows service failed.

  An unexpected error occurred while a Windows service was being registered. This error might occur if there are inconsistencies with the status of that service or if there are not sufficient resources.

  (S)

  Stops command execution.

  (O)

  Restart the system, and then re-execute the command. If the same error occurs again, the system might be corrupted. Collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20428-E

  The specified instance of PFM - Agent for Virtual Machine does not exist. (<instance-name>)

  The specified PFM - Agent for Virtual Machine instance does not exist.

  (S)

  Stops command execution.

  (O)

  Review the name of the PFM - Agent for Virtual Machine instance, and then re-execute the command.

• KAVL20429-E

  The specified instance of PFM - RM for Virtual Machine does not exist. (<instance-name>)

  The specified PFM - RM for Virtual Machine instance does not exist.

  (S)

  Stops command execution.

  (O)

  Review the name of the PFM - RM for Virtual Machine instance, and then re-execute the command. If you want to create a new PFM - RM for Virtual Machine instance, do not specify the -targetadd option.

• KAVL20430-E

  An instance of PFM - RM for Virtual Machine with the specified name already exists. (<instance-name>)

  The specified PFM - RM for Virtual Machine instance already exists.

  (S)

  Stops command execution.

  (O)

  Review the name of the PFM - RM for Virtual Machine instance, and then re-execute the command. If you want to perform migration to an existing PFM - RM for Virtual Machine instance, specify the -targetadd option.

• KAVL20431-E

  The instance of PFM - Agent for Virtual Machine and PFM - RM for Virtual Machine specified are different. (<VM_Type>)

  Different values are specified for the VM_Type properties of the specified instances of PFM - Agent for Virtual Machine and PFM - RM for Virtual Machine.

  (S)

  Stops command execution.

  (O)

  Make sure that you specify migration sources and destination instances whose VM_Type properties are set to the same value. Alternatively, create a new instance without specifying the -targetadd option.

• KAVL20432-E

  The -targethost option is omitted and the value of 'VM_Host' of the instance specified by the -aoinst option is not 1 to 32 bytes of character, or alphanumeric and '-'.

  The -targethost option is not specified. In addition, the VM_Host value of the instance specified by the -aoinst option is not 1 through 32 bytes long or includes characters that are not single-byte alphanumeric characters or hyphens (-).

  (S)

  Stops command execution.

  (O)

  Specify a new monitoring target name for the -targethost option.

• KAVL20433-E

  The specified target of PFM - RM for Virtual Machine does not exist. (instance=<instance-name>, target=<monitoring-target-name>)

  The specified monitoring target of the PFM - RM for Virtual Machine instance does not exist.

  (S)

  Stops command execution.

  (O)

  Check the names of the monitoring targets set up in the PFM - RM for Virtual Machine instance, and then re-execute the command.

• KAVL20434-E

  A target of PFM - RM for Virtual Machine with the specified name already exists. (instance=<instance-name>, target=<monitoring-target-name>)

  The specified monitoring target of the PFM - RM for Virtual Machine instance already exists.

  (S)

  Stops command execution.

  (O)

  Re-execute the command by specifying the name of a monitoring target that has not been set up in the PFM - RM for Virtual Machine instance.

• KAVL20435-E

  The specified PFM - Agent for Virtual Machine is not 09-01 or later versions. (version=<version>)

  The version of the PFM - Agent for Virtual Machine instance is not 09-01 or later.

  (S)

  Stops command execution.

  (O)

  Update PFM - Agent for Virtual Machine to version 09-01 or later.

• KAVL20436-E

  The Store version of the specified instance is not 2.0 or the data model version is not 4.0.

  The Store version of the specified PFM - Agent for Virtual Machine instance environment is not 2.0. Alternatively, the data model version is not 4.0.

  (S)

  Stops command execution.

  (O)

  Convert the PFM - Agent for Virtual Machine instance environment. The data model version of any instance environment created with PFM - Agent for Virtual Machine 09-00 or earlier is 3.0. To convert the data model version to 4.0, use the jpctool db dmconvert command. To update the Store database version to 2.0, use the jpcconf db vrset command.

• KAVL20437-E

  The capacity of the specified Store database of the PFM - RM for Virtual Machine exceeds the maximum migration capacity.

  The size that the Store database of the specified PFM - RM for Virtual Machine instance will be after migration exceeds the maximum size.

  (S)

  Stops command execution.

  (O)

  Specify a new instance as the migration destination, or another instance whose Store database has sufficient free space.

• KAVL20438-E

  The specified backup path of PFM - Agent for Virtual Machine does not exist.

  The specified backup directory of the Store database of PFM - Agent for Virtual Machine does not exist.

  (S)

  Stops command execution.

  (O)

  Make sure that you specify the correct path for the backup directory of the Store database of PFM - Agent for Virtual Machine.

• KAVL20439-E

  The specified backup path of PFM - RM for Virtual Machine does not exist.

  The specified backup directory of the Store database of PFM - RM for Virtual Machine does not exist.

  (S)

  Stops command execution.

  (O)

  Make sure that you specify the correct path for the backup directory of the Store database of PFM - RM for Virtual Machine.

• KAVL20440-E

  The specified backup path of PFM - RM for Virtual Machine is not empty.

  The specified backup directory of the Store database of PFM - RM for Virtual Machine is not empty.

  (S)

  Stops command execution.

  (O)

  Make sure that you specify an empty directory as the backup directory for the Store database of PFM - RM for Virtual Machine.

• KAVL20441-E

  The analysis of the migration files failed, because the error occurred.

  The files to be migrated could not be analyzed due to an error.

  (S)

  Stops command execution.

  (O)

  Remove the cause of the error, and then re-execute the command. Possible causes of the file migration error are as follows:

  • Memory is insufficient.

  • The migration destination does not have sufficient free disk space.

  • Permission to access files or directories is insufficient.

  • Contention occurred when an attempt was made to access a file (for example, a database file).

  • Files such as database files are corrupted.

  If this error occurs again after the cause of the error is removed, collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20443-E

  An unexpected exception has occurred. (rc=<maintenance-code>)

  An unexpected error occurred.

  (S)

  Stops command execution.

  (O)

  Wait a while, and then re-execute the migration command. If this error occurs again, collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20444-E

  The host name specified by the -targethost option is incorrect.

  The monitoring-target host name specified by the -targethost option is incorrect.

  (S)

  Stops command execution.

  (O)

  Make sure that the name of the PFM - RM for Virtual Machine monitoring target you specify for the -targethost option is 1 through 32 bytes long and consists of only single-byte alphanumeric characters and/or hyphens (-). You cannot specify a name that begins with a hyphen (-).

• KAVL20445-I

  If the instance is created in the destination, please delete the instance.

  Migration failed due to an error. If the instance was created at the migration destination, delete the instance.

  (S)

  Stops command execution.

  (O)

  If the PFM - RM for Virtual Machine instance was created, delete it.

• KAVL20446-I

  Start to restore the Store database of the specified PFM - RM for Virtual Machine.

  Restoration of the Store database of the specified PFM - RM for Virtual Machine instance started.

  (S)

  Restores the Store database of the specified PFM - RM for Virtual Machine instance.

• KAVL20447-I

  End to restore the Store database of the specified PFM - RM for Virtual Machine.

  Restoration of the Store database of the specified PFM - RM for Virtual Machine instance was completed.

• KAVL20448-E

  Failed to restore the Store database of the specified PFM - RM for Virtual Machine.

  Restoration of the Store database of the specified PFM - RM for Virtual Machine instance failed.

  (S)

  Stops command execution.

  (O)

  The Store database of PFM - RM for Virtual Machine might be in an incorrect state. Collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20449-I

  Start to backup the Store database of the specified PFM - RM for Virtual Machine.

  Backup processing of the Store database of the specified PFM - RM for Virtual Machine instance started.

  (S)

  Backs up the Store database of the specified PFM - RM for Virtual Machine instance.

• KAVL20450-I

  End to backup the Store database of the specified PFM - RM for Virtual Machine.

  Backup processing of the Store database of the specified PFM - RM for Virtual Machine instance was completed.

• KAVL20451-E

  Failed to backup the Store database of the specified PFM - RM for Virtual Machine.

  Backup processing of the Store database of the specified PFM - RM for Virtual Machine instance failed.

  (S)

  Stops command execution.

  (O)

  Remove the cause of the error, and then re-execute the command. Possible causes of the Store database backup error are as follows:

  • The migration destination does not have sufficient free disk space.

  • Permission to access files or directories is insufficient.

  • A conflict occurred when an attempt was made to access a file (for example, a database file).

  • Files such as database files are corrupted.

  If this error occurs again after removing the cause, collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20452-I

  Start to migrate the Store database.

  Migration of a Store database started.

  (S)

  Migrates a Store database.

• KAVL20453-I

  End to migrate the Store database.

  Migration of a Store database was completed.

• KAVL20462-E

  The specified dictionary file was not found. (dict=<dictionary-file-name>)

  The specified dictionary file does not exist.

  (S)

  Stops command execution.

  (O)

  There are problems with the PFM - Agent for Virtual Machine or PFM - RM for Virtual Machine environment. Collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20463-E

  The specified dictionary file is invalid. (dict=<dictionary-file-name>, line=<line-number>, errmsg=<message>)

  The contents of the dictionary file are incorrect.

  (S)

  Stops command execution.

  (O)

  There are problems with the PFM - Agent for Virtual Machine or PFM - RM for Virtual Machine environment. Collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20464-E

  A datatype cannot be converted. (dict=<dictionary-file-name>, line=<line-number>)

  The data type cannot be converted.

  (S)

  Stops command execution.

  (O)

  There are problems with the PFM - Agent for Virtual Machine or PFM - RM for Virtual Machine environment. Collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20465-E

  A rule cannot be converted. (dict=<dictionary-file-name>, line=<line-number>)

  Consolidation rules cannot be converted.

  (S)

  Stops command execution.

  (O)

  There are problems with the PFM - Agent for Virtual Machine or PFM - RM for Virtual Machine environment. Collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20466-E

  The specified directory was not found. (dir=<directory>)

  The specified directory does not exist.

  (S)

  Stops command execution.

  (O)

  Check whether the indicated directory can be created. If it cannot be created, remove the cause of the obstacle, and then re-execute the command.

• KAVL20467-E

  The specified Store database is invalid. (db=<database>, errmsg=<message>)

  The contents of the Store database are incorrect.

  (S)

  Stops command execution.

  (O)

  There are problems with the PFM - Agent for Virtual Machine or PFM - RM for Virtual Machine environment. Collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20468-E

  The Store database directory cannot be specified as the work directory. (wkdir=<work-directory>, stdir=<database-directory>)

  The Store database directory cannot be specified as the work directory.

  (S)

  Stops command execution.

  (O)

  Check whether the work directory is a symbolic link to the database directory. If so, delete the symbolic link, and then re-execute the command.

• KAVL20471-E

  An attempt to access a file failed. (file=<file-name>, api=<API-name>, en=<error-code>, errmsg=<message>)

  An attempt to access the specified file failed.

  (S)

  Stops command execution.

  (O)

  Check whether you can access the file. If you cannot, remove the cause of the obstacle, and then re-execute the command.

• KAVL20472-E

  An attempt to access a directory failed. (dir=<directory-name>, api=<API-name>, en=<error-code>, errmsg=<message>)

  An attempt to access the specified directory failed.

  (S)

  Stops command execution.

  (O)

  Check whether you can access the directory. If you cannot, remove the cause of the obstacle, and then re-execute the command.

• KAVL20473-E

  The system environment is incorrect. (rc=<maintenance-code>)

  There are problems with the system environment. Necessary system files have been deleted or access permission settings have been changed.

  (S)

  Stops command execution.

  (O)

  If this message is output during command execution, see the message that was output before this one in the common message log. If no message was output before this one, re-install Performance Management.

• KAVL20474-E

  An attempt to access a file or directory (<path>) failed.

  When a general access operation (for example, a create, delete, read, or write operation) was attempted, an error that was not due to insufficient free disk space occurred. Possible causes of this error are as follows:

  • Access permission was insufficient.

  • The file system was unmounted.

  • The specified path was a directory path rather than a file path.

  (S)

  Stops command execution.

  (O)

  Check the status of the file at the indicated path, remove the cause of the error, and then re-execute the command.

  If the specified path is a directory path, files with names that begin with PFM might remain after occurrence of the error. Change the access permission settings, and then delete the files with names that begin with PFM.

• KAVL20475-E

  Conversion of a database has failed. (db=<database-name>)

  Processing stops because the target database could not be converted.

  (S)

  Stops command execution.

  (O)

  Remove the cause of the error, and then re-execute the command. Possible causes of the file migration error are as follows:

  • Memory is insufficient.

  • The migration destination does not have sufficient free disk space.

  • Permission to access files or directories is insufficient.

  • Contention occurred when an attempt was made to access a file (for example, a database file).

  • Files such as database files are corrupted.

  • An attempt was made to create a monitoring target with the same name as the monitoring target deleted by using the jpcconf target unsetup command.

  See the notes on using the migration command in the chapter on the migration command in the manual.

  If this error occurs again after the cause of the error is removed, collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20477-I

  Start to check the store DB size. (Number of files=<file-number>)

  Size checking starts.

  (S)

  Checks the size that the database will have.

• KAVL20478-I

  End to check the store DB size.

  Size checking was completed.

  (S)

  Size checking was completed.

• KAVL20479-E

  An error has occurred during the migration of the Store database.

  An error occurred during migration of the Store database.

  (S)

  Stops command execution.

  (O)

  Remove the cause of the error, and then re-execute the command. Possible causes of the file migration error are as follows:

  • Memory is insufficient.

  • The migration destination does not have sufficient free disk space.

  • Permission to access files or directories is insufficient.

  • Contention occurred when an attempt was made to access a file (for example, a database file).

  • Files such as database files are corrupted.

  • An attempt was made to create a monitoring target with the same name as the monitoring target deleted by using the jpcconf target unsetup command.

  See the notes on using the migration command in the chapter on the migration command in the manual.

  If this error occurs again after the cause of the error is removed, collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20480-W

  The migration process was cancelled.

  Migration was canceled by a user.

  (S)

  Stops command execution.

  (O)

  Delete the instance or monitoring target that was created at the destination, and then re-execute the command.

• KAVL20481-E

  The instance name specified by the -aoinst option is incorrect.

  The PFM - Agent for Virtual Machine instance name specified by the -aoinst option is incorrect.

  (S)

  Stops command execution.

  (O)

  Make sure that the PFM - Agent for Virtual Machine instance name specified by the -aoinst option is 1 through 32 bytes long and consists of only single-byte alphanumeric characters.

• KAVL20482-E

  The backup path specified by the -aobkpath option is incorrect.

  The backup directory name specified by the -aobkpath option is incorrect.

  (S)

  Stops command execution.

  (O)

  Make sure that the backup directory name specified by the -aobkpath option is 1 through 214 bytes long.

• KAVL20483-E

  The backup path specified by the -rmbkpath option is incorrect.

  The backup directory name specified by the -rmbkpath option is incorrect.

  (S)

  Stops command execution.

  (O)

  Make sure that the backup directory name specified by the -rmbkpath option is 1 through 214 bytes long.

• KAVL20484-I

  If the target is created in the destination, please delete the target.

  Migration failed due to an error. If the monitoring target has been created at the destination, delete the monitoring target.

  (S)

  Stops command execution.

  (O)

  If the monitoring target has been created at the migration-destination PFM - RM for Virtual Machine instance, delete the monitoring target.

• KAVL20485-E

  The specified PFM - RM for Virtual Machine service is running.

  The service of the specified PFM - RM for Virtual Machine instance is running.

  (S)

  Stops command execution.

  (O)

  Stop the service of the migration-destination PFM - RM for Virtual Machine instance.

• KAVL20486-I

  Start to analyze the migration files. (Number of files=<file-number>)

  Analysis of the files to be migrated started.

  (S)

  Analyzes the files to be migrated.

• KAVL20487-I

  End to analyze the migration files.

  Analysis of the files to be migrated ended.

  (S)

  Analysis of the files to be migrated ended.

• KAVL20488-E

  An error has occurred in the internal command. (cmd=<command-line>, rc=<maintenance-code>)

  A command internally called from the migration command could not be executed. Check whether the called command is currently being executed by another command.

  (S)

  Stops command execution.

  (O)

  When you execute the migration command, make sure that other commands, such as jpcconf, jpcctrl, jpcspm, jpcstart, and jpcstop, are not running.

• KAVL20505-E

  An attempt to read the target information file has failed. (Target=<monitoring-target-name>)

  The monitoring target information file could not be loaded while the Remote Monitor Collector service was being started.

  (S)

  Stops the Remote Monitor Collector service.

  (O)

  Delete the relevant monitoring target, and then re-create it.

• KAVL20513-W

  The collector process failed to start.

  The collection process could not be started.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Collect maintenance data, and then contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20516-W

  Performance data was not saved to the Store database because it is the same as previous performance data. (Instance=<instance-name>, Target=<monitoring-target-name>, RecordType=<record-type>)

  Performance data was not saved in the Store database because the data was the same as the previously collected data.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Make sure that the collection process execution interval does not exceed the record collection interval.

  If this problem frequently occurs when the collection process execution interval does not exceed the record collection interval, increase the value of the record collection interval or decrease the number of hosts monitored in the instance environment.

• KAVL20517-W

  The record build failed because there is no performance data. (Instance=<instance-name>, Target=<monitoring-target-name>)

  An attempt to build records failed because there was no performance data.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  This alert might occur immediately after startup because no performance data has been collected.

  If this alert continues to occur after the first collection finishes, check the following items:

  • Whether the monitoring-target host has started

  • Whether the following settings (specified during setup of the monitoring target) are correct

    If the monitoring target uses VMware:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether a certificate has been installed (if Security = 1)

    - Whether the Port value is correct

    - Whether the UserID and Password values are correct

    If the monitoring target uses Hyper-V:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether the WMI service is started on the monitoring-target host

    - Whether the WMI connection setup procedure has been performed correctly

    - Whether the UserID, Password, and Domain values are correct

    If the monitoring target uses KVM:

    - Whether the host name (specified for Target Host and VM_Host) can resolve to an IP address

    - Whether the SSH server is started on the monitoring-target host

    - Whether the SSH connection setup procedure has been performed correctly

    - Whether the Port value is correct

    - Whether the UserID and Private_Key_File values are correct

    - Whether the SSH_Client value specified during instance setup is correct

  If the cause cannot be determined, collect maintenance data and contact the system administrator. For details about how to collect maintenance data, see the chapter that explains troubleshooting in the Job Management Partner 1/Performance Management User's Guide.

• KAVL20521-I

  A collector process will restart because the system detected that it stopped. (Instance=<instance-name>)

  The collection process will be restarted because its stoppage was detected.

  (S)

  Continues processing of the Remote Monitor Collector service.

• KAVL20524-W

  There are no SSH client execution modules. (Instance=<instance-name>)

  The value set as the SSH client execution module (SSH_Client) is incorrect. Make sure that you specify a correct value when monitoring KVM.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Check whether the value of the following property that was set during setup of the instance environment is correct:

  • SSH_Client

• KAVL20526-W

  There are no private keys. (Instance=<instance-name>, Target=<monitoring-target-name>)

  The private key file to be used for SSH public key encryption is not correctly set (Private_Key_File). Make sure that you specify a correct value when monitoring KVM.

  (S)

  Continues processing of the Remote Monitor Collector service.

  (O)

  Check whether the value of the following property that was set during setup of the monitoring target is correct:

  • Private_Key_File

To Page Top