Skip to main content

Step by Step Upgrading Database using Autoupgrade utility

 

Step by Step Upgrading Database using Autoupgrade utility 


<<Back to DB Administration Main Page

Step1: create config file 

java -jar autoupgrade.jar -create_sample_file config /oracle/ORCL/ORCL_autoupgrade.cfg

Step2: Adjust the config file  parameters 

global.autoupg_log_dir=/ora_app/cfgtoollogs/autoupgrade

upg1.log_dir=/ora_app/cfgtoollogs/autoupgrade/ORCL 

upg1.sid=ORCL 

upg1.source_home=/ora_app/product/12.1.0.2/home12

upg1.target_home=/ora_app/product/19c/home19

upg1.start_time=NOW 

upg1.upgrade_node=host1.merckgroup.com

upg1.run_utlrp=yes

upg1.timezone_upg=yes

step3: Run PreCheck

java -jar autoupgrade.jar -config /ora_work/ORCL/ORCL_autoupgrade.cfg -mode analyze

AutoUpgrade 24.6.240905 launched with default internal options

Processing config file ...

+--------------------------------+

| Starting AutoUpgrade execution |

+--------------------------------+

1 Non-CDB(s) will be analyzed

Type 'help' to list console commands

upg> Job 100 completed

------------------- Final Summary --------------------

Number of databases            [ 1 ]


Jobs finished                  [1]

Jobs failed                    [0]


Please check the summary report at:

/ora_app/cfgtoollogs/autoupgrade/cfgtoollogs/upgrade/auto/status/status.html

/ora_app/cfgtoollogs/autoupgrade/cfgtoollogs/upgrade/auto/status/status.log


Step4:Perform Fixups if required

java -jar autoupgrade.jar -config /ora_work/ORCL/ORCL_autoupgrade.cfg -mode fixups

AutoUpgrade 24.6.240905 launched with default internal options

Processing config file ...

+--------------------------------+

| Starting AutoUpgrade execution |

+--------------------------------+

1 Non-CDB(s) will be processed

Type 'help' to list console commands

upg>

upg> Job 101 completed

------------------- Final Summary --------------------

Number of databases            [ 1 ]


Jobs finished                  [1]

Jobs failed                    [0]


Please check the summary report at:

/ora_app/cfgtoollogs/autoupgrade/cfgtoollogs/upgrade/auto/status/status.html

/ora_app/cfgtoollogs/autoupgrade/cfgtoollogs/upgrade/auto/status/status.log


Step5:Check Status 

upg> lsj

+----+-------+---------+---------+-------+----------+--------+-------+

|Job#|DB_NAME|    STAGE|OPERATION| STATUS|START_TIME| UPDATED|MESSAGE|

+----+-------+---------+---------+-------+----------+--------+-------+

| 101|ORCL|PREFIXUPS|EXECUTING|RUNNING|  10:53:22|100s ago|       |

+----+-------+---------+---------+-------+----------+--------+-------+

Total jobs 1

Step5:Perform Upgrade 

java -jar autoupgrade.jar -config /ora_work/ORCL/ORCL_autoupgrade.cfg -mode deploy

AutoUpgrade 24.6.240905 launched with default internal options

Processing config file ...

+--------------------------------+

| Starting AutoUpgrade execution |

+--------------------------------+

1 Non-CDB(s) will be processed

Type 'help' to list console commands

upg>

upg> help

exit                            // To close and exit

help                            // Displays help

lsj [<option>] [-a <number>]    // list jobs by status up to n elements.

        -f                Filter by finished jobs.

        -r                Filter by running jobs.

        -e                Filter by jobs with errors.

        -p                Filter by jobs being prepared.

        -n <number>       Display up to n jobs.

        -a <number>       Repeats the command (in <number> seconds).

lsr                             // Displays the restoration queue

lsa                             // Displays the stop queue

tasks                           // Displays the tasks running

clear                           // Clears the terminal

