Describe in sqlplus

Hi,
I am using oracle 9.2.0.4.0 and sql*plus for windows
(SQL*Plus: Release 9.2.0.1.0 - Production)
I have set linsize 1000 and buffers 1000
my select statements are working but when I give Desc <TABLE_NAME>
it shows me the name column and I am unable to see other columns.
It is due to linesize.
But is there any way we can see the output of describe correctly though linesize=1000.
Thanks
Arun Tayal

In my sqlplus with linesize=1000 it works(9.2.0.7 - Windows). Why do not you want set linesize=160 and
then use desc <tableName>
Best Regards
Krystian Zieja / mob

Similar Messages

Insert error on unfamiliar database

I am running Oracle 10.2.0.4 on a 3-node RAC with Windows Server 2008. I am a newbie that has taken over a database that has been left unattended for months. I am running through the configuration and making sure all the nodes are healthy and trying to tackle tasks as they come.
I need to insert a row and ran this script on development just fine:
insert into table_name(a, b, c)
values (1, 2, 3)
commit;
Once I moved it over to production I get this:
ERROR at line 1:
ORA-00942: table or view does not exist
I have checked the schema permissions of my user. I have alter, select, and update any table. The table is owned by my schema. I looked for synonyms but have none under my user. I checked views and have 43. I also have 129 triggers. I don't know anything about either the views or triggers but can start to try to go through them if that may be my issue.
Am I missing something simple here?
To add another question on here (sorry). How would you go about discerning all the triggers/views/synonyms in a database you are not familiar with? I have 3751 views, 161 triggers, and 20141 synonyms! I don't know where to start with that or what are the pertinent things that I need to know that I will have time to go through along with everything else?
Thanks for any help or suggestions!

I believe you are logged in as the user you say. However what I believe does not count, only what Oracle says.
Does the table_name show up in the ALL_TABLES query?
How about USER_TABLES then?
Can you run a DESCRIBE in Sqlplus ?
Can you SELECT from this table?
On the views, triggers, and synonyms questions. Why do you need to know these details? A view is just an in-line query, you can run infinate numbers of SQL combinations againist the database. Trying to know all of them is unreasonable in my humble opinion. Unless the trigger is invalid or you want to disable it for say a special update I would not worry much about these. Know what tables have triggers is probably enough. Synonyms are not a concern unless you have a ton of invalid ones, then I would clean them up.
SELECT
A.OWNER,
A.OBJECT_NAME,
A.OBJECT_TYPE,
A.STATUS,
B. SYNONYM_NAME,
B.TABLE_OWNER
FROM
DBA_OBJECTS A,
DBA_SYNONYMS B
where
A.status='INVALID'
AND
A.OBJECT_TYPE='SYNONYM'
AND
B. SYNONYM_NAME = A.OBJECT_NAME;Best Regards
mseberg
Edited by: mseberg on Dec 30, 2011 1:29 PM

Can't use SQL*Net connection

Hello i'm using oracle 8.1.5 under Linux (mandrake 7.1).The rdbms work properly but i can't use the syntax describe here :
sqlplus system/mnager@demo ...
It tells me an error (NETCMN) ...
However, when i try tnsping demo , the server reply that the connection was good ...
did someone has the same trouble ??
I suppose that my listener.ora or tnsnames.ora is not configurated properly...
The tools netasst don't work with this version :( ...
I can use only the syntax sqlplus system/manager ... but i want simulate a C/S connection.
Thanks.
null

Hi!
Starting from scratch, your users will not have a db account but do only exist in the OID. If you want to (or need to) create users in the database your problem does exist.
I believe that there are two possibilities:
a) users exist in OID only, they authenticate against SSO/OID, the data is then extracted with an application user
b) users do exist in the database, but you manage in the firewall that no direct connection from your users network is possible to the database server.
cu
Andreas

Sqlplus describe dumps core

The describe command dumps core eg.
SQL> describe help;
Name Null? Type
TOPIC NOT NULL VARCHAR2(50)
SEQ NOT NULL NUMBER
Segmentation fault (core dumped)
Same happens on v$license...
O/S RH6.0 Oracle 8.1.5 patch level 8.1.5.0.2
Regards
Theo

Seems linesize is the cause ie. linesize
of 126 or greater causes the core dump.
SQL> set linesize 125;
SQL> describe dba_tables; /* works fine */
SQL> set linesize 126;
SQL> describe dba_tables; /* dumps core */
Regards
Theo

Error conecting linux(sqlplus(ora8/9 client)) to SCO(ora7( DB))

