Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Dim10: Trigger works but shows garbled information
Check the database being used if it is not US7ASCII (Dim 8 or 9)or the UTF8 standard on Dim 10. Then you will need to ensure that you are building the Multibyte characterset varaint of the trigger.
CMS-XML Dim10: TT/DM integration not working when TT database charset is US7ASCII
Dim10: TT/DM integration not working when TT database charset is US7ASCII
CMS-XML KM-Dim9: DBCS named items display corrupted characters with remote Oracle server.
Both server uses same language OS platform. e.g) Dimensions Server : Windows Server 2000 Japanese Remote Oracle Database : Windows Server 2003 Enterprise Edition Japanese (characterset: US7ASCII )
CMS-XML KM-Dim7: Upgrade from 7.0 to 7.1 - High Ascii characters are not shown correctly anymore
Filenames that had characters such as the copyright sign in them, appear as '?' characters after upgrading from 7.0 to 7.1. This problem seems to have occurred on installations that were installed with an Oracle Character Set other than US7ASCII .
CMS-XML KM-Dim7: Edit the install script to allow additional database character sets
In order to install with the WE8ISO8859P1 character set, you will need to edit the following section of the install script (once copied off the distribution CD): # echo " echo "The database character set US7ASCII does not fully support European"
CMS-XML DM2009R2 - Database characterset for service DIM10 unknown: UTF-8 assumed" error
Expected Result This error should not occur because the characterset is US7ASCII : SQL> select * from dm_characterset;
CMS-XML Dim10: Recommendations/Information pertaining to Oracle Character Sets
For upgrades, usually t he US7ASCII multi-byte character set will be listed. This is a subset of the AL32UTF8 unicode character set, which means it can handle a much broader range of languages in the same database.
CMS-XML KM-Dim7: Accented character appearing as 'i' when Change Document is browsed.
Country is FRANCE, AMERICA etc Character Set is either US7ASCII or WE8ISO8859P1 The latter allows for high ascii and accented characters.
CMS-XML DIM CM: Errors in Windows Event Viewer when running a Dim CM agent
DM_DEFAULT_DBMS ORACLE DM_DEFAULT_DBMS_CHARSET UTF8 <= or whatever character set you are running, e.g. WE8ISO8859P15, US7ASCII , etc.
CMS-XML KM-Dim9: How to find out which character set is installed in Oracle?
NLS_CHARACTERSET US7ASCII NLS_CALENDAR GREGORIAN NLS_DATE_FORMAT DD-MON-YYYY NLS_DATE_LANGUAGE AMERICAN NLS_SORT BINARY NLS_TIME_FORMAT HH.MI.SS
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs