View Issue Details

IDProjectCategoryView StatusLast Update
0002932SymmetricDSBugpublic2022-08-02 15:19
Reporterrpotam Assigned Toelong  
Prioritynormal 
Status closedResolutionunable to reproduce 
Product Version3.8.10 
Summary0002932: Db2 not finding sym or other tables from metadata
DescriptionWe are trying to replicate data between DB2 and Mysql by trying out the demo application.

when I keep the config (initial.load.create.first=false) in server.properties, I am getting the following error

[corp-000] - TriggerRouterService - Could not find any database tables matching 'item_selling_price' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_transform_table' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_parameter' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_file_trigger_router' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_table_reload_request' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_node_identity' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_grouplet_link' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_grouplet' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_file_snapshot' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_file_trigger' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_monitor_event' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_trigger_router' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_router' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'item' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_node_group_channel_wnd' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_notification' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_node' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_node_group' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_transform_column' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_load_filter' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_monitor' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_extension' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_node_security' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_trigger' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_node_group_link' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_channel' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_node_host' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_conflict' in the datasource that is configured
[corp-000] - TriggerRouterService - Could not find any database tables matching 'sym_trigger_router_grouplet' in the datasource that is configured


[store-001] - RegistrationService - Unexpected error during registration: Server returned HTTP response code: 500 for URL: http://localhost:31415/sync/corp-000/registration?nodeGroupId=store&externalId=001&syncURL=http%3A%2F%2Fde-mucpaasdb2in%3A31415%2Fsync%2Fstore-001&schemaVersion=%3F&databaseType=MySQL&databaseVersion=5.7&symmetricVersion=3.8.10&hostName=de-mucpaasdb2in&ipAddress=10.40.232.136
java.io.IOException: Server returned HTTP response code: 500 for URL: http://localhost:31415/sync/corp-000/registration?nodeGroupId=store&externalId=001&syncURL=http%3A%2F%2Fde-mucpaasdb2in%3A31415%2Fsync%2Fstore-001&schemaVersion=%3F&databaseType=MySQL&databaseVersion=5.7&symmetricVersion=3.8.10&hostName=de-mucpaasdb2in&ipAddress=10.40.232.136

when I keep the config (initial.load.create.first=true) in server.properties, I am getting the following error


