如何对添加Oracle服务器的监控?

April.H.X

在Database Server Resource Graphs节点下,选择Oracle,在Add Measurements窗口中,添加了Oracle服务器IP,在Oracle Logon窗口中输入帐号,密码及服务名,完成添加, 出现下面的提示信息:

Could not find V$SYSSTAT V$SESSTAT V$STATNAME V$INSTANCE V$SESSION V$PROCESS.
Check their access permission.

请问怎么解决这个问题?

April.H.X

怎么没人回答？？？

pcl2004_27

To configure the Oracle database monitor to monitor multiple instances:
1. Right-click and select "Add measurements" in the Oracle monitor graph from the Controller.
2. Click on the "Add" button for "Monitor Server Machines" and enter the <machine>:<Oracle_instance> information.
   a. For multiple instances, add <machine>:<Oracle_instance1>, then add <machine>:<Oracle_instance2>,etc. Repeat the same process until you added all the instances.
   b. For multiple database servers, add <machine1>:<Oracle_instance>, then add <machine2>:<Oracle_instance>, etc. Repeat the same process until you added all the database servers.
3. Highlight <machine>:<Oracle_instance>, click on the "Add" button for "Resource Measurements on."
4. Fill in the appropriate information in the Oracle Logon window.
5. Click <OK>.
6. Repeat the same process for all the database servers or database instances

pcl2004_27

In order to use the Oracle Monitor, you need to be able to see the following V$ tables:

   V$STATNAME
   V$INSTANCE
   V$SESSION
   V$SESSTAT
   V$SYSSTAT
   V$PROCESS

1. Open up SQL*Plus. Login with the same user ID and password supplied in the Controller when setting up the Oracle Monitor. Run the following SQL statement:

   SELECT * FROM V$STATNAME;

2. If you get a "Table or view does not exist" message, have your DBA grant "SELECT_CATALOG_ROLE" permission for the corresponding useid. This will give read permission to the table.

3. Repeat steps 1 and 2 for all the tables above.

pcl2004_27

ok?
please try again!

April.H.X

thank you in advance, try it later ;)

April.H.X

OMG~~so many measurements....

where can I ge the specification for these measurements?

pcl2004_27

Which Counters to choose?

The 10 most recommended metrics are taken from the V$SYSSTAT table:

•        CPU used by this session - This is the amount of CPU time (in 10s of milliseconds) used by a session between when a user call started and ended. Some user calls can complete within 10 milliseconds and as a result, the start and end user-call time can be the same. In this case, 0 milliseconds are added to the statistic. A similar problem can exist in the reporting by the operating system, especially on systems that suffer from many context switches.

•        Bytes received via SQL*Net from client - The total number of bytes received from the client over Net8.

•        Logons current - The total number of current logons. This statistic is useful only in V$SYSSTAT.

•        Opens of replaced files - The total number of files that needed to be reopened because they were no longer in the process file cache.

•        User calls - Oracle allocates resources (Call State Objects) to keep track of relevant user call data structures every time you log in, parse, or execute. When determining activity, the ratio of user calls to RPI calls, give you an indication of how much internal work gets generated as a result of the type of requests the user is sending to Oracle.

•        SQL*Net roundtrips to/from client - Total number of Net8 messages sent to and received from the client.

•        Bytes sent via SQL*Net to client - The total number of bytes sent to the client from the foreground process(es).

•        Opened cursors current - The total number of current open cursors.

•        DB block changes - Closely related to consistent changes, this statistics counts the total number of changes that were made to all blocks in the SGA that were part of an update or delete operation. These are changes that are generating redo log entries and hence will be permanent changes to the database if the transaction is committed. This statistic is a rough indication of total database work. This statistic indicates (possibly on a per-transaction level) the rate at which buffers are being dirtied.
•        Total file opens - The total number of file opens being performed by the instance. Each process needs a number of files (control file, log file, database file) in order to work against the database.