HI. I apologize of my poor english....
Im trying to connect a new linux machine with ora8 to an old sco with ora7
points about...:
1- tnsping works fine. and I can see it in the logs
2- (here the problem) on "sqlplus user/pass@AUDI"
SQL*Plus: Release 9.2.0.1.0 - Production on Mie Nov 6 15:43:47 2002
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
ERROR:
ORA-03113: end-of-file on communication channel
It got nothing on the trace files on the ora7 DB.
And the ora7 DB is working fine at production level with net clients whitout problems.
The service names tnsnames.ora for AUDI is:
AUDI =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.119.207)(PORT = 1521))
(CONNECT_DATA = (SID = AUDI)(SERVER=DEDICATED))
3- I can connect to any ora8 ora9 DB. without any error
what can I do ?
can I trace to a lower level ?
I really do not know what to do, becose I cant see any error at server side.
may it be an enviroment variable problem ??? I tried to put the same as in the sco enviroment.but nothing.
Please tell me any way to continue with it.
I've searched about and tried it...:
Solution Description:
=====================
The ORA-3113 error is a general error reported by Oracle client tools,
which signifies that they cannot communicate with the oracle shadow
process. As it is such a general error more information must be collected
to help determine what has happened.
This short article describes what information to collect for an
ORA-3113 error when the Oracle server is on a Unix platform.
General Issues:
===============
1) Is it only one tool that encounters the error or
do you get an ORA-3113 from any tool doing a similar operation?
If the problem reproduces in SQL*Plus, use this in all tests
below.
2) Check if the problem is just restricted to:
[ ] One particular UNIX user,
[ ] Any UNIX user
or [ ] Any UNIX user EXCEPT as the Oracle user.
3) Check if the problem is just restricted to:
[ ] One particular ORACLE logon
or [ ] Any ORACLE logon that has access to the
relevant tables.
4) If you have a client-server configuration does this occur from:
[ ] Any client
[ ] Just one particular client
or [ ] Just one group of clients ?
If so what do these clients have in common ?
Eg: Software release .
5) Do you have a second server or database version where the
same operation works correctly?
Connecting to Oracle
====================
If the ORA-3113 error occurs when actually connecting to Oracle then
continue with this section. If you connect to Oracle successfully and get
the error on an established connection, please go to the next section
'An Established Connection'.
Local Connections
~~~~~~~~~~~~~~~~~
For local connections check the following:
1) Have you installed the Parallel Server Option?
ORA-3113 will occur if you have installed the Parallel
Server Option but do NOT have a Distributed Lock Manager
installed or running.
To deinstall the Parallel Server Option:
Shut down any Oracle instances
% script /tmp/relink.out
% cd $ORACLE_HOME/rdbms/lib
# 'oracle' should not exist so delete it if it present
% rm -f oracle
% make -f oracle.mk no_parropt ioracle
% exit
If the above reports any errors Oracle support will need to
see the contents of the file /tmp/relink.out.
2) Try using the SQL*Net V1 driver for local connections:
setenv TWO_TASK P:
Then try the client tool. If this now works you may have a
problem with the default SQL*Net driver.
3) Your 'oracle' executable may be corrupt. Relink it as follows:
Log in as the 'oracle' user.
% script /tmp/relink.out
% cd $ORACLE_HOME/rdbms/lib
% rm -f oracle
% make -f oracle.mk ioracle
% exit
If this reports any errors Oracle support will need to see
the contents of the file /tmp/relink.out .
4) Some Unix platforms need LD_LIBRARY_PATH to be set
correctly to resolve any dynamically linked libraries.
As the user with the problem:
% script /tmp/ldd.out
% id
% cd $ORACLE_HOME/bin
% ldd oracle
% exit
If the 'ldd' command does not exist go to the next step below.
Check that all lines listed show a full library file. If there
are any 'not found' lines reported contact Oracle support
with the output of /tmp/ldd.out.
5) If you cannot connect as the Oracle user AND your system has
the 'truss' command try the following when logged in as
'oracle' (using the relevant client tool):
% truss -o /tmp/truss.out -f sqlplus user/password
Exit from sqlplus (or the problem tool)
Keep the file /tmp/truss.out safe - Oracle MAY need to see it.
Remote Connections
==================
For remote connections check the following:
1) Check if you can make LOCAL connections. If not then follow
the steps above for LOCAL connection problems.
2) Which SQL*Net protocol are you using ?
Table C.1
~~~~~~~~~
SYMBOL SQL*Net V1 Layer Prefix Debug Listener
osnptt PIPE Two Task P: OSNTTD none
osnasy ASYNC A: OSNADBUG none
osnttt TCP/IP Two Task T: OSNTDBUG orasrv
osntlitcp TCP/TLI Two Task TT: OSNTLIDBUG tcptlisrv
osntlispx SPX Two Task X: OSNTLIDBUG spxsrv
osndnt DECNET Two Task D: OSNDDBUG none
For the protocol you are using check that the oracle
executable has this linked in as follows:
Log in as oracle on the server
% script /tmp/drivers.out
% cd $ORACLE_HOME/bin
% drivers oracle
% exit
Eg: If you are using TCP/IP it should list TCP/IP.
If the drivers command does not exist on your machine, check
the oracle executable as below substituting the relevant
symbol from Table C.1 for the word SYMBOL. If you do not
receive any output then:
% script /tmp/symbols.out
% cd $ORACLE_HOME/bin
% nm oracle | grep -i SYMBOL # Use relevant SYMBOL
% exit
Eg: For SQL*Net TCP/IP you would use the command:
% nm oracle | grep -i osnttt
If the required driver is not installed you should:
a) Relink Oracle (See step (B3) above).
b) Re-check the oracle executable for the
relevant driver. If it is still missing then
the relevant SQL*Net driver has probably not
been installed. Reinstall the required SQL*Net
driver.
3) Check your /etc/oratab or /var/opt/oracle/oratab file
is of the form:
# Comments begin with a HASH
SID:/path/to/oracle/home:N
And confirm:
[ ] There are no blank lines.
[ ] The PATH to ORACLE_HOME is correct and contains
no environment variables.
[ ] There are no ':'s in the ORACLE_HOME path.
[ ] There is NOTHING at the end of the line.
The last character on a line should be Y or N.
There should NOT be a fourth field.
4) If you have truss available try to truss the Oracle
connection. You will normally need the root privilege to do this
and should use truss on the relevant listener process (see
Table C1)
Eg: For TCP/IP the listener is 'orasrv' so enter these
commands as 'root':
% truss -o /tmp/truss.out -f -eall -p <PID_of_orasrv>
Attempt the connection to reproduce the ORA-3113 then
interrupt this 'truss' session.
An Established Connection:
==========================
If the ORA-3113 error occurs AFTER you have connected to Oracle, then
it is most likely that the oracle executable has terminated unexpectedly.
1) Determine which database you were connected to and
obtain the following init.ora parameter values:
Parameter Default
USER_DUMP_DEST $ORACLE_HOME/rdbms/log
BACKGROUND_DUMP_DEST $ORACLE_HOME/rdbms/log
CORE_DUMP_DEST $ORACLE_HOME/dbs
Eg: To find these log into SQL*DBA or Server Manager and:
SQLDBA> show parameter dump
2) Check in your 'USER_DUMP_DEST' for any Oracle trace file.
It is important to find the correct trace file. Use the
command 'ls -ltr' to list files in time order with the
latest trace files appearing LAST. If you are not sure
which trace file may be relevant, move all the current trace
files to a different directory and reproduce the problem.
The trace file will typically be of the form 'ora_<PID>.trc'.
3) If there is no trace file check for a core dump in the
CORE_DUMP_DEST. Check as follows:
% cd $ORACLE_HOME/dbs # Or your CORE_DUMP_DEST
% ls -l core*
If there is a file called core, check that its time matches
the time of the problem. If there are directories called
'core_<PID>' check for core files in each of these. It is
IMPORTANT to get the correct core file. Now obtain a stack
trace from this core file. Check each of the sequences below
for the procedure. One of the following should work for your
platform:
If you have dbx:
% script /tmp/core.stack
% dbx $ORACLE_HOME/bin/oracle core
(dbx) where
(dbx) quit
% exit
If you have sdb:
% script /tmp/core.stack
% sdb $ORACLE_HOME/bin/oracle core
* t
* q
% exit
If you have xdb:
% script /tmp/core.stack
% xdb $ORACLE_HOME/bin/oracle core
(xdb) t
(xdb) q
% exit
If you have adb:
% script /tmp/core.stack
% adb $ORACLE_HOME/bin/oracle core
$c
$q
% exit
4) Try to isolate the SQL command that is executing when
the error occurs. Eg: Is it a particular SQL statement
or PL/SQL block that causes the error ?
To help establish this turn on SQL_TRACE for the client
tool.
Eg: Product Action
~~~~~~~ ~~~~~~
SQL*Forms Use the '-s' statistics option at run time.
SQL*Plus Issue 'ALTER SESSION SET SQL_TRACE TRUE;'
Pro* EXEC SQL ALTER SESSION SET SQL_TRACE TRUE;
This should force a server side SQL trace file as detailed
in #2 above. The trace file should give a clue as to what
SQL was being executed.
5) Try to obtain any SQL*Net trace to show what the latest
operation sent to the oracle process was.
For SQL*Net V2 ask for the article [NOTE:16564.1]
For SQL*Net V1 check which SQL*Net protocol you are using
and note the Debug environment variable from table C1 above.
Then catch SQL*Net trace from the client. Eg: For SQL*Net
TCP/IP and sqlplus:
% setenv OSNTDBUG -1 # Use correct OSN*DBUG
variable
% sh
% sqlplus scott/tiger@t:hostname:sid 2>/tmp/net1.out
6) Based on information collected above try to determine a small
test case which will reproduce the problem. This is important
for two reasons:
a) It gives Oracle support a small test case if the
problem does not look like a known problem.
b) It gives you a simple way to check if any patch
supplied will fix the problem.
7) It may be useful to follow the instructions in step (4) above.
This will produce a lot of output but MAY be useful if no
other information is available.

