When I am compiling any of my server job it throws an error " Error Calling RTLog<numbers>". Some times it says "check data stage is set up correctly"
Why is this occurring. Is rebuilding job index is the solution. I have searched forum but did not get solution.
Error in Compling Server jobs
Moderators: chulett, rschirm, roy
Error in Compling Server jobs
Thanks, BK
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Please post the exact message.
Check also that your project directory's file system is not full, and that you have write permission to it.
Re-indexing is unlikely to help, as the log tables are not indexed.
Check also that your project directory's file system is not full, and that you have write permission to it.
Re-indexing is unlikely to help, as the log tables are not indexed.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Yes, I think my file system is full its almost 96% used. So what files I to delete from my project directory to bring it down.ray.wurlod wrote:Please post the exact message.
Check also that your project directory's file system is not full, and that you have write permission to it.
Re-indexing is unlikely to help, as the log tables are ...
Thanks, BK
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Anything in &PH& directory would be a good start. Clear the &PH& directory in all projects. Any file in &SAVEDLISTS& directory that has a name beginning with "&&S." is also not required.
Are there any temporary files (or temporary hashed files) that have been created in the project directory? If you are planning delete hashed files, beware that there's a right way and a wrong way - and using the operating system to delete hashed files from a project is the wrong way.
Allocate some time to checking your job logs. These really do need to be kept as small as possible, commensurate with your retention policy. If a job log is huge, look at it in Director, observe that there are millions of warnings, and purge old entries. If you want to reclaim some of the job log disk space, you will need to RESIZE job log tables.
A useful set of commands for gathering log file sizes are these:
These will, together, gather sizing information about all your log tables into a table called STAT.FILE. You can query this in various ways to identify the "hogs", for example or even the pre-stored query
Are there any temporary files (or temporary hashed files) that have been created in the project directory? If you are planning delete hashed files, beware that there's a right way and a wrong way - and using the operating system to delete hashed files from a project is the wrong way.
Allocate some time to checking your job logs. These really do need to be kept as small as possible, commensurate with your retention policy. If a job log is huge, look at it in Director, observe that there are millions of warnings, and purge old entries. If you want to reclaim some of the job log disk space, you will need to RESIZE job log tables.
A useful set of commands for gathering log file sizes are these:
Code: Select all
SELECT VOC WITH TYPE = "F" AND @ID LIKE "RT_LOG..."
ACCOUNT.FILE.STATS ALL LOCAL
Code: Select all
SELECT * FROM STAT.FILE;
Code: Select all
LIST.FILE.STATS LOCAL
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.