Default path for scripts within SQL Developer version 3.2.20.09.87

I have SQL Developer version 3.2.20.09.87 and needed to know if the 'Set default path to look for scripts' be a UNC path?
Thanks

I hadn't tried it but now I did and it worked.
I also tried setting the Utilities Export default file location to a UNC path and I was able to set it but when I try to go to it via the 'browse' button, it doesnt go to it. It does, however, use it when I export.
Also when I do File > Open, I'm not able to navigate to UNC paths via the 'Home' or 'Desktop' buttons on the left hand side of the window and am not able to navigate to a network location from the 'Locations' box.
Any ideas? I am on Windows 7.
Thanks

Similar Messages

Encoding error occurs using parameter "default path for scripts"

Hello,
assume we have a script "/home/artur/tymczasowe/test.sql". I can execute it using SQL Developer by:
@/home/artur/tymczasowe/test.sql
Everything works as expected.
Then I set parameter "Tools - Preferences - Database - Worksheet - Default path to look for script" to "/home/artur/tymczasowe" and executed:
@test.sql
This time national characters has been lost, everyone replaced with "�".
The script content:
--create table a(enc varchar2(8), data varchar2(255));
delete from a;
insert into a(enc, data) values ('cp1250', 'zażółć gęślą jaźń');
commit;
Operating system is Debian Squeeze amd64, Developer version is 3.1.07, Build MAIN-07.42. This problem occurs using previous, 3.0.* versions too.

Hi user633485
Logged bug:
Bug 13779254 - ENCODING DEFAULTS TO NATIVE RATHER THAN IDE SETTING USING DEFAULT PATH
-Turloch
SQLDeveloper Team

I ther any SQL developer version for SunOS 5.10 (Unix)

Is ther any SQL developer version for SunOS 5.10 (Unix). If it is available, please tell me from where it can be downloaded and how it can be installed?

You can use any of the downloads except the Mac or Linux ones.
We separated out the Windows downloads because that's the largest audience we have. So there are 2: one is the full install, and one which allows users to point SQL Developer to an existing, installed JDK. This means that you don't end up with duplicate or even multiple JDKs installed.You can download either of these. If you don't have the JDK installed, you might as well install the full build. The other thing about the full install is that it includes an early JDK release and many users prefer to use the latest JDK.
The entry for the "multiple platforms" is exactly the same build and code as the Windows without JDK. Both of these require you to download and install or already have a JDK installed.
I try to make this page clearer for each release. It seems I'm not there yet!
We certify on Windows, Linux and the Mac. There is a page detailing certification specifics see the home page of SQL Developer. We do not certify SunOS, but Unix platforms are supported. This means that you can use SQL Developer, but any issues you run into must be tested against a certified platform before we'll track the bugs.
Sue Harper
Product Manager

MS Access 2010 and Oracle SQL Developer Version 4.0.3.16 Error

OS: Windows 7 Enterprise
System Type: 64-bit Operating System
I can not get MS Access 2010 to work/open with SQL Developer version 4.0.3.16.
ERROR when testing connection to MS Access 2010
"Status : Failure -Test failed: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified"
I added the 32-bit ODBC data source for the MS Access I am trying to use with SQL Developer version 4.0.3.16 with the "C:\Windows\SysWOW64\odbcad32.exe" application, but I still get the same error.
I appears that SQL Developer version 4.0.3.16.is looking at the 64-bit driver (ODBC Data Source) and I have no idea to direct SQL Developer version 4.0.3.16 to use the 32-bit driver (ODBC Data Source) when opening MS Access 2010.
Thank you in advance for your advice.

I downloaded the SQL Developer version 4.0.3.16 "sqldeveloper-4.0.3.16.84-x64.zip" that included the jre.
How do I check which Java JDK I am running (32-bit versuns 64-bit)?
In the command prompt I use "java -version" and I get this message "java is not recognized as an internal or external command"

Create trigger not audited when run from sql developer Version 3.2.20.09

