IBM DB2: Unable to monitor tablespace (Error:DB2 SQL Error: SQLCODE=-1092)

IBM DB2: Unable to monitor tablespace (Error:DB2 SQL Error: SQLCODE=-1092)

Problem:

Error: DB2 SQL Error: SQLCODE=-1092 shown in the 'Monitor Information' section in the 'Overview' tab of the DB2 monitor page.

Why do you see this error?

You require a DB2 user with System monitor authority (SYSMON) to monitor the tablespace details in IBM DB2 from Applications Manager. If this privilege is not available, then you will see the error given above.

Solution:

To fix the error, you will have to create an OS group and provide SYSMON authority to the Application Manager's DB2 user by following the steps mentioned below.

In Operating System
  1. Create a OS group in the operating system (ex: apmgrp) and assign Applications Manager DB2 OS user to that group.

In DB2 database
  1. Configure the OS group that was created earlier (apmgrp) to obtain SYSMON permission in the database and then restart the DB2. Subsequently, you will have to provide DATAACCESS privilege or access to the SYSIBMADM functions and SYSPROC procedures and restart the DB2 again. You can do the same using the following commands:
  1. db2 UPDATE DBM CFG USING SYSMON_GROUP <group_name>
  2. db2stop
  3. db2start
  4. db2 GRANT DATAACCESS ON DATABASE TO GROUP <group_name>
  5. db2stop
  6. db2start
ex:
  1. db2 UPDATE DBM CFG USING SYSMON_GROUP apmgrp
  2. db2stop
  3. db2start
  4. db2 GRANT DATAACCESS ON DATABASE TO GROUP apmgrp
  5. db2stop
  6. db2start


      New to M365 Manager Plus?
      New to M365 Manager Plus?
        New to RecoveryManager Plus?
        New to RecoveryManager Plus?
          New to Exchange Reporter Plus?
          New to Exchange Reporter Plus?
            New to SharePoint Manager Plus?
            New to SharePoint Manager Plus?
                See all integrations
                New to ADManager Plus?
                See all integrations
                New to ADManager Plus?

                  New to ADSelfService Plus?

                  Start your free trial
                  Start your free trial

                    • Related Articles

                    • DNS Monitor - Troubleshooting

                      Common DNS Monitor Errors and Troubleshooting Guide 1. Host Not Found Description: The DNS server was unable to locate the requested lookup address. Possible Causes: This may happen if the hostname is incorrect, the domain does not exist, or there is ...

                    • Self monitor Applications Manager using Real User Monitoring

                      We can monitor the Applications Manager using Real User Monitoring with a Java Script injection and this can be used to measure the Applications Manager's performance continuously. All you need is to install and setup the Real User Monitoring (RUM) ...

                    • Mail Server Monitor - Troubleshooting

                      Common Mail Server Monitor Errors and Troubleshooting Guide 1. Unknown Host Error Description: This error occurs when the mail client cannot resolve the hostname of the mail server to an IP address. The issue typically arises from DNS resolution ...

                    • Troubleshooting URL Monitor

                      Here are few of the common errors you may come across in URL monitor, we have mentioned the steps you can follow to troubleshoot them. General troubleshooting for URL monitor Ensure that the URL is accessible from the server in which Applications ...

                    • Real User Monitor (RUM) - Troubleshooting

                      If the monitor has not polled data for a long time, follow the steps below for troubleshooting: Step 1: Check the RUM Agent configuration Real User Monitor requires the RUM Agent to be installed and mapped to the Applications Manager. Refer the help ...

                      Related Products