Database Patching

The database patching utility is delivered under SPLEBASE and is Java-based so you are able to create a standalone package to be able to install database patches on a separate server that has Java 8 installed. You can also install database patches using the components that are delivered under SPLEBASE without the need to move the database patching utility to a different server.

The following is an overview of the process to install database patches on a separate server. You will need to create a jar file containing the utilities and supporting files to allow you to run the database patch installer on another server.

To generate the jar file:

1. Initialize a command shell:

The scripts that are provided with the system need to be run from a shell prompt on the machine where you installed the application server. Before such scripts can be run the shell must be “initialized” by running the splenviron script provided with the system.

UNIX

Log on to your UNIX box as the Oracle Utilities Administrator (default cissys) and open a shell prompt.

In the following example, replace the variables:

• $SPLEBASE with the full directory name that you installed the application into.

• $SPLENVIRON with the name you gave to the environment at installation time.

To initialize the environment enter:

$SPLEBASE/bin/splenviron.sh -e $SPLENVIRON

For example:

/ouaf/DEMO/bin/splenviron.sh -e DEMO

Windows

The command window should be opened on the Windows server that you installed the application on.

In the below example you should replace the following variables:

• %SPLEBASE%: The full directory name that you installed the application into.

• %SPLENVIRON%: The name you gave to the environment at installation time.

To initialize the environment, type the following in your command prompt:

%SPLEBASE%\bin\splenviron.cmd -e %SPLENVIRON%

For example:

D:\ouaf\DEMO\bin\splenviron.cmd -e DEMO

2. Execute the following script to generate the jar file.

UNIX

ksh $SPLEBASE/bin/createDBStandlone.sh

Windows

%SPLEBASE%\bin\createDBStandlone.cmd

Note: By default, the output jar db_patch_standalone.jar is created in SPLEBASE/tools/dbstandalone. You can use the –l option to change the default directory.

3. Transfer the generated jar (db_patch_standalone.jar) to the Windows/Unix machine where you want to run the database patching utility.

4. Extract the contents of the archive file:

jar xvf db_patch_standalone.jar

Note: You must have Java 8 JDK installed on the machine to use the jar command. Be sure to install the JDK that is supported for your platform.

Overview of Database Patching Application

The database patching utility requires you have Java 7 JDK installed on the machine to execute the database patch application process.

The patch application process will perform following items to account for executing patch application under SPLEBASE or on a standalone server.

The database patch application utility will look do the following when it is executed:

• Checks to see if the environment variable $SPLEBASE is set.

If the $SPLEBASE variable is set, the utility uses the libraries under $SPLEBASE to apply the patch.

• When the $SPLEBASE is not set, the utility checks to see if the TOOLSBIN environment variable is set.

If the TOOLSBIN is set, the utility uses the libraries under the TOOLSBIN location.

• When both SPLEBASE and TOOLSBIN environment are not set, the utility prompts for the location of the TOOLSBIN.

The TOOLSBIN is the location of the of the application scripts ouafDatabasePatch.sh[cmd].

Unix Example

The TOOLSBIN location would be set to /ouaf/dbpatch/bin

export TOOLSBIN=/ouaf/dbpatch/bin

Unix Sample - Database Patch Application (ouafDatabasePatch.sh)

Note: The default permissions (ouafDatabasePatch.sh), may need to be adjusted to be executed by your user and group, when applying database fixes.

• Sample Execution – Passing a Password

./ouafDatabasePatch.sh -x ouafadm -p "-t O -d CISADM_Z1_12C_43030_BLD001,slc04lds:1522:Z143Q12C"

• Sample Execution – Prompting for a Password

./ouafDatabasePatch.sh -p "-t O -d CISADM_Z1_12C_43030_BLD001,slc04lds:1522:Z143Q12C"

• Sample Execution - passing in the tools bin location

/ouafDatabasePatch.sh -u

ouafDatabasePatch.sh [-h] [-u] [-v] [-x] [-t tools dir] [-p ouafparms]

-h displays help of ouafpatch

-u displays usage of ouafDatabasePatch.sh

-v displays version of ouafpatch

-x password to be passed to ouafpatch

-b location of the tools bin directory

-p parameters directly passed to ouafpatch must be the last parameter passed and be enclosed with quotes

WINDOWS Example

The TOOLSBIN location would be set to c:\ouaf\dbpatch\bin

SET TOOLSBIN=c:\ouaf\dbpatch\bin

Windows Sample - Database Patch Application (ouafDatabasePatch.cmd)

• Sample Execution – Passing a Password

ouafDatabasePatch.cmd -x password -p "-t O -d SCHEMA_NAME,DBSERVER:DBPORT:DBSID"

• Sample Execution – Prompting for a Password

ouafDatabasePatch.cmd –p “-t O -d SCHEMA_NAME,DBSERVER:DBPORT:DBSID C”

• Sample Execution - passing in the tools bin location

ouafDatabasePatch.cmd -b "C:\temp\db_patch_standalone\bin" -p "-t O -d SCHEMA_NAME,DBSERVER:DBPORT:DBSID -c C:\temp\dbrollup\CDXPatch2\CDXPatch.ini"

Windows Sample Usage:

ouafDatabasePatch.cmd -u

USAGE:

USAGE:ouafDatabasePatch.cmd[-h] [-u] [-v] [-x] [-b tools dir] [-p ouafparms]

USAGE: -h displays help of ouafpatch

USAGE: -u displays usage of ouafDatabasePatch.cmd

USAGE: -v displays version of ouafpatch

USAGE: -x password to be passed to ouafpatch

USAGE: -b location of the tools bin directory

USAGE: -p parameters directly passed to ouafpatch

USAGE: must be enclosed with quotes: " "

USAGE: