Hi Christian, Christian Keller wrote: > > here come's XCDMOUT.LOG and DATABASE.log > > -------------------------------------------------------------- > > Set environment variable 'DBROOT' to '/sapdb/P10/db' > > > Subprocess starts at 20030724224132 > > Execute Command : dbmcli -n sap -d P10 -u CONTROL,CONTROL db_start > > > Subprocess stops at 20030724224133 > > ERR > -24994,ERR_RTE: runtime environment error > 1,Kernel died before reaching COLD state > > -------------------------------------------------------------- > > Set environment variable 'DBROOT' to '/sapdb/P10/db' > > > Subprocess starts at 20030724224706 > > Execute Command : dbmcli -n sap -d P10 -u CONTROL,CONTROL db_state > > > Subprocess stops at 20030724224706 > > OK > State > STOPPED INCORRECTLY > > -------------------------------------------------------------- > > Set environment variable 'DBROOT' to '/sapdb/P10/db' > > > Subprocess starts at 20030724224706 > > Execute Command : dbmcli -n sap -d P10 -u CONTROL,CONTROL db_clear > > > Subprocess stops at 20030724224707 > > OK > > -------------------------------------------------------------- > > Set environment variable 'DBROOT' to '/sapdb/P10/db' > > > Subprocess starts at 20030724224707 > > Execute Command : dbmcli -n sap -d P10 -u CONTROL,CONTROL db_start > > > Subprocess stops at 20030724224708 > > ERR > -24994,ERR_RTE: runtime environment error > 1,Kernel died before reaching COLD state > > -------------------------------------------------------------- > > Set environment variable 'DBROOT' to '/sapdb/P10/db' > > > Subprocess starts at 20030724231649 > > Execute Command : dbmcli -n sap -d P10 -u CONTROL,CONTROL db_state > > > Subprocess stops at 20030724231649 > > Error! Connection failed to node sap for database P10: connection > refused: x_server not running
The installation seems to work fine until the R3Setup is starting up the database instance with db_start. I assume that you found the problem that the RUNDIRECTORY at /sapdb/data/wrk/P10 was not accessable for writing for the group sapsys and the database owner sqd<sid>. After analysing and changeing this you forgot to restore the required state of the database to continue the R3Setup and let the x_server (vserver) stopped. That's the reason for the followup error messages "x_server not running" because this is needed for the remote connection to send commands to the DBMSRV. The same can be seen in the Database.log... > DATABASE.log > ------------ [...] > INFO 2003-07-25 09:41:47 > Starting VSERVER > > INFO 2003-07-25 09:41:47 > Initialize the Database > > INFO 2003-07-25 09:41:47 > Extracting Database Parameter Files > > INFO 2003-07-25 09:41:47 > Setting the User Specific Database Parameters > > INFO 2003-07-25 09:41:47 > Setting the Computed Database Parameters > > INFO 2003-07-25 09:41:47 > Performing Service BCHECK > > INFO 2003-07-25 09:41:47 > Starting SAP DB to Mode COLD > > ERROR 2003-07-25 09:41:48 ADADBGETCOLDFIRST_IND_ADA > InternalInstallationDo:0 > iaxasdbmodus: Error: > > ERROR 2003-07-25 09:41:48 ADADBGETCOLDFIRST_IND_ADA InstallationDo:0 > Phase failed. > > ERROR 2003-07-25 09:41:48 InstController Action:0 > Step ADADBGETCOLDFIRST_IND_ADA could not be performed. > > ERROR 2003-07-25 09:41:48 Main :0 > Installation failed. > > ERROR 2003-07-25 09:41:48 Main :0 > Installation aborted. Thus, please start up the x_server with "x_server start" and restart the R3Setup to continue the installation process. Ciao Ralf _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
