Part of the IBM Analytics family, focused on Analytic Platform product support. This blog is administered by Andrew McCarl (amccarl) and Kate Nichols (KateDawson), and follows the IBM Social Computing Guidelines.
In DPF environment, the lock timeout issue could be caused by indoubt transactions. The indoubt transactions cannot be automatically committed or rollback by database manager therefore whenever the application restarts the lock timeout issue occurs.
Collect the locking data by:
db2pd -db <dbname> -alldbp -wlock -app -trans -repeat 5 10
Note that the above db2pd must have -alldbp option which runs on each logical node on one physical box, if there are multiple physical... [More]
Most default installations of DB2 when bundled with other products lays out the database and storage spaces in its most basic form. Usually it has USERSPACE1 where all of the data are stored by default. Over time as the data grows your so does the time it takes to backup your database bringing it to unacceptable levels.
It has also been observed that in such situations a restore operation of the same database completes in a fraction of the time. To explain this phenomenon it is important to understand the Buffer Manipulator (BM).
After yesterday's blog announcing our May 14 Support Technical Exchange session , we're back with yet another opportunity for you to build your skills in May!
Register for our May 21 Support Technical Exchange: Configuring the Complex Flat File Stage in InfoSphere Information Server
Access to data in mainframe files is on the rise and poses tricky challenges to extract this critical data. The Complex Flat File stage is a file stage designed to process complex EBCDIC and ASCII... [More]
Join us for our upcoming Support Technical Exchange! Our speaker, Gary Foster, will guide us through a deep dive on I BM InfoServer DataStage PX Engine - Lookup Stage.
The parallel lookup stage is one of the most used stages in PX job design. In this presentation, Gary will show the options for use, case scenarios and how this stage works internally so you can make better decisions on how to use this stage in your job designs. With proper use, you can capitalize on available resources and maximize performance of your jobs.... [More]
You are invited to join us for a free education session covering Upgrading from Initiate 10.1 to IBM SE MDM V11.4.
Date: Wednesday May 13
Time: 10:00 AM - 11:00 AM Eastern
Registration Link: https://events.na.collabserv.com/register.php?id=4991bb3d43&l=en-US
In this presentation we will provide an overview on upgrading from Initiate v10.1 to IBM InfoSphere MDM v11.4. The steps to upgrade the Initiate database to MDM v11.4, to point the new MDM installation to the upgraded database and verification... [More]
Today we'd like to share a very important reminder for any of our clients running DB2 version 9.5. You should be aware that DB2 version 9.5 will reach End of Support on April 30, 2015.
Please see our DB2 EOS Technote , for answers and guidance on topics including:
How do I purchase a Support Extension?
Is there information to help me upgrade?
What DB2 9.5 servers are affected?
What if I have a special build or an older fix pack on DB2 9.5? Am I still supported?
I am using DB2 9.5 as... [More]
Connections being rejected on a V9.8 pureScale environment
Any connections being made to the database that is on a v9.8 pureScale instance is experiencing a connection hang and instance may experience a 'hang' like situation.
If we take a few iteration of stacks (db2pd -stacks all -rep 10 5), and the stack analysis may have the following output:
0x0900000000533990 _p_nsleep + 0x10
0x0900000000038BE4 nsleep + 0xE4
0x090000000015B290 nanosleep + 0x190
Please join us for our upcoming Support Technical Exchange!
Our speaker, Scott Brokaw, will guide us through Configuring SSL/HTTPS in InfoSphere Information Server versions 8.5 - 11.3.
Date: Tuesday April 21, 2015
Time: 11:00 am ET
This presentation will discuss how to leverage and configure SSL (Secure Sockets Layer) authentication. SSL authentication is configurable at version 8.5 and later. Beginning at version... [More]
Getting SQL10004C An I/O error occurred while accessing the database directory?
The reason for SQL10004C may vary. Possible reasons are:
- sqldbdir being corrupted
- incorrect permission or access issues to the sqldbdir file under database directory
Another possible cause is that the system may have been maxed out of available file handles. If you scan the /var/log/messages , you may see an error during the same time frame you got SQL10004C error.
kernel: VFS: file-max limit ###... [More]
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... [More]
We have just announced the new IBM InfoSphere Data Replication v 11.3.3 (IIDR).
InfoSphere® Data Replication V11.3.3 offers an easy-to-use, highly scalable, low-impact, and enterprise-ready data replication platform. This release includes the following:
InfoSphere Data Replication V11.3.3 (for IBM® i, Linux™, UNIX™, and Windows™)
InfoSphere Change Data Delivery V11.3.3
InfoSphere Data Replication for Apache Hadoop V11.3.3
InfoSphere Data Replication V11.3.3 is a... [More]
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
Step 3: Once you validate the instance entry is in 'db2greg' output and not in 'db2set' ouput, as root, go to... [More]
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".
Recently came across this question about dropping members that reside in the same physical server.
Consider the db2instance -list output like this.
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