Skip to end of metadata
Go to start of metadata

 

 

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.

Database Upgrade Paths

Between Rice 2.1.2 and 2.2.4, the Rice team was making database changes on parallel branches of development, which made for some confusion around upgrade paths.  The following diagram attempts to clarify the situation (click "zoom" button to enlarge):

Gliffy Zoom Zoom rice-db-upgrade-paths

The upgrade scripts themselves can be found under:

2.0.0

See Rice 2.0 - Upgrade Troubleshooting

2.1.x

The SESN_ID column on the KRNS_PESSIMISTIC_LOCK_T table needs to have a DEFAULT of 'undefined' to prevent issues

If your standalone server or client database has this issue (KULRICE-9288), you can correct it by running the appropriate script for you db platform:

Alternatively, if you upgrade your schema to Rice 2.1.6 using the upgrade scripts, then the issue will be automatically corrected.

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.

The SESN_ID column on the KRNS_PESSIMISTIC_LOCK_T table needs to have a DEFAULT of 'undefined' to prevent issues

If your standalone server or client database has this issue (KULRICE-9288), you can correct it by running the appropriate script for you db platform:

Alternatively, if you upgrade your schema to Rice 2.2.4 using the upgrade scripts, then the issue will be automatically corrected.

scripts/upgrades/2.2.1 to 2.2.2/final/update_client_final_oracle.sql contains a bug that causes it to fail to execute

  • No labels