Hi,
We're using a EP7.0 (NW2004s) portal under Windows 2003 Server with an Oracle 10.2. And I'm wondering if the script used until now couldn't be improved. Currently there is a batch stopping the portal the following way :
D:\usr\sap\<SID>\SYS\exe\uc\NTI386\stopsap.exe name=<SID> nr=<SNUMBER FOR SCS> SAPDIAHOST=<HOSTNAME>
D:\usr\sap\<SID>\SYS\exe\uc\NTI386\stopsap.exe name=<SID> nr=<SNUMBER FOR JC> SAPDIAHOST=<HOSTNAME>
net stop SAP<SID>_<SNUMBER FOR SCS>
net stop SAP<SID>_<SNUMBER FOR JC>
net stop Oracle<SID>102TNSListener
net stop OracleService<SID>
net stop SAPOsCol
Is it enough or too much ??
In the past, from what I understand, we used to put a "shutdown immediate" in an sql file and execute it. But now it seems a net stop OracleService is enough and as clean. Can anybody confirm this ?
For the SAP instances, can't I do directly
net stop SAP<SID>_<SNUMBER FOR SCS>
net stop SAP<SID>_<SNUMBER FOR JC>
and forget the two stopsap lines ?
For the start of the SAP :
net start OracleService<SID>
net start Oracle<SID>102TNSListener
net start SAP<SID>_<SNUMBER FOR JC>
net start SAP<SID>_<SNUMBER FOR SCS>
D:\usr\sap\<SID>\SYS\exe\uc\NTI386\startsap.exe name=<SID> nr=<SNUMBER FOR SCS> SAPDIAHOST=<HOSTNAME>
D:\usr\sap\<SID>\SYS\exe\uc\NTI386\startsap.exe name=<SID> nr=<SNUMBER FOR JC> SAPDIAHOST=<HOSTNAME>
help.sap.com seems to have documentation for windows NT ; perhaps this has changed with all the services and Oracle 10 ?
TIA,
Denis.