Hello Experts,
The LIST_TOO_MANY_LPROS is a kind of dump which fall when there are 50 packs of transactions are being held. It is the call screen where the dump is seen no matter how many of the users are there still one of the user will see it. The call screen is that in which a new user entries are stacked together. While the to navigate between the screen a user can use Set Screen. The call screen displays on the current screen of the session and after leaving the user goes back to calling dynpro.
The issues which are been seen are where control not founded, ORA 00060 –DEADLOCKS, ORA-01089 –IMMEDIATE SHUTDOWN.
The session can be more than 2GB or 4GB it will be a time time to increase the capacity of the system. In control not found the user has to start again as there is nothing can be done for this dumped type of text. ORA 00060 –DEADLOCKS is occurs when another session has the same resources, the only thing to do is to wait for a while and try again. ORA-01089 –IMMEDIATE SHUTDOWN this could be frustrating as the DBM command of shutdown has worked on its own, the required thing is to wait for the system to get restarted.