Delete first 1000 rows in a DB2 table using FETCH FIRST

Question: How can I delete rows in batches ? I’m getting the SQL0964C The transaction log for the database is full error, and don’t have the authority to increase the LOGSECOND parameter? How can I use SQL code to DELETE in batches of 1000? Answer: The FETCH FIRST commands can limit the amount of rows returned. Combining FETCH FIRST with DELETE allows you to manage the batch commit process. Check this example. The SELECT combined with FETCH FIRST statement returns batches of 1000. The DELETE command covers the recordset generated by the SELECT statement DELETE FROM (SELECT * FROM DB1.MY_DB... Read more →

SQL30082N – ROOT CAPABILITY REQUIRED

An application owner reported an error DB2 SQL error SQLCODE -30082, SQLSTATE 08001, SQLERRMC 42;ROOT CAPABILITY REQUIRED;DSRA0010E SQL State = 08001, Error Code = -30,082. I checked in the db2diag.log Password validation for user xxxxx failed with rc = -2146499506 The main reason this sequence of errors appear is due to the DB2 password daemon not started. Therefore the db2sysc process attempts the password check. If the db2sysc process doesn’t have root authority the error code . SQL30082N 42 appears. How to fix the ROOT CAPABILITY REQUIRED error SQL30082N 1) Check to see db2ckpwd is running as Root 2) If... Read more →

Application first database second

“Application first database second” said the scrum master. I had an interesting conversation with a colleague about the philosophy underpinning his development methodology. We were discussing the merits of solid data modelling underpinning the agile method. I’d been considering this topic in Agile DBA His criticism of spending an excessive time creating the ideal data model – impinged upon the project deadlines. Data Architects were spending so much time gathering and analysing requirements , they weren’t able to shift product and new functionality to customers. His mantra of “Application first database second” focused his developers on developing quickly – usually... Read more →

How to protect DB2 against External Attack

Fully protecting DB2 against an external attack requires solid design and regular Audits. Exposing some surface area to external connections ,creates an attack opportunity. As a DBA being aware of potential weaknesses and designing secure systems is a top priority. These are some areas of focus when designing a DB2 security audit. The foundation of DB2 security is a solid DB2 security policy. Any audit should be comparing the results with the security policy 1) Do not use standard ports for DB2. Protect the DB2 server against scans. On Linux, you will have to define a port/service before making remote... Read more →