Jump to Navigation

Oracle Database

Create database fails on package STANDARD

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

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

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

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

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.

OEM Database Control: change HTTP(S) listen port

Symptoms

The port number on which Oracle Enterprise Manager Database Control is listening for HTTP(S) connections is not what you want, especially if more than one database instance is present on your Oracle database server.

Solution

You can change the port number, 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.

Subscribe to RSS - Oracle Database


by Dr. Radut