[corp-000] - Db2v9SymmetricDialect - There are SymmetricDS tables that needed altered
[corp-000] - Db2v9SymmetricDialect - DDL failed: CREATE TABLE "SYM_CHANNEL"(
    "CHANNEL_ID" VARCHAR(128) NOT NULL,
    "PROCESSING_ORDER" INTEGER DEFAULT 1 NOT NULL,
    "MAX_BATCH_SIZE" INTEGER DEFAULT 1000 NOT NULL,
    "MAX_BATCH_TO_SEND" INTEGER DEFAULT 60 NOT NULL,
    "MAX_DATA_TO_ROUTE" INTEGER DEFAULT 100000 NOT NULL,
    "EXTRACT_PERIOD_MILLIS" INTEGER DEFAULT 0 NOT NULL,
    "ENABLED" SMALLINT DEFAULT 1 NOT NULL,
    "USE_OLD_DATA_TO_ROUTE" SMALLINT DEFAULT 1 NOT NULL,
    "USE_ROW_DATA_TO_ROUTE" SMALLINT DEFAULT 1 NOT NULL,
    "USE_PK_DATA_TO_ROUTE" SMALLINT DEFAULT 1 NOT NULL,
    "RELOAD_FLAG" SMALLINT DEFAULT 0 NOT NULL,
    "FILE_SYNC_FLAG" SMALLINT DEFAULT 0 NOT NULL,
    "CONTAINS_BIG_LOB" SMALLINT DEFAULT 0 NOT NULL,
    "BATCH_ALGORITHM" VARCHAR(50) DEFAULT 'default' NOT NULL,
    "DATA_LOADER_TYPE" VARCHAR(50) DEFAULT 'default' NOT NULL,
    "DESCRIPTION" VARCHAR(255),
    "QUEUE" VARCHAR(25) DEFAULT 'default' NOT NULL,
    "MAX_NETWORK_KBPS" DECIMAL(10,3) DEFAULT 0.000 NOT NULL,
    "CREATE_TIME" TIMESTAMP,
    "LAST_UPDATE_BY" VARCHAR(50),
    "LAST_UPDATE_TIME" TIMESTAMP,
    PRIMARY KEY ("CHANNEL_ID")
)
[corp-000] - JdbcSqlTemplate - DB2 SQL Error: SQLCODE=-601, SQLSTATE=42710, SQLERRMC=PAAS_CA.SYM_CHANNEL;TABLE, DRIVER=4.21.29. Failed to execute: CREATE TABLE "SYM_CHANNEL"(
    "CHANNEL_ID" VARCHAR(128) NOT NULL,
    "PROCESSING_ORDER" INTEGER DEFAULT 1 NOT NULL,
    "MAX_BATCH_SIZE" INTEGER DEFAULT 1000 NOT NULL,
    "MAX_BATCH_TO_SEND" INTEGER DEFAULT 60 NOT NULL,
    "MAX_DATA_TO_ROUTE" INTEGER DEFAULT 100000 NOT NULL,
    "EXTRACT_PERIOD_MILLIS" INTEGER DEFAULT 0 NOT NULL,
    "ENABLED" SMALLINT DEFAULT 1 NOT NULL,
    "USE_OLD_DATA_TO_ROUTE" SMALLINT DEFAULT 1 NOT NULL,
    "USE_ROW_DATA_TO_ROUTE" SMALLINT DEFAULT 1 NOT NULL,
    "USE_PK_DATA_TO_ROUTE" SMALLINT DEFAULT 1 NOT NULL,
    "RELOAD_FLAG" SMALLINT DEFAULT 0 NOT NULL,
    "FILE_SYNC_FLAG" SMALLINT DEFAULT 0 NOT NULL,
    "CONTAINS_BIG_LOB" SMALLINT DEFAULT 0 NOT NULL,
    "BATCH_ALGORITHM" VARCHAR(50) DEFAULT 'default' NOT NULL,
    "DATA_LOADER_TYPE" VARCHAR(50) DEFAULT 'default' NOT NULL,
    "DESCRIPTION" VARCHAR(255),
    "QUEUE" VARCHAR(25) DEFAULT 'default' NOT NULL,
    "MAX_NETWORK_KBPS" DECIMAL(10,3) DEFAULT 0.000 NOT NULL,
    "CREATE_TIME" TIMESTAMP,
    "LAST_UPDATE_BY" VARCHAR(50),
    "LAST_UPDATE_TIME" TIMESTAMP,
    PRIMARY KEY ("CHANNEL_ID")
)
[corp-000] - AbstractSymmetricEngine - An error occurred while starting SymmetricDS
org.jumpmind.db.sql.SqlException: DB2 SQL Error: SQLCODE=-601, SQLSTATE=42710, SQLERRMC=PAAS_CA.SYM_CHANNEL;TABLE, DRIVER=4.21.29
        at org.jumpmind.db.sql.AbstractSqlTemplate.translate(AbstractSqlTemplate.java:303)
        at org.jumpmind.db.sql.AbstractSqlTemplate.translate(AbstractSqlTemplate.java:294)
        at org.jumpmind.db.sql.JdbcSqlTemplate.execute(JdbcSqlTemplate.java:493)
        at org.jumpmind.db.sql.JdbcSqlTemplate.update(JdbcSqlTemplate.java:401)
        at org.jumpmind.db.sql.SqlScript.execute(SqlScript.java:107)
        at org.jumpmind.symmetric.db.AbstractSymmetricDialect.createOrAlterTablesIfNecessary(AbstractSymmetricDialect.java:474)
        at org.jumpmind.symmetric.db.db2.Db2SymmetricDialect.createOrAlterTablesIfNecessary(Db2SymmetricDialect.java:48)
        at org.jumpmind.symmetric.db.AbstractSymmetricDialect.initTablesAndDatabaseObjects(AbstractSymmetricDialect.java:155)
        at org.jumpmind.symmetric.AbstractSymmetricEngine.setupDatabase(AbstractSymmetricEngine.java:449)
        at org.jumpmind.symmetric.AbstractSymmetricEngine.setup(AbstractSymmetricEngine.java:423)
        at org.jumpmind.symmetric.AbstractSymmetricEngine.start(AbstractSymmetricEngine.java:580)
        at org.jumpmind.symmetric.AbstractSymmetricEngine.start(AbstractSymmetricEngine.java:571)
        at org.jumpmind.symmetric.ClientSymmetricEngine.start(ClientSymmetricEngine.java:244)
        at org.jumpmind.symmetric.web.SymmetricEngineHolder$EngineStarter.run(SymmetricEngineHolder.java:478)
