Oracle Home

Aplicando Patch Set 10.2.0.5 (8202632) no Banco de Dados Oracle 10.2.0.1 non-RAC

Maycon Tomiasi — Mon, 14 May 2012 15:40:37 +0000

Este artigo tem como objetivo mostrar como aplicar o patch set 10.2.0.5 (patch 8202632) para o Banco de Dados 10.2.0.1.
Estou utilizando o Sistema Operacional Enterprise Linux 5.7 32 Bits, então devemos fazer o download do patch para o banco de dados Oracle deste sistema operacional.
OBS: Para fazer o download é necessário obter as credenciais do Suporte da Oracle.
Download do Patch 8202632

Download Patch Set 10.2.0.5

Após fazer o download do Patch em questão, basta descompactar o mesmo no servidor de Banco de Dados.
OBS: Sempre antes de aplicar o Patch no Banco de Dados, fazer o backup do seu Produto Oracle. Ao aplicar o mesmo, certificar se todos os serviços Oracle esteja baixados.

No caso, os serviços estão todos baixados (Listener, Banco de Dados, Enterprise Manager).

Vamos acessar o diretório do produto Oracle e vamos realizar o Backup do mesmo.

[oracle@serveroracle oraprd01]$ tar -zvcf backup_oracle_home.tar.gz app/
app/
app/oracle/
app/oracle/product/
.
.
.
app/oracle/scritps/backup/bkp_mensal.rcv
app/oracle/scritps/backup/bkp_manutencao_rman.sh
[oracle@serveroracle oraprd01]$ ls -l
total 646196
drwxrwxr-x 3 oracle dba           4096 Mar 29 11:10 app
-rw-r--r-- 1 oracle oinstall 661030969 Apr 17 16:03 backup_oracle_home.tar.gz
drwxrwxr-x 2 oracle dba          16384 Mar 13 15:17 lost+found
[oracle@serveroracle oraprd01]$

Vamos aplicar o Patch já descompactado no servidor.

[oracle@serveroracle ~]$ /orabackup/Disk1/./runInstaller
Starting Oracle Universal Installer...

Checking installer requirements...

Checking operating system version: must be redhat-3, SuSE-9, SuSE-10, redhat-4, redhat-5, redhat-6, UnitedLinux-1.0, asianux-1, asianux-2, asianux-3, enterprise-4, enterprise-5 or SuSE-11
                                      Passed

All installer requirements met.

Preparing to launch Oracle Universal Installer from /tmp/OraInstall2012-04-17_04-04-29PM. Please wait ...[oracle@serveroracle ~]$ Oracle Universal Installer, Version 10.2.0.5.0 Production
Copyright (C) 1999, 2010, Oracle. All rights reserved.

[oracle@serveroracle ~]$

Seguir as imagens abaixo para a instalação passo à passo do Patch.

Tela Inicial de Instalação do Patch Set 10.2.0.5

Instalar no atual Oracle Home.

Tela de Credenciais para o Suporte Oracle

Tela de Aviso das Credenciais do Suporte da Oracle

Tela de checagem dos Pré-Requisitos para a Instalação do Patch Set.

Tela do Sumário do Patch a ser Instalado.

Tela de Progresso de Instalação do Patch

Tela para rodar o Script para permissão do usuário "root". Copie o endereço e coloque num terminal com o usuário "root".

Com o usuário root, vamos executar o script da imagem acima.

[oracle@serveroracle ~]$ su -
Password:
[root@serveroracle ~]# /oraprd01/app/oracle/product/10.2.0/db_1/root.sh
Running Oracle 10g root.sh script...

The following environment variables are set as:
    ORACLE_OWNER= oracle
    ORACLE_HOME=  /oraprd01/app/oracle/product/10.2.0/db_1

Enter the full pathname of the local bin directory: [/usr/local/bin]:
The file "dbhome" already exists in /usr/local/bin.  Overwrite it? (y/n)
[n]: y
   Copying dbhome to /usr/local/bin ...
The file "oraenv" already exists in /usr/local/bin.  Overwrite it? (y/n)
[n]: y
   Copying oraenv to /usr/local/bin ...
The file "coraenv" already exists in /usr/local/bin.  Overwrite it? (y/n)
[n]: y
   Copying coraenv to /usr/local/bin ...

Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root.sh script.
Now product-specific root actions will be performed.
[root@serveroracle ~]# exit
logout
[oracle@serveroracle ~]$

Tela de finalização a instalação do Patch. Clique em Exit.

Tela de finalização de instalação do Patch.

Após executar o script da permissão do usuário “root”, com o usuário oracle, vamos iniciar os serviços do Banco de Dados Oracle.
OBS: Seguir o README.html do Patch para aplicar o mesmo.

[oracle@serveroracle ~]$ lsnrctl start

LSNRCTL for Linux: Version 10.2.0.5.0 - Production on 17-APR-2012 16:14:02

Copyright (c) 1991, 2010, Oracle.  All rights reserved.

Starting /oraprd01/app/oracle/product/10.2.0/db_1/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version 10.2.0.5.0 - Production
System parameter file is /oraprd01/app/oracle/product/10.2.0/db_1/network/admin/listener.ora
Log messages written to /oraprd01/app/oracle/product/10.2.0/db_1/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=serveroracle.localdomain)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC0)))

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=serveroracle.localdomain)(PORT=1521)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 10.2.0.5.0 - Production
Start Date                17-APR-2012 16:14:02
Uptime                    0 days 0 hr. 0 min. 0 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /oraprd01/app/oracle/product/10.2.0/db_1/network/admin/listener.ora
Listener Log File         /oraprd01/app/oracle/product/10.2.0/db_1/network/log/listener.log
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=serveroracle.localdomain)(PORT=1521)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC0)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
  Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "orcl" has 1 instance(s).
  Instance "orcl", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
