 |
|
EnterpriseDB: PostgreSQL
Oracle Tips by
Burleson
|
Adding
servers for EnterpriseDB and PostgreSQL differ only in the drop down
chosen (Figure 5.12). The Port will usually vary between databases.
The parameters you enter create a JDBC connection to that database.
Figure
5.12: Configure EnterpriseDB Server Connection
When
configuring a PostgreSQL database, you select the PostgreSQL server
type but all other information is the same.
The
Nickname field is the name you will see, and choose, in the navigator
pane. You may want to use a nickname that will let you know which
machine, DB type and user is connecting.
The Host
may be a named host or an IP address. If you are connecting to a
database on the localhost, you may use localhost as the name.
The Port
is the port where the database is listening for connections.
EnterpriseDB listens to 5444 by default and PostgreSQL listens to 5432
by default.
The
Initial DB is the database that you will connect to upon logon.
EnterpriseDB and PostgreSQL differ from Oracle in that, what Oracle
would call a local database, EnterpriseDB and PostgreSQL call a
cluster. In Oracle terms, the most closely connected term would be
the schema that you want to connect to.
Finally,
you enter the user name and password of the user to which you wish to
connect.
Figure
5.13 shows a fully populated PostgreSQL 8.2 connection.
Figure
5.13: PostgreSQL 8.2 Server Connection
Oracle
An
Oracle connection looks much like an EnterpriseDB connection but
instead of an Initial DB, you need to enter a service name. This is
the service associated in the Oracle TNS listener file.
This is
a JDBC connection and as such, you do not need a local Oracle client
installed. You do need to know the server-level service name of the
database though.
Oracle
defaults to port 1521 but many administrators change that port for
security reasons.
All of
the other parameters are the same. Figure 5.14 provides an example of
an Oracle server connection.
Figure
5.14: Oracle Server Connection
If you
have errors connecting to the Oracle server, you may want to install
the Oracle client and get that working first. If you have a working
client, then you know the problem is not client side.
This
is an excerpt from the book "EnterpriseDB:
The Definitive Reference" by Rampant TechPress. |
