1. Is it correct that EXEC_START_UTC_TS is identical for all the consecutive EXECUTE statements ?
Rao – Nope. Every execute should have its own start time... we need to change the current way of prepare time to execute time.
Run following steps from trafci
>PREPARE testord FROM select * from mgbtest.ord where ORDERID = ?;
>EXECUTE testord USING 1; //pQuery_info->m_exec_start_utc_ts =212292649111812177
>EXECUTE testord USING 2; //pQuery_info->m_exec_start_utc_ts =212292649111812177
2. For multiple EXECUTE statements per PREPARE ,shall we insert only one row or multiple rows? What is the design for this?
Rao – If aggregation is enabled then whatever executes completed within the aggregation time are accumulated and written to repository as one record.
Discussion about how to fix the issue:
1. Is it correct that EXEC_START_UTC_TS is identical for all the consecutive EXECUTE statements ?
Rao – Nope. Every execute should have its own start time... we need to change the current way of prepare time to execute time.
Run following steps from trafci
>PREPARE testord FROM select * from mgbtest.ord where ORDERID = ?;
>EXECUTE testord USING 1; //pQuery_ info->m_ exec_start_ utc_ts =212292649111812177
>EXECUTE testord USING 2; //pQuery_ info->m_ exec_start_ utc_ts =212292649111812177
2. For multiple EXECUTE statements per PREPARE ,shall we insert only one row or multiple rows? What is the design for this?
Rao – If aggregation is enabled then whatever executes completed within the aggregation time are accumulated and written to repository as one record.