Export - File Character Set list is empty

Running version 1.6.1.00.02 on Oracle 10g. We are having problems moving a particular application into our production environment. Getting a parsing error. Doing some research - noticed that others have experienced similar issues - some threads have suggested making sure that the character set choices between export and import are the same. I've noticed that whenever we import, we must pick the character set. However, when exporting, the File Character Set list is empty - actually there's no type of drop down control present. Is this an issue?

PLSQL_GATEWAY = WebDb
GATEWAY_IVERSION = 3
SERVER_SOFTWARE = Oracle-Application-Server-10g/9.0.4.1.0 Oracle-HTTP-Server
GATEWAY_INTERFACE = CGI/1.1
SERVER_PORT = 7777
SERVER_NAME = ret6f001.svr.bankone.net
REQUEST_METHOD = POST
PATH_INFO = /wwv_flow.accept
SCRIPT_NAME = /pls/htmldb
REMOTE_ADDR = 172.28.176.77
SERVER_PROTOCOL = HTTP/1.0
REQUEST_PROTOCOL = HTTP
REMOTE_USER = htmldb_public_user
HTTP_CONTENT_LENGTH = 500
HTTP_CONTENT_TYPE = application/x-www-form-urlencoded
HTTP_USER_AGENT = Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
HTTP_HOST = reports.finone.bankone.net:7777
HTTP_ACCEPT = image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-powerpoint, application/vnd.ms-excel, application/msword, LL5.1.0.469, application/x-shockwave-flash, */*
HTTP_ACCEPT_LANGUAGE = en-us
HTTP_REFERER = http://reports.finone.bankone.net:7777/pls/htmldb/f?p=4500:3:5981935966734062333::NO:3::
HTTP_ORACLE_ECID = 1129981032:155.180.226.114:17023:0:28697,0
WEB_AUTHENT_PREFIX =
DAD_NAME = htmldb
DOC_ACCESS_PATH = docs
DOCUMENT_TABLE = wwv_flow_file_objects$
PATH_ALIAS =
REQUEST_CHARSET = US7ASCII
REQUEST_IANA_CHARSET = US-ASCII
SCRIPT_PREFIX = /pls
HTTP_COOKIE = ORACLE_PLATFORM_REMEMBER_UN=E009491:INFORMATION_ONE; WWV_FLOW_USER2=6B0BDED178928680; eSource40=403SPI|Jeffrey Truck|E009491|NA|CFS|AF|none|BANK1; PhoneBk=ID4=171272&ID2=750271&ID9=26009&ID15=531583&ID7=499247&ID14=491993&ID5=211422&ID13=544129&ID3=524989&ID12=542210&ID1=568789&ID8=235884&ID11=218896&ID6=571979&ID10=84550; SITESERVER=ID=6e4810d34113245334c55f6841924372; RETAILCOOKIE=; Yellow=PrevID6=&PrevID1=&PrevID8=&PrevID4=&PrevID10=&PrevID2=&PrevID9=&PrevID11=&PrevID0=1698&PrevID7=&PrevID12=&PrevID5=&PrevID13=&PrevID3=&PrevID14=

Similar Messages

What Determines the "File Character Set" on Export?

When we Export a Page, for example, from APEX, the File Character Set is defaulted to some value (and not editable). On some of our instances, this defaults to "Western European Windows 1252" while on others it is "Unicode UTF-8." Specifically, what setting is being used to make this determination? This is kind of a pain because we have some environments wherein we are promoting changes from environment to environment and these settings differ. If, during import, the user neglects to set this to the same File Character Set in which the file was originally exported, we get issues (non-printable control characters and the like). Therefore, we'd love to make all of the environments match but, aren't sure how to do this.
Thanks,
-Joe
Edited by: Joe Upshaw on Apr 10, 2013 3:25 PM

Hello Joe,
In your environment, the character set of the APEX exported files is set according to the DAD character set, and with your APEX version, it must be set to AL32UTF8 (regardless of the database character set).
Re: Export - File Character Set list is read only (fixe UTF-8 value)
You should check the DAD character set setting in the environments in which APEX is not exporting the files using UTF8.
Regards,
Arie.
&diams; Please remember to mark appropriate posts as correct/helpful. For the long run, it will benefit us all.
&diams; Author of Oracle Application Express 3.2 – The Essentials and More

Write XML to file - character set problem

I have a package that generates XML from relational data using SQLX. I want to write the resulting XML to the unix file system. I can do this with the following code :
DECLARE
v_xml xmltype;
doc dbms_xmldom.DOMDocument;
BEGIN
v_xml := create_my_xml; -- returns an XMLType value
doc := dbms_xmldom.newDOMDocument(v_xml);
dbms_xmldom.writeToFILE(doc, '/mydirectory/myfile.xml');
END;
This creates the file but characters such å,ä and ö are getting 'corrupted' and the resultant xml is invalid.(I've checked the xml within SQL*Plus and the characters are OK)
I assume the character set of the unix operating system doesn't support these characters. How can I overcome this ?

Hi,
Do you mean that you would like to write output to an external file somewhere on flask disk or perhaps even inside the directory where the MIDlet is located?? To be able to do so you will need manufacturere specific APIs extended on FileConnection (=JSR, don't know the number right now...). The default MIDP I/O libary does not support direct action on a file.
However, such a FileConnection method invocation requires an import statement that is manufacturere specifc...
To keep your MIDlet CLDC MIDP compliant you can try using RMS with which you can write data that will be stored in a 'database' within the 'res' directory inside your MIDlet suite. If you're new to RMS, please check the web for tutorials, etc etc.
Cheers for now,
Jasper

Error During INSTALL of Application Export File

An error is reported during INSTALL of an application that I am trying to copy (Import/Install) from a "development" Work Space into a "production" Work Space. The production (target) Work Space is on the same HTML DB instance as the development Work Space.
I am receiving the following INSTALL error:
ORA-20001: GET_BLOCK Error. ORA-20001: GET_STMT error. ORA-20001: Execution of the statement was unsuccessful. ORA-06550: line 15, column 1: PLS-00103: Encountered the symbol &quot;,'39','RD8','8','S','10','U','43','UD','41','UG','11','W')) END)&quot; when expecting one of the following: . ( * @ % &amp; = - + ; &lt; / &gt; at in is mod remainder not rem &lt;an exponent (**)&gt; &lt;&gt; or != or ~= &gt;= &lt;=
Following is some pertinent (hopefully) information:
The above INSTALL error takes exception to part of a Region Select (sql) that works fine in the development Work Space.
The common HTML DB (v1.6) instance is on UNIX.
A new Work Space was created on the same instance.
A new schema name was created during creation of the new Work Space. However, this schema does not point to a database. (We were not certain how to setup the schema to parse to our live database.) I will be running DBLINK upon production application startup in order to access the database objects.
EXPORT INFO -
File Format: UNIX (also, tried DOS but received same error during INSTALL)
IMPORT INFO -
File Type: Application/Page Export
File Character Set: Western European Windows 1252
Target Work Space is newly created on the same HTML DB instance.
INSTALL INFO -
*Parse As Schema: COLLIVE17 (Again, this schema does not parse to a database. I intend to use DBLINK.)
*Build Status: Run and Build Application
Please refer to above error message.
Again, any insights or suggestions are appreciated.

Urgently need help! I've read several other Forum messages having a related problem but none having same Install error message.
Again, my Export/Import from development Workspace to production Workspace is successful. The following error is reported when I attempt to "Install" into the production Workspace:
ORA-20001: GET_BLOCK Error. ORA-20001: GET_STMT error. ORA-20001: Execution of the statement was unsuccessful. ORA-06550: line 15, column 1: PLS-00103: Encountered the symbol &quot;,'39','RD8','8','S','10','U','43','UD','41','UG','11','W')) END)&quot; when expecting one of the following: . ( * @ % &amp; = - + ; &lt; / &gt; at in is mod remainder not rem &lt;an exponent (**)&gt; &lt;&gt; or != or ~= &gt;= &lt;=
The "snippet" of Region Sql Select code that relates to the reported error is:
ELSE htmldb_item.display_and_save (5, DECODE (GET_GRADE_B93 (sac.stc_final_grade,sac.stc_verified_grade),'18','AU','1','A','3','B','4','C','7','CR','5','D','46','DR','6','F','47','FW','49','IB','30','IC','31','ID','23','IF','44','MW','9','NC','21','RD','14','RD0','33','RD1','32','RD2','34','RD3','35','RD4','36','RD5','37','RD6','38','RD7','39','RD8','8','S','10','U','43','UD','41','UG','11','W'),'GRADE_'||ROWNUM) END q_v_grade,
HTML DB version is: 1.6.0.00.67. I've also tried to Export/Import/Install the application into the "same" Workspace specifying the same schema, and only changing the Application ID. However, I get the same Install error (see above).
Any suggestions on things to try in order to get application into production is greatly appreciated.
Thanks, Bernard.

CHARACTER SET CONVERSION PROBLEM BETWEEN WIN XP (SOURCE EXPORT) AND WIN 7

Hi colleagues, please assist:
I have a laptop running win 7 professional. Its also running oracle database 10g release 10.2.0.3.0. I need to import a dump into this database. The dump originates from a client pc running win XP and oracle 10g release 10.2.0.1.0 When i use the import utility in my database(on the laptop), the following happens:
Import: Release 10.2.0.3.0 - Production on Tue Nov 9 17:03:16 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Username: system/password@orcl
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options
Import file: EXPDAT.DMP > F:\uyscl.dmp
Enter insert buffer size (minimum is 8192) 30720>
Export file created by EXPORT:V08.01.07 via conventional path
Warning: the objects were exported by UYSCL, not by you
import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
export client uses WE8ISO8859P1 character set (possible charset conversion)
export server uses WE8ISO8859P1 NCHAR character set (possible ncharset conversion)
List contents of import file only (yes/no): no >
when i press enter, the import windows terminates prematurely without completing the process. What should i do to fix this problem?

Import: Release 10.2.0.3.0 - Production on Fri Nov 12 14:57:27 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Username: system/password@orcl
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options
Import file: EXPDAT.DMP > F:\Personal\DPISIMBA.dmp
Enter insert buffer size (minimum is 8192) 30720>
Export file created by EXPORT:V10.02.01 via conventional path
import done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
List contents of import file only (yes/no): no >
Ignore create error due to object existence (yes/no): no >
Import grants (yes/no): yes >
Import table data (yes/no): yes >
Import entire export file (yes/no): no >
Username:

Bad export file

Hello,
I have a problem exporting my applicaton. After exporting (file format:DOS, build status: run & bild, debugging:yes, export object definition:yes, export comments:yes, file character set: Unicode UTF-8) I get file wich is not complete. It's simply broken before logical end of normal export file. Appex version is 3.1.2.00.02 . Here is the end of my export file:
--application/shared_components/security/authentication/hera_auth_scheme
prompt ......scheme 22865111567649335
begin
declare
s1 varchar2(32767) := null;
s2 varchar2(32767) := null;
s3 varchar2(32767) := null;
s4 varchar2(32767) := null;
s5 varchar2(32767) := null;
begin
s1 := null;
s2 := null;
s3 := null;
s4:=s4||'return pck_apex.custom_auth'||chr(10)||
s5 := null;
wwv_flow_api.create_auth_setup (
p_id=> 22865111567649335 + wwv_flow_api.g_id_offset,
p_flow_id=> wwv_flow.g_flow_id,
p_name=> 'HERA_AUTH_SCHEME',
p_description=>'auth. sch.',
p_page_sentry_function=> s1,
p_sess_verify_function=> s2,
p_pre_auth_process=> s3,
p_auth_function=> s4,
p_post_auth_process=> s5,
p_invalid_session_page=>'101',
p_invalid_session_url=>'',
p_cookie_name=>'',
p_cookie_path=>'',
p_cookie_domain=>'',
p_ldap_host=>'',
p_ldap_port=>'',
p_ldap_string=>'',
p_attribute_01=>'',
p_attribute_02=>'wwv_flow_custom_auth_std.logout?p_this_flow=&APP_ID.&p_next_flow_page_sess=&APP_ID.:101',
p_attribute_03=>'',
p_attribute_04=>'',
p_attribute_05=>'',
p_attribute_06=>'',
p_attribute_07=>'',
p_attribute_08=>'',
p_required_pa
Did somebody have such a problem and resolve them?
Thanks

Scott,
that's complete dads.conf file:
# ============================================================================
# mod_plsql DAD Configuration File
# ============================================================================
# 1. Please refer to dads.README for a description of this file
# ============================================================================
# Note: This file should typically be included in your plsql.conf file with
# the "include" directive.
# Hint: You can look at some sample DADs in the dads.README file
# ============================================================================
Alias /i/ "C:/oracle/http/Apache/images/"
AddType text/xml xbl
AddType text/x-component htc
<Location /pls/apex>
Order deny,allow
PlsqlDocumentPath docs
AllowOverride None
PlsqlDocumentProcedure wwv_flow_file_mgr.process_downloadd
PlsqlDatabaseConnectString appserver:1521:orcl ServiceNameFormat
PlsqlNLSLanguage AMERICAN_AMERICA.AL32UTF8
PlsqlAuthenticationMode Basic
SetHandler pls_handler
PlsqlDocumentTablename wwv_flow_file_objects$
PlsqlDatabaseUsername APEX_PUBLIC_USER
PlsqlDefaultPage apex
PlsqlDatabasePassword my_pwd
PlsqlRequestValidationFunction wwv_flow_epg_include_modules.authorize
Allow from all
</Location>
Ivica

Import error due to character set difference?

hi,
hoping anyone to explain reason for the following import error.
here's the situation,
- export client used WE8MSWIN1252 charset (release v10.02.01)
- import server used WE8ISO8859P1 charset (release v10.1.0.4)
all tables appeared to be imported without error, except that import terminated unsuccesfully due to oracle error 2248
"ALTER SESSION SET PLSQL_OPTIMIZE_LEVEL =1 NLS-LENGTH_SEMANTICS = 'BYTE' PLSQL_CODE_TYPE = 'INTERPRETED' PLSQL_DEBUG = FALSE PLSQL_WARNING = 'DISABLE:ALL' PLSQL_CCFLAGS =''"
ORA-02248: invalid option for ALTER SESSION
was error due to the difference release version? char set conversion to non superset?
appreciate any help pls

It is difficult to say what is the current state of the database, so it is recommended to reexport and reimport the object definitions. You may miss some other stuff like object types, contraints, etc. Table data should be OK, so reexport should not include data.
As far as character sets are concerned, because of the difference between the export client character set and the import server character set, you may have lost some characters in the code range 0x80-0x9f. This includes Euro sign, TM, sign, "smart" quotes, en- and em-dash, etc. Use the Windows charmap.exe to see all the codes. If you have some of these codes in the source database, you have lost them on import (they got converted to the reverse quotation mark code 0xbf).
-- Sergiusz

Essbase 9.3.3 - data export files

Hi
I know when creating exports in Essbase when a file reaches 2gb Essbase will automatically generate a new file of the same and append the extension _1 to the name. I'm trying to find out if there is a way to control where the split happens. At the moment when I open the second file it starts halfway through a data line and then the header row appears about 80 rows down into the file. This means I get issues when trying to load this file into another cube using a load rule.
These are the settings I have at the top of my export file.
SET LOCKBLOCK HIGH;
SET UPDATECALC OFF;
SET AGGMISSG ON;
SET NOTICE DEFAULT;
SET MSG SUMMARY;
SET CACHE HIGH;
SET CALCPARALLEL 3;
SET EMPTYMEMBERSETS ON;
SET CREATEBLOCKONEQ OFF;
SET CREATENONMISSINGBLK OFF;
SET FRMLBOTTOMUP ON;
SET DATAEXPORTOPTIONS
DataExportLevel LEVEL0;
DataExportDynamicCalc OFF;
DataExportDecimal 6;
DataExportPrecision 16;
DataExportColFormat ON;
DataExportColHeader "Synapse Pipeline Stage";
DataExportDimHeader ON;
DataExportRelationalFile OFF;
DataExportOverwriteFile ON;
DataExportDryRun OFF;
Thanks in advance for any help.

Could you not break up the export into multiple exports to bring the file size down to less than 2GB, then load the multiple exports into your target database.
Cheers
John
http://john-goodwin.blogspot.com/

Data load uses wrong character set, where to correct? APEX bug/omission?

Hi,
I created a set of Data Load pages in my application, so the users can upload a CSV file.
But unlike the Load spreadsheet data (under SQL Workshop\Utilities\Data Workshop), where you can set the 'File Character Set', I didn't see where to set the Character set for Data Load pages in my application.
Now there is a character set mismatch, "m³/h" and "°C" become "m�/h" and "�C"
Where to set?
Seems like an APEX bug or at least omission, IMHO the Data Load page should ask for the character set, as clients with different character sets could be uploading CSV.
Apex 4.1 (testing on the apex.oracle.com website)

Hello JP,
Please give us some more details about your database version and its character set, and the character set of the CSV file.
>> …But unlike the Load spreadsheet data (under SQL Workshop\Utilities\Data Workshop), where you can set the 'File Character Set', I didn't see where to set the Character set for Data Load pages in my application.
It seems that you are right. I was not able to find any reference to the (expected/default) character set of the uploaded file in the current APEX documentation.
>> If it's an APEX omission, where could I report that?
Usually, an entry on this forum is enough as some of the development team members are frequent participants. Just to be sure, I’ll draw the attention of one of them to the thread.
Regards,
Arie.
&diams; Please remember to mark appropriate posts as correct/helpful. For the long run, it will benefit us all.
&diams; Author of Oracle Application Express 3.2 – The Essentials and More

Sql Developer 3.1 - Exporting a result set in xls generates and empty file

Ever since upgrading to the Production version SQL Developer 3.1 (3.1.07) it appears that there is an issue when attempting to export a result set as a .xls format.
If I attempt to export in .xls format, the exported file is an empty file (i,e no output). When I change the export type to txt, csv or xlsx the results are exported as expected.
This appears to be a bug introduced in the Production version as I was successfully able to perform these tasks on the various 3.1 EA releases.
Am I alone in this, have I misconfigured something or is this a bug?

I keep having problems exporting to XLSX - mostly in cases where the data is voluminous and the format would be preferable over plain XLS as it does not have the 65krows limit ;-{ The data is read to the data grid (sometimes fast, sometimes much slower and "in chunks"), then the "task progress" won't move anymore, and the export file remains empty; If I cancel the task, trying to export again results in a message stating that sqldeveloper still has the output file locked.

Finding the character set of the export dump file

I have an export dump, I don't have the log file for that export dump. How do I check the character set it had been exported in ?

878226 wrote:
Connected to: Oracle8i Enterprise Edition Release 8.1.7.4.1 - Production
With the Partitioning option
JServer Release 8.1.7.4.1 - Production
Export file created by EXPORT:V08.01.07 via conventional path
Warning: the objects were exported by IN, not by you
import done in WE8ISO8859P1 character set and WE8ISO8859P1 NCHAR character set
export server uses UTF8 NCHAR character set (possible ncharset conversion)
Hence, here UTF8 is the characterset used? Is that ri8?Yes that is correct.

Character set in MDL export/import

Hi,
we are running OWB 10.1.0.2. In order to get version control, we perform MDL exports of collections from our development environment and then import them into our test and production environments. Each environment uses its own design repository, but all repositories are in the same database.
When doing an export of a collection, we always specify the character set AL32UTF8 because that is what we are running in the repository database. When later doing an import using the graphical user interface, it is not possible to specify the character set (but this can be done when using the import utility). According to the documentation, the GUI import will then assume that the character set in the collection is the character set of the client, which usually is WE8MSWIN1252. (The documentation also says that it IS possible to specify the character set during GUI import, this is obviously a documentation error).
My questions are: What is the point of specifying character set when doing exports and imports? Could an AL32UTF8 export followed by an WE8MSWIN1252 import cause problems? I assume that the character set used by export is specified in the collection file, so does the import then convert it to WE8MSWIN1252 (or the character set specified in the import utility)?
Or, to be more general: What is actually happening with the character sets during MDL export/import?
/Kjell Gullberg

Dear ski123,
I think you are not going to loose any data of yours when you migrate the database. You may proceed to the import.
Please find below documentations;
http://download.oracle.com/docs/cd/B19306_01/server.102/b14196/install003.htm#sthref81
For Database Character Set, select from one of the following options:
    *Use the Default—Select this option if you need to support only the language currently used by the operating system for all your database users and your database applications.
    *Use Unicode (AL32UTF8)—Select this option if you need to support multiple languages for your database users and your database applications.
    *Choose from the list of character sets—Select this option if you want the Oracle Database to use a character set other than the default character set used by the operating system.Choosing a Character Set;
http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/ch2charset.htm#NLSPG002
AL32UTF8;
http://download.oracle.com/docs/cd/B19306_01/server.102/b14225/glossary.htm#sthref2039
Hope That Helps.
Ogan

[BUG] Exporting to xls and xlsx produces empty file

When I'm viewing a table with data, and in Actions choose "Export...", turn off "Export DDL", choose "xls" for format, everything else is on default, and either leave empty or enter same name for both Query and Data worksheet names, and specify filter query - export produces empty xls/xlsx file. Only when one explicitly enters different worksheet names does valid non-empty excel workbook get generated with two differently named worksheets.
Either validation should be added for worksheet names, or generating them automatically on export should be supported.
I'm using Oracle SQL Developer 3.1.07.
Kind regards,
Stevo.

Hi Stevo,
Really appreciate you reporting this. There was an earlier, somewhat similar thread on this issue that we blamed on export file size:
Sql Developer 3.1 - Exporting a result set in xls generates and empty file
But you have discovered an important variation that explains it for small export file sizes also. Here is what I verified on 3.1.07.42:
1. Normally if the worksheet names are left untouched (empty), then the names default to Export Worksheet and SQL
2. If the name settings in Tools|Preferences|Database|Utilities|Export|Excel Format are null (empty), there is no problem
3. If the name settings are intentionally changed to a single blank character, then the problem you describe occurs.
So, you may wish to go to the preference settings and intentionally Backspace over each to null it out, then click OK.
In the case of intentionally setting both worksheet names, data and query, to the same non-null value, that is also a problem.
Regards,
Gary
SQL Developer Team
Edited by: Gary Graham on Apr 17, 2012 11:55 AM
Logged a bug for this:
Bug 13971991 - FORUM: EXCEL FILE EMPTY IF DATA AND QUERY WORKSHEETS ARE THE SAME AND NON-NULL
Edited by: Gary Graham on May 25, 2012 2:00 PM
Notification received: fixed for 3.2

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.

B2B Validation contains characters not listed in the allowed character set

Hi,
Working on EDIFACT AS2 INVOIC D05A. B2B 10g with Document Editor Version: 6.6.0.2801
payload:
UNA:+.?*'
UNB+UNOB:4::1+A1103206+XXTPHOME+20110413:0456+30000000000545'
UNH+30000000000545+INVOIC:D:05A:UN'
BGM+389+5100256812'
DTM+137:20110413:102'
DTM+143:201104:610'
FTX+CUR+++Consignment stock accounting'
RFF+AOG:0'
NAD+BY+A1103206::234++XXXXXXXXX++81379+DE'
RFF+VA:DE260978148'
CTA+PD+GC SSC ARP:Yyyy Xxxx'
COM+49(2871) 91 3481:TE'
[email protected]:EM'
NAD+SU+A1082156::234++XXXXX:::[email protected]+Nnnnn 7+Llll+DE-BY+90443+DE'
RFF+VA:DE256058056'
NAD+UC+0000000100::92++Gggg Gggg:Hhhh+Kkkkk 2+Bocholt++46395+DE'
TAX+7+VAT:::19% VAT+DE:133:86++:::19.00'
CUX+2:EUR:4'
LIN+000001++UAA3595HN/C3:VP'
PIA+1+A5B00075796235:BP'
IMD+B++:::IC DECTUAA3595HN/C3 PA V20810C6323D:670'
QTY+47:6000.000:PCE'
MOA+203:660.00'
CUX'
I try to validate payload and get 2 errors:
1. Segment COM type an min length 1 max length 512 payload value: [email protected]
Error: ub-Element COM010-010 (Communication address identifier) contains characters not listed in the allowed character set. Segment COM is defined in the guideline at position 0350.
2. Segment group 27 Sub Element CUX payload value is null, value is exists at header level (Group 7 ub-Element CUX)
Error: Unrecognized data was found in the data file as part of Loop Group 27. The last known Segment was MOA at guideline position 1260 - Validator error - Extra data was encountered.
Thanks for any help
Adi

We fix it by change Character set to UNOC

Export - File Character Set list is empty

Similar Messages

Maybe you are looking for