Arquivos Database -

OPATCHAUTO-72141: Execute opatchauto in non-rolling mode.

1 de novembro de 2019 vanberto zuim Database, Exadata

O erro OPATCHAUTO-72141 ocorre devido a um bug:

As part of bug 26367944, development added a validation to enforce user to pass -nonrolling along with opatchauto in single node GI.

So mentioned error message is coming is due to this fix, hence –nonrolling has to be passed to avoid this error. This is already present in 12.2.0.1.10.

As part of bug 26367944, development added a validation to enforce user to pass -nonrolling along with opatchauto in single node GI.

So mentioned error message is coming is due to this fix, hence –nonrolling has to be passed to avoid this error. This is already present in 12.2.0.1.10.

Vamos para a solução do problema:

[root@zmmaq1~]# $ORACLE_HOME/OPatch/opatchauto apply /u01/install/psu/30116789/

OPatchauto session is initiated at Fri Nov 1 11:53:06 2019

System initialization log file is /u01/app/19.3.0.0/grid/cfgtoollogs/opatchautodb/systemconfig2019-11-01_11-53-08AM.log.

Session log file is /u01/app/19.3.0.0/grid/cfgtoollogs/opatchauto/opatchauto2019-11-01_11-53-11AM.log
The id for this session is KJMJ
OPATCHAUTO-72141: Grid patching cannot be performed in rolling mode.
OPATCHAUTO-72141: Grid is installed only on a single node.
OPATCHAUTO-72141: Execute opatchauto in non-rolling mode.
OPatchAuto failed.

OPATCHAUTO-72141: Grid patching cannot be performed in rolling mode.
OPATCHAUTO-72141: Grid is installed only on a single node.
OPATCHAUTO-72141: Execute opatchauto in non-rolling mode.
OPatchAuto failed.

[root@zmmaq1~]# $ORACLE_HOME/OPatch/opatchauto apply /u01/install/psu/30116789/

OPatchauto session is initiated at Fri Nov 1 11:53:06 2019

System initialization log file is /u01/app/19.3.0.0/grid/cfgtoollogs/opatchautodb/systemconfig2019-11-01_11-53-08AM.log.

Session log file is /u01/app/19.3.0.0/grid/cfgtoollogs/opatchauto/opatchauto2019-11-01_11-53-11AM.log

The id for this session is KJMJ

OPATCHAUTO-72141: Grid patching cannot be performed in rolling mode.

OPATCHAUTO-72141: Grid is installed only on a single node.

OPATCHAUTO-72141: Execute opatchauto in non-rolling mode.

OPatchAuto failed.

OPATCHAUTO-72141: Grid patching cannot be performed in rolling mode.

OPATCHAUTO-72141: Grid is installed only on a single node.

OPATCHAUTO-72141: Execute opatchauto in non-rolling mode.

OPatchAuto failed.

Adicione nonrolling no comando do patch

[root@zmmaq1~]# $ORACLE_HOME/OPatch/opatchauto apply /u01/install/psu/30116789/ -nonrolling

OPatchauto session is initiated at Fri Nov 1 11:55:44 2019

System initialization log file is /u01/app/19.3.0.0/grid/cfgtoollogs/opatchautodb/systemconfig2019-11-01_11-55-46AM.log.

Session log file is /u01/app/19.3.0.0/grid/cfgtoollogs/opatchauto/opatchauto2019-11-01_11-55-49AM.log
The id for this session is M6BD

Executing OPatch prereq operations to verify patch applicability on home /u01/app/19.3.0.0/grid
Patch applicability verified successfully on home /u01/app/19.3.0.0/grid


Bringing down CRS service on home /u01/app/19.3.0.0/grid
CRS service brought down successfully on home /u01/app/19.3.0.0/grid


Start applying binary patch on home /u01/app/19.3.0.0/grid
Binary patch applied successfully on home /u01/app/19.3.0.0/grid


Starting CRS service on home /u01/app/19.3.0.0/grid
CRS service started successfully on home /u01/app/19.3.0.0/grid

OPatchAuto successful.

--------------------------------Summary--------------------------------

Patching is completed successfully. Please find the summary as follows:

Host:zmmaq1
CRS Home:/u01/app/19.3.0.0/grid
Version:19.0.0.0.0
Summary:

==Following patches were SKIPPED:

Patch: /u01/install/psu/30116789/29401763
Reason: This patch is already been applied, so not going to apply again.


==Following patches were SUCCESSFULLY applied:

Patch: /u01/install/psu/30116789/30122149
Log: /u01/app/19.3.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2019-11-01_11-58-42AM_1.log

Patch: /u01/install/psu/30116789/30122167
Log: /u01/app/19.3.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2019-11-01_11-58-42AM_1.log

Patch: /u01/install/psu/30116789/30125133
Log: /u01/app/19.3.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2019-11-01_11-58-42AM_1.log

OPatchauto session completed at Fri Nov 1 12:08:15 2019
Time taken to complete the session 12 minutes, 31 seconds
[root@zmmaq1 ~]#

[root@zmmaq1~]# $ORACLE_HOME/OPatch/opatchauto apply /u01/install/psu/30116789/ -nonrolling

OPatchauto session is initiated at Fri Nov 1 11:55:44 2019

System initialization log file is /u01/app/19.3.0.0/grid/cfgtoollogs/opatchautodb/systemconfig2019-11-01_11-55-46AM.log.

Session log file is /u01/app/19.3.0.0/grid/cfgtoollogs/opatchauto/opatchauto2019-11-01_11-55-49AM.log

The id for this session is M6BD

Executing OPatch prereq operations to verify patch applicability on home /u01/app/19.3.0.0/grid

Patch applicability verified successfully on home /u01/app/19.3.0.0/grid

Bringing down CRS service on home /u01/app/19.3.0.0/grid

CRS service brought down successfully on home /u01/app/19.3.0.0/grid

Start applying binary patch on home /u01/app/19.3.0.0/grid

Binary patch applied successfully on home /u01/app/19.3.0.0/grid

Starting CRS service on home /u01/app/19.3.0.0/grid

CRS service started successfully on home /u01/app/19.3.0.0/grid

OPatchAuto successful.

--------------------------------Summary--------------------------------

Patching is completed successfully. Please find the summary as follows:

Host:zmmaq1

CRS Home:/u01/app/19.3.0.0/grid

Version:19.0.0.0.0

Summary:

==Following patches were SKIPPED:

Patch: /u01/install/psu/30116789/29401763

Reason: This patch is already been applied, so not going to apply again.

==Following patches were SUCCESSFULLY applied:

Patch: /u01/install/psu/30116789/30122149

Log: /u01/app/19.3.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2019-11-01_11-58-42AM_1.log

Patch: /u01/install/psu/30116789/30122167

Log: /u01/app/19.3.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2019-11-01_11-58-42AM_1.log

Patch: /u01/install/psu/30116789/30125133

Log: /u01/app/19.3.0.0/grid/cfgtoollogs/opatchauto/core/opatch/opatch2019-11-01_11-58-42AM_1.log

OPatchauto session completed at Fri Nov 1 12:08:15 2019

Time taken to complete the session 12 minutes, 31 seconds

[root@zmmaq1 ~]#

Treinamento Oracle 19c Administrator

7 de outubro de 2019 vanberto zuim Database

Turma confirmada para o dia 18/11/2019!

Erro netca

2 de outubro de 2019 vanberto zuim Database

O erro: Use another port number . The information provided for this listener is currently in use by other software on this computer. You can proceed with the configuration as it is, but it will not be possible to start this listener until the conflict is resolved. Pode ocorrer se o arquivo /etc/hosts estiver configurado errado. Analise a configuração correta e execute novamente o netca.

OEM13c – The page has expired. Click OK to continue

2 de agosto de 2019 vanberto zuim Database

Na tela de monitoramento dos bancos no OEM13c, normalmente apos 45 minutos a sessão expira e é necessário realizar um novo login, , para resolvermos esse problema é bem simples. busque pelo parâmetro oracle.sysman.eml.maxInactiveTime e em definições globais, coloque -1 Problema resolvido!

