Skip to Main Content
Forums

SQL Developer

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Bug while exporting to Excel

user5717693Apr 22 2016 — edited Apr 27 2016

Hi,

I've came across a bug during exporting data to Excel.

Basic info:

Windows 7 64 bit,

SQL Developer Version 4.1.3.20 Build MAIN-20.78,

Java(TM) SE Runtime Environment (build 1.8.0_66-b18)

Java HotSpot(TM) 64-Bit Server VM (build 25.66-b18, mixed mode)

Description:

2 connections to DB (different connections names, same credentials).

2 SQL queries run simultaneously by Run as Statement (longer ones)

After partial results are returned (complete results are bigger ones, with over 100 000 rows) right click on grid and Export as Excel 2003 to 2 different files.

Task Progress shows 2 processes. Firstly Executing Query, then Exporting and count of rows exported.

Bug arises when results of one query is being exported, and then kicks in exporting for second query.

First one finishes immediately, second goes on till the end but resulting file for first query is damaged and for second has 0 length and cannot be removed utils closing results grid in SQL Developer.

Looks like when second export starts during ongoing export of first query first one is being killed and results from second query are written to file of first query. Second file just sits there and waits for data that never will came.

Has anyone noticed similar behavior?

Comments

SureshDooly-Oracle

$oerr ora 12154
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.

Please cross-check the below:

Action: The following actions may be appropriate:
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 sqlnet.ora Oracle Net profile.
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.

1 - 1
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on May 25 2016
Added on Apr 22 2016
#bug, #excel, #export, #sql-developer
5 comments
1,180 views