[oracle@serveroracle ~]$ sqlplus sys/*********** as sysdba

SQL*Plus: Release 10.2.0.5.0 - Production on Tue Apr 17 16:16:09 2012

Copyright (c) 1982, 2010, Oracle.  All Rights Reserved.

Connected to an idle instance.

SQL> startup upgrade
ORACLE instance started.

Total System Global Area 1073741824 bytes
Fixed Size                  1277796 bytes
Variable Size             390070428 bytes
Database Buffers          679477248 bytes
Redo Buffers                2916352 bytes
Database mounted.
Database opened.
SQL>

Seguindo o documento do Patch, vamos aplicar o mesmo executando o primeiro script “utlu102i.sql” (Descreve a informação da Atualização).
OBS: Seguindo o Documento o mesmo solicita executar um spool para verificação após executar o script mencionado.

SQL> SPOOL upgrade_info.log
SQL> @$ORACLE_HOME/rdbms/admin/utlu102i.sql
Oracle Database 10.2 Upgrade Information Utility    04-17-2012 16:17:23
.
**********************************************************************
Database:
**********************************************************************
--> name:       ORCL
--> version:    10.2.0.1.0
--> compatible: 10.2.0.1.0
--> blocksize:  8192
.
**********************************************************************
Tablespaces: [make adjustments in the current environment]
**********************************************************************
--> SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 448 MB
.... AUTOEXTEND additional space required: 8 MB
--> UNDOTBS1 tablespace is adequate for the upgrade.
.... minimum required size: 402 MB
.... AUTOEXTEND additional space required: 102 MB
--> SYSAUX tablespace is adequate for the upgrade.
.... minimum required size: 206 MB
.... AUTOEXTEND additional space required: 6 MB
--> TEMP tablespace is adequate for the upgrade.
.... minimum required size: 58 MB
.... AUTOEXTEND additional space required: 38 MB
.
**********************************************************************
Update Parameters: [Update Oracle Database 10.2 init.ora or spfile]
**********************************************************************
-- No update parameter changes are required.
.
**********************************************************************
Renamed Parameters: [Update Oracle Database 10.2 init.ora or spfile]
**********************************************************************
-- No renamed parameters found. No changes are required.
.
**********************************************************************
Obsolete/Deprecated Parameters: [Update Oracle Database 10.2 init.ora or spfile]
**********************************************************************
-- No obsolete parameters found. No changes are required
.
**********************************************************************
Components: [The following database components will be upgraded or installed]
**********************************************************************
--> Oracle Catalog Views         [upgrade]  VALID
--> Oracle Packages and Types    [upgrade]  VALID
--> JServer JAVA Virtual Machine [upgrade]  VALID
--> Oracle XDK for Java          [upgrade]  VALID
--> Oracle Java Packages         [upgrade]  VALID
--> Oracle XML Database          [upgrade]  VALID
--> Oracle Workspace Manager     [upgrade]  VALID
--> Oracle interMedia            [upgrade]  VALID
--> Expression Filter            [upgrade]  VALID
--> EM Repository                [upgrade]  VALID
--> Rule Manager                 [upgrade]  VALID
.

PL/SQL procedure successfully completed.

SQL> SPOOL OFF

Vamos executar o script “catupgrd.sql” para aplicar o Patch no Banco de Dados (Dicionário de Dados).

SQL> SPOOL patch.log
SQL> @?/rdbms/admin/catupgrd.sql
DOC>######################################################################
DOC>######################################################################
DOC>    The following statement will cause an "ORA-01722: invalid number"
DOC>    error if the user running this script is not SYS.  Disconnect
DOC>    and reconnect with AS SYSDBA.
DOC>######################################################################
DOC>######################################################################
DOC>#

no rows selected

DOC>######################################################################
DOC>######################################################################
DOC>    The following statement will cause an "ORA-01722: invalid number"
DOC>    error if the database server version is not correct for this script.
DOC>    Shutdown ABORT and use a different script or a different server.
DOC>######################################################################
DOC>######################################################################
DOC>#

no rows selected

.
.
.

Total Upgrade Time: 00:18:38
DOC>#######################################################################
DOC>#######################################################################
DOC>
DOC>   The above PL/SQL lists the SERVER components in the upgraded
DOC>   database, along with their current version and status.
DOC>
DOC>   Please review the status and version columns and look for
DOC>   any errors in the spool log file.  If there are errors in the spool
DOC>   file, or any components are not VALID or not the current version,
DOC>   consult the Oracle Database Upgrade Guide for troubleshooting
DOC>   recommendations.
DOC>
DOC>   Next shutdown immediate, restart for normal operation, and then
DOC>   run utlrp.sql to recompile any invalid application objects.
DOC>
DOC>#######################################################################
DOC>#######################################################################
DOC>#
SQL>
SQL> spool off

Após a execução do script “catupgrd.sql”, vamos reiniciar o Banco de Dados.

SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.

Total System Global Area 1073741824 bytes
Fixed Size                  1277796 bytes
Variable Size             415236252 bytes
Database Buffers          654311424 bytes
Redo Buffers                2916352 bytes
Database mounted.
Database opened.
SQL>

Vamos executar o script “utlrp.sql” e recompilar os possíveis objetos inválidos pós aplicação do Patch no Dicionário de Dados.

SQL> @?/rdbms/admin/utlrp.sql

TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_BGN  2012-04-17 16:40:48
DOC>   The following PL/SQL block invokes UTL_RECOMP to recompile invalid
DOC>   objects in the database. Recompilation time is proportional to the
DOC>   number of invalid objects in the database, so this command may take
DOC>   a long time to execute on a database with a large number of invalid
DOC>   objects.
DOC>
DOC>   Use the following queries to track recompilation progress:
DOC>
DOC>   1. Query returning the number of invalid objects remaining. This
DOC>      number should decrease with time.
DOC>         SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
DOC>
DOC>   2. Query returning the number of objects compiled so far. This number
DOC>      should increase with time.
DOC>         SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
DOC>
DOC>   This script automatically chooses serial or parallel recompilation
DOC>   based on the number of CPUs available (parameter cpu_count) multiplied
DOC>   by the number of threads per CPU (parameter parallel_threads_per_cpu).
DOC>   On RAC, this number is added across all RAC nodes.
DOC>
DOC>   UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
DOC>   recompilation. Jobs are created without instance affinity so that they
DOC>   can migrate across RAC nodes. Use the following queries to verify
DOC>   whether UTL_RECOMP jobs are being created and run correctly:
DOC>
DOC>   1. Query showing jobs created by UTL_RECOMP
DOC>         SELECT job_name FROM dba_scheduler_jobs
DOC>            WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>
DOC>   2. Query showing UTL_RECOMP jobs that are running
DOC>         SELECT job_name FROM dba_scheduler_running_jobs
DOC>            WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>#

TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_END  2012-04-17 16:41:33
DOC> The following query reports the number of objects that have compiled
DOC> with errors (objects that compile with errors have status set to 3 in
DOC> obj$). If the number is higher than expected, please examine the error
DOC> messages reported with each object (using SHOW ERRORS) to see if they
DOC> point to system misconfiguration or resource constraints that must be
DOC> fixed before attempting to recompile these objects.
DOC>#

OBJECTS WITH ERRORS
-------------------
                  0
DOC> The following query reports the number of errors caught during
DOC> recompilation. If this number is non-zero, please query the error
DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
DOC> are due to misconfiguration or resource constraints that must be
DOC> fixed before objects can compile successfully.
DOC>#

ERRORS DURING RECOMPILATION
---------------------------
                          0
SQL>

Vamos verificar o registro após aplicação do Patch Set 10.2.0.5.

SQL> col COMP_NAME for a35
SQL> select VERSION, STATUS, MODIFIED, STARTUP, COMP_NAME from dba_registry;

VERSION                        STATUS      MODIFIED             STARTUP  COMP_NAME
------------------------------ ----------- -------------------- -------- -----------------------------------
10.2.0.5.0                     VALID       17-APR-2012 16:35:28          Oracle Enterprise Manager
10.2.0.5.0                     VALID       17-APR-2012 16:41:35          Oracle interMedia
10.2.0.5.0                     VALID       17-APR-2012 16:41:34          Oracle XML Database
10.2.0.5.0                     VALID       17-APR-2012 16:41:34          Oracle Expression Filter
10.2.0.5.0                     VALID       17-APR-2012 16:41:35          Oracle Rule Manager
10.2.0.5.0                     VALID       17-APR-2012 16:41:33          Oracle Workspace Manager
10.2.0.5.0                     VALID       17-APR-2012 16:41:33          Oracle Database Catalog Views
10.2.0.5.0                     VALID       17-APR-2012 16:41:33          Oracle Database Packages and Types
10.2.0.5.0                     VALID       17-APR-2012 16:41:34          JServer JAVA Virtual Machine
10.2.0.5.0                     VALID       17-APR-2012 16:41:34          Oracle XDK
10.2.0.5.0                     VALID       17-APR-2012 16:41:34          Oracle Database Java Packages
SQL> !

Vamos inciar o Enterprise Manager.

[oracle@serveroracle ~]$ emctl start dbconsole
TZ set to Brazil/East
Oracle Enterprise Manager 10g Database Control Release 10.2.0.5.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.

http://serveroracle.localdomain:1158/em/console/aboutApplication

Starting Oracle Enterprise Manager 10g Database Control .......................... started.
------------------------------------------------------------------
Logs are generated in directory /oraprd01/app/oracle/product/10.2.0/db_1/serveroracle.localdomain_orcl/sysman/log
[oracle@serveroracle ~]$ emctl status agent
TZ set to Brazil/East
Oracle Enterprise Manager 10g Database Control Release 10.2.0.5.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
Agent Version     : 10.1.0.6.0
OMS Version       : 10.1.0.6.0
Protocol Version  : 10.1.0.2.0
Agent Home        : /oraprd01/app/oracle/product/10.2.0/db_1/serveroracle.localdomain_orcl
Agent binaries    : /oraprd01/app/oracle/product/10.2.0/db_1
Agent Process ID  : 11833
Parent Process ID : 9626
Agent URL         : http://serveroracle.localdomain:3938/emd/main
Started at        : 2012-04-17 16:51:04
Started by user   : oracle
Last Reload       : 2012-04-17 16:51:04
Last successful upload                       : (none)
Last attempted upload                        : (none)
Total Megabytes of XML files uploaded so far :     0.00
Number of XML files pending upload           :       16
Size of XML files pending upload(MB)         :     4.40
Available disk space on upload filesystem    :    71.39%
---------------------------------------------------------------
Agent is Running and Ready
[oracle@serveroracle ~]$

Tela do Enterprise Manager após aplicar o Patch

Como podemos perceber na imagem acima, o Enterprise Manager está mostrando o Banco de Dados 10.2.0.1.
Para ajuste deste, devemos reconfigurar o Enterprise Manager (dbconsole).
Vamos baixar o serviço do Enterpise Manager e reconfigurar o mesmo.
Para reconfigurar o Enterprise Manager acesse o artigo do Anderson Graf Recriando repositório do Oracle Enterprise Manager.

Vamos seguir o artigo acima.
A configuração pode não ser completada, pois ao subir o serviço do Enterprise Manager o mesmo pode ocorrer um erro de certificado SSL.
Caso haja erro ao recriar o repositório do Enterprise Manager, verifique o status do serviço do mesmo conforme abaixo.

[oracle@serveroracle ~]$ emctl status dbconsole
TZ set to Brazil/East
Oracle Enterprise Manager 10g Database Control Release 10.2.0.5.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.

https://serveroracle.localdomain:1158/em/console/aboutApplication

Oracle Enterprise Manager 10g is not running.
------------------------------------------------------------------
Logs are generated in directory /oraprd01/app/oracle/product/10.2.0/db_1/serveroracle.localdomain_orcl/sysman/log
[oracle@serveroracle ~]$ emctl status agent
TZ set to Brazil/East
Oracle Enterprise Manager 10g Database Control Release 10.2.0.5.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
Agent is Not Running
[oracle@serveroracle ~]$

Para solicionar este, devemos aplicar o Patch 8350262 para o Enterpise Manager.
Para aplicar o mesmo, vamos seguir o artigo Aplicação do Patch 8350262 para Correção do Enterprise Manager..
Seguindo o artigo acima, vamos aplicar o Patch para o Enterprise Manager.

Após aplicado o Patch 8350262 para o Enterprise Manager, vamos verificar o status do serviço do mesmo.

[oracle@serveroracle 8350262]$ emctl status dbconsole
TZ set to Brazil/East
Oracle Enterprise Manager 10g Database Control Release 10.2.0.5.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.

https://serveroracle.localdomain:1158/em/console/aboutApplication

Oracle Enterprise Manager 10g is running.
------------------------------------------------------------------
Logs are generated in directory /oraprd01/app/oracle/product/10.2.0/db_1/serveroracle.localdomain_orcl/sysman/log
[oracle@serveroracle 8350262]$ emctl status agent
TZ set to Brazil/East
Oracle Enterprise Manager 10g Database Control Release 10.2.0.5.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
Agent Version     : 10.1.0.6.0
OMS Version       : 10.1.0.6.0
Protocol Version  : 10.1.0.2.0
Agent Home        : /oraprd01/app/oracle/product/10.2.0/db_1/serveroracle.localdomain_orcl
Agent binaries    : /oraprd01/app/oracle/product/10.2.0/db_1
Agent Process ID  : 31928
Parent Process ID : 29766
Agent URL         : https://serveroracle.localdomain:3938/emd/main
Started at        : 2012-04-17 17:30:02
Started by user   : oracle
Last Reload       : 2012-04-17 17:30:02
Last successful upload                       : 2012-04-17 17:30:36
Total Megabytes of XML files uploaded so far :     4.00
Number of XML files pending upload           :        0
Size of XML files pending upload(MB)         :     0.00
Available disk space on upload filesystem    :    71.29%
---------------------------------------------------------------
Agent is Running and Ready
[oracle@serveroracle 8350262]$

Tela do Enterprise Manager após aplicado Patch para o mesmo e recriado o repositório do mesmo

Pronto aplicamos o Patch Set 10.2.0.5 (8202632) no Banco de Dados 10.2.0.1.
Mais informações sobre o Patch Set acessar o Suporte da Oracle.

Execução paralela de instruções SQL: Parallel Query, DML e DDL

Anderson Graf — Mon, 07 May 2012 12:28:45 +0000

Varias vezes encontramos consultas, processos ou atualizações em massa provocando um alto índice de custos para o ambiente de banco de dados, apesar de varias otimizações serem aplicadas o custo ainda é extremamente alto o que acaba prejudicando varios processos e rotinas.

Então.. o que podemos fazer para diminuir este impacto?

Já pensou em paralelismo?

O Paralelismo, disponibilizado na versão enterprise do Oracle database, oferece a ideia de se quebrar uma tarefa em partes para que, em vez de um único processo fazer todo o trabalho, muitos processos possam executar simultâniamente as partes e no final apresentar um resultado único em menos tempo do que o executado por um único processo.

A execução paralela proporcina melhorias no desempenho mediante a utilização otimizada dos recursos de hardware do servidor, ou seja, podemos utilizar todas as CPUs de um servidor em uma única atividade o que proporcionaria um ganho significativo no processo, por exemplo. Esta mesma distribuição pode ser realizada em um ambiente clusterizado(RAC), onde podemos utilizar, se necessário, os recursos de todos os nodes para uma única tarefa/processo.

Contudo, quando implementado, devemos sempre ficar atentos ao consumo dos recursos do servidor como CPU, memória e discos, pois o paralelismo pode saturar completamente uma máquina, ficando então a cargo do DBA equilibrar cuidadosamente o número de pessoas que executam operações paralelas quanto o grau do paralelismo utilizado para que os recursos do servidor não sejam esgotados.

Para a divisão e execução simultânia das varias partes de uma tarefa, o Oracle cria uma sessão “coordenador” que gerencia os processos escravos responsáveis pelas execuções paralelas e que ao termino recebe de cada escravo os resultados e reproduz uma saida combinada de forma a obtermos o mesmo resultado do que uma execução em serie, porem com o diferencial deste processo paralelo ter concluido muito mais rapidamente.

O paralelismo pode ser especificado em 3 (três) diferentes níveis:

Nível de instrução:

Utilizando hints

Nível de objeto:

Especificando o grau de paralelismo na definição do objeto, tabela ou indice.

Nível de instance:

Ajustando as parâmetrizações da instance. (show parameter parallel)

Visto um básico histórico do funcionamento do paralelismo, vamos agora aprender sobre 3 tipos de paralelismo que são: Parallel Query, DML e DDL

Parallel Query:

O paralelismo de queries, também conhecida como PQO (Parallel Query Option), foi a primeira feature de execução paralela desenvolvida pela Oracle e disponibilizada já na versão 7.1 do Oracle database, sendo que hoje é a feature de paralelismo mais utilizada no SGBD Oracle.

Seu principal objetivo é reduzir o tempo de execução de grandes consultas, porém antes de implementá-lo definitivamente devemos testar todas as consultas para garantir que elas vão se beneficiar do paralelismo.

Para habilitar ou desabilitar o paralelismo podemos alterar uma tabela ou indice informando o grau de paralelismo ou atraves da utilização de hints conforme exemplos abaixo:

Para habilitar/utilizar o paralelismo:

-> Nível de objeto

SQL> alter table teste1 parallel (degree 4);

Table altered.

SQL> alter table teste1 parallel 4;

Table altered.

-> Nível de instrução:

SQL> select /*+ PARALLEL(teste1,4,1) */ count(*) from teste1;

  COUNT(*)
----------
   1250000

Sintaxe:

select /*+ PARALLEL(table_alias, degree, nodes) */ * from table_name

Para visualizar o paralelismo configurado sobre a tabela/indice:

SQL> select degree from user_tables where table_name='TESTE1';

DEGREE
----------
         4

Para desabilitar o paralelismo:

-> Nível de objeto

SQL> alter table teste1 NOPARALLEL;

Table altered.

SQL> select degree from user_tables where table_name='TESTE1';

DEGREE
----------
         1

-> Nível de instrução:

SQL> select /*+ NOPARALLEL(teste1) */ count(*) from teste1;

  COUNT(*)
----------
   1250000

Vamos realizar agora um explain da query para verificar como fica sem e com paralelismo:

SQL> explain plan for
  2  select count(*) from teste1
  3  /

Explained.

SQL> SELECT * FROM TABLE(dbms_xplan.display);

PLAN_TABLE_OUTPUT
---------------------------------------------------------------------
Plan hash value: 3242138447

