16400s - Workload Manager
No new writeups yet.
16400 18 Workload manager could not set the completion time for action with handle %d.
16401 18 Workload manager could not determine the start time for action with handle %d.
16402 17 Unable to allocate a logical cluster descriptor for logical cluster '%.*s'. Drop an existing logical cluster or raise the configuration parameter 'workload manager cache size'.
16403 17 Unable to allocate a descriptor for route '%.*s'. Drop an existing route or raise the configuration parameter 'workload manager cache size'.
16404 17 Unable to allocate a descriptor for load profile '%.*s'. Drop an existing load profile or raise the configuration parameter 'workload manager cache size'.
16405 17 Unable to allocate a descriptor for action with handle %d. Release a completed action or raise the configuration parameter 'workload manager cache size'.
16406 18 Encountered logical cluster '%.*s' with illegal state %d. Reboot ASE to clear this problem.
16407 18 Workload manager encountered an unexpected state of %d for logical cluster '%.*s' on instance %d. Reboot ASE to clear this problem.
16408 10 Logical cluster '%.*s' could not be brought online on instance %d because it is in the TIMEDWAIT state on that instance.
16409 14 Workload management rules do not allow your connection to continue. Please contact your System Administrator for assistance.
16410 16 Unknown attribute id %d passed to the workload manager.
16411 18 Attempt to acquire the workload manager global configuration lock failed.
16412 16 A logical cluster with name `%.*s` already exists.
16413 16 A logical cluster with id %d already exists.
16414 16 Could not find descriptor for logical cluster with id %d.
16415 16 You cannot rename the system logical cluster.
16416 16 You cannot drop the system logical cluster.
16417 16 You cannot drop the open logical cluster.
16418 16 You cannot drop logical cluster '%.*s' because it has defined routes. Drop all associated routes before dropping the logical cluster.
16419 16 You may not set attribute %d of the system logical cluster.
16420 16 The value %d is not legal for logical cluster attribute %d.
16421 16 %d is not a valid logical cluster attribute id.
16422 16 Cannot find descriptor for load profile with id %d.
16423 16 Could not find descriptor for logical cluster with name '%.*s'.
16424 16 You cannot run the '%.*s' command against the system logical cluster.
16425 16 The wlmgr_admin built-in cannot be executed because the workload manager subsystem is not online.
16426 15 '%.*s' is not a valid workload manager command.
16427 15 '%.*s' is not a valid workload manager sub-command.
16428 15 You cannot specify the same instance in both instance lists.
16429 15 '%.*s' is not a valid workload manager wait option.
16430 15 You cannot specify a time value with wait option '%s'.
16431 15 You must specify a time value with wait option '%s'.
16432 16 Could not find descriptor for action with handle %d.
16433 15 You may not specify a 'from' or 'to' instance list for the '%s %s' command.
16434 15 You must specify a 'from' instance list for the '%s instance' command.
16435 15 '%.*s' is not a legal subcommand for the '%.*s' command.
16436 15 You may not specify a base instance in the from list for the 'failback instance' command.
16437 17 Insufficient memory to allocate workload manager backout structure. Raise the value of configuration parameter 'procedure cache size'.
16438 18 Attempt to acquire object coherency lock for logical cluster '%.*s' failed. Retrun status was %d.
16439 16 Cannot drop logical cluster '%.*s' because it is currently in the '%s' state. Try taking the logical cluster offline before dropping it.
16440 16 You cannot change instance settings for the system logical cluster.
16441 15 Illegal failover group %d specified. Legal values are between %d and %d.
16442 16 Cannot add instance '%s' to logical cluster '%.*s' because it is already an instance in that logical cluster.
16443 16 Cannot drop instance %d ('%s') from logical cluster '%.*s' because it is currently in the '%s' state. Try taking the logical cluster offline on this instance before dropping it.
16444 16 Cannot drop instance %d ('%s') from logical cluster '%.*s' because it is not an instance in that logical cluster.
16445 15 '%c' is not a valid logical cluster instance type.
16446 15 Invalid route type %d.
16447 16 A route of type %d with key '%.*s' already exists.
16448 16 Could not find descriptor for route with type %d and key '%.*s'.
16449 16 A load profile with name '%.*s' already exists.
16450 16 A load profile with id %d already exists.
16451 16 %d is not a valid load profile attribute id.
16452 16 You cannot drop load profile '%.*s' because it is being used by one or more logical clusters.
16453 16 Workload manager could not bring any instances online for logical cluster '%.*s' during the failback command. The command will be aborted.
16454 16 Workload manager could not bring any instances online for logical cluster '%.*s' during the failover command. The command will be aborted.
16455 18 Attempt to acquire object coherency lock for action %d failed. Return status was %d.
16456 18 A failure was encountered while multicasting the execute event for action %d. The action will use an infinite wait on instances that did not receive the message.
16457 17 Workload manager could not allocate an alarm for action %d. Try raising the 'number of alarms' configuration parameter.
16458 18 Attempt to set an alarm for action %d failed. The action will run on this instance until all affected user connections disconnect or migrate.
16459 16 Cannot create a user load profile with an id less than %d.
16460 18 Workload manager fatal error: could not initialize the system logical cluster.
16461 18 Attempt to acquire object coherency lock for workload manager control failed. Return status was %d.
16462 17 Failed to spawn the workload manager thread.
16463 18 Workload manager could not setup a scan of sysattributes. The on disk configuration could not be read.
16464 18 Workload manager encountered an error while retrieving existing actions at boot time.
16465 18 Unable to install action with handle %d.
16466 17 The workload manager could not establish a load update alarm. Load statistics for this instance will not be tracked.
Try raising the 'number of alarms' configuration parameter.
16467 18 Unable to do proper shutdown handling for logical cluster '%.*s'. The logical cluster will be recovered when this instance exits.
16468 15 The user supplied workload metric value must be greater than or equal to zero.
16469 16 You cannot set the user workload metric for instance '%s' because that instance is not in the UP state.
16470 18 Workload manager encountered an error posting the user workload metric update event. The user workload metric value has not been changed.
16471 18 Workload manager encountered a DMM error while retrieving usage data for logical cluster '%.*s'.
16472 18 Route of type %d with key '%.*s' could not be activated because a matching route descriptor cuold not be found.
16473 16 You cannot submit a new action for logical cluster '%.*s' on instance '%s' because it already has an action pending on that instance.
16474 18 Workload manager is unable to submit action with handle %d for execution due to a previous error. However, changes to logical cluster '%.*s' have already been
committed and will not be undone. The action will behave with an infinite wait.
16475 16 Action with handle %d is associated with logical cluster %.*s, not logical cluster '%.*s'.
16476 18 Workload manager encountered a PCM error (%d) while sending a remote command. The current command will be aborted.
16477 18 Workload manager remote operation %d succeeded on %d instance(s) but failed on %d instance(s). This operation cannot be undone, and the
workload manager may now be in an inconsistent state.
16478 18 Workload manager encountered an error during remote operation %d and the operation will be aborted.
Consult the Adaptive Server log on each instance for additional details.
16479 15 A wait option is required for the '%s %s' command.
16480 18 Attempt to send a cluster event for command '%s %s' failed. The command will be aborted.
16481 16 The action you are trying to release is active. You must wait for it to complete or cancel it prior to releasing it.
16482 16 The action you are trying to release is already being released.
16483 18 The workload manager command '%s %s' failed because it could not submit an action. Refer to previous errors or the Adaptive Server error log for additional details.
16484 15 You may not specify a 'from' instance list for the '%s %s' command.
16485 16 The failover instance command requires that all 'from' instances be in the online state.
16486 16 Instance %d ('%s') is not a defined instance for logical cluster '%.*s'.
16487 10 Could not automatically start logical cluster '%.*s' at startup. Consult the Adaptive Server error log for additional details.
16488 18 Workload manager encountered an error while completing the timed wait transition for logical cluster '%.*s' and this logical cluster will not properly go offline.
Consult the Adaptive Server error log for additional details.
16489 16 A workload manager operation has aborted due to an attention flag.
16490 0 Cannot create a user load profile that begins with sybase_profile.
16491 16 Spid %d is not migratable.
16492 0 Instance '%d' is not online on logical cluster '%.*s'.
16493 16 Workload manager cannot perform a failover for logical cluster '%.*s' without a specified failover instance while the failover mode is set to group
and additional instances remain online.
16494 16 The failover cluster command requires that the cluster be in the online state.