Final error: 0xe0000340 - The Database script returned an error.

[Wonpyo]

Hi,

The backup runs well and suddenly it fails one day.

The customer says that he just rebooted.

But Oracle backup fails.

The error message is "The database script returned an error. For more information, see the section Database Script Output in the Activity Log."

So I checked the database scripts, I don't understand.

I found the Veritas guide.."It is recommended to perform a DBA-initiated restore to allow RMAN to perform the restores."

https://www.veritas.com/support/en_US/article.100023170.html

Is this guide for DBA?

What can I do with backup exec?

[MIL1]

Hi,

The error message suggests that the Oracle backup job has failed and you will need to review the RMAN output from failed job log. Please attach the job log or provide the details of the errors seen in the RMAN output.

[Wonpyo]

Hi,

The file can not be attached, So I copy&paste oracle RMAN Script message.

복구 관리자: Release 11.2.0.4.0 - Production on 금 1월 5 11:07:17 2018

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

ORA-12154: TNS:지정된 접속 식별자를 분석할 수 없음

 # -----------------------------------------------------------------

# RMAN command section

# -----------------------------------------------------------------

 RUN {

 SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO 'BE_';

ALLOCATE CHANNEL ch0

     TYPE 'SBT_TAPE';

SEND 'BSA_SERVICE_HOST=40.40.40.128,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE={1E5E5F2C-3609-4E41-94F8-2590B84C380D},NBBSA_DB_DEVICE_NAME=Oracle-Win::\\WIN-8VLJL98IV0A\OES';

BACKUP

     INCREMENTAL LEVEL=0

     FORMAT 'BE_U'

DATABASE FORCE PLUS ARCHIVELOG FORCE NOT BACKED UP;

BACKUP CURRENT CONTROLFILE

     FORMAT 'BE_U';

 RELEASE CHANNEL ch0;

}

명령어 수행: SET CONTROLFILE AUTOBACKUP FORMAT

복구 카탈로그 대신 대상 데이터베이스 제어 파일을 사용하고 있습니다.

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: allocate 명령 실패(01/05/2018 11:07:18에서)

RMAN-06171: 대상 데이터베이스로 접속할 수 없습니다

EXIT

복구 매니저가 완성되었습니다.

[MIL1]

The following errors logged by RMAN

RMAN-03002: Failure of allocate command

RMAN-06171: unable to connect to target database

The above indicates that the job did not complete as Oracle RMAN was unable to connect to the target database. Please check the Oracle server and confirm if Oracle Database was shutdown\unavailable due to some reason.

You also mentioned that the server was "rebooted".  Does the problem occur only when the Oracle server is rebooted or was the server rebooted due to some issue with Oracle ? Please let me know the version of Backup Exec and if Oracle database is installed on Windows or Linux OS.

[Wonpyo]

Hi MIL1,

This error message no longer appears due to oracle system password changes.

But another message was output.

 V-79-57344-5125

 So I did the following.

1. DB Server Agent Re-installed.

2. Firewall check (5633 port, oracle.exe)

3. Registry check

4. Oracle DB mount status check, Archive log mode check, listener status check

But every time backup failed.

[Colin_Weaver]

Have you configured that required sections of the Remote Agent Uility (vxmon.exe)?

I think the info in this document may still apply

https://www.veritas.com/support/en_US/article.100017883.html

[MIL1]

Check if the Remote Agent Utility is configured and also confirm if CORBA connection port is set on Media Server and Remote Agent utility on the Oracle Server. Please check the following document

https://www.veritas.com/support/en_US/article.000090767

[Wonpyo]

https://www.veritas.com/support/en_US/article.000090767

I've already covered this article.

Port setting, firewall check and check the host file.