A script enabled browser is required for this page to function properly. ShowDoc
Home
My Oracle Support (the new MetaLink) Bookmarks Admin Profile Feedback Sign Out Help 
   Headlines Knowledge Service RequestCollectorPatches & UpdatesCommunityCertify
   Knowledge Browser  Advanced Search   Bug Search    
Quick Find
Go
      Advanced   Saved Searches
Did this article help solve your problem? Would you recommend this document to others?
 
Bookmark Fixed font Go to End Monitor Bug

Bug No. 5599831
Filed 12-OCT-2006 Updated 08-NOV-2006
Product Enterprise Manager for RDBMS Product Version 10.2.0.2
Platform HP-UX PA-RISC (64-bit) Platform Version No Data
Database Version 10.1.0.4 Affects Platforms Generic
Severity Severe Loss of Service Status Not a Bug. To Filer
Base Bug N/A Fixed in Product Version No Data

Problem statement:

NOT ABLE TO MANAGE 9I STATSPACK USING 10G GRID

 

*** JOBJOSEP 10/12/06 11:16 pm ***

TAR

---

5818870.992

.

Problem:

--------

We are not able to manage statspack reports on a 9i database using 10g Grid.

.

Note:274436.1 says the steps needs to be followed for configuring statspack

using Grid.

But we are not able to see the "SNAPSHOTS" link.

.

We even tied the steps discussed in

.

@ http://st-doc.us.oracle.com/10/102/em.102/b16242/addnl_tasks.htm#sthref1154

.

starting with

.

"To manually install Statspack and the other required database objects into

an Oracle9i database that you are managing with Enterprise Manager, you can

use SQL*Plus and the following procedure:

.

Log in to the database host using an account with privileges that allow you

to write to the database home directory and to the Management Agent home

directory.

.

For each of the commands in this procedure, replace AGENT_HOME with the

actual path to the Oracle Management Agent home directory and replace

ORACLE_HOME with the path to the database home directory.

.

Start SQL*Plus and connect to the database using the SYS account with SYSDBA

privileges.

.

For example:

.

$PROMPT> ./sqlplus "connect / as sysdba"

.

Enter the following command to run the database dbmon script:

.

SQL> @AGENT_HOME/sysman/admin/scripts/db/config/dbmon

"

.

But nothing helps. We are not able to see the "SNAPSHOT" link in performance

page. Issue reproduces inhouse.

.

Versions:

---------

Grid : 10.1.0.4

9i : 9.2.0.4

.

Diagnostic Analysis:

--------------------

.

Reproducibility:

----------------

.

Test Case:

----------

Testcase details

.

@ MACHINE:netapp2.idc.oracle.com

@ Grid URL :http://netapp2.idc.oracle.com:4889/em

9i database name :ora920 (Already added as a target)

.

OMS details

-----------

ORACLE_SID=ora1g2

ORACLE_HOME=/u01/grid/oms10g

.

AGENT details

------------

ORACLE_SID=ora1g2

ORACLE_HOME=/u01/grid/agent10g

.

EMREP details

=============

ORACLE_SID=emrep

ORACLE_HOME=/u01/grid/db10g

.

9i Database details

------------------

ORACLE_SID=ora920

ORACLE_HOME=/u01/ora920

.

.

.

Workaround:

-----------

NA

.

Related Bug(s):

---------------

.

Location Of Information (i.e. ESS30):

-------------------------------------

.

Stack Trace and Errors:

-----------------------

.

Uploaded Configuration Files:

-----------------------------

.

24-hour Contact Information For P1 Bugs:

----------------------------------------

.

Additional Environment Information:

-----------------------------------

.

Memory Leak Information:

------------------------

.

Uploaded Trace/Log Files:

-------------------------

.

*** DRUSSELL 10/13/06 04:25 am *** (CHG: Prod->1366 Comp->INSTANCE)

*** MHORNSPE 10/16/06 06:07 am *** (CHG: Asg->MHORNSPE)

*** MHORNSPE 10/16/06 06:54 am *** (CHG: Sta->10)

*** MHORNSPE 10/16/06 06:54 am ***

@ BDE Bug Screening

@ .

@ 1. Can we clarify the versions ? The bug header / body refer to GRID 10.1.0.4

@ while the SR mentions OMS 10.2.0.1. I'd like to know the exact versions of

@ the OMS and the agent being used to monitor this 9i database.

@ .

@ 2. Note 344852.1 describes certified targets. In terms of 9i databases,

@ 9.2.0.6 and above are certified targets while 9.2.0.4 is not. As the issue

@ reproduces inhouse, can we verify whether the problem reproduces with 9.2.0.6

@ (or 9.2.0.7/8) ?

@ .

.

.

