Some errors we used to see because of performance of DB logging -
1. DS Director becomes slower and slower.
2. When I tried to log in I got the following message:
ACCESS DENIED: Project currently locked. The project is currently locked by the Administrator. Try again later or see your administrator.3. We would see the director just freeze up as we try to open the logs.
4. You could not rerun a job for a very long time after it was done.
5. Job is not in a runnable state. This we learnt was because the logs were still being written long after job completed and the server thought the job is still active.
Cause:
DS logs are kept in xmeta (DB2)
Solution:
Solution:
Move logs from xmeta to UV
Step:
1. In DSParams file, change RTLogging=1, ORLogging=0
Step:
1. In DSParams file, change RTLogging=1, ORLogging=0
2. Restart the DataStage
3. Note that all logs in DS Director will be disappeared because of storage changed. (DB2 > UV)
4. Recommend to set auto purge log in DS Administrator
Further reading
http://datastagetips.blogspot.com/2010/04/rtlogging-and-orlogging.html
https://www-304.ibm.com/support/docview.wss?uid=swg21370048
Further reading
http://datastagetips.blogspot.com/2010/04/rtlogging-and-orlogging.html
https://www-304.ibm.com/support/docview.wss?uid=swg21370048
No comments:
Post a Comment