Resource Info: ODBC DSN configuration with db2cfexp and db2cfimp utilities on Windows Operating System
MaryKKassey 2700055CKK Visits (476)
Export from 64-bit windows - machine 1, import to 64-bit Windows- machine 2:
- db2cfexp with template/backup option on machine1
When using the Configuration Assistant on Windows 64-bit platforms, ODBC Data Sources can be configured only for 64-bit applications.
- db2cli32.exe is part of DB2 64-bit products, it is used to register 32-bit ODBC DSN's on 64-bit Windows.
- 32-bit DB2 products come with only db2cli.exe which is used to register 32-bit ODBC DSN.
KateDawson 060001TQ2C Visits (376)
We did it... we reached a million views! And for that, we want to thank our amazing group of readers who make this blog successful.
Another big thanks goes to our many talented content contributors, who share their product expertise with us through this blog!
But, like all good IBMers, we're always driving to our next milestone and we want to hear from you to help us get there! What would you like to see from this blog? Do you have ideas for topics or technical challenges you'd like us to address? Add a comment to this post and we'll see about getting the posts written for you.
And finally, here are a few links to our most popular posts over time:
Thanks again and happy reading!
P.S. Did you know we are also active on Facebook, Twitter, and in the developerWorks product forums?
wilhap 0600007F3T Visits (333)
At present most of the Informix configuration parameters can be modified dynamically. Typically, users run 'onmode -wf' or 'onmode -wm' command to dynamically change a specific configuration parameter. But there may be a situation when you need to modify multiple parameters at once. For example, you have ten Informix instance and want to tune some of SQL statement cache configuration parameters on all the Informix instances.
Now, you can import a configuration file using onmode command to change multiple configuration parameter at once. Importing a configuration file is often faster and more convenient than changing one configuration parameter at a time. You can use the 'onmode -wi' command to import a file that contains new values for multiple configuration parameters. If the parameters are dynamically tunable, the database server applies the new values. The import operation ignores the configuration parameters in the file that are not dynamically tunable and if the new parameter values same as the existing value.
However, you need to keep a note hare that an import operation changes the values of configuration parameters only in the memory. It does not modify the values in the ONCONFIG file on disk.
Let's take the same example as before, modify some of SQL statement cache configuration parameters using import operation. Currently, you have following settings:
You create a 'onconfig.new' file under '/tmp' directory with following values to modify the configuration parameters:
Next, you run the following command to import configuration values from file named 'onconfig.new' in the the /tmp directory:
The above command generates appropriate messages on screen and the message log. Following is an excerpt of the message log:
You can notice only three out of the five parameters has been changed because either those are not dynamically tunable or using same existing value.
As the 'onmode -wi' command import a configuration file, you can also export configuration parameters from memory to a file using 'onmode -we' command.
-- Thanks Sanjit
wilhap 0600007F3T Visits (282)
The following Informix information centers will be sunset in the near future:
ubektas 27000478GM Visits (434)
InfoSphere® QualityStage® Address Verification Interface (AVI) V10.0 enables you to standardize, verify, correct, and enhance international address information.
IBM® InfoSphere® QualityStage® Address Verification Interface parses, validates, and transliterates address data for over 240 countries or regions from around the world.
ubektas 27000478GM Visits (450)
Do you know that there is a new process for submitting enhancement requests against InfoSphere Information Server ?.
And you no longer need to open a support ticket to accomplish this.
The following URLs contain FAQ and video tutorial on various RFE operations.
JunGuo 270006BN0K Visits (243)
gorddbds 060001JCXS Visits (440)
DB2 LUW is capable of running stored procedures and functions coded in several languages. Among these languages is Java. Since Java stored procedures and functions, (collectively referred to as routines) require a JVM there are some configuration settings that are specific to this type of routine. DB2 comes with a JDK and by default it is this JDK that is used to run Java routines. It is possible to alter DB2 to use another JDK to run Java routines. JDKs that are supported to run routines are documented in the DB2 infocenter for each release.
The Version 10.1 page is located at the following URL.
The JDK DB2 uses is specified by the JDK_PATH dbm cfg variable and by default is set to the instance's JDK location.
The following URL documents this variable for version10.1
In addition to the JDK you can specify how much Java Heap each JVM will use. If you believe your routine workload may require more or less Java Heap than the default, you can modify the amount of heap allocated by changing the dbm cfg variable JAVA_HEAP_SZ to the desired value.
The following URL documents the JAVA_HEAP_SZ variable for version10.1
The JVM for DB2 Java routines is created per process. Java routines that have been created as “threadsafe” can run with other routines in a single process and use a single JVM. If there is a Java routine that is expected to use a large amount of resources. You may wish to create this routines as “not threadsafe”. This will cause it to be run in its own process and have all the resources of the JVM for its use.
The following URLs document the Create Procedure and Create function statements for 10.1
Create Scalar Function
Create Table Function
gorddbds 060001JCXS Visits (392)
DB2 LUW has two basic edition classifications Clients and Servers. Clients include drivers and full DB2 clients. Servers include both DB2 and DB2 Connect servers. DB2 Clients do not require a license to use when connecting to DB2 LUW servers. DB2 servers include DB2 client code and if no permanent license is installed the server functionality will be unavailable once the trial period expires but the client code may still be used. To license purchased DB2 LUW server products two licenses will need to be installed.
One license referred to as the base license is shipped with the product and identifies the specific DB2 product. This license does not enable server or DB2 Connect functionality. DB2 LUW editions will automatically enter try and buy mode if no product licenses are detected and the base license is installed. This mode will allow the DB2 server editions to run for 90 days after which time the trial will end and only client functionality will be available. The base license is usually automatically installed with DB2.
The second license file is the permanent license and represents the license agreement that is purchased with the product. Since DB2 LUW can be licensed in more than one way there is more than one type of permanent license file. Each license type uses a different permanent license file. The names of the license files and what licenses they apply to are documented at the following infocenter URLs.
Once a permanent license is installed, the db2licm -l command will return Permanent for the Expiry date. If any value other than permanent returns there is no permanent license installed.
Permanent licenses are available on Passport Advantage. The following URL documents locating and downloading a permanent license.
Swati Thorve 270004FTYS Visits (357)
Recently I came across a PMR, customer was using sysp
We cannot delete one policy unless delete all of them:
db2 "call sysi
and then install the default policy:
db2 "call sysi
More details on sysinstallobjects objects here.
Thank you for reading!
Resource Info: Memory Limitations for DB2 Workgroup Server Restricted License for different versions
MaryKKassey 2700055CKK Visits (384)
Do you know the instance memory limitations for DB2 Workgroup Server Restricted License for different DB2 versions?
First of all, I would like to explain what DB2 Workgroup Server Edition (WSE) Restricted License (db2wse_o.lic) means. Its nothing but that your DB2 database product was obtained as part of another IBM® product. In this case, the license terms of the bundling product takes precedence over the usual DB2 Version Workgroup Server Edition license terms.
The DB2 license command 'db2licm -l' will display the following output:
JunGuo 270006BN0K Visits (265)
JunGuo 270006BN0K Visits (262)
Alfresco Connector is now available in Fix Central. The customer distribution file can be downloaded at Fix Central
Overview of Changes
Slakshmi 060001JD9S Visits (583)
Looking for a way to test Automatic Client Re-route using a simple JDBC program that uses IBM data server driver for JDBC & SQLJ (JCC) & JDBC DriverManager Connection?
Here are the steps to follow:
Step 1: UPDATE ALTERNATE SERVER INFORMATION in BOTH PRIMARY & STANDBY SERVERS:
Lets assume that following are the Primary and Standby Server's hostnames and Port numbers.
a) On DB2 Primary system:
Step 2: UPDATE THE JDBC CONNECTION URL WITH THE clie
Sample program to test the automatic Client re-route:
To compile the program:
Step 3: Once you run the above program, it connects to the primary. On the DB2 server, do a failover to the standby. Now the application will automatically re-route the connection to the former standby.
0XST_John_Gera 2700020XST Visits (998)
There are situations where in a HADR environment, transaction on the Primary are bloc
Brewer's CAP Theorem:
Brewer's CAP theorem states that, in a Distributed Computer System, we can guarantee only two of the following simultaneously:
- Consistency (all nodes see the same data at the same time)
- Availability (a guarantee that every request receives a response about whether it was successful or failed)
- Partition tolerance (the system continues to operate despite arbitrary message loss or failure of part of the system,)
Figure 1. Venn Diagram above shows that there can be only 2 of Consistency(C), Availability (A) or Partition tolerance(P) at a given time
Now putting that in terms of DB2 HADR for a LOGGED OPERATION:
Consistency (C) - Data is the SAME on Primary and Standby
Availability (A) - Clients are ALWAYS able to connect and get a response (i.e no blocking)
Partition Tolerance (P) - Netw
Basically the theorem says that in the presence of a partition event (like a network outage between the 2 hadr nodes) there MUST BE a tradeoff between availability and consistency.
HADR sync modes are the primary dial to control C vs. A tradeoffs:
Transaction are committed on the Primary after relevant logs have been written to disk on Primary and:
SYNC --> logs have been written to disk on Standby as well ==> Highest C (Data guaranteed on Standby)
NEARSYNC --> Logs are received into memory on Standby ==> More C
ASYNC --> Logs sent to the Standby on the Network (Don't wait for ACK) ==> More A
SUPERASYNC --> Don't wait for Standby!! ==> Highest A (No guarantee)
In SYNC mode, the total time for a log write = Σ (Primary_Log_Write + Log_Send + Standby_Log_Write + Ack_Message)
Figure 2: Shows the various sync modes
Further fine tuning C vs A :
HADR_TIMEOUT --> How long to wait before considering communication failure. Till we reach this time we are still considered PEER ==> More C
HADR_PEER_WINDOW --> In case of communication failure, how long to wait before actually breaking the connection ==> More C
When both HADR_PEER_WINDOW and HADR
Where does DB2_HADR_BUF_SIZE and DB2
DB2_HADR_BUF_SIZE --> For increasing the HADR standby log receive buffer size
Higher DB2_HADR_BUF_SIZE and DB2
In situation where we see the Transaction being blocked on the Primary, it is because the HADR setup is in favor of C vs A. For example:
1. Sync Mode = SYNC/NEARSYNC
2. There is a Partition event (standby log buffer full/network failure)
Then we see blocking on Primary i.e no A. In such situations we can tune:
- DB2_HADR_BUF_SIZE - (to get CA)
Note: Starting v10.1 we have introduced a new parameter 'HADR_SPOOL_LIMIT'. Log data that is sent by the primary is written, or spooled, to disk on the standby if it falls behind in log replay. The standby can later on read the log data from disk.
Bada Bing Bada Boom!! :)