Erorr Message during backup of database

From: David <dt_146_at_yahoo.co.in>
Date: 3 Mar 2004 02:49:26 -0800
Message-ID: <d5840ebd.0403030249.4348eb50@posting.google.com>

Hi,

During Backup of database I got the following error message. If possible, could you please read the following error messages of alert log file?

I highlighted the error messages.
The SNP files also contain these error messages.

Below you also find the error messages from the alert log file:

Error Message from Alert log file:

Windows NT Version 4.0 Service Pack 6, CPU type 586 Starting up ORACLE RDBMS Version: 8.1.7.0.0. System parameters with non-default values:   ......
............

####################################################

Mon Mar 01 13:20:33 2004
Errors in file Q:\oracle\admin\PROD\bdump\orclSNP0.TRC:

ORA-12012: error on auto execute of job 28
ORA-02067: transaction or savepoint rollback required
ORA-06512: at "ACO.COPYTOSTANDBY", line 4528
ORA-02067: transaction or savepoint rollback required
ORA-02055: distributed update operation failed; rollback required
ORA-02068: following severe error from STANDBYDB
ORA-03113: end-of-file on communication channel
ORA-06512: at line 1
#####################################################3

Mon Mar 01 13:21:45 2004
Thread 1 advanced to log sequence 18182
  Current log# 2 seq# 18182 mem# 0: Q:\ORACLE\ORADATA\PROD\REDO02.LOG Mon Mar 01 13:21:45 2004
ARC0: Beginning to archive log# 1 seq# 18181 ARC0: Completed archiving log# 1 seq# 18181 Mon Mar 01 13:25:34 2004
Thread 1 advanced to log sequence 18183
  Current log# 3 seq# 18183 mem# 0: Q:\ORACLE\ORADATA\PROD\REDO03.LOG Mon Mar 01 13:25:34 2004
ARC0: Beginning to archive log# 2 seq# 18182 ARC0: Completed archiving log# 2 seq# 18182 Mon Mar 01 13:29:52 2004

&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;
&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.

This message only occurs during backup of database.

The SNP files also contain same error messages. Could someone please suggest me what is the reason of this error message and what should we do in order to avoid that message?

Thanks

David Received on Wed Mar 03 2004 - 04:49:26 CST