Chapter 8. Installing and configuring DB2 99
3. Connect to the remote instance to start working with it:
attach to psxinst
4. Catalog the test database:
catalog database seed as psxseed at node psxinst
5. Connect to the remote database:
connect to psxseed
6. Verify the connection to the database by selecting from a table (choose a
table you know exists on the remote server):
db2 => select * from test_table
1 record(s) selected.
If you are still having trouble connecting to the remote database, consult the next
section, “Troubleshooting the DB2 UDB installation” on page 99. If
not—congratulations! You have now successfully tested the database engine and
You may also have to perform additional steps, such as upgrading to the latest
fixpack. Consult the PeopleSoft Installation Manual, found on PeopleSoft
Customer Connection, for details.
8.5 Troubleshooting the DB2 UDB installation
Though there are many excellent resources on troubleshooting DB2 UDB
installation, we will mention some of the more common pointers from our
8.5.1 Connection and cataloging issues
Whether trying to connect to a remote database via a graphic tool (such as DB2
Control Center and Configuration Assistant), or directly through the DB2
Command Processor, these are some of the things you can check if experiencing
򐂰 Named systems and services can sometimes fail to resolve. You can avoid
this issue by specifying the system you would like to connect to in the
/etc/hosts file with a line like this: bottom440
100 Implementing PeopleSoft Enterprise on xSeries and Linux
This statement defines the IP address, its canonical name, and an alias that
we can then use in our catalog definitions.
򐂰 You can also use explicit IP addresses and service ports rather than
hostnames and service names (for example, instead of
bottom440, or 51000 instead of db2inst1_serv). This will help you isolate
whether the problem is in the networking, communication stacks, or the
database engine itself.
򐂰 Check the /etc/services file to verify that your local and remote services are
properly assigned. Uncataloging nodes through the DB2 tools does not
always remove the no longer relevant entries.
򐂰 If you are having trouble starting the graphical tools as a user other then root,
check that the appropriate users have permissions to connect to the X-server.
Use the xhost utility to adjust X-server access controls.

Get Implementing PeopleSoft Enterprise on xSeries and Linux now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.