BR*Tools Studio 7.10 for Oracle Multi-instance Server Standalone Part 2: Server, Database Instances and their Users

Transcription

1 BR*Tools Studio 7.10 for Oracle Multi-instance Server Standalone Part 2: Server, Database Instances and their Users Applies to: SAP BR*Tools Studio 7.10(2) for Oracle DBA on Unix/Linux with examples on IBM AIX. For more information, visit the Landscape Design and Architecture homepage. Summary This article describe server, database instances and users definitions in SAP BR*Tools Studio for Oracle DBA on Unix/Linux in Multi-instance Server Standalone scenario. The objective is to motivate this scenario usage. Also this article is considered to be first aid in frequently difficulties or issues found in this configuration. Thus, overcoming the difficulties of this configuration and elevating use and reliable of SAP BR*Tools Studio. Author: Alexandre Prudente Company: Independent Technology Consultant Created on: 20 December 2010 Author Bio Alexandre is a Brazilian Independent Technology Consultant. He has 12+ years of experience in Technology consultancy. He has worked in assessment, design, setup and operation of solution landscapes in great companies of telecommunications, data centers and retails. He has trained in SAP Netweaver Administrator academy and SAP BW academy SAP AG 1

2 Table of Contents Applies to:... 1 Summary... 1 Author Bio... 1 Table of Contents... 2 BR*Tools Studio: Server, Database Instances and their users... 3 BR*Tools Server instance authentication key... 4 Check the authentication key... 4 Authentication key creation... 4 Regular Server Instance Management... 5 Start BR*Tools Server instance... 5 Shutdown BR*Tools Server instance... 6 Shutdown BR*Tools Web Application... 6 Change BR*Tools Server password (optional)... 7 Database instance configuration... 7 Check the Database instance operation prerequisites... 7 Secure shell (SSH) configuration for the Database instance operation... 9 Add the Database instance in BR*Tools Studio Landscape Show all Database instances in BR*Tools Studio Landscape Alter the Database instance in BR*Tools Studio Landscape Remove the Database instance in BR*Tools Studio Landscape Users and Roles administration for each Database Instance in BR*Tools Studio Connect to Database instance in BR*Tools Studio Explain available roles in BR*Tools Studio Administration Add User to Database instance in BR*Tool Studio Administration Show all Database instances Users in BR*Tools Studio Administration Alter Database instance User in BR*Tools Studio Administration Alter your Database instance User Password in BR*Tools Studio Administration Remove Database instance User in BR*Tools Studio Administration BR*Tools Studio Wizard Related Content Disclaimer and Liability Notice SAP AG 2

3 BR*Tools Studio: Server, Database Instances and their users If you did Part 1 or if you have a BR*Tools Studio Server instance installed, you may manage your server instance and you may define your database instances landscape for management with this feature and their users. Our case study will go show regular procedures in BR*Tools Studio Server instance management. Also this study will go show how to database instances are defined in BR*Tools Studio Landscape using Secure Shell (SSH). Finally, this study will go show how to users are created for this database instances and which roles may be assigned with them SAP AG 3

4 BR*Tools Server instance authentication key For secure shell communication, you must have an authentication key shared between sender and receiver. This process will go treat of the BR*Tools Server instance authentication key only. Process 1. Check if you have an authentication key yet. 2. Authentication key creation. Check the authentication key Now, you will go check if you have an authentication key. 1. Open Operating system session (telnet, ssh and so) in BR*Tools Studio Server using their owner user. 2. Check if you have a RSA authentication key for your owner user and hostname, like the follow example. saphom:sapdba > grep sapdba@saphom ~/.ssh/id_rsa.pub Note: When you have a RSA authentication key, the check above will be result the authentication key line. In this case, the authentication key creation procedure is not necessary. Authentication key creation Now, you will go create the RSA authentication key 1. Open Operating system session (telnet, ssh and so) in BR*Tools Studio Server using their owner user. 2. Create the RSA authentication key with suggested directory and no passphrase, like the follow example. saphom:sapdba > ssh-keygen -t rsa Generating public/private rsa key pair. Enter file in which to save the key (/usr/sap/brtools/studio/.ssh/id_rsa): Created directory '/usr/sap/brtools/studio/.ssh'. Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /usr/sap/brtools/studio/.ssh/id_rsa. Your public key has been saved in /usr/sap/brtools/studio/.ssh/id_rsa.pub. The key fingerprint is: 48:9f:f1:eb:32:24:a0:1f:56:72:94:14:fc:bf:ce:49 sapdba@saphom 2010 SAP AG 4

