[midPoint] Migrating to another database

[Pavol Mederly]

Hello Aivo,


thank you for your comments.


I've fixed the wiki page - it really pointed to a wrong file.

As for the import: you're right, referential integrity can be a problem 
in this scenario. As for me, I usually import objects with the default 
settings. (But yes, Keep OID + Overwrite existing object is reasonable 
in your case, as we can expect conflicts on initial objects.)


I don't know about the status of MariaDB driver; maybe someone else 
could comment on this.


Best regards,

Pavol Mederly
Software developer
evolveum.com

On 09.08.2016 15:08, Aivo Kuhlberg wrote:
>
> Hi Pavol,
> Thanks for the useful tip. Exporting all objects made my migration to 
> MariaDB quite easy. Here are some things what I noticed and what may 
> be useful to other users:
>
>   * When creating initial database structure I selected wrong sql file
>     because of the information here
>     <https://wiki.evolveum.com/display/midPoint/MySQL>. File
>     midpoint-3.4/config/sql/midpoint/3.4/mysql/mysql-3.4.sql does not
>     contain all objects and had to use
>     midpoint-3.4/config/sql/_all/mysql-3.4-all.sql. I think the MySQL
>     wiki page needs to be corrected.
>   * When importing I accidently checked too many import options ("Keep
>     OID", "Overwrite existing object", "Referential integrity",
>     "Validate dynamic schema", "Validate static schema") but seems
>     that at last some of these options cause problems in import. I
>     think its because when importing objects from file some imported
>     objects may refer to objects which have not yet imported. So I
>     checked only 2 options in import dialog - "Keep OID" and
>     "Overwrite existing object".
>   * I did not succeed to set up database connection with MariaDB
>     connector. (Is this connector supported yet with midPoint?) So I
>     had to use MySQL connector.
>   * After migration I saw in my midPoint log file following error
>     messages: Can not read response from server. Expected to read 4
>     bytes, read 0 bytes before connection was unexpectedly lost. For
>     me the problem was solved when I changed database global setting
>     wait_timeout from 90 to 3600.
>
>
> Regards,
>
> Aivo
>
> ------------------------------------------------------------------------
> *Saatja:* midPoint <midpoint-bounces at lists.evolveum.com> nimelPavol 
> Mederly <mederly at evolveum.com>
> *Saadetud:* 4. august 2016 10:28
> *Adressaat:* midpoint at lists.evolveum.com
> *Teema:* Re: [midPoint] Migrating to another database
> I'm sorry I have to clarify myself: I meant exporting via midPoint, 
> i.e. "Export all objects" in Configuration -> Repository objects.
> You can then inspect generated XML and do any fixes you need manually 
> (if needed).
>
> Before importing, I'd delete automatically generated connector objects 
> from MariaDB, so the only ones left would be imported ones.
>
> Best regards,
> Pavol
>
> On 04.08.2016 9:11, Pavol Mederly wrote:
>>
>> Hello Aivo,
>>
>>
>> one of possible ways is to export all objects from H2 and re-import 
>> them to MariaDB.
>>
>> Beware of encrypted data compatibility - it's probably good idea to 
>> copy midPoint keystore before first start of midPoint in MariaDB.
>>
>>
>> Best regards,
>>
>> Pavol Mederly
>> Software developer
>> evolveum.com
>> On 04.08.2016 9:08, Aivo Kuhlberg wrote:
>>>
>>> I have so far used midPonit with embedded H2 database but now plan 
>>> to move to MariaDB. I can set up my test environment again from 
>>> scratch but it would be much easier to migrate existing data to 
>>> another database. Is there a (not too complicated) way to migrate 
>>> current midPoint data to another database?
>>>
>>>
>>> Thanks,
>>> Aivo Kuhlberg
>>>
>>>
>>> ------------------------------------------------------------------------
>>> Käesolev e-kiri võib sisaldada asutusesiseseks kasutamiseks 
>>> tunnistatud teavet.
>>> This e-mail may contain information which is classified for official 
>>> use.
>>>
>>>
>>> _______________________________________________
>>> midPoint mailing list
>>> midPoint at lists.evolveum.com
>>> http://lists.evolveum.com/mailman/listinfo/midpoint
>>
>>
>>
>> _______________________________________________
>> midPoint mailing list
>> midPoint at lists.evolveum.com
>> http://lists.evolveum.com/mailman/listinfo/midpoint
>
>
> ------------------------------------------------------------------------
> Käesolev e-kiri võib sisaldada asutusesiseseks kasutamiseks 
> tunnistatud teavet.
> This e-mail may contain information which is classified for official use.
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20160810/170c33a9/attachment.htm>