システム・メッセージ: Qカタログ1200-1299
|
1205 |
ERROR: Invalid high threshold type | |
|
Description |
While executing the qcreate or qchange command, an invalid upper threshold value was specified (the suffix was not valid). The threshold value must be a number suffixed with 'b', 'B', '%', or 'm'. |
Action |
Re-enter the qcreate or qchange command using an appropriate threshold value. | |
See Also |
| |
1207 |
ERROR: Invalid high threshold number | |
|
Description |
While executing the qcreate or qchange command, an upper threshold value of 0 was specified, or a percentage greater than 100 was given. |
Action |
Re-enter the qcreate or qchange command using an appropriate threshold value. | |
See Also |
| |
1210 |
ERROR: High and low threshold types do not match | |
|
Description |
While executing the qcreate or qchange command, the suffix on the upper threshold value doesn't match the suffix on the lower threshold value. |
Action |
Re-enter the qcreate or qchange command using appropriate threshold values. | |
See Also |
| |
1212 |
ERROR: Low threshold must be less than high threshold | |
|
Description |
While executing the qcreate or qchange command, the lower threshold value is larger than the upper threshold value. |
Action |
Re-enter the qcreate or qchange command using appropriate threshold values such that the lower value is less than the upper threshold value. | |
See Also |
| |
1215 |
ERROR: Threshhold command length must be less than len characters | |
|
Description |
While executing the qcreate or qchange command, the threshold command was too long (that is, len characters or more). |
Action |
Re-enter the command with a threshold command that is 128 characters or less in length. | |
See Also |
| |
1216 |
ERROR: Queue creation failed for queue name | |
|
Description |
While executing the qcreate command, qmadmin failed to create the specified queue. There are many possible reasons for the failure and the specific reason is written to the standard output or the userlog. |
Action |
Re-enter the command when the problem has been resolved. | |
See Also |
| |
1221 |
WARN: Priority not changed | |
|
Description |
While changing message priorities with the qchangeprio command, the user did not respond with Y or y to the prompt for confirmation and the operation was not done. |
Action |
No action required. | |
See Also |
| |
1223 |
ERROR: Queue name length must be less than len characters | |
|
Description |
While executing the qchangequeue command, the queue name was too long (that is, len characters or more). |
Action |
Re-enter the command with a queue name that is 15 characters or less in length. | |
See Also |
| |
1224 |
ERROR: Queue name must be specified | |
|
Description |
While executing the qdestroy command, the queue name was not entered at the prompt or an empty string was specified on the command line. |
Action |
Re-enter the qdestroy command specifying a valid queue name. | |
See Also |
| |
1226 |
WARN: Queue not changed | |
|
Description |
While changing the queue on which messages are queued with the qchangequeue command, the user did not respond with Y or y to the prompt for confirmation and the operation was not done. |
Action |
No action required. | |
See Also |
| |
1228 |
ERROR: Invalid time format | |
|
Description |
While executing the qchangetime command, an invalid date and time value was specified. |
Action |
Re-enter the qchangetime command using a valid date/time value. The value must be of the form | |
See Also |
| |
1230 |
WARN: Time not changed | |
|
Description |
While changing message execution time with the qchangetime command, the user did not respond with Y or y to the prompt for confirmation and the operation was not done. |
Action |
No action required. | |
See Also |
| |
1232 |
WARN: Messages not deleted | |
|
Description |
While deleting messages with the qdeletemsg command, the user did not respond with Y or y to the prompt for confirmation and the operation was not done. |
Action |
No action required. | |
See Also |
| |
1233 |
ERROR: Cannot specify the -p and -f options together | |
|
Description |
While executing the qdestroy command, both the -p and -f options were specified. |
Action |
Re-enter the qdestroy command with either the -p or -f option but not both. | |
See Also |
| |
1234 |
ERROR: Cannot specify the -p and -f options together | |
|
Description |
While executing the qdestroy command, both the -p and -f options were specified. |
Action |
Re-enter the qdestroy command with either the -p or -f option but not both. | |
See Also |
| |
1237 |
WARN: Queue not destroyed | |
|
Description |
While destroying a message queue with the qdestroy command, the user did not respond with Y or y to the prompt for confirmation and the operation was not done. |
Action |
No action required. | |
See Also |
| |
1238 |
ERROR: Failed to destroy queue queue | |
|
Description |
While executing the qdestroy command, qmadmin failed to destroy the specified queue, queue. There are many possible reasons for the failure and the specific reason is written to the standard output or the userlog. |
Action |
Re-enter the command when the problem has been resolved. If the command fails because other processes are attached to the queue space, the -f option can be specified to force destroying the queue. If the command fails because there are messages on the queue, the -p option can be specified to purge the queue and destroy it. | |
See Also |
| |
1241 |
ERROR: Failed to open queue space queue_space_name on config config | |
|
Description |
While executing the qopen command, qmadmin failed to open the specified queue space, queue_space_name, on the configuration device config. There are many possible reasons for the failure and the specific reason is written to the userlog. |
Action |
Check the userlog for the specific reason for failure. Re-enter the command when the problem has been resolved. | |
See Also |
| |
1246 |
WARN: Transaction not aborted | |
|
Description |
While heuristically aborting a transaction with the qaborttrans command, the user did not respond with Y or y to the prompt for confirmation and the operation was not done. |
Action |
No action required. | |
See Also |
| |
1250 |
WARN: Transaction not committed | |
|
Description |
While heuristically committing a transaction with the qcommittrans command, the user did not respond with Y or y to the prompt for confirmation and the operation was not done. |
Action |
No action required. | |
See Also |
| |
1256 |
ERROR: Invalid time format | |
|
Description |
While executing the qscan command, an invalid date and time value was specified. |
Action |
Re-enter the qscan command using a valid date/time value. The value must be of the form YY[MM[DD[HH[MM[SS]]]]] (that is, 2 digits for year, and optionally 2 digits each for the month, date, hour, minute, and second). | |
See Also |
| |
1257 |
ERROR: Invalid time format | |
|
Description |
While executing the qscan command with a range of date/time values, an invalid date and time value was specified for the second value. |
Action |
Re-enter the qscan command using a valid date/time value. The value must be of the form YY[MM[DD[HH[MM[SS]]]]] (that is, 2 digits for year, and optionally 2 digits each for the month, date, hour, minute, and second). A range of date/time values is two date/time values separated by a hyphen. | |
See Also |
| |
1258 |
ERROR: Invalid priority | |
|
Description |
While executing the qscan command, an invalid priority value was specified. |
Action |
Re-enter the qscan command using a valid priority value. The value must be numeric in the range 1-100, inclusive. | |
See Also |
| |
1259 |
ERROR: Invalid priority | |
|
Description |
While executing the qscan command, an invalid range of priority values was specified. |
Action |
Re-enter the qscan command using a valid priority value. A priority value must be numeric in the range 1-100, inclusive, and a range of priorities is two priority values separated by a hyphen. | |
See Also |
| |
1260 |
ERROR: Invalid message id | |
|
Description |
While executing the qscan command, an invalid message identifier value was specified. |
Action |
Re-enter the qscan command using a valid message identifier value. The value must be a string, less than 33 characters in length, with backslash and non-printable characters entered as a backslash followed by a two-character hexadecimal value for the character. | |
See Also |
| |
1261 |
ERROR: Invalid correlation id | |
|
Description |
While executing the qscan command, an invalid correlation identifier value was specified. |
Action |
Re-enter the qscan command using a valid correlation identifier value. The value must be a string, less than 33 characters in length, with backslash and non-printable characters entered as a backslash followed by a two-character hexadecimal value for the character. | |
See Also |
| |
1262 |
ERROR: Queue name length must be less than len characters | |
|
Description |
While executing the qset command, the queue name was too long (that is, len characters or more). |
Action |
Re-enter the command with a queue name that is 15 characters or less in length. | |
See Also |
| |
1279 |
ERROR: Must specify queue space name | |
|
Description |
While executing the qspacecreate command, the queue space name specified is the null string (that is, the name was entered on the command line as "", or return was entered for the prompt for the Queue Space Name). |
Action |
Re-enter the qspacecreate command with the correct queue space name. | |
See Also |
| |
1280 |
ERROR: Queue space name length must be less than len characters | |
|
Description |
While executing the qspacecreate command, the queue space name was too long (that is, len characters or more). |
Action |
Re-enter the command with a queue space name that is 15 characters or less in length. | |
See Also |
| |
1282 |
ERROR: Queue name length must be less than length characters in old queue space | |
|
Description |
For Oracle Tuxedo release older than 11gR1, the queue name must be less than length. The length queue name has increased to 127 from Oracle TUXEDO 11gR1 and above: however, it is not allowed to create, change queue with long names if the opened queue space is created by earlier Oracle TUXEDO releases. |
Action |
Correct the value of queue name with a name less than length and retry the action. | |
See Also |
| |
1284 |
ERROR: Error queue name length must be less than length characters in old queue space | |
|
Description |
For Oracle Tuxedo release older than 11gR1, the queue name must be less than length. The length queue name is enlared to 127 from TUXEDO 11gR1 and above, but it is not allowed to change error queue with long names if the opened queue space is created by earlier Oracle TUXEDO releases. |
Action |
Correct the value of error queue name with a name less than length and retry the action. | |
See Also |
| |
1294 |
ERROR: Error queue name length must be less than len characters | |
|
Description |
While executing the qspacecreate command, the error queue name was too long (that is, len characters or more). |
Action |
Re-enter the command with an error queue name that is 15 characters or less in length. | |
See Also |
| |
1295 |
ERROR: Queue space creation failed | |
|
Description |
While executing the qspacecreate command, qmadmin failed to create the specified queue space. There are many possible reasons for the failure and the specific reason is written to the standard output or the userlog. |
Action |
Re-enter the command when the problem has been resolved. | |
See Also |
| |
1298 |
WARN: Queue space not destroyed | |
|
Description |
While destroying a queue space with the qspacedestroy command, the user did not respond with Y or y to the prompt for confirmation and the operation was not done. |
Action |
No action required. | |
See Also |
|