After Upgrade 2.2.5 to 2.3.0 Getting Error:CMS_BLOCK_STORE_BLOCK_ID_CMS_BLOCK_BLOCK_ID' to system tables,












1














After Upgrade 2.2.5 To 2.3.0 when i am runnung php bin/magento setup:upgrade it give bellow error:



Schema creation/updates:




SQLSTATE[HY000]: General error: 1823 Failed to add the foreign key constraint 'test@test@002dtestnew/CMS_BLOCK_STORE_BLOCK_ID_CMS_BLOCK_BLOCK_ID' to system tables, query was: ALTER TABLE cms_block_store MODIFY COLUMN block_id smallint(6) NOT NULL , ADD CONSTRAINT CMS_BLOCK_STORE_BLOCK_ID_CMS_BLOCK_BLOCK_ID FOREIGN KEY (block_id) REFERENCES cms_block (block_id) ON DELETE CASCADE, ADD CONSTRAINT CMS_BLOCK_STORE_STORE_ID_STORE_STORE_ID FOREIGN KEY (store_id) REFERENCES store (store_id) ON DELETE CASCADE











share|improve this question





























    1














    After Upgrade 2.2.5 To 2.3.0 when i am runnung php bin/magento setup:upgrade it give bellow error:



    Schema creation/updates:




    SQLSTATE[HY000]: General error: 1823 Failed to add the foreign key constraint 'test@test@002dtestnew/CMS_BLOCK_STORE_BLOCK_ID_CMS_BLOCK_BLOCK_ID' to system tables, query was: ALTER TABLE cms_block_store MODIFY COLUMN block_id smallint(6) NOT NULL , ADD CONSTRAINT CMS_BLOCK_STORE_BLOCK_ID_CMS_BLOCK_BLOCK_ID FOREIGN KEY (block_id) REFERENCES cms_block (block_id) ON DELETE CASCADE, ADD CONSTRAINT CMS_BLOCK_STORE_STORE_ID_STORE_STORE_ID FOREIGN KEY (store_id) REFERENCES store (store_id) ON DELETE CASCADE











    share|improve this question



























      1












      1








      1







      After Upgrade 2.2.5 To 2.3.0 when i am runnung php bin/magento setup:upgrade it give bellow error:



      Schema creation/updates:




      SQLSTATE[HY000]: General error: 1823 Failed to add the foreign key constraint 'test@test@002dtestnew/CMS_BLOCK_STORE_BLOCK_ID_CMS_BLOCK_BLOCK_ID' to system tables, query was: ALTER TABLE cms_block_store MODIFY COLUMN block_id smallint(6) NOT NULL , ADD CONSTRAINT CMS_BLOCK_STORE_BLOCK_ID_CMS_BLOCK_BLOCK_ID FOREIGN KEY (block_id) REFERENCES cms_block (block_id) ON DELETE CASCADE, ADD CONSTRAINT CMS_BLOCK_STORE_STORE_ID_STORE_STORE_ID FOREIGN KEY (store_id) REFERENCES store (store_id) ON DELETE CASCADE











      share|improve this question















      After Upgrade 2.2.5 To 2.3.0 when i am runnung php bin/magento setup:upgrade it give bellow error:



      Schema creation/updates:




      SQLSTATE[HY000]: General error: 1823 Failed to add the foreign key constraint 'test@test@002dtestnew/CMS_BLOCK_STORE_BLOCK_ID_CMS_BLOCK_BLOCK_ID' to system tables, query was: ALTER TABLE cms_block_store MODIFY COLUMN block_id smallint(6) NOT NULL , ADD CONSTRAINT CMS_BLOCK_STORE_BLOCK_ID_CMS_BLOCK_BLOCK_ID FOREIGN KEY (block_id) REFERENCES cms_block (block_id) ON DELETE CASCADE, ADD CONSTRAINT CMS_BLOCK_STORE_STORE_ID_STORE_STORE_ID FOREIGN KEY (store_id) REFERENCES store (store_id) ON DELETE CASCADE








      magento2.3.0






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited yesterday









      Manashvi Birla

      6,09441840




      6,09441840










      asked yesterday









      Navin Bhudiya

      736824




      736824






















          1 Answer
          1






          active

          oldest

          votes


















          2














          An error was due to Duplicate tables in a database, BK_cms_block.
          i was copied table and rename it for backup purpose and that creating issue , so i just delete BK tables and error resolve






          share|improve this answer





















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "479"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f256764%2fafter-upgrade-2-2-5-to-2-3-0-getting-errorcms-block-store-block-id-cms-block-bl%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            2














            An error was due to Duplicate tables in a database, BK_cms_block.
            i was copied table and rename it for backup purpose and that creating issue , so i just delete BK tables and error resolve






            share|improve this answer


























              2














              An error was due to Duplicate tables in a database, BK_cms_block.
              i was copied table and rename it for backup purpose and that creating issue , so i just delete BK tables and error resolve






              share|improve this answer
























                2












                2








                2






                An error was due to Duplicate tables in a database, BK_cms_block.
                i was copied table and rename it for backup purpose and that creating issue , so i just delete BK tables and error resolve






                share|improve this answer












                An error was due to Duplicate tables in a database, BK_cms_block.
                i was copied table and rename it for backup purpose and that creating issue , so i just delete BK tables and error resolve







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered yesterday









                Navin Bhudiya

                736824




                736824






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Magento Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.





                    Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                    Please pay close attention to the following guidance:


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f256764%2fafter-upgrade-2-2-5-to-2-3-0-getting-errorcms-block-store-block-id-cms-block-bl%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    An IMO inspired problem

                    Management

                    Investment