resume -job <number> [-ignore_errors=<ORA-#####,ORA-#####>] // Restarts a job with option to ignore errors

status [<option>] [-a <number>] // Summary of current execution

        -config                     Show Config Information

        -job <number>               Summary of a given job

        -job <number> -c <dbname>   Show details of container

        -a [<number>]               Repeats the command (in <number> seconds).

restore -job <number>           // Restores the database to its state prior to the upgrade

restore all_failed              // Restores all failed jobs to their previous states prior to the upgrade

logs                            // Displays all the log locations

stop -job <number>              // Stops the specified job

h[ist]                          // Displays the command line history

/[<number>]                     // Executes the command specified from the history. The default is the last command

meta                            // Displays Internal latch count

hwinfo                          // Displays additional information

fxlist -job <number> [<option>]                // FixUps summary

        -c <dbname>                                  Container specific FixUps

        -c <dbname> alter <check> run <yes|no|skip>  Update Run Configuration



upg> status

Config


        User configuration file    [/ora_work/ORCL/ORCL_autoupgrade.cfg]

        General logs location      [/ora_app/cfgtoollogs/autoupgrade/cfgtoollogs/upgrade/auto]

        Mode                       [DEPLOY]

Jobs Summary


        Total databases in configuration file [1]

        Total Non-CDB being processed         [1]

        Total Containers being processed      [0]


        Jobs finished successfully            [0]

        Jobs finished/stopped                 [0]

        Jobs in progress                      [1]


Progress

        +---+---------------------------------------------------------+

        |Job|                                                 Progress|

        +---+---------------------------------------------------------+

        |102|[||||||||||||||||||||                              ] 38 %|

        +---+---------------------------------------------------------+


upg> lsj

+----+-------+---------+---------+-------+----------+-------+-----------+

|Job#|DB_NAME|    STAGE|OPERATION| STATUS|START_TIME|UPDATED|    MESSAGE|

+----+-------+---------+---------+-------+----------+-------+-----------+

| 102|ORCL|DBUPGRADE|EXECUTING|RUNNING|  16:01:11|55s ago|0%Upgraded |

+----+-------+---------+---------+-------+----------+-------+-----------+

Total jobs 1


upg> tasks

+---+----------------------+-------------+

| ID|                  NAME|         Job#|

+---+----------------------+-------------+

|  1|                  main|      WAITING|

| 16|  Attach API wait loop|     RUNNABLE|

| 54|            event_loop|TIMED_WAITING|

| 55|               console|     RUNNABLE|

| 56|          queue_reader|      WAITING|

| 58|                 cmd-0|      WAITING|

| 59|               StatUpg|      WAITING|

| 60|            event_loop|TIMED_WAITING|

| 61|     ClassCache Reaper|      WAITING|

| 62|         job_manager-0|      WAITING|

| 67|             exec_loop|      WAITING|

| 68|             exec_loop|      WAITING|

|437|   monitor_ORCL_102|TIMED_WAITING|

|441|        catctl_ORCL|      WAITING|

|442| abort_monitor_ORCL|TIMED_WAITING|

|443|             Thread-25|     RUNNABLE|

+---+----------------------+-------------+

upg> logs

AutoUpgrade logs folder [/ora_app/cfgtoollogs/autoupgrade/cfgtoollogs/upgrade/auto]

logs folder [ORCL][/ora_app/cfgtoollogs/autoupgrade/ORCL/ORCL]


upg> hwinfo

AutoUpgrade up time:5 min

System time:      2024-09-25 16:06:10

Hostname:         host1.merckgroup.com

HW CPU Cores:     2


upg> status


Config


        User configuration file    [/ora_work/ORCL/ORCL_autoupgrade.cfg]

        General logs location      [/ora_app/cfgtoollogs/autoupgrade/cfgtoollogs/upgrade/auto]

        Mode                       [DEPLOY]

Jobs Summary


        Total databases in configuration file [1]

        Total Non-CDB being processed         [1]

        Total Containers being processed      [0]


        Jobs finished successfully            [0]

        Jobs finished/stopped                 [0]

        Jobs in progress                      [1]


Progress

        +---+---------------------------------------------------------+

        |Job|                                                 Progress|

        +---+---------------------------------------------------------+

        |102|[||||||||||||||||||||||||                          ] 46 %|

        +---+---------------------------------------------------------+


upg> tasks

+---+----------------------+-------------+

| ID|                  NAME|         Job#|

+---+----------------------+-------------+

|  1|                  main|      WAITING|

| 16|  Attach API wait loop|     RUNNABLE|

| 54|            event_loop|TIMED_WAITING|

| 55|               console|     RUNNABLE|

| 56|          queue_reader|      WAITING|

| 58|                 cmd-0|      WAITING|

| 59|               StatUpg|      WAITING|

| 60|            event_loop|TIMED_WAITING|

| 61|     ClassCache Reaper|      WAITING|

| 62|         job_manager-0|      WAITING|

| 67|             exec_loop|      WAITING|

| 68|             exec_loop|      WAITING|

|437|   monitor_ORCL_102|TIMED_WAITING|

|441|        catctl_ORCL|      WAITING|

|442| abort_monitor_ORCL|TIMED_WAITING|

|443|             Thread-25|     RUNNABLE|

+---+----------------------+-------------+

upg>

upg> status


Config


        User configuration file    [/ora_work/ORCL/ORCL_autoupgrade.cfg]

        General logs location      [/ora_app/cfgtoollogs/autoupgrade/cfgtoollogs/upgrade/auto]

        Mode                       [DEPLOY]

Jobs Summary


        Total databases in configuration file [1]

        Total Non-CDB being processed         [1]

        Total Containers being processed      [0]


        Jobs finished successfully            [0]

        Jobs finished/stopped                 [0]

        Jobs in progress                      [1]


Progress

        +---+---------------------------------------------------------+

        |Job|                                                 Progress|

        +---+---------------------------------------------------------+

        |102|[||||||||||||||||||||||||                          ] 46 %|

        +---+---------------------------------------------------------+


upg> Job 102 completed

------------------- Final Summary --------------------

Number of databases            [ 1 ]


Jobs finished                  [1]

Jobs failed                    [0]

Jobs restored                  [0]

Jobs pending                   [0]


---- Drop GRP at your convenience once you consider it is no longer needed ----

Drop GRP from ORCL: drop restore point AUTOUPGRADE_9212_ORCL121020


AutoUpgrade with Source and Target Database Homes on Different Servers

-->On the target server, start up the database in upgrade mode, and then run AutoUpgrade in upgrade mode

java -jar autoupgrade.jar -config config.txt -mode upgrade


Comments

Post a Comment

Popular posts from this blog

How to Power On/off Oracle Exadata Machine

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using  button on front of the server The power on sequence is as follows. 1. Start Rack, including switches  Note:- Ensure the switches have had power applied for a few minutes to complete power on  configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers  Note:- Ensure all Exadata Storage Servers complete the boot process before starting the   database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the serve...
Post a Comment
Read more

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco...
7 comments
Read more

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1     node1-vip node2     node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:
1 comment
Read more

ORA-46630: keystore cannot be created at the specified location

<<Back to DB Administration Main Page ORA-46630: keystore cannot be created at the specified location CDB011> ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "xxxxxxx"; ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "EncTest123" * ERROR at line 1: ORA-46630: keystore cannot be created at the specified location Cause  Creating a keystore at a location where there is already a keystore exists Solution To solve the problem, use a different location to create a keystore (use ENCRYPTION_WALLET_LOCATION in sqlnet.ora file to specify the keystore location), or move this ewallet.p12 file to some other location. Note: Oracle does not recommend deleting keystore file (ewallet.p12) that belongs to a database. If you have multiple keystores, you can choose to merge them rather than deleting either of them.
Post a Comment
Read more

ORA-65104: operation not allowed on an inactive pluggable database alter pluggable database open

<<Back to DB Administration Main Page ORA-65104: operation not allowed on an inactive pluggable database SQL> alter pluggable database TEST_CLON open; alter pluggable database TEST_CLON open * ERROR at line 1: ORA-65104: operation not allowed on an inactive pluggable database Cause The pluggable database status was UNUSABLE. It was still being created or there was an error during the create operation. A PDB can only be opened if it is successfully created and its status is marked as NEW in cdb_pdbs.status column SQL> select PDB_NAME,STATUS from cdb_pdbs; PDB_NAME             STATUS -------------------- --------------------------- PDB$SEED             NORMAL TEST_CLON            UNUSABLE Solution:  Drop the PDB and create it again. Related Posts How to Clone Oracle PDB (Pluggable Database) with in the Same Container
Post a Comment
Read more

ORA-16905: The member was not enabled yet

<<Back to Oracle DataGuard Main Page ORA-16905 Physical Standby Database is disabled DGMGRL> show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database (disabled)       ORA-16905: The member was not enabled yet. Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 58 seconds ago) DGMGRL> DGMGRL> enable database 'ORCL1PS'; Enabled. DGMGRL>  show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 38 seconds ago)
Post a Comment
Read more

