This page is intended to house resources and facilitate information sharing on troubleshooting upgrades to Kuali Rice. Feel free to post comments or add topics to this page in order to help others in the community should they encounter similar issues.
Client datasets that were upgraded to 2.2 or 2.2.1 are missing the KRAD_MSG_T table
If your client dataset has this issue (KULRICE-9179), you can correct it by running the appropriate script for your db platform:
- for Oracle: https://svn.kuali.org/repos/rice/tags/rice-2.2.0/scripts/upgrades/2.1%20to%202.2/db-updates/2012-08-29.sql
- for MySQL: https://svn.kuali.org/repos/rice/tags/rice-2.2.0/scripts/upgrades/2.1%20to%202.2/db-updates/mysql-2012-08-29.sql
Alternatively, if you upgrade your schema to Rice 2.2.2 using the upgrade scripts, then the issue will be automatically corrected.\
KRAD_MSG_T primary key is too long for MySQL 5.1 - (Rice 2.2 through 2.2.1)
There is a known issue (KULRICE-9152) with the Rice schema and MySQL 5.1 due to the PK size for the KRAD_MSG_T table. The error message for this issue looks something like this:
If you are unable to impex a Rice database due to this issue, edit the
db/impex/<dataset>/src/main/resources/schema.xml file and reduce the KRAD_MSG_T.LOC column size from 255 to 80. After making this change, you should be able to successfully create a Rice database using impex with MySQL 5.1.