Using Oracle passwords with SAP
Which SAP user communicates with Oracle internally? Does SAP use the password of ora<sid> or <sid>adm to communicate with Oracle?

Thanks.

    Requires Free Membership to View

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

During normal operation, SAP does not use the ora<sid> or <sid>adm user to connect to the database. All SAP tables are owned by the database user SAPR3 (or SAP<SID> as of SAP release 6.20). The password of this user is stored in the database table SAPUSER owned by <sid>adm.

At startup, SAP first connects as user <sid>adm to the database. It retrieves the password entry from the SAPUSER table and then re-connects using the SAPR3 user with the correct password. The password of user SAPR3 should therefore always be changed with SAPDBA or BRTOOLS instead of using the standard Oracle tools.

This setup is explained in detail in the Database Security for Oracle white paper which is available for download at the SAP Developer Network (http://sdn.sap.com).

This was first published in September 2006

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.