Datastage slow performance
Moderators: chulett, rschirm, roy
Datastage slow performance
Hi Team,
From that last 2 days all the Datastage jobs are running slow in our server.
Even extraction from sequential files seems to be slow.
We have around 60 GB Free space in the Drive where DS is installed. All Hashfiles and output files are kept in separate Drive which has around 200 GB Free space.
We are trying to clear the job logs using Director. Is there any way to clear all logs ?
What all other steps we should perform to make the jobs run faster
Regards
Sree
From that last 2 days all the Datastage jobs are running slow in our server.
Even extraction from sequential files seems to be slow.
We have around 60 GB Free space in the Drive where DS is installed. All Hashfiles and output files are kept in separate Drive which has around 200 GB Free space.
We are trying to clear the job logs using Director. Is there any way to clear all logs ?
What all other steps we should perform to make the jobs run faster
Regards
Sree
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
-
- Premium Member
- Posts: 376
- Joined: Sat Jan 07, 2012 12:25 pm
- Location: Piscataway
Also have a peek into the &PH& directory to ensure that the number of files isn't too much. You decide how much is too much.
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
Data Integration Consultant at AWS
Connect With Me On LinkedIn
Life is really simple, but we insist on making it complicated.
No. And it's CLEAR.FILE as in all CAPS as was posted.
Also wanted to emphasis the previous answer: NO. What makes you think they are the problem? Are they 'large' and if so, do you not have auto-purge enabled for your job logs? This also assumes that you have your logging going to the Universe repository rather than XMETA, any idea what your LOGGING settings are?sreesuku2 wrote:Can I delete the RT_Log files from the project directory ?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Of course. What you read was than in older versions Auto Purge settings / changes would only be automatically applied to new jobs. You can always enable it one by one for any job you desire. Newer versions will propagate Auto Purge settings to all jobs, something easy enough to test to see for yourself. What version are you running?sreesuku2 wrote:Is it possible to do Auto-purge for existing jobs ?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Right - it will start purging them the next time it runs, assuming the job does not fail. Oh, and by 'let us know' I meant check a job via the Director to see what the current Auto Purge settings are that it has, no need to run the job just to check that.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers