Reports character set

I create report using 9iDS with data in English and Russian.
When i run report on a server, html page do not display correctly Russian data.
If I look source code of that html-page it contains tag "charset=iso-8859-5".
I have 9iAS R2 and custom database 8.1.7.
Database has parameter:
NLS_CHARACTERSET=CL8ISO8859p5
and iAS has NLS parameters set:
NLS_LANG=RUSSIAN_CIS.CL8ISO8859p5
USER_NLS_LANG=RUSSIAN_CIS.CL8ISO8859p5
DEVELOPER_NLS_LANG=RUSSIAN_CIS.CL8ISO8859p5
REPORTS_NLS_XML_CHARSET=CL8ISO8859P5
Configuration files for reports server include string "encoding=iso-8859-5" or "default_charset=iso-8859-5"
How can I tuning Reports Server for a correct work with character set CL8ISO8859p5???

It looks like you're hitting a known bug, which is addressed in the first patch set. This is planned to be available towards the end of October - check on Metalink.
Thanks,
Danny

Similar Messages

Trouble with MSSQL Reporting Services and Oracle: PLS-00553: character set

First off, Oracle version is 8.1.7.4.0. SQL is 64bit 2005 on Windows 2003 with all the latest patches. We’re using the Oracle 10.2 client on the SQL box.
A few months ago queries against Oracle stopped working on our MSSQL reporting services server - after a service pack on this same system.
I ended up having to grant permissions on Oracle directories to eliminate the first error and then renamed the NLS_LANG registry entry (effectively deleting it) to get rid of the second error.
The second error was: ORA-12705: Cannot access NLS data files or invalid environment specified. I don’t have docs on the first error, but it was a reference to a file access problem. Looking at this error again makes me think that I still have some file access problems.
The old value for the NLS_LANG registry key was: AMERICAN_AMERICA.WE8MSWIN1252
Everything has been working fine since then.
Now we are moving some new reports into production which use Oracle stored procedures and they are getting this error:
--- End of inner exception stack trace ---
w3wp!processing!8!7/27/2009-09:26:09:: e ERROR: An exception has occurred in data source 'CSUD3_RPTAPL'. Details: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for data set 'MYDATASET'. ---> System.Data.OracleClient.OracleException: ORA-06550: line 1, column 57:
PLS-00553: character set name is not recognized
ORA-06550: line 0, column 0:
PL/SQL: Compilation unit analysis terminated
I've created a test package as below, which has also gotten the same error.
create or replace
PACKAGE BODY SQLTEST AS
PROCEDURE OPEN_CURSOR (ResultCursor OUT T_CURSOR,
SQLTESTIN IN VARCHAR
AS
l_query varchar2(3000);
BEGIN
l_query := 'Hi there';
open ResultCursor for select l_query "field1" from dual;
END OPEN_CURSOR;
END SQLTEST;
I tried setting the NLS_Lang value back to its old value, but it did not fix this problem – and made all the regular oracle queries break again.
From what I've read, the client should be using the database default if the charset is not specified on the client.
Can anyone advise on what the problem might be?
Thanks!
Sam Greene

With all due respects I can not think of a worse reporting tool than MS Reporting Services.
Give serious consideration to getting a real report writing tool from Oracle or SAP (Business Objects / Crystal).
Reporting Services is one nightmare after another.

Problem with character set - Reports 11.1.1.4

Hi!
I have a problem with Oracle Reports 11g regarding character set configuration. The default character set WE8ISO8859P1 works, so PDF reports have a regular display except for Eastern European (EE) letters which are replaced by "¿" sign.
So, when I set any other character set in reports.sh, which would be a normal step to get EE letters, I'm always getting Greek Alphabet in PDF reports. Why Greek Alphabet?
The character sets I tried to use are: EE8ISO8859P2, UTF8 and AL32UTF8.
I changed uifont.ali and included PDF Subset with all four Arial font variants and, of course, I placed all fonts in fonts folder which is pointed by REPORTS_FONT_DIRECTORY.
In Reports Builder everything works fine, but when I have to deploy the report to the Reports Services, the problem occurs.
Also, when I've tried to execute PDF report using In-Process Reports Server (rep_wls_reports_hostnameasinst1) instead of AS Instance Reports Server (RptSvr_hostnameasinst1, which is a regular server), I'm getting Greek Alphabet in PDF reports even if the default character set is WE8ISO8859P1 in reports.sh. What is wrong with it? Where is Greek Alphabet configured?
The production environment is 64-bit Oracle Linux 5.6 with Weblogic 10.3.4 and Forms&Reports 11.1.1.4. Forms works fine with character set EE8ISO8859P2 defined in default.env file.
Thanks in advance!
Regards,
Dejan

Thank you, Denis!
Doc 300416.1 was very useful but Note 356221.1 - A Practical Methodology on Porting Reports from Windows to Unix with Different Font is actually crucial for configuring Reports on Linux.
Also, there is a bug in 11.1.1.3 and 11.1.1.4, which can be fixed using the patch ( Note 1138405.1 - PDF Reports With Font Subsetting Raises Error "Bad /Bbox" on 64-Bit Linux ).
Kind regards!

National character set in JSP report

Hi. National character set is not seen in JSP reports, while in paper reports all is OK. What's the problem?

Hi Volodia,
You can set the character set inside the JSP as:
<%@ page contentType="text/html;charset=ISO-8859-1" %>
Change the character set to "utf-8" or an appropriate value.
Alternatively, in the web browser also, you can change the encoding (View > Encoding > ...)
Navneet.

How to change the Forms and Reports's NLS_LANG character set on OAS

Hi,
I'm having problems with the OAS10g's actual character set, when displaying a report made with Reports Builder 10g who has the letter "ñ" it displays "ñ " with a blank space at the final so i need to change this character set for one that suits this requirement.
which file or files should i change ??
could this change affect something else, for example another product in my OAS ??
Regards
Carlos

I have this Forms and Reports Application in Brazilian Potuguese. What I do at new installations is:
1. Open this file: <MiddlewareOracleHome>/forms/server/default.env and add the NLS parameters below the FORMS_PATH definition:
FORMS_PATH=D:\Oracle\home207middle\forms;D:\MYENV\Exe;D:\MYENV\Imagens
NLS_LANG=BRAZILIAN PORTUGUESE_BRAZIL.WE8MSWIN1252
NLS_NUMERIC_CHARACTERS=,.2. Open this file: <MiddlewareOracleHome>/reports/conf/<your_report_server_name>.conf and create an "environment" section with the NLS variables:
   <environment id="MYENV">
      <envVariable name="REPORTS_PATH" value="D:\MYENV\Exe;D:\MYENV\Imagens"/>
      <envVariable name="NLS_LANG" value="BRAZILIAN PORTUGUESE_BRAZIL.WE8MSWIN1252"/>
      <envVariable name="NLS_DATE_FORMAT" value="DD/MM/YYYY"/>
      <envVariable name="NLS_NUMERIC_CHARACTERS" value=",."/>
   </environment>For this one to work, the application must set RP2RROREPORTSENV=MYENV before launching the report.

Reports 9i and character set

We have reports in character set WINDOWS 1251
But iAS do they in UTF 8.
We tried to set character set in uifont.ali, but there was not effect.
How to change default character set from UTF8 to WINDOWS 1251 ?
Environment:
iAS 9i R2
nls_lang=AMERICAN.CL8MSWIN1251
uifont.ali:
COURIER....UTF8=COURIER....CL8MSWIN1251

Laura,
First, You can run the 6i reports with OGD in reports 9i, provided you have your Oracle 6i home is in system path
and the regsitry variable ORACLE_GRAPHICS6I_HOME is set to pint your 6i oracle home
Now, if you wan to open these 6i report with OGD and modify the report in 9i builder, then the OGDs are loast when saving this reports from 9i
buikder, so you would need to recreate the graphs using the graph wizard
Thanks
The Oracle Reports Team

Character set migration error to UTF8 urgent

Hi
when we migrated from ar8iso889p6 to utf8 characterset we are facing one error when i try to compile one package through forms i am getting error program unit pu not found.
When i running the source code of that procedure direct from database using sqlplus its running wihtout any problem.How can i migrate this forms from ar8iso889p6 to utf8 characterset. We migrated from databas with ar8iso889p6 oracle 81.7 database to oracle 9.2. database with character set UTF8 (windows 2000) export and import done without any error
I am using oracle 11i inside the calling forms6i and reports 6i
with regards
ramya
1) this is server side program yaa when connecting with forms i am getting error .When i am running this program using direct sql its working when i running compiling i am getting this error.
3) yes i am using 11 i (11.5.10) inside its calling forms 6i and reports .Why this is giving problem using forms.Is there any setting changing in forms nls_lang
with regards