Clonando o Oracle_Home

17 de julho de 2019 vanberto zuim Database

Em muitas ocasiões ,é bem mais fácil para um dba clona um ORACLE_HOME existente do que tentar criar um novo, Abaixo segue o passo a passo para realizar o clone do ORACLE_HOME . 1. Como Root entre na pasta do oracle_base e zip o oracle Home

cd /u01/app/oracle/db1

tar -cvzf /u01/home_11.2.0.4.tgz 11.2.0.4

tar -cvzf home_11.2.0.4.tgz 11.2.0.4

cd /u01/app/oracle/db1

tar -cvzf /u01/home_11.2.0.4.tgz 11.2.0.4

tar -cvzf home_11.2.0.4.tgz 11.2.0.4

2. Copie o arquivo home_11.2.0.4.tgz para o servidor de banco 3. Descompacte o arquivo com o usuário root na estrutura desejada

tar -xvf home_11.2.0.4.tgz

tar -xzvf home_11.2.0.4.tgz

tar -xvf home_11.2.0.4.tgz

tar -xzvf home_11.2.0.4.tgz

4. Entre na pasta 11.2.0.4 depoiso comando abaixo com os valores[…]

Alterando um datafile no standby

5 de julho de 2019 vanberto zuim Database

Quando um datafile é criado no banco de produção e o diskgroup ou a partição não está mapeada no standby, pode ocorrer o erro abaixo:

ORA-01119: erro ao criar o arquivo '+dg1_zmsolution' de banco de dados
ORA-17502: ksfdcre:4 Falhou ao criar o arquivo +dg1_zmsolution
ORA-15001: grupo de discos "DG1_ZMSOLUTION" não existe ou não está montado
ORA-15001: diskgroup "DG1_ZMSOLUTION" does not exist or is not mounted
File #198 added to control file as 'UNNAMED00198'.
Originally created as:
'+DG1_ZMSOLUTION/zmdb/datafile/zuim_ts_tx_data.280.1008514969'
Recovery was unable to create the file as:
'+dg1_zmsolution'
Errors with log +DG_FRA/zmdb/zuim_arc_1_131660_890817996.dbf
MRP0: Background Media Recovery terminated with error 1274
Errors in file /u01/app/zmdb/diag/rdbms/zmdbsty/zmdbsty1/trace/zmdbsty1_pr00_7388.trc:
ORA-01274: não é possível adicionar o arquivo de dados '+DG1_ZMSOLUTION/zmdb/datafile/zuim_ts_tx_data.280.1008514969' - o arquivo não pôde ser criado
Recovery interrupted!
Fri May 17 16:20:59 2019
Recovery stopped due to failure in applying recovery marker (opcode 17.30).
Datafiles are recovered to a consistent state at change 6189833565041 but controlfile could be ahead of datafiles.
Fri May 17 16:20:59 2019
MRP0: Background Media Recovery process shutdown (zmdbsty1)

ORA-01119: erro ao criar o arquivo '+dg1_zmsolution' de banco de dados

ORA-17502: ksfdcre:4 Falhou ao criar o arquivo +dg1_zmsolution

ORA-15001: grupo de discos "DG1_ZMSOLUTION" não existe ou não está montado

ORA-15001: diskgroup "DG1_ZMSOLUTION" does not exist or is not mounted

File #198 added to control file as 'UNNAMED00198'.

Originally created as:

'+DG1_ZMSOLUTION/zmdb/datafile/zuim_ts_tx_data.280.1008514969'

Recovery was unable to create the file as:

'+dg1_zmsolution'

Errors with log +DG_FRA/zmdb/zuim_arc_1_131660_890817996.dbf

MRP0: Background Media Recovery terminated with error 1274

Errors in file /u01/app/zmdb/diag/rdbms/zmdbsty/zmdbsty1/trace/zmdbsty1_pr00_7388.trc:

ORA-01274: não é possível adicionar o arquivo de dados '+DG1_ZMSOLUTION/zmdb/datafile/zuim_ts_tx_data.280.1008514969' - o arquivo não pôde ser criado