HI. I apologize of my poor english....
Im trying to connect a new linux machine with ora8 to an old sco with ora7
points about...:
1- tnsping works fine. and I can see it in the logs
2- (here the problem) on "sqlplus user/pass@AUDI"
SQL*Plus: Release 9.2.0.1.0 - Production on Mie Nov 6 15:43:47 2002
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
ERROR:
ORA-03113: end-of-file on communication channel
It got nothing on the trace files on the ora7 DB.
And the ora7 DB is working fine at production level with net clients whitout problems.
The service names tnsnames.ora for AUDI is:
AUDI =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.119.207)(PORT = 1521))
(CONNECT_DATA = (SID = AUDI)(SERVER=DEDICATED))
3- I can connect to any ora8 ora9 DB. without any error
what can I do ?
can I trace to a lower level ?
I really do not know what to do, becose I cant see any error at server side.
may it be an enviroment variable problem ??? I tried to put the same as in the sco enviroment.but nothing.
Please tell me any way to continue with it.
I've searched about and tried it...:
Solution Description:
=====================
The ORA-3113 error is a general error reported by Oracle client tools,
which signifies that they cannot communicate with the oracle shadow
process. As it is such a general error more information must be collected
to help determine what has happened.
This short article describes what information to collect for an
ORA-3113 error when the Oracle server is on a Unix platform.
General Issues:
===============
1) Is it only one tool that encounters the error or
do you get an ORA-3113 from any tool doing a similar operation?
If the problem reproduces in SQL*Plus, use this in all tests
below.
2) Check if the problem is just restricted to:
[ ] One particular UNIX user,
[ ] Any UNIX user
or [ ] Any UNIX user EXCEPT as the Oracle user.
3) Check if the problem is just restricted to:
[ ] One particular ORACLE logon
or [ ] Any ORACLE logon that has access to the
relevant tables.
4) If you have a client-server configuration does this occur from:
[ ] Any client
[ ] Just one particular client
or [ ] Just one group of clients ?
If so what do these clients have in common ?
Eg: Software release .
5) Do you have a second server or database version where the
same operation works correctly?
Connecting to Oracle
====================
If the ORA-3113 error occurs when actually connecting to Oracle then
continue with this section. If you connect to Oracle successfully and get
the error on an established connection, please go to the next section
'An Established Connection'.
Local Connections
~~~~~~~~~~~~~~~~~
For local connections check the following:
1) Have you installed the Parallel Server Option?
ORA-3113 will occur if you have installed the Parallel
Server Option but do NOT have a Distributed Lock Manager
installed or running.
To deinstall the Parallel Server Option:
Shut down any Oracle instances
% script /tmp/relink.out
% cd $ORACLE_HOME/rdbms/lib
# 'oracle' should not exist so delete it if it present
% rm -f oracle
% make -f oracle.mk no_parropt ioracle
% exit
If the above reports any errors Oracle support will need to
see the contents of the file /tmp/relink.out.
2) Try using the SQL*Net V1 driver for local connections:
setenv TWO_TASK P:
Then try the client tool. If this now works you may have a
problem with the default SQL*Net driver.
3) Your 'oracle' executable may be corrupt. Relink it as follows:
Log in as the 'oracle' user.
% script /tmp/relink.out
% cd $ORACLE_HOME/rdbms/lib
% rm -f oracle
% make -f oracle.mk ioracle
% exit
If this reports any errors Oracle support will need to see
the contents of the file /tmp/relink.out .
4) Some Unix platforms need LD_LIBRARY_PATH to be set
correctly to resolve any dynamically linked libraries.
As the user with the problem:
% script /tmp/ldd.out
% id
% cd $ORACLE_HOME/bin
% ldd oracle
% exit
If the 'ldd' command does not exist go to the next step below.
Check that all lines listed show a full library file. If there
are any 'not found' lines reported contact Oracle support
with the output of /tmp/ldd.out.
5) If you cannot connect as the Oracle user AND your system has
the 'truss' command try the following when logged in as
'oracle' (using the relevant client tool):
% truss -o /tmp/truss.out -f sqlplus user/password
Exit from sqlplus (or the problem tool)
Keep the file /tmp/truss.out safe - Oracle MAY need to see it.
Remote Connections
==================
For remote connections check the following:
1) Check if you can make LOCAL connections. If not then follow
the steps above for LOCAL connection problems.
2) Which SQL*Net protocol are you using ?
Table C.1
~~~~~~~~~
SYMBOL SQL*Net V1 Layer Prefix Debug Listener
osnptt PIPE Two Task P: OSNTTD none
osnasy ASYNC A: OSNADBUG none
osnttt TCP/IP Two Task T: OSNTDBUG orasrv
osntlitcp TCP/TLI Two Task TT: OSNTLIDBUG tcptlisrv
osntlispx SPX Two Task X: OSNTLIDBUG spxsrv
osndnt DECNET Two Task D: OSNDDBUG none
For the protocol you are using check that the oracle
executable has this linked in as follows:
Log in as oracle on the server
% script /tmp/drivers.out
% cd $ORACLE_HOME/bin
% drivers oracle
% exit
Eg: If you are using TCP/IP it should list TCP/IP.
If the drivers command does not exist on your machine, check
the oracle executable as below substituting the relevant
symbol from Table C.1 for the word SYMBOL. If you do not
receive any output then:
% script /tmp/symbols.out
% cd $ORACLE_HOME/bin
% nm oracle | grep -i SYMBOL # Use relevant SYMBOL
% exit
Eg: For SQL*Net TCP/IP you would use the command:
% nm oracle | grep -i osnttt
If the required driver is not installed you should:
a) Relink Oracle (See step (B3) above).
b) Re-check the oracle executable for the
relevant driver. If it is still missing then
the relevant SQL*Net driver has probably not
been installed. Reinstall the required SQL*Net
driver.
3) Check your /etc/oratab or /var/opt/oracle/oratab file
is of the form:
# Comments begin with a HASH
SID:/path/to/oracle/home:N
And confirm:
[ ] There are no blank lines.
[ ] The PATH to ORACLE_HOME is correct and contains
no environment variables.
[ ] There are no ':'s in the ORACLE_HOME path.
[ ] There is NOTHING at the end of the line.
The last character on a line should be Y or N.
There should NOT be a fourth field.
4) If you have truss available try to truss the Oracle
connection. You will normally need the root privilege to do this
and should use truss on the relevant listener process (see
Table C1)
Eg: For TCP/IP the listener is 'orasrv' so enter these
commands as 'root':
% truss -o /tmp/truss.out -f -eall -p <PID_of_orasrv>
Attempt the connection to reproduce the ORA-3113 then
interrupt this 'truss' session.
An Established Connection:
==========================
If the ORA-3113 error occurs AFTER you have connected to Oracle, then
it is most likely that the oracle executable has terminated unexpectedly.
1) Determine which database you were connected to and
obtain the following init.ora parameter values:
Parameter Default
USER_DUMP_DEST $ORACLE_HOME/rdbms/log
BACKGROUND_DUMP_DEST $ORACLE_HOME/rdbms/log
CORE_DUMP_DEST $ORACLE_HOME/dbs
Eg: To find these log into SQL*DBA or Server Manager and:
SQLDBA> show parameter dump
2) Check in your 'USER_DUMP_DEST' for any Oracle trace file.
It is important to find the correct trace file. Use the
command 'ls -ltr' to list files in time order with the
latest trace files appearing LAST. If you are not sure
which trace file may be relevant, move all the current trace
files to a different directory and reproduce the problem.
The trace file will typically be of the form 'ora_<PID>.trc'.
3) If there is no trace file check for a core dump in the
CORE_DUMP_DEST. Check as follows:
% cd $ORACLE_HOME/dbs # Or your CORE_DUMP_DEST
% ls -l core*
If there is a file called core, check that its time matches
the time of the problem. If there are directories called
'core_<PID>' check for core files in each of these. It is
IMPORTANT to get the correct core file. Now obtain a stack
trace from this core file. Check each of the sequences below
for the procedure. One of the following should work for your
platform:
If you have dbx:
% script /tmp/core.stack
% dbx $ORACLE_HOME/bin/oracle core
(dbx) where
(dbx) quit
% exit
If you have sdb:
% script /tmp/core.stack
% sdb $ORACLE_HOME/bin/oracle core
* t
* q
% exit
If you have xdb:
% script /tmp/core.stack
% xdb $ORACLE_HOME/bin/oracle core
(xdb) t
(xdb) q
% exit
If you have adb:
% script /tmp/core.stack
% adb $ORACLE_HOME/bin/oracle core
$c
$q
% exit
4) Try to isolate the SQL command that is executing when
the error occurs. Eg: Is it a particular SQL statement
or PL/SQL block that causes the error ?
To help establish this turn on SQL_TRACE for the client
tool.
Eg: Product Action
~~~~~~~ ~~~~~~
SQL*Forms Use the '-s' statistics option at run time.
SQL*Plus Issue 'ALTER SESSION SET SQL_TRACE TRUE;'
Pro* EXEC SQL ALTER SESSION SET SQL_TRACE TRUE;
This should force a server side SQL trace file as detailed
in #2 above. The trace file should give a clue as to what
SQL was being executed.
5) Try to obtain any SQL*Net trace to show what the latest
operation sent to the oracle process was.
For SQL*Net V2 ask for the article [NOTE:16564.1]
For SQL*Net V1 check which SQL*Net protocol you are using
and note the Debug environment variable from table C1 above.
Then catch SQL*Net trace from the client. Eg: For SQL*Net
TCP/IP and sqlplus:
% setenv OSNTDBUG -1 # Use correct OSN*DBUG
variable
% sh
% sqlplus scott/tiger@t:hostname:sid 2>/tmp/net1.out
6) Based on information collected above try to determine a small
test case which will reproduce the problem. This is important
for two reasons:
a) It gives Oracle support a small test case if the
problem does not look like a known problem.
b) It gives you a simple way to check if any patch
supplied will fix the problem.
7) It may be useful to follow the instructions in step (4) above.
This will produce a lot of output but MAY be useful if no
other information is available.

