Hi Thomas, You should have a look to your db2diag.log file (it may be named slightly different, like db2diag.0.log for instance).
It should be located here : < instance owner home directory>/sqllib/db2dump Let's have a look to the files recently modified in this directory too. As instance owner, can you : - Start the instance using the "db2start" command ? - Connect to the database using the "db2 connect to tsmdb1" command ? Regards, Erwann ----- Mail original ----- De: "Thomas Denier" <thomas.den...@jeffersonhospital.org> À: ADSM-L@VM.MARIST.EDU Envoyé: Lundi 1 Octobre 2012 16:22:19 Objet: [ADSM-L] Version 6 startup after OS crash We have a zSeries Linux system with two TSM 6.2.2.0 server instances. One instance is a dedicated library manager with a small database. The other instance is used to store client data. The Linux system crashed yesterday. Once it was brought back up the library manager instance started without incident. The other instance was started after the library manager began to accept administrative client connections. The second instance is still not accepting administrative client connections some twelve hours later. Based on a discussion of crash recovery I found on the Web, I logged on as the instance user and executed the Linux command 'db2pd -recovery -db TSMDB1'. The response is 'Database is not in recovery state.' I have opened a severity 1 problem call with IBM. Thomas Denier Thomas Jefferson University Hospital