Recovery interrupted!

Fri May 17 16:20:59 2019

Recovery stopped due to failure in applying recovery marker (opcode 17.30).

Datafiles are recovered to a consistent state at change 6189833565041 but controlfile could be ahead of datafiles.

Fri May 17 16:20:59 2019

MRP0: Background Media Recovery process shutdown (zmdbsty1)

O procedimento para altera a localização do datafile é bem simples . altere o standby_file_management para manual

alter system set standby_file_management='manual';

1	alter system set standby_file_management='manual';

Criei o novo datafile levando em questão o datafile criado fora de ordem.

alter database create datafile '/u01/app/zmdb/product/11.2.0.4/dbs/UNNAMED00023' as '+DG4/zmdbsty/datafile/zuim_ts_tx_data.262';

1	alter database create datafile '/u01/app/zmdb/product/11.2.0.4/dbs/UNNAMED00023' as '+DG4/zmdbsty/datafile/zuim_ts_tx_data.262';

Altere o standby_file_management para Automático

alter system set standby_file_management='auto';

1	alter system set standby_file_management='auto';

Habilite novamente a replicação.

recover managed standby database disconnect;

1	recover managed standby database disconnect;

OPatch requires a response file for Oracle Configuration Manager (OCM).

19 de junho de 2019 vanberto zuim Database

Erro no Opatch.. 🙁

Verifying environment and performing prerequisite checks...
UtilSession failed:
To run in silent mode, OPatch requires a response file for Oracle Configuration Manager (OCM).
Please run "/tmp/oracle-home-156017296682832/OPatch/ocm/bin/emocmrsp" to generate an OCM response file. The generated response file
can be reused on different platforms and in multiple OPatch silent installs.
To regenerate an OCM response file, Please rerun "/tmp/oracle-home-156017296682832/OPatch/ocm/bin/emocmrsp".
Log file location: /u01/app/sa/product/11.2.0.4/db_1/cfgtoollogs/opatch/opatch2019-06-10_10-22-53AM_1.log
OPatch failed with error code 73

Para Resolução :
Execute
$ORACLE_HOME/OPatch/ocm/bin/emocmrsp

Altere a permissão do arquivo 
chmod 775 ocm.rsp

Execute o opatch com a clausula <strong>- ocmrf</strong>
 /u01/app/oracle/product/11.2.0.4/db_1/OPatch/opatch apply -silent -ocmrf /u01/ocm.rsp

Verifying environment and performing prerequisite checks...

UtilSession failed:

To run in silent mode, OPatch requires a response file for Oracle Configuration Manager (OCM).

Please run "/tmp/oracle-home-156017296682832/OPatch/ocm/bin/emocmrsp" to generate an OCM response file. The generated response file

can be reused on different platforms and in multiple OPatch silent installs.

To regenerate an OCM response file, Please rerun "/tmp/oracle-home-156017296682832/OPatch/ocm/bin/emocmrsp".

Log file location: /u01/app/sa/product/11.2.0.4/db_1/cfgtoollogs/opatch/opatch2019-06-10_10-22-53AM_1.log

OPatch failed with error code 73

Para Resolução :

Execute

$ORACLE_HOME/OPatch/ocm/bin/emocmrsp

Altere a permissão do arquivo

chmod 775 ocm.rsp

Execute o opatch com a clausula <strong>- ocmrf</strong>

/u01/app/oracle/product/11.2.0.4/db_1/OPatch/opatch apply -silent -ocmrf /u01/ocm.rsp

Alterando o CHARACTER do Oracle

3 de junho de 2019 vanberto zuim Database, Não categorizado

Nesse post vamos altera o CHARACTER do banco de dados Oracle.

conn / as sysdba
sho parameter CLUSTER_DATABASE
sho parameter PARALLEL_SERVER
2. Execute the following commands in sqlplus connected as "/ AS SYSDBA":

conn / as sysdba

SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
ALTER SYSTEM ENABLE RESTRICTED SESSION;
ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;
ALTER SYSTEM SET AQ_TM_PROCESSES=0;
ALTER DATABASE OPEN;
ALTER DATABASE CHARACTER SET INTERNAL_USE WE8ISO8859P1;
SHUTDOWN IMMEDIATE;

