Windows2003中，em的主机身份验证无法通过

解决方法：
设置 --> 控制面板 --> 管理工具 -->

本地安全策略 --> 本地策略 --> 用户权利指派

--> 作为批处理作业登录(最下面一项) --> 添加你的帐号

注意：
使用Administrator登录操作或具有相同权限。
用户口令不能是空，是空的话一样会报错。

这个问题其实在metalink中也有解释,只是我们很少注意

Goal:
Quick Start Guide: How to Configure Enterprise Manager 9i
Environment:
Oracle Enterprise Manager 9i
Oracle Management Server 9i
Oracle Intelligent Agent 9i
Enterprise Manager Repository
Fix:
How to configure Enterprise Manager 9i when using a three-tier architecture (EM CONSOLE -> MANAGEMENT SERVER -> INTELLIGENT AGENT).
For ease of setup, each tier should each be configured and verified before moving to the next tier. To facilitate this building process, set up the tiers third-tier through first-tier.

 

A. Configure the Target Nodes (Third-Tier):
To manage nodes and other Oracle services on those nodes, an Intelligent Agent must be configured and running on the node. The Intelligent Agent is installed from the Oracle Server CD. For details on installing an Intelligent Agent, consult your Oracle Server installation Guide or the Intelligent Agent Users Guide.

If the managed node is a Windows NT/2000 system:
Start the Intelligent Agent (As a default, the Agent is started automatically.)
Setup a Windows Admin user with "Logon as Batch Job" privilege
1. Start the Intelligent Agent:
To start the Intelligent Agent on Windows NT, perform the following steps:
a. Double-click the Services icon in the Control Panel folder.
b. Select the Oracle<oracle home>Agent service.
c. Click the Start push-button to start the agent.
To stop the agent on Windows NT, perform the following steps:
a. Double-click the Services icon in the Control Panel folder.
b. Select the Oracle<oracle home>Agent service.
c. Click the Stop push-button to stop the agent.
To verify the agent is running, perform any combination of the following:
a. Check the status of Oracle<oracle home>Agent in the control panel services
b. Verify the process dbsnmp.exe is running in the NT Task Manager
c. Type NET START at a command prompt. Oracle<oracle home>Agent should appear in the list of services.
2. Set Up a Windows NT User Account for Running Jobs / Events

 

If the managed Node is a UNIX system:
Verify the post-installation script (root.sh) has been ran
Verify permissions on the Intelligent Agent (dbsnmp) executable
Start the Intelligent Agent
1. Run root.sh:
The root.sh script must be ran after each Oracle installation. This script sets the permissions on the Intelligent Agent's executable (dbsnmp). The script will also create/update the oratab file which is used by the Intelligent Agent to determine all the databases discoverable on the system. For each database created, the entry is of the form:
<SID>:<$ORACLE_HOME>:[Y/N]
Verify the oratab file lists each database on the system and follows the correct syntax listed above. The root.sh shell script should have written values of the Oracle Homes and SIDs. If there are no entries in the oratab file, perform the following steps:
> su root
> $ORACLE_HOME/orainst
> ./root.sh
Answer the questions asked. For each database created, the entry is of the form: <SID>:<$ORACLE_HOME>:[Y/N]
You will then be automatically exited out of root.sh.
The agent is normally configured by root.sh as a setuid program. If root.sh was successful, the agent will have been installed as "setuid root" so the agent can run jobs as the user whose name and password are given in the EM Console's Preferred Credentials for that node (server).
2. Check file permissions on dbsnmp:
To verify that root.sh had been run successfully, check the file permissions on dbsnmp:
> cd $ORACLE_HOME/bin
List all relevant details about dbsnmp:
> ls -al dbsnmp
The output of the ls -al command for dbsnmp should be in the form:
-rwsr-xr-x 1 root dba 1497980 Jun 12 21:04 dbsnmp
In this example, root is the owner and the group is dba. The first 10 characters (-rwxr-xr-x) represent the level of permissions set on the executable. The first 4 character (-rws) represents the owners permissions.
For example, the owner has (r)read, (w)write, and (s)setuid on execute. The next 3 characters (r-x) represent the groups permissions. For example, (r)read, (x)execute. Group does not have write permissions. The last 3 characters (r-x) represents the permissions of everyone else or "world". If root is the owner and -rwsr-xr-x are the permissions, then root.sh has been ran successfully.
3. Start the Intelligent Agent on Unix:
On UNIX, the 9i Intelligent Agent uses the "agentctl" utility to start and stop the dbsnmp process. The commands to control the agent are:
agentctl start = To Start the agent on UNIX platform
agentctl stop = To Stop the agent on the UNIX platform
agentctl status = To verify status of the agent

 

B. Configure the OMS and EM REPOSITORY (Middle Tier)
Checklist -
Run the Enterprise Manager Configuration Assistant and upgrade / create a new EM Repository.
Start the Oracle Management Server.

1. Create the EM Repository
How to Configure the Enterprise Manager 9i Management Server and EM Repository, Note 165048.1
2. If not already started, you will need to start the Oracle Management Server (OMS):
To start the OMS on Windows NT, perform the following steps:
a. Double-click the Services icon in the Control Panel folder
b. Select the Oracle<Oracle_Home>ManagementServer service
c. Click the Start push-button to start the OMS
On Solaris:
oemctl start oms
If the OMS fails to start, consult the oms.log file found in the $ORACLE_HOME/sysman/log directory for further information. With the Solaris release of EM 9i, the log file is called oms.nohup.

 

C. Configuring the EM Console (First-Tier):
Checklist -
Start the EM Console
Discover Managed Nodes and their Managed Services
Set Preferred Logon Credentials
Test the Job System
1. Start the EM Console:
To launch the console, on Windows NT:
Click Start => Programs => Oracle<oracle home> => Enterprise Manager Console
or from a command prompt, type:
oemapp console
On Solaris, type:
oemapp console

The default EM logon is:
Username=sysman
Password=oem_temp
After entering the default logon, you will be forced to change the initial password - REMEMBER IT!
After logging on, additional EM users can be setup. These users are known only to the EM console/OMS. They are not database accounts but simply users stored in a table in the EM Repository.