Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Add to the list of information needed the following:</p> <p>Are you using archive logs? How many redo log groups do you have? How many redo logs are in each group? How big are the redo logs?</p> <p>How are you restarting Oracle? Are you just doing a shutdown immediate followed by a startup? Are you rebooting the server?</p> <p>If your log files are too small you might be getting into a state where you're waiting for the redo logs to be written to the archive logs before being able to continue, you can help remedy this by increasing the size of the redo logs.</p> <p>Shutting down and restarting oracle would result in the redo logs all being written to the archive logs and being fresh and ready to go after you start back up. Then as they fill with redo information you hit a bottleneck when it comes time to archive them.</p> <p>An AWR report would really be the most useful thing if you're running Oracle 10g. If you're running 9i then statspack equvalent.</p> <p><strong>Running a AWR Report</strong></p> <p>Login to sqlplus </p> <pre><code>sqlplus &lt;sys or system user&gt;/&lt;password&gt;@&lt;SID&gt; </code></pre> <p>Create a 'before' statistics snapshot </p> <pre><code>SQL&gt; execute dbms_workload_repository.create_snapshot </code></pre> <p>Run your specific performance/load tests</p> <p>Create an 'after' statistics snapshot </p> <pre><code>SQL&gt; execute dbms_workload_repository.create_snapshot </code></pre> <p>Create a workload repository report</p> <pre><code>SQL&gt; start awrrpt </code></pre> <p>Using the AWR report you should be able to determine where your bottleneck is.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload