Online DBA

  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 -------------------

  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 -

  <<Back to DB Administration Main Page Creating and adjusting the config file for AutoUpgrade 19c Creating and adjusting the config file for AutoUpgrade 19c In this post I will show you , how you can create a simple AutoUpgrade config file and adjust it for a database upgrade. java -jar $OH19/rdbms/admin/autoupgrade.jar -create_sample_file config oracle@host1 :/oracle/software/autoupgrade/$ java -jar autoupgrade.jar -create_sample_file config Created sample configuration file /oracle/software/autoupgrade/sample_config.cfg sample output: cat /ora_stage/software/autoupgrade/sample_config.cfg # # Sample config file for AutoUpgrade # # build version 24.6.240905 # build date    2024/09/05 11:30:40 -0400 # # # Global configurations # # This directory will include the following: #   (1) AutoUpgrade''s global directory #   (2) Any logs, not directly tied to a job #   (3) Config files #   (4) progress.json and status.json global.autoupg_log_dir=/ora_app/cfgtoollogs/autoupgrade #

  <<Back to DB Administration Main Page Oracle Database AutoUpgrade tool Starting from oracle 19c there is a tool available to upgrade the databases. This is called oracle auto upgrade and is a recommended method  by oracle to upgrade the database. Start using and adopting it  soon this will be only way to upgrade the database  The idea of the tool is to run the prechecks against multiple databases, fix majority  of the potential issues, set a restore point in case something goes wrong – and then upgrade your databases. And of course, do the postupgrade, recompilation and time zone adjustment. The only thing you need to provide is a config file in text format How to download  AutoUpgrade Tool This tool is available with Oracle Database 19c (19.3)  You can download the most recent version from MOS Note: 2485457.1  AutoUpgrade documentation It is all here included in the Oracle Database 19c Upgrade Guide: Using AutoUpgrade for Oracle Database Upgrades Which database releases are su

  <<Back to Oracle Backup & Recovery Main Page Restoring/Recovering  Table  from RMAN Backup oracle 19c Point In Time table Restore/Recovery in Oracle Today I had a situation where application team accidently deleted data from a table in prod database and wanted to restore it from backup. The requirement was to restore the table with different name washout touching the original table so that the application team can compare it and find out the different eventually deleted rows Before 12.2 the task was complicated and it was achieved by restoring the full database on 3rd server and export  the table from restored database and import it in original database. Oracle has now automated the procedure and made it quite easy. Now you just have to run one command and the rest is taken care by oracle Scenarios Container DB Name: CDBDB Pluggable DB Name: PDB1 Table  to be restored: TEST Schema/Owner of the table: EMPLOYEE New Table Name After Restore: TEST_0701 Restore Timestamp: 01-JUL

  <<Back to Oracle RAC Main Page How to recreate GIMR diskgroup oracle RAC CREATE DISKGROUP GIMR NORMAL REDUNDANCY SITE S1 FAILGROUP GIMR_S1 DISK 'AFD:DISK1' SITE S2 FAILGROUP GIMR_S2 DISK 'AFD:DISK2' ATTRIBUTE 'compatible.asm'='12.1.0.0' , 'compatible.rdbms'='12.1.0.0'; CREATE DISKGROUP GIMR * ERROR at line 1: ORA-15018: diskgroup cannot be created ORA-15030: diskgroup name "GIMR" is in use by another diskgroup Reason:  I dropped the disk group GIMR using sqlplus and tried to create it again with the same name ended with above error message  Solution Though the diskgroup does not exists I dropped it again using asmcmd . Created the diskgroup again it worked  ASMCMD>  dropdg -r -f GIMR;

  <<Back to Oracle RAC Main Page How to re-create oracle RAC -MGMTDB database  Verify Status of -MGMTDB  prompt@node1:~/ [+ASM1]  srvctl status mgmtdb Database is enabled Instance -MGMTDB is running on node node1 prompt@node1:~/ [+ASM1] export ORACLE_SID=-MGMTDB prompt@node1:~/ [-MGMTDB] sqlplus "/as sysdba" Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production Version 19.16.0.0.0 SQL> show pdbs     CON_ID CON_NAME                       OPEN MODE  RESTRICTED ---------- ------------------------------ ---------- ----------          2 PDB$SEED                       READ ONLY  NO          3 MGMT_PDB_01                 READ WRITE NO SQL> select comp_id,status from dba_registry; COMP_ID                        STATUS ------------------------------ -------------------------------------------- CATALOG                        VALID CATPROC                        VALID RAC                            OPTION OFF XDB                            VA