Discussions
Categories
- 197K All Categories
- 2.5K Data
- 546 Big Data Appliance
- 1.9K Data Science
- 450.8K Databases
- 221.9K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 552 MySQL Community Space
- 479 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.1K ORDS, SODA & JSON in the Database
- 556 SQLcl
- 4K SQL Developer Data Modeler
- 187.2K SQL & PL/SQL
- 21.4K SQL Developer
- 296.4K Development
- 17 Developer Projects
- 139 Programming Languages
- 293.1K Development Tools
- 110 DevOps
- 3.1K QA/Testing
- 646.1K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 161 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.2K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 19 Java Essentials
- 162 Java 8 Questions
- 86K Java Programming
- 81 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
- 205 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 474 LiveLabs
- 39 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 175 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 233 Portuguese
Spool csv file format utf-8 vs ansi for excel
I have a spool formatting problem after moving from sqlcl version 4.2 on Windows 7 to 18.1 on Windows 10
In our database we use the character "¬" (unicode 172) as a separator for a particular set of data. But this character doesn't format correctly in excel after the spool.
I still have access to both machines; and from testing between the two, I'm finding that the spool defaults to UTF-8, but when the "¬" is found is changes to ANSI.
But on my new machine it just always outputs to UTF-8, which is causing formatting problems when opened in excel.
I'm a bit stuck as to what to do about this? Any guidence would be appriecated
Thanks
Answers
-
You could try using SQL*Plus instead, starting with version 12.2. it has the option SET MARKUP CSV and the output is using the codepage of the CMD window.
I usually set my CMD codepage via CHCP 1252 before launching SQL*Plus and the spool file can then be correctly openend by Excel.
Depending on your Windows language you might need another codepage.