Skip main navigation (Press Enter).
Log in
Toggle navigation
Home
Communities
My Communities
All Communities
Events
Browse
Discussion Posts
Library Entries
Log in
PureEngage On-Premises
×
Community Home
Discussion
5.9K
Library
92
Blogs
1
Events
0
Members
1.8K
View Only
Sign Up
Back to discussions
Expand all
|
Collapse all
sort by most recent
sort by thread
Job PURGE didn't run
Riccardo Paoli
06-28-2017 09:14
In customer environment we've activated run-maintain flag on GIM application. However in GIM logs we ...
Jakub Němec
06-28-2017 11:53
Seems like incorrect configuration - check the setup.
Jason McLennan
07-04-2017 03:24
Have you ensured your schedule\maintain-start-time is set sufficiently after schedule\etl-end-time ...
1.
Job PURGE didn't run
Like
Riccardo Paoli
Partner
Posted 06-28-2017 09:14
Reply
Reply Privately
Options Dropdown
In customer environment we've activated run-maintain flag on GIM application.
However in GIM logs we find this statement:
Purge doesn't run because last ETL has not being completed successfully.
What are the root cause of this warning?
Thank a lot
2.
RE: Job PURGE didn't run
Like
Jakub Němec
Partner
Posted 06-28-2017 11:53
Reply
Reply Privately
Options Dropdown
Seems like incorrect configuration - check the setup.
3.
RE: Job PURGE didn't run
Like
Jason McLennan
100 Posts
Posted 07-04-2017 03:24
Reply
Reply Privately
Options Dropdown
Have you ensured your
schedule\maintain-start-time is set sufficiently after
schedule\etl-end-time (and well before etl-start-time) to ensure all etl jobs have completed?
In our envirnment we use this setup, but you may need to consult with your dbas if its appropriate for yourself:
etl-start-time = 06:00
etl-start-time = 01:00
maintain-start-time = 02:00
×
New Best Answer
This thread already has a best answer. Would you like to mark this message as the new best answer?
Copyright© 2025 Genesys
. All rights reserved.
Terms of Use
|
Privacy Policy
Copyright 2026. All rights reserved.
Powered by Higher Logic