---------------------------------------------------------------------
| Id  | Operation          | Name   | Rows  | Cost (%CPU)| Time     |
---------------------------------------------------------------------
|   0 | SELECT STATEMENT   |        |     1 |   553   (2)| 00:00:07 |
|   1 |  SORT AGGREGATE    |        |     1 |            |          |
|   2 |   TABLE ACCESS FULL| TESTE1 |  1598K|   553   (2)| 00:00:07 |
---------------------------------------------------------------------

SQL> explain plan for
  2  select /*+ PARALLEL(teste1,4,1) */ count(*) from teste1
  3  /

Explained.

SQL> SELECT * FROM TABLE(dbms_xplan.display);

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------------------------------
Plan hash value: 721361025

--------------------------------------------------------------------------------------------------------
| Id  | Operation              | Name     | Rows  | Cost (%CPU)| Time     |    TQ  |IN-OUT| PQ Distrib |
--------------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT       |          |     1 |   153   (2)| 00:00:02 |        |      |            |
|   1 |  SORT AGGREGATE        |          |     1 |            |          |        |      |            |
|   2 |   PX COORDINATOR       |          |       |            |          |        |      |            |
|   3 |    PX SEND QC (RANDOM) | :TQ10000 |     1 |            |          |  Q1,00 | P->S | QC (RAND)  |
|   4 |     SORT AGGREGATE     |          |     1 |            |          |  Q1,00 | PCWP |            |
|   5 |      PX BLOCK ITERATOR |          |  1598K|   153   (2)| 00:00:02 |  Q1,00 | PCWC |            |
|   6 |       TABLE ACCESS FULL| TESTE1   |  1598K|   153   (2)| 00:00:02 |  Q1,00 | PCWP |            |
--------------------------------------------------------------------------------------------------------

Note que quando executado uma instrução em paralelo temos como evidência as operações PX.

Parallel DML:

As operações de DML (Data Manipulation Language) INSERT, UPDATE e DELETE também podem ser paralizadas e proporcionar grandes ganhos em tempo/custo, contudo quando a paralelização de DML é acionada o Oracle verifica algumas “regras”/restrições para apontar se a paralelização é válida ou não.

Abaixo podemos ver as regras aplicadas, NOTE que UPDATE e DELETE possuem o mesmo escopo de verificação.

Para UPDATE e DELETE:

- A paralelização pode ocorrer em tabelas particionadas, mas somente quando várias partições estão envolvidos;

- Não pode ser paralizado o UPDATE e DELETE em uma tabela não particionada ou quando as operações afetam apenas uma única partição.

Para operações de INSERT:

- O INSERT padrão utilizando a cláusula VALUES não pode ser paralelizado, apenas pode ser paralelizado as declarações INSERT…SELECT.

Vamos demonstrar um exemplo com e sem paralelismo:

-> INSERT…SELECT sem paralelismo:

SQL> set autotrace traceonly explain;
SQL> insert into teste1 select * from teste1;

1250000 rows created.

Execution Plan
----------------------------------------------------------
Plan hash value: 110554063

-----------------------------------------------------------------------------------
| Id  | Operation                | Name   | Rows  | Bytes | Cost (%CPU)| Time     |
-----------------------------------------------------------------------------------
|   0 | INSERT STATEMENT         |        |  1250K|  4882K|   551   (2)| 00:00:07 |
|   1 |  LOAD TABLE CONVENTIONAL | TESTE1 |       |       |            |          |
|   2 |   TABLE ACCESS FULL      | TESTE1 |  1250K|  4882K|   551   (2)| 00:00:07 |
-----------------------------------------------------------------------------------

-> INSERT…SELECT com paralelismo:

SQL> alter session enable parallel dml;

Session altered.

SQL> explain plan for
  2  insert /*+ parallel (teste1,4,1) */ into teste1 select * from teste1;

Explained.

SQL> SELECT * FROM TABLE(dbms_xplan.display);

Execution Plan
----------------------------------------------------------
Plan hash value: 1222195891

-----------------------------------------------------------------------------------------------------------------
| Id  | Operation               | Name     | Rows  | Bytes | Cost (%CPU)| Time     |    TQ  |IN-OUT| PQ Distrib |
-----------------------------------------------------------------------------------------------------------------
|   0 | INSERT STATEMENT        |          |  1250K|  4882K|    29   (2)| 00:00:02 |        |      |            |
|   1 |  PX COORDINATOR         |          |       |       |            |          |        |      |            |
|   2 |   PX SEND QC (RANDOM)   | :TQ10001 |  1250K|  4882K|    29   (2)| 00:00:02 |  Q1,01 | P->S | QC (RAND)  |
|   3 |    LOAD AS SELECT       | TESTE1   |       |       |            |          |  Q1,01 | PCWP |            |
|   4 |     PX RECEIVE          |          |  1250K|  4882K|    29   (2)| 00:00:02 |  Q1,01 | PCWP |            |
|   5 |      PX SEND ROUND-ROBIN| :TQ10000 |  1250K|  4882K|    29   (2)| 00:00:02 |        | S->P | RND-ROBIN  |
|   6 |       TABLE ACCESS FULL | TESTE1   |  1250K|  4882K|    29   (2)| 00:00:02 |        |      |            |
-----------------------------------------------------------------------------------------------------------------

13 rows selected.

SQL> commit;

Commit complete.

SQL> alter session disable parallel dml;

Session altered.

Parallel DDL:

O paralelismo em instruções DDL se aplicam a tabelas e indices, particionadas ou não.

-> Para tabelas:

CREATE TABLE…AS SELECT

ALTER INDEX…REBUILD PARTITION

ALTER INDEX…SPLIT PARTITION

-> Para indices:

CREATE INDEX

ALTER INDEX…REBUILD

ALTER INDEX…REBUILD PARTITION

ALTER INDEX…SPLIT PARTITION

Lembrando que tabelas com objetos/campos com LOB não permitem paralelismo DDL.

Exemplos de paralelismo com DDL:

SQL> explain plan for
  2  create table teste_parallel parallel (degree 4)  as select * from teste1;

Explained.

SQL> SELECT * FROM TABLE(dbms_xplan.display);

PLAN_TABLE_OUTPUT
----------------------------------------------------------------------------------------------------------------------
Plan hash value: 3992983551

----------------------------------------------------------------------------------------------------------------------
| Id  | Operation              | Name           | Rows  | Bytes | Cost (%CPU)| Time     |    TQ  |IN-OUT| PQ Distrib |
----------------------------------------------------------------------------------------------------------------------
|   0 | CREATE TABLE STATEMENT |                |    10M|    38M|  2388   (1)| 00:00:29 |        |      |            |
|   1 |  PX COORDINATOR        |                |       |       |            |          |        |      |            |
|   2 |   PX SEND QC (RANDOM)  | :TQ10000       |    10M|    38M|  1476   (1)| 00:00:18 |  Q1,00 | P->S | QC (RAND)  |
|   3 |    LOAD AS SELECT      | TESTE_PARALLEL |       |       |            |          |  Q1,00 | PCWP |            |
|   4 |     PX BLOCK ITERATOR  |                |    10M|    38M|  1476   (1)| 00:00:18 |  Q1,00 | PCWC |            |
|   5 |      TABLE ACCESS FULL | TESTE1         |    10M|    38M|  1476   (1)| 00:00:18 |  Q1,00 | PCWP |            |
----------------------------------------------------------------------------------------------------------------------

Agora observe se criarmos a tabela sem Paralelismo:

SQL> explain plan for
  2  create table teste_parallel  as select * from teste1;

Explained.

SQL> SELECT * FROM TABLE(dbms_xplan.display);

PLAN_TABLE_OUTPUT
-----------------------------------------------------------------------------------------
Plan hash value: 3174501407

-----------------------------------------------------------------------------------------
| Id  | Operation              | Name           | Rows  | Bytes | Cost (%CPU)| Time     |
-----------------------------------------------------------------------------------------
|   0 | CREATE TABLE STATEMENT |                |    10M|    38M|  8967   (1)| 00:01:48 |
|   1 |  LOAD AS SELECT        | TESTE_PARALLEL |       |       |            |          |
|   2 |   TABLE ACCESS FULL    | TESTE1         |    10M|    38M|  5320   (1)| 00:01:04 |
-----------------------------------------------------------------------------------------

Vamos ver um indice, com e sem paralelismo:

SQL> explain plan for
  2  create index teste_idx01 on teste1(CD_TESTE) parallel (degree 4);

Explained.

SQL> SELECT * FROM TABLE(dbms_xplan.display);

PLAN_TABLE_OUTPUT
---------------------------------------------------------------------------------------------------------------------
Plan hash value: 1444741105

---------------------------------------------------------------------------------------------------------------------
| Id  | Operation                | Name        | Rows  | Bytes | Cost (%CPU)| Time     |    TQ  |IN-OUT| PQ Distrib |
---------------------------------------------------------------------------------------------------------------------
|   0 | CREATE INDEX STATEMENT   |             |    10M|    38M|  2858   (1)| 00:00:35 |        |      |            |
|   1 |  PX COORDINATOR          |             |       |       |            |          |        |      |            |
|   2 |   PX SEND QC (ORDER)     | :TQ10001    |    10M|    38M|            |          |  Q1,01 | P->S | QC (ORDER) |
|   3 |    INDEX BUILD NON UNIQUE| TESTE_IDX01 |       |       |            |          |  Q1,01 | PCWP |            |
|   4 |     SORT CREATE INDEX    |             |    10M|    38M|            |          |  Q1,01 | PCWP |            |
|   5 |      PX RECEIVE          |             |    10M|    38M|  1476   (1)| 00:00:18 |  Q1,01 | PCWP |            |
|   6 |       PX SEND RANGE      | :TQ10000    |    10M|    38M|  1476   (1)| 00:00:18 |  Q1,00 | P->P | RANGE      |
|   7 |        PX BLOCK ITERATOR |             |    10M|    38M|  1476   (1)| 00:00:18 |  Q1,00 | PCWC |            |
|   8 |         TABLE ACCESS FULL| TESTE1      |    10M|    38M|  1476   (1)| 00:00:18 |  Q1,00 | PCWP |            |
---------------------------------------------------------------------------------------------------------------------

Sem paralelismo:

SQL> explain plan for
  2  create index teste_idx01 on teste1(CD_TESTE);

Explained.

SQL> SELECT * FROM TABLE(dbms_xplan.display);

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------------
Plan hash value: 3409988532

--------------------------------------------------------------------------------------
| Id  | Operation              | Name        | Rows  | Bytes | Cost (%CPU)| Time     |
--------------------------------------------------------------------------------------
|   0 | CREATE INDEX STATEMENT |             |    10M|    38M| 10846   (1)| 00:02:11 |
|   1 |  INDEX BUILD NON UNIQUE| TESTE_IDX01 |       |       |            |          |
|   2 |   SORT CREATE INDEX    |             |    10M|    38M|            |          |
|   3 |    TABLE ACCESS FULL   | TESTE1      |    10M|    38M|  5320   (1)| 00:01:04 |
--------------------------------------------------------------------------------------

Referências:

http://docs.oracle.com/cd/B10501_01/server.920/a96524/c20paral.htm
http://www.oracle.com/technetwork/issue-archive/2010/o40parallel-092275.html
http://www.akadia.com/services/ora_parallel_processing.html#Parallel%20Recovery

Falha ao tentar instalar Banco de Dados Oracle 10.2.0.1 em Oracle Linux 5.7

Maycon Tomiasi — Thu, 05 Apr 2012 12:00:48 +0000

Este artigo tem como objetivo explicar e solucionar a Falha durante a instalação do Banco de Dados 10g no Oracle Linux 5.7.

Durante a instalação ocorreu o seguinte erro:
“Checking operating system version: must be redhat-3, SuSE-9, redhat-4, UnitedLinux-1.0, asianux-1 or asianux-2
Failed <<<<”

Segue evidência abaixo:

[oracle@serveroracle database]$ ./runInstaller
Starting Oracle Universal Installer...

Checking installer requirements...

Checking operating system version: must be redhat-3, SuSE-9, redhat-4, UnitedLinux-1.0, asianux-1 or asianux-2
                                      Failed <<<<

Exiting Oracle Universal Installer, log for this session can be found at /tmp/OraInstall2012-03-29_11-17-22AM/installActions2012-03-29_11-17-22AM.log
[oracle@serveroracle database]$

