HP Driver for JDBC User's Manual

Chapter 6 55

Troubleshooting

Connection Process

Step 7. Switching to the Effective User

• Once the process is spawned, the monitor switches the effective user

id to the user that was supplied in the user validation. This ensures

that the user only has the privileges assigned to the user. If this step

fails, the most likely cause is that the monitor was not started by

“root,” the superuser for HP-UX, or a user with the PM capabilities

for MPE/iX. The user can log on to the server and verify that the

monitor process was started by the correct user and has the proper

capabilities.

Step 8. Executing the JDBC Server by the Spawned Process

• If this process fails, the JDBC Server executable could be corrupt,

have incorrect permissions, be missing, or be incompatible to the

server operating system (installed components for incorrect

platform). The user can log on to the server and manually verify the

server installation ﬁles.

Step 9. Attempting to Connect to the Speciﬁed Database

• If this step fails, the client should receive an ALLBASE/SQL error

message through the java.sql.SQLException that is shown.

Common causes of this failing are incorrect database name or a

corrupt database. Make sure the case-sensitivity of the database

name is also checked.

If all the preceding steps are successful, the Driver Manager will return

a connection to the database.