Issues while starting sap using mmc console the strdbs.cmd appears to be red.

You may check the S:\usr\sap\TP3\DVEBMGS00\work and look for the sapstart.log which will indicate if there's any issues with sapmmc related startup activity.

Below going through the below error log hints also check the r3trans -xd for and return code 12 or also try to start the database manually to see if there's any error as well.

SAP-R/3-Startup Program

Starting at 2013/06/27 10:25:13
Startup Profile: "S:\usr\sap\TP3\SYS\profile\START_DVEBMGS00_SUBTAA"
Starting Programs
(1640) Execute: S:\usr\sap\TP3\SYS\exe\nuc\NTAMD64\sapcpe.EXE pf=S:\usr\sap\TP3\SYS\profile\TP3_DVEBMGS00_SUBTAA
(4804) CreateProcess(S:\usr\sap\TP3\SYS\exe\nuc\NTAMD64\strdbs.cmd TP3) failed(2). ENOENT*: No such file or directory OR: The system cannot find the file specified. 
(4900) CreateProcess: S:\usr\sap\TP3\DVEBMGS00\exe\msg_server.EXE pf=S:\usr\sap\TP3\SYS\profile\TP3_DVEBMGS00_SUBTAA
(4452) CreateProcess: S:\usr\sap\TP3\DVEBMGS00\exe\disp+work.EXE pf=S:\usr\sap\TP3\SYS\profile\TP3_DVEBMGS00_SUBTAA
(5088) CreateProcess: S:\usr\sap\TP3\DVEBMGS00\exe\igswd.EXE -mode=profile pf=S:\usr\sap\TP3\SYS\profile\TP3_DVEBMGS00_SUBTAA
(4804) Parent Shutdown at 2013/06/27 10:25:54
(4804) kill(SIGINT 0) failed.
Send Signal SIGKILL to Process 0

strdbs.cmd is a function to start database ( below can be found in START_DVEBMGS00_SUBTAA)

SAPSYSTEMNAME = TP3
SAPGLOBALHOST = SUBTAA
SAPSYSTEM = 00
INSTANCE_NAME = DVEBMGS00
DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64
DIR_EXECUTABLE = $(DIR_INSTANCE)\exe
DIR_PROFILE = $(DIR_INSTALL)\profile
_PF = $(DIR_PROFILE)\TP3_DVEBMGS00_SUBTAA
#-----------------------------------------------------------------------
# Copy SAP Executables
#-----------------------------------------------------------------------
Start_Program_00 = immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF)
#-----------------------------------------------------------------------
# Start ABAP database
#-----------------------------------------------------------------------
_DB = $(DIR_CT_RUN)\strdbs.cmd
Start_Program_01 = immediate $(_DB) TP3
#-----------------------------------------------------------------------
# Start SAP message server
#-----------------------------------------------------------------------
_MS = $(DIR_EXECUTABLE)\msg_server$(FT_EXE)
Start_Program_02 = local $(_MS) pf=$(_PF)
#-----------------------------------------------------------------------
# Start application server
#-----------------------------------------------------------------------
_DW = $(DIR_EXECUTABLE)\disp+work$(FT_EXE)
Start_Program_03 = local $(_DW) pf=$(_PF)
#-----------------------------------------------------------------------
# Start internet graphics server
#-----------------------------------------------------------------------
_IG = $(DIR_EXECUTABLE)\igswd$(FT_EXE)
Start_Program_04 = local $(_IG) -mode=profile pf=$(_PF)


Default Profile DEFAULT.PFL which indicates OS_UNICODE = uc

SAPDBHOST = SUBTAA
j2ee/dbtype = ora
j2ee/dbname = TP3
j2ee/dbhost = SUBTAA
SAPSYSTEMNAME = TP3
SAPGLOBALHOST = SUBTAA
rdisp/bufrefmode = sendoff,exeauto
#-----------------------------------------------------------------------
# SAP Message Server for ABAP
#-----------------------------------------------------------------------
rdisp/mshost = SUBTAA
rdisp/msserv = sapmsTP3
rdisp/msserv_internal = 3900
#-----------------------------------------------------------------------
# SAP Central Service Instance for J2EE
#-----------------------------------------------------------------------
j2ee/scs/host = SUBTAA
j2ee/scs/system = 01
j2ee/ms/port = 3901
#-----------------------------------------------------------------------
# SAP Message Server for ABAP
#-----------------------------------------------------------------------
#-----------------------------------------------------------------------
# SAP Central Service Instance for J2EE
#-----------------------------------------------------------------------
login/system_client = 001
OS_UNICODE = uc


The solution to this problem is to change the os_unicode from nuc to unicode or also alternatively copy the strdbs.cmd to the nuc/NTADM64 folder. Please try