Creating or editing a trigger is not being stored in the audit table when run from sql developer.
Here is a sample script to show the issue:
Grant Connect,create table,create trigger To testuser Identified By testuser;
create table testuser.testtab(t1 number);
Select Count(*) From Dba_Audit_Trail Where Owner='TESTUSER';
CREATE OR REPLACE TRIGGER testuser.testtab_bi_trg BEFORE
Insert
ON testuser.testtab FOR EACH ROW
begin
null;
end;
Select Count(*) From Dba_Audit_Trail Where Owner='TESTUSER';
drop user testuser cascade;
If I run the script from sql developer the CREATE TRIGGER statement does not get audited.
If I run the script from sql plus or All Arround Automations PL/SQL Developer the CREATE TRIGGER statement does get audited.
If I edit the trigger from sql developer the CREATE TRIGGER statement does not get audited.
If I edit the trigger from All Arround Automations PL/SQL Developer the CREATE TRIGGER statement does get audited.

DoyleFreeman wrote:
Not sure what you mean by "perform the audit".
Have you tested my script? Does the "Select Count(*) From Dba_Audit_Trail Where Owner='TESTUSER';" increment by 1 after each of the ddl statements or only after the Create table statement.
Your question doesn't have ANYTHING to do with sql developer and should be posted in the Database General forum
https://forums.oracle.com/community/developer/english/oracle_database/general_questions
Yes - and it works just fine once you ENABLE AUDITING. Your scripIt does NOT include the statements or code used to ENABLE auditing and, specifically, enable auditing for triggers.
Auditing doesn't just 'happen'; you have to enable it and you have to specify any non-default auditing that you want to perform.
Have you read any of the extensive documentation about auditing to learn how to use it?
See the Database Security Guide
http://docs.oracle.com/cd/E11882_01/network.112/e16543/auditing.htm
Also see 'Auditing Functions, Procedures, Packages, and Triggers
http://docs.oracle.com/cd/E11882_01/network.112/e16543/auditing.htm#BCGBEAGC
And see the AUDIT statement in the SQL language doc for how to specify auditing of specific operations.
http://docs.oracle.com/cd/E11882_01/server.112/e26088/statements_4007.htm
Select count(*) From Dba_Audit_Trail Where (Owner='SCOTT' or username = 'SCOTT')
and action_name = 'CREATE TRIGGER';
COUNT(*)
0
audit create trigger by scott
CREATE OR REPLACE TRIGGER emp_copy_bi_trg BEFORE
Insert
ON emp_copy FOR EACH ROW
begin
null;
end;
Select count(*) From Dba_Audit_Trail Where (Owner='SCOTT' or username = 'SCOTT')
and action_name = 'CREATE TRIGGER';
COUNT(*)
1

Unit Test exports between different SQL Developer versions

Hi,
I am having problems with trying to export and import unit test suites between SQL Developer versions. I can't find any documentation in this area. We have a number of unit test suites exported as XML files from version 2.1.1.64, and below are combinations of things I have tried:
- I have tried to import a unit test suite into version 3.0.0.4 that was exported from version 2.1.1.64 and get the error "Import failed. unexpected null value". I expect that this is probably an unsupported action due to repository changes between the two versions - should I be able to do this?
- I have upgraded the repository with unit tests in it. The unit tests run perfectly well in the upgraded repository. However, if I try to export any suites or individual tests, I get an error "Export failed.". A XML file is created but with what looks like only the header part of it.
- I have created a new unit test suite in version 3.0.0.4 and this exports successfully.
- I have gone into each test of a suite in the upgraded repository and made a change so that I can perform a commit. When I do an export, this does then work successfully.
Therefore it appears that something is not carried out by default when the repository is upgraded, but this fixes itself if the test is amended and committed in the upgraded repository. Although this may be a workaround, we have 100's of tests and is not something I really want to do. Has anyone else experienced this and got any recommendations for this?
Thanks, Pierre.