5 Regular Server Instance Management These processes are used in regular management of BR*Tool Server instance. Process 1. Start BR*Tools Server instance. 2. Shutdown BR*Tools Server instance. 3. Shutdown BR*Tools Web Application or Server Exit. 4. Change BR*Tools Server password (optional). Start BR*Tools Server instance Before at all, you have to start BR*Tools Server instance like explained in the follow. 1. Open your internet browser. 2. Go to your SAP BR*Tools Studio Server application, using protocol HTTPS and hostname and port where it was installed Log on SAP BR*Tools Studio server using Administrator user and the same password specified in installation and click on Logon button. 4. On the Landscape tab, choose Server Startup. 5. Click on Start Up button. Note: When the startup process has finished the complete frame is showed and the Server Status has green light in Engine SAP AG 5

6 Shutdown BR*Tools Server instance Now, you may shut down the BR*Tools Server instance. 1. Open your internet browser. 2. Go to your SAP BR*Tools Studio Server application, using protocol HTTPS and hostname and port where it was installed Log on SAP BR*Tools Studio server using Administrator user and the same password specified in installation and click on Logon button. 4. On the Landscape tab, choose Server Shutdown. 5. Click on Shut Down button. 6. Confirm shutdown operation in pop up window. Note: When the shutdown process has finished the complete frame is showed and the Server Status has red light in Engine. Caution All running jobs have finished safely when you confirm shutdown operation. Recurrent jobs scheduled are preserved and run later at the correct time. However, all jobs scheduled for executing in downtime window are lost. Shutdown BR*Tools Web Application Now, you may exit the BR*Tools Server Web Application. 1. Open your internet browser. 2. Go to your SAP BR*Tools Studio Server application, using protocol HTTPS and hostname and port where it was installed Log on SAP BR*Tools Studio server using Administrator user and the same password specified in installation and click on Logon button. 4. On the Landscape tab, choose Server Exit. 5. Click on Exit button. 6. Confirm exit operation in pop up window. Note: Before, BR*Tools Server instance must be shut down for this operation works. This is safe process to stop completely BR*Tools Studio Web Application while the similar process described in Part 1 must be used in emergency situation only SAP AG 6

7 Change BR*Tools Server password (optional) Now, you may change the password of BR*Tools Server. 1. Open your internet browser. 2. Go to your SAP BR*Tools Studio Server application, using protocol HTTPS and hostname and port where it was installed Log on SAP BR*Tools Studio server using Administrator user and the same password specified in installation and click on Logon button. 4. On the Landscape tab, choose Server Password. 5. You will enter new password twice in safe mode. 6. Click on Confirm button. 7. Click on Change button. 8. Confirm change password operation in pop up window. Note: When the change password has finished the complete frame is showed. Caution Administrator user password was changed only in Server and it remains the same defined in another database instances when Administrator user was used in creation of them. Database instance configuration This process will go configure the Database instance in BR*Tools Studio Landscape. Process 1. Check the Database instance operation prerequisites. 2. Secure shell (SSH) configuration for the Database instance operation. 3. Add the Database instance in BR*Tools Studio Landscape. 4. Show all Database instances in BR*Tools Studio Landscape. 5. Alter the Database instance in BR*Tools Studio Landscape. 6. Remove the Database instance in BR*Tools Studio Landscape. Check the Database instance operation prerequisites Now, you will go check if you have all prerequisites for Database instance operation mentioned in Part Open Operating system session (telnet, ssh and so) in Database Server using their owner user. Note: Oracle Database owner user is ora<dbsid>. It is in lowercase and you need this password SAP AG 7