Bug 6002713: Describe table@db_link gives an error that the object does not

Not sure if this is correct place to report on a known bug, can't seem to find a bug site/database on the SQL Developer home page.
Anyway in SQL Developer 1.2.1.32.13 release notes it says that the bug that stops you describing tables via a database link has been resolved.
This doesn't seem to be the case, well 100% fixed anyway.
The following statement works in SQLPlus but not in SQLDeveloper.
DESCRIBE schema_name.object_name@database_link;
You still get the message
ERROR: object object_name@database_link does not exist
It looks like the schema_name component is removed before the describe is executed?

Hi Cliff,
The Release Notes list the main known issues. So the bug #6002713 is a known issue and not a bug fixed. There is a separate Bugs Fixed list.
Not all bugs logged are published. I have now published this bug, so you can track it through Metalink.
Finally, while SQL Developer is a free product, you are supported through Metalink, and hence Oracle Support, if you have a Database Support contract. This detail is available from the "Pricing, Support & Licensing Questions" document on the SQL Developer page on OTN.
Regards
Sue

Connecting to an oracle database with SQLPlus

I'm trying to connect from one CentOS server with SQLPlus installed to another CentOS server with Oracle installed.
I've installed
oracle-instantclient-basic-11.1.0.1-1.i386.rpm
and
oracle-instantclient-sqlplus-11.1.0.1-1.i386.rpm
on the first server.
I'm able to connect to the oracle server via SQL Developer without difficulties.
When I try to connect to it via the command line with SQLPlus, I'm running the following:
sqlplus savantdb@//192.168.100.37:1521/orcl
But all I'm getting back is something that reads like help documentation.
I've exported the LD_LIBRARY_PATH to point at /usr/lib/oracle/11.1.0.1/client/lib/:/lib
I've created a tnsnames.ora file in my home directory containing the following:
orcl=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=tcp)
(HOST=drax)
(PORT=1521)
(CONNECT_DATA=
(SERVICE_NAME=orcl)
Then I tried moving to my home directory and running
sqlplus savantdb@orcl
This prompts for a password, then throws the following error:
ERROR:
ORA-12154: TNS:could not resolve the connect identifier specified
Then asks for a username/password, after which it throws the following error:
ERROR:
ORA-12162: TNS:net service name is incorrectly specified
What I want to do is allow my unit tests written in Selenium and PHPUnit to make shell_exec calls to execute sql files to recreate the database from scratch before putting the application through its paces. So I need to make it totally non-interactive.
Can anyone give me a clue where I'm going wrong here?

You are mixing up the various naming methods. Try to stick to one!
Your first attempt sqlplus savantdb@//192.168.100.37:1521/orcl uses the so-called "easy connect" method.
That's actually not a bad idea, as it is fairly short and does not require a "tnsnames.ora" file, which is a pain in the somewhere or else.
sqlplus has a parsing problem if you don't enclose part of the string in double quotes. You cannot find that in the documentation, but in Metalink Note 274757.1.
The syntax is like this:
sqlplus savantdb@\"//192.168.100.37:1521/orcl\"
Your second attempt tries to use the TNS (local) naming method, but for that you need to have an environment variable TNS_ADMIN pointing to the directory containing "tnsnames.ora". It does not matter if that directory is your current directory or not. You don't need that if you use the method described above.
The last error message is because of the annoying behaviour of sqlplus to ask for username and password (for a local connection!) again if the first attempt failed.
You can avoid that by giving sqlplus the -L flag.
Yours,
Laurenz Albe
PS: If you want to "make it totally non-interactive" you should add a password, like
sqlplus savantdb/password@//192.168.100.37:1521/orcl
In that case, you don't need to add the \"

How to 'DESCRIBE' a XMLType table

Hi,
When I describe a XMLType table, the output is truncated as follow :
SQL> desc scott.purchaseorder
Name Null? Type
TABLE of SYS.XMLTYPE(XMLSchema "http://localhost:8080/home/SCOTT/poSource/xsd/purchaseOrder.xsd" Ele
Is there any way to show the complete string ?
I have tried 'SET LONG' and 'SET LINESIZE', but not succeeded.
Any suggestion ?

I've also found under windows that using sqlplus within a command window gives better results with wrapping text than using sqlplusw (the gui version). Also Oracle are deprecating sqlplusw in favour of the SQL worksheet in enterprise manager from version 10 onwards, although it does still get installed at the moment if you really want to keep using it.
Regards

Cannot run 'exec dbms_xdb.setlistenerlocalaccess(false)' in sqlplus for XE

Cannot run 'exec dbms_xdb.setlistenerlocalaccess(false)' from within sqlplus.
Apparently it does not exist, because when i do
sql> describe dbms_xdb
it shows sethttpport... but not the setlistenerlocalaccess.

Do you get any error messages?
It works correctly for me:
C:\WINDOWS\system32>sqlplus system/<pwd>@xe
SQL*Plus: Release 10.2.0.1.0 - Production on Sa Feb 25 20:47:16 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Verbunden mit:
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
SQL> exec dbms_xdb.setListenerLocalAccess(true);
PL/SQL-Prozedur erfolgreich abgeschlossen.
SQL> exec dbms_xdb.setListenerLocalAccess(false);
PL/SQL-Prozedur erfolgreich abgeschlossen.###
1) As which user do you connect?
2) What version do you use (e.g. Windows Universal or Linux Western European)?
3) Please post your error sqlplus protocol
~Dietmar.

