" /> REP_REBUILD_LOG table in datamart - Genesys CTI User Forum
« previous next »
Pages: [1]   Go Down

Author Topic: REP_REBUILD_LOG table in datamart  (Read 3029 times)

Offline JTL

  • Full Member
  • ***
  • Posts: 123
  • Karma: 2
REP_REBUILD_LOG table in datamart
« on: November 28, 2006, 04:45:15 PM »
Advertisement
Anyone any experiences with this?

We noticed an alarming slow-down with data aggregation in a large environment, and this table was being scanned... and was HUGE.

Why isn't this table "house-kept" by ETL, and does anyone automate the process?
« Last Edit: November 28, 2006, 04:50:55 PM by timetex »
Logged

Offline victor

  • Administrator
  • Hero Member
  • *****
  • Posts: 1419
  • Karma: 18
Re: REP_REBUILD_LOG table in datamart
« Reply #1 on: November 29, 2006, 10:42:05 AM »
We are running it on Oracle and there is not problem with it.

What is wrong with the table being big? It is indexed, so it should not affect your overall performance that much.

Have your looked at the execution plan to see where exactly you get a perfomance hit?

Vic


Logged

Offline Fra

  • Hero Member
  • *****
  • Posts: 856
  • Karma: -3
Re: REP_REBUILD_LOG table in datamart
« Reply #2 on: November 29, 2006, 01:01:31 PM »
In the REP_REBUILD_LOG the dates of the most recently aggregated statistics are recorded so that ETL can know the starting point of the next aggregation. If you delete the latest records, ETL will start re-aggregating.
Pretty strange you have some performances problem; anyway i remember that Genesys Support suggested to create a second index on pre-7 releases.
Logged
Pages: [1]   Go Up
« previous next »