Why is siebel so slow

You can unsubscribe at any time. Well, based on this comment, check the following: Goto your application specific config file siebel. No Account? Sign up. By signing in, you agree to our Terms of Use and Privacy Policy. Already have an account? Sign in. By signing up, you agree to our Terms of Use and Privacy Policy. Enter the email address associated with your account. And after that, when click the tabs, it takes about 5 seconds. Anything can be done to improve it? Then try to log in and check the application object manager log file in the enterprise logs directory for the SQL that is taking so much time or whatever it is that is taking so much time for that matter.

You may have to regenerate database statistics to rebuild the indexes. Anything to identify about the file name? Thank for your help, I found it, but I still have no idea about the problem. I really appreciate your big favor to me. When I was talking about looking at the application manager log files to see what SQL is running slow. If you just go the enterprises directory and do a directory listing it is obvious what these are.

Now each siebel server component that is active on your server will generate a log file with a name of the file that will contain the alias of the component name….. So your application object manager is the call center because you are running the call center siebel application so you everytime that you login to siebel, a new call center log file will be created in this directory which will hold all the information for that session.

I cant think what the alias of the call center is but if you login to the application and then do a directory listing on the log directrory above it should be one of the log files that was most recently created. So now the call center log files will start to generate a lot of information including the SQL that is being executed.

So you want to open the call center application object manager log file and then you can see each even listed with a time against it……so scan through the log file and you can see at what point it jumps in time at what point did it take a long time to do something and this is usually where you will find the bad SQL.

You will also see information about the time it took to execute the SQL etc. This is the start of tuning the application for performance. The first thing you will notice is that these log files get really really large and unless you plan on spending the whole day looking through them its not easy to figure out the slow sqls. Voila theres now a tool: I have run into this problem before and I eventually decided to write an app to do the heavy lifting for me.

Its written in C and has about 3k lines of code and best of all its free. Just start the app open the file you want to analyze and there you go it will give you a list of all the SQL execution times. Tech Community Register Log in. Siebel SQL Performance.