The Quick Tour is not available on DB2 for Linux.
The Quick Tour is optimized to run with small system fonts. You may have to adjust your Web browser's font size to correctly view the Quick Tour on OS/2. Refer to your Web browser's help for information on adjusting font size. To view the Quick Tour correctly (SBCS only), it is recommended that you use an 8-point Helv font. For Japanese and Korean customers, it is recommended that you use an 8-point Mincho font. When you set font preferences, be sure to select the "Use my default fonts, overriding document-specified fonts" option in the Fonts page of the Preference window.
In some cases the Quick Tour may launch behind a secondary browser window. To correct this problem, close the Quick Tour, and follow the steps in 1.8, Error Messages when Attempting to Launch Netscape.
When launching the Quick Tour, you may receive a JavaScript error similar to the following:
JavaScript Error: file:/C/Program Files/SQLLIB/doc/html/db2qt/index4e.htm, line 65: Window is not defined.
This JavaScript error prevents the Quick Tour launch page, index4e.htm, from closing automatically after the Quick Tour is launched. You can close the Quick Tour launch page by closing the browser window in which index4e.htm is displayed.
To download installation packages for all supported DB2 clients, which include all the pre-Version 7.1 clients, connect to the IBM DB2 Client Application Enabler Pack Web site at http://www.ibm.com/software/data/db2/db2tech/clientpak.html
On Windows 2000, when installing over a previous version of DB2 or when reinstalling the current version, ensure that the recovery options for all of the DB2 services are set to "Take No Action".
DB2 Version 7.1 is available in English, French, German, Italian, Spanish, Brazilian Portuguese, Japanese, Korean, Simplified Chinese, Traditional Chinese, Danish, Finnish, Norwegian, Swedish, Czech, Dutch, Hungarian, Polish, Turkish, Russian, Bulgarian and Slovenian.
On UNIX-based platforms, the DB2 product messages and library can be installed in several different languages. The DB2 installation utility will lay down the message catalog filesets into the most commonly used locale directory for a given platform as shown in the following chart.
| Operating System | AIX | HPUX | Solaris | Linux | SGI | Dynix | ||||||
| Language | Locale | Cde Pg | Locale | Cde Pg | Locale | Cde Pg | Locale | Cde Pg | Locale | Cde Pg | Locale | Cde Pg |
| French | fr_FR Fr_FR | 819 850 | fr_FR.iso88591 fr_FR.roman8 | 819 1051 | fr | 819 | fr | 819 |
|
| fr | 819 |
| German | de_DE De_DE | 819 850 | de_DE.iso88591 de_DE.roman8 | 819 1051 | de | 819 | de | 819 |
|
| de | 819 |
| Italian | it_IT It_IT | 819 850 | it_IT.iso88591 it_IT.roman8 | 819 1051 | it | 819 | it | 819 |
|
| es | 819 |
| Spanish | es_ES Es_ES | 819 850 | es_ES.iso88591 es_ES.roman8 | 819 1051 | es | 819 | es | 819 |
|
|
|
|
| Brazilian Portu- guese | pt_BR | 819 |
|
| pt_BR | 819 | pt_BR | 819 |
|
|
|
|
| Japanese | ja_JP Ja_JP | 924 932 | ja_JP.eucJP | 954 | ja | 954 | ja_JP.ujis | 954 |
|
| ja_JP.EUC | 954 |
| Korean | ko_KR | 970 | ko_KR.eucKR | 970 | ko | 970 |
|
| ko_KO.euc | 970 |
|
|
| Simplified Chinese | zh_CN Zh_ CN.GBK | 1383 1386 | zh_CN.hp15CN | 1383 | zh | 1383 | zh zh_CN.GBK | 1386 |
|
|
|
|
| Traditional Chinese | zh_TW Ah_TW | 964 950 | zh_TW.eucTW zh_TW.big5 | 964 950 | zh_TW zh_TW.BIG5 | 964 950 |
|
|
|
|
|
|
| Danish | da_DK Da_DK | 819 850 | da_DK.iso88591 da_DK.roman8 | 819 1051 | da | 819 |
|
|
|
|
|
|
| Finnish | fi_FI Fi_FI | 819 850 | fi_FI.iso88591 fi_FI.roman8 | 819 1051 | fi | 819 |
|
|
|
|
|
|
| Norwegian | no_NO No_NO | 819 850 | no_NO.iso88591 no_NO.roman8 | 819 1051 | no | 819 |
|
|
|
|
|
|
| Sweden | sv_SE Sv_SE | 819 850 | sv_SE.iso88591 sv_SE.roman8 | 819 1051 | sv | 819 |
|
|
|
|
|
|
| Czech | cs_CZ | 912 |
|
|
|
|
|
|
|
|
|
|
| Hungarian | hu_HU | 912 |
|
|
|
|
|
|
|
|
|
|
| Polish | pl_PL | 912 |
|
|
|
|
|
|
|
|
|
|
| Dutch | nl_NL Nl_NL | 819 850 |
|
|
|
|
|
|
|
| nl | 819 |
| Turkish | tr_TR | 920 |
|
|
|
|
|
|
|
|
|
|
| Russian | ru_RU | 915 |
|
|
|
|
|
|
|
|
|
|
| Bulgarian | bg_BG | 915 | bg_BG.iso88595 | 915 |
|
|
|
|
|
|
|
|
| Slovenian | sl_SI | 912 | sl_SI.iso88592 | 912 | sl_SI | 912 |
|
|
|
|
|
|
If your system uses the same code pages but different locale names than those provided above, you can still see the translated messages by creating a link to the appropriate message directory.
For example, if your AIX machine default locale is ja_JP.IBM-eucJP and the codepage of ja_JP.IBM-eucJP is 954, you can create a link from /usr/lpp/db2_07_01/msg/ja_JP.IBM-eucJP to /usr/lpp/db2_07_01/msg/ja_JP by issuing the following command:
ln -s /usr/lpp/db2_07_01/msg/ja_JP /usr/lpp/db2_07_01/msg/ja_JP.IBM-eucJP
After the execution of this command, all DB2 messages will come up in Japanese.
The Control Center, Control Center Help and documentation filesets are placed in the following directories on the target workstation:
Control Center filesets are in Unicode codepage. Documentation and Control Center help filesets are in a browser-recognized codeset. If your system uses a different locale name than the one provided, you can still run the translated version of Control Center and see the translated version of help by creating links to the appropriate language directories.
For example, if your AIX machine default locale is ja_JP.IBM-eucJP, you can create links from /usr/lpp/db2_07_01/cc/ja_JP.IBM-eucJP to /usr/lpp/db2_07_01/cc/ja_JP and from /usr/lpp/db2_07_01/doc/ja_JP.IBM-eucJP to /usr/lpp/db2_07_01/doc/ja_JP by issuing the following commands:
After the execution of these commands, the Control Center and help text will come up in Japanese.
The DB2 UDB family of products includes a number of features that make the products more accessible for people with disabilities. These features include:
The DB2 Control Center can be operated using only the keyboard. Menu items and controls provide access keys that allow users to activate a control or select a menu item directly from the keyboard. These keys are self-documenting, in that the access keys are underlined on the control or menu where they appear.
In UNIX-based systems, the position of the keyboard focus is highlighted, indicating which area of the window is active and where the user's keystrokes will have an effect.
The DB2 Control Center has a number of features that enhance the user interface and improve accessibility for users with low vision. These accessibility enhancements include support for high-contrast settings and customizable font properties.
The Control Center interface supports the high-contrast-mode option provided by the operating system. This feature assists users who require a higher degree of contrast between background and foreground colors.
The Control Center interface allows users to select the color, size, and font for the text in menus and dialog windows.
Users do not need to distinguish between colors in order to use any of the functions in this product.
The user can opt to receive alerts through audio or visual cues.
The DB2 Control Center interface is compatible with screen reader applications such as Via Voice. When in application mode, the Control Center interface has the properties required for these accessibility applications to make onscreen information available to blind users.
Documentation for the DB2 family of products is available in HTML format. This allows users to view documentation according to the display preferences set in their browsers. It also allows the use of screen readers and other assistive technologies.
The name of DB2 Everywhere has changed to DB2 Everyplace.
If you encounter the following error messages when attempting to launch Netscape:
Cannot find file <file path> (or one of its components).
Check to ensure the path and filename are correct and that all
required libraries are available.
Unable to open "D:\Program Files\SQLLIB\CC\..\doc\html\db2help\XXXXX.htm"
you should take the following steps to correct this problem on Windows NT, 95, or 98 (see below for what to do on Windows 2000):
If you encounter the messages on Windows 2000, you should take the following steps:
For all platforms except Windows, a mouse is required to use the tools.
We recommend that you use Microsoft Internet Explorer on Windows 2000.
If you use Netscape, please be aware of the following:
If Netscape Navigator is already open and displaying either a local DB2 HTML document or an external Web site, an attempt to open an external Web site from the Information Center will result in a Netscape error. The error will state that "Netscape is unable to find the file or directory named <external site>."
To work around this problem, close the open Netscape browser before opening the external Web site. Netscape will restart and bring up the external Web site.
Note that this error does not occur when attempting to open a local DB2 HTML document with Netscape already open.
On some systems, the Information Center can be slow to start if you invoke it using the Start Menu, First Steps, or the db2ic command. If you experience this problem, start the Control Center, then select Help --> Information Center.
Acrobat Reader is only offered in English on UNIX based platforms, and errors may be returned when attempting to open PDF files with language locales other than English. These errors suggest font access or extraction problems with the PDF file, but are actually due to the fact that the English Acrobat Reader cannot function correctly within a UNIX non-English language locale.
To view such PDF files, switch to the English locale by performing one of the following steps before launching the English Acrobat Reader:
LANG=C;export LANG
This approach will ensure correct behavior when Acrobat Reader is launched by other applications, such as Netscape Navigator, or an application help menu.
For further information, contact Adobe Systems (http://www.Adobe.com).
Because the DB2 Run-time Client does not have the full set of bind files, the binding of GUI tools cannot be done from the DB2 Run-time Client, and can only be done from the DB2 Administration Client.
DB2 Universal Database Version 7.1 for Solaris Version 2.6 requires patch 106285-02 or higher, in addition to the patches listed in the DB2 for UNIX Quick Beginnings manual.
CPU versions previous to UltraSparc are not supported.
If you are having problems searching the DB2 online information on your Solaris system, check your system's kernel parameters in /etc/system. Here are the minimum kernel parameters required by DB2's search system, NetQuestion:
semsys:seminfo_semmni 256 semsys:seminfo_semmap 258 semsys:seminfo_semmns 512 semsys:seminfo_semmnu 512 semsys:seminfo_semmsl 50 shmsys:shminfo_shmmax 6291456 shmsys:shminfo_shmseg 16 shmsys:shminfo_shmmni 300
To set a kernel parameter, add a line at the end of /etc/system as follows:
set <semaphore_name> = value
You must reboot your system for any new or changed values to take effect.
The Control Center must be installed on an HPFS-formatted drive.
Search discovery is only supported on broadcast media. For example, search discovery will not function through an ATM adapter. However, this restriction does not apply to known discovery.
When adding nodes to a partitioned database that has one or more system temporary table spaces with a page size that is different from the default page size (4 KB), you may encounter the error message: "SQL6073N Add Node operation failed" and an SQLCODE. This occurs because only the IBMDEFAULTBP buffer pool exists with a page size of 4 KB when the node is created.
For example, you can use the db2start command to add a node to the current partitioned database:
DB2START NODENUM 2 ADDNODE HOSTNAME newhost PORT 2
If the partitioned database has system temporary table spaces with the default page size, the following message is returned:
SQL6075W The Start Database Manager operation successfully added the node. The node is not active until all nodes are stopped and started again.
However, if the partitioned database has system temporary table spaces that are not the default page size, the returned message is:
SQL6073N Add Node operation failed. SQLCODE = "<-902>"
In a similar example, you can use the ADD NODE command after manually updating the db2nodes.cfg file with the new node description. After editing the file and running the ADD NODE command with a partitioned database that has system temporary table spaces with the default page size, the following message is returned:
DB20000I The ADD NODE command completed successfully.
However, if the partitioned database has system temporary table spaces that are not the default page size, the returned message is:
SQL6073N Add Node operation failed. SQLCODE = "<-902>"
One way to prevent the problems outlined above is to run:
DB2SET DB2_HIDDENBP=16
before issuing db2start or the ADD NODE command. This registry variable enables DB2 to allocate hidden buffer pools of 16 pages each using a page size different from the default. This enables the ADD NODE operation to complete successfully.
Another way to prevent these problems is to specify the WITHOUT TABLESPACES clause on the ADD NODE or the db2start command. After doing this, you will have to create the buffer pools using the CREATE BUFFERPOOL statement, and associate the system temporary table spaces to the buffer pool using the ALTER TABLESPACE statement.
When adding nodes to an existing nodegroup that has one or more table spaces with a page size that is different from the default page size (4 KB), you may encounter the error message: "SQL0647N Bufferpool "" is currently not active.". This occurs because the non-default page size buffer pools created on the new node have not been activated for the table spaces.
For example, you can use the ALTER NODEGROUP statement to add a node to a nodegroup:
DB2START CONNECT TO mpp1 ALTER NODEGROUP ng1 ADD NODE (2)
If the nodegroup has table spaces with the default page size, the following message is returned:
SQL1759W Redistribute nodegroup is required to change data positioning for objects in nodegroup "<ng1>" to include some added nodes or exclude some drop nodes.
However, if the nodegroup has table spaces that are not the default page size, the returned message is:
SQL0647N Bufferpool "" is currently not active.
One way to prevent this problem is to create buffer pools for each page size and then to reconnect to the database before issuing the ALTER NODEGROUP statement:
DB2START CONNECT TO mpp1 CREATE BUFFERPOOL bp1 SIZE 1000 PAGESIZE 8192 CONNECT RESET CONNECT TO mpp1 ALTER NODEGROUP ng1 ADD NODE (2)
A second way to prevent the problem is to run:
DB2SET DB2_HIDDENBP=16
before issuing the db2start command, and the CONNECT and ALTER NODEGROUP statements.
Another problem can occur when the ALTER TABLESPACE statement is used to add a table space to a node. For example:
DB2START
CONNECT TO mpp1
ALTER NODEGROUP ng1 ADD NODE (2) WITHOUT TABLESPACES
ALTER TABLESPACE ts1 ADD ('ts1') ON NODE (2)
This series of commands and statements generates the error message SQL0647N (not the expected message SQL1759W).
To complete this change correctly, you should reconnect to the database after the ALTER NODEGROUP... WITHOUT TABLESPACES statement.
DB2START
CONNECT TO mpp1
ALTER NODEGROUP ng1 ADD NODE (2) WITHOUT TABLESPACES
CONNECT RESET
CONNECT TO mpp1
ALTER TABLESPACE ts1 ADD ('ts1') ON NODE (2)
Another way to prevent the problem is to run:
DB2SET DB2_HIDDENBP=16
before issuing the db2start command, and the CONNECT, ALTER NODEGROUP, and ALTER TABLESPACE statements.
During migration, error entries in the db2diag.log file (database not migrated) appear even when migration is successful, and can be ignored.
Memory windows is for users on large HP 64-bit machines, who want to take advantage of greater than 1.75 GB of shared memory for 32-bit applications. Memory windows makes available a separate 1 GB of shared memory per process or group of processes. This allows an instance to have its own 1 GB of shared memory, plus the 0.75 GB of global shared memory. If users want to take advantage of this, they can run multiple instances, each in its own window. Following are prerequisites and conditions for using memory windows:
db2instance1 50 db2instance2 60 Note: There can only be a single space between the name and the ID.
db2win db2start db2win db2stop
db2win db2start <== OK db2 connect to db <==SQL1042 db2stop <==SQL1042 db2win db2stop <== OK
=== $HOME/sqllib/db2nodes.cfg for db2instance1 ===
5 host1 0
7 host1 1
9 host2 0
=== $HOME/sqllib/db2nodes.cfg for db2instance2 ===
1 host1 0
2 host2 0
3 host2 1
=== /etc/services.window on host1 ===
db2instance10 50
db2instance11 55
db2instance20 60
=== /etc/services.window on host2 ===
db2instance10 30
db2instance20 32
db2instance21 34
DB2 Spatial Extender functionality will be available in a future release. Updates to DB2 Spatial Extender information will be included in the Release Notes on the DB2 Spatial Extender CD-ROM.
The "Using the DB2 Library" appendix in each book indicates that the SQL Reference is available in PDF format as two separate volumes. This is incorrect.
Although the printed book appears in two volumes, and the two corresponding form numbers are correct, there is only one PDF file, and it contains both volumes. The PDF file name is db2s0x70.
Views become unusable after database migration if the special register USER or CURRENT SCHEMA is used to define a view column. For example:
create view v1 (c1) as values user
In Version 5, USER and CURRENT SCHEMA were of data type CHAR(8), but since Version 6, they have been defined as VARCHAR(128). In this example, the data type for column c1 is CHAR if the view is created in Version 5, and it will remain CHAR after database migration. When the view is used after migration, it will compile at run time, but will then fail because of the data type mismatch.
The solution is to drop and then recreate the view.
If, on a DLFM client, dlfm client_conf fails for some reason, "stale" entries in DB2 catalogs may be the reason. The solution is to issue the following commands:
db2 uncatalog db <dbname> db2 uncatalog node <node alias> db2 terminate
Then try dlfm client_conf again.
It could happen in very rare situations that dlfm_copyd (the copy daemon) does not stop when a user issues a dlfm stop, or there is an abnormal shutdown. If this happens, issue a dlfm shutdown before trying to restart dlfm.
If you are using Simplified Chinese Red Flag Linux Server Version 1.1, visit http://www.redflag-linux.com.cn/downloads.htm to download the Simplified Chinese locale fix.
Before the DB2 DFS Client Enabler is uninstalled, root should ensure that no DFS file is in use, and that no user has a shell open in DFS file space. As root, issue the command:
stop.dfs dfs_cl
Check that /... is no longer mounted:
mount | grep -i dfs
If this is not done, and DB2 DFS Client Enabler is uninstalled, the machine will need to be rebooted.
During DB2 installation, the install may hang after selecting the install type when using a computer with a removable drive that is not attached. To solve this problem, run setup, specifying the -a option:
setup.exe -a
A new DB2 registry variable DB2DOMAINLIST is introduced to complement the existing client authentication mechanism in the Windows NT environment. This variable is used on the DB2 for Windows NT server to define one or more Windows NT domains. Only connection or attachment requests from users belonging to the domains defined in this list will be accepted.
This registry variable should only be used under a pure Windows NT domain environment with DB2 servers and clients running at Version 7.1 (or higher).
For information about setting this registry variable, refer to the "DB2 Registry and Environment Variables" section in the Administration Guide: Performance.
AIX 4.3.3 contains a fix for a libc problem that could cause the AutoLoader to hang during a fork. The AutoLoader is a multithreaded program. One of the threads forks( ) off another process. Forking off a child process causes an image of the parent's memory to be created in the child.
It is possible that locks used by libc.a to manage multiple threads allocating memory from the heap within the same process have been held by a non-forking thread. Since the non-forking thread will not exist in the child process, this lock will never be released in the child, causing the parent to sometimes hang.
Restore of any offline backup that was taken after a database restore, with or without rollforward, will not involve fast reconcile processing. In such cases, all tables with DATALINK columns under file link control will be put in datalink reconcile pending (DRP) state.
If you are using APPC as the communication protocol for remote DB2 clients to connect to your DB2 server and if you use CS/NT as the SNA product, make sure that the following keyword is set correctly in the CS/NT configuration file. This file is commonly found in the x:\ibmcs\private directory.
If you use IGNORE_IF_NOT_DEFINED, you don't have to define a User ID and password in CS/NT.
If you use VERIFY_EVEN_IF_NOT_DEFINED, you have to define User ID and password in CS/NT.
To define the CS/NT User ID and password, perform the following steps:
Following are restrictions that apply to federated systems:
Distributed requests issued within a federated environment are limited to read-only operations.
The published protocol support chart is not completely correct. A Windows 2000 client connected to any OS/2 or UNIX based server using IPX/SPX is not supported. Also, any OS/2 or UNIX based client connected to a Windows 2000 server using IPX/SPX is not supported.
If you are upgrading a previous version of DB2 that is running on your Windows machine, the installation program provides a warning containing a list of processes that are holding DB2 DLLs in memory. At this point, you have the option to manually stop the processes that appear in that list, or you can let the installation program shut down these processes automatically. It is recommended that you manually stop all DB2 processes before installing to avoid loss of data. The best way to ensure that DB2 processes are not running is to view your system's processes through the Windows Services panel. In the Windows Services panel, ensure that there are no DB2 services, OLAP services, or Data warehouse services running.
| Note: | You can only have one version of DB2 running on Windows platforms at any one time. For example, you cannot have DB2 Version 7.1 and DB2 Version 6 running on the same Windows machine. If you install DB2 Version 7.1 on a machine that has DB2 Version 6 installed, the installation program will delete DB2 Version 6 during the installation. Refer to the appropriate Quick Beginnings manual for more information on migrating from previous versions of DB2. |
When installing DB2 UDB Version 7.1 on UNIX based systems, and a DB2 product is already installed, you will need to run the db2iupdt command to update those instances with which you intend to use the new features of this product. Some features will not be available until this command is run.
Some messages will not display on OS/2 running versions of JDK 1.1.8 released prior to 09/99. Ensure that you have the latest JDK Version 1.1.8.
After leaving the DB2 installer on Linux and returning to the terminal window, type the following commands to set the correct environment to run the DB2 Control Center:
su -l <instance name> export JAVA_HOME=/usr/jdk118 export DISPLAY=<your machine name>:0
Then, open another terminal window and type:
su root xhost +<your machine name>
Close that terminal window and return to the terminal where you are logged in as the instance owner ID, and type the command:
db2cc
to start the Control Center.
The Information Catalog Manager component is available in Hebrew and is provided on the DB2 Warehouse Manager for Windows NT CD.
The Hebrew translation is provided in a zip file called IL_ICM.ZIP and is located in the DB2\IL directory on the DB2 Warehouse Manager for Windows NT CD.
To install the Hebrew translation of Information Catalog Manger, first install the English version of DB2 Warehouse Manager for Windows NT and all prerequisites on a Hebrew Enabled version of Windows NT.
After DB2 Warehouse Manager for Windows NT has been installed, unzip the IL_ICM.ZIP file from the DB2\IL directory into the same directory where DB2 Warehouse Manager for Windows NT was installed. Ensure that the correct options are supplied to the unzip program to create the directory structure in the zip file.
After the file has been unzipped, the global environment variable LC_ALL must be changed from En_US to Iw_IL. To change the setting:
The Hebrew version of Information Catalog Manager should now be installed.
To create SQL stored procedures on the server, the application development client (as well as a compiler) must be installed on the server. Otherwise, the create operation will fail with a message indicating that db2udp.dll cannot be loaded.
Host and AS/400 applications cannot access DB2 UDB servers using SNA two phase commit when Microsoft SNA Server is the SNA product in use. Any DB2 UDB publications indicating this is supported are incorrect. IBM Communications Server for Windows NT Version 5.02 or greater is required.
| Note: | Applications accessing host and AS/400 database servers using DB2 UDB for Windows can use SNA two phase commit using Microsoft SNA Server Version 4 Service Pack 3 or greater. |
If you are using Microsoft SNA Server Version 4 SP3 or later, please verify that DB2's SNA SPM started properly after a reboot. Check the \sqllib\<instance name>\db2diag.log file for entries that are similar to the following:
2000-04-20-13.18.19.958000 Instance:DB2 Node:000 PID:291(db2syscs.exe) TID:316 Appid:none common_communication sqlccspmconnmgr_APPC_init Probe:19 SPM0453C Sync point manager did not start because Microsoft SNA Server has not been started. 2000-04-20-13.18.23.033000 Instance:DB2 Node:000 PID:291(db2syscs.exe) TID:302 Appid:none common_communication sqlccsna_start_listen Probe:14 DIA3001E "SNA SPM" protocol support was not successfully started. 2000-04-20-13.18.23.603000 Instance:DB2 Node:000 PID:291(db2syscs.exe) TID:316 Appid:none common_communication sqlccspmconnmgr_listener Probe:6 DIA3103E Error encountered in APPC protocol support. APPC verb "APPC(DISPLAY 1 BYTE)". Primary rc was "F004". Secondary rc was "00000000".
If such entries exist in your db2diag.log, and the time stamps match your most recent reboot time, you must:
Check the db2diag.log file again to verify that the entries are no longer appended.
An additional locale setting is required when you want to use the Java GUI tools, such as the Control Center, on a Japanese or Simplified Chinese Linux system. Japanese or Chinese characters cannot be displayed correctly without this setting. Please include the following setting in your user profile, or run it from the command line before every invocation of the Control Center.
For a Japanese system:
export LC_ALL=ja_JP
For a Simplified Chinese system:
export LC_ALL=zh_CN
Please ensure that the locale of the DB2 Administration Server instance is compatible to the locale of the DB2 instance. Otherwise, the DB2 instance cannot communicate with the DB2 Administration Server.
If the LANG environment variable is not set in the user profile of the DB2 Administration Server, the DB2 Administration Server will be started with the default system locale. If the default system locale is not defined, the DB2 Administration Server will be started with code page 819. If the DB2 instance uses one of the DBCS locales, and the DB2 Administration Server is started with code page 819, the instance will not be able to communicate with the DB2 Administration Server. The locale of the DB2 Administration Server and the locale of the DB2 instance must be compatible. For example, on a Simplified Chinese Linux system, "LANG=zh_CN" should be set in the DB2 Administration Server's user profile.
If specified after the Java method name in the EXTERNAL NAME clause of the CREATE PROCEDURE or CREATE FUNCTION statement, the Java method signature must correspond to the default Java type mapping for the signature specified after the procedure or function name. For example, the default Java mapping of the SQL type INTEGER is "int", not "java.lang.Integer".
In some languages, for the Control Center on UNIX based systems and on OS/2, some keyboard shortcuts do not work. Please use the mouse to select options.
During the installation of DB2 for Windows NT or Windows 2000, the setup program creates several Windows services and assigns a service account for each service. To run DB2 properly, the setup program grants the following user rights to the service account that is associated with the DB2 service:
If you want to use a different service account for the DB2 services, you must grant these user rights to the service account.
In addition to these user rights, the service account must also have write access to the directory where the DB2 product is installed.
The service account for the DB2 Administration Server service (DB2DAS00 service) must also have the authority to start and stop other DB2 services (that is, the service account must belong to the Power Users group) and have DB2 SYSADM authority against any DB2 instances that it administers.