Oracle 10g Enterprise Manager CLI 官方文档简介

需积分: 10 110 浏览量更新于2024-08-02 收藏 1.05MB PDF 举报

"Oracle 10G Enterprise Manager Command Line Interface 官方文档" Oracle 10G Enterprise Manager Command Line Interface (EM CLI) 是一个强大的工具，允许管理员通过命令行方式管理 Oracle 数据库环境，提供了与图形界面 Enterprise Manager 相同的功能，但更适用于自动化任务和脚本编写。这个文档是 10g Release 5 (10.2.0.5) 版本，发布于2009年8月，主要作者是 Michael Zampiceni。在文档中，你会了解到如何使用 EM CLI 来执行各种数据库管理和维护任务，包括但不限于： 1. **数据库实例管理**：启动、停止和监控数据库实例，以及进行故障排除。 2. **性能监控**：收集和分析性能数据，如 SQL 语句的执行情况、系统资源利用率等。 3. **备份与恢复**：创建和管理备份策略，执行数据恢复操作。 4. **安全管理**：管理用户权限，设置角色，更新口令，以及审计安全事件。 5. **数据库配置**：修改数据库参数，创建和删除表空间，管理控制文件等。 6. **数据泵导出导入**：利用 EXPDP 和 IMPDP 命令进行数据迁移和数据集成。 7. **集群管理**：在集群环境中配置和管理数据库实例。 8. **自动任务调度**：使用 DBMS_JOB 或 DBMS_SCHEDULER 创建和管理计划任务。 9. **数据库升级与迁移**：协助数据库版本升级或迁移至其他硬件或平台。 10. **告警与通知**：配置告警规则，接收和管理系统告警，实现问题自动化响应。文档可能还会包含以下内容： - **安装与配置**：介绍如何安装和配置 EM CLI，包括依赖组件和环境设置。 - **命令语法与示例**：提供详细的命令语法说明，以及实用的示例来演示如何执行常见任务。 - **错误处理与诊断**：列出可能遇到的问题及解决方法，帮助管理员快速定位和解决问题。 - **性能优化建议**：指导如何调整数据库配置以提升性能。 - **接口集成**：解释如何将 EM CLI 集成到其他自动化工具或流程中。 Oracle 对其软件及其文档拥有知识产权，未经授权，禁止非法复制、修改或分发。同时，该软件可能受到美国政府的出口管制，使用时需遵守相关法规。 Oracle 10G EM CLI 的优势在于其灵活性和可扩展性，它使得数据库管理更加高效，特别是在需要批量操作或集成到现有运维流程时。通过熟练掌握 EM CLI，IT 专业人员能够更有效地维护和优化 Oracle 数据库环境。

EM CLI Quick Start

1-6 Command Line Interface

1.4.2.4 Using EM CLI Log Files

EM CLI creates log files to record informational and error messages generated during

operation. Not all of the logs in the following examples are necessarily present. Logs

are created as needed and are append-based — they are preserved between

invocations of EM CLI. You can safely delete log files any time without affecting

EM CLI operation. The logs contain stack traces, which may not be useful for the

casual user, but may benefit you with a high level of system knowledge.

The following examples show possible log file locations:

CONFIG_DIR/.emcli.log

CONFIG_DIR/.emcli.log.1

CONFIG_DIR refers to the directory specified by the -dir option in the latest running

of the setup Verb (with an appended .emcli subdirectory). The current

CONFIG_DIR directory can be identified by executing the setup Verb with no options

to display the setup summary.

Log files are limited to a maximum of 0.5 MB. EM CLI alternates between the two log

files — as each file reaches the 0.5 MB limit, EM CLI begins writing to the other file,

overwriting the oldest log file after emcli.log.1 has been filled for the first time.

The following examples show possible log file locations:

Example 1–1 No configuration directory is specified with the setup Verb (Default

location)

user.home/.emcli/.emcli.log

user.home/.emcli/.emcli.log.1

If you do not specify a configuration directory when you run the setup Verb (-dir

option is omitted), EM CLI assumes the .emcli configuration directory is located

within the your local home directory. The log files are placed at the root level of the

.emcli directory. The .emcli directory must be local (not mounted remotely).

