No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


Some Queried Reports doesn’t display_Set_corect_DBTZONE_iWeb version SPC310

Publication Date:  2015-10-07 Views:  111 Downloads:  0
Issue Description

Assuming that you have installed the new iWeb Report system and installed and configured the correct new template, It is time to check whether it is possible to query some reports from the system or not. Checking this point will let you face some errors. The cases KB1000085582, KB1000085459 and KB1000085755 can help deal with these errors but, even without error no report might display because of some key information badly set into the iweb report database. The key rule for this case is to check the database settings and make them feat with the zone where the system is used.

Alarm Information

After user login, when querying reports [agent reports, trunk reports, VDN reports, IVR reports and Skill reports], some of them are empty that means no data displays in the report.

Etc ..

Handling Process


 ·         Check the datastation status, stop the datastation and restart

·         Check configuration tables


·         Check daylog tables for online agent daily reports

·         Check the time zone in the system

The current system is running in Cameroun (GMT+01H), you should make sure the time zone in the system feat with the time zone in the current zone.

select sysdate, t.* from t_dbtimezone t

As you see above, the DBTZONE is +08:00; the dbtzone should be + 01:00 not +08:00.



Root Cause

If the steps described in the Handling process are OK, that means the dbtzone set in the database is not the correct one, it should feat with the current UTC Zone. The steps in the next session help to solve this.


Change the dbtzone in the sysdate table to current time zone:

-       Connect to the database as icd user and Update dbtzone to +01:00

update t_dbtimezone
set dbtzone = +01:00 
where sysdate =2015/08/25 02:43:16 PM;


-       then relogin agent and make a call


Recheck the report display again, it might be OK.