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 KM-Dim10: ORA-24812: character set conversion to or from UCS2 failed ... error browsing/editing request
SELECT value$ FROM sys.props$ WHERE name = 'NLS_ CHARACTERSET ';
CMS-XML Dim10: Database characterset and Dimensions listener characterset consideration
Setting NLS_LANG correctly allows proper conversion from the client operating
CMS-XML Converting your Oracle database from WE8ISO8859P1 to AL32UTF8 for upgrade to SBM 2008
If your database is Oracle with NLS_ Characterset = WE8ISO8859P1 the process would be as follows: Take a backup of your production database where NLS_Characterset = WE8ISO8859P1 Import the database to Oracle database with NLS_Characterset = WE8ISO8859P1
CMS-XML VSS Conversion
VSS Conversion
PDF Serena ChangeMan Conversion Guide
Serena® ChangeMan® DS Conversion Guide
CMS-XML Conversion utility for AIX cisam
Conversion utility for AIX cisam
CMS-XML Conversion from C-ISAM database
Conversion from C-ISAM database
CMS-XML Large File Names Cause VSS Conversion Failures
Large File Names Cause VSS Conversion Failures
CMS-XML STR530B: Starbat syntax conversion
STR530B: Starbat syntax conversion
PDF Serena ChangeMan Conversion Guide
VERSION 5.7 Conversion Guide February 2005
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs