- Página 3 de 6 - zmsolution

AdminServer em Cluster?

9 de maio de 2019 vanberto zuim Apps, EBS, Oracle BPM, Oracle SOA Suite, OSB, Weblogic

Todos Sabemos que não é possível subir o Admin Server em Cluster, mas se ele for configurado corretamente, poderá ser iniciado iniciado em qualquer nó. O erro que mais ocorre quando tentamos subir o Admin Server em outro Nó do Cluster é:

1. weblogic.security.SecurityInitializationException: Authentication for user weblogic denied.
2. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.security.SecurityService
3. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.jndi.internal.RemoteNamingService errors were found
4. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.jndi.internal.RemoteNamingService
5. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.connector.common.ConnectorServiceActivator errors were found
6. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.connector.common.ConnectorServiceActivator

A MultiException has 6 exceptions. They are:
1. weblogic.security.SecurityInitializationException: Authentication for user weblogic denied.
2. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.security.SecurityService
3. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.jndi.internal.RemoteNamingService errors were found
4. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.jndi.internal.RemoteNamingService
5. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.connector.common.ConnectorServiceActivator errors were found
6. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.connector.common.ConnectorServiceActivator

1. weblogic.security.SecurityInitializationException: Authentication for user weblogic denied.

2. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.security.SecurityService

3. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.jndi.internal.RemoteNamingService errors were found

4. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.jndi.internal.RemoteNamingService

5. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.connector.common.ConnectorServiceActivator errors were found

6. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.connector.common.ConnectorServiceActivator

A MultiException has 6 exceptions. They are:

1. weblogic.security.SecurityInitializationException: Authentication for user weblogic denied.

2. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.security.SecurityService

3. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.jndi.internal.RemoteNamingService errors were found

4. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.jndi.internal.RemoteNamingService

5. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.connector.common.ConnectorServiceActivator errors were found

6. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.connector.common.ConnectorServiceActivator

Isso ocorre devido as credencias do Admin Server não estarem corretas nos outros Nós. Para solucionar o problem existe uma saídas simples, copiar a pasta data do Admin Server existente em outros[…]

PL/SQL package RMAN.DBMS_RCVCAT version 11.02.00.04 in RCVCAT database is too old

26 de abril de 2019 vanberto zuim Database

Quandos possuímos bancos na versão 12c e tentamos catalogar o banco em uma versão 11g , ocorrera o seguinte erro: PL/SQL package RMAN.DBMS_RCVCAT version 11.02.00.04 in RCVCAT database is too old Esse erro ocorre devido ao catalogo do rman esta desatualizado. a resolução desse problema é bem simples

[oracle@zmsolution1~]$ rman target / catalog rman/zuim@rman

Recovery Manager: Release 12.2.0.1.0 - Production on Thu Apr 25 16:50:34 2019

Copyright (c) 1982, 2017, Oracle and/or its affiliates.  All rights reserved.

connected to target database: ZUIMDB(DBID=1268148162)
 connected to recovery catalog database
 PL/SQL package RMAN.DBMS_RCVCAT version 11.02.00.04 in RCVCAT database is too old

RMAN> register database;

PL/SQL package RMAN.DBMS_RCVCAT version 11.02.00.04 in RCVCAT database is too old
 PL/SQL package RMAN.DBMS_RCVCAT version 11.02.00.04 in RCVCAT database is too old
 RMAN-00571: ===========================================================
 RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
 RMAN-00571: ===========================================================
 RMAN-03002: failure of register command at 04/25/2019 16:55:06
 RMAN-06429: RCVCAT database is not compatible with this version of RMAN

RMAN> upgrade catalog;

recovery catalog upgraded to version 12.02.00.01
 DBMS_RCVMAN package upgraded to version 12.02.00.01
 DBMS_RCVCAT package upgraded to version 12.02.00.01.

RMAN> register database;

database registered in recovery catalog
 starting full resync of recovery catalog
 full resync complete

RMAN>

[oracle@zmsolution1~]$ rman target / catalog rman/zuim@rman

Recovery Manager: Release 12.2.0.1.0 - Production on Thu Apr 25 16:50:34 2019

connected to target database: ZUIMDB(DBID=1268148162)

connected to recovery catalog database

PL/SQL package RMAN.DBMS_RCVCAT version 11.02.00.04 in RCVCAT database is too old

RMAN> register database;

PL/SQL package RMAN.DBMS_RCVCAT version 11.02.00.04 in RCVCAT database is too old

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of register command at 04/25/2019 16:55:06

RMAN-06429: RCVCAT database is not compatible with this version of RMAN

RMAN> upgrade catalog;