How to Switch Log File from All Instances in RAC

<<Back to Oracle RAC Main Page Switch The Log File of All Instances in Oracle RAC. In many cases you need to switch the logfile of the database. You can switch logfile using alter system switch logfile command but if you want to switch the logfile from all the instances you need to execute the command on all the instances individually and therefore you must login on all the instances. You can avoid this and switch logfile of all instances by just running the below command from any of the instance in RAC database SQL> ALTER SYSTEM SWITCH ALL LOGFILE;   System altered.
Post a Comment
Read more

Starting RMAN and connecting to Database

  <<Back to Oracle Backup & Recovery Main Page Starting RMAN and connecting to Database Starting RMAN and connecting to Database To start RMAN you need to set the environment and type rman and press enter. You can connect to database either using connect command or using command line option. using command line option localhost:$ export ORACLE_HOME=/ora_app/product/18c/dbd2 localhost:$ export PATH=$ORACLE_HOME/bin:$PATH localhost:$ export ORACLE_SID=ORCL1P localhost:$ rman target / Recovery Manager: Release 18.0.0.0.0 - Production on Sun Apr 4 08:11:01 2021 Version 18.11.0.0.0 Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved. connected to target database: ORCL1P (DBID=4215484517) RMAN> using connect option localhost:$ rman RMAN> connect target sys@ORCL1P  target database Password:******** connected to target database: ORCL1P (DBID=4215484517) NOTE: To use connect command you need to ensure that  you have proper TNS sentry...
