cancel
Showing results for 
Search instead for 
Did you mean: 

How to trigger Offline backup in standby mode.

Former Member
0 Kudos


Dear All,

OS: AIX

Database used: Oracle 11g

Please tel the steps to trigger an Offline backup in standby mode .

Primary_db = SID and backup Type = offline_standby has been maintained in initKBP.sap File and we triggerd the backup.

******************************************************************

1 - BRBACKUP profile (profile) ....... [initKBP.sap]
2 - Backup device type (device) ...... [util_file]
3 # Tape volumes for backup (volume) . []
4 ~ BACKINT/Mount profile (parfile) .. [/oracle/KBP/112_64/dbs/initKBP.utl]
5 - Database user/password (user) .... [/]
6 - Backup type (type) ............... [offline_standby]
7 # Disk backup for backup (backup) .. [no]
8 # Delete disk backup (delete) ...... [no]
9 ~ Files for backup (mode) .......... [all]

*******************************************************************************

We are getting Error for Offline standby Backup as shown below

**********************************************************************************************

BR0280I BRBACKUP time stamp: 2014-02-25 14.53.39
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /@KBP'
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance KBP/PRIMARY failed
BR0280I BRBACKUP time stamp: 2014-02-25 14.53.39
BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:
'CONNECT /@KBP'
ORA-01017: invalid username/password; logon denied
BR0310E Connect to database instance KBP/PRIMARY failed

**************************************************************************************************************

Please tel me the parameters to be maintained for trigerring an Offline backup in STANDBY MODE.

Please tel the steps to trigger an Offline backup in standby mode

Thanks and Regards,

Gayathri.K

Accepted Solutions (0)

Answers (2)

Answers (2)

nirmal_konchada
Active Contributor
0 Kudos

Hello Gayathri,

Can you please check the value of primary_db parameter in initSID.sap. Apart from it please check the below 2 parameters

REMOTE_LOGIN_PASSWORD 

REMOTE_OS_AUTHENT

By default the above parameters should set to EXCLUSIVE and FALSE values respectively in the standby.

And in a standby database, you can only login with "sys" user and no other user works.

Regards,

Nirmal

Former Member
0 Kudos

Dear Nirmal,

The parameters maintained in init<KBP>.SAP is given below

backup_type = offline_standby

archive_function = save

primary_db = KBP

The below two parameters have been maintained in spfile only

*.REMOTE_LOGIN_PASSWORDFILE='EXCLUSIVE'

*.REMOTE_OS_AUTHENT='false'

*.replication_dependency_tracking=FALSE

regards,

gayathri.K

former_member188883
Active Contributor
0 Kudos

Hi Gayathri,

Change the below parameter

REMOTE_OS_AUTHENT='TRUE'


Hope this helps.


Regards,

Deepak Kori

Former Member
0 Kudos

Dear Deepak,

Tried

REMOTE_OS_AUTHENT='TRUE'


in spfile also.

Still getting same error

***************************

BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:

'CONNECT /@KBP'

ORA-01017: invalid username/password; logon denied

BR0310E Connect to database instance KBP/PRIMARY failed

BR0280I BRBACKUP time stamp: 2014-02-25 16.49.07

BR0301E SQL error -1017 at location BrDbConnect-2, SQL statement:

'CONNECT /@KBP'

ORA-01017: invalid username/password; logon denied

BR0310E Connect to database instance KBP/PRIMARY failed

****************************

Regards,

Gayathri.K

former_member188883
Active Contributor
0 Kudos

Hi Gayathri,

Refer to the remote db connection settings in the link below

http://help.sap.com/saphelp_nwpi711/helpdata/en/47/0df1abd14363efe10000000a114a6b/content.htm

Also refer settings as per note

914174 - Minor functional enhancements in BR*Tools (1)

Hope this helps.

Regards,

Deepak Kori

Former Member
0 Kudos

brbackup will access tables SDBAD from your primary database. Please set parameter primary_db.

FYI.. note 1576837 - ORA-01017: invalid username/password; to resolve the ORA-01017 issue first.