DX NetOps

Hello community, Im running the nhSaveDb command for backups, and Im getting erros.

C:\eHealth\bin>nhSaveDb -p D:\BKP\EH01_MIERCOLES.tdb
See log file C:/eHealth/log/save.log for details...
Begin processing 2/8/2017 13:42:32.
2/8/2017 13:42:32 - Performing initial checks ...
2/8/2017 13:42:32 - Performing space check. This will take 1 to 3 minutes ...
2/8/2017 13:42:32 - Initial checks completed. Starting save ...
2/8/2017 13:48:08 - Starting validate ...
2/8/2017 13:57:44 - Error: Validate failed. rman encountered errors in script:
D:/BKP/EH01_MIERCOLES.tdb/oracle_rman/nh_rman_validate.scr
see logfile:
D:/BKP/EH01_MIERCOLES.tdb/oracle_rman/rman_save3.log
command was:
rman target 'sys/ehealth' nocatalog < D:/BKP/EH01_MIERCOLES.tdb/oracle_rman/nh_r
man_validate.scr > D:/BKP/EH01_MIERCOLES.tdb/oracle_rman/rman_save3.log

2/8/2017 13:57:44 - Error: Rman recovery failed.
Refer to log D:/BKP/EH01_MIERCOLES.tdb/oracle_rman/rman_save.log for more detail
s..
Error: The program nhiSaveDb failed.

But if I run "nhSaveDb.bat -p D:\BKP\EH01_MIERCOLES_ASCII.tdb -ascii -fast" the backup end successfully.

Any idea what could be wrong with normal backup.

Thanks

Diego Pereyra

The first command you have run does a Binary Save and the second command does a ascii save. So the backup process followed for both would be bit different , see below link for some understanding 

CA Tuesday Tip: The most important thing you can do to ensure the safety o 

Please check the rman_save log file and you might find some further clues on why it failed and the error details . Could be the below issue 

RMAN-06059: expected archived log not found, lost of archived log compromises recoverability 

yep, Im doing ascii backup because the binary give RMAN error.

In logs I found this.

RMAN>
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=305 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of crosscheck command on ORA_DISK_1 channel at 08/02/2017 13:48:21
ORA-19633: control file record 723 is out of sync with recovery catalog

Checking with RMAN

RMAN> crosscheck archivelog all;

released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=260 devtype=DISK
validation succeeded for archived log
[.....]
archive log filename=C:\EHEALTHDB\ORADATA\EHEALTH\ARCHIVELOGS\LOG14700459002214
6.ARC recid=469772 stamp=951042455
validation succeeded for archived log
archive log filename=C:\EHEALTHDB\ORADATA\EHEALTH\ARCHIVELOGS\LOG14700469002214
6.ARC recid=469773 stamp=951042490
Crosschecked 63 objects

RMAN>

Thanks !

Hi Diego!

Do have enough disk space?

What is the eHealth version?

What you have in the rman_save.log?

Hi Alex, the version is old.. EH 6.2., where Im saving the backup there is 80g free.

in rman_save3.log

I have 
RMAN>
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=305 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of crosscheck command on ORA_DISK_1 channel at 08/02/2017 13:48:21
ORA-19633: control file record 723 is out of sync with recovery catalog

Thanks

Diego

Diego,

Especially with it being so old, can you provide the full eHealth version info by running:

nhShowRev

This will allow us to see what Oracle version as well.  After a bit of digging it does seem that there were some Oracle bugs that existed in the past that caused this sort of symptom.  If this is not the case though it does not look like it is going to be a simple fix and would likely require a support case.

Troy

Yes.. its old. but keep working.

C:\eHealth\bin>nhShowRev
eHealth version: 6.2.1 D17

The ascii backup can be restored, no? may I live only doing ascii backups and not with rman.?

diego

Diego!

The ASCII Backup can be restored on any eHealth Version/ Any OS Version, so for example you can do the ASCII Backup from a Windows 2003 using eHealth 6.2.1 into a Linux Server with eHealth 6.3 version.

So I forget about the bug running normal backup, and use only ASCII method.

Thanks.