<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SQL TRACE in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/sql-trace/m-p/2548050#M876071</link>
    <description>Manuel&lt;BR /&gt;&lt;BR /&gt;What are the oracle processes that you see, (or saw) at the top of top?  If they were something like&lt;BR /&gt;&lt;BR /&gt;ora_lgwr_SID then it could be that you are generating a lot of redo, and could benefit from multiple redo log writer processes. &lt;BR /&gt;&lt;BR /&gt;ora_dbwr_SID this it could be that you are making a large number of changes on the database, and you could benefit from multiple database writer processes - and maybe a larger SGA.  (Depending on what is going on at the time.)&lt;BR /&gt;&lt;BR /&gt;If the database is at fault, then the real answers will be in the utlbstat reports - although they take alot of deceiphering.&lt;BR /&gt;&lt;BR /&gt;rgds&lt;BR /&gt;&lt;BR /&gt;Steve</description>
    <pubDate>Mon, 09 Jul 2001 06:45:33 GMT</pubDate>
    <dc:creator>Steve Slade</dc:creator>
    <dc:date>2001-07-09T06:45:33Z</dc:date>
    <item>
      <title>SQL TRACE</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sql-trace/m-p/2548047#M876068</link>
      <description>Clay:&lt;BR /&gt;&lt;BR /&gt;- We have reindexed database and review programming. We tkprof all the sqlcode structures to minimize CPU usage.&lt;BR /&gt;&lt;BR /&gt;- We notice certain improve but it wasn't enough for resolve the whole problem.&lt;BR /&gt;&lt;BR /&gt;- When database is performing poorly we can see with top all Oracle processes (ora"sid") on the top of the list. Top load averages grows up very fast but idle time doesn't goes down with same speed. We can have 5 or 6 load points and 80% idle. That?s make as thing to have an I/O problem but we are not sure. We are not either sure if we are suffering any problem with kernel parameters.&lt;BR /&gt;&lt;BR /&gt;- We continue reviewing code to minimize accesing to database but the experience is we are not going to improve enough performance to resolve the problem.&lt;BR /&gt;&lt;BR /&gt;Thanks a lot Clay.</description>
      <pubDate>Tue, 03 Jul 2001 06:18:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sql-trace/m-p/2548047#M876068</guid>
      <dc:creator>Manuel G</dc:creator>
      <dc:date>2001-07-03T06:18:17Z</dc:date>
    </item>
    <item>
      <title>Re: SQL TRACE</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sql-trace/m-p/2548048#M876069</link>
      <description>Hi Manuel,&lt;BR /&gt;&lt;BR /&gt;Please APPEND your comments and responses to your ORIGINAL question to allow to everyone to follow the discussion. Thanks alot. &lt;BR /&gt;Magdi</description>
      <pubDate>Tue, 03 Jul 2001 06:22:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sql-trace/m-p/2548048#M876069</guid>
      <dc:creator>Magdi KAMAL</dc:creator>
      <dc:date>2001-07-03T06:22:35Z</dc:date>
    </item>
    <item>
      <title>Re: SQL TRACE</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sql-trace/m-p/2548049#M876070</link>
      <description>Manuel,&lt;BR /&gt;&lt;BR /&gt;keep in mind to calculate statistics for tables and indexes after your created new indexes.&lt;BR /&gt;&lt;BR /&gt;Check for buffer-qualities using utlbstat.sql and utlestat.sql.&lt;BR /&gt;Check for io and swaps with sar and/or vmstat.&lt;BR /&gt;Check for lock activity in V$LOCK.&lt;BR /&gt;&lt;BR /&gt;Volker</description>
      <pubDate>Tue, 03 Jul 2001 07:09:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sql-trace/m-p/2548049#M876070</guid>
      <dc:creator>Volker Borowski</dc:creator>
      <dc:date>2001-07-03T07:09:06Z</dc:date>
    </item>
    <item>
      <title>Re: SQL TRACE</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sql-trace/m-p/2548050#M876071</link>
      <description>Manuel&lt;BR /&gt;&lt;BR /&gt;What are the oracle processes that you see, (or saw) at the top of top?  If they were something like&lt;BR /&gt;&lt;BR /&gt;ora_lgwr_SID then it could be that you are generating a lot of redo, and could benefit from multiple redo log writer processes. &lt;BR /&gt;&lt;BR /&gt;ora_dbwr_SID this it could be that you are making a large number of changes on the database, and you could benefit from multiple database writer processes - and maybe a larger SGA.  (Depending on what is going on at the time.)&lt;BR /&gt;&lt;BR /&gt;If the database is at fault, then the real answers will be in the utlbstat reports - although they take alot of deceiphering.&lt;BR /&gt;&lt;BR /&gt;rgds&lt;BR /&gt;&lt;BR /&gt;Steve</description>
      <pubDate>Mon, 09 Jul 2001 06:45:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sql-trace/m-p/2548050#M876071</guid>
      <dc:creator>Steve Slade</dc:creator>
      <dc:date>2001-07-09T06:45:33Z</dc:date>
    </item>
  </channel>
</rss>

