Forum .LRN Q&A: Re: .LRN 2.1 a2 tagged

Collapse
27: Re: .LRN 2.1 a2 tagged (response to 1)
Posted by Nima Mazloumi on 09/21/04 02:31 PM
What we had to do to upgrade from 2.0.3 to 2.1 (Postgres):

1. file-storage upgrade failed
Commented line in upgrade-5.1.0d1-5.1.0d2.sql (line 49):
drop function file_storage__new_root_folder (integer);

2. static-portlet broken:
Changed query in static-portlet/www/element.xql to
select content ...

3. static-portlet broken:
Changed query in static-portlet/www/static-portlet.tcl
select content ...

4. static-portlet broken: static-portal-content-procs.xql
static_portal_content::update.update_content_item
static_portal_content::get_content.get_content.select

5. dotlrn/www/admin/cockpit.tcl
^M at the end of each line cause list builder problem. All were replaced.

6. Workflow packages failed to upgrade:
Several sql commands fails in upgrade-1.2-2.0d1.sql

psql:upgrade-1.2-2.0d1.sql:13: ERROR:  relation named "wf_roles_short_name_un" already exists
psql:upgrade-1.2-2.0d1.sql:14: ERROR:  relation named "wf_roles_pretty_name_un" already exists
psql:upgrade-1.2-2.0d1.sql:16: ERROR:  relation named "wf_actions_short_name_un" already exists
psql:upgrade-1.2-2.0d1.sql:17: ERROR:  relation named "wf_actions_pretty_name_un" already exists
psql:upgrade-1.2-2.0d1.sql:19: ERROR:  relation named "wf_fsm_states_short_name_un" already exists
psql:upgrade-1.2-2.0d1.sql:20: ERROR:  relation named "wf_fsm_states_pretty_name_un" already exists
psql:upgrade-1.2-2.0d1.sql:24: ERROR:  Relation "workflow_initial_action" does not exist
psql:upgrade-1.2-2.0d1.sql:36: ERROR:  Cannot create unique index. Table contains non-unique values
psql:upgrade-1.2-2.0d1.sql:50: ERROR:  relation named "workflow_deputies_deputy_idx" already exists
psql:upgrade-1.2-2.0d1.sql:57: ERROR:  ALTER TABLE / DROP CONSTRAINT: wf_cases_object_id_un does not exist
psql:upgrade-1.2-2.0d1.sql:61: ERROR:  relation named "wf_fsm_states_workflow_idx" already exists
psql:upgrade-1.2-2.0d1.sql:64: ERROR:  ALTER TABLE / DROP CONSTRAINT: wf_fsm_acn_enb_in_st_acn_id_fk does not exist
psql:upgrade-1.2-2.0d1.sql:68: ERROR:  relation named "wf_fsm_act_en_in_st_action_idx" already exists
psql:upgrade-1.2-2.0d1.sql:69: ERROR:  relation named "wf_fsm_act_en_in_st_state_idx" already exists
psql:upgrade-1.2-2.0d1.sql:80: ERROR:  ALTER TABLE: column name "parent_action_id" already exists in table "workflow_actions"
psql:upgrade-1.2-2.0d1.sql:86: ERROR:  ALTER TABLE: column name "trigger_type" already exists in table "workflow_actions"
psql:upgrade-1.2-2.0d1.sql:92: ERROR:  Relation "workflow_initial_action" does not exist
psql:upgrade-1.2-2.0d1.sql:93: ERROR:  table "workflow_initial_action" does not exist
psql:upgrade-1.2-2.0d1.sql:97: ERROR:  ALTER TABLE: column name "timeout" already exists in table "workflow_actions"
psql:upgrade-1.2-2.0d1.sql:105: ERROR:  ALTER TABLE: column name "parent_action_id" already exists in table "workflow_fsm_states"
psql:upgrade-1.2-2.0d1.sql:106: ERROR:  relation named "wf_fsm_states_prnt_action_idx" already exists
psql:upgrade-1.2-2.0d1.sql:110: ERROR:  Relation 'workflow_case_enbl_act_seq' already exists
psql:upgrade-1.2-2.0d1.sql:134: ERROR:  Relation 'workflow_case_enabled_actions' already exists
psql:upgrade-1.2-2.0d1.sql:136: ERROR:  relation named "wf_case_enbl_act_case_idx" already exists
psql:upgrade-1.2-2.0d1.sql:137: ERROR:  relation named "wf_case_enbl_act_action_idx" already exists
psql:upgrade-1.2-2.0d1.sql:151: ERROR:  Relation 'workflow_case_action_assignees' already exists
psql:upgrade-1.2-2.0d1.sql:153: ERROR:  relation named "wf_case_actn_asgn_en_act_idx" already exists
psql:upgrade-1.2-2.0d1.sql:154: ERROR:  relation named "wf_case_actn_asgn_party_idx" already exists
psql:upgrade-1.2-2.0d1.sql:161: ERROR:  ALTER TABLE: column name "parent_enabled_action_id" already exists in table "workflow_case_fsm"
psql:upgrade-1.2-2.0d1.sql:165: ERROR:  relation named "wf_case_fsm_case_parent_un" already exists
psql:upgrade-1.2-2.0d1.sql:167: ERROR:  relation named "wf_case_fsm_prnt_enbl_actn_idx" already exists
psql:upgrade-1.2-2.0d1.sql:168: ERROR:  relation named "workflow_case_fsm_state_idx" already exists
psql:upgrade-1.2-2.0d1.sql:184: ERROR:  Cannot drop view workflow_case_assigned_actions because other objects depend on it