Hi Ramya
what i understand from your question is that you are trying to compile a procedure from a forms interface at client side?
if yes you should check the code in the forms that is calling the compilation package.
does it contains strings that might be affected from the character set change???
Tony G.

Crystal XI R2 exporting issues with double-byte character sets

NOTE: I have also posted this in the Business Objects General section with no resolution, so I figured I would try this forum as well.
We are using Crystal Reports XI Release 2 (version 11.5.0.313).
We have an application that can be run using multiple cultures/languages, chosen at login time. We have discovered an issue when exporting a Crystal report from our application while using a double-byte character set (Korean, Japanese).
The original text when viewed through our application in the Crystal preview window looks correct:
性能著概要
When exported to Microsoft Word, it also looks correct. However, when we export to PDF or even RPT, the characters are not being converted. The double-byte characters are rendered as boxes instead. It seems that the PDF and RPT exports are somehow not making use of the linked fonts Windows provides for double-byte character sets. This same behavior is exhibited when exporting a PDF from the Crystal report designer environment. We are using Tahoma, a TrueType font, in our report.
I did discover some new behavior that may or may not have any bearing on this issue. When a text field containing double-byte characters is just sitting on the report in the report designer, the box characters are displayed where the Korean characters should be. However, when I double click on the text field to edit the text, the Korean characters suddenly appear, replacing the boxes. And when I exit edit mode of the text field, the boxes are back. And they remain this way when exported, whether from inside the design environment or outside it.
Has anyone seen this behavior? Is SAP/Business Objects/Crystal aware of this? Is there a fix available? Any insights would be welcomed.
Thanks,
Jeff

