Administrando Oracle en AIX

File System Opción Descripción
JFS2 cio Concurrent Input-Output es un mejor parámetro que Direct Input-Output sobre JFS2, porque este provee soporte para multiples lecturas y escrituras concurrentes en un mismo archivo. Sin embargo, debido a las restricciones de AIX sobre JFS2/CIO, el Concurrent Input-Output está destinado para ser usado solo con los Oracle data files, control files, y log files. It should be applied only to file systems that are dedicated to such a purpose. For the same reason, the Oracle home directory is not supported on a JFS2 file system mounted with the cio option. For example, during installation, if you inadvertently specify that the Oracle home directory is on a JFS2 file system mounted with the CIO option, then while trying to relink Oracle, you may encounter the following error:

“ld: 0711-866 INTERNAL ERROR: Output symbol table size miscalculated”

If you are placing Oracle Database logs on a JFS2 file system, then the optimal configuration is to create the file system using the agblksize=512 option and to mount it with the cio option.

Before Oracle Database 11g, Direct Input-Output and Concurrent Input-Output could not be enabled at the file level on JFS/JFS2. Therefore, the Oracle home directory and data files had to be placed in separate file systems for optimal performance. The Oracle home directory was placed on a file system mounted with default options, with the data files and logs on file systems mounted using the dio or cio options.

With Oracle Database 11g, you can enable Direct Input-Output and Concurrent Input-Output on JFS/JFS2 at the file level. You can do this by setting the FILESYSTEMIO_OPTIONS parameter in the server parameter file to setall or directIO. This enables Concurrent Input-Output on JFS2 and Direct Input-Output on JFS for all data file Input-Output. Because the directIO setting disables asynchronous Input-Output it should normally not be used. As a result of this 11g feature, you can place data files on the same JFS/JFS2 file system as the Oracle home directory and still use Direct Input-Output or Concurrent Input-Output for improved performance. As mentioned earlier, you should still place Oracle Database logs on a separate JFS2 file system for optimal performance.

Parámetros Sistema Operativo

Se debe reiniciar el servidor despues de aplicar estos ajustes.
vmo -p -o strict_maxperm=0
vmo -p -o strict_maxclient=1
vmo -p -o lru_file_repage=0
vmo -p -o maxperm%=90
vmo -p -o minperm%=5
vmo -p -o v_pinshm=1
vmo -p -o maxpin%=54
ioo -p -o pv_min_pbuf=768
chdev -l sys0 -P -a maxuproc=16384
chdev -l aio0 -P -a maxreqs='16384'
 

Crear Usuario Oracle

mkgroup oinstall
useradd -c "Oracle User"     -g oinstall -m -d /home/oracle -s /usr/bin/bash oracle

Agregar parametros limitantes para el usuario oracle en el archivo /etc/security/limits. Esto es para que pueda transferir archivos mayores a 1GB

oracle:
        fsize = -1
        data = -1
        stack = -1
        fsize_hard = -1
        cpu_hard = -1
        data_hard = -1
        stack_hard = -1
        core_hard = -1
        rss = -1
        nofiles = -1
  • Filesystem para REDOLOGS
JFS2
cio
agblksize=512