How to prepare a response file for a grid 18c silent upgrade
Due to security and complexity of the environment, the option to use Graphical User Interface (GUI) is not always available. Upgrade operations will need to be performed from the command line interface (CLI). Determine groups assigned to grid and oracle user: [code] [oracle@racnode-dc1-1 ~]$ id grid uid=54320(grid) gid=54321(oinstall) groups=54321(oinstall),54318(asmdba),54319(asmoper),54320(asmadmin),54322(dba) [oracle@racnode-dc1-1 ~]$ id oracle uid=54321(oracle) gid=54321(oinstall) groups=54321(oinstall),54318(asmdba),54320(asmadmin),54322(dba),54323(backupdba),54324(oper),54325(dgdba),54326(kmdba) [oracle@racnode-dc1-1 ~]$ [/code] Create response file gridsetup_upgrade.rsp from gridsetup.rsp. There are 667 lines from gridsetup.rsp and it's not efficient to view the entire file to identify modifications. [code] [oracle@racnode-dc1-1 18cLinux]$ wc -l gridsetup.rsp 667 gridsetup.rsp [oracle@racnode-dc1-1 18cLinux]$ [/code] One method to identify change: [code] [oracle@racnode-dc1-1 18cLinux]$ egrep -v "^#" gridsetup_upgrade.rsp | awk -F'=' '$2' oracle.install.responseFileVersion=/oracle/install/rspfmt_crsinstall_response_schema_v18.0.0 INVENTORY_LOCATION=/u01/app/oraInventory oracle.install.option=UPGRADE ORACLE_BASE=/u01/app/oracle oracle.install.asm.OSDBA=asmdba oracle.install.asm.OSOPER=asmoper oracle.install.asm.OSASM=asmadmin oracle.install.crs.config.scanType=LOCAL_SCAN oracle.install.crs.config.ClusterConfiguration=STANDALONE oracle.install.crs.config.configureAsExtendedCluster=false oracle.install.crs.config.gpnp.configureGNS=false oracle.install.crs.config.ignoreDownNodes=false [/code] Another option is to use sdiff; however, a disadvantage is that it does not provide a version for a response file: [code] [oracle@racnode-dc1-1 18cLinux]$ sdiff -iEZbWBst -w 120 gridsetup.rsp gridsetup_upgrade.rsp INVENTORY_LOCATION= | INVENTORY_LOCATION=/u01/app/oraInventory oracle.install.option= | oracle.install.option=UPGRADE ORACLE_BASE= | ORACLE_BASE=/u01/app/oracle oracle.install.asm.OSDBA= | oracle.install.asm.OSDBA=asmdba oracle.install.asm.OSOPER= | oracle.install.asm.OSOPER=asmoper oracle.install.asm.OSASM= | oracle.install.asm.OSASM=asmadmin oracle.install.crs.config.scanType= | oracle.install.crs.config.scanType=LOCAL_SCAN oracle.install.crs.config.ClusterConfiguration= | oracle.install.crs.config.ClusterConfiguration=STANDALONE oracle.install.crs.config.configureAsExtendedCluster= | oracle.install.crs.config.configureAsExtendedCluster=false oracle.install.crs.config.gpnp.configureGNS= | oracle.install.crs.config.gpnp.configureGNS=false oracle.install.crs.config.ignoreDownNodes= | oracle.install.crs.config.ignoreDownNodes=false [oracle@racnode-dc1-1 18cLinux]$ -i, --ignore-case -E, --ignore-tab-expansion -Z, --ignore-trailing-space -b, --ignore-space-change -W, --ignore-all-space -B, --ignore-blank-lines -s, --suppress-common-lines -t, --expand-tabs (expand tabs to spaces in output) -w, --width=NUM [/code] In conclusion, the steps outlined should provide for a more efficient method to provide only pertinent changes for the response file.
Share this
You May Also Like
These Related Stories
Favorite way: migrating to exadata
Favorite way: migrating to exadata
Sep 9, 2015
1
min read
Fix: The Instance ID 'MSSQLServer' is Already in Use by SQL Server Instance 'MSSQLServer.Inactive'
Fix: The Instance ID 'MSSQLServer' is Already in Use by SQL Server Instance 'MSSQLServer.Inactive'
Sep 27, 2023
2
min read
Merge Replication Identity Range Management - An Identity Disorder? Part 2
Merge Replication Identity Range Management - An Identity Disorder? Part 2
Feb 4, 2014
5
min read
No Comments Yet
Let us know what you think