ORA-08103: object no longer exists in simple Server job

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
vpauls
Premium Member
Premium Member
Posts: 37
Joined: Mon May 09, 2005 2:26 am
Location: Oslo

ORA-08103: object no longer exists in simple Server job

Post by vpauls »

Using DataStage 7.5.1.A on Oracle 10g:

We have a server job which simply loads data from a view into a table within the same db schema ("manual" materialization of an oracle view).

Like this:
Oracle stage (view) -> Transformer with 1:1 mapping -> Oracle stage (table)

When called within a normal Director run (initiated from a sequence within a larger run where a lot of other data are loaded) the job fails approximately 1 out of 2 times with:

ORA-08103: object no longer exists

on the Oracle "input" node.

When run directly from Director (i.e. when starting the job directly in isolation) it never fails.

Also, when run from within Designer, it never fails.

All job parameters are global, and given default value $PROJDEF. No parameter values are passed from the calling job sequence. The view errors on ORA-08103 is not referenced any other place in the project than in the Oracle input node mentioned above.

Any suggestions on what is causing this and how to fix it?
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Could it be that the failure happens when the machine is under heavy load and manual starts happen when that is not the case? It this a materialized view in Oracle or a dynamic one?
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Generally considered to be an Oracle bug.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply