- zmsolution

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 ~]#

Erro no Clone EBS12.2.7

22 de outubro de 2019 vanberto zuim EBS

O erro ocorre na hora da execução do clone do patch System File Edition.

/u01/app/oracle/fs1/EBSapps/comn/clone/bin/../jre/bin/java -Xmx600M -DCONTEXT_VALIDATED=true -Doracle.installer.oui_loc=/oui -classpath /u01/app/oracle/fs1/EBSapps/comn/clone/jlib/xmlparserv2.jar:/u01/app/oracle/fs1/EBSapps/comn/clone/jlib/ojdbc6.jar:/u01/app/oracle/fs1/EBSapps/comn/clone/jlib/java:/u01/app/oracle/fs1/EBSapps/comn/clone/jlib/oui/OraInstaller.jar:/u01/app/oracle/fs1/EBSapps/comn/clone/jlib/oui/ewt3.jar:/u01/app/oracle/fs1/EBSapps/comn/clone/jlib/oui/share.jar:/u01/app/oracle/fs1/FMW_Home/webtier/../Oracle_EBS-app1/oui/jlib/srvm.jar:/u01/app/oracle/fs1/EBSapps/comn/clone/jlib/ojmisc.jar:/u01/app/oracle/fs1/FMW_Home/wlserver_10.3/server/lib/weblogic.jar:/u01/app/oracle/fs1/EBSapps/comn/clone/jlib/obfuscatepassword.jar oracle.apps.ad.clone.ApplyAppsTier -e /u01/app/oracle/fs1/inst/apps/ebshmg_ebshmgapp/appl/admin/ebshmg_ebshmgapp.xml -stage /u01/app/oracle/fs1/EBSapps/comn/clone -showProgress -nopromptmsg
Log file located at /u01/app/oracle/fs1/inst/apps/ebshmg_ebshmgapp/admin/log/clone/ApplyAppsTier_10212035.log
/ 100% completed
ERROR while running Apply...
Mon Oct 21 21:02:32 2019

Enabling EBS_LOGON Trigger...

ERROR: Failed to execute /u01/app/oracle/fs1/EBSapps/comn/clone/bin/adclone.pl

/u01/app/oracle/fs1/EBSapps/comn/clone/bin/../jre/bin/java -Xmx600M -DCONTEXT_VALIDATED=true -Doracle.installer.oui_loc=/oui -classpath /u01/app/oracle/fs1/EBSapps/comn/clone/jlib/xmlparserv2.jar:/u01/app/oracle/fs1/EBSapps/comn/clone/jlib/ojdbc6.jar:/u01/app/oracle/fs1/EBSapps/comn/clone/jlib/java:/u01/app/oracle/fs1/EBSapps/comn/clone/jlib/oui/OraInstaller.jar:/u01/app/oracle/fs1/EBSapps/comn/clone/jlib/oui/ewt3.jar:/u01/app/oracle/fs1/EBSapps/comn/clone/jlib/oui/share.jar:/u01/app/oracle/fs1/FMW_Home/webtier/../Oracle_EBS-app1/oui/jlib/srvm.jar:/u01/app/oracle/fs1/EBSapps/comn/clone/jlib/ojmisc.jar:/u01/app/oracle/fs1/FMW_Home/wlserver_10.3/server/lib/weblogic.jar:/u01/app/oracle/fs1/EBSapps/comn/clone/jlib/obfuscatepassword.jar oracle.apps.ad.clone.ApplyAppsTier -e /u01/app/oracle/fs1/inst/apps/ebshmg_ebshmgapp/appl/admin/ebshmg_ebshmgapp.xml -stage /u01/app/oracle/fs1/EBSapps/comn/clone -showProgress -nopromptmsg

Log file located at /u01/app/oracle/fs1/inst/apps/ebshmg_ebshmgapp/admin/log/clone/ApplyAppsTier_10212035.log

/ 100% completed

ERROR while running Apply...

Mon Oct 21 21:02:32 2019

Enabling EBS_LOGON Trigger...

ERROR: Failed to execute /u01/app/oracle/fs1/EBSapps/comn/clone/bin/adclone.pl

Erro:

SEVERE : oct 21, 2019 6:26:12 AM - ERROR - CLONE-20372 Server port validation failed.
SEVERE : oct 21, 2019 6:26:12 AM - CAUSE - CLONE-20372 Ports of following servers - oacore_server2(7226),forms_server2(7
426),oafm_server2(7626),forms-c4ws_server2(7826) - are not available.
SEVERE : oct 21, 2019 6:26:12 AM - ACTION - CLONE-20372 Provide valid free ports.
oracle.as.t2p.exceptions.FMWT2PPasteConfigException: PasteConfig failed. Make sure that the move plan and the values specified in moveplan are correct.

SEVERE : oct 21, 2019 6:26:12 AM - ERROR - CLONE-20372 Server port validation failed.

SEVERE : oct 21, 2019 6:26:12 AM - CAUSE - CLONE-20372 Ports of following servers - oacore_server2(7226),forms_server2(7

426),oafm_server2(7626),forms-c4ws_server2(7826) - are not available.

SEVERE : oct 21, 2019 6:26:12 AM - ACTION - CLONE-20372 Provide valid free ports.

oracle.as.t2p.exceptions.FMWT2PPasteConfigException: PasteConfig failed. Make sure that the move plan and the values specified in moveplan are correct.

Communication error with the OPMN server local port.
Check the OPMN log files
SEVERE : Mar 31, 2015 3:37:31 PM - ERROR - CLONE-20218   Cloning is not 
successful.
SEVERE : Mar 31, 2015 3:37:31 PM - CAUSE - CLONE-20218   An internal 
operation failed.
SEVERE : Mar 31, 2015 3:37:31 PM - ACTION - CLONE-20218   Provide the clone 
log and error file for investigation.
oracle.as.clone.cloner.exception.ApplyCloneException:  Instance "Create &amp; 
Start" step  failed.

Communication error with the OPMN server local port.

Check the OPMN log files

SEVERE : Mar 31, 2015 3:37:31 PM - ERROR - CLONE-20218 Cloning is not

successful.

SEVERE : Mar 31, 2015 3:37:31 PM - CAUSE - CLONE-20218 An internal

operation failed.

SEVERE : Mar 31, 2015 3:37:31 PM - ACTION - CLONE-20218 Provide the clone

log and error file for investigation.

oracle.as.clone.cloner.exception.ApplyCloneException: Instance "Create &

Start" step failed.

Para a solução do problema, Antes de iniciar o clone do patch File system, execute o comando abaixo:

 export T2P_JAVA_OPTIONS="-Dt2p.temporary.port.range=5001-5050"
 ./adcfgclone.pl appsTier

1 2	export T2P_JAVA_OPTIONS="-Dt2p.temporary.port.range=5001-5050" ./adcfgclone.pl appsTier

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.

Habilitando o vnc no Exadata

2 de outubro de 2019 vanberto zuim Exadata

Para habilitar o VNC no exadata instale os pacotes abaixo:

yum install xorg-x11-xauth

yum install xorg-x11-utils

yum install xterm

yum install twm

yum install tigervnc-server

yum install xorg-x11-xauth

yum install xorg-x11-utils

yum install xterm

yum install twm

yum install tigervnc-server

Apos instalar os pacotes entre no usuário oracle e execute os comandos abaixo:

su – oracle

vncpasswd

vncserver

su – oracle

vncpasswd

vncserver

PO Output For Communication Performance is very slow

1 de outubro de 2019 vanberto zuim EBS

Alguns dias tivemos um problema de lentidão no concurrent PO Output For Communication , apos um grande período de analise ,verificamos que a lentidão esta ocorrendo na geração do PDF do concurrent . pesquisei bastante sobre o que poderia estar causando essa lentidão e acabei encontrando o seguinte note no metalink: PO Output For Communication Performance Issues But SQL Trace Show No Performance Problems (Doc ID 1575175.1) o que explica a oracle sobre o problema: This is[…]

How to Replace a Hard Drive in an Exadata Storage Server (Predictive Failure) X7

2 de setembro de 2019 vanberto zuim Exadata

Segue um How to para alterar um disco no exadata (Predictive Failure)) 1- Encontre o disco que deve ser alterado. Normalmente a oracle envia no SR um texto assim: Slot Number: 6 Drive’s postion: DiskGroup: 6, Span: 0, Arm: 0 Enclosure position: 0 Device Id: 9 WWN: 5000CCA267226EC7 Sequence Number: 2 Media Error Count: 83 <<<<<<<<<<<<<<<<< Other Error Count: 187 <<<<<<<<<<<<<<<<<<<<<<<< Predictive Failure Count: 0 Last Predictive Failure Event Seq Number: 0 PD Type: SAS Para[…]

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;