Hi Jef
I searched on the forums and got the following information:
1) If font linking is enabled on your device, you can examine the registry by enumerating the subkeys of the registry key at HKEY_LOCAL_MACHINEu2013\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontLink\SystemLink to determine the mappings of linked fonts to base fonts. You can add links by using Regedit to create additional subkeys. Once you have located the registry key that has just been mentioned, from the Edit menu, Highlight the font face name of the font you want to link to and then from the Edit menu, click Modify. On a new line in the dialog field "Value data" of the Edit Multi-String dialog box, enter "path and file to link to," "face name of the font to link".u201D
2) "Fonts in general, especially TrueType and OpenType, are u201CUnicodeu201D.
Since you are using a 'true type' font, it may be an Unicode type already.However,if Bud's suggestion works then nothing better than that.
Also, could you please check the output from crystal designer with different version of pdf than the current one?
Meanwhile, I will look out for any additional/suitable information on this issue.

Problem with Character Set after upgrade

Hello,
I have a probelm and was wondering if anyone has seen this before.
I have been running Java 1.4.2_13 for a while now on some Windows servers. About a month ago we upgraded to Java 1.6.0_12.
We are reading input files that are in the character set Big5 HKSCS. After the upgrade our application started to report certain characters as invalid. Some of the characters are 0xD843, 0xD844.
These should be valid characters and were in the previous version of Java (1.4.2_13).
Has anyone seen this?
Thanks in advance,
Jerry

The [Supported Encodings|http://java.sun.com/javase/6/docs/technotes/guides/intl/encoding.doc.html] page for the Java 6 release describes that charset as
Big5 with Hong Kong extensions, Traditional Chinese (incorporating 2001 revision)You would know more than I do about that 2001 revision (or at least, not less than I do, since I know nothing about it). Perhaps that's the source of your problem?
Edit: especially since the [Supported Encodings|http://www.j2ee.me/j2se/1.4.2/docs/guide/intl/encoding.doc.html] page for Java 1.4 doesn't mention the 2001 revision.

Oracle to MySql character set problem

Dear Gurus,
My database is Oracle 11g R2 (11.2.0.1.0) on Sun Solaris 10. To get data from mysql database for reporting purpose, I used DG4ODBC and followed strictly the OMSC note "Detailed Overview of Connecting Oracle to MySQL Using DG4ODBC Database Link [ID 1320645.1]. Here are main configuration steps:
- Check DG4ODBC 32/64-bit
- Install and configure ODBC Driver Manager unixodbc-2.2.14
- Install and configure MyODBC 5.1.8
- Configure tnsnames.ora and listener.ora
- Create db links
Oracle character set is AL32UTF8
MySQL charactoer set is uft8
$ODBC_HOME/etc/odbc.ini
[ODBC Data Sources]
myodbc5 = MyODBC 5.1 Driver DSN
[myodbc5]
Driver = /opt/mysql/myodbc5/lib/libmyodbc5.so
Description = Connector/ODBC 5.1 Driver DSN
SERVER = <mysql server ip>
PORT = 3306
USER = <mysql_user>
PASSWORD = ****
DATABASE = <mysql db name>
OPTION = 0
TRACE = OFF
$ORACLE_HOME/hs/admin/initmyodbc5.ora
# HS init parameters
HS_FDS_CONNECT_INFO=myodbc5 # Data source name in odbc.ini
HS_FDS_TRACE_LEVEL=OFF
HS_FDS_SHAREABLE_NAME=/opt/unixodbc-2.2.14/lib/libodbc.so
HS_FDS_SUPPORT_STATISTICS=FALSE
HS_LANGUAGE=AMERICAN_AMERICA.WE8ISO8859P1
# ODBC env variables
set ODBCINI=$ODBC_HOME/etc/odbc.ini
My issue is I can query data from mysql database tables but the output is incorrect in character type columns (VARCHAR columns). It just shows the first character in such columns. I tried to read through some OMSC notes but none is useful. If you experienced on such issues, please share your idea / help me resolve it.
Thanks much in advance,
Hieu

S. Wolicki, Oracle wrote:
I have little experience with MySQL and ODBC Gateway, but this setting looks weird to me: HS_LANGUAGE=AMERICAN_AMERICA.WE8ISO8859P1. Why do you configure WE8ISO8859P1 when both databases are Unicode UTF-8. Shouldn't the setting be AMERICAN_AMERICA.AL32UTF8 instead?
-- SergiuszIf I set HS_LANGUAGE=AMERICAN_AMERICA.AL32UTF8 or without the HS_LANGUAGE setting, the following error will happen.
SQL> select count(*) from "nicenum_reserve"@ussd;
select count(*) from "nicenum_reserve"@ussd
ERROR at line 1:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
I followed the metalink note "Error Ora-28500 and Sqlstate I Issuing Selects From a Unicode Oracle RDBMS With Dg4odbc To Mysql or SQL*Server [ID 756186.1]" to resolve the above error. The note guides to set HS_LANGUAGE=AMERICAN_AMERICA.WE8ISO8859P1 and resolved the above error.
The following are the output from original database (MySql) and Oracle via SQLPLUS and TOAD.
On MySQL database (Sorry because of the output format)
SQL> select ID, source_msisdn, target_msisdn, comment from nicenum_reserve where ID=91;
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| ID | source_msisdn | target_msisdn | comment |
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 91 | 841998444408 | 84996444188 | Close reservation becasue of swap activity |
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
SQLRowCount returns 1
1 rows fetched
Via Sqlplus on Oracle server:
SQL> select "ID","source_msisdn","target_msisdn","comment" from "nicenum_reserve"@ussd where "ID"=91;
ID
source_msisdn
target_msisdn
comment
91
8 4 1 9 9 8 4 4 4 4 0 8
8 4 9 9 6 4 4 4 1 8 8
C l o s e r e s e r v a t i o n b e c a s u e o f s w a p a c t i v i
t y
Via TOAD connected to Oracle server:
ID source_msisdn target_msisdn comment
91 8 8 C
It's likely this issue related to character set settings but I don't know how to set it properly.
Brgds,
Hieu

How to change character set to arabic in Develper suite forms 10g

Dear all,
Our company wants migrate oracle forms 4.5/6i applications to Oracle developer suite 10g version.
They also want there database to upgrade from 9i to 10g.
They gave me test machine, on which windows xp is installed and i did the following:-
1,Installed Oracle 10g Xe edition database.
2,Installed Oracle 10g Devloper suite(oracle forms, Oracle reports).
3, Configured the connection of Oracle Developer suite 10g to Oracle Database 10g.
4, Loaded Data into the 10g database. *( they are few columns like DEPARTMENT_NAME_ARB, FUNCTION_NAME_ARB which is supposed to show in arabic fonts, as it is in arabic in 9i database, now they are showing in some special characters)*
What I would like to know is: Is there a way through which i can set characterset?
Is it in the database in which i have to make character set change?
Is it in the oracle developer suite application in which i have to make character set change?
Is it in the registry in which i have to make changes?
please help.

Hi freinds,
It is very encouraging to see your replies, i apologize for the late reponse, i still got no success with updating PROPS$,
I relgiously followed all the instructions given to me by all of you. Like u could see in my previous posts
Luckiily, i am able to insert one row at a time manaually iin arabic and in english by pressing (ALT+SHIFT).
When i create datablocks in forms builder, i do see output in arabic.
When i create report in group style i do see ouptput in arabic.
i have thousands of rows(in GB's) which needs to be inserted in this new database 10g XE edition (downloaded from oracle)
I have attempted multiple times insertion of data by just running script, or simply copying numerous insert statement rows from notepad to sql*plus, unluckily it alwayz retreived the special charachters rather than retreiving arabic characters.
Is there a way to insert data in this new oracle 10g xe editon database via oracle developer suite 10g forms/reports?
Do I have to use inbuilt data load/unload utilities in oracle 10g xe edition?
Do I have to install sql*loader separately to load the data?
Do you think TOAD can help in this?
Could you please tell me how to add snap shots in this post?(user10947262)
Here are the following details of National Language Parameter Value
Before
NLS_CALENDAR     GREGORIAN
NLS_CHARACTERSET     AL32UTF8 (IS this multibyte (UTF-8) character set SARAH?)
NLS_COMP     BINARY
NLS_CURRENCY     $
NLS_DATE_FORMAT     DD-MON-RR
NLS_DATE_LANGUAGE     AMERICAN
NLS_DUAL_CURRENCY     $
NLS_ISO_CURRENCY     AMERICA
NLS_LANGUAGE     AMERICAN
NLS_LENGTH_SEMANTICS     BYTE
NLS_NCHAR_CHARACTERSET     AL16UTF16
NLS_NCHAR_CONV_EXCP     FALSE
NLS_NUMERIC_CHARACTERS     .,
NLS_SORT     BINARY
NLS_TERRITORY     AMERICA
NLS_TIMESTAMP_FORMAT     DD-MON-RR HH.MI.SSXFF AM
NLS_TIMESTAMP_TZ_FORMAT     DD-MON-RR HH.MI.SSXFF AM TZR
NLS_TIME_FORMAT     HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT     HH.MI.SSXFF AM TZR
After
NLS_CALENDAR     GREGORIAN
NLS_CHARACTERSET     AL32UTF8
NLS_COMP     BINARY
NLS_CURRENCY     ر.س.
NLS_DATE_FORMAT     DD/MM/RR
NLS_DATE_LANGUAGE     ARABIC
NLS_DUAL_CURRENCY     ر.س.
NLS_ISO_CURRENCY     SAUDI ARABIA
NLS_LANGUAGE     ARABIC
NLS_LENGTH_SEMANTICS     BYTE
NLS_NCHAR_CHARACTERSET     AL16UTF16
NLS_NCHAR_CONV_EXCP     FALSE
NLS_NUMERIC_CHARACTERS     .,
NLS_SORT     ARABIC
NLS_TERRITORY     SAUDI ARABIA
NLS_TIME_FORMAT     HH12:MI:SSXFF PM
NLS_TIMESTAMP_FORMAT     DD/MM/RR HH12:MI:SSXFF PM
NLS_TIMESTAMP_TZ_FORMAT     DD/MM/RR HH12:MI:SSXFF PM TZR
NLS_TIME_TZ_FORMAT     HH12:MI:SSXFF PM TZR
Certainly Christian, i dont want to screw my oracle 10g database xe edition software and installation, and i agree and hope with this that creating new database and doing exporting and importing will work for me. (XE edition doesnt give option to create new database, i need to install 10g release2 media pack from edelivery)
However, with the above informatiion provided, Is it really needed?
Please help me.
Thanks and Regards

Invalid Characters shown in UTF-8 character set

There is an XMLP report whose template output character set is ISO-8859-1. The character set ISO-8859-1 is required for this report as per Spanish Authorities. When the report is run, output gets generated in the output directory file of application server. This output file doesn't contain any invalid characters.
But when the output is opened from SRS window, which opens it in a browser, the invalid characters are shown for characters like Ñ , É etc.
Investigation done:
Found that the output generated on the server is having ISO encoding and hence doesn't contain any invalid characters. Whereas the output generated from SRS window, it is in UTF encoding, so it seems the invalid characters are displayed when conversion takes place from ISO to UTF-8 format.
Created the eText output using the data xml and template using BI publisher tool, the output is in ISO encoding. So if i go and change the encoding to UTF-8 by opening it in explorer or Notepad++, invalid charcters are shown for Ñ, É etc.
Is there any limitation, that output from SRS window will show only in UTF-8 encoding? If not then please suggest.
Thanks,
Saket
Edited by: 868054 on Aug 2, 2012 3:05 AM
Edited by: 868054 on Aug 2, 2012 3:05 AM

Hi Srini,
When customer is viewing output from the SRS window, then it contains invalid characters because it is in UTF-8 character set. Customer is on Oracle OnDemand so they cannot take the output generated on the server.Every time they have to raise a request to Oracle for the output file. So the concern here is, why don't the output from SRS window show output with valid characters ?
The reason could be conversion of ISO format to UTF-8. How could this be resolved ? Does SRS window output cannot generate in ISO format ?
A quick reply will be appreciated as customer is chasing for an update.
Thanks,
Saket
Edited by: 868054 on Aug 7, 2012 11:08 PM

How to Change National character set for a database

Hi All,
My database is Oracle 10G. Stand alone DB.
National character set for my DB is "WE8ISO8859P1" and need to change national character set to UTF8.
Need Help on this.
Thanks in advance.
Regards,
Suresh

Please go through the topic,
[http://arjudba.blogspot.com/2009/02/what-is-national-character-set.html|http://arjudba.blogspot.com/2009/02/what-is-national-character-set.html] [http://arjudba.blogspot.com/2009/03/unicode-characterset-in-oracle-database.html|http://arjudba.blogspot.com/2009/03/unicode-characterset-in-oracle-database.html]
and decide whether you need migration . If you need migration then have a look at,
[http://arjudba.blogspot.com/2009/03/difference-between-we8mswin1252-and.html|http://arjudba.blogspot.com/2009/03/difference-between-we8mswin1252-and.html]
[http://arjudba.blogspot.com/2009/03/difference-between-we8iso8859p1-and.html|http://arjudba.blogspot.com/2009/03/difference-between-we8iso8859p1-and.html]
[http://arjudba.blogspot.com/2009/03/difference-between-we8iso8859p1-and_11.html|http://arjudba.blogspot.com/2009/03/difference-between-we8iso8859p1-and_11.html]
And always check for reports in csscan.
Edited by: user9533551 on 07-Jul-2009 04:29

Are there any plans to fix the misinterpretation of the Exchange ActiveSync policy "Minimum number of character sets" in IOS5?

We are testing using IOS5 in our Corporate environment and came across a scenario where IOS5 incorrectly interprets the Exchange 2010 ActiveSync policy "Minimum number of character sets" as the number of special characters required rather than the number of character sets required. Is anyone aware of any plans to correct this in future releases? Here is a thread on Microsoft's forums about the issue:
http://social.technet.microsoft.com/Forums/en-US/exchangesvrmobility/thread/fe05 1d55-24ba-45e4-b054-67861f28422d/

Thanks for the responses. I did submit this issue as a bug report earlier this morning also but thought I'd post here in the event any Apple insiders saw this and cared to comment.
This really is a significant problem in that our testing shows that the way IOS5 interprets this ActiveSync policy in Exchange 2010 does not allow you to enforce a password using just letters and numbers. This is because the only valid values for this policy are 1-4. The way IOS5 interprets this requires 1-4 special characters in the password, not 1-4 character sets.

[8i] ORA-12704: character set mismatch (and other issues)

I've been trying to put together sample data on this problem since Friday, but I'm having issues. I'm thinking the problem is something specific to the old database I'm trying to work in:
BANNER
Oracle8i Enterprise Edition Release 8.1.7.2.0 - Production
PL/SQL Release 8.1.7.2.0 - Production
CORE    8.1.7.0.0       Production
TNS for HPUX: Version 8.1.7.2.0 - Production
NLSRTL Version 3.4.1.0.0 - ProductionI tried copying over all the data into my test database:
BANNER
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Product
PL/SQL Release 10.2.0.1.0 - Production
CORE    10.2.0.1.0      Production
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - ProductionAnd, I can't duplicate the problem there. In fact, I ran my original query in my test database, using the db llink, the query ran just fine.
But, I tried to create some sample data anyway to try to get some help here, so, I created 3 tables in my test database as SELECT from the old database (via a db link).
One table was really the results of a query (with many sub-queries) that was working just fine in the old database. It was the 2nd highest level query that wasn't giving me any problems. (Below, in my query, subquery 'a' runs just fine in the test database also; it's only the top level query that gives me an error.)
The other two tables I created were just simple sub-sets of the original tables in the old database.
I ran my query in my test database against those tables, and again, it ran just fine. No character set mismatch error.
So, based on the tables from the old database, I created the following test tables:
TEST TABLE DEFINITIONS
CREATE TABLE     test_inv_1
(     cust_id          CHAR(10)
,     item_id          VARCHAR2(32) -- becomes 96 if I create as select
,     match_item_id     CHAR(10)
,     docdate          DATE
,     tot_amt          NUMBER(5)
INSERT INTO     test_inv_1
VALUES('C1000','I0001','I0001',TO_DATE('01/01/2011','mm/dd/yyyy'),1000);
INSERT INTO     test_inv_1
VALUES('C1000','I0002','I0002',TO_DATE('01/05/2011','mm/dd/yyyy'),1050);
INSERT INTO     test_inv_1
VALUES('C1000','MANUAL ADJUSTMENT','MANUAL ADJ',TO_DATE('01/01/2011','mm/dd/yyyy'),1000);
INSERT INTO     test_inv_1
VALUES('C1001','I0003','I0003',TO_DATE('01/01/2011','mm/dd/yyyy'),500);
INSERT INTO     test_inv_1
VALUES('C1001','OTHER ADJUSTMENT','OTHER ADJU',TO_DATE('01/01/2011','mm/dd/yyyy'),50);
INSERT INTO     test_inv_1
VALUES('C1001','M123','M123',TO_DATE('01/10/2011','mm/dd/yyyy'),150);
CREATE TABLE     test_btab_1
(     billing_id          CHAR(10)     NOT NULL -- becomes 30
,     payment_terms_cd     CHAR(3)                -- becomes 9
INSERT INTO     test_btab_1
VALUES ('I0001', '01');
INSERT INTO     test_btab_1
VALUES ('I0002', '01');
INSERT INTO     test_btab_1
VALUES ('I0003', '02');
INSERT INTO     test_btab_1
VALUES ('M123', 'COD');
INSERT INTO     test_btab_1
VALUES ('I0004', '01');
CREATE TABLE     test_tabm_1
(     record_type     CHAR(4)          NOT NULL     -- becomes 12
,     record_key     CHAR(10)     NOT NULL     -- becomes 30
,     numeric_1     NUMBER(15,5)
,     numeric_5     NUMBER(7)
,     numeric_6     NUMBER(7)
INSERT INTO     test_tabm_1
VALUES ('LOCA','A1234',NULL,NULL,NULL);
INSERT INTO     test_tabm_1
VALUES ('TERM','01',2,10,30);
INSERT INTO     test_tabm_1
VALUES ('TERM','02',0,0,45);
INSERT INTO     test_tabm_1
VALUES ('TERM','COD',0,0,30);Again, the first table, test_inv_1, is an example of the results of a query that was working just fine in the old database. (There are comments in the table definitions above--I'll explain those in a bit.)
Here is the query I ran against this data:
QUERY
SELECT     a.*
,     1 - (t.numeric_1/100)          AS amt_pst_disc
,     a.docdate + t.numeric_5 - 1     AS disc_end_date
,     a.docdate + t.numeric_6 - 1     AS duedate
FROM     (
     SELECT     ic.*
     ,     CASE
               WHEN     b.payment_terms_cd     IS NULL
               THEN     CAST('03' AS CHAR(10))
               ELSE     CAST(b.payment_terms_cd AS CHAR(10))
          END                         AS pay_term
     ,     CASE
               WHEN     b.payment_terms_cd     IS NULL
               THEN     'Default Payment Terms'
          END                         AS pt_flag
     FROM     test_inv_1 ic
     ,     test_btab_1 b
     WHERE     ic.match_item_id     = b.billing_id (+)
     ) a
,     test_tabm_1 t
WHERE     a.pay_term     = t.record_key
AND     t.record_type     = 'TERM'
;In the old database, I get the error:
WHERE   a.pay_term      = t.record_key
ERROR at line 107:   --this is actually line 22 in the above query, since test_inv_1 represents the results of a sub-query
ORA-12704: character set mismatchIn my test database, in every form, including with the sample data above, I don't have any problems.
I unfortunately don't have a v8 test environment, and I suspect there aren't many people who actually do, anymore, so using my v10 test database is the best I can do to come up with test data...
The other odd thing I noticed is that when I DESC the tables I created in my test database via SELECT statements, and compare them with the tables I created from CREATE statements (based on the table descriptions I got from the old database), some of the data lengths don't match up. That's what's in the comments in my table definitions. I noted where the tables I created via SELECT statements had different data lengths. I'm not sure if it's important or not, but in case it is, I thought I'd include it.
Also, I'm creating this query to make a report for someone else, and the reporting system only has access to the v8 database, not my test database. So, I'm stuck making the query run against it.
Any help on this would be greatly appreciated!

I think it has something to do with my CASE statement. I found a kind of work-around solution. Instead of getting payment_term_cd associated with the item_id, the person I'm creating the report for wants the payment terms associated with the cust_id. Now, btab has the one associated with item_id, and not every item_id is in the btab table, so in my query, I was assuming a default value of '03' when it didn't find a payment_term_cd (i.e. it was NULL) for an item_id, which is what my first CASE statement is doing.
However, every cust_id definitely has a payment_term_cd associated with it (in another table I did not provide sample data for, since I didn't know I'd need to use it). Here's the general idea of that table:
CREATE TABLE     test_cust_1
(     cust_id               CHAR(10)     NOT NULL
,     payment_terms_cd     CHAR(3)     --while it's not specified as NOT NULL, there are no NULLs for this column. I think anything that would be NULL, the system initializes as '***'
INSERT INTO     test_cust_1
VALUES ('C1000','01');
INSERT INTO     test_cust_1
VALUES ('C1001','03');
INSERT INTO     test_cust_1
VALUES ('C1002','COD');So, there's no need for me to do a case statement. I can get away with something like:
SELECT     ip.item_id
,     ip.docdate
,     ip.cust_id
,     ip.tot_amt
,     ip.pay_terms
,     t.record_key
FROM     (
     SELECT     i.item_id
     ,     i.docdate
     ,     i.cust_id
     ,     i.tot_amt
     ,     CAST(c.payment_terms_cd AS CHAR(10))     AS pay_terms
     FROM     test_inv_1 i
     ,     test_cust_1 c
     WHERE     c.cust_id     = i.cust_id
     AND     i.tot_amt     <> 0
     ) ip
,     test_tabm_1 t
WHERE     t.record_key     = ip.pay_terms
AND     t.record_type     = 'TERM'-- edited out the incorrect results
Anyway, when I used this new table with my original query in the 8i database, I didn't get a character set error, so that's why I think it has to do with the case statement.
Edited by: user11033437 on Aug 22, 2011 1:43 PM -- fixed an error in my results

Reports character set

Similar Messages

Maybe you are looking for