Resetting Auto-Purge for existing jobs
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 298
- Joined: Tue Aug 26, 2008 12:17 pm
Resetting Auto-Purge for existing jobs
Hi everybody!!!!
4 years earlier I wrote this topic...
I am now working for a company where they use Datastage version 11.5 and they are complaining about job logs cause it takes so much time to load them each time Director is opened. It's been impossible to use Director with such slow performance.
A configuration that keeps only 7 days of log only works for new jobs, right?
Cause here they set to keep 30 days and got regreted after some months.
How could we keep only 7 days for all jobs?
Thanks in advance!
Best regards,
Joyce
4 years earlier I wrote this topic...
I am now working for a company where they use Datastage version 11.5 and they are complaining about job logs cause it takes so much time to load them each time Director is opened. It's been impossible to use Director with such slow performance.
A configuration that keeps only 7 days of log only works for new jobs, right?
Cause here they set to keep 30 days and got regreted after some months.
How could we keep only 7 days for all jobs?
Thanks in advance!
Best regards,
Joyce
Joyce A. Recacho
São Paulo/SP
Brazil
São Paulo/SP
Brazil
Re: Resetting Auto-Purge for existing jobs
I'm not sure that's still the case, I seem to recall that behavior changing in later versions. Someone with actual experience with doing a change like that would need to chime in, however.joycerecacho wrote:A configuration that keeps only 7 days of log only works for new jobs, right?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
in the short run, you may get relief by selecting "Show Folders" on the VIEW drop-down menu.
If you are familiar with the folder structure of your project(s), and you don't NEED to see all jobs simultaneously, this may be usable for a time.
Added:
I see that I have misunderstood the question, but I will leave this here in the off-chance it will help some lost soul.
john3
If you are familiar with the folder structure of your project(s), and you don't NEED to see all jobs simultaneously, this may be usable for a time.
Added:
I see that I have misunderstood the question, but I will leave this here in the off-chance it will help some lost soul.
john3
john3
----------------------------------------------------
InfoSphere 8.5.0.2; DataStage 8.5.0.0; OS-RHEL 6.6; DB-Oracle Enterprise Edition 11g (11.2.0.4)
----------------------------------------------------
InfoSphere 8.5.0.2; DataStage 8.5.0.0; OS-RHEL 6.6; DB-Oracle Enterprise Edition 11g (11.2.0.4)
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Okay, once again we are treating the symptom, not the disease. Can someone answer the question as to how changing auto purge at the project level affects existing jobs? We know the change will take effect on any new jobs but what about existing jobs?
I seem to recall people here saying that in some flavor of later versions, any current job that hadn't specifically / individually had its purge setting overridden would immediately take on the new project level setting. Yes no maybe so? If true, do you know with what release that was introduced?
I seem to recall people here saying that in some flavor of later versions, any current job that hadn't specifically / individually had its purge setting overridden would immediately take on the new project level setting. Yes no maybe so? If true, do you know with what release that was introduced?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 298
- Joined: Tue Aug 26, 2008 12:17 pm
-
- Participant
- Posts: 298
- Joined: Tue Aug 26, 2008 12:17 pm
Ray,ray.wurlod wrote:Disable refresh in Director, or set it to a very long interval. ...
Thank you. It can help a little bit however is just a workaround.
Actually I have difficulty even to open the Director, imagine!
It takes about 3 minutes just to open it.
I am reading the log through Designer, pontually to that job.
Thank you in advance!
Joyce A. Recacho
São Paulo/SP
Brazil
São Paulo/SP
Brazil
Open a smaller project and enable folder view.
Switch back to the project you desired.
==============
Have your admin open Admin tool and set project level autopurge to the quantity of days you wish.
Upon the NEXT EXECUTION of the job, your logs will be purged.
You could also "Validate" a job and that would constitute an execution as well.
You could execute a RESET on the job (from the dsjob command line) and that would update the log as well.
Scripting a loop for each job and hitting reset would do that big purge you want. (highly believe this would be what you want)
Granted that this might be a PROD environment, you would have to get the application team signoff to halt the flow, touch each job, then allow them to resume their flow.
Switch back to the project you desired.
==============
Have your admin open Admin tool and set project level autopurge to the quantity of days you wish.
Upon the NEXT EXECUTION of the job, your logs will be purged.
You could also "Validate" a job and that would constitute an execution as well.
You could execute a RESET on the job (from the dsjob command line) and that would update the log as well.
Scripting a loop for each job and hitting reset would do that big purge you want. (highly believe this would be what you want)
Granted that this might be a PROD environment, you would have to get the application team signoff to halt the flow, touch each job, then allow them to resume their flow.
-
- Participant
- Posts: 298
- Joined: Tue Aug 26, 2008 12:17 pm