I Upgraded our land scape from ECC6.0 to ECC6.0 EHP5. also we upgraded our oracle database from 10g to 11g.
Now the problem is our Zprograms Are getting timed out.
these programs has to be run in foreground. before upgrade it was working fine,after upgarde we are facing this issue...
please suggest some solution..
There are many reasons to face with this performance problem. For example, number of fetched records might be increased.
One another reason might be the missing indexes on the table. Check DB02. Secondly, you can check the execution plan belong to the executed select statements in order to identify the optimizer is selecting correct path. Thirdly, check the optimizier statistics are updated on DB13.
In order to find out the bottleneck, you need to analyze the issue by using the tools that I noted in my previous messages. On the other hand, there's no indication that the ECC 6.0 cause a performance problem on the customer developed program.
Performance problem, can be caused by a BAPI called in the program or an index use or some other point. You should give more information such as execution plan and SM30 output.
In order for us to help you, you would work a little before.
The information you provide is useless.
Lets think a litlte about what you provide and what we would need to help
OK, you upgraded SAP and Oracle.
Your Z programs are not finishing.
As they are not SAP standard, it is probable that the SAP upgrade (from ECC6.0 to ECC6.0 EHP5) has not influence on them (this is an assumption)
So it is possible that the oracle upgrade (to which EXACT version, patch set and SBP?) is the one to blame.
but this does not help.
Lets keep thinking.
Something was fast before and slow now. What?
The Z program(s), but this program has a LOTS of calls (ABAP and Oracle) so we do not know what is slow. YOU have to find out what is slow.
Tracing. You have two options
1) ST05 => do only a SQL trace
2) ST12 => ABAP+SQL trace together.
After this is done, then YOU have to find out what are the statements that take LONG time and analyze them (is it long time per execution/per record, what is the explain plan, why is "bad" or "good", how could it be before, are my parameters OK ...?
After YOU analyze it, then it is possible to try to get a solution, you can ask for help.
I do not see any of this. Someone ask you for the ST05 trace (Orkun) and you reply that you did it.
PERFECT, AND? have look at it, a trace is to be analyzed, if yo do it and you do not analyze it then the problem will not be solved alone.
Finally you ask
Here i need to know one thing is that why these programs which are worked in ECC6.0 and now why they are giving timed out error.
As I mentioned, you changed the oracle version. the CBO optimizer is different and you have new statistics. It is possible that it thinks now that a different path is better but it is wrong
it may be a bug or new functionality or a change of behaviour or simply new statistics (or a feature)
Note: I'm assuming that the issue is on the oracle side