*** MHORNSPE 10/16/06 07:05 am ***

.

.

.

*** JOBJOSEP 10/17/06 07:05 am *** (CHG: Sta->16)

*** JOBJOSEP 10/17/06 07:05 am ***

@ Hi,

@ .

@ These are the versions from customer end.

@ .

@ Agent Version : 10.2.0.1.0

@ OMS Version : 10.2.0.1.0

@ the 9i Database version is :9.2.0.6

@ .

@ But still she is still not able to see the snapshot link.

@ .

@ Could you tell me the exact step by step instructions to follow to setup the

@ statspack.

@

@ The testcase I reproduced was for a de-supported matrix.

@ If you could give the exact steps I can give that to customer and see any

@ problems in the steps we are following.

@ .

@ .

@ Thanks

@ Jobin

*** MHORNSPE 10/18/06 07:11 am ***

@ Created a brand new 9.2.0.7 database with a dictionnary managed system

@ tablespace and installed statspack with 10.2.0.2 GC. This went thru fine but

@ indeed the Snapshots link does not show up there.

@ .

@ Will try with another 9.2.x database version.

*** MHORNSPE 10/19/06 07:38 am *** (CHG: SubComp->PERF)

*** MHORNSPE 10/19/06 07:57 am ***

@ Tried against several 9.2.0.7 RDBMS - no way to see the SNAPSHOT link

@ anymore.

@ Confirmed that the STATSPACK is installed properly by using the "Configure"

@ option in the list of all database targets.

@ Confirmed as well that we don't have any invalid objects.

@ .

@ One needs to have two valid snapshots in order to display historical data.

@ If STATSPACK is installed properly, the TOPSQL data should be available.

@ .

@ Investigating further...

*** MHORNSPE 10/20/06 05:36 am *** (CHG: Sta->10)

*** MHORNSPE 10/20/06 05:36 am ***

@ BDE Update

@ ==========

@ 1. First of all, as 9.2.0.6 and above are certified DB targets, one does not

@ need to install STATSPACK manually but rather let GC do it for you.

@ It's not just about running the dbmon script as one also needs to create a

@ PERFSTAT schema and so on.

@ .

@ To do so:

@ a. Go in the Targets -> Databases tab/subtab.

@ b. Select the radio button in front of your database.

@ c. Click Configure

@ d. If things were partially installed, de-install the STATSPACK and proceed

@ with the wizard.

@ e. Repeat the same steps to re-install STATSPACK properly from there.

@ f. Verify in the Jobs tab that the STATSPACK install job succeeded properly.

@ .

@ 2. As of now, there is a DBMS_JOB executed every hour which collects a

@ database snapshot. This can be verified by querying the DBA_JOBS view under

@ the schema DBSNMP against the target 9.2.0.6 database.

@ .

@ 3. To ensure that STATSPACK works fine in GC, wait for a couple of hours as

@ we need at least two snapshots to be collected to view historical data. Then,

@ go in GC -> Targets -> Database -> < Your 9.2.0.6 Database> -> Performance

@ tab. Choose Top SQL and select Historical Data. As soon as you have more than

@ two snapshots collected, historical data should be visible.

@ Please confirm this works.

@ .

@ 4. When monitoring 8.1.7.x and 9.2.0.x databases, GC is using STATSPACK. When

@ monitoring 10gR1 / 10gR2 databases, GC is using AWR (Automatic Workload

@ Repository). As such, the links "Snapshots" gets displayed in the database

@ performance page. However, it displays AWR Snapshots and not STATSPACK

@ snapshots. I don't even believe we should see this Snapshots link at all when

@ monitoring a 9.2.0.x database, as there is no AWR concept in 9.2.0.x RDBMS.

@ .

@ Please clarify what exactly (e.g. Doc Pointer, Note, ...) makes you think we

@ should see this Snapshots link against a 9.2.0.x RDBMS. I'm really not

@ convinced this is a bug.

@ .

@ Now, if customers wants to gather more details about the snapshots, they can

@ run Snapshot reports, as described in Note 149124.1.

*** JOBJOSEP 11/08/06 05:27 am *** (CHG: Sta->16)

*** JOBJOSEP 11/08/06 05:27 am ***

@ Hi,

@ .

@ You are right..Customer agreed to accept this truth.

@ The note 274436.1 seems to be misleading.

@ Please close this as "not a bug"

@ .

@ Thanks

@ Jobin

*** MHORNSPE 11/08/06 05:38 am *** (CHG: Sta->32)

*** MHORNSPE 11/08/06 05:38 am ***

@ Closing as not a bug - might be good to add a remark to this note as it's

@ indeed misleading.

.
    
Copyright © 2006, Oracle. All rights reserved. Legal Notices  and Terms of Use | Privacy Statement