Avoid users to login into the database thru SQLPlus

I'm trying to use the after logon trigger described below, to avoid users to login into the database thru SQLPlus, user can only connect from from pls help me

If your only concern is preventing users from logging in via SQL*Plus, you could use the PRODUCT_USER_PROFILE table.
However, and this is a big however, this will not prevent users from logging in using any other tool (SQL Developer, SQL Programmer, TOAD, etc) if they know the Oracle user name and password. You can create a login trigger that generates an exception if the program that the client reports is connecting isn't on a list of valid products, but this sort of thing is easily circumvented just by renaming the executable on the client machine.
Fundamentally, if you have given a person an Oracle user name and an Oracle password, whatever privileges are available to the Oracle account are available to that individual. No matter what tool that person uses to connect to the database, they are going to have the same privileges. That's why you ideally want to restrict what users can do to the point that you don't care what tool they're using. Barring that, you can enable auditing and let the users know what they are and are not allowed to do by policy and use the audit logs to ensure compliance.
Justin

Could not connect from SQLPLUS

hi guys, i have a problem with my Oracle
My Database 10g database is on AIX 5L, I can connect to this database from local and i can connect from others computer, but i have a problem when i want connect from one oh my server which is installed with Oracle 10g as well. here is the error
ora10g@prod01:/home/ora10g> sqlplus system@devbant01
SQL*Plus: Release 10.2.0.1.0 - Production on Fri Sep 28 15:02:38 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter password:
ERROR:
ORA-00600: internal error code, arguments: [kssadd_stage: null parent], [], [],
ERROR:
ORA-00600: internal error code, arguments: [kssadd_stage: null parent], [], [],
Error accessing package DBMS_APPLICATION_INFO
SP2-0575: Use of Oracle SQL feature not in SQL92 Entry Level.
SQL>
anyone knows about this problem and how to fixed it?..it could not connect only from this server where others i can connect
please help
Thanks

