Continuando
con la actualización a Oracle 12c Release 2.
En este articulo vamos a detallar los pasos para poder actualizar el
motor de base de datos y las bases de datos que corren sobre la plataforma.
En
internet van a encontrar muchos procedimientos para actualizar la base de datos
con DBUA, es por eso que en este articulo quiero compartir con Uds. la
actualización manual utilizando el nuevo comando dbupgrade.
Vuelvo a
indicar la información general del ambiente en el que vamos a trabajar es la
siguiente.
12cR1
|
12cR2
|
|
Sistema Operativo
|
Oracle Linux 6.8
|
Oracle Linux 6.8
|
ORACLE_BASE
|
/u01/app/oracle/
|
/u01/app/oracle/
|
ORACLE_GRID_HOME
|
/u01/app/oracle/product/12.1.0/grid_1
|
/u01/app/oracle/product/12.2.0/grid_1
|
ORACLE_DB_HOME
|
/u01/app/oracle/product/12.1.0/db_1
|
/u01/app/oracle/product/12.2.0/db_1
|
Antes de
realizar el Upgrade debemos de cumplir los pre-requisitos.
PRE-REQUISITOS
1.
Revisión de la versión de Base de datos.
Para
poder actualizar la base de datos a la versión Oracle 12c Release 2, es
importante revisar la versión original de base de datos. Dependiendo de la versión, es posible definir
un método de actualización.
En el
siguiente cuadro resumo los probables métodos para cada versión.
Versión Original
|
PATCH SET
|
¿Soporta Upgrade Directo?
|
Oracle 12c
|
12.1.0.1,
12.1.0.2
|
Si
|
Oracle 11g Release 2
|
11.2.0.3,
11.2.0.4
|
SI
|
11.2.0.1, 11.2.0.2
|
No
|
|
Oracle 11g
Release 1 and anterior
|
Todos
|
No
|
Para
nuestro ejercicio utilizamos la versión 12.1.0.2
SQL> select
BANNER from v$version;
BANNER
-------------------------------------------------------------------------
Oracle Database
12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
PL/SQL Release
12.1.0.2.0 - Production
CORE 12.1.0.2.0 Production
TNS for Linux:
Version 12.1.0.2.0 - Production
NLSRTL Version
12.1.0.2.0 – Production
2.
Instalación de los binarios Oracle 12c Release 2
Previo a
la actualización de la base de datos, debemos instalar los binarios para Oracle
12c Release 2.
Descomprimimos
el instalador y ejecutamos el comando runInstaller desde una interfaz con
soporte gráfico.
[oracle@oracle12c ~]$ cd /u01/Install/
[oracle@oracle12c
Install]$ unzip -q linuxx64_12201_database.zip
[oracle@oracle12c
Install]$ vncserver
[oracle@oracle12c
Install]$ cd database/
[oracle@oracle12c
database]$ ./runInstaller
Starting Oracle
Universal Installer...
Checking Temp
space: must be greater than 500 MB. Actual
1867 MB Passed
Checking swap
space: must be greater than 150 MB.
Actual 2856 MB Passed
Checking
monitor: must be configured to display at least 256 colors. Actual 16777216 Passed
Seleccionamos
la opción
Install Database software only
Indicamos
la arquitectura que vamos a instalar. Para este ejemplo es
Single Instance Database installation.
Definimos
la edición de la base de datos.
Definimos
el ORACLE_BASE y ORACLE_HOME para la versión 12c Release 2
Seleccionamos
los grupos de Sistema Operativo para cada rol.
Verificamos
el Resumen y procedemos instalación del motor Oracle 12c Release 2.
Ejecutamos
el script con el usuario ROOT.
[root@oracle12c
12.2.0]# /u01/app/oracle/product/12.2.0/db_1/root.sh
Performing root user operation.
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME=
/u01/app/oracle/product/12.2.0/db_1
Enter the full pathname of the local bin directory:
[/usr/local/bin]:
The contents of "dbhome" have not changed.
No need to overwrite.
The file "oraenv" already exists in
/usr/local/bin. Overwrite it? (y/n)
[n]:
The contents of "coraenv" have not changed.
No need to overwrite.
Entries will be added to the /etc/oratab file as
needed by
Database Configuration Assistant when a database is
created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Do you want to
setup Oracle Trace File Analyzer (TFA) now ? yes|[no] :
Con la
instalación del motor 12.2.0.1 procedemos con el Upgrade de la base de datos.
Upgrade de Base de datos a 12.2.0.1
1.
Preparación de la base de datos origen.
Revisar
que no haya ningún proceso de refresco de Vistas Materializadas activo.
SQL> SELECT
o.name FROM sys.obj$ o, sys.user$ u, sys.sum$ s WHERE o.type# = 42 AND
bitand(s.mflags, 8) =8;
no rows selected
Revisar
que ninguna tarea de Backup se encuentre activa.
SQL> SELECT *
FROM v$backup WHERE status != 'NOT ACTIVE';
no rows selected
Sacar
estadísticas de diccionario para un proceso de actualización más rápido
SQL> EXEC
DBMS_STATS.GATHER_DICTIONARY_STATS;
PL/SQL procedure
successfully completed.
Limpiar
el Recycle bin.
SQL> PURGE DBA_RECYCLEBIN;
DBA Recyclebin
purged.
2.
Remover componentes de base de datos – Oracle 11g
Si la
actualización se va a realizar desde Oracle 11g, es necesario remover la
consola EM y el componente OLAP.
SQL> @?/rdbms/admin/emremove.sql
SQL> @?/olap/admin/catnoamd.sql
3.
Ejecutar el comando preupgrade.jar
Ejecutamos
el comando preupgrade.jar para poder
hacer la revisión previa a la actualización de la base de datos. Este comando genera 2 archivos SQL y 1
archivo de LOG.
- preupgrade.log
- preupgrade_fixups.sql
- postupgrade_fixups.sql
[oracle@oracle12c
~]$ cd $ORACLE_HOME/jdk/bin/
[oracle@oracle12c bin]$ java -jar
/u01/app/oracle/product/12.2.0/db_1/rdbms/admin/preupgrade.jar FILE
Preupgrade generated files:
/u01/app/oracle/cfgtoollogs/orcl/preupgrade/preupgrade.log
/u01/app/oracle/cfgtoollogs/orcl/preupgrade/preupgrade_fixups.sql
/u01/app/oracle/cfgtoollogs/orcl/preupgrade/postupgrade_fixups.sql
Ejecutamos
el archivo SQL preupgrade_fixups.sql generado por el comando anterior.
SQL> @/u01/app/oracle/cfgtoollogs/orcl/preupgrade/preupgrade_fixups.sql
Executing Oracle
PRE-Upgrade Fixup Script
Auto-Generated
by: Oracle Preupgrade Script
Version: 12.2.0.1.0
Build: 1
Generated
on: 2018-03-04 03:43:27
For Source
Database: ORCL
Source Database
Version: 12.1.0.2.0
For Upgrade to
Version: 12.2.0.1.0
Fixup
Check Name Status Further DBA Action
---------- ------ ------------------
invalid_objects_exist Failed
Manual fixup recommended.
mv_refresh Failed Manual fixup recommended.
PL/SQL procedure
successfully completed.
4.
Generar un punto de Restauración
Cuando
vayan a realizar un Upgrade o Migración de base de datos les recomiendo
fuertemente crear un punto de restauración rápida. Personalmente utilizo mucho Flashback
Database debido a su fácil uso y su rápida recuperación.
Puede que
necesiten un poco de espacio para almacenar los Flashback Logs, pero vale la
pena el consumo de espacio para asegurar un camino de retorno.
SQL> alter
database flashback on;
Database
altered.
SQL> create
restore point migracion;
Restore point
created.
5.
Copiar archivos de configuración al nuevo ORACLE_HOME
Copiamos
los archivos de configuración ORACLE NET al nuevo ORACLE_HOME 12c Release 2.
[oracle@oracle12c
bin]$ cd $ORACLE_HOME_12R1/network/admin
[oracle@oracle12c
admin]$ cp listener.ora tnsnames.ora sqlnet.ora
/u01/app/oracle/product/12.2.0/db_1/network/admin/.
Copiamos
los archivos de configuración de la base de datos al nuevo ORACLE_HOME
[oracle@oracle12c
admin]$ cd $ORACLE_HOME_12R1/dbs
[oracle@oracle12c
dbs]$ cp spfileorcl.ora orapworcl /u01/app/oracle/product/12.2.0/db_1/dbs/.
Finalmente
bajamos la base de datos para empezar con la actualización.
SQL> shut
immediate
Database closed.
Database
dismounted.
ORACLE instance
shut down.
6.
Actualizar la base de datos con dbupgrade
Definimos
las variables hacia el nuevo ORACLE_HOME 12c Release 2.
export
ORACLE_BASE=/u01/app/oracle
export
ORACLE_HOME=$ORACLE_BASE/product/12.2.0/db_1
export
ORACLE_SID=orcl
Levantamos
la base de datos en modo Upgrade.
SQL> startup
upgrade
ORACLE instance
started.
Total System
Global Area 1577058304 bytes
Fixed Size 8621136 bytes
Variable
Size 536871856 bytes
Database
Buffers 603979776 bytes
Redo
Buffers 8155136 bytes
In-Memory
Area 419430400 bytes
Database mounted.
Database opened.
Realizamos
el Upgrade con el comando $ORACLE_HOME/bin/dbupgrade.
Este comando puede recibir varios parámetros, pero los más importantes son:
-n indica el nivel de
paralelismo para el Upgrade.
-l indica el directorio donde
escribe el log para el Upgrade.
[oracle@oracle12c
~]$ cd $ORACLE_HOME/bin
[oracle@oracle12c
bin]$ ./dbupgrade -n 2 -l /home/oracle/upgrade
Argument list
for [/u01/app/oracle/product/12.2.0/db_1/rdbms/admin/catctl.pl]
Run in c = 0
Do not run
in C = 0
Input
Directory d = 0
Echo OFF e = 1
Simulate E = 0
Forced
cleanup F = 0
Log Id i = 0
Child
Process I = 0
Log Dir l = /home/oracle
Priority List
Name L = 0
Upgrade Mode
active M = 0
SQL Process
Count n = 2
…
------------------------------------------------------
Phases
[0-115] Start Time:[2018_03_04
04:09:55]
------------------------------------------------------
*********** Executing Change Scripts ***********
Serial Phase #:0
[orcl] Files:1 Time: 253s
*************** Catalog Core SQL ***************
Serial Phase #:1
[orcl] Files:5 Time: 229s
Restart Phase #:2
[orcl] Files:1 Time: 0s
*********** Catalog Tables and Views ***********
Parallel Phase
#:3 [orcl] Files:19 Time: 65s
Restart Phase #:4
[orcl] Files:1 Time: 0s
************* Catalog Final Scripts ************
Serial Phase #:5
[orcl] Files:6 Time: 42s
***************** Catproc Start ****************
Serial Phase #:6
[orcl] Files:1 Time: 48s
***************** Catproc Types ****************
Serial Phase #:7
[orcl] Files:2 Time: 45s
Restart Phase #:8
[orcl] Files:1 Time: 0s
**************** Catproc Tables ****************
Parallel Phase
#:9 [orcl] Files:69
…
Serial Phase #:115
[orcl] Files:1 Time: 40s
------------------------------------------------------
Phases
[0-115] End Time:[2018_03_04
06:19:01]
------------------------------------------------------
Grand Total
Time: 7753s
LOG FILES: (/home/oracle/catupgrd*.log)
Upgrade Summary
Report Located in:
/home/oracle/upg_summary.log
7.
Actualizar el Timezone de la base de datos
A
diferencia del DBUA, el proceso manual no actualiza el Timezone de la base de
datos. Este procedimiento lo debemos
hacer nosotros.
En Oracle
Support podemos encontrar el documento Doc ID 1585343.1 donde Oracle brinda
scripts para poder hacer la actualización del Timezone mucho más rápida.
Pueden
bajar el archivo ZIP desde Aquí.
Ejecutamos
los scripts upg_tzv_check.sql y upg_tzv_apply.sql para realizar la actualización
del Timezone.
SQL> spool
upg_tzv_check.log
SQL> @upg_tzv_check.sql
INFO: Starting
with RDBMS DST update preparation.
INFO: NO actual
RDBMS DST update will be done by this script.
INFO: If an
ERROR occurs the script will EXIT sqlplus.
INFO: Doing
checks for known issues ...
INFO: Database
version is 12.2.0.1 .
INFO: Database
RDBMS DST version is DSTv18 .
INFO: No known
issues detected.
INFO: Now
detecting new RDBMS DST version.
A prepare window
has been successfully started.
INFO: Newest
RDBMS DST version detected is DSTv26 .
INFO: Next step
is checking all TSTZ data.
INFO: It might
take a while before any further output is seen ...
A prepare window
has been successfully ended.
INFO: A newer
RDBMS DST version than the one currently used is found.
INFO: Note that
NO DST update was yet done.
INFO: Now run
upg_tzv_apply.sql to do the actual RDBMS DST update.
INFO: Note that
the upg_tzv_apply.sql script will
INFO: restart
the database 2 times WITHOUT any confirmation or prompt.
SQL> spool
off
SQL> spool
upg_tzv_apply.log
SQL> @upg_tzv_apply.sql
INFO: If an
ERROR occurs the script will EXIT sqlplus.
INFO: The
database RDBMS DST version will be updated to DSTv26 .
WARNING: This
script will restart the database 2 times
WARNING: WITHOUT
asking ANY confirmation.
WARNING: Hit
control-c NOW if this is not intended.
INFO: Restarting
the database in UPGRADE mode to start the DST upgrade.
Database closed.
Database
dismounted.
ORACLE instance
shut down.
ORACLE instance
started.
..
INFO: Total
failures during update of TSTZ data: 0 .
An upgrade
window has been successfully ended.
INFO: Your new
Server RDBMS DST version is DSTv26 .
INFO: The RDBMS
DST update is successfully finished.
INFO: Make sure
to exit this sqlplus session.
INFO: Do not use
it for timezone related selects.
SQL> spool
off
8.
Ejecutar scripts post migración.
Una vez
finalizado la migración, debemos de ejecutar scripts post migración.
Los
scripts que debemos correr son:
- postupgrade_fixups.sql
- utlu122s.sql
- catuppst.sql
- utlrp.sql
SQL> @/u01/app/oracle/cfgtoollogs/orcl/preupgrade/postupgrade_fixups.sql
Session altered.
PL/SQL procedure
successfully completed.
PL/SQL procedure
successfully completed.
Package created.
No errors.
Package body
created.
No errors.
Package created.
No errors.
Package body
created.
No errors.
Executing Oracle
POST-Upgrade Fixup Script
Auto-Generated
by: Oracle Preupgrade Script
Version: 12.2.0.1.0
Build: 1
Generated
on: 2018-03-04 03:43:38
For Source
Database: ORCL
Source Database
Version: 12.1.0.2.0
For Upgrade to
Version: 12.2.0.1.0
Fixup
Check Name Status Further DBA Action
---------- ------ ------------------
depend_usr_tables Passed
None.
old_time_zones_exist Passed
None
apex_patch Passed None
post_dictionary Passed None
PL/SQL procedure
successfully completed.
SQL> @?/rdbms/admin/utlu122s.sql
Oracle Database
12.2 Post-Upgrade Status Tool 03-04-2018 06:44:28
Component Current Version Elapsed Time
Name Status Number HH:MM:SS
Oracle
Server
UPGRADED 12.2.0.1.0 00:35:28
JServer JAVA
Virtual Machine UPGRADED 12.2.0.1.0 00:28:28
Oracle Real
Application Clusters UPGRADED 12.2.0.1.0 00:00:01
Oracle Workspace
Manager UPGRADED 12.2.0.1.0 00:02:41
OLAP Analytic
Workspace UPGRADED 12.2.0.1.0 00:01:56
Oracle OLAP
API UPGRADED 12.2.0.1.0 00:00:41
Oracle Label
Security UPGRADED 12.2.0.1.0 00:00:50
Oracle XDK UPGRADED 12.2.0.1.0 00:05:19
Oracle Text UPGRADED 12.2.0.1.0 00:03:20
Oracle XML
Database UPGRADED 12.2.0.1.0 00:06:10
Oracle Database
Java Packages UPGRADED 12.2.0.1.0 00:01:25
Oracle
Multimedia
UPGRADED 12.2.0.1.0 00:09:21
Spatial UPGRADED 12.2.0.1.0 00:19:46
Oracle
Application Express
VALID 5.0.3.00.03 00:00:08
Oracle Database
Vault UPGRADED 12.2.0.1.0 00:01:48
Final
Actions
00:06:28
Post
Upgrade
00:01:04
Total Upgrade
Time: 02:05:13
Database time
zone version is 26. It meets current release needs.
Summary Report
File = /home/oracle/upg_summary.log
SQL> @?/rdbms/admin/catuppst.sql
..
06:44:41 SQL>
SELECT dbms_registry_sys.time_stamp('CATUPPST') as timestamp from dual;
TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP
CATUPPST 2018-03-04
06:44:41
DBUA_TIMESTAMP
CATUPPST FINISHED 2018-03-04
06:44:41
DBUA_TIMESTAMP
CATUPPST NONE 2018-03-04
06:44:41
1 row selected.
Elapsed:
00:00:00.02
06:44:41 SQL>
06:44:41 SQL>
Rem Set errorlogging off
06:44:41 SQL>
SET ERRORLOGGING OFF;
06:44:41 SQL>
06:44:41 SQL>
Rem
06:44:41 SQL>
Rem Set _ORACLE_SCRIPT to false
06:44:41 SQL>
Rem
06:44:41 SQL>
ALTER SESSION SET "_ORACLE_SCRIPT"=false;
Session altered.
Elapsed:
00:00:00.00
06:44:41 SQL>
06:44:41 SQL>
Rem *********************************************************************
06:44:41 SQL>
Rem END catuppst.sql
06:44:41 SQL>
Rem *********************************************************************
SQL> @?/rdbms/admin/utlrp.sql
…
ERRORS DURING
RECOMPILATION
---------------------------
0
Function
created.
PL/SQL procedure
successfully completed.
Function
dropped.
...Starting
validation 07:03:35
...Database user
"SYS", database schema "APEX_050000", user# "117"
07:03:35
ORA-20001:
MISSING GRANT: grant execute on "MDSYS"."SDO_DIM_ARRAY" to
"APEX_050000"
ORA-20001:
MISSING GRANT: grant execute on "MDSYS"."SDO_DIM_ELEMENT"
to
"APEX_050000"
ORA-20001:
MISSING GRANT: grant execute on "MDSYS"."SDO_POINT_TYPE" to
"APEX_050000"
...grant execute
on "SYS"."DBMS_CRYPTO_INTERNAL" to APEX_050000 07:03:40
...grant execute
on "SYS"."DIANA" to APEX_050000 07:03:42
...grant execute
on "SYS"."DIUTIL" to APEX_050000 07:03:42
...grant execute
on "SYS"."KU$_DDL" to APEX_050000 07:03:43
...grant execute
on "SYS"."KU$_DDLS" to APEX_050000 07:03:43
...272 packages
...265 package
bodies
...465 tables
...8 functions
...16 procedures
...4 sequences
...497 triggers
...1582 indexes
...254 views
...0 libraries
...14 types
...5 type bodies
...0 operators
...0 index types
...Begin key
object existence check 07:03:47
...Completed key
object existence check 07:03:48
...Setting DBMS
Registry 07:03:48
...Setting DBMS
Registry Complete 07:03:48
...Exiting
validate 07:03:48
Cambiamos
el parámetro COMPATIBLE al valor 12.2.0
SQL> alter
system set compatible='12.2.0' scope=spfile;
System altered.
Verificamos
el correcto Upgrade de la base de datos.
SQL> select banner from v$version;
BANNER
-------------------------------------------------------------------------
Oracle Database
12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
PL/SQL Release 12.2.0.1.0 - Production
CORE
12.2.0.1.0 Production
TNS for Linux: Version 12.2.0.1.0 - Production
NLSRTL Version 12.2.0.1.0 – Production
9.
Aplicar el Release Update (RU) más reciente para la base de
datos.
Ahora que
la base de datos se encuentra en la versión 12.2.0.1. Es muy importante aplicar el último Release Update.
En este
ejercicio utilizamos el RU de enero 2018 para la base de datos con numero de
parche 27105253. Para aplicar
el parche se necesita actualizar el OPatch a la versión mínima de 12.2.0.1.6.
Se puede
descargar el parche 6880880 de la página de Oracle Support.
Actualizamos
el OPatch
[oracle@oracle12c
Install]$ cp p6880880_122010_Linux-x86-64.zip $ORACLE_HOME/.
[oracle@oracle12c Install]$ cd $ORACLE_HOME
[oracle@oracle12c
db_1]$ mv OPatch OPatch.old
[oracle@oracle12c
db_1]$ unzip -q p6880880_122010_Linux-x86-64.zip
[oracle@oracle12c db_1]$ cd ./OPatch
[oracle@oracle12c OPatch]$ ./opatch version
OPatch Version: 12.2.0.1.12
Descomprimimos
el parche 27105253 en un directorio temporal.
[oracle@oracle12c
OPatch]$ cd /u01/Install/
[oracle@oracle12c
Install]$ unzip -q p27105253_122010_Linux-x86-64.zip
Detenemos
las bases de datos sobre los binarios Oracle 12c R2
SQL> shut
immediate
Database closed.
Database
dismounted.
ORACLE instance shut
down.
Se
procede a realizar el parchado de los binarios de base de datos Oracle 12c R2.
[oracle@oracle12c 27105253]$ cd /u01/Install/27105253
[oracle@oracle12c
27105253]$ $ORACLE_HOME/OPatch/opatch
apply
Oracle Interim
Patch Installer version 12.2.0.1.12
Copyright (c)
2018, Oracle Corporation. All rights
reserved.
Oracle Home : /u01/app/oracle/product/12.2.0/db_1
Central
Inventory : /u01/app/oraInventory
from :
/u01/app/oracle/product/12.2.0/db_1/oraInst.loc
OPatch
version : 12.2.0.1.12
OUI version : 12.2.0.1.4
Log file
location :
/u01/app/oracle/product/12.2.0/db_1/cfgtoollogs/opatch/opatch2018-03-04_07-19-27AM_1.log
Verifying
environment and performing prerequisite checks...
OPatch continues
with these patches: 27105253
Do you want to
proceed? [y|n]
y
User Responded
with: Y
All checks
passed.
Please shutdown
Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home =
'/u01/app/oracle/product/12.2.0/db_1')
Is the local
system ready for patching? [y|n]
y
User Responded
with: Y
Backing up
files...
…
Patching
component oracle.network.rsf, 12.2.0.1.0...
Patching
component oracle.rdbms.deconfig, 12.2.0.1.0...
Patching
component oracle.tfa, 12.2.0.1.0...
Patching
component oracle.rdbms, 12.2.0.1.0...
Patching
component oracle.rdbms.util, 12.2.0.1.0...
…
Patching
component oracle.sdo, 12.2.0.1.0...
Patch 27105253
successfully applied.
Log file
location: /u01/app/oracle/product/12.2.0/db_1/cfgtoollogs/opatch/opatch2018-03-04_07-19-27AM_1.log
OPatch succeeded.
Es
necesario cargar los archivos SQL modificados por el parche en la base de
datos. Se ejecuta el comando datapatch
SQL> startup
ORACLE instance
started.
Total System
Global Area 1577058304 bytes
Fixed Size 8621136 bytes
Variable
Size 536871856 bytes
Database
Buffers 603979776 bytes
Redo
Buffers 8155136 bytes
In-Memory
Area 419430400 bytes
Database
mounted.
Database opened.
[oracle@oracle12c
27105253]$ cd $ORACLE_HOME/OPatch
[oracle@oracle12c
OPatch]$ ./datapatch -verbose
SQL Patching
tool version 12.2.0.1.0 Production on Sun Mar
4 07:32:33 2018
Copyright (c)
2012, 2017, Oracle. All rights reserved.
Log file for
this invocation:
/u01/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_6822_2018_03_04_07_32_33/sqlpatch_invocation.log
Connecting to
database...OK
Bootstrapping
registry and package to current versions...done
Determining current
state...done
Current state of
SQL patches:
Bundle series
DBRU:
ID 180116 in the binary registry and not
installed in the SQL registry
Adding patches
to installation queue and performing prereq checks...
Installation
queue:
Nothing to roll back
The following patches will be applied:
27105253 (DATABASE RELEASE UPDATE
12.2.0.1.180116)
Installing
patches...
Patch
installation complete. Total patches
installed: 1
Validating
logfiles...
Patch 27105253
apply: SUCCESS
logfile:
/u01/app/oracle/cfgtoollogs/sqlpatch/27105253/21862470/27105253_apply_ORCL_2018Mar04_07_33_09.log
(no errors)
SQL Patching
tool complete on Sun Mar 4 07:39:29 2018
Con esto
finalizamos el procedimiento de actualización de la base de datos a Oracle 12c
Release 2 de manera Exitosa.
¡Felicidades tu base de
datos ya se encuentra actualizada!
Espero
les pueda servir.
No hay comentarios.:
Publicar un comentario