-
Notifications
You must be signed in to change notification settings - Fork 3
FAQ
OSPRep is reported to work with Oracle versions 8i to 11g. I cannot always test with all these versions - so I need your feedback to tell me whether there are problems. At least for v0.4.2, support for 8i was completely broken (hopefully fixed with v0.4.3) without my notice (8i is not longer supported by Oracle, and I rarely use it), since nobody reported for a long time I found out only lately. So please feel encouraged to always give a short feedback, and don't always rely on others ;)
If you get this error, you probably try to generate a report against some Oracle 11g database. OSPRep is not yet tested with Oracle 11g, so errors like this may come up. Luckily, for this one there is an easy work-around confirmed by one user - and implemented with v0.4.3: Simply change to the plugins/ directory, take the sp102.pls file and copy (or symlink) it to sp111.pls (in the same directory) will solve this issue (and may work for future versions, too).
It looks very much like 11g didn't change Statspack structures (compared to 10g) too much, so you may have the same luck if experiencing similar problems. If so, please report so this article can be updated.
The AWR compatibility layer introduced with OSPRep v0.4.5 basically is a collection of views created against the dba_hist_* tables used by the AWR (Automated Workload Repository) of Oracle 10g, plus a basic statspack package holding the statspack.stat_changes procedure. These objects are created when you run the install/database/awr_setup.sql script against an Oracle user with similar permissions to the perfstat user (but it must NOT be the perfstat user itself, as the views take the names of perfstats tables). This means, once created, you can use this layer also with your own customized Oracle StatsPack related scripts. Keep in mind that this is neither perfect nor even complete: Things may be missing (please report!), and others just contain dummy data (or rather no data), just to keep your scripts from crashing. Not all StatsPack data are available this way, you can e.g. not get any Top-SQL statistics here.