The 'StatisticsFailedSQLs.log' file is a text file that captures the Structured Query Language (SQL) statements that are issued against the statistics database. This file is only generated in case of a failure where the Statistics Manager component within Strategy Intelligence Server fails to write to the statistics database.
The file should be used for recovery purposes only. The SQL statements recorded in the file are simple INSERT or UPDATE statements and can be executed with any native database connectivity tool or using the ODBC Test/DB Query tool against the statistics database(s). The statements are database specific, whose forms are derived from the database type defined for the corresponding statistics database instance.
The following is an excerpt from a sample 'StatisticsFailedSQLs.log' file:
insert into IS_SESSION_STATS values ('17E2AAD0473C7824B7C859A66F8450E1', '916851674CD915368CB7719E8A4ECE22', 'J_Doe3', 'J_Doe3', '-1', '54F3D26011D2896560009A8E67019608', 'J_Doe3', 3, {ts'2003-01-17 13:08:03'}, 1, 'SignIn to Server',GETDATE());
insert into IS_REPORT_STATS values (48, '17E2AAD0473C7824B7C859A66F8450E1', '916851674CD915368CB7719E8A4ECE22', 'J_Doe3', 'J_Doe3', 'EA6086B5416447B326CD099F0E847926', '54F3D26011D2896560009A8E67019608', 'AF76BE6511D424EEC000D8906B98494F', '4943056811D473A7C00009B3D86C964F', 1, '4943056711D473A7C00009B3D86C964F', 1, -1, '0CE5EAC647A3283B295E9CB5038A75D4', 'sa', 0, {ts'2003-01-17 13:09:26'}, 1202, 1202, 8873, 5, 3, 0, 0, 0, 0, 0, 0, 0, 0, 1, 999, 0, 7,GETDATE()); NOTE: If there are multiple projects that are logging to different database instances and if more than one project fail to log their statistics, the failed SQL statements for all projects will be appended to the same 'StatisticsFailedSQLs.log' file. Users should, therefore, be careful about the statistics database(s) against which they are issuing the failed SQL statements.
The 'StatisticsFailedSQLs.log' file is generated under the '...\IntelligenceServer\' directory of the Strategy installation. The file is generated and appended from the first time the Statistics Manager fails to insert into the statistics table(s).
If the Statistics Manager fails to initialize, or equivalently the statistics configuration is not set up properly at the time of start-up for at least one of the projects, users will realize another entry in the 'StatisticsFailedSQLs.log' file as follows:
insert into MSI_STATS_LOG values ('', 1, , 1) This indicates that the component failed to initialize, and none of the consecutive statistics SQL will be recorded in the log file for the projects with the incorrect configurations. The regular statistics logging will continue for the projects with the correct configurations.
NOTE: 'StatisticsFailedSQLs.log' does not record the statistics SQL statements in case the statistics configuration after the start-up is incorrect for any of the projects. Examples of incorrect statistics configuration include non-existent statistics tables at the target database, failure to login to the statistics database, etc.
NOTE: Multiple StatisticsFailedSQLs.log files may be generated with a numeric suffix, e.g., StatisticsFailedSQLs0.log, StatisticsFailedSQLs1.log etc., when the latest log file grows too large. These files are limited to 4MB apiece to avoid degrading Intelligence Server performance. When this limit is reached, a new file is created taking the next integer.