O erro ocorreu pois ao checar a versão do Sistema Operacional o Oracle Linux 5 não passou pela certificação. Isso acontece pois o instalador do Oracle 10g é antigo, ou seja, novos instaladores são já certificados.
Observando os sistemas operacionais na mensagem acima “must be redhat-3, SuSE-9, redhat-4, UnitedLinux-1.0, asianux-1 or asianux-2″ não tem o redhat-5.

Há duas maneiras de solucionar este problema:
- Adicionando o “redhat-5″ no arquivo “oraparam.ini”;
- Utilizar o comando “./runInstaller -ignoreSysPrereqs”. Veja no Metalink: [ID 419646.1]

Vou utilizar a primeira opção. Vamos adicionar o “redhat-5″ no arquivo de instalação do Oracle.

[oracle@serveroracle database]$ ls -l
total 28
drwxr-xr-x 9 oracle oinstall 4096 Oct 29  2007 doc
drwxr-xr-x 5 oracle oinstall 4096 Mar 29 11:19 install
drwxr-xr-x 2 oracle oinstall 4096 Oct 29  2007 response
-rwxr-xr-x 1 oracle oinstall 1327 Jul  2  2005 runInstaller
drwxr-xr-x 9 oracle oinstall 4096 Oct 29  2007 stage
-rwxr-xr-x 1 oracle oinstall 5213 Jul  2  2005 welcome.html
[oracle@serveroracle database]$

Vamos acessar o diretório “install/”.

[oracle@serveroracle database]$ cd install/
[oracle@serveroracle install]$ ls -l
total 180
-rwxr-xr-x 1 oracle oinstall     28 Jul  2  2005 addLangs.sh
-rwxr-xr-x 1 oracle oinstall     76 Jul  2  2005 addNode.sh
drwxr-xr-x 2 oracle oinstall   4096 Oct 29  2007 images
-rwxr-xr-x 1 oracle oinstall  35634 Jul  2  2005 lsnodes
-rwxr-xr-x 1 oracle oinstall   2268 Jul  2  2005 oneclick.properties
-rwxr-xr-x 1 oracle oinstall   2387 Jul  2  2005 oraparam.ini
-rwxr-xr-x 1 oracle oinstall   6428 Jul  2  2005 oraparamsilent.ini
drwxr-xr-x 2 oracle oinstall   4096 Oct 29  2007 resource
drwxr-xr-x 2 oracle oinstall   4096 Oct 29  2007 response
-rwxr-xr-x 1 oracle oinstall 102612 Jul  2  2005 unzip
[oracle@serveroracle install]$

No arquivo “oraparam.ini” estão os parâmetros de inicialização para a instalação do Software Oracle no Linux.
Vamos visualizar o mesmo.

[oracle@serveroracle install]$ cat oraparam.ini
[Oracle]
DISTRIBUTION=TRUE
SOURCE=../stage/products.xml
LICENSE_LOCATION=
JRE_LOCATION=../stage/Components/oracle.swd.jre/1.4.2.8.0/1/DataFiles
JRE_MEMORY_OPTIONS=" -mx150m"
DEFAULT_HOME_LOCATION=oracle/product/10.2.0/db
DEFAULT_HOME_NAME=OraDb10g_home
NO_BROWSE=/net
NLS_ENABLED=TRUE
BOOTSTRAP=TRUE
PREREQ_CONFIG_LOCATION=../stage/prereq
OUI_VERSION=10.2.0.1.0
#SHOW_HOSTNAME=ALWAYS_SHOW shows the hostname panel always
#SHOW_HOSTNAME=NEVER_SHOW does not the hostname panel
#SHOW_HOSTNAME=CONDITION_SHOW shows the hostname panel on condition
SHOW_HOSTNAME=NEVER_SHOW
#THIN_JDBC_FILENAME is optional and defaults to classes12.jar
#The value specified for this should be packaged with OUI, and should
#be relative to /jlib/
THIN_JDBC_FILENAME=classes12.jar
#JRE_OSDPARAM is to set OS dependent param for JRE ( mainly for native VM in 1.3.1)
#JRE_OSDPARAM is optional and should be set to -native for the JRE's
#that support native VM ( mainly for Unix platforms ), in JRE 1.3.1
#For JRE 1.4.1 this should be set to empty or the type of VM that is
#supported client/server. The default value is -native in UNIX platforms
#that supports native VM
#Unix supporting native - JRE_OSDPARAM="-native"
#Unix NOT supporting native and 1.4.1 - JRE_OSDPARAM=""
JRE_OSDPARAM=""
CLUSTERWARE={"oracle.crs","10.1.0.2.0"}
#RUN_OUICA specifies the batch script name that needs to be run
#The script is ouica.bat for win32, and ouica.sh for solaris.
#If the value is not specified, then the OUICA script is not run
RUN_OUICA=ouica.sh
SILENT_VARIABLE_VALIDATION=TRUE

[Certified Versions]
Linux=redhat-3,SuSE-9,redhat-4,UnitedLinux-1.0,asianux-1,asianux-2

[UnitedLinux-1.0-optional]
TEMP_SPACE=80
SWAP_SPACE=150
MIN_DISPLAY_COLORS=256

[Linux-redhat-3.0-optional]
TEMP_SPACE=80
SWAP_SPACE=150
MIN_DISPLAY_COLORS=256

[Linux-SuSE-9-optional]
TEMP_SPACE=80
SWAP_SPACE=150
MIN_DISPLAY_COLORS=256

[Linux-redhat-4.0-optional]
TEMP_SPACE=80
SWAP_SPACE=150
MIN_DISPLAY_COLORS=256

[Linux-asianux-1.0-optional]
TEMP_SPACE=80
SWAP_SPACE=150
MIN_DISPLAY_COLORS=256

[Linux-asianux-2.0-optional]
TEMP_SPACE=80
SWAP_SPACE=150
MIN_DISPLAY_COLORS=256

[IMAGES]
FILE1=images/rdbms_1.gif
FILE2=images/rdbms_2.gif
FILE3=images/rdbms_3.gif
FILE4=images/rdbms_4.gif
FILE5=images/rdbms_5.gif
FILE6=images/rdbms_6.gif
FILE7=images/rdbms_7.gif
FILE8=images/rdbms_8.gif

LICENSE_LOCATION=license.txt
[oracle@serveroracle install]$

Conforme acima, na linha abaixo de [Certified Versions] “Linux=redhat-3,SuSE-9,redhat-4,UnitedLinux-1.0,asianux-1,asianux-2″ vamos adicionar o redhat-5 nesta.

[oracle@serveroracle install]$ vi oraparam.ini
[oracle@serveroracle install]$ cat oraparam.ini
[Oracle]
DISTRIBUTION=TRUE
SOURCE=../stage/products.xml
LICENSE_LOCATION=
JRE_LOCATION=../stage/Components/oracle.swd.jre/1.4.2.8.0/1/DataFiles
JRE_MEMORY_OPTIONS=" -mx150m"
DEFAULT_HOME_LOCATION=oracle/product/10.2.0/db
DEFAULT_HOME_NAME=OraDb10g_home
NO_BROWSE=/net
NLS_ENABLED=TRUE
BOOTSTRAP=TRUE
PREREQ_CONFIG_LOCATION=../stage/prereq
OUI_VERSION=10.2.0.1.0
#SHOW_HOSTNAME=ALWAYS_SHOW shows the hostname panel always
#SHOW_HOSTNAME=NEVER_SHOW does not the hostname panel
#SHOW_HOSTNAME=CONDITION_SHOW shows the hostname panel on condition
SHOW_HOSTNAME=NEVER_SHOW
#THIN_JDBC_FILENAME is optional and defaults to classes12.jar
#The value specified for this should be packaged with OUI, and should
#be relative to /jlib/
THIN_JDBC_FILENAME=classes12.jar
#JRE_OSDPARAM is to set OS dependent param for JRE ( mainly for native VM in 1.3.1)
#JRE_OSDPARAM is optional and should be set to -native for the JRE's
#that support native VM ( mainly for Unix platforms ), in JRE 1.3.1
#For JRE 1.4.1 this should be set to empty or the type of VM that is
#supported client/server. The default value is -native in UNIX platforms
#that supports native VM
#Unix supporting native - JRE_OSDPARAM="-native"
#Unix NOT supporting native and 1.4.1 - JRE_OSDPARAM=""
JRE_OSDPARAM=""
CLUSTERWARE={"oracle.crs","10.1.0.2.0"}
#RUN_OUICA specifies the batch script name that needs to be run
#The script is ouica.bat for win32, and ouica.sh for solaris.
#If the value is not specified, then the OUICA script is not run
RUN_OUICA=ouica.sh
SILENT_VARIABLE_VALIDATION=TRUE

[Certified Versions]
Linux=redhat-3,SuSE-9,redhat-4,UnitedLinux-1.0,asianux-1,asianux-2,redhat-5

[UnitedLinux-1.0-optional]
TEMP_SPACE=80
SWAP_SPACE=150
MIN_DISPLAY_COLORS=256

[Linux-redhat-3.0-optional]
TEMP_SPACE=80
SWAP_SPACE=150
MIN_DISPLAY_COLORS=256

[Linux-SuSE-9-optional]
TEMP_SPACE=80
SWAP_SPACE=150
MIN_DISPLAY_COLORS=256

[Linux-redhat-4.0-optional]
TEMP_SPACE=80
SWAP_SPACE=150
MIN_DISPLAY_COLORS=256

[Linux-asianux-1.0-optional]
TEMP_SPACE=80
SWAP_SPACE=150
MIN_DISPLAY_COLORS=256

[Linux-asianux-2.0-optional]
TEMP_SPACE=80
SWAP_SPACE=150
MIN_DISPLAY_COLORS=256

[IMAGES]
FILE1=images/rdbms_1.gif
FILE2=images/rdbms_2.gif
FILE3=images/rdbms_3.gif
FILE4=images/rdbms_4.gif
FILE5=images/rdbms_5.gif
FILE6=images/rdbms_6.gif
FILE7=images/rdbms_7.gif
FILE8=images/rdbms_8.gif

LICENSE_LOCATION=license.txt
[oracle@serveroracle install]$

Após adicionarmos o redhat-5 na linha de certificação das versões dos sistemas operacionais, vamos executar novamente o “./runInstaller”.

[oracle@serveroracle database]$ ./runInstaller
Starting Oracle Universal Installer...

Checking installer requirements...

Checking operating system version: must be redhat-3, SuSE-9, redhat-4, UnitedLinux-1.0, asianux-1, asianux-2 or redhat-5
                                      Passed

All installer requirements met.

Preparing to launch Oracle Universal Installer from /tmp/OraInstall2012-03-29_11-21-25AM. Please wait ...[oracle@serveroracle database]$

Pronto solucionamos o problema, agora basta continuar a instalação.

1º GUOB 2012

Leandro Lana — Sat, 31 Mar 2012 18:55:55 +0000

Conforme a muito tempo estavamos publicando via twitter, blogs pessoais e até mesmo aqui no oraclehome. Participamos do 1º encontro de 2012 do Grupo de Usuários Oracle (GUOB), que foi realizado no ultimo final de semana 24/03/2012 em São Paulo que contou com a presença do performance man Craig A. Shallahamer.

Infelizmente perdemos a metade da primeira palestra, logística de Blumenau até São Paulo é meio complicada! Mas não vamos nos atentar a detalhes extra campo, vamos ao que nos interessa.

A primeira palestra conduzida por Craig, apesar de pegarmos pela metade devido os problemas citados acima, conseguimos ainda ver bastante conteúdo novo sobre o tema “Unit of work time based performance analysis” que nos dará pelo menos alguns meses de estudo para conhecermos mais sobre o assunto.

Para quem tiver interesse pode baixar o material desta palestra Clique aqui

O segundo palestrante, Flávio Rangel pela Fusion Solution aprentou a ferramenta Forms-up que permite a migração de forms/reports em pouco tempo de trabalho e sem demandar de um alto investimento. Ocorreram alguns erros tecnicos, mas isso esta sujeito a ocorrer em apresentações ao vivo.

Vale lembrar que a ferramenta Forms-up é 100% brasileira!

A terceira palestra foi conduzida pelo Kleuber Matta da Quest Software que mostrou uma grade de softwares desenvolidos para administração de monitoramento de banco de dados, em especial o Foglight, simplesmente fantástico tanto pela facilidade quanto pela quantidade de informações que o mesmo traz de forma rápida e precisa.