8 2. Check if you have a BR*Tools compatible version, like the follow example. sapdes:oranwh > brtools V BR0651I BRTOOLS 7.00 (42)... kernel release patch level Note: BR*Tools Studio is compatible with BR*Tools 7.10 Patch 12 or higher, or BR*Tools 7.00 Patch 34 or higher. When your BR*Tools are early or incompatible, you may download new one using SAP Note (Current versions of BR*Tools and SAPDBA). 3. Check if you have a Security Shell Connectivity Tools, like the follow example. sapdes:oranwh > ssh V OpenSSH_5.0p1, OpenSSL 0.9.8h 28 May 2008 Note: If you don t have a Security Shell Connectivity Tool, you may ask for your Unix/Linux system administrator. The most used is OpenSSH and it is available at but it would be recommend you looking for specific solution in your operating system vendor. The link may be useful in this research. 4. Check if you have a Security Shell directory, like the follow example. sapdes:oranwh > ls -ld ~/.ssh drwx oranwh dba 256 Dec 16 14:43 /home/oranwh/.ssh Note: If you don t have a Security Shell directory, you may create it with mkdir command or Authentication key creation procedure describe above using your current login session SAP AG 8

9 Secure shell (SSH) configuration for the Database instance operation Now, you will go configure Secure Shell communication between BR*Tools Studio Server and your Database instance. 1. Open Operating system session (telnet, ssh and so) in BR*Tools Studio Server using their owner user. 2. Establish Secure Shell communication. If it is first time then you have to confirm the connection with yes and provide the database owner user password in safe mode, like the follow example. saphom:sapdba > ssh -C "hostname ; id" The authenticity of host 'planhomdb ( )' can't be established. RSA key fingerprint is 6f:2e:48:3c:27:7c:44:19:f1:67:da:44:7a:d5:3b:c8. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'planhomdb, ' (RSA) to the list of known hosts. oranwh@planhomdb's password: <password> saphom uid=217(oranwh) gid=101(dba) groups=205(sapinst),207(oper) Note: In first Secure Shell communication, the ~/.ssh/ known_hosts configuration file is added with new target host key. 3. When provide password occurs then you have to export public BR*Tools Server authentication key and thus provide the database owner user password by the last time, like the follow example. saphom:sapdba > cat ~/.ssh/id_rsa.pub ssh oranwh@planhomdb -C "cat >> ~/.ssh/authorized_keys" oranwh@planhomdb's password: <password> 4. Check establishment Secure Shell communication with no more asking, like the follow example. saphom:sapdba > ssh oranwh@planhomdb -C "hostname ; id" saphom uid=217(oranwh) gid=101(dba) groups=205(sapinst),207(oper) 2010 SAP AG 9

10 Add the Database instance in BR*Tools Studio Landscape Now, you may add the database instance in your BR*Tools Studio Landscape. 1. Open your internet browser. 2. Go to your SAP BR*Tools Studio Server application, using protocol HTTPS and hostname and port where it was installed Log on SAP BR*Tools Studio server using Administrator user and the same password specified in installation and click on Logon button. 4. On the Landscape tab, choose Instances Create. 5. Fill the database instance information frame, like the follow example. Syntax Name Remote Shell : <DBSID> : ssh ora<dbsid>@<dbhost> x l ora<dbsid> C<space> Example Name : NWH Remote Shell : ssh oranwh@planhomdb x l oranwh C Note: Don t forget the end space in remote shell command. Some early versions of SSH don t have C option, if this occurs you may remove this option. 6. Click on Next button. 7. Fill the database instance connection frame beyond BR*Tools instance user password, like the follow example. Syntax Database User Name Database User Password BR*Tools Default Profile Example Database User Name Database User Password BR*Tools Default Profile : <SAPSR3 SAPSR3DB> : <password> : <ORACLE_HOME>/dbs/init<DBSID>.sap : SAPSR3 : <password> : /oracle/nwh/102_64/dbs/initnwh.sap Note: Frequently, SAPSR3 is database schema for ABAP database and SAPSR3DB is database schema for JAVA database. When your database instance is JAVA database only, you must read SAP Note (Installing BR tools on a non-abap database) and following it instructions. 8. Click on Confirm button SAP AG 10

