BR0301W SQL error -1017

[Former Member]

Hi,

I want to management and monitoring to a oracle remote database (JAVA database). I´ve made the connection from dbacockpit and I´ve put the user of schema sapsr3db and the connection it´s succesfully established

-- MESSAGE Database connection Java_db established successfully

But I want to schedule the administrative actions for DB, via DB13 I´ve always the next message error:

Parameters:-u / -jid LOG__20110501373222 -sid D10 -c force -p initepd.sap -sd

BR0002I BRARCHIVE 7.00 (52)

BR0252E Function fopen() failed for 'F:oracleorasap102databaseinitepd.sap' at location BrInitSapRead-1

BR0253E errno 13: Permission denied

BR0159E Error reading BR*Tools profile F:oracleorasap102databaseinitepd.sap

BR0280I BRARCHIVE time stamp: 2011-05-01

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

'CONNECT /'

ORA-01017: invalid username/password; logon denied

BR0310W Connect to database instance D10 failed

BR0007I End of offline redo log processing: aefuiaiw.log 2011-05-01

BR0280I BRARCHIVE time stamp: 2011-05-01

BR0005I BRARCHIVE terminated with errors

External program terminated with exit code 3

BRARCHIVE returned error status E

I´ve found several notes with this error 480266 , 400241, 113747, 651351 but I´m not sure that It´s the same error.

More thanks.

[Former Member]

Looks like the problem described in

Note 1292339 - 10.2: DBUA changes file access authorizations during upgrade

[Former Member]

I´ve the oracle patchset 10.2.0.5, then the note 1292339 cannot be implemented.

I´ve put the security permissions for the user SAPServiceSID under directory 102 and database , but the result it´s the same.

I´ve execute with Brtools the BrBackup and BrArchive, and both are right.

[sivakumar_kilari3]

Check at OS level in Administrative tools---> computer management.

What are the groups is available and compare both user ids sidadm and Sapservicesid

Is the both users sidadm and SAPService<SID> in the backup operators group?

if SAPService<SID> user is not there you have to this user under backup operators group.

Thanks

Siva

[Former Member]

Yes there are both users in this group

The users sidadm an SAPServiceSID and sidam from ABAP, and SAPServiceSID and sidadm from JAVA on Backup Operatos.

[Former Member]

Hi Ruben,

You faced with the two major problems; first one is OPS$ mechanism and the second one is permission on file system. I assume that you are running on a standalone gateway installation over the Java server and have <sid>adm and SAPService<SID> users, belongs to the standalone gateway installation. Please find the answers, below;

In order to solve the permission problem;

1) Logon with "<sid>adm" gateway installation user, to the system,

2) Open "F:\oracle\orasap\102\database\initepd.sap" with a wordpad,

3) Copy all the content of the file,

4) Rename "initepd.sap" file to "initepd.sap.orig",

5) Create a new file with "initEPD.sap" under "F:\oracle\orasap\102\database\" and paste clipboard in it,

6) Then, save the file,

7) Probably, you will face with this error on "initEPD.dba" file, also. If you face this error, then apply steps 1 to 6 for "initEPD.dba", also,

😎 If you face with this problem on "sapcheck" folder, give full permission to the <sid>adm and SAPService<SID> gateway installation users.

It should solve the permission problem.

In order to solve the OPS$ mechanism problem;

1) You should create a new "SAPUSER" table and synonym, belongs to the gateway installation users, as below;

CREATE USER "OPS$<HOSTNAME>\<SID>ADM" DEFAULT TABLESPACE SYSTEM TEMPORARY TABLESPACE PSAPTEMP IDENTIFIED EXTERNALLY;

CREATE USER "OPS$<HOSTNAME>\SAPSERVICE<SID>" DEFAULT TABLESPACE SYSTEM TEMPORARY TABLESPACE PSAPTEMP IDENTIFIED EXTERNALLY;

CREATE TABLE "OPS$<HOSTNAME>\<SID>ADM".SAPUSER (USERID VARCHAR2(256), PASSWD VARCHAR2(256));

CREATE SYNONYM "OPS$<HOSTNAME>\SAPSERVICE<SID>".SAPUSER FOR "OPS$<HOSTNAME>\<SID>ADM".SAPUSER;

GRANT SELECT, UPDATE ON "OPS$<HOSTNAME>\<SID>ADM".SAPUSER TO "OPS$<HOSTNAME>\SAPSERVICE<SID>";

GRANT CONNECT, RESOURCE TO "OPS$<HOSTNAME>\SAPSERVICE<SID>";

GRANT CONNECT, RESOURCE TO "OPS$<HOSTNAME>\<SID>ADM";

INSERT INTO "OPS$<HOSTNAME>\<SID>ADM".SAPUSER VALUES ('<Java database owner (Ex:SAPSR3DB)>', '<Password>');

COMMIT;

Don't forget to execute commands, below, for gateway OS users, also;

brconnect -c -u / -f chpass -o "OPS$<HOSTNAME>\EPDADM" -p <password>

brconnect -c -u / -f chpass -o "OPS$<HOSTNAME>\SAPSERVICEEPD" -p <password>

It should solve the OPS$ mechanism problem.

Best regards,

Orkun Gedik

[Former Member]

Thanks for your answer Orkun,

But I don´t have standalone gateway installed. I ´ve two instances on the same host, I could use the gateway of the ABAP instance,not? Then the users are of the abap instance,not?

[Former Member]

Hi Ruben,

Of course, you can use the ABAP instance as the gateway. In this case, you don't need an additional gateway instance. So, if we discuss over my message, replace "gateway OS users" with the "ABAP OS users", then apply the steps 1 to 6.

1) Logon with "<sid>adm" ABAP user, to the system,

