This content has been marked as final. Show 5 replies
Hm, 12514 or 12154?
ORA-12154: TNS:could not resolve the connectThis means that your tnsnames.ora (or other naming method) is missing the called for entry/stanza.
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Jun 6 23:02:34 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
ORA-12154: TNS:could not resolve the connect identifier specified
but then sqlplus prompts me once again for user nameIn the username field you could input for example user@service
and pass (it does not prompt for service name) and
after entering those two connection is established as
If this is the only oracle product installed on the machine, and you are connecting to it locally, you could use just
which uses the "default" instance (on Windows, that is).
lsnrctl serviceslsnrctl serv is on the server side, it does not matter what you have in tnsnames.ora
I have no idea why the XE service is unavailable
while it is properly configured in my tnsnames.ora
Normally the database should register itself to the listener, so the XE instance should have a service for it listed.
If you restart the instance's Windows service, does it show up in the listener?
Message was edited by:
From one side, your oracle instance has not yet been registered. It probably means it has not been started yet or it is facing difficulties in getting registered against the listener.
Make sure you have started the instance (not only the service) and open a sqlprompt from the os command line and force registration:
sqlplus / as sysdba
SQL> ALTER SYSTEM REGISTER;
Once done with this, check XE has already been registered against your listener.
On the other hand, the 12514 error means XE is not recognizes as a valid alias. Verify your PATH environment variable and make sure you are executing the sqlplus at the Oracle XE home.