Re: command line vs grid control

On Jul 4, 12:11 am, DA Morgan <damor...@xxxxxxxxx> wrote:
i...@xxxxxxxxxxx wrote:
On Jul 3, 1:45 pm, DA Morgan <damor...@xxxxxxxxx> wrote:
Bob Jones wrote:
"DA Morgan" <damor...@xxxxxxxxx> wrote in message
news:1183413703.619051@xxxxxxxxxxxxxxxxxxxxxxxxx
emdproduct...@xxxxxxxxxxx wrote:
I am used to my old time shell/perl scripts to monitor my database,
routine work, should I invest in oracle 10g grid control?
Any commends will be appreciated
Assuming some version of Oracle more recent than 9.2.0.8 you can not
monitor a database using shell/perl scripts any longer.
Anyone that claims otherwise doesn't understand the product.
What is the change in 9.2.0.8 makes it impossible?
I said "more recent than" and the list is nearly endless which
is precisely the point. You couldn't write all the scripts
required to duplicate the functionality of the OEM grid control
if you worked on it 40 hours a week for the next 6 months. In

No need to duplicate everything. OP talks "monitor my database,
routine work". This can continue to be done with his existing scripts.
"You can not monitor a database using shell/perl scripts any longer"
for 10g+ looks like an overstatement.

fact some of that functionality is literally impossible to
duplicate with any shell script.

And what this functionality is exactly?

Regards,
Igor

The original question was "should I invest in" and the answer is
yes.
--
Daniel A. Morgan
University of Washington
damor...@xxxxxxxxxxxxxxxx (replace x with u to respond)
Puget Sound Oracle Users Groupwww.psoug.org

One simple example: You can not do this.

SELECT TO_CHAR(s.startup_time,' DD MON "at" HH24:MI:SS') INSTART_FMT,
di.instance_name INST_NAME, di.db_name DB_NAME, s.snap_id SNAP_ID,
TO_CHAR(s.end_interval_time,'DD MON YYYY HH24:MI') SNAPDAT,
s.snap_level LVL
FROM dba_hist_snapshot s, dba_hist_database_instance di
WHERE di.dbid = s.dbid
AND di.instance_number = s.instance_number
AND di.startup_time = s.startup_time
ORDER BY snap_id;

Well of course you can. But to do so you would need to buy the
license to do so in the Grid Control. So you've already spent
the money.

Take a look at the list of features monitored here:http://www.psoug.org/reference/dbms_serv_alert.html
To do this with a shell script would require that you again buy
the appropriate Grid Control license.

Perhaps we should define "monitoring" more precisely but it's hardly
an ability to select from dba_hist views. Anyway any decent custom
monitoring scripts save point-in-time measurements as historical data.
Or you can fall back to Staspack. It doesn't equal AWR or Diagnostics
Pack but certainly covers "monitoring" bit.

More developers were used to build the 10g Grid Control than
to build the 10g database. How far do you think you are going
to get duplicating that with a shell script unless you violate
your employer's license agreement.

Apparently you didn't read my reply so I'll repeat once more:
_No_need_to_duplicate_everything_in_OEM;_it_contains_much_more_than_just_monitoring.
OP talks "monitor my database, routine work". This can continue to be
done with his existing scripts.

You are talking functionality which is not even available for every
10g edition (as JG mentioned it's EE only). Does it mean non-EE can
not be "monitored" (in your understanding of the word) even with
Oracle's own tools?

Is it still "You can not monitor a database using shell/perl scripts
any longer"?

On Jul 4, 12:13 am, DA Morgan <damor...@xxxxxxxxx> wrote:
You've no right to endanger your employer by putting them into legal jeopardy with Oracle.

No worries mate, my employer has it all covered. Appreciate your
concern anyway :)

Igor.

--
Daniel A. Morgan
University of Washington
damor...@xxxxxxxxxxxxxxxx (replace x with u to respond)
Puget Sound Oracle Users Groupwww.psoug.org


.

Relevant Pages

  • Re: command line vs grid control
    ... Assuming some version of Oracle more recent than 9.2.0.8 you can not ... monitor a database using shell/perl scripts any longer. ... required to duplicate the functionality of the OEM grid control ... monitoring scripts save point-in-time measurements as historical data. ...
    (comp.databases.oracle.server)
  • Re: command line vs grid control
    ... routine work, should I invest in oracle 10g grid control? ... Assuming some version of Oracle more recent than 9.2.0.8 you can not ... monitor a database using shell/perl scripts any longer. ... required to duplicate the functionality of the OEM grid control ...
    (comp.databases.oracle.server)
  • Re: command line vs grid control
    ... Assuming some version of Oracle more recent than 9.2.0.8 you can not ... monitor a database using shell/perl scripts any longer. ...
    (comp.databases.oracle.server)
  • Re: command line vs grid control
    ... If your scripts cover your requirements, ... The quality of monitoring: Oracle wins ... The fact that their code is tested: Oracle wins ... Given that we use grid control (which suits our ...
    (comp.databases.oracle.server)
  • Re: command line vs grid control
    ... Assuming some version of Oracle more recent than 9.2.0.8 you can not ... monitor a database using shell/perl scripts any longer. ... required to duplicate the functionality of the OEM grid control ...
    (comp.databases.oracle.server)