1.2.6 oracle lite connecting using SQL*PLUS

i have successfully installed a oracle 8iLite on win2000 professional.
user id --- system
password --- manager
host string ---- odbc:polite
But when i try to give this command
" set serveroutput on " i am getting a message "Server not available or version too low for this feature"
Can anybody help me to overcome this problem.
i am new to Oracle .
PLEASE EMAIL ME
THANK YOU
[email protected]

hi, I'd like to know if its
TNS 12560: protocol Adapter error
Make sure address uses the proper protocol specification in your connect descriptor.
if its that then U will have to verify that your database is registered with the Listener....
Also verify that your Oracle SID is set to the specific instance
You can do that by settin the environment variable;
c:\> set oracle_sid=<database_sid>
then try to connect after words.

Similar Messages

Cannot connect to database using SQL*Plus

Hi, I have Oracle 10g XE installed in my labtop and I cannot connect using SQL*Plus.
I can connect using the broser User Interface though, which I was able to do after doing the following procedure to change the password of the sys account:
-     open a command prompt
-     - type sqlplus
-     On the “Enter user-name” line, type /as sysdba
-     On the SQL> prompt, type alter user sys identified by NewPassword;
But the thing is that even though I am able to connect using sys/NewPassword from my browser UI, I dont get the same result when doing it using the SQL prompt.
What I am trying to do is this:
SQL> connect sys/NewPassword
Then I get first a warming saying that I need to use either sysdba or sysoper to connect to the system account, but neither of those work.
Can anyone advice me on this matter?
Thanks in advance

Thanks for that.
I run the command to list the usernames on the database and I got SYS and SYSTEM in the list. But again, when I try to use SYS with a password that I know is working because I can access it through the browser UI, it doesnt work. It seems like this sys is different to the sys I used in the UI.
I dont know if I am explaining myself correclty... In the Browser UI I use sys, and a password and I get connected to the sys account. However, if I try to use the same sys.password combination from my sqlplus prompt, I get error messages
Does this make sense at all?

Segmentation Fault when connecting to SQL*Plus from Applications tier

