KateDawson 060001TQ2C Visits (1138)
100 Tech Tips: #74: Stay informed about upcoming EOS dates
Do you know how to check the End of Support (EOS) date for your products? All EOS dates are available on the IBM Product Lifecycle page. Since we have a number of important products reaching EOS on April 30, 2012, we thought now would be a great time to remind you to check the Product Lifecycle page regularly or sign up to receive updates through RSS.
Click here to view a summary of Information Management Products listed by their End of Support dates.
Here is a summary of some of the key products reading EOS on April 30, 2012:
dlang 060001V98P Visits (1607)
Does runstats seem to be running longer than usual? There could be a few explinations for this. First you should consider if there is a significant amount of data than before, this could just be normal. If you are in a situation where you will be working with a larger volume of data, you may consider different sampling options with runstats. When collecting detailed statistics collection can consume considerable CPU and memory for large tables, and may take longer than planned. The various sampling options can provide accurate statistics with less resource usage.
However, there may be a chance that the runstats is taking longer simply because the data in the database is highly fragmented. If a reorganization of the data has not been done in a long time, and the runstats utility seems to take longer and longer, this may be an indication of highly fragmented data. If you are unsure that a reorg would be of benefit you can run the reorgchk tool. You may likely find that after a reorg of your key tables, the runstats performance should improve.
I/O is one of the most expensive operations that happens. Once a table is reorg-ed, the number of small, scattered i/o should go down, and larger, sequential i/o can happen, which would drastically improve IO. Often the number of trips made to storage will be a big factor in the throughput. With fewer, trips, getting large chunks of data, the throughput will go up. When making a lot of small i/o requests (and bouncing around the disk) we have all the overhead with making and processing the storage request and you can expect this type of frequent activity can consume alot of time. If there are frequent DML activities like inserts/deletes, fragmentation is going to happen, and that will effect the I/O effectiveness of the runstats if reorg maintenance isn't done.
KateDawson 060001TQ2C Visits (1541)
Back in December 2011, when we were way back at tip #44, we posted a summary of our Technical Support tips categorized by product/interest area.
Since we are now about 75% complete on our goal of posting 100 Tech Tips by June 16 2012 (one tip for every year IBM has been in business), we have updated our summary and below you'll find links to 75 pieces of valuable technical support information!!
We hope you find this list useful. Please share it with colleagues who may benefit from this list and let us know if you'd like to see a particular tip by leaving a comment on this blog post.
100 Tech Tips: #76: BigInsights V1.3 Fix Pack 1 AQL file with no output views is not automatically compiled when dependent AQL files are compiled
wbratton 120000E4TY Visits (800)
100 Tech Tips: #76: BigInsights V1.3 Fix Pack 1 AQL file with no output views is not automatically compiled when dependent AQL files are compiled.
When Text Analytics Project A depends on Text Analytics Project B, compiling Project B does not automatically trigger the compilation of Project A when Project A contains an AQL with no output views. Click here for more information...
ubektas 27000478GM Visits (863)
IBM InfoSphere Information Server MustGather documents aid in problem determination and save time resolving Problem Management Records (PMRs).
You can gather the necessary information to improve the accuracy and completeness of the data collection process. This gathering of information can be done as follows:
* Automated gathering - Use the ISALite for InfoSphere Information Server collectors to gather log files and other artifacts. Refer to the link for automated information gathering.
* Manual gathering - Contact your IBM customer support representative before you gather information as outlined in the MustGather link for IBM InfoSphere Information Server document.
0XST_John_Gera 2700020XST Visits (1108)
While running redistribute in a DPF environment, the following suggestions may help improve redistribute performance
Starting DB2 V9.5 FP1 and V9.7 GA, the "NOT ROLLFORWARD RECOVERABLE" parameter was introduced. With this option logging is minimal because the data is moved in bulk instead of by internal insert and delete operations which improves performance. (But please consider recovery implications as there is minimal logging.)
Some other options to help performance would be to tune the following parameters:
Specifies the number of 4 KB pages to use as buffered space for transferring data within the utility. This command parameter can be used only when the NOT ROLLFORWARD RECOVERABLE parameter is also specified.
Set this parameter to at least 100000 (approximately 400 MB). If you have additional memory then set it to a value of 180000. If a DATA BUFFER value is not specified, an intelligent default is calculated by the utility at runtime at the beginning of processing each table. (By default it is 50% of the memory available in the utility heap at the time redistribution)
The util_heap_sz is critical to the data movement processing between database partitions – allocate as much memory as possible to util_heap_sz for the duration of the redistribution (If DATA BUFFER parameter is set, set util_heap_sz to about 10% greater to that of DATA BUFFER value. If DATA BUFFER is not set, set util_heap_sz to a very high value, such as 200000 or greater depending on the available memory)
Sufficient sortheap is required, if index rebuild is done as part of the redistribution. Set to a value between 10000 and 20000
This parameter is an instance-wide soft limit on the total amount of memory that can be consumed by private sorts at any given time. This parameter should be set to at least two times the largest sortheap defined for any database within the inst
MaryKKassey 2700055CKK Visits (1230)
Here is a list of license documents that may help resolve the DB2 license errors you encounter with DB2 on Linux, Unix and Windows:
Useful DB2 license references from our Information Center:
License issues- Contains nodelock file location
Registering a DB2 product or feature license key using the db2licm command
Registering a DB2 database product or feature license key using the License Center
Checking DB2 license compliance
100 Tech Tips: #80: Supported combinations of DB2 Client and DB2 Server versions on Linux, Unix and Windows
Slakshmi 060001JD9S Visits (1284)
Looking for supported combination of DB2 Client and DB2 Server versions on Linux,Unix and Windows?
For DB2 V9.7 on LUW:
For DB2 V9.5 on LUW:
Adam Koile 270000GAYM Visits (1480)
Looking for some help on how to resolve the error SQL1092N on Windows using Domain ID's . Then you're in luck because we have put together the following tech doc to help you with that:
Still seeing the error or have questions about it, then please feel free to comment below.
KateDawson 060001TQ2C Visits (1233)
100 Tech Tips: #82: Find IBM Netezza on the Support Portal!
Attention IBM Netezza Clients: You can now search for and select IBM Netezza in the Support Portal to find IBM Netezza information, technical documents, sign up for automated notifications about your Appliance, and open service requests.
Click this link to access the Support Portal with IBM Netezza already selected in your product list.
As you become familiar with the Portal, here are a few tips:
The following images are from the Support Home tab of the Portal.