This was a strange one. Attempts at recompiling the following package body resulted in this PLS-00801 error. COL owner FOR A20 COL object_name FOR A40 BREAK ON object_name SELECT owner, object_name, object_type, status, created, last_ddl_time FROM dba_objects WHERE object_name = ‘PKG_FINANCIALS_WORK’ ORDER BY status, object_type / OWNER OBJECT_NAME
This week one of our developers highlighted the fact that the DBMS_SCHEDULER on one of our 11.2.0.3 databases was running jobs an hour later than scheduled until just recently, when the clocks went back (26/10/2014) for British Summer Time (BST) …and now they’re running on-time again! I’d not seen this before, and at first I thought we
I hit the following problem with a 9.2.0.8 database running on Windows 2003 this morning (info pulled from the alert log). The database had failed to restart after a client’s cold backup process 🙄 ALTER DATABASE MOUNT Wed Jan 15 22:32:08 2014 ORA-09341: scumnt: unable to mount database OSD-04400: unable to acquire internal semaphore for
I’ve hit this problem a couple of times lately where a developer is trying to recompile a PL/SQL package and their session hangs until they eventually get this error: SQL> @new_pkg CREATE OR REPLACE PACKAGE BODY test_package * ERROR at line 1: ORA-04021: timeout occurred while waiting to lock object Basically, whilst someone or something else (a
How to check which PSU is installed…if any Oracle PSUs (Patch Set Updates) are referenced by their 5-place version number. Unfortunately they do not change version numbers in the Oracle binaries, product banners and such though (see MOS 861152.1), so here’s how to identify which PSU your ORACLE_HOME is at… Database Server: To check the Oracle