Jump to Navigation

Secondary menu

Oracle Database

A strange Java OPatch error

Thu, 04/18/2019 - 11:56

After installing a new version of OPatch on an Oracle database home, I got the somewhat mystifying error:

The java.library.path system variable is missing or invalid. Please set java.library.path with a correct value and retry the operation.

It turns out this is the error you get when you install a 32-bit version of OPatch into a 64-bit Oracle home.

Create database fails on package STANDARD

Mon, 04/03/2017 - 14:32

While scripting the creation of an Oracle database, I somehow kept getting errors during the CREATE DATABASE:

ERROR:
ORA-06553: PLS-213: package STANDARD not accessible

Very weird. Until I realized I was using a generic scripting function that issued a SET SERVEROUTPUT ON. It turns out that Oracle can not cope with that until you have loaded catalog.sql and catproc.sql.

Certificate headaches

Thu, 11/27/2014 - 15:27

Creating and managing PKI certificates is always tricky. A small list of what went wrong today when following my own guide for importing your own Oracle Enterprise Manager certificate:

OEM Database Control: security certificate

Tue, 11/18/2014 - 12:18

Symptoms

Oracle Enterprise Manager Database Control has a web front end that can be accessed through HTTPS. By default, the certificate used will not be trusted by any web browsers.

Solution

You can change the certificate, provided you have command-line access on the database server as the user Oracle was installed with. This will cause no downtime on the database, though Enterprise Manager itself will need to be restarted.

OEM Database Control: using HTTPS

Mon, 11/17/2014 - 21:50

Symptoms

Oracle Enterprise Manager Database Control has a web front end that can be accessed through either HTTP or HTTPS. The current protocol is not what you want.

Solution

You can change the protocol, provided you have command-line access on the database server as the user Oracle was installed with. This will cause no downtime on the database, though Enterprise Manager itself will need to be restarted.

OEM Database Control: change port numbers

Mon, 11/17/2014 - 21:22

Symptoms

Several port numbers are used internally by Oracle Enterprise Manager Database Control. You want to change them, for instance because they collide with reserved ports for other applications on the same server.

Solution

You can change the port numbers, provided you have command-line access on the database server as the user Oracle was installed with. This will cause no downtime on the database, though Enterprise Manager itself will need to be restarted.

Pages

Subscribe to RSS - Oracle Database


by Dr. Radut