recovery catalog upgraded to version 12.02.00.01

DBMS_RCVMAN package upgraded to version 12.02.00.01

DBMS_RCVCAT package upgraded to version 12.02.00.01.

RMAN> register database;

database registered in recovery catalog

starting full resync of recovery catalog

full resync complete

RMAN>

Error occurred while waiting for ICM to go down

3 de agosto de 2018 vanberto zuim EBS

Em alguns momentos quando realizamos o procedimento de Cutover no EBS 12.2, podemos nos deparar com algum tipo de problema, um deles é o erro abaixo:

Waiting for ICM to go down...
[UNEXPECTED]Error while trying to find the status of ICM
[UNEXPECTED]Error occurred while waiting for ICM to go down
[UNEXPECTED]Cutover phase completed with errors/warnings. Please check logfiles
[STATEMENT] Please run adopscanlog utility, using the command

Waiting for ICM to go down...

[UNEXPECTED]Error while trying to find the status of ICM

[UNEXPECTED]Error occurred while waiting for ICM to go down

[UNEXPECTED]Cutover phase completed with errors/warnings. Please check logfiles

[STATEMENT] Please run adopscanlog utility, using the command

Esse erro pode ocorrer se o gerenciador de concurrent estiver fora ou se tivermos algum problema na configuração do arquivo .dbc no diretório $FND_SECURE

[applzmuser@zmsolution ~]$ adop phase=cutover

Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:

Validating credentials...

Initializing...
Run Edition context : /ebs/fs1/inst/apps/ebszm_ebszm/appl/admin/ebszm_ebszm.xml
Patch edition context: /ebs/fs2/inst/apps/ebszm_ebszm/appl/admin/ebszm_ebszm.xml
Patch file system freespace: 92.56 GB

Validating system setup...
Node registry is valid.

Checking for pending adop sessions...
Continuing with existing session [Session id: 159]...
Session Id : 159
Prepare phase status : COMPLETED
Apply phase status : COMPLETED
Cutover phase status : NOT COMPLETED
Abort phase status : NOT COMPLETED
Session status : FAILED

===========================================================================
ADOP (C.Delta.6)
Session ID: 159
Node: ebsqa
Phase: cutover
Log: /ebs/fs_ne/EBSapps/log/adop/159/adop_20180802_150633.log
===========================================================================

Validating configuration on node: [ebszm]...
Log: /ebs/fs_ne/EBSapps/log/adop/159/cutover_20180802_150633/ebsqa_ebsqa

Checking if finalize required...
Finalize phase steps are not required

Submitting request for ICM shutdown...
cp wait parameter passed with value: N\n

You are running adcmctl.sh version 120.19.12020000.4

Shutting down concurrent managers for ebsqa ...
ORACLE Password:
Submitted request 87111032 for CONCURRENT FND SHUTDOWN
adcmctl.sh: exiting with status 0
adcmctl.sh: check the logfile /ebs/fs1/inst/apps/ebszm_ebszm/logs/appl/admin/log/adcmctl.txt for more information ...

Cancelling ADZDPATCH concurrent request

Waiting for ICM to go down...
[UNEXPECTED]Error while trying to find the status of ICM
[UNEXPECTED]Error occurred while waiting for ICM to go down
[UNEXPECTED]Cutover phase completed with errors/warnings. Please check logfiles
[STATEMENT] Please run adopscanlog utility, using the command

"adopscanlog -latest=yes"

to get the list of the log files along with snippet of the error message corresponding to each log file.

files

[applzmuser@zmsolution ~]$ adop phase=cutover

Enter the APPS password:

Enter the SYSTEM password:

Enter the WLSADMIN password:

Validating credentials...

Initializing...

Run Edition context : /ebs/fs1/inst/apps/ebszm_ebszm/appl/admin/ebszm_ebszm.xml

Patch edition context: /ebs/fs2/inst/apps/ebszm_ebszm/appl/admin/ebszm_ebszm.xml

Patch file system freespace: 92.56 GB

Validating system setup...

Node registry is valid.

Checking for pending adop sessions...

Continuing with existing session [Session id: 159]...

Session Id : 159

Prepare phase status : COMPLETED

Apply phase status : COMPLETED

Cutover phase status : NOT COMPLETED

Abort phase status : NOT COMPLETED

Session status : FAILED

===========================================================================

ADOP (C.Delta.6)

Session ID: 159

Node: ebsqa

Phase: cutover

Log: /ebs/fs_ne/EBSapps/log/adop/159/adop_20180802_150633.log

===========================================================================

Validating configuration on node: [ebszm]...

Log: /ebs/fs_ne/EBSapps/log/adop/159/cutover_20180802_150633/ebsqa_ebsqa

