SQLDeveloper encoding and export database
0
votes
0
answers
109
views
I've been requested to make a dump of an Oracle 11g EE Database. However, i can't use the Oracle Data Pump utility, since I have no direct access to the host machine, nor I think the db user have the correct privileges.
So I opted for using the Database export utility that SQL Developer provides. But I do have the following doubts:
- Am I actually viewing the correct encoding through SQL Developer? I'm asking this because I can see there's a lot of question marks inside some tables. I'm wondering if the application that saved the data used the wrong encoding, or if SQL Developer is using the wrong encoding and i'm not viewing it correctly.
- How do I export with the correct encoding? I'm aware that SQL Developer has an utility that would allow the user to export a script file with both DDL and DML instructions, but it asks me to specify the file encoding.
I've make some tests myself, but since i do not trust the tools i've used completely (EG: WinMerge does not recognise the Windows equivalent of ISO 8859-15, as far as i know), i'm wondering if anyone has been in my shoes and tried better.
The internal encoding of the DB should be WE8ISO8859P15, which I think it is the equivalent of ISO 8859-15. When I try to use the Export functionality of SQLDeveloper, it asks me in which encoding the file should use.
I've used this utility twice: exporting both a ISO 8859-15 Windows equivalent (can't remember it right now, i'll update this section asap) and a UTF-8 encoding. Both WinMerge and Meld tells me that the only difference between the files are the encoding (and not the characters)
Asked by Dont Throw Me Away
(1 rep)
Jan 6, 2025, 04:11 PM