Simple Oracle troubleshooting

Two days ago, when I returned to Beijing, I encountered a problem at work: the company has an Oracle project in Shenzhen, and the Oracle database cannot be connected after a system restart. The project developer asked me for help. I want to read some Oracle books some time ago. Just try it. After remotely connecting to the server of the other party, use sqlplus to access the database. It is found that the database can be mounted but cannot be open. So I checked the alert_xxxx.log file in the bdump directory and found that the prompt was: the memory could not be allocated on the mongo_pool. Then, I checked the size of the cmd_pool in show parameter and found it to be around 87 MB. So I asked the project staff about the memory size of the other server. The answer was 16*2 GB. Why is the shared pool so small with such a large memory? It is possible to expand the size of the Shared Pool to solve the problem. I changed the size of the Shared Pool, shut down the database, and then opened it. I found everything was okay.

In fact, this problem is very simple. Although I do not have much practical experience in Oracle, it can also be easily solved. The developer of that project has already developed two or three Oracle-related projects, and cannot solve these problems. This is so disappointing to me. If developers do not have the spirit of continuous learning, it is a huge loss for themselves and their companies, and they will gradually lose the pleasure and idea of engaging in development.