2) Open "F:\oracle\orasap\102\database\initepd.sap" with a wordpad,

3) Copy all the content of the file,

4) Rename "initepd.sap" file to "initepd.sap.orig",

5) Create a new file with "initEPD.sap" under "F:\oracle\orasap\102\database\" and paste clipboard in it,

6) Then, save the file,

7) Probably, you will face with this error on "initEPD.dba" file, also. If you face this error, then apply steps 1 to 6 for "initEPD.dba", also,

😎 If you face with this problem on "sapcheck" folder, give full permission to the <sid>adm and SAPService<SID> ABAP OS users.

Best regards,

Orkun Gedik

[Former Member]

Discuse me, but the second part of to create the SAPUSER table, I´ve to do it?

[Former Member]

Hi Ruben,

Yes, but you should replace "gateway installation users" with ABAP OS users.

After you applied steps respectively, check "r3trans -xd" return code, over the ABAP stack, in order to be sure that the ABAP installation didn't effected, negatively.

Best regards,

Orkun Gedik

[Former Member]

Let me clarify the steps;

1) login to the java server OS by using <sid>adm user

2) perform the steps, below;

CREATE USER "OPS$<HOSTNAME>\<ABAP_SID>ADM" DEFAULT TABLESPACE SYSTEM TEMPORARY TABLESPACE PSAPTEMP IDENTIFIED EXTERNALLY;

CREATE USER "OPS$<HOSTNAME>\SAPSERVICE<ABAP_SID>" DEFAULT TABLESPACE SYSTEM TEMPORARY TABLESPACE PSAPTEMP IDENTIFIED EXTERNALLY;

CREATE TABLE "OPS$<HOSTNAME>\<ABAP_SID>ADM".SAPUSER (USERID VARCHAR2(256), PASSWD VARCHAR2(256));

CREATE SYNONYM "OPS$<HOSTNAME>\SAPSERVICE<ABAP_SID>".SAPUSER FOR "OPS$<HOSTNAME>\<ABAP_SID>ADM".SAPUSER;

GRANT SELECT, UPDATE ON "OPS$<HOSTNAME>\<ABAP_SID>ADM".SAPUSER TO "OPS$<HOSTNAME>\SAPSERVICE<ABAP_SID>";

GRANT CONNECT, RESOURCE TO "OPS$<HOSTNAME>\SAPSERVICE<ABAP_SID>";

GRANT CONNECT, RESOURCE TO "OPS$<HOSTNAME>\<ABAP_SID>ADM";

INSERT INTO "OPS$<HOSTNAME>\<ABAP_SID>ADM".SAPUSER VALUES ('<Java database owner (Ex:SAPSR3DB)>', '<Password>');

COMMIT;

Please note that, I recommend you install a standalone gateway for that kind of operations.

Best regards,

Orkun Gedik

Edited by: Orkun Gedik on May 5, 2011 11:18 AM

[sivakumar_kilari3]

Hi,

Check this service SAP<SID>_00 and SAP<SID>_01 started by which user? in services

if it is started by local admin change user id SAPServiceSID

Thanks

Siva

[Former Member]

Hi Orkun,

When I´ve executed the third sql command:

CREATE TABLE "OPS$domain;'

How have i to create OPS&user? With Domain o without domain?

[Former Member]

Hi Ruben,

First of all, you should login as sysdba role (sqlplus "/as sysdba") to the system, in order to execute the query, below;

CREATE TABLE "OPS$domain\<abapsid>ADM".SAPUSER (USERID VARCHAR2(256), PASSWD VARCHAR2(256));

Secondly, you should use domain name or hostname, as I noted in the SQL statements. By the way, please find the statement below, in the same note;

Note:
As a general rule, the user name and the domain of the Windows user, under which the SAP service was started on the NT computer, must be used. If the service is started with a local user, use the host name of the Application Server as the domain name.

Best regards,

Orkun Gedik

Edited by: Orkun Gedik on May 6, 2011 8:01 PM

[Former Member]

Hi Orkun,

I´ve connected as sysdba user at portal database, but I´ve got the error.

SQL> connect /as sysdba

Connected.

SQL> CREATE TABLE "OPS$DOMAINSIDADM".SAPUSER (USERID VARCHAR2(256), PASSWD VAR

CHAR2(256));

CREATE TABLE "OPS$DOMAINSIDADM".SAPUSER (USERID VARCHAR2(256), PASSWD VARCHAR2

(256))

*

ERROR at line 1:

ORA-01950: no privileges on tablespace 'SYSTEM'

The users were created correctly

[Former Member]

Hi Rubin,

Firstly, grant rights to the users, as below;

GRANT CONNECT, RESOURCE TO "OPS$<HOSTNAME>\SAPSERVICE<SID>";

GRANT CONNECT, RESOURCE TO "OPS$<HOSTNAME>\<SID>ADM";

Then, apply steps below;

CREATE TABLE "OPS$<HOSTNAME>\<ABAP_SID>ADM".SAPUSER (USERID VARCHAR2(256), PASSWD VARCHAR2(256));

CREATE SYNONYM "OPS$<HOSTNAME>\SAPSERVICE<ABAP_SID>".SAPUSER FOR "OPS$<HOSTNAME>\<ABAP_SID>ADM".SAPUSER;

GRANT SELECT, UPDATE ON "OPS$<HOSTNAME>\<ABAP_SID>ADM".SAPUSER TO "OPS$<HOSTNAME>\SAPSERVICE<ABAP_SID>";

INSERT INTO "OPS$<HOSTNAME>\<ABAP_SID>ADM".SAPUSER VALUES ('<Java database owner (Ex:SAPSR3DB)>', '<Password>');