Checking if finalize required...

Finalize phase steps are not required

Submitting request for ICM shutdown...

cp wait parameter passed with value: N\n

You are running adcmctl.sh version 120.19.12020000.4

Shutting down concurrent managers for ebsqa ...

ORACLE Password:

Submitted request 87111032 for CONCURRENT FND SHUTDOWN

adcmctl.sh: exiting with status 0

adcmctl.sh: check the logfile /ebs/fs1/inst/apps/ebszm_ebszm/logs/appl/admin/log/adcmctl.txt for more information ...

Cancelling ADZDPATCH concurrent request

Waiting for ICM to go down...

[UNEXPECTED]Error while trying to find the status of ICM

[UNEXPECTED]Error occurred while waiting for ICM to go down

[UNEXPECTED]Cutover phase completed with errors/warnings. Please check logfiles

[STATEMENT] Please run adopscanlog utility, using the command

"adopscanlog -latest=yes"

to get the list of the log files along with snippet of the error message corresponding to each log file.

files

para a resolução do problema sera necessário primeiro avaliar se o gerenciador de concurrent está no ar, se o gerenciador estiver funcionando corretamente , valide se[…]

Instalando o Oracle RAC 12c no OL6 Usando VirtualBox 5

5 de junho de 2018 vanberto zuim Database

Neste artigo vamos instalar o Oracle RAC 12c (12.1) no Oracle Linux 6 Usando VirtualBox 5, preferi iniciar pelo Oracle 12.1, para podermos realizar a migração para o Oracle 12.2 em um novo artigo. Para começar vamos baixar os instaladores do Oracle. Oracle Database 12c Release 1 (12.1.0.2.0) for Linux x86-64 http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html Oracle Database 12c Release 1 Grid Infrastructure (12.1.0.2.0) for Linux x86-64 http://www.oracle.com/technetwork/database/enterprise-edition/downloads/database12c-linux-download-2240591.html Criando a Máquina Virtual Antes de iniciar, crie uma pasta com o[…]

ORA-28040: No matching authentication protocol ocilogon():

8 de maio de 2018 vanberto zuim Database

Uma Solução de contorno para o erro é , acessar o diretório $ORACLE_HOME/network/admin/ e adicionar os parâmetros abaixo no sqlnet.ora. SQLNET.ALLOWED_LOGON_VERSION_SERVER=8 SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8

cd $ORACLE_HOME/network/admin/

vi sqlnet.ora

SQLNET.ALLOWED_LOGON_VERSION_SERVER=8
SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8

cd $ORACLE_HOME/network/admin/

vi sqlnet.ora

SQLNET.ALLOWED_LOGON_VERSION_SERVER=8

SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8

Can’t locate Env.pm in @INC

25 de abril de 2018 vanberto zuim Database

O erro abaixo ocorreu quando eu tentava executar o rootcrs.pl -unlock no banco oracle 12.2 com OL7

[root@zmsolution1install]# ./rootcrs.pl -unlock
Can't locate Env.pm in @INC (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 . . ./../../perl/lib) at crsinstall.pm line 286.
BEGIN failed--compilation aborted at crsinstall.pm line 286.
Compilation failed in require at ./rootcrs.pl line 165.
BEGIN failed--compilation aborted at ./rootcrs.pl line 165.

[root@zmsolution1install]# ./rootcrs.pl -unlock

Can't locate Env.pm in @INC (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 . . ./../../perl/lib) at crsinstall.pm line 286.

BEGIN failed--compilation aborted at crsinstall.pm line 286.

Compilation failed in require at ./rootcrs.pl line 165.

BEGIN failed--compilation aborted at ./rootcrs.pl line 165.

Para solucionar o problema executei uma busca com o comando locate para saber onde tinha o arquivo e após copiei para o diretorio que o Oracle estava buscando.

locate Env.pm

/u01/app/oracle/product/12.2.0/db_1/perl/lib/5.22.0/Env.pm
/u01/app/oracle/product/12.2.0/db_1/perl/lib/5.22.0/TAP/Harness/Env.pm
/u01/app/oracle/product/12.2.0/grid/perl/lib/5.22.0/Env.pm
/u01/app/oracle/product/12.2.0/grid/perl/lib/5.22.0/TAP/Harness/Env.pm
/u01/install/grid/perl/lib/5.22.0/Env.pm
/u01/install/grid/perl/lib/5.22.0/TAP/Harness/Env.pm

locate Env.pm

/u01/app/oracle/product/12.2.0/db_1/perl/lib/5.22.0/Env.pm

