Page History

Profiling enables you to store parameters related to specific profiling sessions, in a profile configuration for stored routines. Multiple configurations can be created for each data source in your enterprise and saved with unique names that identify them in the application.

...

1. Right-click the data source you want to build a configuration for and select Profile As from the menu, then choose Profile Configurations.
   The Profile Configurations dialog appears. Image Removed
2. Select the name of the data source and modify the parameters on the Profile tab, as needed. 
3. In the Name field, provide a name for the launch configuration. You should select a name that will make the launch configuration unique and easily identified once it is saved in the application. 

4. In the Profiling Target area, click Real Application Cluster (RAC) mode if the target database is an Oracle RAC. This enables you to profile the entire cluster in one profiling session. (In general, profiling a RAC entails querying the GV$ views.) 

   Info
   When profiling a RAC, you can also filter the profiling details to show only the details for a selected instance. At the top of the Profiling view, click the Instances list and choose the instance you want to examine.

   In the Profiling Repository area, choose to save the profile session to disk or if you are profiling an Oracle data source then you can choose to save the profile session to a data source registered as a Profiling Repository.
   If you choose to save the session to disk, in the Time interval length area specify the length of the profiling session. When you try to close the Profile Session, you will be prompted to save the file and can then name the file as desired. A .oar file saved to
5. disk opens very quickly from File > Open dialog and has a limit of just under 1000 hours of profiling data. Profiling to a data source directly allows the system to capture more data for a longer period of time, until you decide to stop the profiling session. The profiling session is automatically saved to the Profiling Repository where other SQL Query Tuner users can also view the session for their own analysis. Click Apply. The launch configuration is stored in the application. 
6. Once a launch configuration is defined, you can execute it in profiling. For more information, see Running a Profiling Session. 

...

The

...

The following describes fields and options of the Profile tab that require further explanation.

• Name indicates the name of the profile configuration.
• Data source indicates the name of the data source to which the profile applies.
• Save to disk/Save to data source gives you the option to save your profiling session to a .oar file which you can access from within SQL Query Tuner or you can save the profiling session to a data source of your choice if you are using an Oracle data source. SQL Query Tuner will create a Profiling Repository, similar to the following on the selected Oracle data source. The structure of the Profiling Repository is created from the name of the data source and the date and time of each specific profiling session. 
  Image Removed

Saving your profiling sessions to a live data source enables you to better organize your profile session data for later review.

...