From Peter Bradford @scend we have:
#1 We made requests for enhancements (RFEs) public!
#2: DB2 Developer-C! All DB2 features, free for development, a MySQL substitute! Download 6/22
#3: The new “Download & Go” installation experience, available with Developer-C Download 6/2. Download a platform specific binary. Small download, less than 15 minutes to install. Install reduced to 3 clicks and User/Password input only.
#4: We will support DB2 V11 on Solaris Sparc later this year with our V22.214.171.124 release, by 12/15/17 (if not sooner)
#5: New “Continuous Support” offering for customers on DB2 V9.7 and V10.1!
How To and Workaround assistance, no new defect fixes
This still provides existing fixed but no new custom special builds or codes fixed
If you have questions contact
Twitter: @db2support or https://twitter.com/db2_support
Just heard someone at IDUG EMEA 2016 asking about how to setup DB2 LUW shadow tables.
This will depend upon DB2 Version,you also need a compatible CDC (Infosphere Replication) version,check via Finding System Requirements for IBM Software Products.
The steps are at http://www.smooth1.co.uk/db2/cancun.html#1.1
NOTE: This was written when the feature first came out DB2 LUW 10.5 FP4.
CDC Components to download were:
- InfoSphere CDC for DB2 for LUW
- InfoSphere CDC Access Server
- InfoSphere CDC Management Console
IBM has a Software Product Compatibility Reports facility.
db2look -m -r
The “-r” option is used to generate db2look output without runstats command output. However, current db2look code cannot reset SYSSTAT.COLUMNS and SYSSTAT.INDEXES when -r is applied. As a result, SQL1227N sometimes occur when applying the mimic when COLCARD etc, and CARD for the table is inconsistent. In db2look up to version in V10.5 please use db2look -m without -r option or insert resetting SYSSTAT.COLUMNS and SYSSTAT.INDEXES manually in db2look output with “-m” and “-r”. This limitation will be changed in releases later than V10.5. In most cases it should not cause SQL1227N error, but still the error can occur when the statistics on the source system is inconsistent. Here are examples:
Why COLCARD is sometimes bigger than CARD after RUNSTATS?
Runstats may update unexpected HIGH2KEY and LOW2KEY statistic values which may cause SQL1227N
As documented in above technotes, you can bypass the error by setting following undocumented registry variable even if the statistics are inconsistent:
recycle the instance
This registry variable can be used from 9.7FP9/10.1FP4/10.5.
DB2 11.1 has been announced with a download date of June 15 2016
Potential new features are:
Enterprise Encryption supports Centralized Key Managers (KMIP)
Support for Encryption to use KMIP 1.1 with a Centralized Key Manager
– update dbm cfg using keystore_type kmip
– update dbm cfg using keystore location /home/justdave/isklm.cfg
Config file contains host, port number etc.
Technology Preview of support for Hardware Security Modules
Zero Data Loss HADR
More online management
More platforms supported
Power Linux (LE) supported
Virtualization for RDMA (x86) supported
Very Large Database Performance
DB2 9.7 and higher can be directly upgraded to DB2 11.1 (support for upgrades from 3 releases back)
Online upgrades with no need for an offline backup.
A recovery procedure including roll-forward thtough a database upgrade exists. This does not include DPF and requires upgrading from DB2 10.5 FP7 or higher.
Steamlined HADR upgrade
HADR environments can be upgraded with need to re-initialized the secondary. This does not apply to Purescale and requires upgrading from DB2 10.5 FP7 or higher.
MPP supports BLU
DPF renamed to MPP
Faster ELT/ETL Performance
More Query Workloads Optimized
More functions supported
OLAP+BLU Performance increased
Multi-Lingual SQL Advances
Support for European Languages
DB2 10.5 Fixpack 6 is out
“Fix Pack 6 does not contain new enhancements, and there were no changes to the existing functionality. This fix pack and future fix packs will deliver only APAR and security vulnerability fixes.”
Managing GSKit Master Keys