other backgroud process and alert log【每日一译】--2012-10-15

Other Background Processes
There are several other background processes that might be running. These can

include the following:

有几个其它后台进程可能在运行的，包含以下几种：

MMON performs various manageability-related background tasks, for example:
■ Issuing alerts whenever a given metrics violates its threshold value
■ Taking snapshots by spawning additional process (MMON slaves)

■ Capturing statistics value for SQL objects which have been recently modified

MMON执行多种相关管理的后台任务，比如：

#发出警报无论啥时候给定一个指标违反了阀值

#执行快照通过产生额外的进程（MMON子进程）

MMNL performs frequent and light-weight manageability-related tasks, such as

session history capture and metrics computation.

MMNL频繁执行轻量级的管理相关的任务，像会话历史捕捉和指标比较。

MMAN is used for internal database tasks.

MMAN用于数据库内部的任务。

RBAL coordinates rebalance activity for disk groups in an Automatic Storage
Management instance. It performs a global open on Automatic Storage Management

disks.

RBAL协助重新平衡磁盘组的活动在一个ASM实例里。它执行一个全球性的开放在ASM磁盘上。

ORBn performs the actual rebalance data extent movements in an Automatic Storage
Management instance. There can be many of these at a time, called ORB0, ORB1, and
so forth.

ORBN执行实例的重平衡数据区的移动在ASM实例。在同一时间有许多这样的事件，

叫作ORB,ORB1等等。

OSMB is present in a database instance using an Automatic Storage Management disk
group. It communicates with the Automatic Storage Management instance.

OSMB出现在使用ASM磁盘组的数据库实例，它与ASM实例通信。

Trace Files and the Alert Log
Each server and background process can write to an associated trace file. When a
process detects an internal error, it dumps information about the error to its trace file.

每一个服务和后台进程可以写到一个相关的TRACE文件。当一个进程检测到一个内部

错误，它DUMP出关于ERROR的信息到它的TRACE文件。

If an internal error occurs and information is written to a trace file, the administrator
should contact Oracle Support Services.

如果一个内部错误发生和信息写入到一个TRACE文件，管理员将联系ORACLE支持服务。

All filenames of trace files associated with a background process contain the name of
the process that generated the trace file. The one exception to this is trace files
generated by job queue processes (Jnnn).

所有的TRACE文件的文件句与后台进程相关包含了进程的名字在创建的TRACE文件中，有

一个例外就是被对列进程创建TRACE文件。

Additional information in trace files can provide guidance for tuning applications or
an instance. Background processes always write this information to a trace file when
appropriate.

额外的信息在TRACE文件中可以提供向导对于调试应用或者是一个实例，在适当时候后台

进程通常写入信息到TRACE文件。

Each database also has an alert.log. The alert log of a database is a chronological log
of messages and errors, including the following:

每一个数据库有一个ALERT.LOG文件，数据库的告警日志是按日志的的时间先后顺序的信息

和错误，包含以下这些：

■ All internal errors (ORA-600), block corruption errors (ORA-1578), and deadlock
errors (ORA-60) that occur

所有的内部错误（ORA-600），块中断错误（ORA-1578),和死锁错误（ORA-60)发生

■ Administrative operations, such as the SQL statements CREATE/ALTER/DROP
DATABASE/TABLESPACE and the Enterprise Manager or SQL*Plus statements
STARTUP, SHUTDOWN, ARCHIVE LOG, and RECOVER

管理操作，像SQL语句CREATE/ALTER/DROP DATABASE/TABLESPACE 和企业管理器

或者SQL*PLUS语句启动，关闭，归档和恢复。

■ Several messages and errors relating to the functions of shared server and
dispatcher processes

对共享服务和调度进程有关的信息和错误的功能。

■ Errors during the automatic refresh of a materialized view

错误在自动刷新一个物化视图时。
Oracle uses the alert log to keep a record of these events as an alternative to displaying
the information on an operator’s console. (Many systems also display this information
on the console.) If an administrative operation is successful, a message is written in the
alert log as "completed" along with a time stamp.

ORACLE使用ALERT日志保存这些事件作为一个可选择的显示信息在操作者的控制台。

（非常多的信息也显示在控制台的信息）如果一个管理操作是成功，那么信息写入到

ALERT日志标记“COMPLETED”和一个时间戳。