|
Setting Database Trace optionsC-1261 
Complete this dialog box to control which database operations are traced. Select or clear boxes in two columns.
- Select the Trace box to turn on tracing for the selected operation.
- Select the Generate stack trace box when (in addition to tracing), the system is to present a full Java stack trace.
Label |
Operation |
| Prepared Statements |
Each read, update, or delete operation requested by the PRPC server results in a prepared statement query sent to the PegaRULES database. Causes the DB Trace output to include a line for all three types of prepared statements. |
| Prepared Statement Queries |
Causes the output to include a line for each query (SQL database read) operation. |
| Prepared Statement Updates |
Causes the output to include a line for each update (SQL database insert, update, or delete) operation. |
| Get Database Metadata |
Causes the DB Trace output to include a line for each check of the rule cache; such checks typically occur before read operations the first time since startup that a table is accessed. |
| Read blob |
Causes the DB Trace output to include a line each time the Storage Stream column (pzPVStream) in a row is read. The size of the entry in the column is also reported. |
| Write blob |
Causes the DB Trace output to include a line each time Storage Stream column (pzPVStream) in a row is written. |
| Commit |
Causes the DB Trace output to include a line each time an internal database commit operation completes. (This is not directly related to the PRPC Commit method.) |
| Rollback |
Causes the DB Trace output to include a line when a PRPC Commit operation is in process but a database rollback operation occurred. |
| Assign Connection to Thread |
Causes the DB Trace output to include a line when a database connection in a pool is reassigned to a new requestor thread. |
| Cache Hit (found) |
Causes the DB Trace output to include a line when a rule cache hit occurred and the requested row was found. |
| Cache Hit (not found) |
Causes the DB Trace output to include a line when a rule cache hit occurred and the requested row did not exist. (For rules, the database cache records requests not found as well as successful requests.) |
| Cache Miss |
Causes the DB Trace output to include a line when a rule cache miss occurred. |
| Run List |
Causes the DB Trace output to include a line when a list rule (Rule-Obj-List rule type) was processed by the Obj-List method in an activity. |
| List Result Count |
Causes the DB Trace output to include a line when a list rule completed; indicates the number of rows returned. |
| Activity Start |
Causes the DB Trace output to include a line when an activity execution starts. |
| Activity End |
Causes the DB Trace output to include a line when an activity execution completes. |
Click OK to apply your settings. The system saves this information in the pyDBTraceSettings page within your requestor page.
|
rule cache, Storage Stream |
|
Working with the PegaRULES database |
About the Performance tool