SAP for Healthcare Discussions
Foster discussions about patient care, cost reduction, and operational excellence in healthcare organizations using SAP. Join the conversation.
cancel
Showing results for 
Search instead for 
Did you mean: 

performance problem with NWP1

Former Member
0 Kudos
459

Hello everybody,

we have IS-H 463B with patch level 26. We have big problems with the performance at calling the Clinical Work Station (NWP1) with the medical views. We analyzed with transaction ST05 and SE30 and we concluded that the view

N_VBEWFAL takes a very long time. We asked SAP but they answered that from a technical point of view the the program runs in the best possible way.

My question is if anyone knows a way to solve this problem?

Thanks in advance,

Alexander

1 ACCEPTED SOLUTION

Former Member
0 Kudos
293

Hi Alexander!

If you are using Oracle 9i/10g try to put the following parameter in the spfile/pfile:

OMPTIMPEEK_USER_BINDS=FALSE

Restart the server and try again. Hope this helps you!

Best Regards,

Roger Allué i Vall

View solution in original post

5 REPLIES 5

Former Member
0 Kudos
294

Hi Alexander!

If you are using Oracle 9i/10g try to put the following parameter in the spfile/pfile:

OMPTIMPEEK_USER_BINDS=FALSE

Restart the server and try again. Hope this helps you!

Best Regards,

Roger Allué i Vall

0 Kudos
293

upgrading to a more actual release or at least the latest (and last) patch level for 4.63B doesn't seem unreasonable to me as well

0 Kudos
293

trying to find out what that directive does I came to believe that it is

OPTIMPEEK_USER_BINDS=FALSE

rather than

OMPTIMPEEK_USER_BINDS=FALSE

my 2 cents, anton

0 Kudos
293

Yes,

OPTIMPEEK_USER_BINDS=FALSE

sorry for the spelling.

Roger Allué i Vall

Former Member
0 Kudos
293

Hi Alexander,

We just had a similar problem (with another table) and it was cause by the introduction of new functionality which started to fill a foreignkeyfield (indexed) which was empty before.

The solution which worked for us was to generate the tablestatistics again (use calculate and not estimate!). The problem occurred for an ORACLE database. (Under Maxdb everthing there were no problems).

Kind regards,

Martin