Seems a bug described in the metalink note 419992.1 solved by applying patchset 10.2.0.3.
Nicolas.

Sqlplus "/as sysdba" is not working

We created oinstall group & oracle user (group is oinstall) on Solaris 10, 64bit SPARC box. And installed oracle 10g release 2. From the UNIX box sqlplus "/as sysdba" is not working.
sqlplus
Enter user-name: sys as sysdba
Enter password:
is working fine.
What could be the problem? Please help.
Thanks,
Prasad

For any of a number of reasons, you do not have 'operating system authentication' enabled.
This setup is fairly well described here http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/dba.htm#sthref149

Srvctl and sqlplus issue

Folks
I am having very weird issue. Need your help/opinion on this.
I have 2 node cluster, Solaris 10, 10.2.0.3 with CRS bundle. Installation went fine. No issue at all.
Now on one of the node (Node2), I am having problem.
Issue is:
If I reboot machine, everything comes up fine. But I can't do "sqlplus / as sysdba" to ASM as well as Database instance.
It says connected to idle instance. ps -ef |grep smon shows that both instances are up and running (ASM and Database). Even crs_stat shows, everything is up. Even "shutdown abort" doesn't work.
Now, When I shutdown instance using srvctl. and then start it up using sqlplus , it works. I am able to so sqlplus. BUT crs_stat shows instance DOWN. Also, if I try to stop instance using srvctl, it DOESNOT work.
So bottom line is , I can use either srvctl OR sqlplus in order to manage instances on that node.
I saw post on internet from Mike Ault describing similar situation and some other note on these forums also, but there is no solution. Also those problems are related to 11g only.
Re: srvctl issue
www.toadworld.com/LinkClick.aspx?fileticket=Y2Pd9kF64Wg=&tabid=234
Does anyone have any idea?
I have similar setup on Test environment and everything is working fine without any issue
Thanks in advance
PG

