The OpenNET Project / Index page

[ новости /+++ | форум | wiki | теги | ]

Поиск:  Каталог документации

9. Troubleshooting

The following section covers some of the common problems you may encounter while installing DB2, creating an instance, or using a DB2 database.

9.1. Problems with DB2 installation

The following section covers some of the common problems you may encounter when you install DB2.

9.1.1. When I try to run db2setup, I get the following error: DBI1503E An error was encountered when opening or writing to file, "/tmp/.dbinst.swp".
9.1.2. When I try to run db2setup, I get the following error: ./db2inst: error while loading shared libraries: libncurses.so.4: cannot open shared object file: No such file or directory
9.1.3. Creating a DB2 instance on SuSE Linux: Default user name already exists
9.1.4. Creating a DB2 instance on SuSE Linux: Default group name already exists
9.1.5. Creating a DB2 instance on SuSE Linux: Default home directory points to /usr/lib/db2/
9.1.6. After creating a DB2 instance, I installed the Application Development Client, but I can't use that instance to create DB2 applications.
9.1.7. I installed DB2, but none of the permissions in /usr/IBMdb2/V7.1/bin are executable!

If you did not remove the default DB2 user IDs created by SuSE Linux before installing DB2 (see Section 3.6), the DB2 Create Instance panel places the corresponding user ID in the "User ID" field. This can cause a problem when you change the value of the User Name field to reflect the name of the new instance, because the value of the "User ID" still reflects the original user name.

Ensure that you select the "Use default UID" check box to automatically associate the new user name with its corresponding user ID.

If you did not remove the default DB2 user IDs created by SuSE Linux before installing DB2 (see Section 3.6), the DB2 Create Instance panel places the corresponding group ID in the Group ID field. This can cause a problem when you change the value of the Group Name field to reflect the name of the new instance, because the value of the Group ID still reflects the original group name.

Ensure that you select the "Use default GID" check box to automatically associate the new group name with its corresponding group ID.

If you did not remove the default DB2 user IDs created by SuSE Linux before installing DB2 (see Section 3.6), the default user name already exists and was created in the /usr/lib/db2/ directory. To change the home directory of your new DB2 instance, you must manually specify the location of the new instance. The default home directory is /home/.

When you create an instance, as described in Section 6, DB2 copies selected files from /usr/IBMdb2/V7.1/bin into the $HOME/sqllib/bin directory of the instance. DB2 sets the appropriate permissions on the copies of the files in the instance directory.

9.2. Problems creating a DB2 instance

The following section covers some of the common problems you may encounter when you create a DB2 instance.

9.2.1. Creating a DB2 instance or a DB2 Administration Server fails.
9.2.2. db2setup indicated that it successfully created an instance, but I checked /tmp/db2install.log and it contains the message DBI1766W Cannot change the secondary group list of "" (Caldera OpenLinux 2.4).

9.3. Problems using DB2

The following section covers some of the common problems you may encounter when you use a DB2 database.

9.3.1. DB2 is running out of available connections.
9.3.2. I installed DB2 Version 6.1 and db2start just hangs.
9.3.3. I'm using DB2 PE 7.1 on linux (RH 6.0), and I'm having problems when trying to connect with my username and password. I can connect successfully to the database with the default user ID:

bash$ db2 connect to sample

Database Connection Information

Database server        = DB2/LINUX 7.1.0
SQL authorization ID   = userID
Local database alias   = SAMPLE
But when I try to connect to the database using the explicit user ID, it fails:

bash$ db2 CONNECT TO sample USER userID
Enter current password for userID:
SQL1403N  The username and/or password supplied is incorrect.
SQLSTATE=08004
Why can't I connect with an explicit user ID?
9.3.4. When I run any db2 commands, part of the output is Welcome to your OpenLinux system!. How do I change this? (Caldera OpenLinux 2.4)
9.3.5. How do I connect from a DB2 Connect for Linux client to a DB2 for AS/400 server?

9.4. Problems starting the DB2 Control Center

The following section covers some of the common problems you may encounter trying to start the DB2 Control Center.

9.4.1. When I start the DB2 Control Center with db2cc, nothing happens.
9.4.2. When I start the DB2 Control Center, I get a message box with the error SQL1042C An unexpected system error occurred.
9.4.3. I followed the instructions for installing IBM JDK 1.1.8 but Java applications, including the DB2 Control Center, don't work.
9.4.4. The DB2 Control Center starts normally, but the "Systems" folder is empty.
9.4.5. When I try to start the DB2 Control Center, I get the following message at the console: Xlib: connection to "localhost:0.0" refused by server
9.4.6. When I start the DB2 Control Center, I get a message box with the error SQL1042C An unexpected system error occurred.
9.4.7. When I try to start the DB2 Control Center with the db2cc command, the splash screen comes up, then disappears.

Ensure that you have installed the IBM Developer Kit for Java, and that the directory containing the jre or java executable is in your path. If you issue the command
bash$ java -fullversion
, you should get a response like this: java full version "JDK 1.1.8 IBM build l118-20000325 (JIT enabled: jitc)" or, for the IBM JDK 1.3: java full version "J2RE 1.3.0 IBM build cx130-20000623" Java virtual machines from other sources may not work. For a quick guide to installing the IBM Developer Kit for Java, see Section 11.




Спонсоры:
PostgresPro
Inferno Solutions
Hosting by Hoster.ru
Хостинг:

Закладки на сайте
Проследить за страницей
Created 1996-2022 by Maxim Chirkov
Добавить, Поддержать, Вебмастеру