/u01/app/oracle/product/12.2.0/db_1/perl/lib/5.22.0/TAP/Harness/Env.pm

/u01/app/oracle/product/12.2.0/grid/perl/lib/5.22.0/Env.pm

/u01/app/oracle/product/12.2.0/grid/perl/lib/5.22.0/TAP/Harness/Env.pm

/u01/install/grid/perl/lib/5.22.0/Env.pm

/u01/install/grid/perl/lib/5.22.0/TAP/Harness/Env.pm

cp /u01/install/grid/perl/lib/5.22.0/Env.pm /usr/share/perl5/vendor_perl

1	cp /u01/install/grid/perl/lib/5.22.0/Env.pm /usr/share/perl5/vendor_perl

Agora vou executar o comando novamente.

[root@zmsolution1 install]# ./rootcrs.pl -unlock
Using configuration parameter file: ./crsconfig_params
The log of current session can be found at:
  /u01/app/oracle/crsdata/s00lnx95/crsconfig/crsunlock_s00lnx95_2018-04-24_12-05-58AM.log
2018/04/24 12:06:08 CLSRSC-357: Failed to stop current Oracle Clusterware stack during upgrade
2018/04/24 12:06:09 CLSRSC-347: Successfully unlock /u01/app/oracle/product/12.2.0/grid
[root@zmsolution1  install]#

[root@zmsolution1 install]# ./rootcrs.pl -unlock

Using configuration parameter file: ./crsconfig_params

The log of current session can be found at:

/u01/app/oracle/crsdata/s00lnx95/crsconfig/crsunlock_s00lnx95_2018-04-24_12-05-58AM.log

2018/04/24 12:06:08 CLSRSC-357: Failed to stop current Oracle Clusterware stack during upgrade

2018/04/24 12:06:09 CLSRSC-347: Successfully unlock /u01/app/oracle/product/12.2.0/grid

[root@zmsolution1 install]#

ORA-00600: internal error code, arguments: [kcratr_nab_less_than_odr]

18 de abril de 2018 vanberto zuim Database

Em bases que o archivelog não esta ativado corremos muitos riscos, entre ele o risco de termos o erro: ORA-00600: internal error code, arguments: [kcratr_nab_less_than_odr] , esse erro podo ocorrer de muitas formas : This Problem is caused by Storage Problem of the Database Files. The Subsystem (eg. SAN) crashed while the Database was open. The Database then crashed because the Database Files were not accessible anymore. This caused a lost Write into the Online RedoLogs[…]

Criando um Cluster no Oracle SOA Suite 12c

15 de abril de 2018 vanberto zuim Apps, Oracle BPM, Oracle SOA Suite, OSB, Weblogic

Neste artigo vamos aprender como criar um Cluster no Oracle SOA Suíte 12C. Para quem está chegando agora e quer saber um pouco mais sobre a instalação do Oracle SOA Suite, sugiro dar uma olhada nos artigos abaixo. Parte 1: Preparando e Instalando o Banco de Dados Parte 2: Preparando e Instalando o Oracle SOA Suíte Parte 3: Configurações necessárias do Oracle SOA Suíte Acesse a console administrativa do Weblogic Clique em Lock & Edit Clique em Servers Clique em[…]

Aplicando Patch no Oracle SOA Suíte 12.2.1.3

3 de abril de 2018 vanberto zuim Oracle BPM, Oracle SOA Suite, OSB, Weblogic

No Oracle SOA Suíte 10.3 existiam três formas de aplicação de Patch: OPATCH,BSU e PSA O OPATCH funciona para patchs no Oracle Home, o BSU que funciona para no weblogic e PSU funciona para patchs no FMW schemas que no caso são os esquemas de banco que criamos com o rca. Acho bem interessante fazer esse comentário sobre o Oracle SOA Suíte 10.3 devido a maioria dos produtos Oracle ainda funcionarem em cima dessa versão[…]

Instalando o Oracle Https Server 12.2.1.3

26 de março de 2018 vanberto zuim Apps, EBS, Oracle BPM, Oracle SOA Suite, OSB, Weblogic

Hoje vamos instalar o Oracle Https Server 12.2.1.3. O OHS facilita bastante na hora de trabalharmos com balanceamento e alta disponibilidade do Oracle SOA Suite. Para quem está chegando agora e quer saber mais sobre como instalar o Oracle SOA Suite, aconselho dar uma olhada nas nossas matérias anteriores. Parte 1: Preparando e Instalando o Banco de Dados Parte 2: Preparando e Instalando o Oracle SOA Suíte Parte 3: Configurações necessárias do Oracle SOA Suíte O Oracle Https Server será configurado na mesma máquina em[…]