TNS Protocol adapter error while starting Oracle SQL*Plus
Solution 1
Try
sqlplus sys/<your password>@<your SID> as sysdba
Solution 2
Ensure the OracleService is running. I keep running into this error, but when I go into Services, find OracleServiceXE and manually start it, the problem is resolved. I have it set to start automatically, but sometimes it just seems to stop on its own; at least, I can't find anything I am doing to stop it.
Solution 3
Try typing all of this on the command line:
sqlplus / as sysdba
As what you are doing is starting sqlplus and then using sys as sysdba
as the user-name which is incorrect as that is not a valid user. By using the above command Oracle is using your system login credentials to access the db.
Also, I would confirm that the sqlplus executable you are running is the correct one by checking your path - ensure it is in the bin of the server installation directories.
Solution 4
Use this command, in command prompt
sqlplus userName/password@host/serviceName
Solution 5
You are getting ORA-12560: TNS:protocol adaptor error becuase you didn't start the Oracle database.
You can start Oracle database like this. From START-> select Oracle Database 11g Express Edition( 11g or what ever your database type.you can find this from All Programs). Then inside this folder there is a DB icon with green color spot. It is the Start Service icon.Click it.Then it will take some seconds and start the service.
After getting the above message,again try to connect through the SQL plus command line by giving user name and password.
Brian
Updated on May 17, 2020Comments
-
Brian about 4 years
Whenever I try to login into SQL*Plus (11g Standar Edition Win 64) I get an error related to some connection error.
I try to login as sys as sysdba and provide the password.
All the services are started. I'm on Windows 7.
Any help would be appreciated.
-
John Doyle over 12 yearsDo you get the same error if you use
tnsping <instance name>
? What do you see if you uselsnrctl status
? (Ignore my initial suggestion that usingsys as sysdba
is incorrect, it is acceptable, your error is something else.)