COMMIT;

At this stage, please note that even you can use existing ABAP instance as a gateway, I recommend that you install a new standalone gateway. This because, that ABAP gateway is belong to the its own ABAP system. When you are executing br*tools, it will use existing environment variables (such as ORACLE_SID, dbs_ora_schema). Because of those values are belongs to the ABAP system, you will not be able to execute the commands successfully. When you install a new standalone gateway, it will have its own environment variables. By doing so, your existing ABAP stack will not be affected by this configuration.

I hope that I clarified issue,

Best regards,

Orkun Gedik

[Former Member]

Hi Orkun,

I´ve executed the previous steps correctly. But, now what can i do?

In the connection of database in DBACOCKPIT I´ve filled with OPS$hostgatewayuserADM, but the connection is not successfully

What is the function of SAP gateway in this landscape?

The log show this:

Parameters:-u / -jid FLL__20110510122922 -sid SID -c force -t online -m full -p initsid.sap

BR0051I BRBACKUP 7.00 (52)

BR0055I Start of database backup: befvuhyl.fnd 2011-05-10 12.29.27

BR0484I BRBACKUP log file: D:oraclePBIsapbackup efvuhyl.fnd

BR0280I BRBACKUP time stamp: 2011-05-10 12.29.29

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

'CONNECT /'

ORA-01045: user OPS$DOMAINSAPSERVICEPBI lacks CREATE SESSION privilege; logon denied

BR0310E Connect to database instance SID failed

BR0280I BRBACKUP time stamp: 2011-05-10 12.29.29

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

'CONNECT /'

ORA-01045: user OPS$DOMAINSAPSERVICEPBI lacks CREATE SESSION privilege; logon denied

BR0310E Connect to database instance SID failed

[Former Member]

Hi Ruben,

Where did you set "OPS$host\gatewayuserADM" value? You should use dbowner (Ex:SAPSR3) not ""OPS$host\gatewayuserADM" on the DBACOCKPIT tx. Please find the configuration summary, below;

1) You created "OPS$host\gatewayuserADM".SAPUSER table, on the Java database. Granted user rights to this table (all the steps that I've noted previously),

2) You installed a standalone gateway and configured same environment variables as Java "sidadm" user,

3) If you are able to collect data from DBACOCKPIT succesfully, with this configuration, you should be able to execute DB13 jobs over remote database, also.

First two items are prerequisites to execute DB13 jobs over remote database.

Best regards,

Orkun Gedik

[Former Member]

Hi ,

Please run sapdba_role.sql via orasid in case you are using UNIX.

sqlplus "/as sysdba" @sapdba_role.sql SR3 (if your schema is SAPSR3)

Thanks..

Mohit

[Former Member]

Hi Orkun,

Where did you set "OPS$hostgatewayuserADM" value? You should use dbowner (Ex:SAPSR3) not ""OPS$hostgatewayuserADM" on the DBACOCKPIT tx. Please find the configuration summary, below;

I´ve put SAPSR3DB in the remote connection to the database

-- MESSAGE Database connection <NAME CONNECTION>L established successfully

1) You created "OPS$hostgatewayuserADM".SAPUSER table, on the Java database. Granted user rights to this table (all the steps that I've noted previously),

I've connected to the server with <JAVASID>adm and put the next sql sentences

CREATE USER "OPS$hostADM".SAPUSER VALUES ('SAPSR3DB', 'password');

COMMIT;

2) You installed a standalone gateway and configured same environment variables as Java "sidadm" user,

I´ve put the E.V for sidadm

ORACLE_HOME

ORACLE_SID

SAPDATA_HOME

TNS_ADMIN

3) If you are able to collect data from DBACOCKPIT succesfully, with this configuration, you should be able to execute DB13 jobs over remote database, also.

In the DBACOCKPIT only appear info in the Performance Overview in the other tabs nothing appears

First two items are prerequisites to execute DB13 jobs over remote database.

[Former Member]

Hi Ruben,

As a last step, did you checked gateway options in "SAPXPG_DBDEST_<hostname>", at SM59 tx?

Best regards,

Orkun Gedik

[Former Member]

Not This method I´ve not configured

[Former Member]

Hi Ruben,

I didn't say your configuration is working. I just note that did you checked SM59 connection?

Best regards,

Orkun Gedik

[Former Member]

I´ve configured the RFC SAPXPG_DBDEST_HOST, but in the connections of database in dbacockpit I don´t know how to setting this connection.

Remote Database is sure, but in the next two options:

Database Connection

Via RFC Connection

RFC Connection

I´ve marked the all options but always RFC destination SAPXPG_DBDEST_Host: Communication error 'COMMUNICATION_FAILURE'

[Former Member]

Hi Ruben,

The system generates "SAPXPG_DBDEST_HOST" connection, automatically. It is really hard to figure out what the problem is ,without investigating the configuration on the site. At this stage, I recommend that you open an OSS message in order to investigate the issue, on the site.

Best regards,

Orkun Gedik

[Former Member]

The @sapdba_role.sql is mandatory?

[Former Member]

It means that DBACOCKPIT cannot connect to the remote gateway. Check your firewall or the system is up and running. You must be sure that this connection is working properly.

Best regards,

Orkun Gedik

[Former Member]

Hi Orkun,

How can undo the steps created before? I refer about the creation of users,etc. To left the DB in the status before this changes

More thanks

[Former Member]

Hi Ruben,

You just need to drop newly created "SAPUSER" table and the related synonym. Please be careful while dropping those objects. If you installed a standalone gateway, you can uninstall it easily. You don't need to do any thing, over OS level.

I hope that I clarified the issue.

Best regards,

Orkun Gedik

[Former Member]

