Entering content frameProcedure documentation Starting the SAP Utility Programs Locate the document in its SAP Library structure

To avoid authorization problems when starting the SAP utility programs SAPDBA and BRBACKUP, bear in mind the following notes:

  1. On the database server create local groups ORA_<DBSID>_DBA and ORA_<DBSID>_OPER (or ORA_DBA and ORA_OPER). Include the SAP users <SID>ADM and SAPSERVICE<SID> in this group, if this has not been done during the installation.
  2. When you log on to the database using connect internal via SQLPLUS you no longer have to enter a password. The user is authorized to start and stop the database.

    You can now call SAPDBA, BRBACKUP and BRARCHIVE as usual:
    sapdba -u system/<password>

  3. SAPDBA
  4. If you call SAPDBA at operating system level, the following alternative to the procedure described in 1. is available. Use the password mechanism to start SAPDBA. The command line option is as follows:

    sapdba -U internal/<password>

    If you call SAPDBA without the option -U, the password is requested interactively. If the database logon is as super user internal, the database user is sys, not system.

  5. BRBACKUP

If you call BRBACKUP at operating system level, the following alternatives (A;B) to the procedure described in 1. are available:

Example: brbackup -u internal/<password>

If the database logon is as super user internal, the standard user is sys, not system.

grant sysdba to system;

grant sysoper to system;

Now you can call BRBACKUP as usual:
brbackup -u system/<password>

 

 

Leaving content frame