/ *** OEM foundation *** /
OEMs in Oracle 9i are three-layer architecture: * The first layer is the user client, composed of Java-based console and integrated application tools. * The first layer is Oracle Management Server (OMS) or OMS group constructed Management, providing a centralized intelligent management environment and distributed control between clients and management targets. * The third layer is the management target, which can be a computer node, database server, both in various management nodes. Run the Oracle Intelligent Agent service to monitor the running status of the node and accept and assign the management job sent by OMS.
OMS is the core in the OEM architecture. It is responsible for managing OEM administrators users, handles special management tasks (jobs, events, etc.) and between console (first layers) and database servers (Layer 3) Send message.
Oracle OMS uses a special database-data file library to save all OEM system data, application data, and information managed node. In installation of Oms, the data file library will be created, the data file is specially stored OEM management Database database, OMS, during operation, save the system's maintenance information, management application information, and other management information in the data archive. You can create a new database for the data archive, or save it Any table space for existing databases. Each OMS must be used and can only use a data archive, but a data file can be shared by multiple OMS.
If you create a database separately for the data archive, the default name (SID) of this database is OEMREP. The data file user is a user in the database of saving the profile library, with all objects in the information archive library in its mode. When an OMS connection information archive, use is this user's account. The data file user name must be unique on the entire network, that is, different OMS must use different data files when connecting the same information archive. User name, because the Intelligent Agent is distinguished by the data file user name used by OMS. The default information archive username is best set in the form of "OEM_ hostname _oemrep". By default, The data file username and password are saved in the OMSConfig.properties configuration file, and the OMS will read the file at startup and log in to the username and password provided in the file to the information archive library.
If an error occurs during the startup OMS, you can open the OMS.NoHUP file located in the Oracle_Home / Sysman / Log directory to view the error message. After installing OEM, you will create a default OEM administrator account: sysman / oem_temp.
Stop OMS Service: You will prompt you to enter the OEM administrator's account and password. Note that the OEM administrator account is not a data archive user account, but Sysman / Oem_Temp.
Deleting a profile: You must have a DBA account in a database of stored data files (note that the data file user account is not the data file, but the database user with SYSDBA privileges such as SYSTEM or SYS). In addition, the OMS service must be stopped, and if there is other OMS being connected to this information archive, it cannot be deleted.
OEM super administrators can determine which managers can see which managers and objects can be seen in a general administrator, which can be implemented by setting target access for the general administrator account. After establishing a new administrator account, it is necessary To set the preferred identity for him, the preferred identity of the administrator will be saved in the data file. When the administrator connection has the first identity certificate, the intelligent agent will automatically log in to the target, so that Avoid administrators enter your username and password.
