- Página 3 de 7 - zmsolution

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>

RMAN-20020: database incarnation not set

12 de maio de 2019 vanberto zuim Database, Não categorizado

Quando tentamos fazer a ressincronização do catálogo com o banco de dados de destino, se recebermos a menssagem RMAN-20020: database incarnation not set, então temos que redefinir o banco de dados para definir a encarnação para o atual.

Step 1
connect to  rman and connect to the target database with recovery catalog
rman
Recovery Manager: Release 11.2.0.4.0 - Production 
Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
 
connect target /
connected to target database: <SID> (DBID=<database_id>)
 
connect catalog rman/<password>@<catalog database service name>
connected to recovery catalog database

Step2

RMAN> resync catalog
2> ;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of resync command on default channel at 05/14/2013 13:36:02
RMAN-20020: database incarnation not set

RMAN> backup datafile <file_number>;
Starting backup at 14-MAY-13
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 05/14/2013 13:37:14
RMAN-03014: implicit resync of recovery catalog failed
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20020: database incarnation not set

Step 3
once you got the incarnation not set check the list of incarnation the database has

 list incarnation ;
List of Database Incarnations
DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
------- ------- -------- ---------------- --- ---------- ----------
29      360     ZMDB    728861074        PARENT  1          05-MAR-18
29      361    ZMDB    728861074       PARENT  14640435   08-JUN-18
29      98      ZMDB   728861074        PARENT  14882874888 22-JUN-18
29      30      ZMDB   728861074        ORPHAN  15574861795 11-JUL-18
29      321    ZMDB    728861074       CURRENT 15996977185 22-AUG-18


SQL> select * from v$controlfile_record_section where TYPE ='DATABASE INCARNATION';

TYPE                         RECORD_SIZE RECORDS_TOTAL RECORDS_USED FIRST_INDEX LAST_INDEX LAST_RECID
---------------------------- ----------- ------------- ------------ ----------- ---------- ----------
DATABASE INCARNATION                  56           292            4           1          4          4

we can check the no of database incarnations in the database control file ...

Step 4
To sync the incarnation number with the catalog issue the Reset the database  command in the rman 
and test the backup

RMAN> reset database;

database incarnation already registered

RMAN> backup datafile 3;
Starting backup at 14-MAY-13
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=4256 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00003 name=+DATA/fahdb/datafile/<datafile_number>
channel ORA_DISK_1: starting piece 1 at 14-MAY-13
channel ORA_DISK_1: finished piece 1 at 14-MAY-13
piece handle=+FLASH/fahdb/backupset/2013_05_14/nnndf0_tag20130514t135843_0.282.815407125 tag=TAG20130514T135843 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07
Finished backup at 14-MAY-13
Starting Control File and SPFILE Autobackup at 14-MAY-13
piece handle=+FLASH/fahdb/autobackup/2013_05_14/s_815407132.326.815407133 comment=NONE
Finished Control File and SPFILE Autobackup at 14-MAY-13

RMAN> resync catalog ;
starting full resync of recovery catalog
full resync complete

Step 1

connect to rman and connect to the target database with recovery catalog

rman

Recovery Manager: Release 11.2.0.4.0 - Production

connect target /

connected to target database: <SID> (DBID=<database_id>)

connect catalog rman/<password>@<catalog database service name>

connected to recovery catalog database

Step2

RMAN> resync catalog

2> ;

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

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

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

RMAN-03009: failure of resync command on default channel at 05/14/2013 13:36:02

RMAN-20020: database incarnation not set

RMAN> backup datafile <file_number>;

Starting backup at 14-MAY-13

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

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

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

RMAN-03002: failure of backup command at 05/14/2013 13:37:14

RMAN-03014: implicit resync of recovery catalog failed

RMAN-06004: ORACLE error from recovery catalog database: RMAN-20020: database incarnation not set

Step 3

once you got the incarnation not set check the list of incarnation the database has

list incarnation ;

List of Database Incarnations

DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time

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

29 360 ZMDB 728861074 PARENT 1 05-MAR-18

29 361 ZMDB 728861074 PARENT 14640435 08-JUN-18

29 98 ZMDB 728861074 PARENT 14882874888 22-JUN-18

29 30 ZMDB 728861074 ORPHAN 15574861795 11-JUL-18

29 321 ZMDB 728861074 CURRENT 15996977185 22-AUG-18

SQL> select * from v$controlfile_record_section where TYPE ='DATABASE INCARNATION';

TYPE RECORD_SIZE RECORDS_TOTAL RECORDS_USED FIRST_INDEX LAST_INDEX LAST_RECID

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

DATABASE INCARNATION 56 292 4 1 4 4

we can check the no of database incarnations in the database control file ...

Step 4

To sync the incarnation number with the catalog issue the Reset the database command in the rman

and test the backup

RMAN> reset database;

database incarnation already registered

RMAN> backup datafile 3;

Starting backup at 14-MAY-13

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=4256 device type=DISK

channel ORA_DISK_1: starting full datafile backup set

channel ORA_DISK_1: specifying datafile(s) in backup set

input datafile file number=00003 name=+DATA/fahdb/datafile/<datafile_number>

channel ORA_DISK_1: starting piece 1 at 14-MAY-13

channel ORA_DISK_1: finished piece 1 at 14-MAY-13

piece handle=+FLASH/fahdb/backupset/2013_05_14/nnndf0_tag20130514t135843_0.282.815407125 tag=TAG20130514T135843 comment=NONE

channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07

Finished backup at 14-MAY-13

Starting Control File and SPFILE Autobackup at 14-MAY-13

piece handle=+FLASH/fahdb/autobackup/2013_05_14/s_815407132.326.815407133 comment=NONE

Finished Control File and SPFILE Autobackup at 14-MAY-13

RMAN> resync catalog ;

starting full resync of recovery catalog

full resync complete

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[…]