The profiling session is saved automatically or when you try to close it according to the choices made in the Profile Configuration dialog. For information on configuring profiling sessions, see Building profiling configurations. Profiling sessions can be saved in the current workspace in an archive file with a .oar suffix or for Oracle users, into a Profiling Repository.
The .oar archive file is named with a default file name of:
- The name of the data source if the session was not initiated from a named launch configuration
- The name of the launch configuration if the session was initiated from a named launch configuration.
If you are using an Oracle data source and have configured DB Optimizer to automatically save profiling sessions in a Profiling Repository within an Oracle data source, then the profiling session is saved in the Profiling Repository under the name of the data source. Each profiling session for that data source is named using a date and time stamp. As you can see below, the duration of the profiling session is also saved with the session data.
For information on working with the Profiling Repository, see Work with the Profiling Repository. The time period of the saved session is the amount of data on the chart. The maximum amount of data on the chart is determined when profiling is started (1-hour default). You can specify the amount of time to profile the data source in the Profile Configurations dialog and you can also stop the profiling at any time.
Saving the profile lets you open the archive at a later time for subsequent analysis by yourself or by other DB Optimizer users. Use standard DB Optimizer file techniques to save, open, or close SQL Profiling archives. If you open a profiling archive on a machine on which the associated data source is not registered, a Data source not available warning appears in the profiling editor header. Use the associated control to specify a data source already defined on the machine or to register a new data source.
Work with the Profiling Repository
Saving wait-time statistics to the Profiling Repository is not supported in Developer Editions of DB Optimizer.
The Profiling Repository is only available when profile session data is saved to an Oracle data source. You can specify a profiling repository on any supported version of Oracle data source. For information configuring profiling repositories, see Specify Profile Repositories Preferences. You can specify which profiling to save a session to using the Profile Configurations dialog. For more information, see Building profiling configurations. When the system is configured to automatically save profiling information to a Profiling Repository, DB Optimizer can profile 24 hours a day 7 days a week, thus providing much more statistical data for analysis. Also, since a Profiling Repository resides on a data source and not on the local disk, other DB Optimizer users can also view and analyze the profiles.
To start saving profile sessions to the Profiling Repository
- From the Data Source Explorer right-click the data source you want to profile for and select Profile As from the menu, then choose Profile Configurations.
The Profile Configurations dialog appears.
- In the Name field of the Profile tab, enter a name for the profile session for this data source.
- In the Profiling Target Data source field, select a data source from the list.
- In the Profiling Repository area of the Profile tab, click Save to data source and then from the list of registered profiling repositories, choose the Oracle data source to which you want to store the profiling session information.
- Click Apply and then click Profile to start a profiling session immediately.
Any new profiling session that you start continue until you manually stop it. The profile session can be for as long as you like, days or weeks even. When the profiling session is stopped, a profile file is stored in the profile group for this data source. The name of the profile file is the date and time when the profile finished.
To delete profile sessions saved in the Profiling Repository
In the Data Source Explorer, locate and then click the Profiling Repository.
You access the profile repositories either in the Managed Data Sources node or in the Profiling Repositories.
If the data source is not already connected, DB Optimizer connects to the Profiling Repository data source.To delete all sessions in the Profiling Repository, right-click Profiling Repository and then select Delete All.
To delete a specific profiling session, expand the Profiling Repository and the data source containing the profiling session, and right-click the name of the profiling session, and then select Delete.
The profiling session data is deleted, however, some information about the data source is retained in order to expedite future profiling on this data source. If you are certain you will not want to retain this information, right-click the Profiling Repository and then select Clean.You can also delete the profiling sessions saved to a repository by unregistering the repository. For more information see Specify Profile Repositories Preferences.