Skip to main content

Oracle Autoupgrade Options

 

Oracle Autoupgrade Available Commands


<<Back to DB Administration Main Page

java -jar autoupgrade.jar -help

Usage: java -jar autoupgrade.jar <option(s)>

Syntax: <required> [optional] default*


options = <run_type1|run_type2|run_type3>


run_type1 = -version | -help | -create_sample_file <options> | -listchecks <checkName>


run_type2 = [-settings <settings>]

            <-config <config>|-config_values <config_values>>

            [-mode <mode>]

            [-load_password]

            [-restore_on_fail]

            [-console | -noconsole]

            [-debug]

            [-clear_recovery_data [-jobs job#,job#,...]]

            [-restore -jobs <job#,job#,...>]>

            [-zip [-sid <sid>] [-d <dir>] [-zip_exclusion_list <list>]]


run_type3 = -preupgrade <preupgrade>

            [-mode <analyze|fixups|postfixups>]

            [-debug]


-help*

Displays available options.


Example:

java -jar autoupgrade.jar -help


-version


Displays the AutoUpgrade version


Example:

java -jar autoupgrade.jar -version


-listchecks


List all checks or specified check


Example:

java -jar autoupgrade.jar -listchecks

java -jar autoupgrade.jar -listchecks ORACLE_RESERVED_USERS


-error_code [errorcode]


errorcode  - Error to be filtered .


Displays the AutoUpgrade error codes


Example:

java -jar autoupgrade.jar -error_code

java -jar autoupgrade.jar -error_code UPG-3101


-create_sample_file <config [filename] [type] | settings [filename]>


type     = [full*|unplug|noncdbtopdb]

config   - Creates a sample configuration file.

settings - Creates a sample internal configuration file to

overwrite default configuration settings.

filename - The name of the config or settings file to create.

type     - The type of config file to generate.


Creates a sample configuration file that can be used as reference.


Example:

java -jar autoupgrade.jar -create_sample_file settings settings.cfg

java -jar autoupgrade.jar -create_sample_file config config.cfg

java -jar autoupgrade.jar -create_sample_file config config.cfg unplug


-settings <settings_path>


settings_path - Path to internal settings file to overwrite the

                default values.


Overwrites the default internal settings.

This is not needed for most cases.


Example:

java -jar autoupgrade.jar -settings settings.cfg -config config.cfg -mode analyze


-config <config_path>


config_path - User config file with the databases to upgrade or patch.


Specifies the user config file with the database(s) to upgrade or patch.


Example:

java -jar autoupgrade.jar -config config.cfg -mode analyze


-config_values <config_values>


config_values - User input comma-separated list where *

                separates database entries.


Specifies the content of the configuration file without creating one,

it will read the ORACLE_HOME,ORACLE_SID,ORACLE_TARGET_HOME

and ORACLE_TARGET_VERSION from the environmental variables.


Example:

java -jar autoupgrade.jar -config_values "source_home=value,...*,source..." -mode analyze


-preupgrade <preupgrade>


preupgrade - User input comma-separated preupgrade options.


Makes the autoupgrade behave as the legacy preupgrade tool,

it will read the target ORACLE_HOME and ORACLE_VERSION

from the environmental variables.


Example:

java -jar autoupgrade.jar -preupgrade "target_version=21,dir=/tmp/log" -mode fixups


-clear_recovery_data [-jobs jobs_number]


jobs_number - comma-separated list of jobs to clear


Removes the recovery information which causes AutoUpgrade to start from

scratch on the specified or all databases. Use after manually restoring a

database and attempting a new upgrade or patch.

If no list of jobs is provided by default all the metadata is removed,

this will not remove log files or reset the jobid counter, only the

AutoUpgrade files used to keep track of the progress of each job.


Example:

java -jar autoupgrade.jar -config config.cfg -clear_recovery_data

java -jar autoupgrade.jar -config config.cfg -clear_recovery_data -jobs 111,222


-mode <mode>


mode = <analyze|fixups|deploy|upgrade|postfixups>

analyze  -   Executes the checks in the source home

             database readiness status.

fixups   -   Executes the checks and pre-upgrade fixups but does not perform

             the upgrade or patch.

deploy   -   Performs the upgrade or patching of the databases from start to end.

upgrade  -   Performs the database upgrade or patching and post actions.

             The database must already be up and running in the target home.

postfixups - Executes the postfixups in the target home.


Mode on which the AutoUpgrade will start and behave.


Example:

java -jar autoupgrade.jar -config config.cfg -mode analyze

java -jar autoupgrade.jar -config config.cfg -mode deploy

java -jar autoupgrade.jar -preupgrade "target_version=21" -mode fixups


-load_password


Initiates an interactive console allowing passwords to be

loaded into AutoUpgrade's keystore


-console*


Start the AutoUpgrade with the console enabled.


-noconsole


Start the AutoUpgrade with the console disabled.


-restore_on_fail


If present, when a job fails, the database is restored automatically.

Errors in PDBs are not considered irrecoverable, only errors in

CDB$ROOT or Non-CDBs


-debug


Debug messages enabled


-restore -jobs <job#,job#,...>


job#,job#,... - comma-separated jobs list to restore


Executes a system-level restoration of the specified jobs.

The databases are flashed back to the Guarantee Restore Point (GRP).

The GRP must have been created by AutoUpgrade prior this command is run.

The console is disabled by default.


Example:

java -jar autoupgrade.jar -config config.cfg -restore -jobs 111

java -jar autoupgrade.jar -config config.cfg -restore -jobs 111,222 -console

java -jar autoupgrade.jar -config config.cfg -restore -jobs 111,222 -noconsole


-zip [-sid <sid>] [-d <dir>] [-zip_exclusion_list <list>]


-sid <sid>  - Zip file will contain all the SIDs that are given in a

              comma separated list.

-d <dir>    - Directory path to save AutoUpgrade zip

-zip_exclusion_list <list> - A double comma separated regular string list to exclude all matched files in the zip file


Zips up log files required for filing an AutoUpgrade service request

If no "sid" is passed, it will create a zip file for all databases

in the config file.

If "zip_exclusion_list" is passed, it will exclude all files that match zip_exclusion_list


Example:

java -jar autoupgrade.jar -config config.cfg -zip

java -jar autoupgrade.jar -config config.cfg -zip -sid db18700

java -jar autoupgrade.jar -config config.cfg -zip -sid db18700,db19300

java -jar autoupgrade.jar -config config.cfg -zip -zip_exclusion_list "db18700/.*"

java -jar autoupgrade.jar -config config.cfg -zip -sid db18700 -d /tmp/

java -jar autoupgrade.jar -config config.cfg -load_win_credential <prefix>

- Opens a WinCredential cmdlet which prompts for user name and password and stores the values into an encrypted credential.


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