[Deploying Sakai] Migrate Sakai 2.5.0 to 2.6.0

[leonardo jr escorido]

Hi Steve,

So here's what have been done up to this point.

1. Installed a fresh Sakai 2.6.0 which by default is pointing to 'sakai' database.

2. Backed up the production db (w/c is using Sakai 2.5.0 schema) and made a second copy of it. Upgraded that copy into 2.6 schema by executing the db scripts.

Next, how to point Sakai 2.6.0 to use the copy of the production db instead of the default 'sakai' db?


Thanks,
Leo

--- On Tue, 3/23/10, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:

From: Steve Swinsburg <steve.swinsburg at gmail.com>
Subject: Re: [Deploying Sakai] Migrate Sakai 2.5.0 to 2.6.0
To: "leonardo jr escorido" <escorido at yahoo.com>
Cc: production at collab.sakaiproject.org
Date: Tuesday, March 23, 2010, 3:13 PM

Hi Leo,
Comments inline:
blogger_file
 blogger_image
 blogger_post

These will be created when the tool is first accessed so are in 2.6.0
chat_channel
 chat_messageThese have been replaced by:chat2_channelchat2_message
If you don't have a chat2_* tables, something is wrong. These tables were added for 2.4.
 clemembership
Custom/Contrib
dp_datapoint
 dp_datapoint_submission
 dp_submitter_roleCustom/Contrib
dw_asn_assignment
 dw_asn_att
 dw_asn_*
 dw_form_data_evaluation
 dw_form_evaluation_levels
 dw_gmt_*Related to the rest of the dw_ tables for the Data Warehouse tool. Not seen in 2.6.
 edia_skinmanager_archive
EDIA Skin Manager tool, contrib.
gmt_context_association
 gmt_*
 Custom/Contrib?
hibernate_unique_keyUnknown.
hierarchy_node
 hierarchy_node_metaCustom/Contrib
(JForum)
 jforum_*JForum contrib tool
(Melete)
 melete_*Melete contrib tool
rsn_osp_*
rsn_to_*
rsn_tool_*Unknown.
sst_events
 sst_job_run
 sst_preferences
 sst_resources
 sst_siteactivity
 sst_sitevisits
SiteStats, contrib for 2.6, core for 2.7+

cheers,Steve

On 24/03/2010, at 12:35 AM, leonardo jr escorido wrote:
These are the tables in the customized Sakai not found in 2.6.0. I didn't put here all the table names. I think the contrib used can be recognized by their initials. My concern is the "clemembership" table, perhaps this table is being used by the class(es) created by the third party.
 

blogger_file
 blogger_image
 blogger_post

 chat_channel
 chat_message
 
 clemembership

 dp_datapoint
 dp_datapoint_submission
 dp_submitter_role

 dw_asn_assignment
 dw_asn_att
 dw_asn_*
 dw_form_data_evaluation
 dw_form_evaluation_levels
 dw_gmt_*
 
 edia_skinmanager_archive

 gmt_context_association
 gmt_*
 
 hibernate_unique_key
 
 hierarchy_node
 hierarchy_node_meta
 
(JForum)
 jforum_*

(Melete)
 melete_*

rsn_osp_*
 rsn_to_*
 rsn_tool_*
 
(SiteStats ? )
 sst_events
 sst_job_run
 sst_preferences
 sst_resources
 sst_siteactivity
 sst_sitevisits

Thanks,
Leo
--- On Tue, 3/23/10, Steve Swinsburg
 <steve.swinsburg at gmail.com> wrote:

From: Steve Swinsburg <steve.swinsburg at gmail.com>
Subject: Re: [Deploying Sakai] Migrate Sakai 2.5.0 to 2.6.0
To: "leonardo jr escorido" <escorido at yahoo.com>
Cc: production at collab.sakaiproject.org
Date: Tuesday, March 23, 2010, 1:18 AM

Hi Leo,
What are the tables and we can point you in the right direction for the contrib tools you might need to install to match.
That said, you should still be able to apply the conversion to the 2.5 database to bring it up to 2.6 and get it going. Extra tables shouldn't do any harm.
cheersSteve



      



      _______________________________________________
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"



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20100324/cb1021f4/attachment.html