What happens is that the backend attempts to start in response to the startup command you supplied in SQL*Plus. That fails -- logging an error in alert.log -- and SQL*Plus loses its connection with the backend, so you receive the end-of-file on communication channel error.
SQL> startup pfile='C:\more_ctlfiles.ora'
ORACLE instance started.
If you are simply looking to start and stop it, and a service or systemctl module doesn't exist on your machine, you can use pg_ctl to start and stop the Postgres server. You will also need to have the path to the data directory handy (typically, the folder that contains postgresql.conf and pg_hba.conf), and pass that in along with the -D flag:
pg_ctl -D /...
systemctl | grep postgres
... and you'll be able to see what the service is actually called.
phil@ironforge:~/M$ systemctl | grep postgr
postgresql.service loaded active exited PostgreSQL RDBMS
email@example.com loaded active ...
That means that there is no file named
in your systemd directory.
The exact location varies between Linux distributions, but it is usually /usr/lib/systemd/system or /lib/systemd/system.
As stated in the comment, please check your privilege. This change you are trying to make will write startup parameters to the registry and need privilege beyond member of sysadmin role in SQL Server.
Ref: SCM Services - Configure Server Startup Options
Limitations and Restrictions
SQL Server Configuration Manager writes startup parameters to the
I ran into the same problem. The database did not start with the service. First I checked the setting for the service using the Oracle Administration Assistant for Windows and configured the DB to start with the service start (by the way, I prefer the database to shut down immediately when the service is shut down).
But enabling the database to open at ...