Hi,
I am having problems with trying to export and import unit test suites between SQL Developer versions. I can't find any documentation in this area. We have a number of unit test suites exported as XML files from version 2.1.1.64, and below are combinations of things I have tried:
- I have tried to import a unit test suite into version 3.0.0.4 that was exported from version 2.1.1.64 and get the error "Import failed. unexpected null value". I expect that this is probably an unsupported action due to repository changes between the two versions - should I be able to do this?
- I have upgraded the repository with unit tests in it. The unit tests run perfectly well in the upgraded repository. However, if I try to export any suites or individual tests, I get an error "Export failed.". A XML file is created but with what looks like only the header part of it.
- I have created a new unit test suite in version 3.0.0.4 and this exports successfully.
- I have gone into each test of a suite in the upgraded repository and made a change so that I can perform a commit. When I do an export, this does then work successfully.
Therefore it appears that something is not carried out by default when the repository is upgraded, but this fixes itself if the test is amended and committed in the upgraded repository. Although this may be a workaround, we have 100's of tests and is not something I really want to do. Has anyone else experienced this and got any recommendations for this?
Thanks, Pierre.

Which sql developer version will support oracle 8.1.7

hi
which sql developer version will support oracle 8.1.7 or is it necessary to use plsql developer to connect to database (oracle 8.1.7)

Hi,
SQL Developer version 1.2.1 is able to connect to 8.1.7 with limited functionality (prepared reports and browser for objects could not work)..
Next version (tested with 3.2 64-bit) of SQL developer could be "hacked" to connect to 8.1.7 by simply copy file C:\oracle\product\10.2.0\client_1\jdbc\lib\classes12.zip from Oracle client prior 11
into appropriate jdk\jre\lib\ext folder.

NullPointerException when opening a script in SQL Developer 4.0.0.12

I recently upgraded to SQL Developer v.4.0.0.12 64 bit, and am running into some issues.
I am running this on 64 bit Windows 7. I have a 64 bit Oracle 11, and in addition have the 32 bit oracle client installed.
I made an association between the .sql file extension and sqldeveloper64W.exe.
However I frequently get a nullpointerexception when clicking on a script in the file explorer.
It seems to occur mostly if I loaded scripts into SQL Developer before.
If I close all the windows before closing SQL Developer and then click on a script in the file manager, things work (startup is arguably slower than v.3).
But in most cases either nothing happens, or I get the NullPointerException below.
What am I doing wrong?
Regards,
Wim
java.lang.NullPointerException
at oracle.dbtools.raptor.plsql.FindHighlightListener.editorDeactivated(FindHighlightListener.java:63)
at com.oracle.jdeveloper.nbwindowsystem.NbEditorManager.fireEditorEvent(NbEditorManager.java:1315)
at com.oracle.jdeveloper.nbwindowsystem.NbEditorManager.handleEditorEvent(NbEditorManager.java:1294)
at com.oracle.jdeveloper.nbwindowsystem.NbEditorManager.whenCurrentEditorChanges(NbEditorManager.java:1556)
at com.oracle.jdeveloper.nbwindowsystem.editor.TabGroup.whenCurrentEditorChanges(TabGroup.java:1026)
at com.oracle.jdeveloper.nbwindowsystem.editor.TabGroup.setCurrentTabGroupState(TabGroup.java:847)
at com.oracle.jdeveloper.nbwindowsystem.editor.TabGroup.addTabGroupState(TabGroup.java:129)
at com.oracle.jdeveloper.nbwindowsystem.NbEditorManager.createEditor(NbEditorManager.java:534)
at com.oracle.jdeveloper.nbwindowsystem.NbEditorManager.createEditor(NbEditorManager.java:511)
at com.oracle.jdeveloper.nbwindowsystem.NbEditorManager.openEditor(NbEditorManager.java:379)
at oracle.ide.cmd.OpenCommand.openWithNoProject(OpenCommand.java:337)
at oracle.ide.cmd.OpenCommand.access$100(OpenCommand.java:62)
at oracle.ide.cmd.OpenCommand$1.run(OpenCommand.java:266)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733)
at java.awt.EventQueue.access$200(EventQueue.java:103)
at java.awt.EventQueue$3.run(EventQueue.java:694)
at java.awt.EventQueue$3.run(EventQueue.java:692)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:703)
at oracle.javatools.internal.ui.EventQueueWrapper._dispatchEvent(EventQueueWrapper.java:169)
at oracle.javatools.internal.ui.EventQueueWrapper.dispatchEvent(EventQueueWrapper.java:151)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)

