The resolution was to run the "install_hotfix_update_oracle_script.sql" script (found in the 83SP3-SQL_Update_Scripts.zip file) against the database.
The database Migration Manager only migrated the database version from 8.2.02 to 8.3.00. The script updates the version to 8.3.03.
Added this resolution as a knowledge capture.
That is what is laid out in the upgrade instructions…
There is only one reference to this on the Upgrade page at the beginning. But the docs continue with explicit instructions for you to follow depending on the database and OS. We followed through the docs to the end and there were no instructions on running these scripts after the database migration, so we thought we were done.
I posted this in case anyone else ran into this problem. I will make docs suggestion in the interim.
Application Server and Console:Special condition or scenario
If upgrading from a version earlier than 8.0 Run the postmigration file to migrate pre-8.x compliance rules and discovery signatures. If upgrading from 8.2.x or earlier Run the Data Migration Manager using the version 8.3 external files to upgrade your Oracle or SQL Server database to version 8.3. If smart group conditions were defined in any earlier version Run the postmigration file to migrate and update smart group conditions. Any upgrade Run the scripts found in the 83-SP3-SQL_Update_Scripts.zip file. This file is available in the BMC Server Automation 8.3.03 section of the EPD. Run these scripts as the BMC Server Automation database owner (as provided to blasadmin).
Correct, it's an overall guide to the process. Then you go to Upgrading section of the docs to actually walk through the process with instructions on how to perform each step.
Again, there is a mention of it on the first page, just like the SP page. But when you step through each process to upgrade, there are specific instructions on how to perform each step. There is no mention of this step, nor the instructions on how to perform it. Like all the other steps it should exist with or right after the Migration Manager step.
I think the issue is that in the ‘upgrading’ link you showed there it’s an upgrade to the GA release, not an upgrade to the SP. so do we need some text in the ‘upgrading’ section that links back to the SP upgrade instructions so that if you are upgrading to a SP you need to look there ?
Most upgrades would be to SPs and Patches, not the GA. So I think it should belong on the Upgrading area. Isn't this step always the same; run a DB script?
This step immediately follows the Migration Manager, so I would suggest adding this upgrade step after that, on that page. Rather than redirecting you back to the SP page. But as long as a page Export adds the child pages correctly, I don't think it matters where it lives. My personal preference is expanding through an area vs. jumping from place to place. That can get confusing.
I added that suggestion as a comment and the admins will update the doc accordingly. We can review it once they do.