DBD failing

Allan_Cochrane

Database designer fails with this in the log: 2013-08-29 16:54:26 Setting search path: SET search_path=valresdev; 2013-08-29 16:54:26 Executing: select a.* from "v_dbd_des1_des1".output_event_history_report as a, "v_dbd_des1_des1".current_event as b where a.time_stamp = b.time_stamp; 2013-08-29 16:54:29 Status: 0. Result: ['2013-08-29 16:53:44.682|Optimizing for query performance|1|7|7|6|5|Choosing best projections|||||'] 2013-08-29 16:54:34 Setting search path: SET search_path=valresdev; 2013-08-29 16:54:34 Executing: select count(*) from v_internal.vs_views where table_schema = 'v_dbd_des1_des1' and table_name = 'output_event_history_report'; 2013-08-29 16:54:34 Status: 0. Result: ['1'] 2013-08-29 16:54:36 Setting search path: SET search_path=valresdev; 2013-08-29 16:54:36 Executing: select a.* from "v_dbd_des1_des1".output_event_history_report as a, "v_dbd_des1_des1".current_event as b where a.time_stamp = b.time_stamp; 2013-08-29 16:54:36 Status: 0. Result: ['2013-08-29 16:54:34.78|Error during design||||||Design did not complete successfully. ERROR - A DDL statement interfered with DBDesigner|||||'] 2013-08-29 16:54:37 Ended execution of: select dbd_wait_for_design('des1','des1'); 2013-08-29 16:54:37 Status: 0. Result: ['0'] 2013-08-29 16:54:39 Setting search path: SET search_path=valresdev; 2013-08-29 16:54:40 Executing: select count(*) from v_internal.vs_views where table_schema = 'v_dbd_des1_des1' and table_name = 'output_event_history_report'; 2013-08-29 16:54:40 Status: 0. Result: ['1'] 2013-08-29 16:54:40 Setting search path: SET search_path=valresdev; 2013-08-29 16:54:40 Executing: select a.* from "v_dbd_des1_des1".output_event_history_report as a, "v_dbd_des1_des1".current_event as b where a.time_stamp = b.time_stamp; 2013-08-29 16:54:40 Status: 0. Result: ['2013-08-29 16:54:34.78|Error during design||||||Design did not complete successfully. ERROR - A DDL statement interfered with DBDesigner|||||'] 2013-08-29 16:54:41 Setting search path: SET search_path=valresdev; 2013-08-29 16:54:41 Executing: SELECT count(*) from "v_dbd_des1_des1".output_event_history_report where current_step_description = 'Design/Deployment cancelled'; 2013-08-29 16:54:41 Status: 0. Result: ['0'] 2013-08-29 16:54:41 Setting search path: SET search_path=valresdev; 2013-08-29 16:54:42 Executing: SELECT count(*) from "v_dbd_des1_des1".output_event_history_report where stage_type IN ('Error during deployment', 'Error during design'); 2013-08-29 16:54:43 Status: 0. Result: ['1'] 2013-08-29 16:54:43 Design errored . 2013-08-29 16:54:45 Setting search path: SET search_path=valresdev; 2013-08-29 16:54:45 Executing: SELECT max(current_step_description) from "v_dbd_des1_des1".output_event_history_report where stage_type IN ('Error during deployment', 'Error during design'); 2013-08-29 16:54:46 Status: 0. Result: ['Design did not complete successfully. ERROR - A DDL statement interfered with DBDesigner'] 2013-08-29 16:54:46 The error is: Design did not complete successfully. ERROR - A DDL statement interfered with DBDesigner 2013-08-29 16:54:46 Setting search path: SET search_path=valresdev; 2013-08-29 16:54:46 Executing: select dbd_remove_design('des1','des1'); 2013-08-29 16:54:49 Status: 0. Result: ['0'] 2013-08-29 16:54:49 Setting search path: SET search_path=valresdev; 2013-08-29 16:54:49 Executing: select dbd_drop_design('des1','des1'); 2013-08-29 16:54:50 Status: 0. Result: ['0'] 2013-08-29 16:54:50 Setting search path: SET search_path=valresdev; 2013-08-29 16:54:50 Executing: select dbd_drop_workspace('des1'); 2013-08-29 16:54:51 Status: 0. Result: ['0'] 2013-08-29 16:54:51 Database Designer finished. But what was the DDL that caused the problem?

Sharon_Cutter

When I hit this error, it was because I was running DBD from a node other than node0001. Running it from node0001 cleared it up. You might have a different root cause though.

Allan_Cochrane

How do I know which node I'm on, I cannot seem to find a way from the docs!

Daniel_Leybovic

Hi! Try next: select node_name from current_session;

Allan_Cochrane

Thanks, I was on node0001 so it seems to be a different cause.