Caused by: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-601, SQLSTATE=42710, SQLERRMC=PAAS_CA.SYM_CHANNEL;TABLE, DRIVER=4.21.29
        at com.ibm.db2.jcc.am.kd.a(kd.java:810)
        at com.ibm.db2.jcc.am.kd.a(kd.java:66)
        at com.ibm.db2.jcc.am.kd.a(kd.java:140)
        at com.ibm.db2.jcc.am.sp.c(sp.java:2796)
        at com.ibm.db2.jcc.am.sp.d(sp.java:2784)
        at com.ibm.db2.jcc.am.sp.b(sp.java:2146)
        at com.ibm.db2.jcc.t4.bb.j(bb.java:233)
        at com.ibm.db2.jcc.t4.bb.c(bb.java:48)
        at com.ibm.db2.jcc.t4.p.b(p.java:38)
        at com.ibm.db2.jcc.t4.vb.h(vb.java:124)
        at com.ibm.db2.jcc.am.sp.jb(sp.java:2141)
        at com.ibm.db2.jcc.am.sp.a(sp.java:3336)
        at com.ibm.db2.jcc.am.sp.e(sp.java:1111)
        at com.ibm.db2.jcc.am.sp.execute(sp.java:1090)
        at org.apache.commons.dbcp.DelegatingStatement.execute(DelegatingStatement.java:264)
        at org.apache.commons.dbcp.DelegatingStatement.execute(DelegatingStatement.java:264)
        at org.jumpmind.db.sql.JdbcSqlTemplate$6.execute(JdbcSqlTemplate.java:416)
        at org.jumpmind.db.sql.JdbcSqlTemplate$6.execute(JdbcSqlTemplate.java:401)
        at org.jumpmind.db.sql.JdbcSqlTemplate.execute(JdbcSqlTemplate.java:491)
        ... 11 more
[corp-000] - AbstractSymmetricEngine - Stopping SymmetricDS externalId=000 version=3.8.10 database=DB2/LINUXX8664
[corp-000] - AbstractSymmetricEngine - SymmetricDS: type=server, name=corp-000, version=3.8.10, groupId=corp, externalId=000, databaseName=DB2/LINUXX8664, databaseVersion=10.5, driverName=IBM Data Server Driver for JDBC and SQLJ, driverVersion=4.21.29




Tagsddl/schema, dialect: db2, install

Activities

chenson

2016-12-04 16:42

administrator   ~0000924

That looks to me as if tables have been created, but symmetricds can't see them via metadata so it thinks it needs to create them again. Can you log onto the DB2 database with the credentials that SymmetricDS is using and see the tables?

rpotam

2016-12-05 08:05

reporter   ~0000925

I could able to view tables that are created by SymmetryDS, i.e with the credentials that I supplied.

What I suspect is that SymmetryDS is looking for tables in small-case, where as DB2 stores all objects in Upper-case. But I am not sure I just suspect that. But I couldn't think SymmetryDS would have not taken care of case-sensitivity, when they are implementing this to multiple databases.

Issue History

Date Modified Username Field Change
2016-12-02 06:03 rpotam New Issue
2016-12-04 16:42 chenson Note Added: 0000924
2016-12-05 08:05 rpotam Note Added: 0000925
2019-04-24 14:18 elong Tag Attached: ddl/schema
2019-04-24 14:18 elong Tag Attached: dialect: db2
2019-04-24 14:18 elong Tag Attached: install
2019-05-13 20:23 elong Summary Db2 to Mysql Replication => Db2 not finding sym or other tables from metadata
2019-05-14 17:03 elong Category Improvement => Bug
2022-08-02 15:19 elong Assigned To => elong
2022-08-02 15:19 elong Status new => closed
2022-08-02 15:19 elong Resolution open => unable to reproduce