Post a Comment
Read more

How to Attach to a Datapump Job and Check Status of Export or Import

<<Back to Oracle DATAPUMP Main Page How to check the progress of  export or import Jobs You can attach to the export/import  job using ATTACH parameter of oracle datapump utility. Once you are attached to the job you check its status by typing STATUS command. Let us see how Step1>  Find the Export/Import Job Name You can find the datapump job information from  DBA_DATAPUMP_JOBS or  USER_DATAPUMP_JOBS view. SQL> SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME                       OPERATION            JOB_MODE   STATE ---------- ------------------------------ -------------------- ---------- ---------- SYSTEM     SYS_EXPORT_FULL_02          ...
7 comments
Read more

ORA-46655: no valid keys in the file from which keys are to be imported

<<Back to DB Administration Main Page SQL> administer key management import encryption keys with secret "xxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxx" with backup; administer key management import encryption keys with secret "xxxxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxxxx" with backup * ERROR at line 1: ORA-46655: no valid keys in the file from which keys are to be imported Cause: Either the keys to be imported already present in the target database or correct container (PDB) is not set. Solution: In my case I got the error because I attempted to import the keys for newly plugged database PDB02 from CDB$ROOT container. To Solve the issue just switched to the correct container and re run the import. SQL> show con_name CON_NAME ------------------------------ CDB$ROOT <===Wrong Container selected  SQL> alter session set container=PDB02; Session alt...
Post a Comment
Read more