Page History

...

...

For more information, see Oracle Findingsfindings.

Anchor
Aboutdrillingdownincontext Aboutdrillingdownincontext

About drilling down in context

The term '"in-context' " means that you can display additional information on a selected item by drilling down to another tab or view. The filter settings you defined (for example, the selected time frame you chose) and the entity you selected are carried over to the other view or tab, to allow you to continue analyzing your subject from a different perspective. This concept takes on slightly different meanings depending upon where you are attempting to drill down in context from.

...

• General settings. Includes the General, SQL, Display, Tree view, and What-If/Recommend tabs.
• Time Frame settings.
• Findings settings. Includes the Dashboard, Activity, Objects, and SQL tabs.

Anchor
Aboutconfiguringgeneralsettings Aboutconfiguringgeneralsettings

About configuring general settings

On the General tab of the General Settings dialog box, you can adjust the following:

• Number of items that will be displayed for each association. From the list, select the maximum number of items that will be displayed in a table. The default is 50 items. You can control the number of items returned for a specific association by using the More... option  option in the Association controls. This way, you can display up to 500 items.
• Maximum number of characters to display in a text ToolTip. When you move your cursor over text columns in a table listing Statements or PL/SQLs, a ToolTip appears, displaying more text than can normally fit into a table cell. This field controls the maximum number of characters that can be displayed. The default is 500 characters.
• How often the information in the Current tab is refreshed. If you select the Auto-refresh Current tab every check box, the Current tab automatically refreshes at the specified interval. By default, the tab is not refreshed automatically. If you select this option, the default refresh interval is every five minutes.
• Display concurrent managers history for the last x days.
• Display concurrent managers request history for the last x hours.

...

• When Precise for Oracle carries out an explain plan operation, it needs to connect to the database. By default, it uses the Oracle account specified during the installation. This option lets you override the database user and password that will be used.
• Precise for Oracle's own parsing functions can be disabled at the expense of some of the formatting features of the explain plan. This option is useful when Precise for Oracle cannot parse a statement. See About Precise for Oracle tabs.
• You can fine-tune the way that Precise for Oracle generates alternatives to SQL in a number of ways:
  • You can control the maximum number of alternative SQL statements.
  • You can control the percentage of the items that are highlighted in the Oracle explain tree based on “In In Oracle Time”Time.
  • You can have Precise for Oracle ignore alternatives that generate the same execution plan.
  • When Precise for Oracle generates alternatives (referred to as Related SQL), any views are expanded to show the full view text, rather than just the name.
  • If a Precise for Oracle view is expanded, Precise for Oracle may consider rewriting the text of the view itself, not just the statement that uses the view, when it generates alternatives.
  • You can have Precise for Oracle use different Oracle Optimizer modes.

...

1. Click the calendar icon. In the dialog box that is displayed perform one of the following:
   1. To define a time frame independent from the current time, select the ‘Time Frame’ option and Time Frame, and then select the Start and End dates and times.
   2. To define a time frame up to the current time, select the ‘Last’ option Last, and then enter the desired time frame.
   3. To use one of the three previously used time frames, select the ‘Recently used’ option and from the drop- down menu Recently used, and then select the desired time frame.
   4. To use a previously saved time frame, select Use a previously saved time frame and from the drop-down menu , and then select the desired time frame.
2. To save your settings for future access, select Save these definitions for future use as: and  and enter a name in the corresponding field.
3. Click OK.

...

To edit the properties of a statement

1. Click the Actions icon>Edit icon > Edit Properties.
2. In the Edit Statement Properties dialog box, choose the relevant properties for the statement from the drop-down lists and enter a statement name.
   The following properties are available:
   • Instance. Name of the instance that the statement belongs to. The instance cannot be changed.
   • Parsing User. Choose an Oracle user name that will parse the statement from the drop-down list.
   • Cabinet. Choose a cabinet to save the statement in, from the drop-down list or type in a name.
   • Folder. Choose a folder to save the statement in, from the drop-down list or type in a name.
   • Statement. Type a user-defined name for the statement.
   • Comment. Type an optional tuning comment that is to be associated with the statement.
   The maximum number of items displayed in the Cabinet, Folder, and Statement lists is limited. You may also type the names.
3. Click OK.

...

You can send an email message to one or more recipients from the Precise toolbar. The default subject for the message will be “Link is, "Link to a Precise application”application."

The email will include a link to the Precise product in the current context (time frame and selected entries). To send an email message

...