Hi Orkun,

I´ve connected with the database and now I can see the space statistics, scheduled backups.

But the problem now is when I´ve scheduled and Check and update optimizer statistics, Cleanup logs, Check database but always I get and error. I can see the log file over sap system, but I can´t find the file , for example cefweoev.log, in the server.

Where are stored this log files?

I´ve search the logs of the scheduled tasks of ABAP databases and the extension of

optimizer statistics --> *.sta

Check database--> *.chk

Then the file logs created for the scheduled tasks of remote databases doesn´t create?¿

More thanks.

[Former Member]

Hi Ruben,

The configuration is working properly. Then, you have good news

The answer is; log files are created at the remote side.

For the instance, you are executing an "UpdateStats" job on the "DBA Planning Calendar", over the remote system. So, during the process and at the end of the process, you'll be able to see the trace files on remote system "/oracle/<SID>/sapcheck" path. Check the environment variables, including "SAPTRACE".

Best regards,

Orkun Gedik

[sivakumar_kilari3]

Hi,

> BR0252E Function fopen() failed for 'F:\oracle\orasap\102\database\initepd.sap' at location BrInitSapRead-1

> BR0253E errno 13: Permission denied

> BR0159E Error reading BR*Tools profile F:\oracle\orasap\102\database\initepd.sap

Problem is initepd.sap profile. I think there is some special character.

Execute BRTOOLS at OS level login with sidadm user. You will get error message or paste your initepd.sap prfile

Thanks

Siva

[Former Member]