Na quarta e ultima palestra, volta a cena o Craig com o tema “Introduction to Oracle Buffer Cache Internals”. Foi uma palestra muito tecnica e explicou a vida de um buffer chain, como funciona a lista de LRU e MRU, muito bom para quem esta começando no mundo oracle. Fóra que o Craig é uma figura, vivia fazendo piadinhas na palestra e isso divertiu muita gente.

Para quem tiver interesse pode baixar o material desta palestra Clique aqui

Não podemos deixar de comentar também que o evento teve grande foco na confratermização entre os participantes do eventos afim de trocar contatos e experiências profissionais sobre o mundo Oracle.

Tivemos a participação neste eventos de alguns membros do programa Oracle ACE como David Siqueira, Rodrigo Almeida e Rodrigo Mufalani.

Pelo Oracle Home tivemos a participação dos administradores Anderson Graf, Leandro Lana e Rafael Stoever.

Abaixo temos a agenda dos próximos eventos de 2012, contamos com sua presença! Para ajudar a comunidade a crescer ainda mais.

Junho/2012	2º Encontro do GUOB 2012	Brasilia
11/08/2012	GUOB Tech Day 2012	Hotel Blue Tree Morumbi – São Paulo
Outubro/2012	3º Encontro do GUOB 2012	Rio de Janeiro
22/11/2012	4º Encontro do GUOB 2012	Porto Alegre
Dezembro/2012	Oracle Open World Latin America	São Paulo

As datas podem sofrer alterações.

SYS_CONTEXT ‘USERENV’

Leandro Lana — Thu, 29 Mar 2012 12:00:20 +0000

Bom dia.

Para muitos esse é um tópico batido, e muitos já saberão a fundo do mesmo. Porem não custa escrever para quem não conhece utilizar.

Aqui no www.oraclehome.com.br já tivemos um post do nosso ADM Anderson Graf que utilizou o sys_context para pegar o seu sid. Clique aqui para ver o post do Anderson.

Bom pessoal o sys_context foi criado para coletar informações próprias.

Observe a syntaxe.

select sys_context('USERENV','SID') "SID" from dual;

Este select irá retornar o sid da seção que esta executando. Porem temos varias outras possibilidades para o sys_context.

Observe o select abaixo:

SELECT
  SYS_CONTEXT( 'USERENV', 'ACTION' ) action,
  SYS_CONTEXT( 'USERENV', 'AUTHENTICATION_METHOD' ) authentication_method,
  SYS_CONTEXT( 'USERENV', 'BG_JOB_ID' ) bg_job_id,
  SYS_CONTEXT( 'USERENV', 'CLIENT_IDENTIFIER' ) client_identifier,
  SYS_CONTEXT( 'USERENV', 'CLIENT_INFO' ) client_info,
  SYS_CONTEXT( 'USERENV', 'CURRENT_SCHEMAID' ) current_schemaid,
  SYS_CONTEXT( 'USERENV', 'CURRENT_SCHEMA' ) current_schema,
  SYS_CONTEXT( 'USERENV', 'CURRENT_USER' ) current_user,
  SYS_CONTEXT( 'USERENV', 'DB_DOMAIN' ) db_domain,
  SYS_CONTEXT( 'USERENV', 'DB_NAME' ) db_name,
  SYS_CONTEXT( 'USERENV', 'DB_UNIQUE_NAME' ) db_unique_name,
  SYS_CONTEXT( 'USERENV', 'HOST' ) host,
  SYS_CONTEXT( 'USERENV', 'INSTANCE' ) instance,
  SYS_CONTEXT( 'USERENV', 'INSTANCE_NAME' ) instance_name,
  SYS_CONTEXT( 'USERENV', 'IP_ADDRESS' ) ip_address,
  SYS_CONTEXT( 'USERENV', 'ISDBA' ) isdba,
  SYS_CONTEXT( 'USERENV', 'LANG' ) lang,
  SYS_CONTEXT( 'USERENV', 'LANGUAGE' ) language,
  SYS_CONTEXT( 'USERENV', 'NETWORK_PROTOCOL' ) network_protocol,
  SYS_CONTEXT( 'USERENV', 'NLS_CALENDAR' ) nls_calendar,
  SYS_CONTEXT( 'USERENV', 'NLS_CURRENCY' ) nls_currency,
  SYS_CONTEXT( 'USERENV', 'OS_USER' ) os_user,
  SYS_CONTEXT( 'USERENV', 'SERVER_HOST' ) server_host,
  SYS_CONTEXT( 'USERENV', 'TERMINAL' ) terminal
FROM dual;

Então estes são todos os parâmetros que você pode coletar de si mesmo.
Muitos vão me questionar. Pra que serve saber meu IP, ou meu host?
Bom, para muitas coisas. Para debugar um pl/sql ou até mesmo para auditar informações de quem executou determinadas funções.

Também há como coletar estas informações através de funções.

DECLARE
   PROCEDURE showenv (str IN VARCHAR2) IS
   BEGIN
      DBMS_OUTPUT.PUT_LINE (
         str || '=' || SYS_CONTEXT ('USERENV', str));
   END;
BEGIN
   showenv ('NLS_CURRENCY');
   showenv ('NLS_CALENDAR');
   showenv ('NLS_DATE_FORMAT');
   showenv ('NLS_DATE_LANGUAGE');
   showenv ('NLS_SORT');
   showenv ('SESSION_USER');
   showenv ('CURRENT_USER');
   showenv ('CURRENT_SCHEMA');
   showenv ('CURRENT_SCHEMAID');
   showenv ('SESSION_USERID');
   showenv ('CURRENT_USERID');
   showenv ('IP_ADDRESS');
END;
/

Cada campo “showenv (‘XXXXXXX’);”, pode ser adicionado uma linha daquelas la em cima onde já postei.
Observe na Pratica.

SQL> set serveroutput on
SQL> DECLARE
  2     PROCEDURE showenv (str IN VARCHAR2) IS
  3     BEGIN
  4        DBMS_OUTPUT.PUT_LINE (
  5           str || '=' || SYS_CONTEXT ('USERENV', str));
  6     END;
  7  BEGIN
  8     showenv ('NLS_CURRENCY');
  9     showenv ('NLS_CALENDAR');
 10     showenv ('NLS_DATE_FORMAT');
 11     showenv ('NLS_DATE_LANGUAGE');
 12     showenv ('NLS_SORT');
 13     showenv ('SESSION_USER');
 14     showenv ('CURRENT_USER');
 15     showenv ('CURRENT_SCHEMA');
 16     showenv ('CURRENT_SCHEMAID');
 17     showenv ('SESSION_USERID');
 18     showenv ('CURRENT_USERID');
 19     showenv ('IP_ADDRESS');
 20  END;
 21  /

NLS_CURRENCY=$
NLS_CALENDAR=GREGORIAN
NLS_DATE_FORMAT=DD-MON-RR
NLS_DATE_LANGUAGE=AMERICAN
NLS_SORT=BINARY
SESSION_USER=LANA
CURRENT_USER=LANA
CURRENT_SCHEMA=LANA
CURRENT_SCHEMAID=56
SESSION_USERID=56
CURRENT_USERID=56
IP_ADDRESS=192.168.10.198

PL/SQL procedure successfully completed

Qualquer duvida estou a disposição para responder seus comentários.

Ref: docstore.mik.ua e docs.oracle.com

Erro ao subir o ASM durante aplicação do Patch 12419392

Maycon Tomiasi — Tue, 27 Mar 2012 10:31:53 +0000

Este artigo tem como objetivo explicar o motivo do erro após aplicar o Patch PSU 10.2.0.5.4 para o Banco de Dados Oracle 10.2.0.5.0 ao subir a instância ASM.
Estou usando um Banco de Dados Single Instance com ASM, ou seja, non-RAC.

Após o Patch Aplicado continuei o processo de aplicação do Patch no Banco de Dados. Subi os serviços do Banco de Dados e no momento de subir a instância ASM ocorreu o erro.

Subindo o Listener.

[oracle@serveroracle 12419392]$ lsnrctl start

LSNRCTL for Linux: Version 10.2.0.5.0 - Production on 15-MAR-2012 17:52:43

Copyright (c) 1991, 2010, Oracle.  All rights reserved.

Starting /oraprd01/app/oracle/product/10.2.0/db_1/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version 10.2.0.5.0 - Production
System parameter file is /oraprd01/app/oracle/product/10.2.0/db_1/network/admin/listener.ora
Log messages written to /oraprd01/app/oracle/product/10.2.0/db_1/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.56.104)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC0)))

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.56.104)(PORT=1521)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 10.2.0.5.0 - Production
Start Date                15-MAR-2012 17:52:43
Uptime                    0 days 0 hr. 0 min. 0 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /oraprd01/app/oracle/product/10.2.0/db_1/network/admin/listener.ora
Listener Log File         /oraprd01/app/oracle/product/10.2.0/db_1/network/log/listener.log
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.56.104)(PORT=1521)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC0)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
  Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "dbprod" has 1 instance(s).
  Instance "dbprod", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
[oracle@serveroracle 12419392]$

Vamos subir a Instância ASM.

