Skip to content

Commit

Permalink
rhpam version changes implemented
Browse files Browse the repository at this point in the history
  • Loading branch information
veena-ux committed Dec 6, 2024
1 parent d2128c5 commit 5db9e29
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions migration-guide/redhat-to-ibm.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -432,20 +432,20 @@ They are all mapped by the version progression, so it will be fairly quick.
So, for instance, if you are running a PostgreSQL database, you must do the following:

. Connect to your database instance using your method of preference.
. Apply the SQL scripts appropriate for the version you are migrating from up to RHPAM 7.13.
. Apply the SQL scripts appropriate for the version you are migrating from up to RHPAM 7.13.x

[source,shell,subs="attributes+"]
----
...
$ psql -h $dbhost -U $user < rhpam-7.11-to-7.12.sql
$ psql -h $dbhost -U $user < rhpam-7.12-to-7.13.sql
$ psql -h $dbhost -U $user < rhpam-7.13-to-7.13.1.sql
$ psql -h $dbhost -U $user < rhpam-7.13.1-to-7.13.2.sql
$ psql -h $dbhost -U $user < rhpam-7.13.2-to-7.13.3.sql
...
----

[NOTE]
====
{PRODUCT_SHORT} version {VERSION_80}'s database is compatible with {RH_PAM} 7.13, so all you need to do is to update the database to that level, and you will be set to migrate the rest of your application.
{PRODUCT_SHORT} version {VERSION_80}'s database is compatible with {RH_PAM} 7.13.x, so all you need to do is to update the database to that level, and you will be set to migrate the rest of your application.
====

Once you have executed these SQL statements, your datasource is now up to date.
Expand Down

0 comments on commit 5db9e29

Please sign in to comment.