Discussions
Categories
- 196.9K All Categories
- 2.2K Data
- 239 Big Data Appliance
- 1.9K Data Science
- 450.4K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 546 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.9K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.6K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 155 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 442 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
Delimiter not saved to SQL Developer import settings xml

When importing a CSV file to an existing table, SQL Developer (since 4.1?) offers the "Save state" option to save the import sessings to a SQLDeveloper Import Settings file (.sdimp) and "Restore state" to reuse import settings from GUI as well as from the command line utility "sdcli utility import"
The selected delimiter is not saved in the file, so when I try to use the import settings file with a delimiter other than the default (comma -- at least on my system), import fails.
Steps to reproduce:
- create a table with two varchar(50) columns
- prepare a CSV with 2 fields, delimited by semicolon (;) (BTW: file content preview is updated only on the second click on semicolon, which is annoying, but can be worked around)
- right click on the table in the object navigator, and choose "import data".
- select format: CSV, Delimiter: semicolon (and other options as required)
- next-next..., and before Finish, save the import settings by clicking on "Save state".
- complete the import data wizard.
- see that the resulting XML file does not have delimiter at /IMPORT_TOOL/IMPORT_DATA_FORMAT
And now try to use the import settings file:
- right click on the table in the object navigator, and choose "import data".
- click on "restore state", select the previously saved import settings file, and see that delimiter is not applied.
- SQL Developer will also not find the columns, so an error message will be displayed cited below, as it was unable to find the 2nd column in the CSV file
This error makes it impossible to import a semicolon-delimited CSV file using "sdcli utility import"
- please correct this bug
- is there a TAG that I should add to the SDimp file that "Restore state" would process, so I can work around this bug until it will be corrected? (I tried /IMPORT_TOOL/IMPORT_DATA_FORMAT/DELIMITER but it didn't work)
- BTW: while the SDimp file contains /IMPORT_TOOL/IMPORT_DATA_FORMAT/DELIMITER for file format "delimited", restore import setting does not work at all for formats: text, delimited
Error message shown when restoring import state:
Errors or differences detected opening configuration file . Import errors may occur if you proceed. Configuration file contains connection sample_connection. Configuration file contains table DEMOUSER.TABLE. Configuration file contains file /home/user/temp/sample.csv. Field [Ljava.lang.Object;@7ff07003 in configuration file is not specified in the data file.File definition saved in the configuration file does not match the import file. Field COLUMN2 in configuration file is not specified in the data file.
Answers
-
I'll take a look-see but it would be best if you could file an SR with MOS
-
OK, I've filed SR 3-11876368241 in MOS.
What I've forgotten to add here is the software versions used:
SQL Developer version: 4.1.2.20.64
Oracle JDK: 1.8.0_31, 64bit, Linux
Instant client: x64-12.1.0.2.0 (inactive per SQL Developer configuration)
The same erroneous behaviour on Windows 8, SQL Developer version: 4.1.2.20.64, Oracle JDK 8u66, 32bit.