11 9. Click on Create button. Note: When the create process has finished the complete frame is showed and the Server Status remains green light in Connectivity. Also Administrator account has been created for this database instance. Show all Database instances in BR*Tools Studio Landscape Now, you may show all database instances of your BR*Tools Studio Landscape with their connectivity status. 1. Open your internet browser. 2. Go to your SAP BR*Tools Studio Server application, using protocol HTTPS and hostname and port where it was installed Log on SAP BR*Tools Studio server using Administrator user and the same password specified in installation and click on Logon button. 4. On the Landscape tab, choose Instances All Instances. 5. Click on Isolated Instance Name for Detailed Information of this one. Alter the Database instance in BR*Tools Studio Landscape Now, you may alter the database instance in your BR*Tools Studio Landscape. 1. Open your internet browser. 2. Go to your SAP BR*Tools Studio Server application, using protocol HTTPS and hostname and port where it was installed Log on SAP BR*Tools Studio server using Administrator user and the same password specified in installation and click on Logon button. 4. On the Landscape tab, choose Instances All Instances. 5. Click on Isolated Instance. 6. On the Landscape tab, choose Instance Administration Alter. 7. Fill the database instance information frame with your corrections. 8. Click on Confirm button. 9. Click on Alter button. Note: When the alter process has finished the complete frame is showed and the Server Status remains green light in Connectivity SAP AG 11

12 Remove the Database instance in BR*Tools Studio Landscape Now, you may remove the database instance in your BR*Tools Studio Landscape. 1. Open your internet browser. 2. Go to your SAP BR*Tools Studio Server application, using protocol HTTPS and hostname and port where it was installed Log on SAP BR*Tools Studio server using Administrator user and the same password specified in installation and click on Logon button. 4. On the Landscape tab, choose Instances All Instances. 5. Click on Isolated Instance. 6. On the Landscape tab, choose Instance Administration Drop. 7. Click on Drop button. 8. Confirm drop operation in pop up window. Note: When the drop process has finished the complete frame is showed and the Server Status remains green light in Connectivity SAP AG 12

13 Users and Roles administration for each Database Instance in BR*Tools Studio This process will go configure the safe access of Database instance in BR*Tools Studio, allowing connections with identity defined, role assigned and some personalization. Process 1. Connect to Database instance in BR*Tools Studio. 2. Explain available roles in BR*Tools Studio Administration. 3. Add User to Database instance in BR*Tool Studio Administration. 4. Show all Database instances Users in BR*Tools Studio Administration. 5. Alter Database instance User in BR*Tools Studio Administration. 6. Alter your Database instance User Password in BR*Tools Studio Administration. 7. Remove Database instance User in BR*Tools Studio Administration. Connect to Database instance in BR*Tools Studio Now, you will go connect to database instances in BR*Tools Studio 1. Open your internet browser. 2. Go to your SAP BR*Tools Studio Server application, using protocol HTTPS and hostname and port where it was installed Log on Selected Database instance using Administrator user and respective password and click on Logon button. Note: Everything which you will do after this connection, it will be related with this isolate Database instance and it is agreed with your current user privileges. Caution When you terminate all your tasks in this database instance then you must disconnect this session for adequate information in BR*Tools Studio Landscape Clients SAP AG 13

14 Explain available roles in BR*Tools Studio Administration Role defines set of operations that user is allowed to perform. Each user has assigned only one role and this assignment is done in each Database instance. There are four discrete Roles in BR*Tools Studio like following figure show for Wizard and Administration tabs available in BR*Tools Studio when you are connected to an isolated Database instance. You may create all users that you need for each Database instance and you must assign right role to each user SAP AG 14

