Tracy,

The culprit appears to be tablespace unable to extend.

Error from alert.log: ORA-1654: unable to extend index SAPDAT.VBFS~0 by
64640 in tablespace PSAPDATGVBAKI

Added datafile to TS and update job completed successfully soon after.



-----Original Message-----
From: Tracey Cole
[mailto:oracledba-ezmlmshield-x80011670.[Email address protected]
Sent: Wednesday, March 05, 2008 11:18 AM
To: LazyDBA Discussion
Subject: Re: ORA-02055


---- Napasindayao Don S <oracledba-ezmlmshield-x46944979.[Email
address protected] wrote:
Error: ORA 2055
Text: distributed update operation failed; rollback required
------------------------------------------------------------------------
-------
Cause: A failure during a distributed update operation may not have
rolled
back all effects of the operation.
Since some sites may be inconsistent with others, the
transaction must
roll back to a savepoint or roll back entirely.
Action: Roll back to a savepoint or roll back the entire transaction and

resubmit the rolled-back statements.

The other choice is to manually complete the transaction.

The assumption here is that you have a transaction touching multiple
databases and Oracle is not the broker of transaction completion. You
could be updating something through a database link to another Oracle
database or some non-Oracle (gasp!) data source.

> Oracle Experts:
>
> Is anybody familiar with the following ora-err and what causes are:
> ORA-02055: distributed update operation failed; rollback ?
>
> Thanks in advance....
>
> Don
>
>


---------------------------------------------------------------------
TO REPLY TO EVERYBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY To post a
dba job: http://jobs.lazydba.com To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html



Oracle LazyDBA home page