Hi.
Maybe you can do a checklist :
- When you type : "sqlplus / as sysdba" what is the content of ORACLE_SID variable ?
- Check the healthy of CRS stack using crsctl check crc command.
- Check the OCR integrity (ocrcheck) .
Regards

Sqlplus connection problem

when i connect sqlplus username/password following error occurs
SQL> Disconnected from Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.4.0 - Production
[oracle@ora9i bdump]$ sqlplus mkt/cslkcl
SQL*Plus: Release 9.2.0.4.0 - Production on Thu Dec 14 09:53:09 2006
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.4.0 - Production
SP2-0042: unknown command "head     1.1" - rest of line ignored.
SP2-0042: unknown command "access" - rest of line ignored.
SP2-0042: unknown command "symbols" - rest of line ignored.
SP2-0734: unknown command beginning "locks; str..." - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
comment     @# @
ERROR at line 1:
ORA-00969: missing ON keyword
SP2-0042: unknown command "1.1" - rest of line ignored.
SP2-0734: unknown command beginning "date     2006...." - rest of line ignored.
SP2-0042: unknown command "branches" - rest of line ignored.
SP2-0042: unknown command "next     " - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
Usage: DESCRIBE [schema.]object[@db_link]
SP2-0042: unknown command "head     1.1" - rest of line ignored.
SP2-0042: unknown command "access" - rest of line ignored.
SP2-0042: unknown command "symbols" - rest of line ignored.
SP2-0734: unknown command beginning "locks; str..." - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
comment     @# @
ERROR at line 1:
ORA-00969: missing ON keyword
SP2-0042: unknown command "1.1" - rest of line ignored.
SP2-0734: unknown command beginning "date     2006...." - rest of line ignored.
SP2-0042: unknown command "branches" - rest of line ignored.
SP2-0042: unknown command "next     " - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
Usage: DESCRIBE [schema.]object[@db_link]
SP2-0042: unknown command "head     1.1" - rest of line ignored.
SP2-0042: unknown command "access" - rest of line ignored.
SP2-0042: unknown command "symbols" - rest of line ignored.
SP2-0734: unknown command beginning "locks; str..." - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
comment     @# @
ERROR at line 1:
ORA-00969: missing ON keyword
SP2-0042: unknown command "1.1" - rest of line ignored.
SP2-0734: unknown command beginning "date     2006...." - rest of line ignored.
SP2-0042: unknown command "branches" - rest of line ignored.
SP2-0042: unknown command "next     " - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
Usage: DESCRIBE [schema.]object[@db_link]
SP2-0042: unknown command "head     1.1" - rest of line ignored.
SP2-0042: unknown command "access" - rest of line ignored.
SP2-0042: unknown command "symbols" - rest of line ignored.
SP2-0734: unknown command beginning "locks; str..." - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
comment     @# @
ERROR at line 1:
ORA-00969: missing ON keyword
SP2-0042: unknown command "1.1" - rest of line ignored.
SP2-0734: unknown command beginning "date     2006...." - rest of line ignored.
SP2-0042: unknown command "branches" - rest of line ignored.
SP2-0042: unknown command "next     " - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
Usage: DESCRIBE [schema.]object[@db_link]
SP2-0042: unknown command "head     1.1" - rest of line ignored.
SP2-0042: unknown command "access" - rest of line ignored.
SP2-0042: unknown command "symbols" - rest of line ignored.
SP2-0734: unknown command beginning "locks; str..." - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
comment     @# @
ERROR at line 1:
ORA-00969: missing ON keyword
SP2-0042: unknown command "1.1" - rest of line ignored.
SP2-0734: unknown command beginning "date     2006...." - rest of line ignored.
SP2-0042: unknown command "branches" - rest of line ignored.
SP2-0042: unknown command "next     " - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
Usage: DESCRIBE [schema.]object[@db_link]
SP2-0042: unknown command "head     1.1" - rest of line ignored.
SP2-0042: unknown command "access" - rest of line ignored.
SP2-0042: unknown command "symbols" - rest of line ignored.
SP2-0734: unknown command beginning "locks; str..." - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
comment     @# @
ERROR at line 1:
ORA-00969: missing ON keyword
SP2-0042: unknown command "1.1" - rest of line ignored.
SP2-0734: unknown command beginning "date     2006...." - rest of line ignored.
SP2-0042: unknown command "branches" - rest of line ignored.
SP2-0042: unknown command "next     " - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
Usage: DESCRIBE [schema.]object[@db_link]
SP2-0042: unknown command "head     1.1" - rest of line ignored.
SP2-0042: unknown command "access" - rest of line ignored.
SP2-0042: unknown command "symbols" - rest of line ignored.
SP2-0734: unknown command beginning "locks; str..." - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
comment     @# @
ERROR at line 1:
ORA-00969: missing ON keyword
SP2-0042: unknown command "1.1" - rest of line ignored.
SP2-0734: unknown command beginning "date     2006...." - rest of line ignored.
SP2-0042: unknown command "branches" - rest of line ignored.
SP2-0042: unknown command "next     " - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
Usage: DESCRIBE [schema.]object[@db_link]
SP2-0042: unknown command "head     1.1" - rest of line ignored.
SP2-0042: unknown command "access" - rest of line ignored.
SP2-0042: unknown command "symbols" - rest of line ignored.
SP2-0734: unknown command beginning "locks; str..." - rest of line ignored.
SP2-0044: For a list of known commands enter HELP
and to leave enter EXIT.
comment     @# @

