Blog

How to Configure SQL Developer to Connect to PostgreSQL

A client likes to use Oracle SQL Developer to connect to PostgreSQL databases. During the configuring, some errors occurred. This post shows how to resolve the configuration issues from Oracle SQL Developer and third party libraries .

The typical issue is you will get the following errors when connecting to PostgreSQL database by using non ‘postgres’ users.

Failure -FATAL: database "user1" does not exist

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe

So it is not correct that we have to use ‘postgres’ username which is the same name as database name to connect to PostgreSQL databases. Instead, any user can be used to connect to a PostgreSQL database.

ORA-31633: unable to create master table SYS_EXPORT_SCHEMA_01

The following errors occur when exporting/importing through data pump:

 ORA-31626: job does not exist
 ORA-31633: unable to create master table "USERNAME.SYS_EXPORT_SCHEMA_01"
 ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
 ORA-06512: at "SYS.KUPV$FT", line 1048
 ORA-01031: insufficient privileges

SOLUTION

To make sure user ‘USERNAME’ to have enough privileges to do import/export.

How to Create Service on Non-RAC PDB

As we know, we can use ‘srvctl’ utility to create a service for a RAC database. Now I demonstrate how to create a service for a standalone CDB/PDB database.

For non CDB/PDB database, we can use ‘service_name’ parameter to specify service names.

SQL> show parameter service_name;

 NAME             TYPE    VALUE
 --------------- ------- ------------------
 service_names   string  HR,STOCK,INVENTORY

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe

ORA-04021: timeout occurred while waiting to lock object

When manually compiling a package body, the following error occurs:

SQL> alter package USER.PKGNAME compile body;
alter package USER.PKGNAME compile body
*
ERROR at line 1:
ORA-04021: timeout occurred while waiting to lock object USER.PKGNAME

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe

Code to Report Table Index Schema or Database Fragmentation in PostgreSQL

We are always asked by a client or our manager about how fragmented a table, an index, a schema or whole database is in PostgreSQL database. The following code will answer this question with the following information reported for a schema. 

Toal 7415.00 MB, Free 1918.87 MB, Fragmentation 25.88 Percent

Please do NOT run the code during busy or peak hours, ideally run the code in after hours or off-peak hours.

Subscribe to get access

Read more of this content when you subscribe today.

Subscribe