The developerWorks Connections platform will be sunset on December 31, 2019. On January 1, 2020, this blog will no longer be available. More details available on our FAQ.
75 ways to demystify DB2: #23: Techtip: Error SqlCode = -4700 returned to JCC applications after upgrading DB2/Z servers to V11 CM mode.
Recently we are seeing lot of cases where applications using IBM DB2 JDBC drivers(db2jcc.jar/db2jcc4.jar)) start failing with SqlCode = -4700 after DB2/zOS server upgrade to V11 CM (Compatibility mode). I wanted to clarify about the error and explain the background. -4700 is a sqlcode returned by the DB2/Z server. It means: "ATTEMPT TO USE NEW FUNCTION BEFORE NEW FUNCTION MODE" The error is returned when the application queries the special register CLIENT_CORR_TOKEN . This special register is not available in V11 CM and introduced in... [More]
Tags: 75_db2demystify jcc -4700 db2_techtip |
75 ways to demystify DB2: #22: Techtip: Why is db2ilist not listing my instances?
DB2 instance is up and running fine, but when issuing 'db2ilist' no output is being returned, what needs to be done? Step 1: Dump out the registry and validate if you have the instance listed or not db2greg -dump | grep <instance name> Step 2: As an instance owner issue db2set and validate if you have the instance name outputted db2set -l Step 3: Once you validate the instance entry is in 'db2greg' output and not in 'db2set' ouput, as root, go to <installpath>/instance cd... [More]
Tags: 75_db2demystify db2_techtip db2greg db2iset db2ilist |
75 ways to demystify DB2: #21: Techtip: Getting SQL0444N with Reason code: "6"
Getting SQL0444N with Reason code: "6" ? For example, when you do a query like: db2 "select count(*) from SYSIBMADM.DB_HISTORY" You can get the following error. SQL0444N Routine "*IST_HIST" (specific name "ADMIN_LIST_HIST") is implemented with code in library or path "...e/db2adminListHist", function "adminListHistTrusted" which cannot be accessed. Reason code: "6". SQLSTATE=42724 Why is that? How to troubleshoot? 1.... [More]
Tags: db2_techtip 75_db2demystify sql0444n |
75 ways to demystify DB2: #20: Tech Tip: Question about dropping members in a pureScale environment.
Hello DBAs Recently came across this question about dropping members that reside in the same physical server. Consider the db2instance -list output like this. #db2instance -list ID TYPE STATE HOME_HOST CURRENT_HOST ALERT PARTITION_NUMBER LOGICAL_PORT ETNAME -- ---- ----- --------- ------------ ----- ---------------- ------------ ------ 0 MEMBER STARTED host1 host1 NO 0 1 host1-en1.xxxx.com 1 MEMBER STARTED host1 host1 NO 0 0 host1-en1.xxxx.com 2 MEMBER STARTED host2 host2 NO 0 0 host2-en1.xxxx.com 3 MEMBER STARTED host2 host2 NO 0 1... [More]
|
75 ways to demystify DB2: #1: Expert Advice: DB2 Database Backup and Restore in DPF using Single System View
Have you tried taking DB2 database backup and restoring it in DPF using Single System View? DB2 Version 9.5 (or later) provides the Single System View (SSV) function which allows backing up multiple database partitions at once. In earlier releases, partitioned databases needed to be backed up one partition at a time which can be time consuming and prone to errors. The backup timestamp associated with all database partitions is the same. I am listing down the commands with minimum clauses to illustrate how SSV can be used.... [More]
Tags: single_system_view dpf db2_techtip backup restore 75_db2demystify |
75 ways to demystify DB2: #19: Techtip : Slow crash recovery in DB2 due to replaying load pending operations
During crash recovery, if many load operations have to be replayed, then it might take a long time to complete. The load operation will keep the pending operations in transaction logs no matter if it is recoverable load or non-recoverable. These pending operations will be kept in transaction log just before the table status is changed back from "load in progress" state to "normal" state. If the crash recovery starting point - min(lowtranlsn, minbufflsn) is before load pending operations then db2 will have to replay... [More]
Tags: db2_techtip 75_db2demystify |
75 ways to demystify DB2: #18: Techtip: Why the DB2 HADR is not using the assigned port numbers ONLY ?
When using DB2 HADR the local service/port (HADR_LOCAL_SVC) and remote service/port (HADR_REMOTE_SVC) are defined. But, why netstat output shows that hadr is using other port numbers too ? Both HADR_LOCAL_SVC and HADR_REMOTE_SVC are used as the lower level TCP server listener port numbers only. The client side of the TCP uses free ports available from OS from that side. HADR uses TCP server and TCP client at the lower level. In this context, one HADR db side listens on its hadr_local_svc port as TCP server, the... [More]
Tags: 75_db2demystify db2_techtip hadr |
75 ways to demystify DB2: #17: Expert Advice: NullPointerException while loading DB2 JCC driver using Custom class loader.
Issue: NullPointerException was thrown when one of our customers tried to load latest DB2 JCC driver (db2jcc.jar - V10.1 and above) using a custom class loader ( like open source module NestedJarClassLoader). The same worked while loading old DB2 V8.2 db2jcc.jar driver (2.11.24). Here is the error stack: Caused by: java.lang.NullPointerException at com.ibm.db2.jcc.am.md.run(md.java:49) at java.security.AccessController.doPrivileged(Native Method)... [More]
Tags: db2_advice 75_db2demystif |
75 ways to demystify DB2: #16: Resource Info: Supported Perl with DB2 on Windows.
As of now, DB2 on Windows supports ActivestatePerl (both 32bit and 64 bit) and Strawberry Perl (32 bit ONLY). To get the 32 bit DBD::DB2 binaries supported with 32 bit Strawberry Perl, you must email opendev@us.ibm.com or contact IBM support for the required binaries. 64 bit Strawberry Perl is not supported yet. Thanks!
Tags: 75_db2demystify db2_resource |
75 ways to demystify DB2: #15: On Linux, DB2 instance is not automatically starting upon system reboot
Recently worked on an issue with DB2 Fault Monitor (FM) process failing to start on a Linux RHEL 6 platform. After following the steps in the technical note below: http://www.ibm.com/support/docview.wss?uid=swg21209001 the DB2 Fault Monitor process was failing with the following message : # su - db2inst1 $ . ./sqllib/db2profile $ db2fm -s -S Gcf module 'fault monitor' is INSTALLED PROPERLY but NOT ALIVE Gcf module '/opt/IBM/DB2/lib64/libdb2gcf.so' is INSTALLED PROPERLY but NOT ALIVE As a result, the DB2 instance will not... [More]
Tags: db2_resource 75_db2demystify automatic db2_techtip db2 db2_event db2_advice |
