Answer
Confirm the installation is actually being run as the correct application-owner database account — running the installer as the wrong account is a real, if easy-to-overlook, cause of an installer failing to find an API procedure that does genuinely exist under the correct owner schema.