Use the dbupdate tool that is provided by the
appliance to upgrade your external runtime databases, such as DB2, Oracle, PostgreSQL, and
solidDB.
About this task
Use this task if your Security Access Manager appliance version is 9.0.0.0 or later.
If your appliance version is earlier than 9.0.0.0, you must first update the appliance and the
external database to version 9.0.0.0 by using the following methods:
You must have Java version 8 or later to run the database update tool.
Procedure
-
In the local management interface, go to .
-
Expand .
-
Select the dbupdate9.zip file.
This file contains the database update tool (dbupdate.jar), the
README file, and update files for all databases and SQL types.
-
Click Export.
-
Save the file.
-
Extract the dbupdate9.zip file and run the
dbupdate.jar tool for your environment.
- The usage of the tool is as follows:
${JAVA_HOME}/bin/java -jar dbupdate.jar [-t] [-n]
<dbType> <sqlType> <connectString> <user> [<password>]
-t
- Enable debug trace output.
-n
- Do not perform any updates, but instead output the update operations that would have been
executed.
dbType
- The database type. Valid values are
config
or
runtime
.
sqlType
- The database server type. Valid values are
db2
, oracle
,
postgresql
, or soliddb
.
connectString
-
The string that is used when establishing a connection to the database server.
- db2
- Typically the database name, which is used in "
db2 CONNECT TO <connectString> USER
<user> USING <password>;
".
- oracle
- If the string is not empty, it corresponds to the value used for
sqlplus
"CONNECT <user>/<password>@<connectString>;
". If the string is empty (""),
the ORACLE_SID
environment variable is used.
- postgresql
-
The
connectString
for PostgreSQL contains the psql command line
options that need to be supplied to connect to the database. This usually consists of the hostname,
port and database name. For
example:
'--host=<hostname> --port=<port> --dbname=<db name>'
- soliddb
- Typically "
tcp <host> <port>
", which is used in the "solsql
<options> <connectString> <user> <password>
" command.
user
- Database user to update the database with.
password
- Database user's password. If not provided, the value is read from console.
Note: For DB2 external databases, the db2 command must be in
the path. For Oracle external databases, the sqlplus command must be in the path.
For PostgreSQL external database, the psql command must be in the path. For
SolidDB external databases, the solsql command must be in the path.
- Java 8 or later is required for running the tool.
- The following command shows an example of using the tool to update a DB2
database:
/opt/ibm/java-x86_64-80/jre/bin/java -jar dbupdate.jar runtime db2
"HVDB" db2inst1 passw0rd
The
following command shows an example of using the tool to update an Oracle
database:/opt/ibm/java-x86_64-80/jre/bin/java -jar dbupdate.jar runtime oracle
"" SYSTEM passw0rd
- If the tool is not flexible enough for your environment, you can see which commands
the tool runs without executing them and manually run those commands to suit your environment. To
see which commands the update tool runs against the database, run the tool with the
-n option. This option still must be able to read from the database to get
the current update versions in order to determine which updates to apply. However, it will not
execute any update operations.
- See the README file that is included in the
dbupdate9.zip file for more details about the update tool.