Use Resource Manager to optimize Oracle Performance

1. Operating System Optimization

1) Concept

Factors that should be taken into account during operating system optimization include memory usage, Cpu usage, IO level, and network traffic. Each factor affects each other. The correct order of optimization is memory, IO, and CPU.

The operating system uses the Virtual Memory concept. The virtual memory makes each application feel that they are the only application that uses the memory. Each application sees a separate piece of memory starting from 0, the virtual memory is divided into 4 K or 8 K pages. The operating system maps these pages to the physical memory through MMU (memory management unit). This ing relationship is controlled through the page table.

Raw device is a disk or disk partition without a file or directory structure. because it ignores the operating system cache, it can significantly improve Oracle performance in some cases, but in windows NT, because operating system IO operations do not use file system cache, raw device cannot display performance advantages.

2) Guideline

The maximum CPU usage is 90%;

OS/USER process count: 40/60;

The load of each CPU should be roughly balanced.

3) server security check

A. Check the UNIX System User Password

Check:/etc/passwd,/etc/shadow. the UNIX Password uses the shadow mechanism to ensure high security.

Suggestion: modify some settings of the/etc/default/passwd file by referring to the UNIX Command passwd, such as MAXWEEKS, MINWEEKS, and PASSLENGTH to rationalize the password modification.

Suggestion: regularly change the following user passwords for UNIX systems: root, oraprod, applprod, and appprod.

B. Check Remote Login

Started rlogin, server database a, database B, database c, terminal le1, le2, le3, and T3 to form a highly trusted relationship, you only need to have the super permissions of a server to rlogin. no Password is required for any host specified by rhosts.

Suggestion: very insecure. Refer to the file. rhosts in the UNIX Command rlogin and/directory. Do not establish this remote trust mechanism between the formal environment server and the test environment server.

C. Check the FTP service

Check the user (/etc/ftpusers) who can FTP to the server and comment out the root user, that is, the user can use the root permission to FTP to the server. The permission is too large.

Suggestion: remove the root annotator (#) from/etc/ftpusers and add users such as oraprod, applprod, and appprod to the list to prevent the FTP server from being used. If necessary (such as when uploading a PATCH), open the FTP permission of applprod.

D. Suggestion: the UNIX System Administrator regularly checks messages, sulog,/etc/syslog. conf, and other information under/var/adm. Check whether there are illegal users logging on to UNIX. Suggestion: Better monitoring methods with UNIX engineers

4) database and application product security check

A. Suggestion: Modify the. profile file under the root directory of the oracle user and set the File Permission to 500. Even if the user does not execute the environment variables related to the database or application during login, this increases security and Oracle performance.

B. Check the password of the database DBA and the password of the application SYSTEM user: the password of SYSTEM and APPS has been changed, and the password of SYS or the initial installation password Change_on_install

Suggestion: Change the SYS user password immediately and change the passwords of APPS, SYSTEM, and SYS on a regular basis.

C. Regularly check and clear the alert_PROD.log file and background process trace file under the $ ORACLE_HOME/admin/bdump directory. Regularly clear the trc files in the $ ORACLE_HOME/admin/udump directory.

D. Suggestion: Set the Password Expiration limit for users logging on to the application product, for example, the password access limit or the time (days) limit.

Suggestion: do not share the user name and password of an application product. Each user is assigned an application product user name.

Suggestion: it is not suitable for users with application system administrator permissions to revoke and manage permissions in a unified manner.

E. Regularly check and clear the log files related to the Apache Server. The directory is:

/U01/prodora/iAS/Apache/logs/acccess_log, error_log

/U01/prodora/iAS/Apache/Jserv/logs/jserv. log, mod_jserv.log

F. Regularly check and clear the listener and tnsname log files. The files are stored in:

/U01/prodora/8.0.6/network/admin/pai_prod.log,

/U01/proddb/8.1.7/network/admin/prod. log

/U01/proddb/8.1.7/network/log/listener. log, sqlnet. log...

G. Multiple images of the Database Control file are placed on multiple disks to improve security.

5) network security check

Check the $ ORACLE_HOME/dbs/initPROD. ora file.

# Remote_login_passwordfile = EXCLUSIVE

Set to REMOTE_LOGIN_PASSWORDFILE = NONE. Remote users are not allowed to log on using INTERNAL.

2. Resource Manager)

You can use the resource manager to manage hybrid workloads and control Oracle system performance. The Database Resource Manager includes:

• Resource plans: including resource plan ctictives, which specifies the resources allocated to each resource consumer group.

• Resource consumer groups: defines a group of users with similar Resource usage requirements.

• Resource plan directives: Specify resource plans for consumer groups or subplans, and allocate resources for each consumer groups or subplans of the Resource plan.

　

1. Prospective role in Oracle Database Maintenance
2. Rollback Segment optimization for Oracle Performance Optimization
3. Introduction to Oracle database development experience
4. Effect of disk sorting on Oracle database performance (1)
5. Manage Oracle constraints and partition tables (1)