Hi Everyone -
I am currently in the process of upgrading a client from 11.5.10.2 to 12.1.1 (eventually 12.1.3) on a OEL x86-64 server. I have laid down the software stack and followed all of the requirements as per the Installation manuals and 761566.1. I also have an open SR right now on this issue - but I wanted to see if any of you have ever run into the issue that I am encountering.
When I try to run adadmin/adpatch - I get to the prompt of providing the system user password and the utility simply exits. No errors in adpatch.log or adadmin.log (both are 0 bytes in size).
When I try to connect using SQL*Plus from the applications tier using either:
sqlplus apps/****@SID
sqlplus system/****@SID
I get a Segmentation Fault error. There are also no errors in my alert log file on the database tier. I found this error while attempting to apply the upgrade merge patch.
Has anyone ever seen s Segmentation Fault error? I have search MOS, found a couple of potential solutions - but nothing has solved the issue so far.
Thanks in advance...
Brenna

>
Are you on 11.1.0.5.0? Is this the database version?
No, my database tier is 11.2.0.3 (the database version displayed above was the client version running on the Application Tier.
Who is the owner of the application tier files? If it is applmgr user, please make sure you login as that user and source the application env file before running sqlplus -- Please issue "echo $ORACLE_HOME" and "which sqlplus" and post the output here.
My owner of the application tier is oracle. I have sourced the environment using $APPL_TOP/APPSR12Dev1_******.env
[oracle@****** log]$ echo $ORACLE_HOME
/u01/app/oracle/R12Dev1/apps/tech_st/10.1.2
[oracle@****** log]$ which sqlplus
/u01/app/oracle/R12Dev1/apps/tech_st/10.1.2/bin/sqlplus
>
Please relink sqlplus by issuing "$ORACLE_HOME/bin/relink all > relink.txt 2>&1" and check the relink.txt file for any error
A number of errors occur during the relink, here are some of them:
/u01/app/oracle/R12Dev1/apps/tech_st/10.1.2/bin/genclntsh
/usr/bin/ld: warning: i386:x86-64 architecture of input file `/u01/app/oracle/R12Dev1/apps/tech_st/10.1.2/lib/libn10.a(nnfgt.o)' is incompatible with i386 output
/usr/bin/ld: warning: i386:x86-64 architecture of input file `/u01/app/oracle/R12Dev1/apps/tech_st/10.1.2/lib/libn10.a(ntcontab.o)' is incompatible with i386 output
/u01/app/oracle/R12Dev1/apps/tech_st/10.1.2/bin/genagtsh /u01/app/oracle/R12Dev1/apps/tech_st/10.1.2/lib/libagtsh.so 1.0
/usr/bin/ld: warning: i386:x86-64 architecture of input file `/u01/app/oracle/R12Dev1/apps/tech_st/10.1.2/lib/libn10.a(nnfgt.o)' is incompatible with i386 output
/usr/bin/ld: warning: i386:x86-64 architecture of input file `/u01/app/oracle/R12Dev1/apps/tech_st/10.1.2/lib/libn10.a(ntcontab.o)' is incompatible with i386 output
/u01/app/oracle/R12Dev1/apps/tech_st/10.1.2/lib/libn10.a(nnfgt.o):(.rodata+0xc8): undefined reference to `nnflboot'
/u01/app/oracle/R12Dev1/apps/tech_st/10.1.2/lib/libn10.a(ntcontab.o):(.data+0x8): undefined reference to `nttini'
/u01/app/oracle/R12Dev1/apps/tech_st/10.1.2/lib/libn10.a(ntcontab.o):(.data+0x28): undefined reference to `ntzini'
/u01/app/oracle/R12Dev1/apps/tech_st/10.1.2/lib/libn10.a(ntcontab.o):(.data+0x68): undefined reference to `ntpini'
/u01/app/oracle/R12Dev1/apps/tech_st/10.1.2/lib/libn10.a(ntcontab.o):(.data+0x88): undefined reference to `ntusini'
collect2: ld returned 1 exit status
Thanks again...

XE: Cant connect to sql*plus, APEX seems to function

Hi! I am a beginner in oracle.
I installed oracle XE 10g, both the server and the client on mandriva linux, using the supplied RPM's. After that I ran /etc/init.d/xe/configure and accepted the default values. Then I performed the post-installation steps as mentioned in APEX insstallation guide (sourcing the shell scripts).
In the APEX interface I can see the database, its staistics and I created a user. But when I try to connect using sql*plus, the connection is refused:
SQL> conn sys as sysdba
Enter password:
ERROR:
ORA-12545: Connect failed because target host or object does not exist
Judging from the output of commands below, there is something missing. Any ideas?
*> tnsping XE*
TNS Ping Utility for Linux: Version 10.2.0.1.0 - Production on 27-APR-2009 20:47:20
Copyright (c) 1997, 2005, Oracle. All rights reserved.
Message 3511 not found; No message file for product=network, facility=TNSTNS-03505: Message 3505 not found; No message file for product=network, facility=TNS
*> lsnrctl status*
LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 27-APR-2009 20:45:35
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Message 1053 not found; No message file for product=network, facility=TNSMessage 1020 not found; No message file for product=network, facility=TNSMessage 1021 not found; No message file for product=network, facility=TNSMessage 1022 not found; No message file for product=network, facility=TNSMessage 1023 not found; No message file for product=network, facility=TNSMessage 1026 not found; No message file for product=network, facility=TNSMessage 1034 not found; No message file for product=network, facility=TNSMessage 1024 not found; No message file for product=network, facility=TNSMessage 1025 not found; No message file for product=network, facility=TNSMessage 1040 not found; No message file for product=network, facility=TNSMessage 1422 not found; No message file for product=network, facility=TNSMessage 1033 not found; No message file for product=network, facility=TNSMessage 1028 not found; No message file for product=network, facility=TNSMessage 1415 not found; No message file for product=network, facility=TNS Message 1050 not found; No message file for product=network, facility=TNS
Message 1050 not found; No message file for product=network, facility=TNS
Message 1050 not found; No message file for product=network, facility=TNS
Message 1029 not found; No message file for product=network, facility=TNSMessage 1411 not found; No message file for product=network, facility=TNS
Message 1408 not found; No message file for product=network, facility=TNS
Message 1411 not found; No message file for product=network, facility=TNS
Message 1408 not found; No message file for product=network, facility=TNS
Message 1411 not found; No message file for product=network, facility=TNS
Message 1408 not found; No message file for product=network, facility=TNS
Message 1411 not found; No message file for product=network, facility=TNS
Message 1408 not found; No message file for product=network, facility=TNS
Message 1052 not found; No message file for product=network, facility=TNS

The messages tell me that you do not have the ORACLE_HOME variable set correctly. This has been discussed umpteen times, but since search is beyond the call of duty, I'll copy/paste one of my recent responses
In Linux and Unix Oracle REQUIRES that variables ORACLE_HOME and ORACLE_SID be set properly. And *nix REQUIRES that an executable be in the PATH or explicitly referenced. The easiest way of setting those consistently and correctly is to source the oraenv routine which is placed in /usr/local/bin by the installer. To use that, and assuming you are using Linux,
1) Find out the ORACLE_SID for your reference
tail /etc/oratab
and note the last line. The first field will be the SID.
2) Source oraenv
. oraenv
[ oracle ]?: enter the SID here
and if you want to put this into a script, enter something like
ORAENV_ASK=NO
ORACLE_SID={enter your SID ehere}
. oraenv
ORAENV_ASK=
Many people will suggest you set these variables in your profile. In the long term that is a bad idea (and DBAs should always be thinking in the long term) since most DBAs end up with a second database, ORACLE_HOME, upgrade or product and oraenv ensures that there will be no conflicts.

Can I use SQL *Plus 11.1.0.7.0 to connect Oracle Express 10g

Hi guys:
I download "Oracle 11g ODAC *11.1.0.7.20* with Oracle Developer Tools for Visual Studio", trying to use SQL *plus to see if configuration is alright.
But after entering account/pwd, I got a error:
ORA-12560: TNS:protocol adapter error
What is wrong with my environment?
Thanks,
Ricky

user12086319 wrote:
Hi EdStevens,
Following the instructions in previous post, I can connect with SQL plus (the database is on the same box* as your sqlplus client); I just enter sqlplus in windows console.
In addition, i am still curious about how SQL plus connect to a remote* box. Could you shed more light on that?SQLPlus connects to a remote db the same way any other app does. After all, sqlplus is just another client app.
It's all in the connect string. So say, at a command prompt you enter
$> sqlplus scott/tiger@mydbso in the above example, 'scott' is the user, 'tiger' is the password, and 'mydb' is the tns service name. Of course, the OS passes all that to sqlplus as a command line parameter. Internally, sqlplus makes a call to the tns layer and passes it the connect information it has. TNS will take a look at the tnsnames.ora file and find an entry for 'mydb', and from there it will get the name or ip address of the host server, a port number, and a service name. That information will be passed on down the network stack for routing. (If a name was provided instead of an ip address, the OS network stack will use whatever means are at its disposal - a hosts file, a dns lookup, or whatever, to get an ip address). The request will arrive at the specified host and placed on the specified port. If everything was configured correctly, there will be an oracle listener process monitoring that port. It will pick up the request and see if it recognizes the service name. If it does, it will spawn a user server process on a different port to complete the connection, then get out of the way and continue listening for more requests.
This is how it happens most of the time. There are a lot of other variants, but that's the gist of it.
More information can be found in the fine documentation at tahiti.oracle.com.

Connecting Oracle using SQL Plus in command window through LDAP settings?

Hi
Just like to know if it is possible to connect Oracle using SQL Plus with connection type as LDAP.
Generally we connect to Oracle in cmd window as
username/password@DBServiceName
Similarly is it possible to connect Oracle using SQL plus cmd window using LDAP configuration settings.
Eg:-
If my LDAP server is oid:123:456
Context is: cn=OracleContext,dc=abcdefgh,dc=com
DBService is: xyz
Regards
jc

Specify the -L command line option to SQL*Plus, i.e.:
sqlplus -L username/password@db @blah.sql
(this will prevent the second prompt for username/password if the initial login is unsuccessful for any reason, like an invalid password).

Connect via SQL*Plus taking more time in Oracle 11 than in 10

Oracle Version
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE 11.2.0.3.0 Production
TNS for IBM/AIX RISC System/6000: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Productioncurrently migrating from
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE 10.2.0.4.0 Production
TNS for IBM/AIX RISC System/6000: Version 10.2.0.4.0 - Productio
NLSRTL Version 10.2.0.4.0 - ProductionOS is AIX 5.3 for Oracle 10 and AIX 6.1 for Oracle 11.
We are currently in the process of migrating some applications from Oracle 10 to 11. Our admins have setup a new development system for us with an Oracle 11 instance. Regarding performance the new system behaves more or less the same than our old, e.g. when executing SQLs we notice hardly any performance differences and those we find are slightly in favour of the new system.
But now we discovered that the time it takes to establish a database connection via SQL*Plus is longer on the Oracle 11 system. Running the following code
sqlplus -s user/pw@database <<END
quit
ENDa thousand times takes ~60s under Oracle 10 but ~140s under Oracle 11. This may not seem much but we are running a test framework consisting of a bunch of shell scripts where several thousand connections are openend via SQL*Plus to execute some SQLs, so that even this small time difference results in rather huge difference in total runtime. The SQLs themself require roughly the same time in both databases, as already mentioned above they are in fact slightly faster in Oracle 11.
To analyze the time difference I ran a trace for the connect with the following parameters in sqlnet.ora
TRACE_LEVEL_CLIENT=4
TRACE_UNIQUE_CLIENT=ONand found out that there is a time difference of about 70ms during the connect handshake:
Oracle 10
[22-MAR-2013 12:13:09:595] nscon: doing connect handshake...
[22-MAR-2013 12:13:09:595] nscon: sending NSPTCN packet
[22-MAR-2013 12:13:09:621] nscon: got NSPTRS packet
[22-MAR-2013 12:13:09:621] nscon: sending NSPTCN packetOracle 11
(1) [22-MAR-2013 12:15:26:812] nscon: doing connect handshake...
(1) [22-MAR-2013 12:15:26:812] nscon: sending NSPTCN packet
(1) [22-MAR-2013 12:15:26:906] nscon: got NSPTRS packet
(1) [22-MAR-2013 12:15:26:906] nscon: sending NSPTCN packetUnder Oracle 10 there are 26ms between sending the NSPTCN packet and getting the NSPTRS packet, whereas under Oracle 11 this takes 94ms. I ran the trace again, this time with
TRACE_LEVEL_CLIENT=16and got the following results for the critical interval:
Oracle 10:
[22-MAR-2013 13:17:37:638] nscon: sending NSPTCN packet
[22-MAR-2013 13:17:37:638] nspsend: entry
[22-MAR-2013 13:17:37:638] nspsend: plen=218, type=1
[22-MAR-2013 13:17:37:638] nttwr: entry
[22-MAR-2013 13:17:37:638] nttwr: socket 9 had bytes written=218
[22-MAR-2013 13:17:37:638] nttwr: exit
[22-MAR-2013 13:17:37:638] nspsend: packet dump
<<packet dump removed>>
[22-MAR-2013 13:17:37:638] nspsend: 218 bytes to transport
[22-MAR-2013 13:17:37:638] nspsend: normal exit
[22-MAR-2013 13:17:37:638] nscon: exit (0)
[22-MAR-2013 13:17:37:638] nsdo: nsctxrnk=0
[22-MAR-2013 13:17:37:638] nsdo: normal exit
[22-MAR-2013 13:17:37:638] nsdo: entry
[22-MAR-2013 13:17:37:638] nsdo: cid=0, opcode=68, *bl=512, *what=9, uflgs=0x0, cflgs=0x3
[22-MAR-2013 13:17:37:638] nsdo: rank=64, nsctxrnk=0
[22-MAR-2013 13:17:37:638] nsdo: nsctx: state=2, flg=0x4005, mvd=0
[22-MAR-2013 13:17:37:638] nsdo: gtn=10, gtc=10, ptn=10, ptc=2011
[22-MAR-2013 13:17:37:638] nscon: entry
[22-MAR-2013 13:17:37:638] nscon: recving a packet
[22-MAR-2013 13:17:37:638] nsprecv: entry
[22-MAR-2013 13:17:37:638] nsprecv: reading from transport...
[22-MAR-2013 13:17:37:638] nttrd: entry
[22-MAR-2013 13:17:37:665] nttrd: socket 9 had bytes read=8
[22-MAR-2013 13:17:37:665] nttrd: exit
[22-MAR-2013 13:17:37:665] nsprecv: 8 bytes from transport
[22-MAR-2013 13:17:37:665] nsprecv: tlen=8, plen=8, type=11
[22-MAR-2013 13:17:37:665] nsprecv: packet dump
[22-MAR-2013 13:17:37:665] nsprecv: 00 08 00 00 0B 00 00 00 |........|
[22-MAR-2013 13:17:37:665] nsprecv: normal exit
[22-MAR-2013 13:17:37:665] nscon: got NSPTRS packetOracle 11
(1) [22-MAR-2013 13:33:40:504] nscon: sending NSPTCN packet
(1) [22-MAR-2013 13:33:40:504] nspsend: entry
(1) [22-MAR-2013 13:33:40:504] nspsend: plen=205, type=1
(1) [22-MAR-2013 13:33:40:504] nttwr: entry
(1) [22-MAR-2013 13:33:40:504] nttwr: socket 8 had bytes written=205
(1) [22-MAR-2013 13:33:40:504] nttwr: exit
(1) [22-MAR-2013 13:33:40:504] nspsend: packet dump
<<packet dump removed>>
(1) [22-MAR-2013 13:33:40:505] nspsend: 205 bytes to transport
(1) [22-MAR-2013 13:33:40:505] nspsend: normal exit
(1) [22-MAR-2013 13:33:40:505] nscon: exit (0)
(1) [22-MAR-2013 13:33:40:505] snsbitts_ts: entry
(1) [22-MAR-2013 13:33:40:505] snsbitts_ts: acquired the bit
(1) [22-MAR-2013 13:33:40:505] snsbitts_ts: normal exit
(1) [22-MAR-2013 13:33:40:505] nsdo: nsctxrnk=0
(1) [22-MAR-2013 13:33:40:505] snsbitcl_ts: entry
(1) [22-MAR-2013 13:33:40:505] snsbitcl_ts: normal exit
(1) [22-MAR-2013 13:33:40:505] nsdo: normal exit
(1) [22-MAR-2013 13:33:40:505] nsdo: entry
(1) [22-MAR-2013 13:33:40:505] nsdo: cid=0, opcode=68, *bl=2048, *what=9, uflgs=0x0, cflgs=0x3
(1) [22-MAR-2013 13:33:40:505] snsbitts_ts: entry
(1) [22-MAR-2013 13:33:40:505] snsbitts_ts: acquired the bit
(1) [22-MAR-2013 13:33:40:505] snsbitts_ts: normal exit
(1) [22-MAR-2013 13:33:40:505] nsdo: rank=64, nsctxrnk=0
(1) [22-MAR-2013 13:33:40:505] snsbitcl_ts: entry
(1) [22-MAR-2013 13:33:40:505] snsbitcl_ts: normal exit
(1) [22-MAR-2013 13:33:40:505] nsdo: nsctx: state=2, flg=0x4005, mvd=0
(1) [22-MAR-2013 13:33:40:505] nsdo: gtn=10, gtc=10, ptn=10, ptc=8155
(1) [22-MAR-2013 13:33:40:505] nscon: entry
(1) [22-MAR-2013 13:33:40:505] nscon: recving a packet
(1) [22-MAR-2013 13:33:40:505] nsprecv: entry
(1) [22-MAR-2013 13:33:40:505] nsprecv: reading from transport...
(1) [22-MAR-2013 13:33:40:505] nttrd: entry
(1) [22-MAR-2013 13:33:40:618] nttrd: socket 8 had bytes read=8
(1) [22-MAR-2013 13:33:40:618] nttrd: exit
(1) [22-MAR-2013 13:33:40:618] nsprecv: 8 bytes from transport
(1) [22-MAR-2013 13:33:40:618] nsprecv: tlen=8, plen=8, type=11
(1) [22-MAR-2013 13:33:40:618] nsprecv: packet dump
(1) [22-MAR-2013 13:33:40:618] nsprecv: 00 08 00 00 0B 00 00 00 |........|
(1) [22-MAR-2013 13:33:40:618] nsprecv: normal exit
(1) [22-MAR-2013 13:33:40:618] nscon: got NSPTRS packetAny ideas what could be the reason for this time difference? Something in our network configuration or something else?

With local connections - I do not think a TCP packet send from an IP to the same IP, leaves the interface as an actual wire protocol/signal. If I'm correct, then running local connection tests will be mostly useless in checking the actual network infrastructure.
Tests 3 and 4 should be showing the same connection times as the same physical network infrastructure is used - only the direction is reversed in the tests.
I would assume that port settings on the switches and interface settings on the routers treat packets equally in both directions between 2 servers. But this could in part explain the problem if this is not the case. In a case of a router for example, the 1st test's ingress interface is the egress interface of the 2nd test (and vice versa). Configurations can differ substantially between interfaces on the same router. Likewise if there is a firewall - as different rule sets are applied in each test and these rule sets could differ.
So I would not be too quick to state that this is definitely not a network problem. But I agree that based on the small percentage difference (assuming comparable tests), it does not look like a network issue.
The next step is to determine what the delay is between the listener accepting the client connection, and the connection being serviced by a dedicated server process.
This will require listener tracing - tracing the time from when the listener accepted the connection (and parsed the TNS connection string), to handing off the connection to the dedicated server process.
As a comparison test, you can also test shared server connections. Dispatcher processes (of the db instance) register themselves with the listener. The shared server client hand off is thus done to an existing server process - no need for the Listener to make a kernel call to load and initialise an executable image.
Shared connections are typically faster than dedicated connections in this respect.
If there is a major time difference, then it means some kind of issue with the listener dealing with dedicated servers as oppose to dispatcher hand off's. As both connections would have had very similar network transit time - which means the connection time difference is related directly to dealing with a dedicated server connection request and hand off.
You can also substitute the oracle executable with a wrapper - and troubleshoot the actual dedicated server startup. I've only done this with Oracle XE 10.2 though and with local IPC connections. Unsure how robust this will be for testing purposes via TCP using 11g.

How to use log in to Oracle 8i personal edition SQL Plus?

Hi, this is my first time using Oracle 8i personal edition. But after installation, I was told to enter
User Name, password and host string in order to use SQL Plus
But I have no idea what to enter for the above three
By the way, I was prompted with the following message after installation,
Global Database Name: Oracle
SID : Oracle
Password : ******
database name : People
system identifier : People
system account : manager

hi to connect to SQL plus write the following:
user name: scott
password : tiger
host string : leave it empty if it requires again then write orcl
bye

Logging into ORACLE 9I using SQL*PLUS.TNS Error

I have installed Oracle 9i for windows and am trying to login using SQL*PLUS
user: system
pwd: manager
Host String: BHURU
It says TNS could resolve service name.
I have all the services running in the admin monitor.
Am I missing something? Please advise.

Can you post your tnsnames.ora file contents and listener.ora contents here?
There may be tons of things wrong with the error actually,
ORA-12154:     TNS:could not resolve the connect identifier specified
Cause:     A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached.
Action:
- If you are using local naming (TNSNAMES.ORA file):
- Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA)
- Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible.
- Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file.
- Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable.
- If you are using directory naming:
- Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Verify that the LDAP directory server is up and that it is accessible.
- Verify that the net service name or database name used as the connect identifier is configured in the directory.
- Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier
- If you are using easy connect naming:
- Verify that "EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Make sure the host, port and service name specified are correct.
- Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming.
HTH
Aman....
Edited by: Aman.... on Oct 7, 2008 5:46 PM
Added error info

Connection ... able to connect using sql developer, but not sqlplus or toad too

Hi folks, having this issue, with only one of my so many databases, what might be the reason and how to fix/correct this, please assist.
Able to connect using sql developer, but not sqlplus or toad too; sqlplus error: ORA-12154: TNS:could not resolve the connect identifier specified
thanks in advance.

SQLDEVELOPER works since it use JDBC Thin & does not use tnsnames.ora
ORA-12154 ALWAYS only occurs on SQL Client & no SQL*Net packets ever leave client system
ORA-12154 [B]NEVER[/B] involves the listener, the database itself or anything on the DB Server.
ORA-12154 occurs when client requests a connection to some DB server system using some connection string.
TNS-03505 is thrown by tnsping & is same error as ORA-12154 thrown by sqlplus or others.
The lookup operation fails because the name provided can [B]NOT[/B] be resolved to any remote DB.
The analogous operation would be when you wanted to call somebody, but could not find their name in any phonebook.
The most frequent cause for the ORA-12154 error is when the connection alias can not be found in tnsnames.ora.
The lookup operation of the alias can be impacted by the contents of the sqlnet.ora file; specifically DOMAIN entry.
TROUBLESHOOTING GUIDE: ORA-12154 & TNS-12154 TNS:could not resolve service name [ID 114085.1]
http://edstevensdba.wordpress.com/2011/02/26/ora-12154tns-03505/

Using sql*plus to login to oracle 9i

I have installed Oracle 9i for windows and am trying to login using SQL*PLUS
user: system
pwd: manager
Host String: BHURU
It says TNS could resolve service name.
I have all the services running in the admin monitor.
Am I missing something?

This is not a right forum to post your problem. This is SQL PL/SQL forum.
Please post it in Database General Forum.
Regards.
Satyaki De.

Error when connecting to SQL*PLUS via ODBC to Excel

OS: Windows 2000 Professional
Oracle DB: 9i release 2
SQL*Plus: Release 9.2.0.1.0
MS Excel: 2000
===================
When I try to connect to SQL*PLUS via ODBC to Excel with "connect scott/tiger@odbc:libro" I get the following error:
ORA-03121: no interface driver connected - function not performed

SQL Server objects are commonly case sensitive, so please surround the column and table names by double quotes:
SELECT "Type_PK_ID" FROM "dbo"."boundaries"@sqlserver
SIDE NOTE: Oracle is by default not case sensitive and all object names are stored in upper case. To get case sensitive objects they need to be surrounded by double quotes. In HSODBC case sensitive table names were commonly found even when not surrounded by double quotes as the gateway used internal SQL Server methods to find the correct table nameing - this method does not work for column names. So to be able to query a case sensitive column it needs to be surrounded by double quotes and the table name must be written as stored in the source database.

TNSPING failure and but surprising connecting through SQL*PLUS

I have Oracle 9i and Oracle 10g express edition installed on my local machine.But since in the path i specified path of Oracle10g first so always tnsnames.ora got picked up from Oracl10g directory which is
C:\softwares\oraclexe\app\oracle\product\10.2.0\server\network\admin\sqlnet.ora
Following are the contents of my sqlnet.ora :--->
SQLNET.AUTHENTICATION_SERVICES = (NTS)
Following are the contents of my tnsnames.ora:-->
CCTD91 =(DESCRIPTION =
(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = cctdev91.jankoc.com)(PORT = 1521)))(CONNECT_DATA =(SERVICE_NAME = CCTD91)))
Now when i am doing tnsping to this i got the error as:
C:\>tnsping cctd91
TNS Ping Utility for 32-bit Windows: Version 10.2.0.1.0 - Production on 23-APR-2011 16:08:52
Copyright (c) 1997, 2005, Oracle. All rights reserved.
Used parameter files:
C:\softwares\oraclexe\app\oracle\product\10.2.0\server\network\admin\sqlnet.ora
TNS-03505: Failed to resolve name
But when i connect through Oracle 9i client(SQL*Plus) like peter/devworks@CCTD91, then i am able to connect successfully to Oracle 11g.
Could someone let me know why TNSPING is failing for this and then still why i am able to connect thru SQL*PLUS using the name defined in TNSNAMES.ORA. ?

sqlnet.ora is having just one line:
SQLNET.AUTHENTICATION_SERVICES = (NTS)
I tried by adding another line: NAMES.DIRECTORY_PATH=(TNSNAMES) but did not make any difference so i removed.
C:\>lsnrctl service
LSNRCTL for 32-bit Windows: Version 10.2.0.1.0 - Production on 24-APR-2011 19:06:36
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC_FOR_XE)))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Service "XEXDB" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Handler(s):
"D000" established:0 refused:0 current:0 max:1002 state:ready
DISPATCHER <machine: localhost, pid: 3288>
(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.XXX.XXX.COM)(PORT=1041))
Service "XE_XPT" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
LOCAL SERVER
Service "xe" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
LOCAL SERVER
The command completed successfully
C:\>lsnrctl status
LSNRCTL for 32-bit Windows: Version 10.2.0.1.0 - Production on 24-APR-2011 19:08:48
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC_FOR_XE)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Production
Start Date 23-APR-2011 16:05:49
Uptime 1 days 3 hr. 2 min. 59 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Default Service XE
Listener Parameter File C:\softwares\oraclexe\app\oracle\product\10.2.0\server\network\admin\listener.ora
Listener Log File C:\softwares\oraclexe\app\oracle\product\10.2.0\server\network\log\listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC_FOR_XEipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost.xxx.xxx.COM)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=8080))(Presentation=HTTP)(Session=RAW))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "XEXDB" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Service "XE_XPT" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
Service "xe" has 1 instance(s).
Instance "xe", status READY, has 1 handler(s) for this service...
The command completed successfully
C:\>
Oracle 11g is installed remotely on our office LAN.
Please note that i just removed company name with XXX from the above lsnrcts commands output, just for security reasons.

ORA-01031: insufficient privileges when connecting by SQL PLUS 8.0 with sys

From client, I use SQL PLUS 8.0 to connect to server: sys/password@MYDB1 as sysdba
The error always raises “ORA-01031: insufficient privileges”
I have done:
- Set: remote_login_passwordfile=exclusive in tnsname.ora file
- Uncomment: SQLNET.AUTHENTICATION_SERVICES in “sqlnet.ora” file
Also on this client:
to use SQL PLUS 8.0 to connect to server: manager/password@MYDB1. To connect normally
to use PLSQL Deverloper (it is the same oracle_home with SQL PLUS 8.0) to connect to database normally with user sys.
To use Enterprise manager console (it is other oracle_home with SQL PLUS 8.0) to connect to database normally with user sys
Please, help me to solve this trouble

THIS IS CONTENT OF SQLNET.ora CLIENT
# copyright (c) 1996 by the Oracle Corporation
# NAME
# sqlnet.ora
# FUNCTION
# Oracle Network Client startup parameter file example
# NOTES
# This file contains examples and instructions for defining all
# Oracle Network Client parameters. It should be possible to read
# this file and setup a Client by uncommenting parameter definitions
# and substituting values. The comments should provide enough
# explanation to enable a reasonable user to manage his TNS connections
# without having to resort to 'real' documentation.
# SECTIONS
# ONames Client
# Namesctl
# Native Naming Adpaters
# MODIFIED
# skanjila 06/06/97 - Correct default for Automatic_IPC
# eminer 05/15/97 - Add the relevant onrsd parameters.
# asriniva 04/23/97 - Merge with version from doc
# ggilchri 03/31/97 - mods
# bvasudev 02/07/97 - Change sqlnet.authentication_services documentation
# bvasudev 11/25/96 - Merge sqlnet.ora transport related parameters
# asriniva 11/12/96 - Revise with new OSS parameters.
# asriniva 11/05/96 - Add ANO parameters.
# - ONames Client ----------------------------------------------------
#names.default_domain = world
#Syntax: domain-name
#Default: NULL
# Indicates the domain from which the client most often requests names. When
# this parameter is set the default domain name (for example, US.ACME), the
# domain name will be automatically appended to any unqualified name in an
# ONAmes request (query, register, deregister, etc). Any name which contains
# an unescaped dot ('.') will not have the default domain appended. Simple
# names may be qualified with a trailing dot (for example 'rootserver.').
#names.initial_retry_timeout = 30
#Syntax: 1-600 seconds
#Default: 15 (OSD)
# Determines how long a client will wait for a response from a Names Server
# before reiterating the request to the next server in the preferred_servers
# list.
#names.max_open_connections = 3
#Syntax: 3-64
#Default: ADDRS in preferred_servers
# Determines how many connections an ONames client may have open at one time.
# Clients will ordinarily keep connections to servers open once they are
# established until the operation (or session in namesctl) is complete. A
# connection will be opened whenever needed, and if the maximum would be
# exceeded the least recently used connection will be closed.
#names.message_pool_start_size = 10
#Syntax: 3-256
#Default: 10
# Determines the initial number of messages allocated in the client's message
# pool. This pool provides the client with pre-allocated messages to be used
# for requests to ONames servers. Messages which are in the pool and unused
# may be reused. If a message is needed and no free messages are available in
# the pool more will be allocated.
#names.preferred_servers = (address_list =
# (address=(protocol=ipc)(key=n23))
# (address=(protocol=tcp)(host=nineva)(port=1383))
# (address=(protocol=tcp)(host=cicada)(port=1575))
#Syntax: ADDR_LIST
#Default: Well-Known (OSD)
# Specifies a list of ONames servers in the client's region; requests will be
# sent to each ADDRESS in the list until a response is recieved, or the list
# (and number of retries) is exhausted.
# Addresses of the following form specify that messages to the ONames server
# should use Oracle Remote Operations (RPC):
# (description =
# (address=(protocol=tcp)(host=nineva)(port=1383))
# (connect_data=(rpc=on))
#names.request_retries = 2
#Syntax: 1-5
#Default: 1
# Specifies the number of times the client should try each server in the list
# of preferred_servers before allowing the operation to fail.
#names.directory_path
#Syntax: <adapter-name>
#Default: TNSNAMES,ONAMES,HOSTNAME
# Sets the (ordered) list of naming adaptors to use in resolving a name.
# The default is as shown for 3.0.2 of sqlnet onwards. The default was
# (TNSNAMES, ONAMES) before that. The value can be presented without
# parentheses if only a single entry is being specified. The parameter is
# recognized from version 2.3.2 of sqlnet onward. Acceptable values include:
# TNSNAMES -- tnsnames.ora lookup
# ONAMES -- Oracle Names
# HOSTNAME -- use the hostname (or an alias of the hostname)
# NIS -- NIS (also known as "yp")
# CDS -- OSF DCE's Cell Directory Service
# NDS -- Novell's Netware Directory Service
# - Client Cache (ONRSD) ---------------------------------------------
names.addresses = (ADDRESS=(PROTOCOL=IPC)(KEY=ONAMES))
Syntax: ADDR
Default: (ADDRESS=(PROTOCOL=IPC)(KEY=ONAMES))
Address on which the client cache listens (is available to clients).
Any valid TNS address is allowed. The default should be used if at
all possible; clients have this entry hardwired as the first line
of their server-list file (sdns.ora). If the address is set to a
non-default value the client's preferred_servers parameter should
be set to include the client-cache address first.
names.authority_required = False
Syntax: T/F
Default: False
Determines whether system querys (for the root etc) require Authoritative
answers.
names.auto_refresh_expire = 259200
Syntax: Number of seconds, 60-1209600
Default: 259200
This is the amount of time (in seconds) the server will cache the addresses
of servers listed in server-list file (sdns.ora). When this time expires the
server will issue another query to the servers in those regions to refresh
the data.
names.auto_refresh_retry = 180
Syntax: Number of seconds, 60-3600
Default: sec.     180
This set how often the server will retry when the auto_refresh query fails.
names.cache_checkpoint_file = cache.ckp
Syntax: filename
Default: $ORACLE_HOME/network/names/ckpcch.ora
Specifies the name of the operating system file to which the Names Server
writes its foreign data cache.
names.cache_checkpoint_interval = 7200
Syntax: Number of seconds, 10-259200
Default: 0 (off)
Indicates the interval at which a Names Server writes a checkpoint of its
data cache to the checkpoint file.
names.default_forwarders=
(FORWARDER_LIST=
(FORWARDER=
(NAME= rootserv1.world)
(ADDRESS=(PROTOCOL=tcp)(PORT=42100)(HOST=roothost))))
Syntax: Name-Value/address_list
Default: NULL
A list (in NV form) of the addresses of other servers which should be used to
forward querys while in default_forwarder (slave) mode. NAME is the global
names for the server to which forwards whould be directed, and ADDRESS is its
address.
names.default_forwarders_only = True
Syntax: T/F
Default: False
When set to true this server will use the servers listed in default_forwarders
to forward all operations which involve data in foreign regions. Otherwise it
will use the servers defined in the server-list file (sdns.ora) in addition
to any defined in the default_forwarders parameter.
names.log_directory = /oracle/network/log
Syntax: directory
Default: $ORACLE_HOME/network/log
Indicates the name of the directory where the log file for Names Server
operational events are written.
names.log_file = names.log
Syntax: filename
Default: names.log
The name of the output file to which Names Server operational events are
written.
names.log_stats_interval = 3600
Syntax: Number of seconds, 10-ub4max
Default: sec.     0 (off)
Specifies the number of seconds between statistical entries in log file.
names.log_unique = False
Syntax: T/F
Default: False
If set to true the server will guarantee that the log file will have a unique
name which will not overwrite any existing files (note that log files are
appended to, so log information will not be lost if log_unique is not true).
names.max_open_connections = 10
Syntax: 3-64
Default: 10
Specifies the number of connections that the Names Server can have open at any
given time. The value is generated as the value 10 or the sum of one
connection for listening, five for clients, plus one for each foreign domain
defined in the local administrative region, whichever is greater. Any
operation which requires the server to open a network connection will use
an already open connection if it is available, or will open a connection
if not. Higher settings will save time and cost network resources; lower
settings save network resources, cost time.
names.max_reforwards = 2
Syntax: 1-15
Default: 2
The maximum number of times the server will attempt to forward a certain
operation.
names.message_pool_start_size = 24
Syntax: 3-256
Default: 10
Determines the initial number of messages allocated in the server's message
pool. This pool provides the server with pre-allocated messages to be used
for incoming or outgoing messages (forwards). Messages which are in the pool
and unused may be reused. If a message is needed and no free messages are
available in the pool more will be allocated.
names.no_modify_requests = False
Syntax: T/F
Default: False
If set to true, the server will refuse any operations which modify the
data in its region (it will still save foreign info in the cache which is
returned from foreign querys).
names.password = 625926683431AA55
Syntax: encrypted string
Default: NULL
If set the server will require that the user provide a password in his
namesctl session (either with sqlnet.ora:namesctl.server_password or 'set
password') in order to do 'sensitive' operations, like stop, restart, reload.
This parameter is generally set in encrypted form, so it can not be set
manually.
names.reset_stats_interval = 3600
Syntax: 10-ub4max
Default: 0 (off)
Specifies the number of seconds during which the statistics collected by the
Names Servers should accumulate. At the frequency specified, they are reset
to zero. The default value of 0 means never reset statistics.
names.trace_directory = /oracle/network/trace
Syntax: directory
Default: $ORACLE_HOME/network/trace
Indicates the name of the directory to which trace files from a Names Server
trace session are written.
names.trace_file = names.trc
Syntax: filename
Default: names.trc
Indicates the name of the output file from a Names Server trace session.
names.trace_func # NA
Syntax: T/F
Default: False
Internal mechanism to control tracing by function name.
names.trace_level = ADMIN
Syntax: T/F
Default: False
Syntax: {OFF,USER,ADMIN,0-16}
Default: OFF (0)
Indicates the level at which the Names Server is to be traced.
Available Values:
     0 or OFF - No trace output
     4 or USER - User trace information
     10 or ADMIN - Administration trace information
     16 or SUPPORT - WorldWide Customer Support trace information
names.trace_mask = (200,201,202,203,205,206,207)
Syntax: list of numbers
Default: NULL
Internal mechanism to control trace behavior.
names.trace_unique = True
Syntax: T/F
Default: False
Indicates whether each trace file has a unique name, allowing multiple trace
files to coexist. If the value is set to ON, a process identifier is appended
to the name of each trace file generated.
# - Namesctl ---------------------------------------------------------
#namesctl.trace_directory = /oracle/network/trace
#Syntax: directory
#Default: $ON/trace
# Indicates the name of the directory to which trace files from a namesctl
# trace session are written.
#namesctl.trace_file = namesctl.trc
#Syntax: filename
#Default: namesctl.trc
# Indicates the name of the output file from a namesctl trace session.
#namesctl.trace_func # NA
#Syntax: word list
#Default: NULL
# Internal mechanism to control tracing by function name.
#namesctl.trace_level = ADMIN
#Syntax: {OFF,USER,ADMIN,0-16}
#Default: OFF (0)
# Indicates the level at which the namesctl is to be traced.
# Available Values:
#     0 or OFF - No trace output
#     4 or USER - User trace information
#     10 or ADMIN - Administration trace information
#     16 or SUPPORT - WorldWide Customer Support trace information
#namesctl.trace_mask # NA
#Syntax: number list
#Default: NULL
# Internal mechanism to control trace behavior.
#namesctl.trace_unique = True
#Syntax: T/F
#Default: False
# Indicates whether each trace file has a unique name, allowing multiple trace
# files to coexist. If the value is set to ON, a process identifier is appended
# to the name of each trace file generated.
#namesctl.no_initial_server = False
#Syntax: T/F
#Default: False
# If set to TRUE namesctl will suppress any error messages when namesctl is
# unable to connect to a default names server.
#namesctl.internal_use = True
#Syntax: T/F
#Default: False
# If set to true namesctl will enable a set of internal undocumented commands.
# All internal commands are preceded by an underscore ('_') in order to
# distinguish them as internal. Without going into details, the commands
# enabled are:
# adddata createname deletename
# fullstatus ireplacedata newttlname
# pause                 remove_data renamename
# replacedata start                 walk*
# There are also a set of names server variables which may be set when
# namesctl is in internal mode:
# authorityrequired autorefresh*
# cachecheckpoint_interval cachedump
# defaultautorefresh_expire defaultautorefresh_retry
# defaultforwarders_only forwardingdesired
# maxreforwards modifyops_enabled
# nextcache_checkpoint nextcache_flush
# nextstat_log nextstat_reset
# reload                         request_delay
# restart                        shutdown
#namesctl.noconfirm = True
#Syntax: T/F
#Default: False
# When set to TRUE namesctl will suppress the confirmation prompt when
# sensitive operations (stop, restart, reload) are requested. This is
# quite helpful when using namesctl scripts.
#namesctl.server_password = mangler
#Syntax: string
#Default: NULL
# Automatically sets the password for the names server in order to perform
# sensitive operations (stop, restart, reload). The password may also be
# set manually during a namesctl session using 'set password'.
#namesctl.internal_encrypt_password = False
#Syntax: T/F
#Default: True
# When set to TRUE namesctl will not encrypt the password when it is sent to
# the names server. This would enable an unencrypted password to be set in
# names.ora:names.server_password
# - Native Naming Adpaters -------------------------------------------
#names.dce.prefix = /.:/subsys/oracle/names
#Syntax: DCE cell name
#Default: /.:/subsys/oracle/names
#Specifies the DCE cell (prefix) to use for name lookup.
#names.nds.name_context = personnel.acme
#Syntax: NDS name
#Default: (OSD?)
# Specifies the default NDS name context in which to look for the name to
# be resolved.
#names.nis.meta_map # NA
# Syntax: filename
# Default: sqlnet.maps
# Specifies the file to be used to map NIS attributes to an NIS mapname.
# Currently unused.
# - Advanced Networking Option Authentication Adapters ----------------
#sqlnet.authentication_services
# Syntax: A single value or a list from {beq, none, all, kerberos5,
#       cybersafe, securid, identitx}
# Default: NONE
# Enables one or more authentication services. To enable
# authentication via the Oracle Security Server, use (beq, oss). If
# the Advanced Networking Option has been installed with Kerberos5
# support, using (beq, kerberos5) would enable authentication via
# Kerberos.
sqlnet.authentication_services=(beq, oss)
## Parmeters used with Kerberos adapter.
#sqlnet.kerberos5_cc_name
# Syntax: Any valid pathname.
# Default: /tmp/krb5cc_<uid>
# The Kerberos credential cache pathname.
#sqlnet.kerberos5_cc_name=/tmp/mycc
#sqlnet.kerberos5_clockskew
# Syntax: Any positive integer.
# Default: 300
# The acceptable difference in the number of seconds between when a
# credential was sent and when it was received.
#sqlnet.kerberos5_clockskew=600
#sqlnet.kerberos5_conf
# Syntax: Any valid pathname.
# Default: /krb5/krb.conf
# The Kerberos configuration pathname.
#sqlnet.kerberos5_conf=/tmp/mykrb.conf
#sqlnet.kerberos5_realms
# Syntax: Any valid pathname
# Default: /krb5/krb.realms
# The Kerberos host name to realm translation file.
#sqlnet.kerberos5_realms=/tmp/mykrb.realms
#sqlnet.kerberos5_keytab
# Syntax: Any valid pathname.
# Default: /etc/v5srvtab
# The Kerberos secret key file.
#sqlnet.kerberos5_keytab=/tmp/myv5srvtab
#sqlnet.authentication_kerberos5_service
# Syntax: Any string.
# Default: A default is not provided.
# The Kerberos service name.
#sqlnet.authentication_kerberos5_service=acme
## Parmeters used with CyberSAFE adapter.
#sqlnet.authentication_gssapi_service
# Syntax: A correctly formatted service principal string.
# Default: A default is not provided.
# The CyberSAFE service principal
#sqlnet.authentication_gssapi_service=acme/[email protected]
## Parmeters used with Identix adapter.
#sqlnet.identix_fingerprint_method
# Syntax: Must be oracle.
# Default: A default is not provided.
# The Identix authentication server method
#sqlnet.identix_fingerprint_method=oracle
#sqlnet.identix_fingerprint_database
# Syntax: Any string.
# Default: A default is not provided.
# The Identix authentication server TNS alias
#sqlnet.identix_fingerprint_database=ofm
#sqlnet.identix_fingerprint_database_user
# Syntax: Any string
# Default: A default is not provided.
# The Identix authentication service well known username.
#sqlnet.identix_fingerprint_database_user=ofm_client
#sqlnet.identix_fingerprint_database_password
# Syntax: Any string
# Default: A default is not provided.
# The Identix authentication service well known password.
#sqlnet.identix_fingerprint_database_password=ofm_client
# - Advanced Networking Option Network Security -------------------------
#sqlnet.crypto_checksum_client
#sqlnet.crypto_checksum_server
#sqlnet.encryption_client
#sqlnet.encryption_server
# These four parameters are used to specify whether a service (e.g.
# crypto-checksumming or encryption) should be active:
# Each of the above parameters defaults to ACCEPTED.
# Each of the above parameters can have one of four possible values:
# value          meaning
# ACCEPTED     The service will be active if the other side of the
#          connection specifies "REQUESTED" or REQUIRED" and
#          there is a compatible algorithm available on the other
#          side; it will be inactive otherwise.
# REJECTED     The service must not be active, and the connection
#          will fail if the other side specifies "REQUIRED".
# REQUESTED     The service will be active if the other side specifies
#          "ACCEPTED", "REQUESTED", or "REQUIRED" and there is a
#          compatible algorithm available on the other side; it
#          will be inactive otherwise.
# REQUIRED     The service must be active, and the connection will
#          fail if the other side specifies "REJECTED" or if there
#          is no compatible algorithm on the other side.
#sqlnet.crypto_checksum_types_client
#sqlnet.crypto_checksum_types_server
#sqlnet.encryption_types_client
#sqlnet.encryption_types_server
# These parameters control which algorithms will be made available for
# each service on each end of a connection:
# The value of each of these parameters can be either a parenthesized
# list of algorithm names separated by commas or a single algorithm
# name.
# Encryption types can be: RC4_40, RC4_56, RC4_128, DES, DES40
# Encryption defaults to all the algorithms.
# Crypto checksum types can be: MD5
# Crypto checksum defaults to MD5.
#sqlnet.crypto_seed ="4fhfguweotcadsfdsafjkdsfqp5f201p45mxskdlfdasf"
#sqlnet.crypto_checksum_server = required
#sqlnet.encryption_server = required
# - Oracle Security Server ---------------------------------------------
#oss.source.my_wallet
# Syntax: A properly formatted NLNV list.
# Default: Platform specific. Unix: $HOME/oracle/oss
# The method for retrieving and storing my identity.
#oss.source.my_wallet
# =(source
# =(method=file)
# (method_data=/dve/asriniva/oss/wallet)
#oss.source.location
# Syntax: A properly formatted NLNV list.
# Default: Oracle method, oracle_security_service/oracle_security_service@oss
# The method for retrieving encrypted private keys.
#oss.source.location
# =(source
# =(method=oracle)
# (method_data=
# (sqlnet_address=andreoss)
# - Sqlnet(v2.x) and Net3.0 Client ------------------------------------------
# In the following descriptions, the term "client program" could mean
# either sqlplus, svrmgrl or any other OCI programs written by users
#trace_level_client = ADMIN
#Possible values: {OFF,USER,ADMIN,0-16}
#Default: OFF (0)
#Purpose: Indicates the level at which the client program
# is to be traced.
# Available Values:
# 0 or OFF - No Trace output
#     4 or USER - User trace information
#      10 or ADMIN - Administration trace information
#     16 or SUPPORT - Worldwide Customer Support trace information
#Supported since: v2.0
#trace_directory_client = /oracle/network/trace
#Possible values: Any valid directory path with write permission
#Default: $ORACLE_HOME/network/trace ($ORACLE_HOME=/oracle at customer
# site)
#Purpose: Indicates the name of the directory to which trace files from
# the client execution are written.
#Supported since: v2.0
#trace_file_client = /oracle/network/trace/cli.trc
#Possible values: Any valid file name
#Default:     $ORACLE_HOME/network/trace/cli.trc ($ORACLE_HOME =
#          /oracle at customer site)
#Purpose: Indicates the name of the file to which the execution trace
# of the client is written to.
#Supported since: v2.0
#trace_unique_client = ON
#Possible values: {ON, OFF}
#Default: OFF
#Purpose: Used to make each client trace file have a unique name to
#     prevent each trace file from being overwritten by successive
#     runs of the client program
#Supported since: v2.0
#log_directory_client = /oracle/network/log
#Possible values: Any valid directory pathname
#Default: $ORACLE_HOME/network/log ($ORACLE_HOME = /oracle at customer
#     site)
#Purpose: Indicates the name of the directory to which the client log file
#     is written to.
#Supported since: v2.0
#log_file_client = /oracle/network/log/sqlnet.log
#Possible values: This is a default value, u cannot change this
#Default: $ORACLE_HOME/network/log/sqlnet.log ($ORACLE_HOME=/oracle in
# customer site)
#Purpose: Indicates the name of the log file from a client program
#Supported since: v2.0
#log_directory_server = /oracle/network/trace
#Possible values: Any valid diretcory path with write permission
#Default: $ORACLE_HOME/network/trace ( $ORACLE_HOME=/oracle at customer
#     site)
#Purpose: Indicates the name of the directory to which log files from the
#      server are written
#Supported since: v2.0
#trace_directory_server = /oracle/network/trace
#Possible values: Any valid directory path with write permission
#Default: $ORACLE_HOME/network_trace ( $ORACLE_HOME=/oracle at customer
#     site)
#Purpose: Indicates the name of the directory to which trace files from
# the server are written
#Supported since: v2.0
#trace_file_server = /orace/network/trace/svr_<pid>.trc
#Possible values: Any valid filename
#Default: $ORACLE_HOME/network/trace/svr_<pid>.trc where <pid? stands for
# the process id of the server on UNIX systems
#Purpose: Indicates the name of the file to which the execution trace of
# the server program is written to.
#Supported since: v2.0
#trace_level_server = ADMIN
#Possible values: {OFF,USER,ADMIN,0-16}
#Default: OFF (0)
#Purpose: Indicates the level at which the server program
# is to be traced.
# Available Values:
# 0 or OFF - No Trace output
# 4 or USER - User trace information
# 10 or ADMIN - Administration trace information
# 16 or SUPPORT - Worldwide Customer Support trace information
#Supported since: v2.0
#use_dedicated_server = ON
#Possible values: {OFF,ON}
#Default:      OFF
#Purpose: Forces the listener to spawn a dedicated server process for
#     sessions from this client program.
#Supported since: v2.0
#use_cman = TRUE
#Possible values: {TRUE, FALSE}
#Default:     FALSE
#Purpose:
#Supported since: v3.0
#tnsping.trace_directory = /oracle/network/trace
#Possible values: Any valid directory pathname
#Default: $ORACLE_HOME/network/trace ($ORACLE_HOME=/oracle at customer
#     site)
#Purpose: Indicates the directory to which the execution trace from
#     the tnsping program is to be written to.
#Supported since: v2.0
#tnsping.trace_level = ADMIN
#Possible values: {OFF,USER,ADMIN,0-16}
#Default: OFF (0)
#Purpose: Indicates the level at which the server program
# is to be traced.
# Available Values:
# 0 or OFF - No Trace output
# 4 or USER - User trace information
# 10 or ADMIN - Administration trace information
# 16 or SUPPORT - Worldwide Customer Support trace information
#Supported since: v2.0
#sqlnet.expire_time = 10
#Possible values: 0-any valid positive integer! (in minutes)
#Default: 0 minutes
#Recommended value: 10 minutes
#Purpose: Indicates the time interval to send a probe to verify the
#     client session is alive (this is used to reclaim watseful
#     resources on a dead client)
#Supported since: v2.1
#sqlnet.client_registration = <unique_id>
#Possible values:
#Default: OFF
#Purpose: Sets a unique identifier for the client machine. This
#     identifier is then passed to the listener with any connection
#     request and will be included in the Audit Trail. The identifier
#     can be any alphanumeric string up to 128 characters long.
#Supported since: v2.3.2
#bequeath_detach = YES
#Possible values: {YES,NO}
#Default: NO
#Purpose: Turns off signal handling on UNIX systems. If signal handling
#     were not turned off and if client programs written by users make
#     use of signal handling they could interfere with Sqlnet/Net3.
#Supported since: v2.3.3
#automatic_ipc = OFF
#Possible values: {ON,OFF}
#Default: OFF
#Purpose: Force a session to use or not to use IPC addresses on the
#     client's node.
#Supported since: v2.0
#disable_oob = ON
#Possible values: {ON,OFF}
#Default: OFF
#Purpose: If the underlying transport protocol (TCP, DECnet,...) does
# not support Out-of-band breaks, then disable out-of-band
#     breaks
#Supported since: v2.0
#

Can't connect to SQL Plus after installation...

Windows XP (Admin account)
installed 10g XE
I have no other ORACLE_HOME or TNS files.
All services are started
here is the listener
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Beta
Start Date 17-NOV-2005 23:34:31
Uptime 0 days 0 hr. 5 min. 22 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Default Service XE
Listener Parameter File C:\oraclexe\app\oracle\product\10.2.0\server\network\a
dmin\listener.ora
Listener Log File C:\oraclexe\app\oracle\product\10.2.0\server\network\l
og\listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1ipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=VANDERBI-M8R870)(PORT=1521)))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
Instance "CLRExtProc", status UNKNOWN, has 3 handler(s) for this service...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
when I try to connect with SQL PLUS
SQL*Plus: Release 10.2.0.1.0 - Beta on Thu Nov 17 23:44:45 2005
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> connect / as sysdba
ERROR:
ORA-12560: TNS:protocol adapter error
I do have the entry in TNSNAMES.ORA
XE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = VANDERBI-M8R870)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = XE)
any ideas?

The TNS-12154 (ORA-12154) error appears when SQL*Net cannot find the alias specified for a connection in the TNSNAMES.ORA file or other naming adapter.
Since we can clearly see the XE entry in your TNSNAMES.ORA file from your further post, the message implies that you are not using the TNSNAMES.ORA that contains the entry, or something is changing the lookup so the entry is not found.
Using a different TNSNAMES.ORA can occur under the following situations:
1) You have a TNS_ADMIN environment variable or registry entry that points somewhere other than this TNSNAMES.ORA
2) You are on Windows NT and are using a SQLPLus that is in a different ORACLE_HOME. The WIndows environment forces the use of the networking subsystem in the ORACLE_HOME as the client program (such as SQLPLUS), which defaults to the TNSNAMES.ORA in the home as the client.
Things I would check:
- is there another TNSNAMES.ORA anywhere on the system
- is there a system environment variable called TNS_ADMIN, or is that string found in the registry
- is there possibly a second SQLPlus.exe (even on a networked drive) that migt be called before the XE - supplied SQLPLUS
It is also possible to have a SQLNET.ORA impacting the way TNSNAMES.ORA is used. If all else checks out, we should look at the %ORACLE_HOME%\network\admin\sqlnet.ora in detail as well.
By the way, the Oracle Network Administration docco has two whole chapters devoted to troubleshooting networking issues, from initial config through data errors in the various config files. If you want to track it faster, check out http://download-east.oracle.com/docs/cd/B19306_01/network.102/b14212/troublestng.htm

1.2.6 oracle lite connecting using SQL*PLUS

Similar Messages

Maybe you are looking for