Please refer to this White paper for how to generate PL/SQL package for workflow deployment:
Oracle Data Miner (Extension of SQL Developer 4.0)
Generate a PL/SQL script for workflow deployment
http://www.oracle.com/technetwork/database/options/advanced-analytics/odmrcodegenwhitepaper-2042206.pdf

Japanese characters in SQL Developer Version 1.5.4

I am using SQL Developer ver 1.5.4 with Oracle 11g. There are Japanese characters stored in VARCHAR2 field.
When I execute a SELECT SQL query, SQL Developer does not display Japanese characters in the Result window -- it displays row of small square characters instead.
(When I execute the same query as a script -- it displays the Japanese characters in Script Output window,
What should I do to have SQL Developer to display Japanese characters in Result window?
Thank you!
Mark.
Edited by: MarcoPolo on Jul 7, 2009 11:16 AM

Hi there, Have you fixed this issue?
I'm having the same issue albeit with SQL Developer VERSION 1.5.5
The Select stmt displays the the empty square boxes in the result window, I've set the encoding preferences to UTF8 in the menu and font to Arial Unicode (there is no option to set script to Japanese). How can i display japanese characters in the results window??
When i export these empty square boxes in the result window to notepad (where encoding set to Unicode and Font set to Arial Unicode and Script to Japanese), the japanese value is displayed correctly in the notepad.
Kindly provide some input
Many Thanks

Oracle sql developer version

Hi,
My first question is
where do i find the version of oracle sql developer?
My second question is
when i check one of the OSUSER name column is null.how it occurs? and how do i give corresponding name to its column?
Kindly help .
thanx in advance

Hi,
Thankx for your help for my 1st question,it has answered.
My sql developer version is 2.1.0.63
Coming to my2nd question.
I have used the following command to check the corresponding user.
select sys_context('USERENV','OS_USER') from dual
It show null value for osuser column.
I use RHEL 4 operating system
None other than this user,all the user has osuser value.
So here i want assign value for the corresponding user?
Your help will be more appreciated

Changing password within SQL Developer

Hi, Thanks for the great product. I'm beginning to migrate from TOAD to SQL Developer and have run into one minor snafu. The one minor feature missing within SQL Developer (unless I missed it) is to easily change a password like TOAD in the UI (This is a common complaint among other devlopers trying it out). I work on a lot of seperate databases occasionally and have to reset the passwords every 60 days.
I would like to request this minor feature.
How can I change my password without using SQL Plus, but within SQL Developer? Is there a way?
Thank you!

Sounds like a good enhancement and I will record it. In the meanwhile, just open a SQL Worksheet and issue your command.
-- Sharon

Unable to generate insert stmt scripts using sql developer

We are not able to generate INSERT statement script using SQL Developer. In the INSERT script system is inserting some spaces due to carriage return which we cannot reviewed individually.

DELETE FROM IM_INSTANCE_EXT_VAL_FRM
WHERE IEVF_TRG_FLD_NAME = 'PRAI_NUM_03'
AND IEVF_INST_CODE = 'APV-QQ-03'
AND IEVF_BLK_NAME = 'PGIT_POL_RISK_ADDL_INFO_01';
-- INSERTING into IM_INSTANCE_EXT_VAL_FRM
Insert into IM_INSTANCE_EXT_VAL_FRM (IEVF_SYS_ID,IEVF_INST_CODE,IEVF_PROG_CODE,IEVF_BLK_NAME,IEVF_TRG_FLD_NAME,IEVF_ACT_FLDS,IEVF_ACTION,IEVF_PROC,IEVF_SRNO,IEVF_ERR_NO,IEVF_ERR_YN,IEVF_APP_CODE,IEVF_REMARKS,IEVF_UPD_UID,IEVF_UPD_DT,IEVF_CR_UID,IEVF_CR_DT,IEVF_TRG_NAME,IEVF_CLEAR_FLD_YN,IEVF_VALIDATE_YN) values (IEVF_SYS_ID.NEXTVAL,'APV-QQ-03','PGIT6_03','PGIT_POL_RISK_ADDL_INFO_01','PRAI_NUM_03','PRAI_DATA_15,','ENABLED','VFB_EV_GEN.EXT_VAL_DISABLE_PHY_DAMAGE(:PGIT_POL_RISK_ADDL_INFO_01.PRAI_POL_SYS_ID,
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_END_NO_IDX,
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_END_SR_NO,
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_LVL1_SYS_ID,
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_CODE_02,
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_NUM_03,:P_FLAG_OUT)',1,null,'N','01','VALIADTION',null,null,'PREMIA',
to_date('19-SEP-07','DD-MON-RR'),'WHEN-VALIDATE-ITEM','0','1');
Insert into IM_INSTANCE_EXT_VAL_FRM (IEVF_SYS_ID,IEVF_INST_CODE,IEVF_PROG_CODE,IEVF_BLK_NAME,IEVF_TRG_FLD_NAME,IEVF_ACT_FLDS,IEVF_ACTION,IEVF_PROC,IEVF_SRNO,IEVF_ERR_NO,IEVF_ERR_YN,IEVF_APP_CODE,IEVF_REMARKS,IEVF_UPD_UID,IEVF_UPD_DT,IEVF_CR_UID,IEVF_CR_DT,IEVF_TRG_NAME,IEVF_CLEAR_FLD_YN,IEVF_VALIDATE_YN) values (IEVF_SYS_ID.NEXTVAL,'APV-QQ-03','PGIT6_03','PGIT_POL_RISK_ADDL_INFO_01','PRAI_NUM_03',null,'VALIDATE','VFB_EV_GEN.EXT_VAL_VEHICLE_AGE(:PGIT_POL_RISK_ADDL_INFO_01.PRAI_POL_SYS_ID, :PGIT_POL_RISK_ADDL_INFO_01.PRAI_PSEC_SYS_ID,
''APV'',
''APV'',
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_NUM_03,
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_NUM_07,
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_NUM_08,
:P_FLAG_OUT,
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_NUM_35_OUT) ',3,null,'N','01','VALIADTION',null,null,'PREMIA',to_date('19-SEP-07','DD-MON-RR'),'WHEN-VALIDATE-ITEM','1','1');
Insert into IM_INSTANCE_EXT_VAL_FRM (IEVF_SYS_ID,IEVF_INST_CODE,IEVF_PROG_CODE,IEVF_BLK_NAME,IEVF_TRG_FLD_NAME,IEVF_ACT_FLDS,IEVF_ACTION,IEVF_PROC,IEVF_SRNO,IEVF_ERR_NO,IEVF_ERR_YN,IEVF_APP_CODE,IEVF_REMARKS,IEVF_UPD_UID,IEVF_UPD_DT,IEVF_CR_UID,IEVF_CR_DT,IEVF_TRG_NAME,IEVF_CLEAR_FLD_YN,IEVF_VALIDATE_YN) values (IEVF_SYS_ID.NEXTVAL,'APV-QQ-03','PGIT6_03','PGIT_POL_RISK_ADDL_INFO_01','PRAI_NUM_03','PRAI_DATA_15,','DEFAULT','VFB_EV_GEN.DEFAULT_PHYSICAL_DAMAGE_SYMBOL(:PGIT_POL_RISK_ADDL_INFO_01.PRAI_POL_SYS_ID,
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_PROD_CODE,
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_PSEC_SYS_ID,
''APV'',
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_NUM_03,
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_NUM_07,
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_CODE_03,
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_CODE_02,
:P_FLAG_OUT,
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_DATA_15_OUT)',2,null,'N','01','DEFAULT',null,null,'PREMIA',to_date('30-AUG-07','DD-MON-RR'),'WHEN-VALIDATE-ITEM','0','1');
Insert into IM_INSTANCE_EXT_VAL_FRM (IEVF_SYS_ID,IEVF_INST_CODE,IEVF_PROG_CODE,IEVF_BLK_NAME,IEVF_TRG_FLD_NAME,IEVF_ACT_FLDS,IEVF_ACTION,IEVF_PROC,IEVF_SRNO,IEVF_ERR_NO,IEVF_ERR_YN,IEVF_APP_CODE,IEVF_REMARKS,IEVF_UPD_UID,IEVF_UPD_DT,IEVF_CR_UID,IEVF_CR_DT,IEVF_TRG_NAME,IEVF_CLEAR_FLD_YN,IEVF_VALIDATE_YN) values (IEVF_SYS_ID.NEXTVAL,'APV-QQ-03','PGIT6_03','PGIT_POL_RISK_ADDL_INFO_01','PRAI_NUM_03',null,'VALIDATE','VFB_EV_GEN.EXT_VAL_PHY_DAMAGE(:PGIT_POL_RISK_ADDL_INFO_01.PRAI_POL_SYS_ID,
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_END_NO_IDX,
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_END_SR_NO,
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_LVL1_SYS_ID,
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_CODE_02,
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_NUM_03,
:P_FLAG_OUT,
:PGIT_POL_RISK_ADDL_INFO_01.PRAI_DATA_15_OUT)',9,null,'N','01','VALIADTION',null,null,'PREMIA',
to_date('19-SEP-07','DD-MON-RR'),'WHEN-VALIDATE-ITEM','1','1');
script which is taken from Sql Developer and got error while running in SQL* PLUS
Following error was raised on running the script in SQL * PLUS
5 rows deleted.
1 row created.
1 row created.
1 row created.
SP2-0734: unknown command beginning ":P_FLAG_OU..." - rest of line ignored.
SP2-0734: unknown command beginning ":PGIT_POL_..." - rest of line ignored.
SP2-0734: unknown command beginning "to_date('1..." - rest of line ignored.