• Relative Time Frame. Saving relative time frame instead of static date. For example, saving the last 7 seven days will always display the last 7 seven days, depending on the day entered.
• One click to specific location. Once you open Precise by launching a saved Favorite item, you will not have to enter a login credential nor click the login button.
• IE Favorites support. Adding a new Favorite item in Precise will also add it to the IE Favorites menu.
• Auto Complete. The Favorites dialog includes a new combo box which supports AutoComplete.
• Auto Naming. The Favorites dialog generates item names based on the current location.

...

In Oracle State	Icon	In Oracle Sub-State	Description	Typical Oracle Events
Using CPU		Using CPU	The session is using CPU executing SQL.	N/A
I/O Wait		Direct I/O Wait	The session is waiting on direct I/O.	direct path read; direct path write
I/O Wait		Scattered I/O Wait	The session is waiting on scattered I/O.	db file scattered read
I/O Wait		Sequential I/O Wait	the The session is waiting on sequential I/O.	db file sequential read; control file sequential read
I/O Wait		Other I/O Wait	the The session is waiting on another type of I/O.	db file parallel write; log file parallel write; control file parallel write; asynch disk I/O
I/O Wait			Info The I/O sub-states Direct I/O Wait, Scattered I/O Wait, Sequential I/O Wait, and OtherIOther I/O Wait only apply to Oracle files, objects, and storage entities. For other entities, the sub-state is simply shown as I/O Wait.
Application Lock Wait		Row Lock Wait	the The session is waiting on row locks. Enq: TX - row lock contention (Oracle 10g)
Application Lock Wait		Table Lock Wait	The session is waiting on table locks.	Enq: TM - contention (Oracle 10g)
Internal Lock Wait		Other Lock Wait	The session is waiting on other Oracle locks, such as streams, latches, or internal locks.	STREAMS events; enqueue; other enq: events; latch activity; latch free; latch: events
Application Lock Wait			Info Enqueue may appear in Row Lock Wait and Table Lock Wait, depending on the values of the P1, P2, and P3 parameters. The Collector captures these parameters and assigns the wait state accordingly. This can be seen in the Current and Activity tabs. However, the Collect Instance Statistics PMDB process does not capture the parameters so that in the Statistics tab, the wait is always shown as Other Lock Wait.
Operating System Waits		CPU Wait	The session is in the operating system queue waiting for CPU.	N/A
Operating System Waits		Memory Wait	The session is waiting on a memory operation, such as page-in or page-out. This sub-state may also include memory-mapped I/O.	N/A
Operating System Waits		Other Host Wait	The session is waiting on another type of OS operation, such as sorting.	N/A
RAC/OPS/ Other Waits		RAC/OPS Wait	The session is waiting on RAC or OPS synchronization.	DFS events; DLM events; gc events; gcs events; ges events; global events
RAC/OPS/ Other Waits		Other Wait	The session is waiting on another, less common lock event.	N/A
Commit & Checkpoint Waits		Rollback Segment Wait	The session is waiting on a rollback segment operation.	alter rbs offline; undo segment events
Commit & Checkpoint Waits		Redo Log Buffer Wait	The session is waiting on a redo log buffer operation.	log buffer space; log file syn
Commit & Checkpoint Waits		Log Switch and Clear Wait	The session is waiting for a log switch and clear operation to occur.	checkpoint events; log file switch events
Oracle Server Wait		Parallel Query Server Wait	The session is waiting for a parallel query server to become available.	PX create server; PX server shutdown; parallel query; create server; parallel query; dequeue wait
Oracle Server Wait		Parallel Query Sync. Wait	The session is waiting for a parallel query server to get synchronized with another parallel query server.	Other PX events; other parallel query events
Oracle Server Wait		Resource Manager Wait	The session is waiting for a resource to become available (only if the database resource manager is enabled).	resmgr events
Oracle Server Wait		Multi-Threaded Server Wait	The session is waiting for a multi-threaded server to become available.	alter system set dispatcher; alter system set mts_dispatcher
Oracle Server Wait		Background Process Wait	The session is waiting for an Oracle background process, such as DBWR or LGWR.	LGWR events
Client Request Wait		Request wait	Request wait is generally considered as an idle event as the Oracle server process is waiting for the client process.	Client messages
Communication Wait		Oracle/Oracle Communication Wait	The session is waiting for another Oracle instance, usually as a result of a DBLINK event or a standby database.	SQL*Net break/reset to DBLINK; SQL*Net message from DBLINK; SQL*Net message to DBLINK; SQL*Net more data from DBLINK; SQL*Net more data to DBLINK
Communication Wait		Oracle/Client Communication Wait	The session is waiting for data sent to the client, usually as a result of a selected statement, or for data sent from a client, usually as a result of bind variables.	SQL*Net break/reset to client; SQL*Net message to client; SQL*Net more data from client; SQL*Net more data to client
Internal Lock Wait		Shared Pool Wait	The session is waiting for a shared pool operation.	library cache load lock; library cache lock; library cache pin
Internal Lock Wait		Buffer Wait	The session is waiting for a buffer cache operation.	buffer busy; buffer busy wait; buffer latch