15 Add User to Database instance in BR*Tool Studio Administration Now, you may add the user database instance in your BR*Tools Studio Administration. 1. Connect to Database instance in BR*Tools Studio like item above. 2. On the Administration tab, choose Users Create. 3. Fill the user account information frame, like the follow example. Syntax Name : <USER_ID> Role : <BR Adm Br Op DB Adm DB Op> Password and Confirm Password : <BR user password> Database User Name : <SAPSR3 SAPSR3DB> Database User Password : <db user password> BR*Tools Default Profile : <ORACLE_HOME>/dbs/init<DBSID>.sap Example Name : Role : BR*Tools Studio Administrator Password and Confirm Password : <BR user password> Database User Name : SAPSR3 Database User Password : <db user password> BR*Tools Default Profile : /oracle/nwh/102_64/dbs/initnwh.sap 4. Click on Confirm button. 5. Click on Create button. Note: When the create process has finished the complete frame is showed. Show all Database instances Users in BR*Tools Studio Administration Now, you may show all database instance users of your BR*Tools Studio Administration with their roles. 1. Connect to Database instance in BR*Tools Studio like item above. 2. On the Administration tab, choose Users All Users. 3. Click on isolated user for Detailed Information of this one SAP AG 15

16 Alter Database instance User in BR*Tools Studio Administration Now, you may alter the database instance user in your BR*Tools Studio Administration. 1. Connect to Database instance in BR*Tools Studio like item above. 2. On the Administration tab, choose Users All Users. 3. Click on isolated user. 4. On the Administration tab, choose User Administration Alter. 5. Fill the user account information frame with your corrections. 6. Click on Confirm button. 7. Click on Alter button. Note: When the alter process has finished the complete frame is showed. Alter your Database instance User Password in BR*Tools Studio Administration Now, you may alter the database instance user password in your BR*Tools Studio Administration. 1. Connect to Database instance in BR*Tools Studio like item above. 2. On the Administration tab, choose Users My Users. 3. On the Administration tab, choose User Administration Alter. 4. Fill the user account information frame with your corrections. Note: When you did step 2 then you can change your BR*Tools Studio user password. 5. Click on Confirm button. 6. Click on Alter button. Note: When the alter process has finished the complete frame is showed SAP AG 16

17 Remove Database instance User in BR*Tools Studio Administration Now, you may remove the database instance user in your BR*Tools Studio Administration. 1. Connect to Database instance in BR*Tools Studio like item above. 2. On the Administration tab, choose Users All Users. 3. Click on isolated user. 4. On the Administration tab, choose User Administration Drop. 5. Click on Drop button. 6. Confirm drop operation in pop up window. Note: When the drop process has finished the complete frame is showed SAP AG 17

18 BR*Tools Studio Wizard For each Database instance user session, you can use Wizard tab for all Regular Database instance Administration activities. Every activity is performed in BR*Tools and they have logs. If you have an ABAP Stack installed in this SAP System, you can see these logs with DB14 transaction (DBA Operations logs). Furthermore, these logs are available in operating system sessions with SAP System Administrator or Database Administrator. There are default locations and action related extensions that they are explained in SAP Database Guide Oracle that you may read in following link. SAP Netweaver SAP Database Guide: Oracle (BC-DB-ORA-DBA) BR*Tools Studio Wizard has many administration activities related with: Instance management. Space management. Segment management. Backup and Database Copy. Restore and Recovery. Check and Verification. Database Statistics SAP AG 18

19 Related Content BR*Tools Studio 7.10 for Oracle Multi-instance Server Standalone Parte 1: Installation on Unix/Linux SAP. BR*Tools Studio for Oracle DBA. September 2008 Note BR*Tools Studio: Frequently Asked Questions (FAQ). SAP BR*Tools Studio for Oracle: Features SAP BR*Tools Studio for Oracle: The Engine SAP BR*Tools Studio for Oracle: The Wizard Note FAQ: BR*TOOLS and SAPDBA WikiBooks: Internet Technologies/SSH For more information, visit the Landscape Design and Architecture homepage SAP AG 19

20 Disclaimer and Liability Notice This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document SAP AG 20