SAP (BRTOOLS)+RMAN Backup configuration
Hi,
I am trying to configure SAP (BRTOOLS)+RMAN Backup
Master server -- 7.6.0.3 on (Red Hat 4.4.6-3)
SAP server - 7.6.0.1 on solaris 10.5
I followed below given link to configure the backup :-
http://www.symantec.com/connect/articles/netbackup-sap-backup-using-rman
As admin guide for sap has no clear view about to configue sap backup with rman
After configuration i ran below command to intiate the backup : -
brbackup -d util_file_online -t online -m all
But backup failed with error :-
BR0051I BRBACKUP 7.20 (34)
BR0055I Start of database backup: bepnbogp.fnr 2014-12-29 12.14.03
BR0484I BRBACKUP log file: /oracle/OL1/sapbackup/bepnbogp.fnr
BR0280I BRBACKUP time stamp: 2014-12-29 12.14.03
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT system/*******'
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance OL1 failed
BR0280I BRBACKUP time stamp: 2014-12-29 12.14.03
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT system/*******'
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance OL1 failed
BR0056I End of database backup: bepnbogp.fnr 2014-12-29 12.14.03
BR0280I BRBACKUP time stamp: 2014-12-29 12.14.03
BR0054I BRBACKUP terminated with errors
Can you please help me to resolve the issue and please let me know if i followed wrong procedure to configure the backup.
One more query do i required to get seprate RMAN script for SAP+RMAN backup
Thanks in Advance
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT system/*******'
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance OL1 failedIf no username and password are specified in your script - and I suspect they are not - you'll need to add it to your command line by adding the -u (username/password) switch. Or add it to your script.
You'll want to make sure the account you're specifying has the appropriate privileges.
Good luck!
DISCLAIMER: I know nothing about database backups but this came up in a search of previous cases with similar log output.