Any idea?

Greetings,
Nima

Collapse
32: Re: .LRN 2.1 a2 tagged (response to 27)
Posted by Bruce Spear on 10/22/04 11:56 AM
Hi Nima:  Where are you now with the upgrade?  I'm now ready to upgrade from 2.0.3 to 2.1 and am studying the general upgrade instructions.  You indicate some problems that I might run into: have you (and others!) solved them, and if so, I'd love to spare myself some trouble by hearing about it.  Thanks!  Bruce
Collapse
33: Re: .LRN 2.1 a2 tagged (response to 32)
Posted by Hector Amado on 10/22/04 06:36 PM
Hi Bruce,

  I've finished the upgrade,

  Working with postgres, from 2.0.3 (tarball)) to 2.1.0b2 (oacs-5-1)


  dotlrn:
    tcl/apm-callback-procs.tcl

    I changed the apm_upgrade_logic from  2.0.3 2.1.0  to  2.0.3 2.1.0b2


  file-storage:
    upgrade-5.1.0d1-5.1.0d2.sql
        The script did not work,  i commented this line:
        line 49
        -- drop function file_storage__new_root_folder(integer);

        This line was a problem for me because i did not have the
        function file_storage__new_root_folder(integer) so i don`t
        know if i should commit this change.


workflow:
    upgrade-1.2-2.0d1.sql

    I had a problem with this script because it alters a table:

    alter table workflow_fsm_action_en_in_st add constraint
    workflow_fs_action_en_in_st_pk primary key (action_id, state_id);

    The instruction crash because i had duplicate rows, I deleted the
    rows,

    delete from workflow_fsm_action_en_in_st where action_id='4'; ...

    Check the table before running the script.

file-storage:
    upgrade-5.1.0a6-5.1.0a7.sql

    I had a problem with a constraint, but it was a problem with a
    row in my system, i searched the row and change a title.


  static-portlet:
    upgrade-2.0.3d1-2.0.3d2.sql

    This script was not run in the upgrade, check if it is in the
    list of scripts to run, if not run it manually after the upgrade.

    psql -f
    packages/static-portlet/sql/postgresql/upgrade/upgrade-2.0.3d1-2.0.3d2.sql ....



    These were my troubles,  if you have a problem with a script it
    will be because a row in your system or a constraint.
    See your table and modify or delete rows.


    I did the upgrade for two sites,  form 2.0.3 to 2.1.0a2 / 2.1.0b2
    You can use the tarball beta 2.1.0b1 or a checkout from oacs-5-1


    Best Regards,
    Héctor.