Oracle Enterprise Manager (OEM) FAQs

OracleEnterpriseManager (Oracle Enterprise Manager (OEM) provides management services for managing distributed environments through a set of Oracle programs. OEM includes a set of DBA tools, a repository, and a graphical console. The OEM console corresponds to the intelligent agent on each server. Intelligent

OracleEnterpriseManager (Oracle Enterprise Manager (OEM) provides management services for managing distributed environments through a set of Oracle programs. OEM includes a set of DBA tools, a repository, and a graphical console. The OEM console corresponds to the intelligent agent on each server. Intelligent

OracleEnterpriseManager (Oracle Enterprise Manager (OEM) provides management services for managing distributed environments through a set of Oracle programs. OEM includes a set of DBA tools, a repository, and a graphical console. The OEM console corresponds to the intelligent agent on each server. Intelligent Agents can monitor specific events of the system and execute tasks (jobs) Just as you do locally in the system. The results of events and jobs are sent back to the console, so that all systems can be managed in one place.

Compared with ServerManagerMotif, OEM has the following advantages:

1) In terms of applicability, OEMs can monitor and manage multiple databases on multiple systems at the same time, so they are particularly suitable for distributed environments, while ServerManager can only monitor and manage one database.

2) from the perspective of management objects, OEMs can monitor management nodes, databases, and listener processes, while ServerManager can only monitor databases.

3) from the perspective of applicable versions, OEMs can monitor and manage Oracle7.x and 8.xat the same time. From version 8, ServerManager does not exist.

This document describes common OEM problems and solutions.

Q: What are the functions of the OEM database tool group?

A: The OEM database tool group is A set of tools that enable DBA to manage Oracle databases through the GUI. Includes the following tools:

DataManager (Data Manager): This tool enables you to execute data export/import like loading data.

SchemaManager: This tool enables you to manage objects in the database. It can be used to create, modify, and delete tables, indexes, views, snapshots, sequences, and so on.

SecurityManager: This tool enables you to manage users, roles, permissions, and profiles.

StorageManager: this tool allows you to create and modify tablespaces, data files, and rollback segments.

InstanceManager: this tool allows you to close, start an instance, and store and manage database parameters.

SQL * Worksheet: This tool enables you to run or create SQL scripts and store them on hard disks. You can use this tool to reproduce the last executed statement and check the execution results displayed on the screen.

BackupManager: this tool allows you to manage backups and restore to Oracle7 and Oracle8 databases. In Oracle7, this tool supports EnterpriseBackupUtility (EBU), and in Oracle8, this tool supports the recovery manager RecoveryManager.

SoftwareManager: This allows you to install remote software on a remote server that supports this feature.

Q: The job status has been submitted and has not changed to scheduled ).

A: The job is created on the OEM console and sent to intelligent proxy through SQL * net. Once an intelligent agent accepts a job request, a notification is sent back to the OEM console, and the status changes to "Reservation ". If the status never changes from submission to reservation, the agent may not receive a job request. Check whether the agent has been started and whether SQL * net and OEM have been properly configured.

Q: The job status is always scheduled and has not changed to running.

A: When the current manager starts running A job, A notification is sent back to the OEM console, and the status changes to "sent" or "started ". If the job status remains unchanged, it may be that the agent cannot open a socket and return to the OEM console, the cause may be a TCP/IP problem or the agent does not have sufficient permissions to derive a process to run the job. Use the host name on the server to Ping the console to check whether the TCP/IP address is correct. Make sure that the database user running the job has the permissions of dba, connect, and resource.

Q: An error occurred while running the job. The error message is "FailedtoAuthenticateUser ".

A: On the NT System, you must grant the "Logonasabatchjob" permission to the logon user and set this user in OEMPreferredCredentials. If the agent is a 7.3.x agent, the user must be a local NT user and cannot be a DOMAIN user. On Unix systems, the proxy program has the following permissions:-rwsr-xr-xrootdba

Dbsnmp "s" permission means that the dbsnmp process runs with the permissions of the root user. After this permission is set, the job is run by the user set in the PreferredCredentials window on the OEM console. Confirm that the user set in the PreferredCredentials window on the OEM console has the right to log on to the server.

Q: Can customers create custom events?

A: In OEM1.x, you cannot create custom events. This will be a new feature of OEM2.x. However, you can create a job to run the TCL script and trigger an event by using the TCL command orareportevent. For more information about orareportevent, see the OEM application developer manual.

Q: On the console, the database is displayed in red circles and diagonal lines, indicating that the database is closed. However, the database is running.

A: If the database, monitoring process or node is displayed in A red circle and diagonal line, the OEM console is trying to notify you that the service has been disabled. If the service is not closed, you need to click "OutstandingEventstab" in the event window and move the notification to history.

Clear the close prompt in the navigator and map Windows.

Q: How to Create OEMRepository?

A: OEMRepository is A group of tables in the Oracle7 or Oracle8 database. These tables store information graphically browsed through the OEM console. In the OEM1.x structure, these tables are stored under a specific user and cannot be shared with other users. In OEM1.2.x, a non-"system" user should be logged on to run the script SMPCRE. SQL. This user must have the connect, resource, and dba permissions. In OEM1.3.x, the Repository is automatically created when the OEM console icon is activated for the first time. If an earlier version of repository already exists, the system prompts to update the table. If no OEM table exists, the system prompts to create a table.

Q: How do I customize the OEM toolbar?

A: To set the OEM toolbar, right-click the toolbar and select Customizetab. You can edit the name of a toolbar project, delete a project, or add a project. If you click Databasetab, you can enter logoncredentials and select a default input item for each database.

Q: When you log on to the OEM console, the following error message is displayed:

VOC-00002: Failuretoobtaininterfacelogin

A: The reason is that the OEM communication background process cannot open A connection with Repository.

Check whether the TCP/IP configuration is correct and whether the default parameters of the Communication background process have been modified (DaemonManager is used ).

Q: When using the OEM console, the following error message is displayed:

VOC-00107: FailuresettingcredentialdetailsORA-03114: Not connected to ORACLE

A: The reason is that the database where OEMRepository is located has been shut down or the service connecting to the database has encountered A network fault.

Q: When you log on to the OEM console using SYSDBA, the following error message is displayed:

VOC-00121: Failureupdatingorinsertingauserdetailentry

ORA-00942: Tableorviewdoesnotexist.

A: The default role that the user logs on to the OEM console is NORMAL. If you need to connect as SYSDBA, set the CONNECTASSYSDBA option in the PreferredCredentials window.