Statpack report

Hi,
i have applicated the spreport.sql for having a report on my server in slow state,
in the "Top 5 Timed Events" the event :
Avg
Total Wait wait Waits
Event Waits Timeouts Time (s) (ms) /txn
log buffer space 1,195 140 436 365 -0.0
it mean that:
1- The buffer for logfiles is too small
2- Or the acces on disk is too long for the location of logfiles .
For 1-
The value for log_buffer is 524288 is it too small, if i increase it, are there any impacts on other parameters.
For 2-
We are on RAID 5 and we have not other possibilities.
Regards.

you are right Tom. It was an error in the last report.
That 's the new one:
Snap Id Snap Time Sessions Curs/Sess Comment
Begin Snap: 4 21-Apr-06 08:00:17 38 3.9
End Snap: 5 21-Apr-06 08:40:13 95 3.7
Elapsed: 39.93 (mins)
Cache Sizes (end)
~~~~~~~~~~~~~~~~~
Buffer Cache: 1,920M Std Block Size: 8K
Shared Pool Size: 336M Log Buffer: 512K
Load Profile
~~~~~~~~~~~~ Per Second Per Transaction
Redo size: 14,185.35 5,237.00
Logical reads: 2,769.19 1,022.34
Block changes: 79.48 29.34
Physical reads: 73.84 27.26
Physical writes: 9.06 3.35
User calls: 33.02 12.19
Parses: 48.71 17.98
Hard parses: 6.12 2.26
Sorts: 5.94 2.19
Logons: 0.07 0.03
Executes: 49.80 18.39
Transactions: 2.71
% Blocks changed per Read: 2.87 Recursive Call %: 89.94
Rollback per transaction %: 3.41 Rows per Sort: 923.06
Instance Efficiency Percentages (Target 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Buffer Nowait %: 99.98 Redo NoWait %: 100.00
Buffer Hit %: 97.42 In-memory Sort %: 100.00
Library Hit %: 95.58 Soft Parse %: 87.44
Execute to Parse %: 2.19 Latch Hit %: 99.77
Parse CPU to Parse Elapsd %: 4.91 % Non-Parse CPU: 55.12
Shared Pool Statistics Begin End
Memory Usage %: 79.12 95.73
% SQL with executions>1: 7.38 5.37
% Memory for SQL w/exec>1: 9.70 8.16
Top 5 Timed Events
~~~~~~~~~~~~~~~~~~ % Total
Event Waits Time (s) Ela Time
latch free 25,565 1,743 54.01
db file sequential read 48,535 560 17.35
db file scattered read 10,692 528 16.38
CPU time 187 5.81
buffer busy waits 1,294 69 2.13
Thanks for any suggestion.

Similar Messages

  • How to understand STATPACKS report ?

    Hi,
    How to understand STATPACKS report ? Some documents or link ?
    Thank you.

    http://www.akadia.com/services/ora_statspack_survival_guide.html
    http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96533/statspac.htm
    http://jonathanlewis.wordpress.com/2008/02/18/analysing-statspack/
    and many..many more....!!!!
    Grrod reading...
    Sim

  • No statpack report from 10g onwards required

    I had a query that statpack report may not be required in 10g onwards as AWR (Automatic workload repository) has been introduced since 10g.
    I hope, my question is clear that is it possible to allocate a certain amount for memory for the database.
    Please revert with the reply to my query.
    Regards

    Sorry about the post, please do not consider that sentence as my query was limited to only whether statpack report may not be required in 10g onwards as AWR has been introduced since 10g.

  • Statpack analyzing of 9i database.

    hi Expertise
    Please help me for sorting the statpack report of my production DB in 9i. Also advise some recommendation after analyzing my statpack view.
    Elapsed:     3.75 (min)     225 (sec)
    DB Time:     7.84 (min)     470.65 (sec)
    Cache:     10,016 MB     
    Block Size:     8,192 bytes     
    Transactions:     2.01 per second     
    Performance Summary
    Physical Reads:     15,666/sec          MB per second:     122.39 MB/sec     
    Physical Writes:     22/sec          MB per second:     0.17 MB/sec     
    Single-block Reads:     1,412.69/sec          Avg wait:     0.03 ms     
    Multi-block Reads:     1,916.26/sec          Avg wait:     0.05 ms     
    Tablespace Reads:     3,346/sec          Writes:     22/sec     
    Top 5 Events
    Event     Percentage of Total Timed Events
    CPU time     79.89%
    PX Deq: Execute Reply     6.38%
    db file scattered read     4.32%
    SQL*Net more data from dblink     4.29%
    db file sequential read     2.00%
    Tablespace I/O Stats
    Tablespace     Read/s     Av Rd(ms)     Blks/Rd     Writes/s     Read%     % Total IO
    TS_CCPS     3,117      0     2.5      0      100%     92.5%
    TS_OTHERS     204      0.2     26.2      1      99%     6.09%
    TS_AC_POSTED03     19      1.9     127      2      89%     0.63%
    Load Profile
    Logical reads:     42,976/s          Parses:     39.41/s     
    Physical reads:     15,666/s          Hard parses:     5.43/s     
    Physical writes:     22/s          Transactions:     2.01/s     
    Rollback per transaction:     0%          Buffer Nowait:     100%     
    4 Recommendations:
    Your database has relatively high logical I/O at 42,976 reads per second. Logical Reads includes data block reads from both memory and disk. High LIO is sometimes associated with high CPU activity. CPU bottlenecks occur when the CPU run queue exceeds the number of CPUs on the database server, and this can be seen by looking at the "r" column in the vmstat UNIX/Linux utility or within the Windows performance manager. Consider tuning your application to reduce unnecessary data buffer touches (SQL Tuning or PL/SQL bulking), using faster CPUs or adding more CPUs to your system.
    You are performing more than 15,666 disk reads per second. High disk latency can be caused by too-few physical disk spindles. Compare your read times across multiple datafiles to see which datafiles are slower than others. Disk read times may be improved if contention is reduced on the datafile, even though read times may be high due to the file residing on a slow disk. You should identify whether the SQL accessing the file can be tuned, as well as the underlying characteristics of the hardware devices.
    Check your average disk read speed later in this report and ensure that it is under 7ms. Assuming that the SQL is optimized, the only remaining solutions are the addition of RAM for the data buffers or a switch to solid state disks. Give careful consideration these tablespaces with high read I/O: TS_CCPS, TS_OTHERS, TS_AC_POSTED03, TS_RATING, TS_GP.
    You have more than 1,222 unique SQL statements entering your shared pool, with the resulting overhead of continuous RAM allocation and freeing within the shared pool. A hard parse is expensive because each incoming SQL statement must be re-loaded into the shared pool; with the associated overhead involved in shared pool RAM allocation and memory management. Once loaded, the SQL must then be completely re-checked for syntax & semantics and an executable generated. Excessive hard parsing can occur when your shared_pool_size is too small (and reentrant SQL is paged out) or when you have non-reusable SQL statements without host variables. See the cursor_sharing parameter for an easy way to make SQL reentrant and remember that you should always use host variables in you SQL so that they can be reentrant.
    Instance Efficiency
    Buffer Hit:     69.13%          In-memory Sort:     100%     
    Library Hit:     96.4%          Latch Hit:     99.99%     
    Memory Usage:     95.04%          Memory for SQL:     64.19%     
    2 Recommendations:
    Your Buffer Hit ratio is 69.13%. The buffer hit ratio measures the probability that a data block will be in the buffer cache upon a re-read of the data block. If your database has a large number of frequently referenced table rows (a large working set), then investigate increasing your db_cache_size. For specific recommendations, see the output from the data buffer cache advisory utility (using the v$db_cache_advice utility). Also, a low buffer hit ratio is normal for applications that do not frequently re-read the same data blocks. Moving to SSD will alleviate the need for a large data buffer cache.
    Your shared pool maybe filled with non-reusable SQL with 95.04% memory usage. The Oracle shared poolcontains Oracle´s library cache, which is responsible for collecting, parsing, interpreting, and executing all of the SQL statements that go against the Oracle database. You can check the dba_hist_librarycache table in Oracle10g to see your historical library cache RAM usage.
    SQL Statistics
    Click here to see all SQL data
    Wait Events
    Event     Waits     Wait Time (s)     Avg Wait (ms)     Waits/txn
    PX Deq: Execute Reply     137     30     219     0.3
    db file scattered read     431,159     20     0     951.8
    SQL*Net more data from dblin     51,140     20     0     112.9
    db file sequential read     317,856     9     0     701.7
    io done     6,842     5     1     15.1
    db file parallel read     21     1     52     0.0
    local write wait     250     1     4     0.6
    db file parallel write     825     1     1     1.8
    SQL*Net message from dblink     208     1     3     0.5
    log file parallel write     2,854     1     0     6.3
    0 Recommendations:
    Instance Activity Stats
    Statistic     Total     per Second     per Trans
    SQL*Net roundtrips to/from client     87,889     390.6     194.0
    consistent gets     10,141,287     45,072.4     22,387.0
    consistent gets - examination     884,579     3,931.5     1,952.7
    db block changes     100,342     446.0     221.5
    execute count     18,913     84.1     41.8
    parse count (hard)     1,222     5.4     2.7
    parse count (total)     8,868     39.4     19.6
    physical reads     3,525,003     15,666.7     7,781.5
    physical reads direct     539,879     2,399.5     1,191.8
    physical writes     5,132     22.8     11.3
    physical writes direct     29     0.1     0.1
    redo writes     1,598     7.1     3.5
    session cursor cache hits     4,378     19.5     9.7
    sorts (disk)     0     0.0     0.0
    sorts (memory)     4,988     22.2     11.0
    table fetch continued row     310     1.4     0.7
    table scans (long tables)     82     0.4     0.2
    table scans (short tables)     18,369     81.6     40.6
    workarea executions - onepass     0     0.0     0.0
    5 Recommendations:
    You have high network activity with 390.6 SQL*Net roundtrips to/from client per second, which is a high amount of traffic. Review your application to reduce the number of calls to Oracle by encapsulating data requests into larger pieces (i.e. make a single SQL request to populate all online screen items). In addition, check your application to see if it might benefit from bulk collection by using PL/SQL "forall" or "bulk collect" operators.
    You have 3,931.5 consistent gets examination per second. "Consistent gets - examination" is different than regular consistent gets. It is used to read undo blocks for consistent read purposes, but also for the first part of an index read and hash cluster I/O. To reduce logical I/O, you may consider moving your indexes to a large blocksize tablespace. Because index splitting and spawning are controlled at the block level, a larger blocksize will result in a flatter index tree structure.
    You have high update activity with 446.0 db block changes per second. The DB block changes are a rough indication of total database work. This statistic indicates (on a per-transaction level) the rate at which buffers are being dirtied and you may want to optimize your database writer (DBWR) process. You can determine which sessions and SQL statements have the highest db block changes by querying the v$session and v$sessatst views.
    You have high disk reads with 15,666.7 per second. Reduce disk reads by increasing your data buffer size or speed up your disk read speed by moving to SSD storage. You can monitor your physical disk reads by hour of the day using AWR to see when the database has the highest disk activity.
    You have high small table full-table scans, at 81.6 per second. Verify that your KEEP pool is sized properly to cache frequently referenced tables and indexes. Moving frequently-referenced tables and indexes to SSD or theWriteAccelerator will significantly increase the speed of small-table full-table scans.
    Buffer Pool Advisory
    Current:     3,599,469,418 disk reads     
    Optimized:     1,207,668,233 disk reads     
    Improvement:     66.45% fewer     
    The Oracle buffer cache advisory utility indicates 3,599,469,418 disk reads during the sample interval. Oracle estimates that doubling the data buffer size (by increasing db_cache_size) will reduce disk reads to 1,207,668,233, a 66.45% decrease.
    Init.ora Parameters     
    Parameter     Value     
    cursor_sharing     similar     
    db_block_size     8,192     
    db_cache_size     8GB     
    db_file_multiblock_read_count     32     
    db_keep_cache_size     1GB     
    hash_join_enabled     true     
    log_archive_start     true     
    optimizer_index_caching     90     
    optimizer_index_cost_adj     25     
    parallel_automatic_tuning     false     
    pga_aggregate_target     2GB     
    query_rewrite_enabled     true     
    session_cached_cursors     300     
    shared_pool_size     2.5GB     
    optimizercost_model     choose     
    1 Recommendations:
    You are not using large blocksizes for your index tablespaces. Oracle research proves that indexes will build flatter tree structures in larger blocksizes.

    Systemwide Tuning using STATSPACK Reports [ID 228913.1] and http://jonathanlewis.wordpress.com/statspack-examples/ should be useful.

  • Statspack HTML reports to Analyze

    Hi Experts,
    I have always used ADDM to interpret the AWR reports.
    Now, we have an environment which is not licensed to use diagnostic pack; so we are collecting statspack reports level 7 periodically;
    Statspack html reports look like AWR reports, but, I sill missed the useful information that ADDM report deliver;
    I would like to know if there is any useful tool FREE that could help me analyze the HTML statpacks reports;
    I found a few but only accept Statspack text format.
    I don't have access to the database server and I only provided the HTML statpacks reports to interpret,
    Thank you

    Statspack in HTML format , sounds interesting , can you tell how to get them.

  • Repository reports differences

    Hi,
    Does anyone have a complete list of the changes that where made to the naming of Repository Reports between 1.3.2 and 6.0. I have to deliver CDM reports given in the old name from a Designer 6.0 repository and I can't find the right reports.
    Thanks for the help.
    RATL..

    hi,
    if your where to run a statpack report and an awr report from sql you would see very little difference between them as far as I have seen. there must however be some benefits for awr as this is the way that Oracle is going. As far as I am aware you need no special privilege to run awr.
    rgds
    alan

  • STATSPACK Report in Oracle RAC

    Dear friends,
    When I tried to make a STASPACK report on RAC nodes, I got the following error:
    The starting snap_id doesnot belong to this instance.
    When I tried using the other node, I got hte error:
    The ending snap_id doesnot belong to this instance.
    Is there any thing to do special for RAC expect for the constraint of STATSPACK be of level 7 or higher.
    Regards,
    Aravind K R

    Snapshots are different for different nodes. Please put the correct snap ID for gathering the statpack report.
    Regards
    Asif Kabir

  • Statspack: High log file sync timeouts and waits

    Hi all,
    Please see an extract from our statpack report:
    Top 5 Timed Events
    ~~~~~~~~~~~~~~~~~~ % Total
    Event Waits Time (s) Ela Time
    log file sync 349,713 215,674 74.13
    db file sequential read 16,955,622 31,342 10.77
    CPU time 21,787 7.49
    direct path read (lob) 92,762 8,910 3.06
    db file scattered read 4,335,034 4,439 1.53
    Avg
    Total Wait wait Waits
    Event Waits Timeouts Time (s) (ms) /txn
    log file sync 349,713 150,785 215,674 617 1.8
    db file sequential read 16,955,622 0 31,342 2 85.9
    I hope the above is readable. I'm concerned with the very high number of Waits and Timeouts, particulary around the log file sync event. From reading around I suspect that the disk our redo log sits on isn't fast enough.
    1) Is this conclusion correct, are these timeouts excessively high (70% seems high...)?
    2) I see high waits on almost every other event (but not timeouts), is this pointing towards an incorrect database database setup (give our very high loads of 160 executes second?
    Any help would be much appreciated.
    Jonathan

    Top 5 Timed Events
    ~~~~~~~~~~~~~~~~~~ % Total
    Event Waits Time (s) Ela Time
    log file sync 349,713 215,674 74.13
    db file sequential read 16,955,622 31,342 10.77
    CPU time 21,787 7.49
    direct path read (lob) 92,762 8,910 3.06
    db file scattered read 4,335,034 4,439 1.53
    Avg
    Total Wait wait Waits
    Event Waits Timeouts Time (s) (ms) /txn
    log file sync 349,713 150,785 215,674 617 1.8
    db file sequential read 16,955,622 0 31,342 2 85.9What's the time frame of this report on?
    It looks like your disk storage can't keep up with the volume of I/O requests from your database.
    The first few thing need to look at, what're IO intensive SQLs in your database. Are these SQLs doing unnecessary full table scan?
    Find out the hot blocks and the objects they belong.
    Check v$session_wait view.
    Is there any other suspicious activity going on in your Server ? Like other program other than Oracle doing high IO activities? Are there any core dump going on?

  • A suggestion about statspack...

    Hi ,
    I need a suggestion in statspack and sql tuning/db performance when an application runs......
    Imagine that I run some forms/reports e.t.c. developed with Developer Suite 10.2 , say form1 , form2 , form3 , form4 .... form15 in a time of 10 minutes...
    Next examining the statpack report , i try to alter a db parameter let's say DB_CACHE_SIZE ......
    Should I run exactly the same forms (form1 , form2 , form3 , form4 .... form15) in about 10 minutes and compare the two statspack report... or should I run other forms in the same (or about the same) amount of time?????
    Something else.... Which is best of the following.. to alter one - by - one db parameter and compare the new statspack report to the older or alter two,three... db parameters at once and compare the new statspack report to the older....one.
    Thanks , a lot
    Simon

    Click here and fill out the form.
    (40845)

  • Index coalesce

    hi masters.,
    this is egarding index management. i am facing the problem regarding one sql query with union and order by clause.
    when i remove order by clause, the query runs faster,than with order by clause.
    is this the problem regarding index????
    i know that indexes rarely need rebuild,thats why i am thinking of coalesce.is this the right decision??
    what may be the problem else????
    i am using oracle 9i. and i dont have statpack report coz the client is offshore.\
    thanks and regards
    VD

    Vikrant,
    Index is not picked by order by clause. Index entries are already sorted. See here a demo where I have used the index in a column.If I give order by clause, I explicitly get a Sort Order By in the plan.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
    With the Partitioning, Oracle Label Security, OLAP, Data Mining,
    Oracle Database Vault and Real Application Testing options
    SQL> create table sampletable as select * from scott.emp;
    Table created.
    SQL> create index idx on sampletable(empno);
    Index created.
    SQL> exec dbms_stats.gaher_table_stats(
    BEGIN dbms_stats.gaher_table_stats(; END;
    ERROR at line 1:
    ORA-06550: line 1, column 36:
    PLS-00103: Encountered the symbol ";" when expecting one of the following:
    ( ) - + case mod new not null <an identifier>
    <a double-quoted delimited-identifier> <a bind variable>
    table continue avg count current exists max min prior sql
    stddev sum variance execute multiset the both leading
    trailing forall merge year month day hour minute second
    timezone_hour timezone_minute timezone_region timezone_abbr
    time timestamp interval date
    <a string literal with character set specification>
    SQL> exec dbms_stats.gaher_table_stats('AMAN','SAMPLETABLE');
    BEGIN dbms_stats.gaher_table_stats('AMAN','SAMPLETABLE'); END;
    ERROR at line 1:
    ORA-06550: line 1, column 18:
    PLS-00302: component 'GAHER_TABLE_STATS' must be declared
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    SQL> exec dbms_stats.gather_table_stats('AMAN','SAMPLETABLE');
    PL/SQL procedure successfully completed.
    SQL> set autot trace exp
    SQL> select * from sampletable order by empno;
    Execution Plan
    Plan hash value: 5644182
    | Id  | Operation          | Name        | Rows  | Bytes | Cost (%CPU)| Time
    |
    |   0 | SELECT STATEMENT   |             |    14 |   504 |     4  (25)| 00:00:01
    |
    |   1 |  SORT ORDER BY     |             |    14 |   504 |     4  (25)| 00:00:01
    |
    |   2 |   TABLE ACCESS FULL| SAMPLETABLE |    14 |   504 |     3   (0)| 00:00:01
    |
    SQL> select * from sampletable order by empno where empno in (7369,7422);
    select * from sampletable order by empno where empno in (7369,7422)
    ERROR at line 1:
    ORA-00933: SQL command not properly ended
    SQL> select * from sampletable  where empno in (7369,7422);
    Execution Plan
    Plan hash value: 3966318501
    | Id  | Operation                    | Name        | Rows  | Bytes | Cost (%CPU)
    | Time     |
    |   0 | SELECT STATEMENT             |             |     2 |    72 |     1   (0)
    | 00:00:01 |
    |   1 |  INLIST ITERATOR             |             |       |       |
    |          |
    |   2 |   TABLE ACCESS BY INDEX ROWID| SAMPLETABLE |     2 |    72 |     1   (0)
    | 00:00:01 |
    |*  3 |    INDEX RANGE SCAN          | IDX         |     2 |       |     0   (0)
    | 00:00:01 |
    Predicate Information (identified by operation id):
       3 - access("EMPNO"=7369 OR "EMPNO"=7422)
    SQL> select * from sampletable  where empno in (7369,7422) order by empno;
    Execution Plan
    Plan hash value: 3966318501
    | Id  | Operation                    | Name        | Rows  | Bytes | Cost (%CPU)
    | Time     |
    |   0 | SELECT STATEMENT             |             |     2 |    72 |     1   (0)
    | 00:00:01 |
    |   1 |  INLIST ITERATOR             |             |       |       |
    |          |
    |   2 |   TABLE ACCESS BY INDEX ROWID| SAMPLETABLE |     2 |    72 |     1   (0)
    | 00:00:01 |
    |*  3 |    INDEX RANGE SCAN          | IDX         |     2 |       |     0   (0)
    | 00:00:01 |
    Predicate Information (identified by operation id):
       3 - access("EMPNO"=7369 OR "EMPNO"=7422)
    SQL>The point that I was making is that it may be happening that you are doing an over sort sort of thing which is causing the query to be slow. Using index for returning rows in the ordered manner is not a good thing as Oracle always say that for a guaranteed ordered result, one must use an order by clause. So either you can choose to remove the order by clause or can choose to rewrite the query without using the Union operator.
    But these all are just guess works. Its not possible to say what's happening specifically in your case as long as you don't post the plan for your query both,with and without the use of index.
    HTH
    Aman....

  • Top 5 Timed Events

    Hi,
    I am getting following in my statspack report for one of the server.
    PL/SQL lock timer
    direct path write
    direct path read
    Any tips how can I investigate.
    Regards,
    Umair

    direct path write/read is sorting in temporary space (ussually).
    Try to increase sort_area_size
    (You can find in your statpack report quantity of sorts in memory and on the disk.)

  • Delays in insert

    My statpack report say:
    CPU Elapsd
    Physical Reads Executions Reads per Exec %Total Time (s) Time (s) Hash Value
    INSERT INTO log_mov ( MOV_institution_id, MOV_local_date, MOV_lo
    cal_time, MOV_trx_code, MOV_trace_num, MOV_access_id, MOV_msg_ty
    pe, MOV_debit_credit_reason, MOV_debit_credit_descr, MOV_trx_act
    ion_code, MOV_pure_action, MOV_transmition_time, MOV_acq_busines
    s_date, MOV_terminal_id, MOV_ref_num, MOV_term_unit, MOV_channel
    9,082 181 50.2 1.4 0.81 61.75 246240137
    My question:
    This Insert delay 61 sec?
    Why?
    Thanks
    Greetings
    Juan

    The data is accumulated.
    So it took 61 secs to insert 181 records.
    Whether that is slow? Who can tell?
    You didn't post a version. Why?
    You didn't post a platform. Why?
    You didn't post data about file statistics. Why?
    You didn't post the report properly formatted. Why?
    Sybrand Bakker
    Senior Oracle DBA

  • STATSPACK Collection Level

    Hi,
    this is Top 5 Timed Events in statpack report :
    Top 5 Timed Events
    ~~~~~~~~~~~~~~~~~~                                                      % Total
    Event                                               Waits    Time (s) Call Time
    CPU time                                                          122     91.65
    db file sequential read                             1,571           2      1.61
    db file scattered read                              1,174           2      1.59
    log file sequential read                              342           2      1.39
    control file parallel write                           450           2      1.39
    Wait Events  DB/Inst: AKI1/AKI1  Snaps: 5-6but in my statpack report I have not the following two lines :
    db file sequential read                             1,571           2      1.61
    db file scattered read                              1,174           2      1.59Which collect level should I chose for my snapshot to have them ?
    Many thanks.

    db file sequential read
    1,571           2
    1.61
    le scattered read                              1,174
    2      1.59 ich collect level should I chose for my snapshot to
    have them ?If these two events are in top 5 they will be in the list.
    You should check Oracle document,
    Using Statspack
    http://download.oracle.com/docs/cd/B10501_01/server.920/a96533/statspac.htm#34837

  • Difference of using AWR

    Hi,
    Are there any differences between Running Workload Repository Reports Using Enterprise Manager and Running Workload Repository Reports Using SQL Scripts? further more what roles and rights do I need to run Workload Repository Reports Using SQL Scripts? Lastly what is difference between statspsck and awr? Which is better?
    Adith

    hi,
    if your where to run a statpack report and an awr report from sql you would see very little difference between them as far as I have seen. there must however be some benefits for awr as this is the way that Oracle is going. As far as I am aware you need no special privilege to run awr.
    rgds
    alan

  • Re: Column is not getting displayed in the BI report

    Hello Gurus,
    I have developed a BI report with more number of parameters.
    Case 1:
    When i run my report , I am able to see data for particular condition but one column doesn't show any thing. All the rows in the column are blank.
    Case 2
    I tried to put the blank column as parameter, The Program works with out displaying that column data.
    I am not sure where it is going wrong. I tried running the code in toad and i am able to see the data.
    I have checked the code, Parameter description, length, Template and data definition.
    Please help.
    Thanks,
    Sreekanth

    Hi ,
    For that column did u changed any alias name in the query...
    check ur template once by loading the xml data...
    check that column form field that matches with the xml tag or not..
    Thanks,
    Ananth

Maybe you are looking for