One of our clients had installed RAA v 184.108.40.206.
System requirements for RAA v220.127.116.11 were met; the installation went well & we were able to verify this, by scanning some sample code.
Later, after applying fixpack v 18.104.22.168, we are unable to bring up RAA. Attached is the error screenshot.
Please let us know if further information could help in resolving this issue.
Appreciate your response.
This topic has been locked.
4 replies Latest Post - 2012-10-30T09:43:13Z by SystemAdmin
Pinned topic Error when applying fixpack v 22.214.171.124 on RAA v 126.96.36.199
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-10-30T09:43:13Z at 2012-10-30T09:43:13Z by SystemAdmin
Re: Error when applying fixpack v 188.8.131.52 on RAA v 184.108.40.206012-10-25T16:43:14Z in response to SystemAdminEvery RAA fixpack is self contained, so if you can rescan all the content, I would just drop the old database, uninstall whatever you have and reinstall 220.127.116.11 fixpack fresh.
jcdelmo 0600012HN8292 PostsACCEPTED ANSWER
Re: Error when applying fixpack v 18.104.22.168 on RAA v 22.214.171.124012-10-25T16:45:29Z in response to SystemAdminThe attached screenshot does not show the entire message, it is truncated at the right.
Would you please post the value of the dbVersion property in the Internal.cfg file located in the <installDir>\config directory?
boyerpl 100000SWES105 PostsACCEPTED ANSWER
Re: Error when applying fixpack v 126.96.36.199 on RAA v 188.8.131.52012-10-25T19:17:58Z in response to SystemAdminWe can see from the partial message that the installed code is at the v601 schema level, but doesn't match what the database indicates. We need to know the database schema level, which should have been in the truncated part of that same message.
You can also find that level by performing the following DB2 commands to query the database:
1. Open a DB2 command window
Start -> Run... -> db2cmd.exe
2. Connect to the database (using your own userid/password)
db2 connect to dmhdb user MYUSER using MYPASSWORD
3. Perform the query (using your schema if different from dmh)
db2 select sys_int_attr from dmh.dmh_system_attr where sys_attr_id = 500
4. Disconnect from the database
db2 connect reset
If the schema is older than 601, you can migrate the database following instructions for the migration utility which can be found in the support area on the RAA product website.
Once the database is at the correct level, you need to restart WAS.