...

The other In Oracle wait states, such as Using CPU, do not apply to an object. See Wait States - In Oracle.

Anchor
StatementidvsOraclehashvalue StatementidvsOraclehashvalue

Statement identifier vs. Oracle hash value

SQL statements in Precise for Oracle are assigned a numeric identifier (a 20-digit number that is divided into 4 four sections, with dot separators) or a user-defined name. The numeric identifier is similar to, but not the same as, the hash value that Oracle assigns to a SQL statement. When Precise for Oracle calculates the numeric identifier, it ignores white space and case, unlike Oracle. It also takes into account whether Collapse Statements is switched on, in which case string literals are replaced with place holders or pseudo-bind variables.

Anchor
Executionsvsopensandfetches Executionsvsopensandfetches

Executions vs. opens and fetches

Precise for Oracle employs the following methods to determine how many times a statement has been executed.

...

The following is an explanation based on an example statement using a parallel query.:

When a session runs a statement for a table with parallel degree of n (4 degrees for example), the Oracle engine creates n new sessions to serve it (these sessions are called: "Parallel Server Agents"). Each of the parallel server agents runs as an individual entity and analyzes part of the requested data, while the original session (the one that you logged in with) is called the coordinator session. The last goal is to receive all the information from the parallel server agents and summarize (sort/filter/calculate/join) it. Usually the coordinator session will not perform an "In Oracle" operation. In fact it is waiting "All the time" when the parallel server agents are working. These parallel server agents can perform I/O / Locks / RAC operations - like any other regular session. These sessions (4 in our example) have the same session identifiers as the coordinator session. Therefore in the collector's aggregation phase all the sessions are aggregate into one row. For example, if a specific statement runs for 1 hour (wall clock time) you can see in the Activity tab that the statement consumed 4 hours "In Oracle" time. You can also find the parallel degree of the statement within the Activity tab.

Anchor
OraclestatisticsusagewithinPreciseforOracle OraclestatisticsusagewithinPreciseforOracle

Oracle statistics usage within Precise for Oracle

Precise for Oracle captures standard Oracle statistics that you can see in the V$SESSTAT table. However, the Collector reads the values in a low-overhead fashion directly from the SGA memory that the V$ tables map onto. Where necessary, the statistics are divided between the sessions executing each SQL statement and then aggregated to the user, program, and instance levels. You will see these statistics in the Current and Activity tabs, displayed as name-value pairs. Each statistic represents a different counter and has its own units. See Oracle’s documentation for more information on these statistics.

...

The following table shows how Precise Interpoint maps the entities in each ERP application. You can find information about how to install Oracle Applications, SAP, PeopleSoft, and Siebel Tier Collectors in the Precise Installation Guideand Administration.

Table 6 Mapping of Precise Interpoint entities per technology

Anchor
PreciseforStorageOracleversionhowresourceconsumptionofstoragedevicesisexamined PreciseforStorageOracleversionhowresourceconsumptionofstoragedevicesisexamined

Precise for Storage, Oracle version - how resource consumption of storage devices is examined

Precise for Storage, Oracle version supports EMC Symmetrix and Clariion, and Hitachi HDS. It offers a unique method to identify I/O problems in your attached storage and reports I/O wait time instead of just I/O counters. This lets you easily identify the resource that is actually being waited for and tune it instead of guessing by rules of thumb. Furthermore, you can associate the storage device with the applications and statements that are waiting on I/O.

...

1. Type the address of the StartPoint user interface into the Address bar of your browser and click Enter. The Precise login page opens. The login page provides secure access to Precise and to your specific product.
2. Specify your authorized role name and password. By default, both role name and password are admin. For more information about role names, see the Precise Administration Guidesee Installation and Administration.
3. Click Login. The StartPoint page opens. This is the Precise home page.
4. On the Product Selection bar, from the drop-down list, select the product you want to launch.