Oracle 10g在Red Hat Enterprise Linux 5部署指南（V1.2）

需积分: 9 180 浏览量更新于2024-07-19 收藏 1.35MB PDF 举报

身份认证购VIP最低享 7 折!

30元优惠券

Oracle 10g Server on Red Hat Deployment Recommendations Version 1.2是针对Oracle 10g数据库在Red Hat Enterprise Linux 5平台上的部署建议文档，发布于2008年11月。这份文档由Red Hat Inc.提供，包含了关于如何优化安装、配置和管理Oracle 10g服务器在Red Hat Enterprise Linux环境中的详细指导。在本指南中，读者可以找到关于以下关键知识点： 1. **兼容性确认**：文档确认了Oracle 10g Server与Red Hat Enterprise Linux 5版本的兼容性，确保用户可以在最新的操作系统上运行Oracle数据库服务。 2. **系统准备**：涵盖了硬件和软件需求，包括内存、CPU、存储和网络要求，以及操作系统的基本配置设置，如安装Oracle所需的依赖库和工具。 3. **安装过程**：详细步骤指导如何通过Red Hat Package Manager (RPM)或源代码编译安装Oracle 10g，包括初始化参数调整和数据库实例创建。 4. **安全性考虑**：涉及数据库防火墙规则、账户权限管理和审计策略，强调了数据安全和隐私保护的重要性。 5. **集群部署**：对于多节点Oracle RAC（Real Application Clusters）环境的部署建议，包括网格基础设施（Grid Infrastructure）和资源适配器的配置。 6. **备份和恢复**：文档可能包含备份策略、归档模式的使用，以及如何执行故障恢复操作。 7. **性能调优**：提供了一些关于数据库性能优化的建议，如索引管理、SQL查询优化和资源调度策略。 8. **监控和维护**：介绍了如何使用Oracle Enterprise Manager和第三方工具进行日常监控，以及定期维护任务的建议。 9. **许可证和法律注意事项**：提醒读者关于Oracle许可协议的要求，以及关于文档分发和修改的Open Publication License规定。 10. **版权和商标声明**：强调了Red Hat、Linux、Red Hat Linux Shadowman标志以及相关的商标所有权，同时也指明了对其他商标所有者的尊重。这份文档为Red Hat Enterprise Linux 5上的Oracle 10g Server部署提供了全面的指南，旨在帮助用户高效、安全地实施和运维Oracle数据库系统。随着技术的更新，部分内容可能已经过时，但基本的部署流程和最佳实践仍具有参考价值。

资源详情

资源推荐

the noop scheduler for device /dev/sdd and verify the result:

# echo noop > /sys/block/sdd/queue/scheduler

# cat /sys/block/sdd/queue/scheduler

[noop] anticipatory deadline cfq

RHEL5 Running as a VMware Guest

By default, the timer interrupt (tick) rate in Red Hat Enterprise Linux 4 and 5 is 1000 Hz. In some situations,

this rate is too high, with frequent interrupts potentially causing a performance impact or unexpected behavior.

This impact would be most notable when running Red Hat Enterprise Linux as a virtual guest. For example,

with the 1000 Hz tick rate, time drift might be observed in a virtual environment.

To compensate for the fact that different workloads and different environments work better with different tick

rates, a new kernel parameter was added to Red Hat Enterprise Linux 5.1 and 4.7. This kernel parameter, "di-

vider", is a boot-time setting that allows the user to divide the tick rate by the desired amount. For example, set-

ting the divider to 10 would cause the default tick rate to be 1000/10, or 100 Hz.

The divider parameter can be set by appending "divider=N" to the kernel boot line in /boot/grub/grub.-

conf.

The recommended kernel line settings for 64-bit Red Hat Enterprise Linux 5 running as a VMware guest are:

divider=10 notsc iommu=soft elevator=noop

and for a 32-bit Red Hat Enterprise Linux 5 Vmware guest:

divider=10 clocksource=acpi_pm iommu=soft elevator=noop

Memory Usage and Page Cache

Checking Memory Usage

To determine the size and usage of memory, you can enter the following command:

$ grep MemTotal /proc/meminfo

Alternatively, you can use the free(1) command to check the memory:

$ free

total used free shared buffers cached

