IBM Security Verify

 View Only
  • 1.  ISAM 9.0.7.1 Upgrade

    Posted 13 days ago
    Hi Team, A customer is asking In the case of upgrading  ISAM 9.0.7.1 ,How does IBM support help on the upgrade? What information does IBM support request? Does anybody has information about or a link describing this IBM support process for the upgrade?

    https://www.ibm.com/support/pages/ibm-security-access-manager-security-verify-access-upgrade-paths-0

    Thanks in advance.
    Regards.


    ------------------------------
    David Vicenteño Sanchez
    ------------------------------


  • 2.  RE: ISAM 9.0.7.1 Upgrade
    Best Answer

    Posted 13 days ago
    Edited by JACK YARBOROUGH 13 days ago
    Hello David,

    This mainly has to do with a few things
    1. 9.0.7.2 is actually further along in firmware and fixes than 10.0.0.0, so if you are at 9.0.7.1 and go to 9.0.7.2 and then upgrade to 10.0.0.0 you are going backwards and may have issues. from 9.0.7.1 you should go to at least 10.0.2.0 and ideally 10.0.3.1

    2. When you install an appliance specific dates are put into a table in the internal configuration database and high volume database that state what SCHEMA file are installed. It is possible with NEW deployments of ISAM 9.0.7.1 to have dates that would prevent the SCHEMA from updating as expected when updating to a future firmware. Specifically if you install it and the 'dsu_version' has a value of '201912239' in the 'postgresql/hvdb.dat' or 'postgresql/config.dat' in a support file with the 'Cluster' selection then we would need to provide a Fixpack to internally change the date and ensure that future schema updates happen as expected.

    To validate a customer should create a support file from their Primary Master (if in a cluster) or the appliance in question (if a standalone appliance) and use the 'System' and 'Cluster' selections.

    Decompress the '.support' file using a compression tool (7zip is open source and my favorite) as it's a compressed archive and review the 'postgres/config.dat' and 'postgres/hvdb.dat' files.

    Here is a command line snippet that uses 'grep' to find the values (the '-A 2' flag doesn't work on AIX):
    grep -R -A 2 "dsu_version" postgresql/*
    postgresql/config.dat: dsu_install_date | dsu_version | dsu_file
    postgresql/config.dat-----------------------------+-------------+----------
    postgresql/config.dat- 2021-04-23 15:16:21.144262 | 201912239 | Install
    --
    postgresql/hvdb.dat: dsu_install_date | dsu_version | dsu_file
    postgresql/hvdb.dat-----------------------------+-------------+----------
    postgresql/hvdb.dat- 2021-03-25 11:09:29.300282 | 201912239 | Install

    Each one respectively should have a 'dsu_version' entry with a date. If that date matches the date above you will need to open a support case to acquire a Fixpack to correct the version. As you can see, my appliance would need the Fixpack since the dates are '201912239'.

    At this point you would engage support, present the technical document and the output above and we can provide the Fixpack for you.

    If you are using an external database for either the 'Configuration' or 'High Volume' database (config/hvdb) you'll need to manually update the values to '201906600' to ensure all schema updates are applied successfully.



    ------------------------------
    JACK YARBOROUGH
    ------------------------------



  • 3.  RE: ISAM 9.0.7.1 Upgrade

    Posted 7 days ago
    Hello Jack,

    What if we are at 9.0.7.1 and go to 9.0.7.2 and then upgrade to 10.0.3.0 ?

    Thanks,
    Nidhi Dahatkar

    ------------------------------
    SD Standard Aviva
    ------------------------------



  • 4.  RE: ISAM 9.0.7.1 Upgrade

    Posted 7 days ago
    Hello Nidhi,

    You still want to check the above condition and correct your databases if necessary to ensure that all updates apply successfully.

    ------------------------------
    JACK YARBOROUGH
    ------------------------------