[oracle@serveroracle 12419392]$ export ORACLE_SID=+ASM
[oracle@serveroracle 12419392]$ sqlplus sys/***** as sysdba

SQL*Plus: Release 10.2.0.5.0 - Production on Thu Mar 15 17:53:01 2012

Copyright (c) 1982, 2010, Oracle.  All Rights Reserved.

Connected to an idle instance.

SQL> startup mount
ORA-29701: unable to connect to Cluster Manager
SQL> shutdown immediate
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory
SQL> exit
Disconnected
[oracle@serveroracle 12419392]$

Ao tentar subir a Instância ASM, ocorreu um problema no Cluster Manager, no qual, não foi possível conectar ao mesmo.
Para resolver o problema, devemos remover o css com o usuário “root” e acessar o diretório “$ORACLE_HOME/bin” e executar os seguintes comandos:
- localconfig delete
- localconfig add

Com estes comandos removerá o CSS e o configurará o mesmo novamente.
Vamos executar os mesmos com o usuário “root”.

[oracle@serveroracle 12419392]$ su -
Password:
[root@serveroracle ~]# /oraprd01/app/oracle/product/10.2.0/db_1/bin/localconfig delete
Stopping CSSD.
Shutting down CSS daemon.
Shutdown request successfully issued.
Shutdown has begun. The daemons should exit soon.
[root@serveroracle ~]# /oraprd01/app/oracle/product/10.2.0/db_1/bin/localconfig add
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
Configuration for local CSS has been initialized

Adding to inittab
Startup will be queued to init within 30 seconds.
Checking the status of new Oracle init process...
Expecting the CRS daemons to be up within 600 seconds.
CSS is active on these nodes.
        serveroracle
CSS is active on all nodes.
Oracle CSS service is installed and running under init(1M)
[root@serveroracle ~]# exit
logout
[oracle@serveroracle 12419392]$

Com o usuário Oracle vamos subir a instância ASM.

[oracle@serveroracle 12419392]$ sqlplus sys/***** as sysdba

SQL*Plus: Release 10.2.0.5.0 - Production on Thu Mar 15 17:55:10 2012

Copyright (c) 1982, 2010, Oracle.  All Rights Reserved.

Connected to an idle instance.

SQL> startup mount
ASM instance started

Total System Global Area   83886080 bytes
Fixed Size                  1272120 bytes
Variable Size              57448136 bytes
ASM Cache                  25165824 bytes
ASM diskgroups mounted
SQL> exit
Disconnected from Oracle Database 10g Release 10.2.0.5.0 - Production
[oracle@serveroracle 12419392]$

Pronto, basta subir o Banco de Dados e terminar o processo de aplicação do Patch 12419392.
Veja o artigo da Aplicação do Patch 12419392 acessando Aplicando Patch PSU 10.2.0.5.4 no Banco de Dados Oracle 10.2.0.5.0 non-RAC.

Como adicionar novos discos SATA, via Oracle VirtualBox em seu ambiente Linux virtualizado ja existente.

Jone Jarouj — Mon, 26 Mar 2012 14:36:22 +0000

O exemplo aqui mostrado foi feito em um SO RedHat Enterprise Linux 5 update 2.

Caso voce tenha criado sua maquina virtual, com pouco espaço, eu necessite adicionar mais espaço devido ao crescimento do seu ambiente, a seguir, daremos passo a passo de como adicionar novos discos SATA ao seu ambiente Linux.

Em sua janela inicial do VirtualBox, selecione a maquina virtual que deseja adicionar disco e clique em configurações:

Na tela de configurações, vá em armazenamento:

Voce pode escolher adicionar novos discos IDE ou novos discos SATA, aqui optado por adicionar um novo disco SATA:

Iremos optar por Criar novo disco.

Optar pelo formato nativo do Oracle VirtualBox, VDI:

Escolher dinamicamente alocado, pois desta forma, o disco que está sendo criado, só irá crescer conforme demanda e não será alocado todo seu tamanho no momento de sua criação.

Escolha a localização do seu novo disco e o tamanho do mesmo, aqui colocado 10 Giga, aproximadamente:

Leia o resumo das suas escolhas e se estiver tudo ok, clique em Criar:

Seu novo disco irá aparecer nas opções de Armazenamento/Controladora SATA com o nome que você o deu anteriormente:

Clique em Ok.

Agora iremos iniciar a maquina virtual e formataremos o disco adicionado, pois o mesmo ao inicia-la, ainda não está pronto para uso.

Logue no Linux com seu usuário/senha do root.

Abra um terminal.

Execute o comando fdisk –l:

Veja que há um dispositivo chamado /dev/sdb que não contem tabelas de partições validas que é justamente o disco que adicionamos.

Iremos formata-lo no formato ext3:

De um “y” e pressione Enter para iniciar a formatação:

Após finalizar iremos monta-lo:

Podemos acessa-lo normalmente neste momento:

Faltam duas coisas para finalizarmos o procedimento neste momento, dar-lhe as permissões necessárias, irei colocar 755 e faze-lo montar automaticamente no boot na maquina.

Segue os procedimentos, então:

Com o comando vi, edite o arquivo /etc/fstab: [root@jonestby ~]# vi /etc/fstab

Agora adicione o dispositivo, o diretório onde o mesmo será montado, o formato de arquivo formatado, configurações defaults para opções de montagem e 1 1 para verificar com o fsck no boot da maquina. Salve o arquivo.

Após isto vamos rebootar a maquina e testar a “montagem” automatica do nosso novo disco.

Logue no seu sistema novamente após reiniciar, abra o terminal e execute o comando df –h, para verificar se seu disco montou automaticamente:

Está ae, agora voce tem mais 10 Giga, aproximadamente em seu Linux virtualizado via Oracle VirtualBox.

Erro “Re-link fails on target “client_sharedlib”" durante aplicação do Patch 12419392

Maycon Tomiasi — Mon, 26 Mar 2012 13:26:46 +0000

Este artigo tem como objetivo explicar o erro ocorrido “Re-link fails on target “client_sharedlib”.” durante aplicaçao do Patch PSU 10.2.0.5.4 para o Banco de Dados Oracle 10.2.0.5.0 e como corrigir o mesmo.
Estou usando um Banco de Dados Single Instance com ASM, ou seja, non-RAC.
OBS: Sempre faz backup do produto Oracle antes aplicar qualquer Patch da Oracle para voltar o mesmo caso a aplicação do Patch não ocorra com Sucesso.
OBS: Para aplicar o Patch, deve-se certificar que todos os serviços do Banco de Dados esteja baixados (Listener, Banco de Dados, Enterprise Manager, ISQLPlus).

Vamos checar a versão do OPatch e verificar se nosso Banco de Dados está baixado.

[oracle@serveroracle 12419392]$ /oraprd01/app/oracle/product/10.2.0/db_1/OPatch/opatch version
Invoking OPatch 10.2.0.5.1

OPatch Version: 10.2.0.5.1

OPatch succeeded.
[oracle@serveroracle 12419392]$ lsnrctl status

LSNRCTL for Linux: Version 10.2.0.5.0 - Production on 15-MAR-2012 16:46:18

Copyright (c) 1991, 2010, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.56.104)(PORT=1521)))
TNS-12541: TNS:no listener
 TNS-12560: TNS:protocol adapter error
  TNS-00511: No listener
   Linux Error: 111: Connection refused
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC0)))
TNS-12541: TNS:no listener
 TNS-12560: TNS:protocol adapter error
  TNS-00511: No listener
   Linux Error: 2: No such file or directory
[oracle@serveroracle 12419392]$ ps -ef | grep pmon
oracle    8371  3654  0 16:46 pts/1    00:00:00 grep pmon
[oracle@serveroracle 12419392]$

Conforme checado a versão do OPatch e o status dos serviços do Banco de Dados Oracle, vamos aplicar o Patch 12419392.

[oracle@serveroracle 12419392]$ /oraprd01/app/oracle/product/10.2.0/db_1/OPatch/opatch apply
Invoking OPatch 10.2.0.5.1

Oracle Home : /oraprd01/app/oracle/product/10.2.0/db_1
Central Inventory : /oraprd01/app/oracle/oraInventory
from : /etc/oraInst.loc
OPatch version : 10.2.0.5.1
OUI version : 10.2.0.5.0
OUI location : /oraprd01/app/oracle/product/10.2.0/db_1/oui
Log file location : /oraprd01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch2012-03-15_17-02-08PM.log

Patch history file: /oraprd01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch_history.txt

ApplySession applying interim patch '12419392' to OH '/oraprd01/app/oracle/product/10.2.0/db_1'
Interim patch 12419392 is a superset of the patch(es) [ 12419392 ] in the Oracle Home
OPatch will rollback the subset patches and apply the given patch.

Running prerequisite checks...
Patch 12419392: Optional component(s) missing : [ oracle.rdbms.dv, 10.2.0.5.0 ] , [ oracle.rdbms.dv.oc4j, 10.2.0.5.0 ]
Provide your email address to be informed of security issues, install and
initiate Oracle Configuration Manager. Easier for you if you use your My
Oracle Support Email address/User Name.
Visit http://www.oracle.com/support/policies.html for details.
Email address/User Name:

You have not provided an email address for notification of security issues.
Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: y

OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/oraprd01/app/oracle/product/10.2.0/db_1')

Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch '12419392' for restore. This might take a while...
Backing up files affected by the patch '12419392' for restore. This might take a while...
ApplySession rolling back interim patch '12419392' from OH '/oraprd01/app/oracle/product/10.2.0/db_1'
Execution of 'sh /oraprd01/app/oracle/product/10.2.0/db_1/.patch_storage/12419392_May_25_2011_01_06_08/original_patch/custom/scripts/pre -rollback 12419392 ':

Return Code = 0

Patching component oracle.rdbms.rman, 10.2.0.5.0...
Running make for target ioracle
Running make for target iwrap
Running make for target client_sharedlib
Make failed to invoke "/usr/bin/make -f ins_net_client.mk client_sharedlib ORACLE_HOME=/oraprd01/app/oracle/product/10.2.0/db_1"....'genclntsh: genclntsh: Could not locate /oraprd01/app/oracle/product/10.2.0/db_1/network/admin/shrept.lst
make: *** [client_sharedlib] Error 1
'
Running make for target proc
Running make for target irman
Running make for target client_sharedlib
Make failed to invoke "/usr/bin/make -f ins_rdbms.mk client_sharedlib ORACLE_HOME=/oraprd01/app/oracle/product/10.2.0/db_1"....'genclntsh: genclntsh: Could not locate /oraprd01/app/oracle/product/10.2.0/db_1/network/admin/shrept.lst
make: *** [client_sharedlib] Error 1
'

The following make actions have failed :

Re-link fails on target "client_sharedlib".
Re-link fails on target "client_sharedlib".

Do you want to proceed? [y|n]
y
User Responded with: Y
ApplySession adding interim patch '12419392' to inventory

Verifying the update...
Inventory check OK: Patch ID 12419392 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 12419392 are present in Oracle Home.

The local system has been patched and can be restarted.

--------------------------------------------------------------------------------
The following warnings have occurred during OPatch execution:
1) OUI-67620:Interim patch 12419392 is a superset of the patch(es) [ 12419392 ] in the Oracle Home
2) OUI-67200:Make failed to invoke "/usr/bin/make -f ins_net_client.mk client_sharedlib ORACLE_HOME=/oraprd01/app/oracle/product/10.2.0/db_1"....'genclntsh: genclntsh: Could not locate /oraprd01/app/oracle/product/10.2.0/db_1/network/admin/shrept.lst
make: *** [client_sharedlib] Error 1
'
3) OUI-67200:Make failed to invoke "/usr/bin/make -f ins_rdbms.mk client_sharedlib ORACLE_HOME=/oraprd01/app/oracle/product/10.2.0/db_1"....'genclntsh: genclntsh: Could not locate /oraprd01/app/oracle/product/10.2.0/db_1/network/admin/shrept.lst
make: *** [client_sharedlib] Error 1
'
4) OUI-67124:Re-link fails on target "client_sharedlib".
Re-link fails on target "client_sharedlib".

--------------------------------------------------------------------------------
OPatch Session completed with warnings.

OPatch completed with warnings.
[oracle@serveroracle 12419392]$

Durante o processo de aplicação do Patch, ocorreu os erros acima ao invocar o “make” para o “client_sharedlib” que não conseguiu encontrar o arquivo “shrept.lst” no diretório “/oraprd01/app/oracle/product/10.2.0/db_1/network/admin/”.
Vamos verificar se existe o arquivo.

[oracle@serveroracle 12419392]$ ls -l /oraprd01/app/oracle/product/10.2.0/db_1/network/admin/shrept.lst
ls: /oraprd01/app/oracle/product/10.2.0/db_1/network/admin/shrept.lst: No such file or directory
[oracle@serveroracle 12419392]$

Conforme acima, o arquivo não existe.
Com o usuário “oracle” realizei uma cópia do arquivo “shrept.lst” de um outro servidor de Banco de Dados e fiz uma cópia do mesmo no meu servidor de Banco de Dados no diretório “/oraprd01/app/oracle/product/10.2.0/db_1/network/admin/”.
Segue o arquivo abaixo:

[oracle@serveroracle admin]$ cat shrept.lst
# function entry points for genclntsh.sh

network : snaumihi_inithostinfo
network : snaumbg_gmt
network : naedpwd_encrypt
network : naumbsb_bld_singlebyte
network : ztapis
[oracle@serveroracle admin]$

Vamos entrar novamente no diretório do Patch e aplicar o mesmo.

[oracle@serveroracle 12419392]$ /oraprd01/app/oracle/product/10.2.0/db_1/OPatch/opatch apply
Invoking OPatch 10.2.0.5.1

Patch history file: /oraprd01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch_history.txt

You have not provided an email address for notification of security issues.
Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: y

OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/oraprd01/app/oracle/product/10.2.0/db_1')

Return Code = 0

Patching component oracle.rdbms, 10.2.0.5.0...
Updating archive file "/oraprd01/app/oracle/product/10.2.0/db_1/lib/libserver10.a" with "lib/libserver10.a/kcbl.o"
.
.
.
Patching component oracle.rdbms.rman, 10.2.0.5.0...
Running make for target ioracle
Running make for target iwrap
Running make for target client_sharedlib
Running make for target proc
Running make for target irman
Running make for target client_sharedlib
ApplySession adding interim patch '12419392' to inventory

Verifying the update...
Inventory check OK: Patch ID 12419392 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 12419392 are present in Oracle Home.

The local system has been patched and can be restarted.

--------------------------------------------------------------------------------
The following warnings have occurred during OPatch execution:
1) OUI-67620:Interim patch 12419392 is a superset of the patch(es) [ 12419392 ] in the Oracle Home
--------------------------------------------------------------------------------
OPatch Session completed with warnings.

OPatch completed with warnings.
[oracle@serveroracle 12419392]$

Pronto corrigimos o problema basta terminar o processo de aplicação do Patch 12419392 PSU 10.2.0.5.4 para o Banco de Dados Oracle 10.2.0.5.
Mais informações sobre aplicação do Patch acompanhar o arquivo README que vem junto no pacote do Patch 12419392.
Veja o artigo da Aplicação do Patch 12419392 acessando Aplicando Patch PSU 10.2.0.5.4 no Banco de Dados Oracle 10.2.0.5.0 non-RAC.

Erro “OPatch failed with error code 73″ durante aplicação do Patch 12419392.

Maycon Tomiasi — Mon, 26 Mar 2012 10:25:59 +0000

Este artigo tem como objetivo explicar o erro ocorrido “OPatch failed with error code 73″ durante aplicação do Patch PSU 10.2.0.5.4 para o Banco de Dados Oracle 10.2.0.5.0 e corrigir o mesmo.
Estou usando um Banco de Dados Single Instance com ASM, ou seja, non-RAC.

Segue os passos que foi realizado para aplicar o Patch 12419392 quando houve o erro.

Vamos acessar o diretório do Patch 12419392.

[oracle@serveroracle ~]$ cd 12419392/
[oracle@serveroracle 12419392]$ ls -l
total 64
drwxr-xr-x 3 oracle oinstall  4096 May 19  2011 custom
drwxr-xr-x 4 oracle oinstall  4096 May 19  2011 etc
drwxr-xr-x 9 oracle oinstall  4096 May 19  2011 files
-rw-r--r-- 1 oracle oinstall  2872 May 18  2011 patchmd.xml
-rw-rw-r-- 1 oracle oinstall 42226 Jul 19  2011 README.html
-rw-rw-r-- 1 oracle oinstall    21 May 25  2011 README.txt
[oracle@serveroracle 12419392]$

Ao entrar no diretório do Patch, vamos aplicar o Patch.
OBS: Para aplicar o Patch, deve-se certificar que todos os serviços do Banco de Dados esteja baixados (Listener, Banco de Dados, Enterprise Manager, ISQLPlus).
OBS: Sempre faz backup do produto Oracle antes aplicar qualquer Patch da Oracle para voltar o mesmo caso a aplicação do Patch não ocorra com Sucesso.

[oracle@serveroracle 12419392]$ /oraprd01/app/oracle/product/10.2.0/db_1/OPatch/opatch apply
Invoking OPatch 10.2.0.4.9

Oracle Interim Patch Installer version 10.2.0.4.9
Copyright (c) 2009, Oracle Corporation.  All rights reserved.

Oracle Home       : /oraprd01/app/oracle/product/10.2.0/db_1
Central Inventory : /oraprd01/app/oracle/oraInventory
   from           : /etc/oraInst.loc
OPatch version    : 10.2.0.4.9
OUI version       : 10.2.0.5.0
OUI location      : /oraprd01/app/oracle/product/10.2.0/db_1/oui
Log file location : /oraprd01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch2012-03-15_16-01-20PM.log

Patch history file: /oraprd01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch_history.txt

ApplySession applying interim patch '12419392' to OH '/oraprd01/app/oracle/product/10.2.0/db_1'
ApplySession failed: ApplySession failed to prepare the system.

Patch 12419392 requires OPatch version 10.2.0.5.0.
The OPatch version being used (10.2.0.4.9) doesn't meet the minimum version required by the patch(es). Please download latest OPatch from My Oracle Support.

System intact, OPatch will not attempt to restore the system

OPatch failed with error code 73
[oracle@serveroracle 12419392]$

O erro acima ocorreu pois nossa versão do OPatch é uma versão antiga para a aplicação do Patch 12419392 PSU 10.2.0.5.4.
Devemos acessar o Metalink (Suporte Oracle) e baixar o Patch do OPtach na versão mais nova.
Estou usando Oracle Enterprise Linux 5.7 32 Bits, então devemos baixar o OPatch para este Sistema Operacional.
Ao acessar o metalink procure pelo [ID 274526.1] e Baixe o Opatch para a versão do Banco de Dados que estás usando, no meu caso, Linux x86.

Download OPtach

Após realizar o Download do OPtach recente, faz uma copia para o servidor de Banco de Dados e descompacta o mesmo no ORACLE_HOME conforme abaixo:

[oracle@serveroracle ~]$ ls -l p6880880_102000_LINUX.zip
-rw-r--r-- 1 oracle oinstall 27412455 Mar 15 16:37 p6880880_102000_LINUX.zip
[oracle@serveroracle ~]$ cp -p p6880880_102000_LINUX.zip /oraprd01/app/oracle/product/10.2.0/db_1/
[oracle@serveroracle ~]$ cd /oraprd01/app/oracle/product/10.2.0/db_1/
[oracle@serveroracle db_1]$ unzip p6880880_102000_LINUX.zip
Archive:  p6880880_102000_LINUX.zip
 extracting: OPatch/ocm/ocm.zip
  inflating: OPatch/ocm/lib/osdt_jce.jar
  inflating: OPatch/ocm/lib/osdt_core3.jar
  inflating: OPatch/ocm/lib/emocmclnt-14.jar
replace OPatch/ocm/lib/emocmutl.jar? [y]es, [n]o, [A]ll, [N]one, [r]ename: A
  inflating: OPatch/ocm/lib/emocmutl.jar
  inflating: OPatch/ocm/bin/emocmrsp
  inflating: OPatch/ocm/ocm_platforms.txt
  inflating: OPatch/crs/patch112.pl
  inflating: OPatch/crs/crsdelete.pm
  inflating: OPatch/crs/crspatch.pm
  inflating: OPatch/crs/s_crsconfig_defs
  inflating: OPatch/crs/crsconfig_lib.pm
  inflating: OPatch/crs/oracss.pm
  inflating: OPatch/crs/auto_patch.pl
  inflating: OPatch/crs/s_crsconfig_lib.pm
  inflating: OPatch/opatch
  inflating: OPatch/opatchprereqs/opatch/runtime_prereq.xml
  inflating: OPatch/opatchprereqs/opatch/opatch_prereq.xml
  inflating: OPatch/opatchprereqs/opatch/rulemap.xml
  inflating: OPatch/opatchprereqs/prerequisite.properties
  inflating: OPatch/opatchprereqs/oui/knowledgesrc.xml
  inflating: OPatch/opatch.ini
  inflating: OPatch/emdpatch.pl
  inflating: OPatch/opatch.pl
  inflating: OPatch/jlib/opatchprereq.jar
  inflating: OPatch/jlib/opatchactions.jar
  inflating: OPatch/jlib/opatchutil.jar
  inflating: OPatch/jlib/opatchfmw.jar
  inflating: OPatch/jlib/opatchext.jar
  inflating: OPatch/jlib/opatch.jar
  inflating: OPatch/opatch.bat
  inflating: OPatch/docs/Prereq_Users_Guide.txt
  inflating: OPatch/docs/FAQ
  inflating: OPatch/docs/Users_Guide.txt
  inflating: OPatch/README.txt
[oracle@serveroracle db_1]$

Após descompactar o OPatch recente para o ORACLE_HOME vamos checar a versão do OPatch.

[oracle@serveroracle db_1]$ /oraprd01/app/oracle/product/10.2.0/db_1/OPatch/opatch version
Invoking OPatch 10.2.0.5.1

OPatch Version: 10.2.0.5.1

OPatch succeeded.

Conforme checado a versão do OPatch, o mesmo é 10.2.0.5.1 o que é recomendável para aplicar o Patch 12419392 para o Banco de Dados 10.2.0.5.
Veja o artigo da Aplicação do Patch 12419392 acessando Aplicando Patch PSU 10.2.0.5.4 no Banco de Dados Oracle 10.2.0.5.0 non-RAC.

Aplicando Patch PSU 10.2.0.5.4 no Banco de Dados Oracle 10.2.0.5.0 non-RAC

Maycon Tomiasi — Fri, 23 Mar 2012 12:52:17 +0000

Este artigo tem como objetivo explicar como aplicar o Patch PSU 10.2.0.5.4 para o Banco de Dados Oracle 10.2.0.5.0.
Estou usando um Banco de Dados Single Instance com ASM, ou seja, non-RAC.

Primeiramente devemos baixar o Patch 12419392. Estou usando Oracle Enterprise Linux 5.7 32 Bits, então devemos baixar o Patch para este Sistema Operacional.
Para baixar o Patch terás que obter as o suporte da Oracle.
Ao baixar o Patch copia o mesmo para o servidor de Banco de Dados e descompacta o mesmo com “unzip”.

Segue abaixo os passos para aplicar o Patch PSU 10.2.0.5.4.

[oracle@serveroracle ~]$ cd 12419392/
[oracle@serveroracle 12419392]$ ls -l
total 64
drwxr-xr-x 3 oracle oinstall  4096 May 19  2011 custom
drwxr-xr-x 4 oracle oinstall  4096 May 19  2011 etc
drwxr-xr-x 9 oracle oinstall  4096 May 19  2011 files
-rw-r--r-- 1 oracle oinstall  2872 May 18  2011 patchmd.xml
-rw-rw-r-- 1 oracle oinstall 42226 Jul 19  2011 README.html
-rw-rw-r-- 1 oracle oinstall    21 May 25  2011 README.txt
[oracle@serveroracle 12419392]$

Vamos verificar se está faltando algum pacote do Linux para a aplicação do Patch.

[oracle@serveroracle 12419392]$ rpm -q binutils gcc glibc glibc-headers glibc-kernheaders glibc-devel compat-libstdc++ cpp compat-gcc make compat-db compat-gcc-c++ compat-libstdc++ compat-libstdc++-devel openmotif openmotif21 setarch pdksh libaio libaio-devel
binutils-2.17.50.0.6-14.el5
gcc-4.1.2-51.el5
glibc-2.5-65
glibc-headers-2.5-65
package glibc-kernheaders is not installed
glibc-devel-2.5-65
package compat-libstdc++ is not installed
cpp-4.1.2-51.el5
package compat-gcc is not installed
make-3.81-3.el5
compat-db-4.2.52-5.1
package compat-gcc-c++ is not installed
package compat-libstdc++ is not installed
package compat-libstdc++-devel is not installed
openmotif-2.3.1-5.el5_5.1
package openmotif21 is not installed
setarch-2.0-1.1
package pdksh is not installed
libaio-0.3.106-5
package libaio-devel is not installed
[oracle@serveroracle 12419392]$

Com o usuário “root” vamos instalar alguns pacotes do Linux que não estão instalados.
OBS: Estes são pacotes complementais para instalação e gerenciamento dos aplicativos.

Em um outro terminal com o usuário “root” vamos instalar os pacotes do Linux.

[root@serveroracle Server]# ls -l  glibc-headers-*
-rw-r--r-- 1 root root 618371 Jun 14  2011 glibc-headers-2.5-65.i386.rpm
[root@serveroracle Server]# rpm -ivh glibc-headers-2.5-65.i386.rpm
warning: glibc-headers-2.5-65.i386.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Preparing...                ########################################### [100%]
        package glibc-headers-2.5-65.i386 is already installed
[root@serveroracle Server]# ls -l glibc-devel-2.5-65*
-rw-r--r-- 1 root root 2143738 Jun 14  2011 glibc-devel-2.5-65.i386.rpm
[root@serveroracle Server]# rpm -ivh glibc-devel-2.5-65.i386.rpm
warning: glibc-devel-2.5-65.i386.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Preparing...                ########################################### [100%]
        package glibc-devel-2.5-65.i386 is already installed
[root@serveroracle Server]# ls -l cpp-4.1.2-51.el5*
-rw-r--r-- 1 root root 2779549 Jun 14  2011 cpp-4.1.2-51.el5.i386.rpm
[root@serveroracle Server]# rpm -ivh cpp-4.1.2-51.el5.i386.rpm
warning: cpp-4.1.2-51.el5.i386.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Preparing...                ########################################### [100%]
        package cpp-4.1.2-51.el5.i386 is already installed
[root@serveroracle Server]# ls -l compat-gcc*
-rw-r--r-- 1 root root  4217682 Nov 17  2010 compat-gcc-34-3.4.6-4.1.i386.rpm
-rw-r--r-- 1 root root 11392445 Nov 17  2010 compat-gcc-34-c++-3.4.6-4.1.i386.rpm
-rw-r--r-- 1 root root  2171879 Nov 17  2010 compat-gcc-34-g77-3.4.6-4.1.i386.rpm
[root@serveroracle Server]# rpm -ivh compat-gcc-34-c++-3.4.6-4.1.i386.rpm
warning: compat-gcc-34-c++-3.4.6-4.1.i386.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Preparing...                ########################################### [100%]
        package compat-gcc-34-c++-3.4.6-4.1.i386 is already installed
[root@serveroracle Server]# ls -l make-3.81-3.el5*
-rw-r--r-- 1 root root 477805 Nov 17  2010 make-3.81-3.el5.i386.rpm
[root@serveroracle Server]# rpm -ivh make-3.81-3.el5.i386.rpm
warning: make-3.81-3.el5.i386.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Preparing...                ########################################### [100%]
        package make-3.81-3.el5.i386 is already installed
        file /usr/bin/make from install of make-3.81-3.el5.i386 conflicts with file from package make-3.81-3.el5.i386
[root@serveroracle Server]# ls -l compat-libstdc++*
-rw-r--r-- 1 root root  92219 Nov 17  2010 compat-libstdc++-296-2.96-138.i386.rpm
-rw-r--r-- 1 root root 237144 Nov 17  2010 compat-libstdc++-33-3.2.3-61.i386.rpm
[root@serveroracle Server]# rpm -ivh compat-libstdc++-33-3.2.3-61.i386.rpm
warning: compat-libstdc++-33-3.2.3-61.i386.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Preparing...                ########################################### [100%]
        package compat-libstdc++-33-3.2.3-61.i386 is already installed
        file /usr/lib/libstdc++.so.5.0.7 from install of compat-libstdc++-33-3.2.3-61.i386 conflicts with file from package compat-libstdc++-33-3.2.3-61.i386
[root@serveroracle Server]# rpm -ivh compat-libstdc++-296-2.96-138.i386.rpm
warning: compat-libstdc++-296-2.96-138.i386.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Preparing...                ########################################### [100%]
        package compat-libstdc++-296-2.96-138.i386 is already installed
        file /usr/lib/libstdc++-3-libc6.2-2-2.10.0.so from install of compat-libstdc++-296-2.96-138.i386 conflicts with file from package compat-libstdc++-296-2.96-138.i386
[root@serveroracle Server]# ls -l openmotif*
-rw-r--r-- 1 root root 1374499 Nov 17  2010 openmotif22-2.2.3-18.i386.rpm
-rw-r--r-- 1 root root 1610158 Nov  3  2010 openmotif-2.3.1-5.el5_5.1.i386.rpm
-rw-r--r-- 1 root root 3102338 Nov  3  2010 openmotif-devel-2.3.1-5.el5_5.1.i386.rpm
[root@serveroracle Server]# rpm -ivh openmotif22-2.2.3-18.i386.rpm
warning: openmotif22-2.2.3-18.i386.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Preparing...                ########################################### [100%]
   1:openmotif22            ########################################### [100%]
[root@serveroracle Server]# ls -l pdksh*
-rw-r--r-- 1 root root 203568 Nov 17  2010 pdksh-5.2.14-36.el5.i386.rpm
[root@serveroracle Server]# rpm -ivh pdksh-5.2.14-36.el5.i386.rpm
warning: pdksh-5.2.14-36.el5.i386.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Preparing...                ########################################### [100%]
   1:pdksh                  ########################################### [100%]
[root@serveroracle Server]# ls -l libaio-devel*
-rw-r--r-- 1 root root 11790 Nov 17  2010 libaio-devel-0.3.106-5.i386.rpm
[root@serveroracle Server]# rpm -ivh libaio-devel-0.3.106-5.i386.rpm
warning: libaio-devel-0.3.106-5.i386.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159
Preparing...                ########################################### [100%]
   1:libaio-devel           ########################################### [100%]
[root@serveroracle Server]#

Vamos aplicar o Patch 12419392.

[oracle@serveroracle 12419392]$ /oraprd01/app/oracle/product/10.2.0/db_1/OPatch/opatch apply
Invoking OPatch 10.2.0.5.1

Patch history file: /oraprd01/app/oracle/product/10.2.0/db_1/cfgtoollogs/opatch/opatch_history.txt

You have not provided an email address for notification of security issues.
Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: y

OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/oraprd01/app/oracle/product/10.2.0/db_1')

Return Code = 0

Verifying the update...
Inventory check OK: Patch ID 12419392 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 12419392 are present in Oracle Home.

The local system has been patched and can be restarted.

--------------------------------------------------------------------------------
The following warnings have occurred during OPatch execution:
1) OUI-67620:Interim patch 12419392 is a superset of the patch(es) [ 12419392 ] in the Oracle Home
--------------------------------------------------------------------------------
OPatch Session completed with warnings.

OPatch completed with warnings.
[oracle@serveroracle 12419392]$

Após o Patch Aplicado vamos continuar o processo de aplicação no Banco de Dados. Vamos subir os serviços do Banco de Dados.
Subindo o Listener.

[oracle@serveroracle 12419392]$ lsnrctl start

LSNRCTL for Linux: Version 10.2.0.5.0 - Production on 15-MAR-2012 17:52:43

Copyright (c) 1991, 2010, Oracle.  All rights reserved.

Starting /oraprd01/app/oracle/product/10.2.0/db_1/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version 10.2.0.5.0 - Production
System parameter file is /oraprd01/app/oracle/product/10.2.0/db_1/network/admin/listener.ora
Log messages written to /oraprd01/app/oracle/product/10.2.0/db_1/network/log/listener.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.56.104)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC0)))

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.56.104)(PORT=1521)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 10.2.0.5.0 - Production
Start Date                15-MAR-2012 17:52:43
Uptime                    0 days 0 hr. 0 min. 0 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /oraprd01/app/oracle/product/10.2.0/db_1/network/admin/listener.ora
Listener Log File         /oraprd01/app/oracle/product/10.2.0/db_1/network/log/listener.log
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.56.104)(PORT=1521)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC0)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
  Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "dbprod" has 1 instance(s).
  Instance "dbprod", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
[oracle@serveroracle 12419392]$

Vamos subir a Instância ASM.

[oracle@serveroracle 12419392]$ export ORACLE_SID=+ASM
[oracle@serveroracle 12419392]$ sqlplus sys/***** as sysdba

SQL*Plus: Release 10.2.0.5.0 - Production on Thu Mar 15 17:55:10 2012

Copyright (c) 1982, 2010, Oracle.  All Rights Reserved.

Connected to an idle instance.

SQL> startup mount
ASM instance started

Total System Global Area   83886080 bytes
Fixed Size                  1272120 bytes
Variable Size              57448136 bytes
ASM Cache                  25165824 bytes
ASM diskgroups mounted
SQL> exit
Disconnected from Oracle Database 10g Release 10.2.0.5.0 - Production
[oracle@serveroracle 12419392]$ export ORACLE_SID=dbprod
[oracle@serveroracle 12419392]$ sqlplus sys/***** as sysdba

SQL*Plus: Release 10.2.0.5.0 - Production on Thu Mar 15 17:55:57 2012

Copyright (c) 1982, 2010, Oracle.  All Rights Reserved.

Connected to an idle instance.

SQL> startup
ORACLE instance started.

Total System Global Area 1073741824 bytes
Fixed Size                  1277824 bytes
Variable Size             541065344 bytes
Database Buffers          524288000 bytes
Redo Buffers                7110656 bytes
Database mounted.
Database opened.
SQL>

Com o Banco de Dados aberto, vamos continuar a aplicar o Patch no Banco de Dados.

SQL> @$ORACLE_HOME/rdbms/admin/catbundle.sql psu apply

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

Generating apply and rollback scripts...
Check the following file for errors:
/oraprd01/app/oracle/product/10.2.0/db_1/cfgtoollogs/catbundle/catbundle_PSU_DBPROD_GENERATE_2012Mar15_18_12_45.log
Apply script: /oraprd01/app/oracle/product/10.2.0/db_1/rdbms/admin/catbundle_PSU_DBPROD_APPLY.sql
Rollback script: /oraprd01/app/oracle/product/10.2.0/db_1/rdbms/admin/catbundle_PSU_DBPROD_ROLLBACK.sql

PL/SQL procedure successfully completed.

Executing script file...

SQL> COLUMN spool_file NEW_VALUE spool_file NOPRINT
SQL> SELECT '/oraprd01/app/oracle/product/10.2.0/db_1/cfgtoollogs/catbundle/' || 'catbundle_PSU_' || name || '_APPLY_' || TO_CHAR(SYSDATE, 'YYYYMonDD_hh24_mi_ss', 'NLS_DATE_LANGUAGE=''AMERICAN''') || '.log' AS spool_file FROM v$database;

SQL> SPOOL &spool_file
SQL> exec dbms_registry.set_session_namespace('SERVER')

PL/SQL procedure successfully completed.

SQL> PROMPT Processing Oracle Enterprise Manager...
Processing Oracle Enterprise Manager...
SQL> ALTER SESSION SET current_schema = SYSMAN;

Session altered.

SQL> @?/sysman/admin/emdrep/sql/core/latest/ecm/ecm_util_pkgdef.sql
.
.
.
SQL> SET TERMOUT on
SQL> SET ECHO off

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

Session altered.

Updating registry...

1 row created.

Commit complete.

Check the following log file for errors:
/oraprd01/app/oracle/product/10.2.0/db_1/cfgtoollogs/catbundle/catbundle_PSU_DBPROD_APPLY_2012Mar15_18_12_46.log
SQL>

Após rodar o “catbundle.sql” vamos rodar o “utlrp.sql” para recompilar os objetos.

SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql

TIMESTAMP
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_BGN  2012-03-15 18:20:24

DOC>   The following PL/SQL block invokes UTL_RECOMP to recompile invalid
DOC>   objects in the database. Recompilation time is proportional to the
DOC>   number of invalid objects in the database, so this command may take
DOC>   a long time to execute on a database with a large number of invalid
DOC>   objects.
DOC>
DOC>   Use the following queries to track recompilation progress:
DOC>
DOC>   1. Query returning the number of invalid objects remaining. This
DOC>      number should decrease with time.
DOC>         SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
DOC>
DOC>   2. Query returning the number of objects compiled so far. This number
DOC>      should increase with time.
DOC>         SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
DOC>
DOC>   This script automatically chooses serial or parallel recompilation
DOC>   based on the number of CPUs available (parameter cpu_count) multiplied
DOC>   by the number of threads per CPU (parameter parallel_threads_per_cpu).
DOC>   On RAC, this number is added across all RAC nodes.
DOC>
DOC>   UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
DOC>   recompilation. Jobs are created without instance affinity so that they
DOC>   can migrate across RAC nodes. Use the following queries to verify
DOC>   whether UTL_RECOMP jobs are being created and run correctly:
DOC>
DOC>   1. Query showing jobs created by UTL_RECOMP
DOC>         SELECT job_name FROM dba_scheduler_jobs
DOC>            WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>
DOC>   2. Query showing UTL_RECOMP jobs that are running
DOC>         SELECT job_name FROM dba_scheduler_running_jobs
DOC>            WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>#

PL/SQL procedure successfully completed.

TIMESTAMP
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_END  2012-03-15 18:20:30

PL/SQL procedure successfully completed.

DOC> The following query reports the number of objects that have compiled
DOC> with errors (objects that compile with errors have status set to 3 in
DOC> obj$). If the number is higher than expected, please examine the error
DOC> messages reported with each object (using SHOW ERRORS) to see if they
DOC> point to system misconfiguration or resource constraints that must be
DOC> fixed before attempting to recompile these objects.
DOC>#

OBJECTS WITH ERRORS
-------------------
                  0

DOC> The following query reports the number of errors caught during
DOC> recompilation. If this number is non-zero, please query the error
DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
DOC> are due to misconfiguration or resource constraints that must be
DOC> fixed before objects can compile successfully.
DOC>#

ERRORS DURING RECOMPILATION
---------------------------
                          0

PL/SQL procedure successfully completed.

SQL>

Vamos verificar se aplicamos o Patch PSU corretamente.

SQL> col COMMENTS for a30
SQL> select ACTION, NAMESPACE, VERSION, BUNDLE_SERIES, COMMENTS from dba_registry_history;

ACTION                         NAMESPACE                      VERSION                        BUNDLE_SERIES                  COMMENTS
------------------------------ ------------------------------ ------------------------------ ------------------------------ ------------------------------
APPLY                          SERVER                         10.2.0.5                       PSU                            PSU 10.2.0.5.4

SQL>

Conforme informações no DBA_REGISTRY_HISTORY podemos concluir que aplicamos o Patch corretamente.
Mais informações sobre aplicação do Patch acompanhar o arquivo README que vem junto no pacote do Patch 12419392.