Buenas a todos!! Este sería mi primer entrada del 2023 y como ya estamos con la versión 12.2.12 de EBS, me parecio interesante volver un poco para atras y guiarlos en los pasos que se deben tomar en cuenta para el upgrade de 12.2.10 a 12.2.11. (serían los mismos para 12.2.12)
Antes de seguir, me ayudarian si siguen el blog: SEGUIR !! Gracias
Les dejo los blog de Oracle con los anuncios:
EBS 12.2.11 https://blogs.oracle.com/ebstech/post/oracle-e-business-suite-12211-now-available
EBS 12.2.12 https://blogs.oracle.com/ebstech/post/oracle-e-business-suite-12212-now-available
Notas Importantes:
Oracle E-Business Suite Release 12.2.11 Readme (MOS Note 2758997.1)After Upgrade Of EBS From 12.2.10 To 12.2.11 PA_PPCC_ECC_PVT Is Invalid (Doc ID 2878294.1)
Oracle E-Business Suite Release 12.2.11 Readme (Doc ID 2758997.1)
Patch 17537119: EBS 12.2 TECHNOLOGY CODELEVEL CHECKER (ETCC)
Oracle E-Business Suite Release 12.2 System Schema Migration (Doc ID 2755875.1)
- Chequeos de Sanidad , previos a cualquier cambio.
- Ejecutar ETCC y aplicar los parches
- Upgrade AD and TXK
- update Filesystem y appsutil nodo DB
- Sync FileSystem
- ValidarADOP
- Aplicar Parche 12.2.11
- Aplicar Online Help Patch
- Migrar objetos sys/system a EBS_SYSTEM (paso importante si nunca se realizo, obligatorio a partir de AD 13)
- Update snapshot
- preclone db
- preclone as
- autoconfig db
- autoconfig as
- reinicio de servicios.
- Validar Objetos descompilados actuales
Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1) tomar en cuenta que para 12.2.12 ya esta la versión AD 14. 2.1
Apply Required Database Patches Los parches del punto 2.1 de la nota fueron cumplidos al instalar los
parches del ETCC en los pasos previos. Section
3: Apply R12.AD.C.Delta.13 and R12.TXK.C.Delta.13 Release Update Packs Abrimos la nota de la sección 6 y descargamos el último AD and TXK Vamos a omitir el análisis de toda la nota y vamos a los puntos
importantes. Download
and unzip the following patches into the $PATCH_TOP directory: Patch 32394134 (R12.AD.C.Delta.13) Patch 32392507 (R12.TXK.C.Delta.13) Patch 33441060:R12.AD.C (Additional critical AD patch) Patch 33550674:R12.TXK.C (Additional critical TXK
patch) ESTAMOS EN UN ABIENTE LAB, ASI QUE NO ES NECESARIO APLICAR EL PARCHE
SOBRE EL PATCH fs, VAMOS DIRECOT AL RUN EDITION. Desde el NODO o ENv DB. Copiamos el adgrant $ export ORACLE_PDB_SID=<PDB_SID> [oracle@apps 19.0.0]$ export ORACLE_PDB_SID=EBSDB
SQL> @$ORACLE_HOME/appsutil/admin/adgrants.sql apps [oracle@apps
19.0.0]$ sqlplus / as sysdba SQL*Plus: Release 19.0.0.0.0 - Production on Sat Aug 27 01:48:45 2022 Version 19.9.0.0.0 Copyright (c) 1982, 2020, Oracle. All rights reserved. Connected
to: Oracle
Database 19c Enterprise Edition Release 19.0.0.0.0 - Production Version 19.9.0.0.0 SQL>
ALTER USER EBS_SYSTEM ACCOUNT UNLOCK; User altered. SQL>
ALTER USER EBS_SYSTEM IDENTIFIED BY manager; User altered. Validar
Schema desde AS Environment $ perl $PATCH_TOP/32394134/ad/bin/adValidateEbssystemSchema.pl Aplicar Parche AD Delta 13 Copiamos los parches al $PATCH_TOP adop phase=apply patches=32394134,33441060 hotpatch=yes
merge=yes . . . Running finalize actions for the patches being applied. Log: @ADZDSHOWLOG.sql
"2022/08/27 02:28:45" Running cutover actions for the patches being applied. Creating workers to
process cutover DDL in parallel Log: /u01/install/APPS/fs_ne/EBSapps/log/adop/36/20220827_015243/apply/apps/log/ cutover.log Performing database cutover in Quick mode Generating post apply reports. Generating log report. Output: /u01/install/APPS/fs_ne/EBSapps/log/adop/36/20220827_015243/apply /apps/adzdshowlog.out The apply phase completed successfully. adop exiting with status = 0 (Success) As per 4.1 Critical AD Patches, apply any applicable AD patches
On the run edition application tier file system, use adop hotpatch mode to apply Patch 32392507 (R12.TXK.C.Delta.13 + critical adop phase=apply patches=32392507,33550674,34207577,33535778 hotpatch=yes merge=yes As per 4.2 Critical TXK Patches, y Update
your database tier with the latest patches. $ perl $AD_TOP/bin/admkappsutil.pl |
On the
application tier (as the applmgr user): Source the run edition file system environment file. UNIX: $ . <EBS_ROOT>/EBSapps.env run Run the admkappsutil.pl utility to create
the appsutil.zip file in <INST_TOP>/admin/out. $ perl <AD_TOP>/bin/admkappsutil.pl On the database tier (as the oracle user): Source the environment for the <RDBMS ORACLE_HOME>. UNIX: $ cd <RDBMS ORACLE_HOME> $ . ./<RDBMS ORACLE_HOME>/<CONTEXT_NAME>.env Change directory to the <RDBMS
ORACLE_HOME> and uncompress appsutil.zip. $ cp
/u01/install/APPS/fs1/inst/apps/EBSDB_apps/admin/out/appsutil.zip
$ORACLE_HOME $ cd $ORACLE_HOME $ unzip -o appsutil.zip Run AutoConfig on the <RDBMS ORACLE_HOME>. Note: For Oracle RAC systems, the steps
in this section need to be run on each Oracle RAC node. For more details,
refer to Oracle E-Business Suite Setup Guide, Release 12.2. UNIX: $ sh $ORACLE_HOME/appsutil/scripts/$CONTEXT_NAME/adautocfg.sh Run AutoConfig on the run edition file system. Note: Before running AutoConfig, if you are using the AutoConfig Customizations feature you must merge any customizations with the AutoConfig templates provided in the AD-TXK Delta 13 RUPs. As the applmgr user, run AutoConfig on all application tier nodes by running the appropriate command for your system: UNIX: $ sh $INST_TOP/admin/scripts/adautocfg.sh Synchronize the file
systems. This action copies the
new run edition code and configuration to the other file system. After you
apply AD-TXK Delta 13, you should run fs_clone to synchronize the
run and patch file systems with the configuration changes that the new
codelevel introduces. If you do not run fs_clone, it will run
automatically in the next prepare phase, which will consequently take more
time. $ adop phase=fs_clone
|
6. Validar Cyclo de ADOP
7. Aplicar Parche 12.2.11
Start an online patching cycle. $ adop phase=prepare Running this adnodemgrctl.sh:
check the logfile
/u01/oracle/EBS1228/fs2/inst/apps/EBS1228_laborasrv1036/logs/appl/admin/log/adnodemgrctl.txt
for more information ... The prepare
phase completed successfully. adop exiting
with status = 0 (Success) |
Me encontre algunos errores. ORA-06512:
at "APPS.AD_ZD_ADOP", line 274
uring the Prepare Phase the ADZDPATCH Concurrent Program Fails
With AD_ZD_ADOP.WAIT_FOR_CP_TO_RUN and Internal Manager Log Shows Routine
AFPCAL Received Failure Code While Parsing or Running Your Concurrent Program
CPMGR (Doc ID 2334520.1)
|
run adadmin . Java was not working so implemented jar signing again; regenerated jar files; and forms were accessible.
Note: Please contact the Java team if assistance is
needed. |
Apply Oracle E-Business Suite Release 12.2.11 Patch 31856789. UNIX:
El punto que más demora y puede estimar el tiempo que puede demorar esto: El proceso se quedo en este status
por bastante tiempo, sin procesos en la DB. Procedi a quitar el Works Inicimos la herramienta adctrl Lo vuelvo a iniciar Hasta aca: 5hs Es necesario Volver a ejecutar el
adctrl y marcar el workers como fixeado |
$ adop phase=cutover
$ adop phase=cleanup
$ adop phase=fs_clone
8. Parche Online Help 12.2.11
· Apply Oracle E-Business Suite Release
12.2.11 Online Help Using adop hotpatch mode on the run file system, apply Oracle E-Business Suite Release 12.2.11 Online Help Patch 31856799.
|
Quedaron
algunos objetos descompilados que se compilo siguiendo la siguiente nota:
How To Compile Oracle Fast Formulas? (Doc ID 155737.1)
Oracle E-Business Suite Release 12.2 System Schema Migration (Doc ID 2755875.1)
Developing and
Deploying Customizations in Oracle E-Business Suite Release 12.2 (Doc ID
1577661.1)