Forum chevron_right Corda 4 chevron_right Corda Community 4.9 version with Postgres SQL

  • Creator
    Topic
  • #9757
    QA Bot
    Keymaster

    The node is not starting with Corda community 4.9 + Postgres SQL.
    I could see the connection is getting established but the issue is coming during schema migration. Below is the error I am getting. any lead/help on this will be appreciated.
    its been 20+ days I am struggling.

    [INFO ] 2022-11-15T19:39:47,405Z [main] visitor.ValidatingVisitor. - Skipping change set migration/node-core.changelog-pkey.xml::non-clustered_pk-1::R3.Corda due to validation error(s): clustered is not allowed on postgresql {changeSet=migration/node-core.changelog-pkey.xml::non-clustered_pk-1::R3.Corda, databaseChangeLog=master.changelog.json}
    [INFO ] 2022-11-15T19:39:47,406Z [main] visitor.ValidatingVisitor. - Skipping change set migration/node-core.changelog-pkey.xml::non-clustered_pk-2::R3.Corda due to validation error(s): clustered is not allowed on postgresql {changeSet=migration/node-core.changelog-pkey.xml::non-clustered_pk-2::R3.Corda, databaseChangeLog=master.changelog.json}
    [INFO ] 2022-11-15T19:39:47,424Z [main] visitor.ValidatingVisitor. - Skipping change set migration/node-core.changelog-pkey.xml::non-clustered_pk-3::R3.Corda due to validation error(s): clustered is not allowed on postgresql {changeSet=migration/node-core.changelog-pkey.xml::non-clustered_pk-3::R3.Corda, databaseChangeLog=master.changelog.json}
    [INFO ] 2022-11-15T19:39:47,428Z [main] visitor.ValidatingVisitor. - Skipping change set migration/node-core.changelog-pkey.xml::non-clustered_pk-4::R3.Corda due to validation error(s): clustered is not allowed on postgresql {changeSet=migration/node-core.changelog-pkey.xml::non-clustered_pk-4::R3.Corda, databaseChangeLog=master.changelog.json}
    [INFO ] 2022-11-15T19:39:47,429Z [main] visitor.ValidatingVisitor. - Skipping change set migration/node-core.changelog-pkey.xml::non-clustered_pk-5::R3.Corda due to validation error(s): clustered is not allowed on postgresql {changeSet=migration/node-core.changelog-pkey.xml::non-clustered_pk-5::R3.Corda, databaseChangeLog=master.changelog.json}
    [INFO ] 2022-11-15T19:39:47,432Z [main] visitor.ValidatingVisitor. - Skipping change set migration/node-core.changelog-pkey.xml::non-clustered_pk-6::R3.Corda due to validation error(s): clustered is not allowed on postgresql {changeSet=migration/node-core.changelog-pkey.xml::non-clustered_pk-6::R3.Corda, databaseChangeLog=master.changelog.json}
    [INFO ] 2022-11-15T19:39:47,438Z [main] visitor.ValidatingVisitor. - Skipping change set migration/node-core.changelog-pkey.xml::non-clustered_pk-7::R3.Corda due to validation error(s): clustered is not allowed on postgresql {changeSet=migration/node-core.changelog-pkey.xml::non-clustered_pk-7::R3.Corda, databaseChangeLog=master.changelog.json}
    [INFO ] 2022-11-15T19:39:47,515Z [main] visitor.ValidatingVisitor. - Skipping change set migration/node-core.changelog-v21.xml::node_transaction_id_size_non-clustered_pk::R3.Corda due to validation error(s): clustered is not allowed on postgresql {changeSet=migration/node-core.changelog-v21.xml::node_transaction_id_size_non-clustered_pk::R3.Corda, databaseChangeLog=master.changelog.json}
    [ERROR] 2022-11-15T19:39:47,594Z [main] internal.NodeStartupLogging. - Incompatible database schema version detected, please run schema migration scripts (node with sub-command run-migration-scripts). Reason: There are 111 outstanding database changes that need to be run.
  • You must be logged in to reply to this topic.

Subscribe to our newsletter to stay up to date on the latest developer news, tools, and articles.