[Deploying Sakai] Upgrading from sakai 2.5.4 to 2.6.x procedure?

[Matthew Jones]

You might want to check to see what (if anything) the subselect returns.

In oracle it would be something like this (for the first query)

select (select REALM_KEY from SAKAI_REALM where REALM_ID =
'!group.template.course'), (select ROLE_KEY from SAKAI_REALM_ROLE
where ROLE_NAME = 'Instructor'),(select FUNCTION_KEY from
SAKAI_REALM_FUNCTION where FUNCTION_NAME = 'site.viewRoster') from
dual;

. . .

You might (for some reason) be missing the viewRoster function added in
http://jira.sakaiproject.org/browse/SAK-2084
and considered for addition again in
http://jira.sakaiproject.org/browse/SAK-16121

(SQL for adding it on the second link)
On Sun, Jan 31, 2010 at 7:10 PM, Leon Kolchinsky <lkolchin at gmail.com> wrote:
> Hello,
>
> Finished running those 2 conversion scripts on 2.5.4 version:
> sakai-2-6-0-oracle-conversion.sql
> sakai_2_6_0-2_6_1_oracle_conversion.sql
> I've got some errors after running first script (full log attached):
> INSERT INTO SAKAI_REALM_RL_FN VALUES((select REALM_KEY from SAKAI_REALM
> where REALM_ID = '!site.template.course'), (select ROLE_KEY from
> SAKAI_REALM_ROLE where ROLE_NAME = 'Instructor'), (select FUNCTION_KEY from
> SAKAI_REALM_FUNCTION where FUNCTION_NAME = 'site.viewRoster'))
> *
> ERROR at line 1:
> ORA-00001: unique constraint (SAKAI.SYS_C003862) violated
>
>
> INSERT INTO SAKAI_REALM_RL_FN VALUES((select REALM_KEY from SAKAI_REALM
> where REALM_ID = '!group.template.course'), (select ROLE_KEY from
> SAKAI_REALM_ROLE where ROLE_NAME = 'Instructor'), (select FUNCTION_KEY from
> SAKAI_REALM_FUNCTION where FUNCTION_NAME = 'site.viewRoster'))
> *
> ERROR at line 1:
> ORA-00001: unique constraint (SAKAI.SYS_C003862) violated
>
>
> INSERT INTO SAKAI_REALM_RL_FN VALUES((select REALM_KEY from SAKAI_REALM
> where REALM_ID = '/site/mercury'), (select ROLE_KEY from SAKAI_REALM_ROLE
> where ROLE_NAME = 'maintain'), (select FUNCTION_KEY from
> SAKAI_REALM_FUNCTION where FUNCTION_NAME = 'site.viewRoster'))
> *
> ERROR at line 1:
> ORA-01400: cannot insert NULL into ("SAKAI"."SAKAI_REALM_RL_FN"."REALM_KEY")
>
>
> Any advice on how to fix those?
> Any highlights on these errors?
>
> Thanks guys
> On Thu, Jan 28, 2010 at 10:47 AM, Matthew Jones <jonespm at umich.edu> wrote:
>>
>> Right, as of now all of those conversions for .x are in that 2_6_0-2_6_1
>> script so you can just run the
>> sakai_2_6_0_oracle_conversion
>> and then
>> sakai_2_6_0-2_6_1_oracle_conversion.sql
>> and be currently be database up-to-date with 2.6.x.
>> If you continue to run on .x with auto.ddl=off you need to keep an eye on
>> the existence of conversion scripts in case there are any changes made.
>> There usually are not many conversions in minor releases but some
>> occasionally need to be made. This is perhaps an advantage of running on a
>> numbered release. (Better testing, and guarantee that someone else has run
>> the scripts on the QA's)
>> At Michigan we always run the db scripts to update the database, and run
>> some tools on the numbered release and some tools on the .x release.
>> On Wed, Jan 27, 2010 at 6:36 PM, Leon Kolchinsky <lkolchin at gmail.com>
>> wrote:
>>>
>>> Hi Matthew,
>>> So I can actually use only this script
>>> sakai_2_6_0-2_6_1_oracle_conversion.sql ?
>>>
>>> And sorry about mixing mysql and oracle, I'm actually using oracle.
>>>
>>> Regards,
>>> Leon
>>>
>>> On Thu, Jan 28, 2010 at 9:29 AM, Matthew Jones <jonespm at umich.edu> wrote:
>>>>
>>>> The path from 2.5.4 to 2.6.x is your second path (2)
>>>> sakai_2_6_0_<db>_conversion.sql (required 2.6 conversion)
>>>> Then the individual 2.6.x conversion scripts
>>>> sakai_2_6_0-2_6_x_<db>_conversion001_SAK-16668.sql
>>>> sakai_2_6_0-2_6_x_<db>_conversion002_SAK-16548.sql
>>>> sakai_2_6_0-2_6_x_<db>_conversion003_SAK-16847.sql
>>>> sakai_2_6_0-2_6_x_<db>_conversion004_SAK-10512.sql
>>>> The point release conversion script (2.6.0->2.6.1) is a roll-up of all
>>>> of the applicable _x conversion scripts (so it contains all 4 of those). You
>>>> can go from 2.5.4 straight to 2.6.0->2.6.x with the 2.6.0+2.6.x conversion
>>>> script(s) as that was then 2.6 was released. You don't need to upgrade to
>>>> 2.5.6. (However running that script won't hurt anything either as it is just
>>>> Updates which are just duplicated in another script)
>>>> In your example you mix and match oracle and mysql, make sure you use
>>>> all the same database type scripts. ;)
>>>> -Matthew
>>>> On Wed, Jan 27, 2010 at 1:05 AM, Leon Kolchinsky <lkolchin at gmail.com>
>>>> wrote:
>>>>>
>>>>> Hello Guys,
>>>>>
>>>>>
>>>>> I've installed Sakai 2.6.x from maintenance branch.
>>>>> On another server I have version 2.5.4 running and I'd like to upgrade
>>>>> to the latest 2.6.x version.
>>>>> I've read this http://confluence.sakaiproject.org/display/DOC/Sakai+2.6
>>>>> and this
>>>>> http://confluence.sakaiproject.org/display/REL/Sakai+2.6.x+Maintenance+Branch
>>>>> and am a little confused with the upgrade procedure.
>>>>> 1) Should the upgrade procedure be in this order?
>>>>> sakai_2_5_5-2_5_6_oracle_conversion.sql
>>>>> sakai_2_6_0-2_6_1_oracle_conversion.sql
>>>>> sakai_2_6_0-2_6_x_mysql_conversion001_SAK-16668.sql
>>>>> sakai_2_6_0-2_6_x_mysql_conversion002_SAK-16548.sql
>>>>> sakai_2_6_0-2_6_x_mysql_conversion003_SAK-16847.sql
>>>>> sakai_2_6_0-2_6_x_mysql_conversion004_SAK-10512.sql
>>>>>
>>>>> 2) Or may be I should use only this one?
>>>>> sakai_2_6_0_oracle_conversion.sql
>>>>> and those?
>>>>> sakai_2_6_0-2_6_x_mysql_conversion001_SAK-16668.sql
>>>>> sakai_2_6_0-2_6_x_mysql_conversion002_SAK-16548.sql
>>>>> sakai_2_6_0-2_6_x_mysql_conversion003_SAK-16847.sql
>>>>> sakai_2_6_0-2_6_x_mysql_conversion004_SAK-10512.sql
>>>>>
>>>>> Thanks,
>>>>> Leon
>>>>> _______________________________________________
>>>>> production mailing list
>>>>> production at collab.sakaiproject.org
>>>>> http://collab.sakaiproject.org/mailman/listinfo/production
>>>>>
>>>>> TO UNSUBSCRIBE: send email to
>>>>> production-unsubscribe at collab.sakaiproject.org with a subject of
>>>>> "unsubscribe"
>>>>
>>>
>>
>
>