sthild at gmail
May 4, 2012, 9:33 AM
Post #13 of 14
(689 views)
Permalink
|
On 05/04/2012 08:14 AM, Pedro Albuquerque wrote:
> Hi Scott,
>
> I successfully migrated from MySQL to Oracle thanks to your script!
I don't know who wrote the script originally , but big thanks to them.
> I just had to make some minor changes but that was it.
> Regarding the sequences, I had to create a PL/SQL procedure to update
> the sequences.currval to have the max id for each table.
Yes, forgot to mention that one.
>
> Many thanks for your help :)
You're welcome, glad it went smooth. Best advice is not to use the
migration tool in SQLDeveloper, we
burnt a lot of time trying to get that to work. We should add the
sequence update to the code
and post it to the wiki.
>
> Cheers,
> Pedro.
>
> On 03/05/2012 15:04, Pedro Albuquerque wrote:
>> Hi Scott,
>>
>> Many thanks for the script and explanation.
>> I will take a look at this and will get back to you.
>>
>> Cheers,
>> Pedro.
>>
>> On 02/05/2012 23:16, Scott wrote:
>>> We did this awhile ago, so my memory may be a little fuzzy. First
>>> off forget the SQLDeveloper migration,
>>> it mostly works but you have to work around some issues. Our
>>> biggest issue was that mysql defaults to
>>> utf8 and our Oracle DB's are not utf8, so some of the stored
>>> documents (mostly word) have don't totally
>>> display right. I thinks its just the apostrophes, quotes, ...etc.
>>> Another issue is that RT doesn't like to
>>> use blobs in PostgreSQL & Oracle, so they base64 encode binary
>>> objects and store them in clobs. Like
>>> I said earlier I just modified the PostgreSQL migration script.
>>> I've attached the script, you probably don't
>>> need the NLS_LANG env setting or you may not want my NLS_DATE_FORMAT
>>> setting. I really didn't change
>>> much. I did add a new table list, just commented out the old one.
>>> So after all our messing around with
>>> the SQLDeveloper migration tool, we had success by using the Oracle
>>> table create sql that comes with
>>> the RT dist and running the attached script. As I said I may be
>>> forgetting a step, but give it a whirl. If
>>> you have questions, I will do my best to answer.
>>>
>>> Scott
>>>
>>>
>>> On 05/02/2012 10:15 AM, Pedro Albuquerque wrote:
>>>> Many thanks Scott.
>>>> Looking forward to hearing from you.
>>>>
>>>> Cheers,
>>>> Pedro.
>>>>
>>>> On 02/05/2012 16:14, Scott wrote:
>>>>> I have done it, let me gather what we did and I will it to you.
>>>>> I think I used the postgresql script and just modified it. Sorry I'm
>>>>> swamped right now, but I will get back to you later today.
>>>>>
>>>>>
>>>>> n 05/02/2012 08:59 AM, pedroalb wrote:
>>>>>> Hi,
>>>>>>
>>>>>> I took a look at the PostgreSQL scripts but they fail, for
>>>>>> instance, when
>>>>>> migrating the attachments. Encoding is base64 in Oracle and other
>>>>>> errors
>>>>>> occur.
>>>>>> I am wondering why RT mentions it is possible to migrate using
>>>>>> Oracle SQL
>>>>>> developer if it does not work? Does anybody successfully migrated
>>>>>> RT from
>>>>>> MySQL to Oracle?
>>>>>>
>>>>>> Cheers,
>>>>>> Pedro.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Pedro Albuquerque-3 wrote:
>>>>>>>> Thanks for the info.
>>>>>>>> I will take a look at these scripts and try to use them in Oracle.
>>>>>>>>
>>>>>>>> I'll get back to you with updates.
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Pedro.
>>>>>>
>>>>>> Pedro Albuquerque-3 wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> I am trying to migrate mysql to oracle to have full text search.
>>>>>>> I updated successfully a RT 3.6.10 to RT 4.0.5 using mysql.
>>>>>>> However, when
>>>>>>> I
>>>>>>> migrate data and objects to oracle using sql developer, there is
>>>>>>> some
>>>>>>> issues in the attachments encoding, for instance.
>>>>>>>
>>>>>>> Does anyone has migrated from mysql to oracle?
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Pedro.
>>>>>>>
>>>>>>>
>>>>>
>>>
|
