Reason:
Your request required a temporary table (for sorting or subquery result set), and the Temporary Table Manager (TTM) area became full.
The SQLSTATE that equates to this SQL return code is 57S05.
Action:
The TTM area can be extended using dynamic extends.
Dynamic extensions of the TTM can be done with no loss of access to any other task areas or TTM usage. You need not close the TTM. Support is provided when the TTM is defined as either DASD or VIRTUAL. When the TTM is DASD, define the dynamic extend or on-demand dynamic extend for the TTM as for any other DASD data set. When the TTM is VIRTUAL, use the dynamic extend or on-demand dynamic extend as for any other VIRTUAL database area.
To specify dynamic extend at MUF startup, use MUF startup options as described in the Database and System Administration Guide.
To change dynamic extend settings for VIRTUAL TTMs after the MUF has started, use the VIRTUAL_DYNAMIC_EXTEND console-like command. For more information about this command, see the Database and System Administration Guide.
To use on-demand dynamic extend, use the DYNAMIC_EXTEND console-like command that is described in the Database and System Administration Guide.
A new column, TTM_BLKS_MAX_USE, that lists the highest number of 4K-blocks that are used, is found in the SQL_STATUS (SQS) table. For more information, see the System Tables Reference Guide.
The TTM can become full due to a combination of temporary tables for your request and other concurrent requests. You may be able to run successfully when other requests are not using temporary tables.
Use the global trace option of the CA Datacom/DB Utility (DBUTLTY) COMM function as follows to determine the number of TTM blocks available and most used since the MUF was started.
COMM OPTION=ALTER,TRACE=TRACEGLOBAL
This information is written to the Statistics and Diagnostics Area (PXX) when a run unit ends and can be reported with either DUMPS=FULL or DUMPS=TRACE.
To determine how many TTM blocks your request requires, use the MSG=NS (execution-time summary messages) plan option. This information is written to the MSG table in base 15. You can access this information using standard record-at-a-time (RAAT), set-at-a-time (SAAT), or SQL access. The SQL table name is SYSADM.SYSMSG. The columns of this table are defined in CA Datacom Datadictionary. This information is deleted when the plan is deleted. If the information is not in this table, the MSG table may be full. This is reported as SQL return code -258.
Note: If the system has just been upgraded and any attempt to access the TTM gets a -560, verify that relative record addressing (DIRECT=YES) is used for the TTM. Print a Directory (CXX) report for your TTM database and check the DIRECT attribute for the key (there is only one key) on the TTM table. If DIRECT=NO, you have found the cause of your problem. You can correct this problem by updating the key definition to reflect DIRECT=YES and recataloging the database.
|
Copyright © 2014 CA.
All rights reserved.
|
|