Example 1–2 Local configuration directory is specified with the setup Verb (-dir=<local

directory>

local.dir/.emcli/.emcli.log

local.dir/.emcli/.emcli.log.1

In this example, the configuration directory is specified using the -dir option when

the setup Verb is run. This allows you to specify a local configuration directory if the

user home directory is mounted remotely (through NFS, for example).

1.4.2.5 Configuring an HTTP Proxy Environment

If you are planning to use EM CLI through an HTTP proxy server, you need to set an

additional environment variable (EMCLI_OPTS) that supplies EM CLI with the

requisite proxy host and port information. The following examples illustrate setting

Tip: For complete information on the Setup verb and its options,

including

ssousername

ssopassword

noautologin

, and

custom_attrib_file

referenced in step 2, see the setup Verb on

page 2-207.

To configure the EM CLI Client to function with multiple OMSes by

implementing multiple setups, see the Examples section for the Setup

verb.

Security and Authentication

1-8 Command Line Interface

1.5.1 HTTPS Trusted Certificate Management

For authenticating an OMS during the SSL server authentication phase of an HTTPS

connection handshake, EM CLI searches for trusted certificates in the following key

stores:

CONFIG_DIR/.emcli/.localkeystore

user.home/.emcli/.keystore

JRE_HOME/lib/security/cacerts

CONFIG_DIR is the directory specified by the -dir option in the latest running of the

setup Verb (with an appended .emcli subdirectory). See "Using EM CLI Log Files"

on page 1-6 for more information about the CONFIG_DIR parameter.

JRE_HOME in a JDK installation is typically JAVA_HOME/jre.

The JDK keytool command can manage the key stores. For more information about

this tool, see the security documentation for your Java VM installation, or at the time

of this writing:

http://java.sun.com/j2se/1.5.0/docs/tooldocs/solaris/

keytool.html

Not all of the key stores in the list above will necessarily be present.

1.5.2 Secure Clients

You can provide credentials to EM CLI in one of two ways:

■ Provide credentials at the time of use. See the login and logout verbs for

information on credentials.

■ Make credentials persistent on the host system where the EM CLI client is

running, as might be the case when executing EM CLI verbs from a shell script.

1.5.3 Secure Mode for the EM CLI Setup

The EM CLI client installs certain configuration files and a client-side implementation

of verbs on the client system. The EM CLI client configuration files contain

information such as OMS URL, Enterprise Manager user name, Enterprise Manager

password, and SSO user name and password (if EM is SSO-enabled). The default

mode stores these credentials, which is inherently insecure because of backward

compatibility reasons.

To eliminate this security risk, a secure mode EM CLI setup does not store any EM or

SSO passwords on the client disk. For a secure setup, you need to specify the

noautologin

option for the Setup verb. You provide the credentials once during setup,

after which a session is established between the client and OMS. All subsequent verbs

use this session. Inactivity or an explicit logout (using the Logout verb) terminates this

session, and a re-setup or an explicit login (using the Login verb) is required before

invoking any new verb.

Caution: You should only make credentials persistent on hosts when

the host is a secure client, since the only protection available for

credentials is the file-system security of the OS.

Oracle also recommends not using persistent credentials if the EM CLI

user’s home directory is mounted over NFS or any other insecure file

system.

Script Availability for Output Data Verbs

Command Line Interface Concepts and Installation 1-9

■ For information on the

noautologin

option, see the setup verb on page 2-207.

■ For information on logging in, see the login verb on page 2-150.

■ For information on logging out, see the logout verb on page 2-152.

1.6 Script Availability for Output Data Verbs

For easy parsing of Verb output by scripts, a –script argument is available for all

verbs that generate output data. If the -script argument is used, all output columns

become tab-separated (with non-null values), and all rows become newline-separated.

You can override the default column and row separators by using the -format

argument in place of -script.

[-script|-format="name:<format type>;column_

separator:<separator_text>;row_separator:<separator_text>"]

Supported -format arguments are shown in Table 1–1.

■ -script is equivalent to –format="name:script;column_

separator:\u0009;row_separator:\u000A"

■ The values for column and row separator are given as one or more character

strings. Any of the characters can be represented by the unicode sequence \uXXXX

(where X is a hex value).

NOTE: The ASCII character set is represented by \u00XX, where XX can range

from 00 to 7F. For example, the tab character is represented by \u0009 and the

newline character is represented by \u000A.

■ The pretty format type has no attributes.

Table 1–1 Supported "-format" Arguments

Argument Explanation

-format="name:pretty" Pretty-print the output. This is

the default when both -script

and -format are not specified.

-format="name:script" Identical to just specifying

–script. Columns are

tab-separated, and rows are

newline- separated.

-format="name:script;column_

separator:<column_sep_string>"

Causes the Verb output to be

column-separated by <column_

sep_string>. Rows are

separated by the newline

character.

-format="name:script;row_separator:<row_sep_

string>"

Causes the Verb output to be

row-separated by <row_sep_

string>. Columns are

separated by the tab character.

-format="name:script;column_

separator:<column_sep_string>;row_

separator:<row_sep_string>"

Causes the Verb output to be

column-separated by <column_

sep_string> and row-

separated by <row_sep_

string>.

-format="name:csv" Produces a table with the

columns separated by commas

and the rows by newlines.

剩余295页未读，继续阅读

highlyjing

粉丝: 7
资源: 26

Oracle 10g Enterprise Manager CLI 官方文档简介

官方资料：[英文]Oracle Data Guard Concepts and Administration 11g(11.2).pdf

ORACLE RMAN

oracleasm RPM包

oracle备份、恢复.docx

最完整的Toad For Oracle使用手册

Oracle Enterprise Manager CLI 深入指南

Oracle Enterprise Manager 12c CLI：自动化与数据库管理的艺术（2014）

DataGuardbroker：简化Oracle数据保护的集中管理平台

Oracle RAC数据库的安装与配置

Oracle远程数据库数据传输：高效与可靠的解决方案

最新资源