grant sysoper to system

grant sysoper to system;

CONNECT can be abbreviated as CONN
To connect as System Operator rather than DBA, replace SYSDBA with SYSOPER in the syntax above.

Examples

SQL> sqlplus "system/manager@ss64.com"

SQL> sqlplus
SQL> connect "system/manager@ss64.com"

SQL> sqlplus "sys/manager@ss64.com AS SYSDBA"

C:\> Set oracle_sid=ss64
C:\> Set LOCAL=%oracle_sid%
SQL> sqlplus
SQL> connect "system/manager"

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

Prerequisites

BRARCHIVE and BRBACKUP, which are started on the standby database server, connect remotely to the primary database. Therefore, make sure that the instance string in the primary_db parameter is defined to Oracle SQL*Net in the tsnnames.ora file.

Test the connection in SQLPLUS with the following command:

connect system/<password>@<value_of_primary_db>

Procedure

1. Create an Oracle password file on the primary database:
   orapwd file=<ORACLE_HOME>/dbs/orapw<DBSID> password=<sys_password> entries=10
2. Set the remote_login_passwordfile parameter in the init<DBSID>.ora as follows:
   remote_login_passwordfile = exclusive
   If the parameter is entered only after an instance has been started up, you must restart it, so that the parameter becomes effective.
3. Start as user SYS and execute the Oracle command:
   SQL> connect / as sysdba
   SQL> grant sysoper to system;
   This grants the system user SYSOPER authorization on the primary database instance.
4. If necessary, change the password for the system user:
   SQL> alter user system identified by <password>;
    Note

   It is not necessary to give the SYSTEM user SYSOPER authority in the Oracle password file of the production database if the primary database remains open all the time before and during the backup of the standby database.

   For more information, see SAP Note 131610.