If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

statspack spreport.sql error

Statspack was installed in a newer 10g database on Solaris 10. Snapshots were gathered throughout the day for performance tuning information. When I try to execute the report via ?/rdbms/admin/spreport.sql I am prompted for start and end snap id's, then I get this error message:
Phys Memory (MB):
~~~~
, e.seg_cr_bks_rc_th ecrb
*
ERROR at line 48:
ORA-00904: "E"."SEG_CU_BKS_RC_TH": invalid identifier

Any clues? I've checked the stats$snapshot table (where the column resides) and everything looks good. I've removed a custom glogin.sql to make sure there were no problems with certain sqlplus parameters for executing the script, still no luck.

Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

PAVB thanks for the info. While going through the motions of your last message I realized what the problem was.

The DB was a 9i DB that was migrated to 10g, the perfstat was installed and the schema was the 9i version, while I was running the 10g spreport.sql. I was working with another db who is part time (and unavailable most other days) and he set it up yesterday so I assumed it was a new install.

Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.