Most Annoying Oracle Errors during SAP connections ORA- 01017 when brarchive / brbackup runs. (OSS notes 400241 - 361641 -) Check the following : - init ora should have os_authent_prefix ops$ , remote_os_authent TRUE - check if OPS$SIDADM exist and it owns SAPUSER table and it has SAPCHEMAOWNER and password enetered in the table: select * from "OPS$<SID>ADM".SAPUSER; If there are no entries set the password of SAPCHEMAOWNER: brconnect -u system/<password> -f chpass -o <sapowner> -p <password> - Make sure the sresource and connect is assigned to OPS$ users. To be able to process brbackup make sure sapdaba is assigned as well.: SELECT GRANTED_ROLE FROM DBA_ROLE_PRIVS WHERE GRANTEE = 'OPS$<os_user>'; - How to assign sapdba and sapoper to system : Connect as sys grant sysdba to system; grant sysoper to system; - If you cannot login as sys change the password and relogin using orasid user: orapws file=PWDSID.ora password=xxxx entries=100 ORA - 01031 Insufficient privileges during brbackup run. Make sure orasid belongs to dba and oper and sidadm belongs to sapsys, dba and oper at the OS level. (OSS note 134592) Run sapdba_role.sql as orasid: sqlplus /nolog @sapdba_role.sql SID (for 9i - use SID UNIX for 8i) ORA- 012541 Tnsnames.ora error. Check db_domain in init.ora. If there is domain defined make sure tnsnames.ora has domain as well. Run tnsping SID R3trans -d For 9i prefer to use SERVICE_NAME instead of SID in tnsnames.ora. |