Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] foreign key constraint error with grouper database migration between identical grouper version

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] foreign key constraint error with grouper database migration between identical grouper version


Chronological Thread 
  • From: "Hyzer, Chris" <>
  • To: Satya Mohapatra <>, grouper-users <>
  • Subject: RE: [grouper-users] foreign key constraint error with grouper database migration between identical grouper version
  • Date: Tue, 8 Oct 2019 14:13:29 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=isc.upenn.edu; dmarc=pass action=none header.from=isc.upenn.edu; dkim=pass header.d=isc.upenn.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NJWN78iBwr/pkThUqU/Ys1swJxaO/POSnyK8Bq2ncxw=; b=bO3UYjdWQG78oNpjyBvkuLZnXS+KlOGm5XzhSHlE+0Ke+brww5P0WgceNIjUQq/6zdi3JD91tZgcHcXc7QU+sG1mZamiwqesMN8k1Mg/0cLz4C2rSPAv2mMUyTc/g+Zlp4IRSge1FNFh3RN8LcKiFTxtLWT8EwLP14B5wkkvypzqFaAgwyZgsBJzPsAUX7nnDfGmhzb9f+/Xnx8dtzJKbawy8+ft34OXXTiDYt9H9iG81nZ4K6HCTlpm4Lgxl4IJblns7paACrumPkztXRh5JhScpG65/GVLwjeEvBj+SakTP0a+faikotLm2YQov1hVTMI7k3kYbDNjwmMGpZSNZA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=HwxuKoosRkQ4OGiqUlxEeotpl+h8dT0eaxxVzXsOmlHu9YAVB1riUjBaB7bsEl4Qm5tlUdU2I3gA2lM+MO0M5LPCz8LzWLgAnbJK3PEIxJV5LjxFRAHQ03UB2IhN+mjAPyoOvZI8hhqYdnBaMZ7Wpr+qdQg2sp+ssXttVg0icquNih4RWn1d1roN0Y0XStQd2LxjqrbYykL93QlQTKEJf73BQmOMvs3RoG+6ZwU34gV5tlnpJ3DH6f4tUwcbq+vAiVHBt68R67tn6lARMw5svxf8b1Ap95HWGWWywZ4Jme6/8NamkzYgtTgCyOdOWcDW9WwPWiCDXAbEi9xOyVzAuQ==

It should work I think... you import without foreign keys enabled, then
enable them. if one doesn’t enable, look at which one it is, and see in
table why it wont enable, see if that foreign key was enabled in the previous
database, and report back why the data is messed up 😊

-----Original Message-----
From:
<> On Behalf Of Satya Mohapatra
Sent: Tuesday, October 08, 2019 10:00 AM
To: grouper-users <>
Subject: [grouper-users] foreign key constraint error with grouper database
migration between identical grouper version

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 | ସତ୍ୟ ମହାପାତ୍ର | सत्य महापात्र | ستیا موہپترا





Archive powered by MHonArc 2.6.19.

Top of Page