RelationalDBDesign 





DB Creation   «Prev 

GUI Version of Oracle Server Manager

For UNIX users, Oracle supplies a GUI version of Server Manager. The command to start it is: svrmgrm.
The “m” at the end of the command stands for “Motif”.
Motif is an X-Windows-based windowing manager that you need in order to use the GUI version.
To start the GUI version of Server Manager from an X-windows client, you first open a Telnet session, then issue the svrmgrm command.
I do not emphasize learning the GUI version of Server Manager because it's not a strategic product for Oracle. Enterprise Manager is Oracle's flagship database administration tool, and it's GUI-based. If you want to learn a GUI administration tool, you are much better off focusing your efforts on learning Enterprise Manager, and in the next course of this series you will begin to do just that.

GUI Tool to manage Oracle Databases

In 1996, Oracle made a first attempt at releasing a GUI tool to manage its databases. This was Oracle Server Manager, which featured a
  1. command line and
  2. GUI interface.


Most DBAs resorted to using only the command line interface of Server Manager, called Server Manager/Line Mode. This was because at that time it was easier to get things done using the command line. In addition, the first few releases of the GUI interface had limited administrative capabilities.
Oracle then released a new version, Oracle Enterprise Manager.
OEM 9.2 was released in 2002, which was when larger numbers of DBAs first started using Enterprise Manager. The console product was Java-based and had to be installed as a separate product on each workstation accessing the central repository of Enterprise Manager.
This OEM 9.2 was a stand-alone console mode without a repository and a mode that connected to a central repository. Many DBAs used the stand-alone mode without the repository; as a result, there was no central repository of database information in many sites even though OEM 9.2 was being used.
In 2004, Oracle rewrote the product with a new architecture based on its application server technology Oracle 9i. The console was now browser-based and could be accessed from any workstation on the corporate network without the need to install software on any workstation. The only installation required was the repository and server agents. The stand-alone mode was no longer possible, thus forcing the use of a centralized repository.
The Enterprise Manager product that allowed management of multiple databases and servers was named Grid Control, after use of the 'g' letter in the Oracle 10g database, and the emphasis it laid on the Grid as the future of computing.
DBAs can understand how Grid Control can assist in the daily database administration activities. DBA would like the automation of jobs without scripts, removing much of the dependence on UNIX shell scripts and cron jobs.

Grid Control

Grid Control can also be used by System Administrators for most of them would appreciate its
  1. host performance monitoring capabilities,
  2. performance history of host CPU,
  3. memory utilization being stored in the repository, and
  4. the host configuration comparison capabilities for troubleshooting.
Question: How can Grid Control help IT managers
  1. achieve an overall view of the corporate infrastructure system and
  2. provide reports and information on security compliance,
  3. application level performance dashboards,
  4. database versions in use,
  5. licensing usage,
  6. conformation to standards,
  7. unnecessary storage allocation, and
  8. unused databases?
Answer:The OEM Grid Control can create databases in a matter of minutes .