An interesting Challenge - Breakpoint gets PRIV

[chutney374]

Hi All,

I've looking at a rather bizzare problem.

I have a 3 tier landscape running oracle 8.1.7.3 and SAP 4.6c. It's old (hence an interesting challenge).

In DEV and PRD when I want to set a session breakpoint point in any abap code for debugging, it's instant and STAD shows that it's taking up about 3 meg to set the breakpoint.

If I do the same on QAS, the process goes into PRIV mode whilst issuing a shortdump stating that storage_parameters_wrong_set and advise to change the dia, and nondia parameters. It takes up 5 GB of memory, blows extended and heap memory (hence PRIV) and simply won't allow me to do anything.

Interestingly though, the parameters are set to exactly the same values as the PRD and DEV system.

Any clues? I've tried SE80, utilities, ABAP Editor but this hasn't made a difference and there is nothing else running on the system, in fact I'm currently, THE only user on the system.

So a little challenge and a blast from the past for anyone willing to step up.

Regards

Paul M

[blueteeth]

Interesting. I wanted to give a long story on Zen Buddhism but stopped lest someone gets ballistic and starts shooting watermelon seeds in my general direction!

Anyway, back to basics. What is your OS?

Have you correlated all parameters that govern memory parameters? Especially Roll and Heap areas?

Is SAP Kernel across the systems of same version?

Since you are on Oracle, is Oracle Optimizer (Update statistics) being run? Have you run Delete Harmful statistics?

Regards,
BT

[chutney374]

Windows 2000 (I know it's old, and it's being addressed)

All Memory Parameters are the same across DEV and QAS.

Kernels are at the same patch level.

I shall check the status of the stats.

Seems odd though, considering all I'm doing is adding 1 breakpoint.

Regards

Paul