I'm using the Test Window to call a function that returns a CLOB, which I store in a CLOB bind variable. Once the Test Window runs through, I open the CLOB in Large Data Editor, so I can save it locally. The text in the Text tab (and all others) looks correct, so I proceed by clicking on the "Save as..." button, at the top of the pop-up window, choose a location, type a file name and click Save.
So far everything as expected...
The problems start when I try using the file. The CLOB in question is a trace file generated by DBMS_HPROF.ANALYZE, and it needs to be processed by the "plshprof" command-line utility. This utility was failing with a very strange error:
ORA-44325: no entry points found in trace file...
I couldn't figure out what was wrong until I opened the saved file in HEX-editor (I use Notepad++, with HEX-Editor plugin). If you open the file in a regular text editor like Windows Notepad (or even Notepad++), the text appears to be fine. In HEX, however (in my case), the first two characters were some odd hieroglyphs, with hex values ff and fe. Then, there was a 00 character between every "regular" character in the file. For example, the first line of the "regular" file started with the following 3 characters (the actual line is much longer that 3 characters):
In HEX they showed as
So, my assumption so far is that Large Data Editor is (somehow) adding these ("garbage") characters when saving the file. The workaround is to highlight the content in the Text tab (Ctrl+A), copy it (Ctrl+C) and manually paste it (Ctrl+V) into a text file, in an external editor.
Please fix it (unless it's not a PL/SQL Developer issue).
I'm on Windows 7 Pro, 64-bit
Oracle 12.2 client, 32-bit
PL/SQL Developer 12.0.5.1828 (32-bit) 01.112462
So far everything as expected...
The problems start when I try using the file. The CLOB in question is a trace file generated by DBMS_HPROF.ANALYZE, and it needs to be processed by the "plshprof" command-line utility. This utility was failing with a very strange error:
ORA-44325: no entry points found in trace file...
I couldn't figure out what was wrong until I opened the saved file in HEX-editor (I use Notepad++, with HEX-Editor plugin). If you open the file in a regular text editor like Windows Notepad (or even Notepad++), the text appears to be fine. In HEX, however (in my case), the first two characters were some odd hieroglyphs, with hex values ff and fe. Then, there was a 00 character between every "regular" character in the file. For example, the first line of the "regular" file started with the following 3 characters (the actual line is much longer that 3 characters):
Code:
P#V
In HEX they showed as
Code:
ff fe 50 00 23 00 56
So, my assumption so far is that Large Data Editor is (somehow) adding these ("garbage") characters when saving the file. The workaround is to highlight the content in the Text tab (Ctrl+A), copy it (Ctrl+C) and manually paste it (Ctrl+V) into a text file, in an external editor.
Please fix it (unless it's not a PL/SQL Developer issue).
I'm on Windows 7 Pro, 64-bit
Oracle 12.2 client, 32-bit
PL/SQL Developer 12.0.5.1828 (32-bit) 01.112462