DB2 fix : SQL0575N View or materialized query table cannot be used because it has been marked inoperative

A user reported the following error , when executing a SELECT statement on a VIEW. [user1@server1 ~]$ db2 "select count(*) from MYSCHEMA.MYTABLE” SQL0575N View or materialized query table "MYSCHEMA.MYTABLE" cannot be used because it has been marked inoperative. SQLSTATE=51024 Another way to check on the error message and as a way to validate the initial error message is to check the the syscat.view valid column. If you see anything other than a Y , then action is required db2 "SELECT viewschema,viewname,valid FROM syscat.views where viewname = 'MYTABLE'" The main reason for the error is because an alias, privilege, table or... Read more →

How to reconfigure DB2 after a Windows Hostname change

If DB2 LUW is installed on a Windows server and there is a Windows Server host name , the services supporting DB2 will not start. Some changes need to be made to allow DB2 to start. You will see errors in Event Logs some examples may be : The DB2 - DB2COPY3 - DB2-0 service terminated with service-specific error %%-1022. The workaround I’ve used to allow DB2 LUW 10.1 and above is : >> Find and open db2nodes.cfg . Using a text editor change the old host names to the new host name >> Open a Windows cmdline and execute:... Read more →

Avamar avtar command option cheat sheet

I've started getting into Avamar as a backup and restore system for DB2. I'm learning all sorts of avtar client command options. I've decided to set up this page as a quick reference. I'll update regularly To view all the command options # ./avtar --help To view the command line option usages # ./avtar --usage To recover information on databases through the avtar # ./avtar --flagfile=/usr/local/avamar/avdb2.flg --backups To view the database details grab the value from --backiups and then run ./avtar --flagfile=/usr/local/avamar/avdb2.flg -tv --labelnum=38 To list backups completed and stored on the data storage system ./avtar --flagfile=/usr/local/avamar/avdb2.flg --list To encode... Read more →

DB2 fix - SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing.

Question: I attempted to complete a db2start on on a DB2 10.1.5 on Linux recently and this was the error returned.The DB2 instance did not start 03/10/2016 09:22:14 0 0 SQL6048N A communication error occurred during START or STOP DATABASE MANAGER processing. SQL1032N No start database manager command was issued. SQLSTATE=57019 What does this error mean and how can I fix the error to allow the DB2 instance starts? Answer: By coincidence , I had a similar problem recently when migrating a server to a test laboratory. As part of the migration the server administrator changed the hostname. This was... Read more →