How to check DB2 LUW load status

Question: How can I check load status in DB2 LUW? Answer: Checking the DB2 LUW load status is achieved by using the load query command. The best way to explain is by demonstrating with a simple example. The DB2 LUW command is used to load data into a DB2 LUW table. The data can be stored in many different forms – including named pipe and tape Starting the load process connect to mydb; create table table2 like table1; load from somedata.del of del insert into table2; While the load process is in flight , create another connection and view the... Read more →

The case of the rapidly expanding TEMPSPACE1 tablespace

An application install was forcing the TEMPSPACE1 to fill very quickly and constantly getting to the system disk is full error. The query was crashing as disk full limits were stopping the query to finish successfully.The db2diag log entries were referencing ADM6017E The following table space is full. Table space name TEMPSPACE1. Disk is full A sql trace captured the query running during this activity. Within the query there was a scalar function.I used the query on How to list UDF in DB2 and returned the routine body. An examination of the routine revealed some useful details. The routine accepted... Read more →

ADM6017E The following table space is full. Table space name TEMPSPACE1. Disk is full

Question: During an application installation this error appeared on the db2diag log ADM6017E The following table space is full. Table space name: "TEMPSPACE1". The underlying file system is full There is very little flexibility about changing the application code and also very limited documentation – limiting my understanding of the amount of TEMPSPACE required. Is there a quick way to workaround this problem? Answer: There are workarounds to the disk is full error when requiring extra temp tablespace particular problem. Without knowing the details , I suspect it’s some sort of function hitting the data which is causing excessive requirement... Read more →

SQL0670N - The row length of the table exceeded a limit of "32677" bytes

Question : The row length of the table exceeded a limit of "32677" bytes. can you give me some advice on how to deal with this problem? the error code associated with the message is SQLCODE=-670, SQLSTATE=54010 I'm using DB2 9.5.0.3 Answer: Without knowing any extra details , I would guess you are attempting to add a column or extend an existing column which is causing the size to be greater than 32768 bytes. The way you approach the problem will depend on what you are attempting to do. For example, if you are executing a create\alter on a table,... Read more →

SQL0286N A table space could not be found with a page size of at least 32768

Question: I got this error on MYDB on MYSERVER: DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL0286N A table space could not be found with a page size of at least "32768" that authorization ID "DB2USER" is authorized to use. SQLSTATE=42727 Answer: You must be attempting to execute a CREATE TABLE statement where the requirement is for a pagesize greater that the tablespace pagesizes available. You could verify this by connecting to the database and running the LIST TABLESPACES SHOW DETAIL command. If... Read more →