conn / as sysdba

sho parameter CLUSTER_DATABASE

sho parameter PARALLEL_SERVER

2. Execute the following commands in sqlplus connected as "/ AS SYSDBA":

conn / as sysdba

SHUTDOWN IMMEDIATE;

STARTUP MOUNT;

ALTER SYSTEM ENABLE RESTRICTED SESSION;

ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;

ALTER SYSTEM SET AQ_TM_PROCESSES=0;

ALTER DATABASE OPEN;

ALTER DATABASE CHARACTER SET INTERNAL_USE WE8ISO8859P1;

SHUTDOWN IMMEDIATE;

Cuidado..valide bem antes antes de fazer isso..

Erro ORA-25226 após import com impdp

17 de maio de 2019 vanberto zuim Database, EBS, Oracle BPM, Oracle SOA Suite, OSB

As vezes realizamos o import de um sistema que possui queue, normalmente após o import ocorre o seguinte erro: ORA-25226 dequeue failed queue not enabled for dequeue, para solucionar esse erro é bem simples, apos o import habilite novamente as queues. segue o comando abaixo:

select para verificar a QUEUE

SQL> select OWNER,NAME,QUEUE_TABLE,ENQUEUE_ENABLED,DEQUEUE_ENABLED from dba_queues where NAME='EVENT_QUEUE';

OWNER NAME
------------------------------ ------------------------------
QUEUE_TABLE ENQUEUE DEQUEUE
------------------------------ ------- -------
STRMADMIN EVENT_QUEUE
EVENT_QUEUE_TAB NO NO

execute o comando com sys para habilitar a queue

EXECUTE DBMS_AQADM.start_queue (queue_name => 'strmadmin.event_queue',enqueue=> TRUE,dequeue=> TRUE);

select para verificar a QUEUE

SQL> select OWNER,NAME,QUEUE_TABLE,ENQUEUE_ENABLED,DEQUEUE_ENABLED from dba_queues where NAME='EVENT_QUEUE';

OWNER NAME

------------------------------ ------------------------------

QUEUE_TABLE ENQUEUE DEQUEUE

------------------------------ ------- -------

STRMADMIN EVENT_QUEUE

EVENT_QUEUE_TAB NO NO

execute o comando com sys para habilitar a queue

EXECUTE DBMS_AQADM.start_queue (queue_name => 'strmadmin.event_queue',enqueue=> TRUE,dequeue=> TRUE);

ORA-31623: a job is not attached to this session via the specified handle

13 de maio de 2019 vanberto zuim Database

O erro ORA-31623 ocorre algumas vezes na hora de executar um expdp, isso ocorre devido o parametro streams_pool_size está com o valor 0 Vamos corrigir o problema.

[oraclezm@zmdb1~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.4.0 Production on Sun May 12 17:11:42 2019

Copyright (c) 1982, 2013, Oracle. All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
Data Mining and Real Application Testing options

SQL> show parameter stream

NAME TYPE
------------------------------------ --------------------------------
VALUE
------------------------------
streams_pool_size big integer
0
SQL> alter system set streams_pool_size=64M scope=both;
alter system set streams_pool_size=64M scope=both
*
ERROR at line 1:
ORA-32001: write to SPFILE requested but no SPFILE is in use


SQL> alter system set streams_pool_size=64M scope=memory;

System altered.

SQL>

[oraclezm@zmdb1~]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.4.0 Production on Sun May 12 17:11:42 2019

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production

With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,

Data Mining and Real Application Testing options

SQL> show parameter stream

NAME TYPE

------------------------------------ --------------------------------

VALUE

------------------------------

streams_pool_size big integer

SQL> alter system set streams_pool_size=64M scope=both;

alter system set streams_pool_size=64M scope=both

ERROR at line 1:

ORA-32001: write to SPFILE requested but no SPFILE is in use

SQL> alter system set streams_pool_size=64M scope=memory;

System altered.

SQL>