jmdiazlr

Excuse me, all is working fine now after ignoring the outgoing batches... maybe this was some bad configuration while implementing the transform. Thanks

I'll appreciate any help... I created a column transform on extract, to send the column only if it changed (transform_type = 'copyIfChanged' and transform_expression = 'IgnoreColumn'). So this column is being ignored if not changed on the extract side. I reviewed the stage area and I saw the batch correctly omitting the column when data is not changed. The outgoing batch error_flag = 1, with sqlmesage saing there was a not null constraint violation. In the receiving side (loading side) the incoming_batch...

Well, I can use #param_name#, but that produce the parameter value not the displayed text in the LOV. Thanks

I tried Saiku with my mondrian cube and it shows some rows only but there are more and it does not show paging controls. I am running art3.8 Thanks.

I think not, but would like to confirm. I tried transform_table.source_schema_name = $(sourceNodeGroupId) but it did not get my transform. Then I set it to a constant value and worked well. Thanks

Let me rephrase my question, I have then following sync network: Server Client A Client B Communication between nodes is only through symmetricds (no direct connection between nodes) How can Client A know the last heartbeat time of Client B or if is it offline ? Maybe a Monitor running at server over the heartbeat time of every client node, manual says table MONITOR_EVENT syncs on heartbeat channel, but does it syncs to client nodes ? Thanks for any comment.

Let me rephrase my question, I have then following sync network: Server Client A Client B Communication between nodes is only through symmetricds (no direct connection between nodes) How can Client A know the last heartbeat time of Client B or if is it offline ? Maybe a Monitor running at server over the heartbeat time of every client node, manual says table MONITOR_EVENT syncs on heartbeat channel, but does it syncs to client nodes ? Thanks for any comment.

Let me rephrase my question, I have then following sync network: Server Client A Client B Communication between nodes is only through symmetricds (no direct connection between nodes) How can Client A know the last heartbeat time of Client B or if is it offline ? Maybe a Monitor running at server over the heartbeat time of every client node, manual says table MONITOR_EVENT syncs on heartbeat channel, but does it syncs to client nodes ? Thanks for any comment.