Skip to Content

This is the final part in a 3-part series. If you missed part 2, see SAP BR*Tools Studio for Oracle: The Engine.

After having looked at BR*Tools Studio Administration in part 2 of this blog, in the third and final part we’ll be looking at the connection between BR*Tools Studio and BR*Tools. The connection uses BR*Tools Wizard, which is the second large part of BR*Tools Studio beside BR*Tools Studio Administration:

Part 3: The Wizard


Depending on the user role, the BR*Tools Wizard shows up to five main groups for each of the administration areas:

  • Instance

    This group contains all functions for instance administration. Here you can find, among other things, the functions to start and stop the database as well as a detailed description of the instance status to complement the visual status display.

  • Database

    This group contains a virtual representation of the logical and physical level of the database. Here you can find views of the database users, tablespaces, tables, indexes and — on the operating system level — the individual files comprising the database. You can execute actions relevant to the objects displayed, such as extending a tablespace.

  • Maintenance

    This group contains further functions for database maintenance. From here you can export, import, or reorganize parts of the database, collect or update database statistics, and much more.

  • Availability

    This group contains all functions to ensure the database remains available and operational, even after a failure. It includes functions such as backup, restore, and recovery.

  • Advanced

    This group enables you to execute BR*Tools functions in the same style as from the well-known BR*Tools command line. You can also set up your own advanced functions beyond the scope of the predefined BR*Tools Studio functionality. You can then store and schedule these special jobs as favorite tasks.


Right from the beginning with BR*Tools Studio we wanted to ensure a simple and intuitive user interface with a uniform path from selection of the required object or operation to the final job handover to the server. To illustrate this, let’s take a look at an example of how you can start up an operation instance:

Selecting the Operation

After logging on as BR*Tools Studio administrator or database administrator, you can find the operation Startup under the instance administration, which you reach from the overview screen of the BR*Tools Wizard by selecting Instance. Since the startup operation is one of the central functions of instance administration, it also appears on the overview page as a quick link.

Clearly visible is the completely red instance status indicator in the BR*Tools Studio console on the left side of the window, indicating that the database is currently stopped.


Figure 1: Selecting the Operation

Setting the Parameters

After selecting Startup, you see the first screen for the operation. A road map shows the individual steps of job creation. The first screen prompts you to make the required settings for the operation. In this example we assume you accept the default settings and go to the next screen by choosing Confirm.


Figure 2: Setting the Parameters

Confirming the Job

In the second step BR*Tools Studio asks you to confirm again the selected settings. You can now also choose whether and how to execute the job:

To be able to execute instance startup easily in the future, you can use the tab Save to make it a favorite task with the preselected parameters. The next tab, Schedule, lets you schedule the operation for single or periodic execution. In this example we assume you want to execute the job immediately so you continue as normal with Start Up. This sends the job to the server.



Figure 3: Confirming the Job

Executing the Operation

The third step shows that the job was successfully created and sent to BR*Tools Studio Server. Since you set the job for immediate execution, the server starts it immediately. The display Jobs in Progress on the left displays information on the progress of the job. At the same time, the instance status display reacts to the database startup: the traffic light changes from red through amber to green.


Figure 4: Executing the Operation

The job was successfully executed and the database is now up and running. If required you can choose the job administration on the right side to reach the detail display of the completed job in BR*Tools Administration, from where you can see the BR*Tools job log to check for errors.

Whenever you execute a job in BR*Tools Studio it follows this basic schema, although there are obviously differences depending on which job you choose.

We hope you’ve enjoyed these blogs and found them informative. Let’s now look forward to the upcoming release of BR*Tools Studio – keep tuned to SAP on Oracle in SDN for up-to-date information!

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member
    Hi ,it wanted to know when this available one and ?

    as they are the pre-requisite to install Brtools Studio?

    As pilot can be participated in the test?

    best regards

    1. Former Member Post author
      Dear Hilaire,

      we plan to keep the pilot phase as short as possible, yet the actual GA will strongly depend on how smoothly the pilot version will go live. While the pilot is running, we will finalize the full version of BR*Tools Studio. All in all, we might expect to see the GA release around turn of the year 2007/2008.

      Best Regards,


Leave a Reply