Oracle backup is failing immediately with error 6

[Pinky472]

Hello Folks,

am facing oracle backup failure.

up on checking the rman logs. i have found RMAN, oracle_SID and Oracle_home path are not picking up.

could you please shed some light on this. even oracle team is also not able to trace.

although i am seeing different SID name in log. please could anyone give some hint.

enabled bphdb logs. found in log like , the specified path cannot exists.

thanks in advance

[Marianne]

@Pinky472 

More info, please - 
- All relevant versions (OS, NBU on master, media, client and Oracle version on client)
- Is this a new config or something that has worked before and now producing errors?
- How is the policy configured - Intelligent Policy or traditional script-based policy?
- How is the backup initiated - from NBU scheduler or another scheduler on the client? 

If script-based backup - can you provide the script?

[Pinky472]

Hello Marianne,

- All relevant versions (OS, NBU on master, media, client and Oracle version on client)

Master/Media: 8.1.1 netbackup appliance

client :7.7.3
- Is this a new config or something that has worked before and now producing errors? new config, after migration
- How is the policy configured - Intelligent Policy or traditional script-based policy? traditional script based
- How is the backup initiated - from NBU scheduler or another scheduler on the client?  from NBU side

If script-based backup - can you provide the script? please find the atatched

ERROR in RMAN log:

==== started on 2020-01-20_18-40-40 ====
Script name: "C:\NetBackupScripts\hot_database_backup.cmd"
#                                      
  RMAN  :  \bin\rman.exe                      
  NLS_LANG  :  american              
  ORACLE_HOME  :          
  ORACLE_SID  :  PRD          
  NLS_DATE_FORMAT  :  YYYY-MM-DD:hh24:mi:ss
  RMAN_LOG_FILE  :  C:\NetBackupScripts\rman_log\hot_database_backup.cmd.log.2020-01-20_18-40-40.txt    
  NB_ORA_SERV  :  servername.ap.novartis.net                    
  NB_ORA_FULL  :  1                    
  NB_ORA_INCR  :  0                    
  NB_ORA_CINC  :  0                    
#  
==== ended in error on Mon 01/20/2020  06:40 ====

[Marianne]

Have all steps been taken as with a new deployment (including NBU Service startup)?

I am not a Windows scripting expert - hopefully other users can have a look and advise.

According to the script, the environment parameters/variables are specified in a separate script :

@SeT ORA_PARAM=%MYDIR%ora_param.cmd

Have you checked this script? 

[Pinky472]

yes i have checked, but it is same for other workign servers.

am confused from where the script is pointing to different SID and RMAN path is also not correct. as i shown in earlier rman_log.

need help in tracing why it is showing different SID and from which file  it is calling

[Marianne]

So, what is defined in ora_param.cmd on this client?

And what about this file?

@SeT SID_NAME=%MYDIR%sid_name.cmd

[Pinky472]

i have attached the file of or_param

sid_name has :

@REM sid_name.cmd - determine SID from policy name

@setlocal ENABLEEXTENSIONS
@Echo off

for /f "tokens=3 delims=-" %%s in ("%1%") do (
 if "%%s" NEQ "" echo %%s
)

[Marianne]

You really need an rman and windows script expert to troubleshoot this...

Can your dba manually type in the rman commands and see what happens?
If all is working from cmd, then the dba needs to carefully look at the scripts to see why the parameters and variables are not pulled in.

Sorry that I have nothing else to offer. 

[Michael_G_Ander]

Agree with Marianne, talk with your Oracle DBA, the DBA might also be able to see something in the Oracle logs.

I have seen the wrong rman/oracle_home path after Oracle have been patched or upgraded. If I remember correct it can be seen in the error.out file under bphdb logs

[Pinky472]

but in error.out file , i can see only system cannot find the specified path.

[Marianne]

---

@Pinky472 wrote:

but in error.out file , i can see only system cannot find the specified path.

---

That is why the dba needs to carefully check the scripts.