Home
All Oracle Error Codes
Oracle DBA Forum

Frequent Oracle Errors

TNS:could not resolve the connect identifier specified
Backtrace message unwound by exceptions
invalid identifier
PL/SQL compilation error
internal error
missing expression
table or view does not exist
end-of-file on communication channel
TNS:listener unknown in connect descriptor
insufficient privileges
PL/SQL: numeric or value error string
TNS:protocol adapter error
ORACLE not available
target host or object does not exist
invalid number
unable to allocate string bytes of shared memory
resource busy and acquire with NOWAIT specified
error occurred at recursive SQL level string
ORACLE initialization or shutdown in progress
archiver error. Connect internal only, until freed
snapshot too old
unable to extend temp segment by string in tablespace
Credential retrieval failed
missing or invalid option
invalid username/password; logon denied
unable to create INITIAL extent for segment
out of process memory when trying to allocate string bytes
shared memory realm does not exist
cannot insert NULL
TNS:unable to connect to destination
remote database not found ora-02019
exception encountered: core dump
inconsistent datatypes
no data found
TNS:operation timed out
PL/SQL: could not find program
existing state of packages has been discarded
maximum number of processes exceeded
error signaled in parallel query server
ORACLE instance terminated. Disconnection forced
TNS:packet writer failure
see ORA-12699
missing right parenthesis
name is already used by an existing object
cannot identify/lock data file
invalid file operation
quoted string not properly terminated

RE: dbms_job failed to execute

Igor Neyman

2005-10-27

Replies:
Magnus,
 
When you are saying that jobs stopped executing on Tuesday, does it mean that they were not executed since then?
Your output from dba_jobs shows that all your jobs were executed this morning (probably when your instance was started) and they all are scheduled to be executed tomorrow at different times (probably, as they are supposed to).
 
The reason they all were executed this morning right after instance started is that most probably your instance was down at the time when they were scheduled to be executed, and when oracle starts, it checks if it missed to execute some jobs while the instance was down.
And if it finds such jobs that "missed" their scheduled time, it will execute them immediately (not waiting for next scheduled time).
 
HTH
Igor


From: oracle-l-bounce@freelists.org [mailto:oracle-l-bounce@freelists.org] On Behalf Of Magnus Andersen
Sent: Thursday, October 27, 2005 10:17 AM
Cc: oracle-l@freelists.org
Subject: Re: dbms_job failed to execute

I found two trace files with the same time stamp on them.  These are the closest to when I saw the problem.  Could this have "hung" since the database bounced?

--
Magnus Andersen
Systems Administrator / Oracle DBA
Walker & Associates, Inc.


Trace file information...

Dump file /opt/oracle/ora92/rdbms/log
/prd/bdump/prd_j000_9659.trc
Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.6.0 - Production
ORACLE_HOME = /opt/oracle/ora92
System name:    Linux
Node name:      oraprd.walkerassoc.com
Release:        2.4.21-32.0.1.ELsmp
Version:        #1 SMP Tue May 17 17:52:23 EDT 2005
Machine:        i686
Instance name: prd
Redo thread mounted by this instance: 1
Oracle process number: 28
Unix process pid: 9659, image: oracle@oraprd.walkerassoc.com (J000)

*** 2005-10-22 00:38:58.415
*** SESSION ID:(27.52095) 2005-10-22 00:38:58.391
OPIRIP: Uncaught error 1089. Error stack:
ORA-01089: immediate shutdown in progress - no operations are permitted
ORA-00448: normal completion of background process