Mem: 4040360 4012200 28160 0 176628 3571348

-/+ buffers/cache: 264224 3776136

Swap: 4200956 12184 4188772

In this example the total amount of available memory is 4040360 KB. 264224 KB are used by processes and

www.redhat.com | 9

3776136 KB are free for other applications. Don't get confused by the first line which shows that 28160KB are

free! Note that most of the memory used is for buffers and cache since Linux always tries to use RAM to the

fullest extent to speed up disk operations. Using available memory for buffers (file system metadata) and cache

(pages containing contents of files or block devices) helps the system to run faster because disk information is

already in memory, thereby reducing I/O. If space is needed by programs or applications such as Oracle, then

Linux will free the necessary buffers and cache to yield memory for the applications. Typically, if the system

has been up for an extended period, a small number can be observed under the "free" column on the first line.

Tuning Page Cache

Page Cache is a disk cache which holds data of files and executable programs, e.g. pages with actual contents of

files or block devices. Page Cache (disk cache) is used to reduce the number of disk reads.

The Page Cache in Red Hat Enterprise Linux 5 is dynamically adjusted. You can adjust the minimum free

pages using

# echo 1024 > /proc/sys/vm/min_free_kbytes

Again to make the change permanent, add the following line to the file /etc/sysctl.conf:

# echo vm.min_free_kbytes=1024 >> /etc/sysctl.conf

The easiest way to tune when to start reclaiming Page Cache pages is to adjust the swappiness percentage. The

default value of /proc/sys/vm/swappiness is 60 which means that applications that are not actively oc-

cupying CPU cycles can be swapped out. Higher values will provide more I/O cache and lower values will wait

longer to swap out idle applications.

In general, swapping out unused pages allows thesystem to be more efficient but it is not always good for

database servers. An Oracle database server typically uses a big cache of its own, in which case swapping pages

may be detrimental. The optimal solution for Oracle database servers is to configure Linux Huge Pages and al-

low Oracle processes to use them for internal caching. Huge pages are not used as a system Page Cache so

Linux and Oracle caching algorithms do not interfere.

Linux usually flushes the page cache using pdflush kernel threads. At any given time, 2 to 8 pdflush threads are

running on the system. You can monitor active threads by monitoring

/proc/sys/vm/nr_pdflush_threads. Whenever all existing pdflush threads are busy for at least one

second, an additional pdflush thread is spawned. The new ones try to write back data to device queues that are

not congested, the goal being each active device has its own thread flushing data to that device. Each time a sec-

ond has passed without any pdflush activity, one of the threads is removed.

Exactly what each pdflush thread does is controlled by a series of parameters in /proc/sys/vm:

dirty_writeback_centisecs (default 500): In hundredths of second, this is how often pdflush wakes up to write

data to disk. The default wakes up pdflush every five seconds.

It may be beneficial to decrease this parameter on systems with lots of memory and active writing processes.

The smaller value will make pdflush threads more aggressive in cleaning dirty pages. The kernel implements

some rules to prevent write congestion. It limits the number of pages that can be flushed at once and may skip

one second between pdflush activations if the threads are too busy. It does not make sense to set this parameter

10 | www.redhat.com

剩余49页未读，继续阅读

粉丝: 44
资源: 2

Oracle 10g在Red Hat Enterprise Linux 5部署指南（V1.2）

Oracle_OSB的安装与配置

oracle osb

ORACLE OSB开发指南

Oracle linux

Artifact test1:war: Error during artifact deployment. See server log for details.

Artifact SchedulingSystem:war exploded: Waiting for server connection to start artifact deployment...

WARNING: This is a development server. Do not use it in a production deployment. falsk WSGI

OCP deployment does not have minimum availability

Artifact shiro_demo01:war: Error during artifact deployment. See server log for details.

This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.这个怎么解决

WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.

Error during artifact deployment. See server log for details

war exploded: Error during artifact deployment. See server log for details.

Artifact ekp:war exploded: Error during artifact deployment. See server log for details.

kubectl get deployment 中deployment 缩写是什么

k8s部署canal-server

TomEE required to support EAR/EJB deployment

Error during artifact deployment. See server log for details.

docker报错This is a development server. Do not use it in a production deployment. Use a production WSGI server instead怎么解决

OSB 开发教程

最新资源