View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001669 | SymmetricDS | Bug | public | 2014-04-16 04:46 | 2019-04-26 15:23 |
Reporter | spiceman | Assigned To | elong | ||
Priority | normal | ||||
Status | closed | Resolution | duplicate | ||
Product Version | 3.5.19 | ||||
Target Version | 3.6.3 | Fixed in Version | 3.6.3 | ||
Summary | 0001669: Oracle triggers fail to compile when using custom sync.table.prefix | ||||
Description | When setting a custom table prefix, oracle triggers fail to compile. 2014-04-16 13:29:24,863 ERROR [node-000] [AbstractSymmetricEngine] [symmetric-startup] An error occurred while starting SymmetricDS org.jumpmind.db.sql.SqlException: ORA-04098: trigger 'DBNAME.FOO_ON_U_FOR_SY_ND_CLNT' is invalid and failed re-validation I configured the node with the foo prefix, and generated triggers try to use sym_pkg (instead of foo_pkg). Looks like a trivial fix of some hardcoded "sym_" :). | ||||
Steps To Reproduce | 1) configure node with sync.table.prefix=foo 2) $ ../bin/symadmin --engine node-XXX create-sym-tables 3) configure nodes, triggers, channels, etc 4) $ ../bin/sym --engine node-XXX | ||||
Additional Information | The generated triggers all have sym_pkg: decode(:old."TRIGGER_ID", null, to_clob('')||'', '"'||replace(replace(to_clob('')||:old."TRIGGER_ID",'\','\\'),'"','\"')||'"'), var_row_data, var_old_data, 'config', foo_transaction_id(), sym_pkg.disable_node_id, null, CURRENT_TIMESTAMP ); | ||||
Tags | trigger | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2014-04-16 04:46 | spiceman | New Issue | |
2019-04-22 17:34 | elong | Tag Attached: trigger | |
2019-04-26 15:23 | elong | Relationship added | duplicate of 0001843 |
2019-04-26 15:23 | elong | Assigned To | => elong |
2019-04-26 15:23 | elong | Status | new => closed |
2019-04-26 15:23 | elong | Resolution | open => duplicate |
2019-04-26 15:23 | elong | Fixed in Version | => 3.6.3 |