Home
All Oracle Error Codes
Oracle DBA Forum

Frequent Oracle Errors

TNS:could not resolve the connect identifier specified
Backtrace message unwound by exceptions
invalid identifier
PL/SQL compilation error
internal error
missing expression
table or view does not exist
end-of-file on communication channel
TNS:listener unknown in connect descriptor
insufficient privileges
PL/SQL: numeric or value error string
TNS:protocol adapter error
ORACLE not available
target host or object does not exist
invalid number
unable to allocate string bytes of shared memory
resource busy and acquire with NOWAIT specified
error occurred at recursive SQL level string
ORACLE initialization or shutdown in progress
archiver error. Connect internal only, until freed
snapshot too old
unable to extend temp segment by string in tablespace
Credential retrieval failed
missing or invalid option
invalid username/password; logon denied
unable to create INITIAL extent for segment
out of process memory when trying to allocate string bytes
shared memory realm does not exist
cannot insert NULL
TNS:unable to connect to destination
remote database not found ora-02019
exception encountered: core dump
inconsistent datatypes
no data found
TNS:operation timed out
PL/SQL: could not find program
existing state of packages has been discarded
maximum number of processes exceeded
error signaled in parallel query server
ORACLE instance terminated. Disconnection forced
TNS:packet writer failure
see ORA-12699
missing right parenthesis
name is already used by an existing object
cannot identify/lock data file
invalid file operation
quoted string not properly terminated

Re: Oracle for Windows XP with INTEL inside

Graeme Farmer

2004-09-20

Replies:
Are you connecting to the host machine via RDP (MS Terminal Services
Client)?
If so, you cannot connect via the method you described (unless you are on
MS Server 2003 and you specify connection to the CONSOLE when initiating
your RDP session).

Also, you cannot connect "system as sysdba" (unless you specifically grant
the SYSDBA privilege to SYSTEM which is not standard practice). You should
connect "SYS AS SYSDBA".

If you DO connect over RDP on <Win2003 then to connect as SYSDBA you will
need to start the listener, configure remote_login_passwordfile=exclusive
in the (s)pfile and connect "SYS@(protected)".

Good luck.

Graeme



"Sinardy Xing" <SinardyXing@(protected)>
Sent by: oracle-l-bounce@(protected)
20/09/2004 02:08 PM
Please respond to
SinardyXing@(protected)


To
<oracle-l@(protected)>
cc

Subject
Oracle for Windows XP with INTEL inside






Hi guys,
Is that true that you cannot connect to Oracle 9.2.0 on Intel + XP machine
"WITHOUT A LISTENER?"


I got this from metalink

---------------------------------

Problem: You could get an ORA-09352 on version 7.x of the database, an
ORA-12203 on version 8.0.x of the database, or an ORA-12560 on version
8.1.x of the database.

Solution: This is because the bequeath connection is not supported on NT
terminal server. Note 66397.1 (INTEL: Windows NT Terminal Server Support)
shows the certification.

---------------------------------

Can you please tell me how to startup Oracle 9.2.0 wihtout using listener?
(on Win XP).

This is my attempt

---------------------------------

run... cmd

C:\> set ORACLE_SID=mytest       (I also try set the variable on the
System Property, Advanced Tab, User variables)

C:\> sqlplus /nolog

SQL> connect system as sysdba
password:.... manager

ORA-12560: TNS: erro....

---------------------------------


Thanks in advance


regards,

Sinardy


--
http://www.freelists.org/webpage/oracle-l



--
This transmission is for the intended addressee only and is confidential information. If you have received this transmission in error, please notify the sender and delete the transmission. The contents of this e-mail are the opinion of the writer only and are not endorsed by the Mincom Group of companies unless expressly stated otherwise.



--
http://www.freelists.org/webpage/oracle-l