Why doesn't IBM Maximo start after a server reboot?

Question

ERP

For the needs of the development department, you need to deploy a server with IBM Maximo Assets Management 7.6. CentOS 7 was chosen as the OS, deployed a version for RHEL 7, IBM WebSphere was chosen as the web server. I installed updates, configured the OS according to the manuals, ran the script and installed it through the GUI, which started up, leaving the names that were by default. The installation went without problems, immediately after it the Maximo web interface works and can be accessed through a browser.
Problems start when you restart the OS. After starting the system, the server itself does not start. When you try to run the components one by one, according to this instruction - www-01.ibm.com/support/knowledgecenter/SSLKT6_7.6.... , the result is the following:
1. Deployment manager starts without problems.
2. Nodeagent starts without problems.
3. Webserver1 displays the following message - ADMU3011E: Server launched, but failed initialization.
4. MXServer sometimes starts without problems, sometimes it gives the same message as webserver1.
When trying to access the Maximo web interface, if the MXServer started normally, it throws the "Error 500 Java.Lang.Nullpointerexception" error. The WebSphere web interface is working fine.
Can you please tell me what could be causing this error?

Answer 1

From experience I will say that such a problem occurs when there is no websphere connection to the database.
If the database is on Oracle, then you need to check the connection settings in the tnsnames.ora and listener.ora files

Answer 2

Already figured out the problem, sorry for not updating, I thought the question had long since gone into the depths of history and is of no interest to anyone.
The problem was that the IBM DB2 database did not start, but it was aggravated by the fact that you cannot start it from under a normal user. To start and operate with DB2, it was necessary to log in from under the user created during installation (dasusr1 by default). Even when switching to root from a normal user, there was no access to the db2start command and others - it stupidly wrote command not found when entering. After sudo su - dasusr1 and switching from there to superuser mode, the command was normally Tab-ala and executed.
I didn’t dig deeper anymore, since the project died out and everything stopped on that test server, but this was enough to work with it.