amccarl 100000AY2G Visits (489)
wilhap 0600007F3T Visits (204)
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
kdillon 20000024FQ Visits (325)
kdillon 20000024FQ Visits (302)
Do you want more details on working with IBM Support? How about using th
Resource Info: how to create a Rule in Information Analyzer that joins a table to itself by creating a virtual table
ubektas 27000478GM Visits (773)
ubektas 27000478GM Visits (892)
ubektas 27000478GM Visits (1133)
the technote that lists some suggestions about how to address this problem.
ubektas 27000478GM Visits (728)
This a great resource to understand how to use APT_DUMP_SCORE and how to read scores in parallel jobs. This document written by the Development team uses a example to show the sections of a typical score and includes descriptions for every section, partition and operator notation, and even suggested self-training excercises
Please refer to the published technote
tfreund 270003NCBN Visits (739)
tfreund 270003NCBN Visits (746)
The IBM Software Accelerated Value Program delivers a proactive, cost-reducing, and productivity enhancing advisory service. The program pairs you with an assigned team who builds a foundational understanding of your overall environment. Through that understanding, the trusted partner works to facilitate faster deployment, lifecycle leadership, risk mitigation, and more by identifying ways to improve your environment, staff skill set, and processes.
To learn more click on the link.
Slakshmi 060001JD9S Visits (1961)
Here it is with simple step-by-step instructions!!!
On the DB2 server:
1) Set the DB2COMM registry variable to tcpip.
2) Verify whether it is set correctly using the following command:
3)Check the DBM CFG for SVCENAME parameter and make a note of it.
db2 get dbm cfg
TCP/IP Service name (SVCENAME) = db2c_db2inst1
(Either use this name (db2c_db2inst1) or find the corresponding port number from /etc/services file)
On the DB2 Client:
From the DB2 Command line:
Run the following commands:
1) Catalog the tcpip node:
db2 catalog tcpip node <nodename> remote <Hostname or ip address of the DB2 server> server <SVCENAME or Corresponding portnumber>
For example: db2 catalog tcpip node mynode remote myse
2) Catalog the remote DB2 database:
db2 catalog db <dbname> as <db alias> at node <nodename>
For example: db2 catalog db Sample as testsamp at node mynode
3) Clear the directory cache:
4) To check the node and database directory.
db2 list node directory.
db2 list db directory.
5) To test the connection:
db2 connect to <dbalias> user <username> using <password>
For example: db2 connect to testsamp user newuser using newpwd1
Voila!!! Now you can connect to a remote server from your DB2 Client!