버전 비교

이전 버전 1

changes.mady.by.user 윤병훈

에 저장

비교대상

새 버전 현재

changes.mady.by.user 윤병훈

에 저장

키

  • 이 줄이 추가되었습니다.
  • 이 줄이 삭제되었습니다.
  • 서식이 변경되었습니다.


코드 블럭
languagebash
title19c 경로로 이동하여 sys 계정으로 DB 접속
linenumberstrue
cd <ORACLE_HOME(19c)>/apex
sqlplus / as sysdba


펼치기


서식 미적용
[oracle@orcl ~]$ echo $ORACLE_HOME
/u01/app/oracle/product/11.2.0/db_1

[oracle@orcl ~]$ cd /u01/app/oracle/product/19c/db_1/apex

[oracle@orcl apex]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.4.0 Production on Fri Feb 28 20:53:01 2020

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, OLAP, Data Mining and Real Application Testing options

SQL>




코드 블럭
title업그레이드 전 버전 확인
linenumberstrue
col comp_name format a35
col status format a12
select comp_name, status, version
from dba_Registry
where comp_name='Oracle Application Express';


펼치기


서식 미적용
SQL> col comp_name format a35
SQL> col status format a12
SQL> select comp_name, status, version
  2  from dba_Registry
  3  where comp_name='Oracle Application Express';

COMP_NAME                           STATUS       VERSION
----------------------------------- ------------ ------------------------------
Oracle Application Express          VALID        3.2.1.00.12





코드 블럭
titlesys 계정으로 APEX 업그레이드 수행
linenumberstrue
@apexins SYSAUX SYSAUX TEMP /i/


펼치기

작업 스크립트 참고 : apex_up.log




코드 블럭
title업그레이드 후 버전 확인
linenumberstrue
col comp_name format a35
col status format a12
select comp_name, status, version
from dba_Registry
where comp_name='Oracle Application Express';


펼치기


서식 미적용
SQL> col comp_name format a35
SQL> col status format a12
SQL> select comp_name, status, version
  2  from dba_Registry
  3  where comp_name='Oracle Application Express';

COMP_NAME                           STATUS       VERSION
----------------------------------- ------------ ------------------------------
Oracle Application Express          VALID        18.2.0.00.12





코드 블럭
title객체 재컴파일
linenumberstrue
@?/rdbms/admin/utlrp.sql


펼치기


서식 미적용
SQL> @?/rdbms/admin/utlrp.sql

TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_BGN  2020-02-28 21:10:12

DOC>   The following PL/SQL block invokes UTL_RECOMP to recompile invalid
DOC>   objects in the database. Recompilation time is proportional to the
DOC>   number of invalid objects in the database, so this command may take
DOC>   a long time to execute on a database with a large number of invalid
DOC>   objects.
DOC>
DOC>   Use the following queries to track recompilation progress:
DOC>
DOC>   1. Query returning the number of invalid objects remaining. This
DOC>      number should decrease with time.
DOC>         SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
DOC>
DOC>   2. Query returning the number of objects compiled so far. This number
DOC>      should increase with time.
DOC>         SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
DOC>
DOC>   This script automatically chooses serial or parallel recompilation
DOC>   based on the number of CPUs available (parameter cpu_count) multiplied
DOC>   by the number of threads per CPU (parameter parallel_threads_per_cpu).
DOC>   On RAC, this number is added across all RAC nodes.
DOC>
DOC>   UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
DOC>   recompilation. Jobs are created without instance affinity so that they
DOC>   can migrate across RAC nodes. Use the following queries to verify
DOC>   whether UTL_RECOMP jobs are being created and run correctly:
DOC>
DOC>   1. Query showing jobs created by UTL_RECOMP
DOC>         SELECT job_name FROM dba_scheduler_jobs
DOC>            WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>
DOC>   2. Query showing UTL_RECOMP jobs that are running
DOC>         SELECT job_name FROM dba_scheduler_running_jobs
DOC>            WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>#

PL/SQL procedure successfully completed.


TIMESTAMP
--------------------------------------------------------------------------------
COMP_TIMESTAMP UTLRP_END  2020-02-28 21:10:25

DOC> The following query reports the number of objects that have compiled
DOC> with errors.
DOC>
DOC> If the number is higher than expected, please examine the error
DOC> messages reported with each object (using SHOW ERRORS) to see if they
DOC> point to system misconfiguration or resource constraints that must be
DOC> fixed before attempting to recompile these objects.
DOC>#

OBJECTS WITH ERRORS
-------------------
                  0

DOC> The following query reports the number of errors caught during
DOC> recompilation. If this number is non-zero, please query the error
DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
DOC> are due to misconfiguration or resource constraints that must be
DOC> fixed before objects can compile successfully.
DOC>#

ERRORS DURING RECOMPILATION
---------------------------
                          0


Function created.


PL/SQL procedure successfully completed.


Function dropped.

...(21:10:27) Starting validate_apex for APEX_180200
...(21:10:28) Checking missing sys privileges
...(21:10:28) Re-generating APEX_180200.wwv_flow_db_version
... wwv_flow_db_version is up to date
...(21:10:28) Key object existence check
...(21:10:29) Setting DBMS Registry for APEX to valid
...(21:10:29) Exiting validate_apex

PL/SQL procedure successfully completed.

SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options