Links
Home
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
GCC 4.x and ORA-00911

GCC 4.x and ORA-00911

2005-11-22       - By Pascal Bleser


This might be slightly off-topic but I've been desperately trying to find some
information about it,
and maybe someone could help on this issue.

When compiling our C++ applications with GCC 4.0.2, we notice a very bizarre
"ORA-00911 (See ORA-00911.ora-code.com)" error
coming back from the server.

Client:
- SUSE 9.1, x86
- Oracle client 9i (9.2.0.1.0)
- GCC 4.0.2 (plain build from source, unpatched)
- we're using OTL (http://otl.sf.net) (i.e. it's OCI calls underneath)
- NLS_LANG set to GERMAN_GERMANY.WE8ISO8859P1

Server:
- SLES 8, x86
- Oracle server 9i (9.2.0.6.0)
- schema's locale is GERMAN_GERMANY.WE8ISO8859P1

I see communication happen between client and server, so it seems the error is
reported by the
server (and not by the OCI client library).

The "funny" thing is that when I compile exactly the same codebase with GCC 3
(3.4.3), it just plain
works (it also works on a number of other Unix/compiler/Oracle version
combinations).

My first guess is that it's somehow related to character encoding. I tried to
specify various values
for NLS_LANG and LANG/LANGUAGE/LC_ALL/LC_CTYPE but all fail. I also tried to
pass -fexec-charset and
-finput-charset options to g++, didn't help either (the source is latin1).
I didn't find anything on the web about this issue and nothing special about
how GCC 4.x
handles/stores string constants that would have changed from GCC 3.x in the
compiler's release notes
either.

The more I think of it, the less it makes sense. Even if GCC 4.x did store
string constants as
UTF-8, it shouldn't affect OCI as the SQL strings don't include "special" chars
above ASCII and
hence, the string is latin1 and even ASCII (backwards) compatible.

I'm going to try to isolate this all the way down to OCI calls but if anyone has
- even the slightest idea what could cause this
- a similar setup that actually works (GCC 4 and Oracle 9i)
I would much appreciate any hints ;)

Thanks

cheers
--
 -o) Pascal Bleser               ATOS Worldline/Aachen(DE)
 /\\   System Architect              WLP Business Platform
_\_v "Really, I'm not out to destroy Microsoft.  That will
just be a completely unintentional side effect."-L.Torvalds

--
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting