Skip to Main Content
Forums

SQL & PL/SQL

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!

Print content of codepage conversion (cntd)

531871Aug 4 2009 — edited Aug 5 2009
Hello

Given the sql:
select  tegn,  convert_back, 
        rn chr, upper(substr(dump(tegn,16),instr(dump(tegn,16),':')+2)) hex, 
        upper(substr(dump(convert(tegn, 'we8BS2000', 'WE8ISO8859P1'),10),instr(dump(convert(tegn, 'we8BS2000', 'WE8ISO8859P1'),10),':')+1)) chr_BS2000 ,
       upper(substr(dump(convert(tegn, 'we8BS2000', 'WE8ISO8859P1'),16),instr(dump(convert(tegn, 'we8BS2000', 'WE8ISO8859P1'),16),':')+1)) Hex_BS2000 ,
       case when convert_back = tegn then null else '... OBS ...' end obs
from (select level rn, chr(level) tegn, convert(convert(chr(level), 'we8BS2000', 'WE8ISO8859P1'),'WE8ISO8859P1','we8BS2000') convert_back
from dual connect by level <= 255);
It would be very nice to have a maxtrix print of a code page like this:
......    00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
------------------------------------------------------------------------------------
00-0F     00 01 02 03 37 2D 2E 2F 16 05 15 0B  0C 0D 0E 0F
10-1F     10 11 12 13 3C 3D 32 26 18 .......
20-2F
F0-FF
-------------------------------------------------------------------------------------
......    00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
How do I chunk up the 256 lines resultset from the above SQL and make it into 16*16 lines the nicest way?

Best regards
Mette
This post has been answered by Frank Kulash on Aug 4 2009
Jump to Answer

Comments

Alex Keh-Oracle

These two errors have different root causes.

The first error is indicative that you are trying to use 64-bit .NET with 32-bit ODP.NET or vice-versa. The bitness of .NET FW and ODP.NET have to match. Once they do, you will no longer see this error.

The second error is due to using a version mismatch between Oracle Client and ODP.NET. For example, your Oracle Client may be version 12.2, but ODP.NET is version 11.2. This can occur inadvertently when you have multiple Oracle Clients installed on a machine. ODP.NET, like any other DLL, will look for its dependent Oracle Client DLLs. The first ones ODP.NET finds, it will use, but those versions may not match ODP.NET's version. To fix this problem, use the DllPath setting in your .NET config file. Set the value to the bin directory from which your ODP.NET should look for its dependent Oracle Client DLLs.

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

Post Details

Locked on Sep 2 2009
Added on Aug 4 2009
#pivot
2 comments
496 views