Skip to content

Commit

Permalink
More changes
Browse files Browse the repository at this point in the history
  • Loading branch information
dohdatabase committed Dec 10, 2024
1 parent d8228cc commit 7366968
Show file tree
Hide file tree
Showing 4 changed files with 14 additions and 5 deletions.
6 changes: 4 additions & 2 deletions patch-me-if-you-can/02-simple-patching/simple-patching.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ Oracle recommends that you first check your database. AutoUpgrade in *analyze* m
-- Be sure to hit RETURN
```
* `source_home` and `sid` describes the current database.
* `source_home` and `sid` describe the current database.
* `target_home` is the location of the new Oracle home. It doesn't exist yet. AutoUpgrade creates it for you.
* `folder` is the location where AutoUpgrade can find and store patch files. Ideally, this location is a network share accessible to all your database hosts.
* `patch` informs AutoUpgrade which patches you want to apply. `RECOMMENDED` means the recent-most OPatch and Release Update plus matching OJVM and Data Pump bundle patches.
Expand Down Expand Up @@ -156,7 +156,9 @@ Oracle recommends that you first check your database. AutoUpgrade in *analyze* m
## Task 2: Patch database
Patching a single instance Oracle Database require downtime. Downtime starts now.
Patching a single instance Oracle Database require downtime.
**Downtime starts now.**
1. Start patching the database.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,8 @@ You use *OPatch* to perform the first part of patching an Oracle Database; patch
. upgr
cd $ORACLE_HOME
</copy>
-- Be sure to hit RETURN
```
2. You find OPatch in a subdirectory. Check the version of OPatch.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ You will use AutoUpgrade just like in lab 2.
-- Be sure to hit RETURN
```
* This config file is much simpler than the previous one from lab 2.
* This config file contains fewer parameters than the previous one from lab 2.
* Since the Oracle home exists, the patch process becomes easier.
* The *UPGR* database is not running ARCHIVELOG mode, so you must disable restoration.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -319,7 +319,7 @@ Install an Oracle manually. This allows you to compare the two methods.
-- Be sure to hit RETURN
```
2. Unzip the base release into the new Oracle home.
2. Unzip the Oracle Database 19.3 base release into the new Oracle home.
```
<copy>
Expand Down Expand Up @@ -450,8 +450,11 @@ Ensure that AutoUpgrade installed the Oracle home and perform a few checks.
```
<copy>
/u01/app/oracle/product/19_25_au/OPatch/opatch lspatches
export ORACLE_HOME=/u01/app/oracle/product/19_25_au
$ORACLE_HOME/OPatch/opatch lspatches
</copy>
-- Be sure to hit RETURN
```
* Because the config file contained `patch=RECOMMENDED` AutoUpgrade installed the recent-most Release Update and matching OPatch and bundle patches.
Expand Down Expand Up @@ -479,6 +482,7 @@ Now that AutoUpgrade has created the first Oracle home, you can start the instal
```
<copy>
export ORACLE_HOME=/u01/app/oracle/product/19_25_man
export PATH=$ORACLE_HOME/bin:$PATH
export ORAINVENTORY=/u01/app/oraInventory
export ORACLE_BASE=/u01/app/oracle
Expand Down Expand Up @@ -555,6 +559,7 @@ Now that AutoUpgrade has created the first Oracle home, you can start the instal
```
<copy>
export ORACLE_HOME=/u01/app/oracle/product/19_25_man
$ORACLE_HOME/OPatch/opatch lspatches
</copy>
```
Expand Down

0 comments on commit 7366968

Please sign in to comment.