Code completion(insight) not working in SQL Developer Version 2.1.1.64

I recently downloaded SQL developer Version 2.1.1.64. However the code completion feature is not working automatically. I have checked the Automatically complete code in SQL worsheet checkbox under Tools->Preferences-> Code Editor-> Completion Insight.
Strangely, I get the code completion pop up window when I explicitly press the completion insight shortcut(Ctrl + Space).
Please help.
Thanks and Regards.

Hi, I am getting the following logs :
Code completion time = 1015
*...?aux tok2?, parse time = 63
InsightableOracleDatabase.fetch() time = 360
Code completion time = 844
Finished parsing = 0
*...?aux tok2?, parse time = 62
InsightableOracleDatabase.fetch() time = 344
Code completion time = 812
Finished parsing = 0
*...?aux tok2?, parse time = 63
InsightableOracleDatabase.fetch() time = 359
Code completion time = 891
Finished parsing = 0
Thanks

Desc not working in SQL Developer Version 1.1.3 Build 27.69

Hi All,
I am using Oracle SQL Developer Version 1.1.3 Build 27.69
select count(*) from abccount(*)
100
using desc / describe table name gives error
desc abcERROR:
ERROR: object abc does not exist
1 rows selected
I am able to perform select on the table but not desc/describe. I tried suffixing with schema name , still the same error persists.
Kindly provide a workaround
Tnx

Well 1.1.3 is quite old.
The best thing to do IMHO is to update to the latest version, it will also enable a load of new features and fixes.
http://www.oracle.com/technetwork/developer-tools/sql-developer/downloads/index.html

SQL Worksheet fails to appear in Oracle SQL Developer Version 2.1

I cannot open the SQL Worksheet in Oracle SQL Developer Version 2.1. When I select SQL Worksheet from the Tools menu, a box appears saying that the SQL Worksheet is opening, but nothing happens. After the first attempt, the box does not appear, but again nothing happens.

Thats odd.
Do you see any exceptions in console ? (to see the console launch sqldeveloper.exe in ../sqldeveloper/sqldeveloper/bin dir.)
-Raghu

Default path for scripts within SQL Developer version 3.2.20.09.87

Similar Messages

Maybe you are looking for