Most common causes are lack of communication with the DATABASE or no memory available. Did you made changes recently to the instance profiles? If so, please review those changes.
To test for the 1st issue, login on the Application Server operating system with the <SIDADM> account and execute the command "R3trans -d". If return code is '0000', then the DB is running and communication is OK. Other error codes means that you have a problem.
For the 2nd, monitor the RAM usage during the startup. The fastest way to increase the memory is to add more swap.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.