When SQL*Plus starts up, it will look for a global login script called glogin.sql in the $ORACLE_HOME/sqlplus/admin directory. If found, this script will be executed.
Or you may have login.sql in the directory.
There are some syntax errors in the scripts. Find either of this scripts and correct the error.

Output format of sqlplus commands under shell script

hi experts
Can you help with some problems please?
1.) I try to run shell script from dbms_scheduler, which runs sqlplus and the output of sqlplus commands is written to file using command spool. To this point everything is running ok.
My problem is, that output of this file is: (e.g.)
SQL> PROMPT ****************USERB******************
****************USERB******************
SQL> --SELECT sid
SQL> -- FROM v
SQL> -- WHERE audsid = SYS_CONTEXT('userenv','sessionid');
But I don't want the whole first line in the output file. I only want the output of this command, like on the second line.
2.) How Can I write two outputs from sqlplus using command spool running at the same time into one file?
Like in first issue described above. The main sqlplus create a job and this execute the background sqlplus using shell script. But both, the main and the background sqlplus are written to output file at the same time. But only one is written into. But I want the both outputs in the file.
How Can I do that, if I can?
Thanks a lot.

user9357436 wrote:
hi experts
Can you help with some problems please?
1.) I try to run shell script from dbms_scheduler, which runs sqlplus and the output of sqlplus commands is written to file using command spool. To this point everything is running ok. then why are you here?
My problem is, that output of this file is: (e.g.)
SQL> PROMPT ****************USERB******************
****************USERB******************so remove PROMPT line from the file
>
SQL> --SELECT sid
SQL> -- FROM v
SQL> -- WHERE audsid = SYS_CONTEXT('userenv','sessionid');
But I don't want the whole first line in the output file. I only want the output of this command, like on the second line.
2.) How Can I write two outputs from sqlplus using command spool running at the same time into one file?you can not do so.
Like in first issue described above. The main sqlplus create a job and this execute the background sqlplus using shell script. But both, the main and the background sqlplus are written to output file at the same time. But only one is written into. But I want the both outputs in the file.
How Can I do that, if I can?Can't.
Now what?
>
Thanks a lot.Why using DBMS_SCHEDULER to invoke OS script to run sqlplus that runs SQL statements?
this is like making THREE Left Turns, instead of single Right Turn.
Just invoke PL/SQL procedure that does what needs to be done.

Describe in sqlplus

Similar Messages

Maybe you are looking for