Summary of Oracle Database installation essentials

1.
Build Library UseAdmin Managedusing policy managed occurs when the instance name of Node 1 is sid_2 in a RAC environment

2.
Some minor patches if you create a database without using custom, you will need to manually upgrade the data dictionary of the database after you create it.


3.
Data files are stored in separate file systems (using ZFS separate mount points in Solaris). Do not put in the default database file storage location, or later in the database upgrade, using the tar command to back up the database software is a bit of trouble.

4.
Redo size, consider the size of the business volume.
According to the database size, communicate with the demand side to determine the size of the redo.
Too big will appear for a long time without switching problems, too small and will switch frequently.

In the case of an archive, the 5th Log group is generally enabled to prevent the database from frequently causing it to not work properly

5.
The processes parameter setting is as large as possible.
Some development departments use the connection pooling capabilities of the middleware, and many developers turn on a lot of middleware, which can lead to a shortage of connections.

6.
SGA+PGA generally do not exceed 50% of system memory, database other processes and EM, and the system needs to consume a certain amount of memory resources. Need to communicate with customers.

7.
Fast recovery directory is not enabled, and there is often a lack of directory size, which prevents the database from starting properly.


8.
Once the repository is complete, check to see if the other directories are of the Oracle (backup/archive directory).

9.
Password Expiration issues

.
General enable EM tool

One by one .
Installing the database software and clustering software requires the latest PSU patches, as well as some frequently used patches.

Patched according to Oracle Recommended patches-Oracle Database (document ID 756671.1).

.
In addition to creating disk groups on your own, be aware of capmpatible, and it's best to stay up to date. COMPATIBLE. ASM and Compatible.rdbms control ASM and Oracle instances can use the oldest version of this disk group. The new features of many disk groups depend on this parameter. COMPATIBLE. RDBMS corresponds to the compatible parameter of the database and should ensure that the compatible parameter of the database is newer than the Compatible.rdbms attribute of DiskGroup. Modification method:
alter DiskGroup DG2 set attribute ' compatible.asm ' = ' 11.1 ';
alter DiskGroup DG2 set attribute ' Compatible.rdbms ' = ' 11.1 ';

.
cve-2012-1675 is a vulnerability to listener,scan_listener that can be registered to a database by configuring local and allowed IP snooping. Prevent hackers from intercepting data through other IPs that are controlled.

The database version is available in 11.2.0.4 and above and can be resolved using the newly added VNCR feature.
The description of the function and the test document are shown below:
Http://bbs.dc.com/forum.php?mod= ... &extra=page%3d1

.
to prevent bug 12311429, execute after the database is created in a RAC environment:
1. Check the snapshot controlfile location:
rman> Show snapshot controlfile name;
2. Configure the snapshot controlfile to a shared disk:
rman> CONFIGURE SNAPSHOT controlfile NAME to ' <shared_disk>/snapcf_<dbname>.f ';
Or in case of ASM use
rman> CONFIGURE SNAPSHOT controlfile NAME to ' +<diskgroup>/snapcf_<dbname>.f ';
detailed documentation is provided in the following link:
Https://support.oracle.com/epmos ... 331556786298562#ref
The bug is simple: Because of the hot backup, the database is in the open state, when backing up the current controlfile, the database if there is controlfile write operation, will use to snapshot controlfile situation appears. If snapshot controlfile is placed on another node, it may be an error. So here you modify the snapshot control to the shared disk/file system to prevent this from happening. Modify configuration Snapshot Controlfile will not be created immediately, remember to use the backup current Controlfile test, so you can use Asmcmd in the corresponding directory to see the file generation, and finally need to delete the test using the backup Controlfile.


A .
because of the recent frequent Ora-12592:tns:bad packet This problem, so each installation of the database need to break into the patch 18841764

.
OLTP-type application customers do not have special requirements when the RAC environment is best to create a service for each instance, the other node is a standby node. It facilitates business separation, reduces the load on the heartbeat line, and increases efficiency.

Summary of Oracle Database installation essentials