Grouper Users - Open Discussion List

[Satya Mohapatra <>]

Hi, 

I have a problem with grouper database migration from one system to another.  
I am trying to move the backend grouper database from system A —to—> B with 
identical grouper version and patch applied.  

While importing the database dumped from system A to system B, I am seeing 
"Cannot add foreign key constraint” error. I gather it has to do with the 
different versions of innodb. 

Is there a way to take care of it via grouper API without really going to the 
database and fixing those entries ?


---------------------------------------------------------------------------
System [A]

Grouper version 2.3, at API patch 110. 
Tomcat version 8. 


# java -version
java version "1.7.0_231"
OpenJDK Runtime Environment (IcedTea 2.6.19) (7u231-2.6.19-1~deb8u2)


# mysql --version
mysql  Ver 14.14 Distrib 5.5.62, for debian-linux-gnu (x86_64) using readline 
6.3


mysql> SHOW GLOBAL VARIABLES LIKE 'innodb_ver%';
+----------------+--------+
| Variable_name  | Value  |
+----------------+--------+
| innodb_version | 5.5.62 |
+----------------+--------+

---------------------------------------------------------------------------

System  [B]

Grouper version 2.3, at API patch 110. 
Tomcat version 9. 

# java -version
openjdk version "1.8.0_232-ea"

# mysql --version
mysql  Ver 14.14 Distrib 5.7.26, for Linux (x86_64) using  EditLine wrapper


l> SHOW GLOBAL VARIABLES LIKE 'innodb_ver%’;
+----------------+--------+
| Variable_name  | Value  |
+----------------+--------+
| innodb_version | 5.7.26 |
+----------------+--------+



Thanks,
---
Satya Mohapatra | ସତ୍ୟ ମହାପାତ୍ର |  सत्य महापात्र |  ستیا موہپترا

Attachment: smime.p7s
Description: S/MIME cryptographic signature