Because MSTR in the design of the entity, the field name is not the same two tables can not be associated (very rigid), so modified the table Tbl_fact_skill_rg96868_hour in the called Field name Called_no->calleeno, About 9 O ' 20. Modify the column name operation.
Due to negligence, forgetting to modify the insert Operation column name of Prc_skill_rg_96868_hour in the new stored procedure of the previous day has not been modified, causing the stored procedure compilation to fail, because the process is also called by the process sp_icd_h_job every half hour at a higher level. Further resulting in this process also failed to compile, but did not do the verification at the time, 9 30 o'clock, the dispatch job began to execute the stored procedure, because the stored procedure compilation failed, resulting in the process is not executed successfully, so 8 to 9 point data is not generated. About 10 o ' Day, there appeared a large area of the scene of the network, until 11 points 10 or so, the report users began to report error message: MSTR Report Web page cannot be opened. So it is urgent to restart the MSTR server (this is another problem, in the morning of the Dragon Boat Festival also appeared this problem, and currently do not know what the reason).
MSTR Server Restart Good, MSTR of the Web can log in normally, and after a while, using personnel to report information that today's reports can only find 0 to 7 points of data, 8 to 10 points of data is not displayed. So I went from the report to fetch a number of the fact table began to follow, found that the new stored procedure was caused by yesterday, and this morning the modified table field name is related to this stored procedure, I immediately modified the corresponding field name in the stored procedure, recompile the stored procedure, compile successfully, and then immediately start to perform data updates, Starting from 8 o'clock, consistent execution to 11 points, the execution of the process just met half an hour of automatic dispatch job, formed a conflict, resulting in 11 points-12 points of automatic job, although the execution is successful, but the loss of data generation, I guess it was because I was manually executing a stored procedure that conflicts with a stored procedure that is automatically executed by the dispatch job.
Review the stored procedure execution log, wait for the dispatch job to complete, and then manually perform the process to refresh data from 11 to 12 points, this time the data is successfully generated.
"Work notes" a report with a modified table field name operation results in missing 2 hours of data