Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CLOSED]reading an Oracle Unicode database with a non-unicode database adapter.

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[CLOSED]reading an Oracle Unicode database with a non-unicode database adapter.
 Login/Join
 
Member
posted
Question for your pondering minds…..

What do you see as issues with Reading an Oracle Unicode database with an Oracle non-Unicode database adapter?
HISTORY:: a non-Unicode adapter was used against a non-Unicode database. sounds good.
then a new Unicode database and created a new domain was created that used a Unicode adapter against it. life was good.
then the TNS name for the non-Unicode adapter was changed to the same TNS name as the Unicode adapter. (how is life still good???)


It is apparently possible, but what are the repercussions? (I found a domain that is currently doing it, but can’t see how it can be right)

My gut is that the non-Unicode adapter would read the Unicode table incorrectly. (seems like the lengths would be off, double byte versus single byte).

This message has been edited. Last edited by: <Emily McAllister>,
 
Posts: 15 | Registered: October 17, 2012Report This Post
Virtuoso
posted Hide Post
Let's assume that the character encoding is UTF8 for this. Under UTF (Unicode Transformation Format) 8, not all characters are multi-byte. All US ANSI characters and numbers are single byte characters in UTF8 environment. French and all other language characters that are not part of the US ANSI character set are at least 2 bytes long. So, length of columns are only a potential issue if extended characters are present.

On the other side, if the db client is aware that query responses can be multi-byte, then they can be translated on the fly to. Same thing for writing, most DBMS clients have their own default encoding. Therefore they can work with one encoding, and the DBMS can translate on the fly before DB inserts.


"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott
 
Posts: 1102 | Location: Toronto, Ontario | Registered: May 26, 2004Report This Post
Member
posted Hide Post
thank you for the insights
 
Posts: 15 | Registered: October 17, 2012Report This Post
Member
posted Hide Post
thank you for your thoughts on this.
 
Posts: 15 | Registered: October 17, 2012Report This Post
Virtuoso
posted Hide Post
I realize that my answer was very simple, considering the subject matter can appear very complex at times. I've done a lot of work with mixed encodings in WF and DM environments. If you have issues, just post the specifics and I'll do my best to address them.


"There is no limit to what you can achieve ... if you don’t care who gets the credit." Roger Abbott
 
Posts: 1102 | Location: Toronto, Ontario | Registered: May 26, 2004Report This Post
Member
posted Hide Post
This was a condition I uncovered with a reporting group. They had been reporting with a non-Unicode adapter from a Unicode database.
 
Posts: 15 | Registered: October 17, 2012Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [CLOSED]reading an Oracle Unicode database with a non-unicode database adapter.

Copyright © 1996-2020 Information Builders