Erro após a finalização do clone no EBS 12.2

Enter password: ERROR: ORA-00604: error occurred at recursive SQL level 1 ORA-20099: E-Business Suite Patch Edition does not exist. ORA-06512: at line 29 1 – Verifique se o parâmetro esta ativo: select value from v$parameter where name=’_system_trig_enabled’; Se não tiver , altere o init.ora e adicione o parâmetro como true 2-Se estiver tudo Ok com o parâmetro, analise a tabela  applsys.TXK_TCC_RESULTS na tabela pode existir linhas duplicadas, se a linha estiver duplicada, elimine uma das linhas[…]

Read more

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

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

Read more

ORA-06512: at “APPS.FND_CP_FNDSM”

O erro ORA-06512: at “APPS.FND_CP_FNDSM” pode fazer com que o gerenciador de concurrent do Oracle EBS pare de Funcionar Cause: cleanup_node failed due to ORA-01427: single-row subquery returns more than one row ORA-06512: at “APPS.FND_CP_FNDSM”, line 91 ORA-06512: at line 1. Para solucionar o problema  execute o select abaixo: select * from FND_CONCURRENT_QUEUES where MANAGER_TYPE = 6   se retorna duas linhas com manager_type=6, elimine a linha que não esta aparecendo no log dos concurrents.[…]

Read more

Alterando o CHARACTER do Oracle

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;     Cuidado..valide bem antes antes de fazer isso..

Read more