Sql-server – Attempting to setup a new named instance but can’t get past the Feature Selection Screen

This means that the listener (the software that listens on the network for database connection attempts) doesn't know that your DB exists.

Normally, when you start up an Oracle 11g DB, it'll automatically "register" with the listener within 60 seconds or so (I believe it's background process PMON responsible for this). You can force a listener registration by connecting as sysdba on the local machine - e.g.:

SHELL> sqlplus / as sysdba

Then typing:

SQL> ALTER DATABASE REGISTER;

This will tell the database to register with the listener.

However - this relies on the database knowing how to talk to the listener! Because your listener is listening on port 1522, so you'll need to explicitly tell your database where to find it:

See http://docs.oracle.com/cd/E11882_01/network.112/e41945/listenercfg.htm#NETAG1154 ("Registering Information with a Local Listener")

For a real-world example, see:

http://edstevensdba.wordpress.com/2011/07/30/exploring-the-local_listener-parameter/

As to whether you should use DBCA or the query... it's up to you. DBCA is by far the simpler, however it also hides the details away. My preference is to use DBCA to generate a set of scripts which I then peruse and alter as appropriate.

You have installed a new instance of SQL Server, so you need to change the way you connect to that new instance.

Previously, you had a default instance, so connecting using any of these in the Server name: box would work fine:

localhost
.
127.0.0.1
<any_local_IP>
<your_machine_name>
<your_FQDN>

Now that you have installed a new instance of SQL Server, you need to reference that instance name as part of the connection string, so any of the above need to become the following:

localhost\MSSQLSERVER14
.\MSSQLSERVER14
127.0.0.1\MSSQLSERVER14
<any_local_IP>\MSSQLSERVER14
<your_machine_name>\MSSQLSERVER14
<your_FQDN>\MSSQLSERVER14