SQL0293N Error accessing a table space container. SQLSTATE=57048 and LinuxSheild

Users started reporting some inconsistency on connecting to a database on DB2 9.5 on RHEL 5.I performed an initial check on connecting via Putty , and received an error of not being able to access the table container. A db2dialog.log snippet revealed: ZRC=0x8402001E=-2080243682=SQLB_CONTAINER_NOT_ACCESSIBLE "Container not accessible" I attempted a backup - which failed due to "not being able to write over a read only file". The problem was resolved by stopping the LinuxSheild 1.6 . It appears LinuxSheild 1.6 had been rolled out without the relevant testing . Modifying the exclusion list solved the problem Ref:Jack Vamvas(http://www.dba-db2.com) Read more →

SQL0964C The transaction log for the database is full.

"Why does this error occur ? SQL0964C The transaction log for the database is full" The SQL0964C error occurs the objects loaded into the transaction log which is cause the the transaction logs to overfill. By default the amount of secondary log files is 2 Resolve the problem by increasing the amount of secondary log files : db2 update db cfg for MY_DB_NAME using LOGSECOND 100 Read More DB2 log management DB2 LOGINDEXBUILD - DBA DB2 ADM1823E active log file full - DBA DB2 DM1823E - Log file has reached its saturation point - DBA DB2 Read more →