Oracle Enterprise Manager (OEM) Common problem solving

Oracleenterprisemanager (Oracle Enterprise Manager, abbreviation OEM) provides management services for managing distributed environments through a set of Oracle programs. OEMs include a set of DBA tools, a repository, and a graphical display of the console. The OEM console corresponds to the intelligent agent (intelligentagent) on each server. Intelligent agents can monitor specific events on a system and perform tasks (jobs) just as you would on a system-local. 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, OEMs have the following advantages:

1 from the scope of application, OEMs can monitor and manage multiple databases on multiple systems at the same time, so they are particularly suitable for distributed environments, and Servermanager can only monitor and manage a single database.

2 from the Management object, OEMs can monitor management nodes, database and listener processes (listener), while Servermanager can only monitor the database.

3 from the applicable version, OEMs can monitor the management of oracle7.x and 8.x at the same time, and starting from the 8 version, Servermanager no longer exists.

This article mainly introduces some OEM's frequently asked questions and the solution method.

What is the function of the Q:OEM database tool group?

The A:OEM Database Tools group is a set of tools that enable DBAs to manage Oracle databases through a GUI interface. Includes the following tools:

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

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

SecurityManager (Security Manager): This tool enables you to manage users, roles, permissions, and profiles.

StorageManager (Storage Manager): This tool allows you to create and modify table spaces, data files, and rollback segments.

Instancemanager (instance Manager): This tool allows you to close, start the instance and store and manage database parameters.

Sql*worksheet: This tool enables you to run or create SQL scripts and store them on your hard disk. You can use this tool to reproduce the last executed statement, while checking the execution results that appear on the screen.

Backupmanager (Backup Manager): This tool allows you to manage backup and restore to Oracle7 and Oracle8 databases. In Oracle7 this tool supports Enterprisebackuputility (EBU), in Oracle8 This tool supports recovery manager Recoverymanager.

Softwaremanager (software Manager): This allows you to install remote software to a remote server that supports this feature.

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

A: Jobs are created at the OEM console and sent to an intelligent agent via sql*net. Once an intelligent agent accepts a job request, a notification is sent back to the OEM console, and the status changes to "scheduled". If the status is never changed from submission to reservation, the agent may not receive a job request. Determine if the agent has been started, and determine if the sql*net and OEM are properly configured.

Q: The job status has been scheduled, not changed to run

A: When the agent starts running the job, a notification is sent back to the OEM console, and the status changes to sent or started. If the job status has been scheduled without change, it may be that the agent cannot open a socket back to the OEM console, either because of a TCP/IP problem or because the agent does not have sufficient permissions to derive a process to run the job. Ping the console using the hostname on the server side to determine that there is no problem with TCP/IP, and that the database user running the job has Dba,connect,resource permissions.

Q: Run job error, error message: "Failedtoauthenticateuser".

A: On the NT system, you must grant the "Logonasabatchjob" permission to the logged-on user, and then set up the user in oempreferredcredentials. If the agent is a 7.3.x agent, the user must be a local NT user and not a domain user. On UNIX systems, the permissions for the agent should be:-RWSR-XR-XROOTDBA

Dbsnmp "s" permission means that the DBSNMP process will run with the root user's privileges. When this permission is set, the job is run by the user set up in the Preferredcredentials window in the OEM console. Verify that the user set up in the Preferredcredentials window of the OEM console has the appropriate logon rights on the server.

Q: Can customers create their own defined events?

A: In oem1.x, customers cannot create events of their own definition. This will be a new feature of oem2.x. However, you can create a job that runs a TCL script that triggers an event by using the TCL command orareportevent. For further information about Orareportevent, see the OEM Application developer manual

Q: On the console, the database appears as a red circle and slash, indicating that the database is closed, however, the database is running.

A: If the database, listener process or node appears as a red circle and Slash, the OEM console is trying to notify you that the service is off. If the service is not closed, you need to click "Outstandingeventstab" in the event window and move the notification to history, which should be derived from the

Navigation (navigator) and maps (map) window clear off prompt.

Q: How to create a oemrepository?

A:oemrepository is a set of tables in a Oracle7 or Oracle8 database that stores information that is graphically browsed through the OEM console. In the oem1.x structure, these tables are stored under a specific user and cannot be shared with another user. In oem1.2.x, you should run the script smpcre.sql with a non-"system" user login, which must have Connect,resource and DBA authority. In oem1.3.x, repository is automatically created when the OEM console icon is first activated. If an earlier version of repository already exists, you are prompted to update the table, or you will be prompted to create the table if there are no OEM tables.

Q: How do I customize the OEM toolbar?

A: If you want to set the OEM toolbar, press the right button on the toolbar; Select Customizetab. You can edit the name of the toolbar item, delete the item, or add the item. If you click on the Databasetab, you can go to logoncredentials and select a default value entry for each database.

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

Voc-00002:failuretoobtaininterfacelogin

A: The reason is that the OEM communications background process cannot open a connection to the repository.

Verify that TCP/IP is configured correctly and that the default parameters for the communication background process have been modified (using Daemonmanager).

Q: When using the OEM console, you receive the following error message:

Voc-00107:failuresettingcredentialdetailsora-03114:not connected to ORACLE

A: The reason is that the oemrepository database is shut down or the service that is connecting to the database has a network failure.

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

Voc-00121:failureupdatingorinsertingauserdetailentry

Ora-00942:tableorviewdoesnotexist

A: The default role for users to log on to the OEM console is normal, and if you need to connect as a SYSDBA, you should set the CONNECTASSYSDBA option in the Preferredcredentials window.