1. @(#) $Id: //bas/701_REL/src/ccm/rsbr/initNT.sap#3 $ SAP

########################################################################

1. #

2. SAP BR*Tools sample profile. #

3. The parameter syntax is the same as for init.ora parameters. #

4. Enclose parameter values which consist of more than one symbol in #

5. double quotes. #

6. After any symbol, parameter definition can be continued on the next #

7. line. #

8. A parameter value list should be enclosed in parentheses, the list #

9. items should be delimited by commas. #

10. There can be any number of white spaces (blanks, tabs and new lines) #

11. between symbols in parameter definition. #

12. Comment lines must start with a hash character. #

13. #

########################################################################

1. backup mode [all | all_data | full | incr | sap_dir | ora_dir

2. | all_dir | <tablespace_name> | <file_id> | <file_id1>-<file_id2>

3. | <generic_path> | (<object_list>)]

4. default: all

backup_mode = all

1. restore mode [all | all_data | full | incr | incr_only | incr_full

2. | incr_all | <tablespace_name> | <file_id> | <file_id1>-<file_id2>

3. | <generic_path> | (<object_list>) | partial | non_db

4. redirection with '=' is not supported here - use option '-m' instead

5. default: all

restore_mode = all

1. backup type [offline | offline_force | offline_standby | offline_split

2. | offline_mirror | offline_stop | online | online_cons | online_split

3. | online_mirror | online_standby | offstby_split | offstby_mirror

4. default: offline

backup_type = online

1. backup device type

2. [tape | tape_auto | tape_box | pipe | pipe_auto | pipe_box | disk

3. | disk_copy | disk_standby | stage | stage_copy | stage_standby

4. | util_file | util_file_online | rman_util | rman_disk | rman_stage

5. | rman_prep]

6. default: tape

backup_dev_type = disk

1. backup root directory [<path_name> | (<path_name_list>)]

2. default: %SAPDATA_HOME%\sapbackup

backup_root_dir = F:\oracle\D10\sapbackup

1. stage root directory [<path_name> | (<path_name_list>)]

2. default: value of the backup_root_dir parameter

stage_root_dir = F:\oracle\D10\sapbackup

1. compression flag [no | yes | hardware | only]

2. default: no

compress = no

1. compress command

2. first $-character is replaced by the source file name

3. second $-character is replaced by the target file name

4. <target_file_name> = <source_file_name>.Z

5. for compress command the -c option must be set

6. recommended setting for brbackup -k only run:

7. "%SAPEXE%\mkszip -l 0 -c $ > $"

8. no default

compress_cmd = "D:\usr\sap\D10\SYS\exe\uc\NTAMD64\mkszip -c $ > $"

1. uncompress command

2. first $-character is replaced by the source file name

3. second $-character is replaced by the target file name

4. <source_file_name> = <target_file_name>.Z

5. for uncompress command the -c option must be set

6. no default

uncompress_cmd = "D:\usr\sap\D10\SYS\exe\uc\NTAMD64\uncompress -c $ > $"

1. directory for compression [<path_name> | (<path_name_list>)]

2. default: value of the backup_root_dir parameter

compress_dir = E:\oracle\D10\sapreorg

1. brarchive function [save | second_copy | double_save | save_delete

2. | second_copy_delete | double_save_delete | copy_save

3. | copy_delete_save | delete_saved | delete_copied]

4. default: save

[Former Member]

archive_function = save

1. directory for archive log copies to disk

2. default: first value of the backup_root_dir parameter

archive_copy_dir = F:\oracle\D10\sapbackup

1. directory for archive log copies to stage

2. default: first value of the stage_root_dir parameter

archive_stage_dir = F:\oracle\D10\sapbackup

1. delete archive logs from duplex destination [only | no | yes | check]

2. default: only

3. archive_dupl_del = only

4. new sapdata home directory for disk_copy | disk_standby

5. no default

6. new_db_home = X:\oracle\C11

7. stage sapdata home directory for stage_copy | stage_standby

8. default: value of the new_db_home parameter

9. stage_db_home = /oracle/C11

10. original sapdata home directory for split mirror disk backup

11. no default

12. orig_db_home = /oracle/C11

13. remote host name

14. no default

15. remote_host = <host_name>

16. remote user name

17. default: current operating system user

18. remote_user = <user_name>

19. tape copy command [cpio | cpio_gnu | dd | dd_gnu | rman | rman_gnu

20. | rman_dd | rman_dd_gnu]

21. default: cpio

tape_copy_cmd = cpio

1. disk copy command [copy | copy_gnu | dd | dd_gnu | rman | rman_gnu

2. | rman_set | rman_set_gnu | ocopy]

3. default: copy

disk_copy_cmd = copy

1. stage copy command [rcp | scp | ftp]

2. default: rcp

stage_copy_cmd = rcp

1. pipe copy command [rsh | ssh]

2. default: rsh

pipe_copy_cmd = rsh

1. flags for cpio output command

2. default: -ovB

cpio_flags = -ovB

1. flags for cpio input command

2. default: -iuvB

cpio_in_flags = -iuvB

1. flags for cpio command for copy of directories to disk

2. default: -pdcu

3. use flags -pdu for gnu tools

cpio_disk_flags = -pdcu

1. flags for dd output command

2. default: "obs=16k"

3. caution: option "obs=" not supported for Windows

4. recommended setting:

5. Unix: "obs=nk bs=nk", example: "obs=64k bs=64k"

6. Windows: "bs=nk", example: "bs=64k"

dd_flags = "bs=64k"

1. flags for dd input command

2. default: "ibs=16k"

3. caution: option "ibs=" not supported for Windows

4. recommended setting:

5. Unix: "ibs=nk bs=nk", example: "ibs=64k bs=64k"

6. Windows: "bs=nk", example: "bs=64k"

dd_in_flags = "bs=64k"

1. number of members in RMAN save sets [ 1 | 2 | 3 | 4 | tsp | all ]

2. default: 1

saveset_members = 1

1. additional parameters for RMAN

2. rman_channels and rman_filesperset are only used when rman_util,

3. rman_disk or rman_stage

4. rman_channels defines the number of parallel sbt channel allocations

5. rman_filesperset = 0 means:

6. one file per save set - for non-incremental backups

7. all files in one save set - for incremental backups

8. the others have the same meaning as for native RMAN

[Former Member]

1. rman_channels = 1

2. rman_filesperset = 0

3. rman_maxpiecesize = 0 # in KB - former name rman_kbytes

4. rman_rate = 0 # in KB - former name rman_readrate

5. rman_maxopenfiles = 0

6. rman_maxsetsize = 0 # in KB - former name rman_setsize

7. additional parameters for RMAN version 8.1

8. the parameters have the same meaning as for native RMAN

9. rman_diskratio = 0 # deprecated in Oracle 10g

10. rman_pool = 0

11. rman_copies = 0 | 1 | 2 | 3 | 4 # former name rman_duplex

12. rman_proxy = no | yes | only

13. special parameters for an external backup library, example:

14. rman_parms = "BLKSIZE=65536 ENV=(BACKUP_SERVER=HOSTNAME)"

15. rman_send = "'<command>'"

16. rman_send = ("channel sbt_1 '<command1>' parms='<parameters1>'",

17. "channel sbt_2 '<command2>' parms='<parameters2>'")

18. rman_compress = no | yes

19. rman_maxcorrupt = (<dbf_name>|<dbf_id>:<corr_cnt>, ...)

20. remote copy-out command (backup_dev_type = pipe)

21. $-character is replaced by current device address

22. no default

copy_out_cmd = "dd ibs=8k obs=64k of=$"

1. remote copy-in command (backup_dev_type = pipe)

2. $-character is replaced by current device address

3. no default

copy_in_cmd = "dd ibs=64k obs=8k if=$"

1. rewind command

2. $-character is replaced by current device address

3. no default

4. operating system dependent, examples:

5. HP-UX: "mt -f $ rew"

6. TRU64: "mt -f $ rewind"

7. AIX: "tctl -f $ rewind"

8. Solaris: "mt -f $ rewind"

9. Windows: "mt -f $ rewind"

10. Linux: "mt -f $ rewind"

rewind = "mt -f $ rewind"

1. rewind and set offline command

2. $-character is replaced by current device address

3. default: value of the rewind parameter

4. operating system dependent, examples:

5. HP-UX: "mt -f $ offl"

6. TRU64: "mt -f $ offline"

7. AIX: "tctl -f $ offline"

8. Solaris: "mt -f $ offline"

9. Windows: "mt -f $ offline"

10. Linux: "mt -f $ offline"

rewind_offline = "mt -f $ offline"

1. tape positioning command

2. first $-character is replaced by current device address

3. second $-character is replaced by number of files to be skipped

4. no default

5. operating system dependent, examples:

6. HP-UX: "mt -f $ fsf $"

7. TRU64: "mt -f $ fsf $"

8. AIX: "tctl -f $ fsf $"

9. Solaris: "mt -f $ fsf $"

10. Windows: "mt -f $ fsf $"

11. Linux: "mt -f $ fsf $"

tape_pos_cmd = "mt -f $ fsf $"

1. mount backup volume command in auto loader / juke box

2. used if backup_dev_type = tape_box | pipe_box

3. no default

4. mount_cmd = "<mount_cmd> $ $ $ [$]"

5. dismount backup volume command in auto loader / juke box

6. used if backup_dev_type = tape_box | pipe_box

7. no default

8. dismount_cmd = "<dismount_cmd> $ $ [$]"

9. split mirror disks command

10. used if backup_type = offline_split | online_split | offline_mirror

11. | online_mirror

12. no default

13. split_cmd = "<split_cmd> [$]"

14. resynchronize mirror disks command

15. used if backup_type = offline_split | online_split | offline_mirror

16. | online_mirror

17. no default

18. resync_cmd = "<resync_cmd> [$]"

19. additional options for SPLITINT interface program

20. no default

21. split_options = "<split_options>"

22. resynchronize after backup flag [no | yes]

23. default: no

24. split_resync = no

25. pre-split command

26. no default

27. pre_split_cmd = "<pre_split_cmd>"

28. post-split command

29. no default

30. post_split_cmd = "<post_split_cmd>"

31. pre-shut command

32. no default

33. pre_shut_cmd = "<pre_shut_cmd>"

34. post-shut command

35. no default

36. post_shut_cmd = "<post_shut_cmd>"

37. volume size in KB = K, MB = M or GB = G (backup device dependent)

38. default: 1200M

39. recommended values for tape devices without hardware compression:

40. 60 m 4 mm DAT DDS-1 tape: 1200M

41. 90 m 4 mm DAT DDS-1 tape: 1800M

42. 120 m 4 mm DAT DDS-2 tape: 3800M

43. 125 m 4 mm DAT DDS-3 tape: 11000M

44. 112 m 8 mm Video tape: 2000M

45. 112 m 8 mm high density: 4500M

46. DLT 2000 10/20 GB: 10000M

47. DLT 2000XT 15/30 GB: 15000M

48. DLT 4000 20/40 GB: 20000M

49. DLT 7000 35/70 GB: 35000M

50. recommended values for tape devices with hardware compression:

51. 60 m 4 mm DAT DDS-1 tape: 1000M

52. 90 m 4 mm DAT DDS-1 tape: 1600M

53. 120 m 4 mm DAT DDS-2 tape: 3600M

54. 125 m 4 mm DAT DDS-3 tape: 10000M

55. 112 m 8 mm Video tape: 1800M

56. 112 m 8 mm high density: 4300M

57. DLT 2000 10/20 GB: 9000M

58. DLT 2000XT 15/30 GB: 14000M

59. DLT 4000 20/40 GB: 18000M

60. DLT 7000 35/70 GB: 30000M

tape_size = 100G

1. volume size in KB = K, MB = M or GB = G used by brarchive

2. default: value of the tape_size parameter

3. tape_size_arch = 100G

4. level of parallel execution

5. default: 0 - set to number of backup devices

[Former Member]

exec_parallel = 0

1. address of backup device without rewind

2. [<dev_address> | (<dev_address_list>)]

3. no default

4. operating system dependent, examples:

5. HP-UX: /dev/rmt/0mn

6. TRU64: /dev/nrmt0h

7. AIX: /dev/rmt0.1

8. Solaris: /dev/rmt/0mn

9. Windows: /dev/nmt0 | /dev/nst0

10. Linux: /dev/nst0

tape_address = /dev/nmt0

1. address of backup device without rewind used by brarchive

2. default: value of the tape_address parameter

3. operating system dependent

4. tape_address_arch = /dev/nmt0

5. address of backup device with rewind

6. [<dev_address> | (<dev_address_list>)]

7. no default

8. operating system dependent, examples:

9. HP-UX: /dev/rmt/0m

10. TRU64: /dev/rmt0h

11. AIX: /dev/rmt0

12. Solaris: /dev/rmt/0m

13. Windows: /dev/mt0 | /dev/st0

14. Linux: /dev/st0

tape_address_rew = /dev/mt0

1. address of backup device with rewind used by brarchive

2. default: value of the tape_address_rew parameter

3. operating system dependent

4. tape_address_rew_arch = /dev/mt0

5. address of backup device with control for mount/dismount command

6. [<dev_address> | (<dev_address_list>)]

7. default: value of the tape_address_rew parameter

8. operating system dependent

9. tape_address_ctl = /dev/...

10. address of backup device with control for mount/dismount command

11. used by brarchive

12. default: value of the tape_address_rew_arch parameter

13. operating system dependent

14. tape_address_ctl_arch = /dev/...

15. volumes for brarchive

16. [<volume_name> | (<volume_name_list>) | SCRATCH]

17. no default

volume_archive = (D10A01, D10A02, D10A03, D10A04, D10A05,

D10A06, D10A07, D10A08, D10A09, D10A10,

D10A11, D10A12, D10A13, D10A14, D10A15,

D10A16, D10A17, D10A18, D10A19, D10A20,

D10A21, D10A22, D10A23, D10A24, D10A25,

D10A26, D10A27, D10A28, D10A29, D10A30)

1. volumes for brbackup

2. [<volume_name> | (<volume_name_list>) | SCRATCH]

3. no default

volume_backup = (D10B01, D10B02, D10B03, D10B04, D10B05,

D10B06, D10B07, D10B08, D10B09, D10B10,

D10B11, D10B12, D10B13, D10B14, D10B15,

D10B16, D10B17, D10B18, D10B19, D10B20,

D10B21, D10B22, D10B23, D10B24, D10B25,

D10B26, D10B27, D10B28, D10B29, D10B30)

1. expiration period for backup volumes in days

2. default: 30

expir_period = 30

1. recommended usages of backup volumes

2. default: 100

tape_use_count = 100

1. backup utility parameter file

2. default: no parameter file

3. util_par_file = initD10.utl

4. mount/dismount command parameter file

5. default: no parameter file

6. mount_par_file = initD10.mnt

7. Oracle connection name to the primary database

8. [primary_db = <conn_name> | LOCAL]

9. no default

10. primary_db = <conn_name>

11. Oracle connection name to the standby database

12. [standby_db = <conn_name> | LOCAL]

13. no default

14. standby_db = <conn_name>

15. description of parallel instances for Oracle RAC

16. parallel_instances = <inst_desc> | (<inst_desc_list>)

17. <inst_desc_list> - <inst_desc>[,<inst_desc>...]

18. <inst_desc> - <Oracle_sid>:<Oracle_home>@<conn_name>

19. <Oracle_sid> - Oracle system id for parallel instance

20. <Oracle_home> - Oracle home for parallel instance

21. <conn_name> - Oracle connection name to parallel instance

22. Please include the local instance in the parameter definition!

23. default: no parallel instances

24. example for initRAC001.sap:

25. parallel_instances = (RAC001:/oracle/RAC/920_64@RAC001,

26. RAC002:/oracle/RAC/920_64@RAC002, RAC003:/oracle/RAC/920_64@RAC003)

27. handling of Oracle RAC database services [no | yes]

28. default: no

29. db_services = yes

30. database owner of objects to be checked

31. <owner> | (<owner_list>)

32. default: all SAP owners

33. check_owner = sapr3

34. database objects to be excluded from checks

35. all_part | non_sap | [<owner>.]<table> | [<owner>.]<index>

36. | [<owner>.][<prefix>]*[<suffix>] | <tablespace> | (<object_list>)

37. default: no exclusion, example:

38. check_exclude = (SDBAH, SAPR3.SDBAD)

39. special database check conditions

40. ("<type>:<cond>:<active>:<sever>:[<chkop>]:[<chkval>]:[<unit>]", ...)

41. check_cond = (<cond_list>)

42. database owner of SDBAH, SDBAD and XDB tables for cleanup

43. <owner> | (<owner_list>)

44. default: all SAP owners

45. cleanup_owner = sapr3

46. retention period in days for brarchive log files

47. default: 30

48. cleanup_brarchive_log = 30

49. retention period in days for brbackup log files

50. default: 30

51. cleanup_brbackup_log = 30

52. retention period in days for brconnect log files

53. default: 30

54. cleanup_brconnect_log = 30

55. retention period in days for brrestore log files

56. default: 30

57. cleanup_brrestore_log = 30

58. retention period in days for brrecover log files

59. default: 30

60. cleanup_brrecover_log = 30

61. retention period in days for brspace log files

62. default: 30

63. cleanup_brspace_log = 30

64. retention period in days for archive log files saved on disk

65. default: 30

66. cleanup_disk_archive = 30

67. retention period in days for database files backed up on disk

68. default: 30

69. cleanup_disk_backup = 30

70. retention period in days for brspace export dumps and scripts

71. default: 30

72. cleanup_exp_dump = 30

73. retention period in days for Oracle trace and audit files

74. default: 30

75. cleanup_ora_trace = 30

76. retention period in days for records in SDBAH and SDBAD tables

77. default: 100

78. cleanup_db_log = 100

79. retention period in days for records in XDB tables

80. default: 100

81. cleanup_xdb_log = 100

82. retention period in days for database check messages

83. default: 100

84. cleanup_check_msg = 100

85. database owner of objects to adapt next extents

[Former Member]

1. <owner> | (<owner_list>)

2. default: all SAP owners

3. next_owner = sapr3

4. database objects to adapt next extents

5. all | all_ind | special | [<owner>.]<table> | [<owner>.]<index>

6. | [<owner>.][<prefix>]*[<suffix>] | <tablespace> | (<object_list>)

7. default: all abjects of selected owners, example:

8. next_table = (SDBAH, SAPR3.SDBAD)

9. database objects to be excluded from adapting next extents

10. all_part | [<owner>.]<table> | [<owner>.]<index>

11. | [<owner>.][<prefix>]*[<suffix>] | <tablespace> | (<object_list>)

12. default: no exclusion, example:

13. next_exclude = (SDBAH, SAPR3.SDBAD)

14. database objects to get special next extent size

15. all_sel:<size>[/<limit>] | [<owner>.]<table>:<size>[/<limit>]

16. | [<owner>.]<index>:<size>[/<limit>]

17. | [<owner>.][<prefix>]*[<suffix>]:<size>[/<limit>]

18. | (<object_size_list>)

19. default: according to table category, example:

20. next_special = (SDBAH:100K, SAPR3.SDBAD:1M/200)

21. maximum next extent size

22. default: 2 GB - 5 * <database_block_size>

23. next_max_size = 1G

24. maximum number of next extents

25. default: 0 - unlimited

26. next_limit_count = 300

27. database owner of objects to update statistics

28. <owner> | (<owner_list>)

29. default: all SAP owners

30. stats_owner = sapr3

31. database objects to update statistics

32. all | all_ind | all_part | missing | info_cubes | dbstatc_tab

33. | dbstatc_mon | dbstatc_mona | [<owner>.]<table> | [<owner>.]<index>

34. | [<owner>.][<prefix>]*[<suffix>] | <tablespace> | (<object_list>)

35. | harmful | locked | system_stats | oradict_stats | oradict_tab

36. default: all abjects of selected owners, example:

37. stats_table = (SDBAH, SAPR3.SDBAD)

38. database objects to be excluded from updating statistics

39. all_part | info_cubes | [<owner>.]<table> | [<owner>.]<index>

40. | [<owner>.][<prefix>]*[<suffix>] | <tablespace> | (<object_list>)

41. default: no exclusion, example:

42. stats_exclude = (SDBAH, SAPR3.SDBAD)

43. method for updating statistics for tables not in DBSTATC

44. E | EH | EI | EX | C | CH | CI | CX | A | AH | AI | AX | E= | C= | =H

45. | =I | =X | +H | +I

46. default: according to internal rules

47. stats_method = E

48. sample size for updating statistics for tables not in DBSTATC

49. P<percentage_of_rows> | R<thousands_of_rows>

50. default: according to internal rules

51. stats_sample_size = P10

52. number of buckets for updating statistics with histograms

53. default: 75

54. stats_bucket_count = 75

55. threshold for collecting statistics after checking

56. <threshold> | (<threshold> [, all_part:<threshold>

57. | info_cubes:<threshold> | [<owner>.]<table>:<threshold>

58. | [<owner>.][<prefix>]*[<suffix>]:<threshold>

59. | <tablespace>:<threshold> | <object_list>])

60. default: 50%

61. stats_change_threshold = 50

62. number of parallel threads for updating statistics

63. default: 1

64. stats_parallel_degree = 1

65. processing time limit in minutes for updating statistics

66. default: 0 - no limit

67. stats_limit_time = 0

68. parameters for calling DBMS_STATS supplied package

69. all:R|B[<buckets>|A|S|R]:0|<degree>A|D

70. | all_part:R|B[<buckets>|A|S|R]:0|<degree>A|D

71. | info_cubes:R|B:A|D|0|<degree>

72. | [<owner>.]<table>:R|B[<buckets>|A|S|R]:0|<degree>A|D

73. | [<owner>.][<prefix>]*[<suffix>]:R|B[<buckets>|A|S|R]:0|<degree>A|D

74. | (<object_list>) | NO

75. R|B[<buckets>|A|S|R]:

76. 'R' - row sampling, 'B' - block sampling,

77. <buckets> - histogram buckets count, 'A' - auto buckets count,

78. 'S' - skew only, 'R' - repeat

79. <degree>A|D:

80. <degree> - dbms_stats parallel degree, '0' - table degree,

81. 'A' - auto degree, 'D' - default degree

82. default: ALL:R:0

83. stats_dbms_stats = ([ALL:R:1,][<owner>.]<table>:R:<degree>,...)

84. definition of info cube tables

85. default | rsnspace_tab | [<owner>.]<table>

86. | [<owner>.][<prefix>]*[<suffix>] | (<object_list>) | null

87. default: rsnspace_tab

88. stats_info_cubes = (/BIC/D, /BI0/D, ...)

89. special statistics settings

90. (<table>:[<owner>]:<active>:[<method>]:[<sample>], ...)

91. stats_special = (<special_list>)

92. recovery type [complete | dbpit | tspit | reset | restore | apply

93. | disaster]

94. default: complete

95. recov_type = complete

96. directory for brrecover file copies

97. default: $SAPDATA_HOME/sapbackup

98. recov_copy_dir = E:\oracle\D10\sapbackup

99. time period for searching for backups

100. 0 - all available backups, >0 - backups from n last days

101. default: 30

102. recov_interval = 30

103. degree of paralelism for applying archive log files

104. 0 - use Oracle default parallelism, 1 - serial, >1 - parallel

105. default: Oracle default

106. recov_degree = 0

107. number of lines for scrolling in list menus

108. 0 - no scrolling, >0 - scroll n lines

109. default: 20

110. scroll_lines = 20

111. time period for displaying profiles and logs

112. 0 - all available logs, >0 - logs from n last days

113. default: 30

114. show_period = 30

115. directory for brspace file copies

116. default: $SAPDATA_HOME/sapreorg

117. space_copy_dir = E:\oracle\D10\sapreorg

118. directory for table export dump files

119. default: $SAPDATA_HOME/sapreorg

120. exp_dump_dir = E:\oracle\D10\sapreorg

121. database tables for reorganization

122. [<owner>.]<table> | [<owner>.][<prefix>]*[<suffix>]

123. | [<owner>.][<prefix>]%[<suffix>] | (<table_list>)

124. no default

125. reorg_table = (SDBAH, SAPR3.SDBAD)

126. database indexes for rebuild

127. [<owner>.]<index> | [<owner>.][<prefix>]*[<suffix>]

128. | [<owner>.][<prefix>]%[<suffix>] | (<index_list>)

129. no default

130. rebuild_index = (SDBAH_{0, SAPR3.SDBAD}0)

131. database tables for export

132. [<owner>.]<table> | [<owner>.][<prefix>]*[<suffix>]

133. | [<owner>.][<prefix>]%[<suffix>] | (<table_list>)

134. no default

135. exp_table = (SDBAH, SAPR3.SDBAD)

136. database tables for import

137. <table> | (<table_list>)

138. no default

139. do not specify table owner in the list - use -o|-owner option for this

140. imp_table = (SDBAH, SDBAD)

[Former Member]

There are two D.B in one oracle_home.

But I want to scheduled backups from DB13 to the external database of enteprise portal of sap.

[Former Member]

There are two D.B in one oracle_home.

But I want to scheduled backups from DB13 to the external database of enteprise portal of sap.

[sivakumar_kilari3]

Did you execute BRTOOLS at OS level?

Thanks

Siva

[Former Member]

Yes, I´ve executed the BRTOOLS under sidadm user, and works fine.

[sivakumar_kilari3]

F:\oracle\orasap\102\database\initepd.sap

Have you given full permissions to 102 and database folders to sidadm and Sapservicesid users.

Thanks

Siva

[Former Member]

Hi Ruben

Try to perform a local DB connection using the schema user

SQLPLUS SAPD10DB/<password>@D10

If you can connect sucessful: check note 134592.

If you cannot connect, check note 400241,

Hope that it help you

Kind regards

Marcelo Macedo

[Former Member]

Thanks for your answer msmacedo,

I can connect with SQLPLUS SAPD10DB/@D10,

But in the note 134592 not appear the error code that I have it. It´s the same?

[Former Member]

Hi Ruben,

Password related issue will throw 1017. You can change the password for the schema through brtools.

Once done you should be able to login.

[Former Member]

I´ve executed the next commando with sidadm and it´s correct

brconnect -u / -c -f check