Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Introduction

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.

If you have a question or a problem that you don't have a solution for, please join the rice.collab@kuali.org list by signing up at http://kuali.org/kis and post your question there.

2.0.0

See Rice 2.0 - Upgrade Troubleshooting

2.1.x

2.2.x

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:

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.

  • No labels