Description of problem:
In the case of different character encodings, content exported from Hosted may exceed Satellite schema, causing satellite-sync failure.

Example:
Recently due to special characters in Errata Description of erratum https://rhn.redhat.com/rhn/errata/details/Details.do?eid=7924, the exported content exceeded 4000 char limit causing all (pre-5.2) Satellite-syncs to fail for RHEL 5 channels.

Bug 476751 -  ValueError: string data too large
and 
Bug 476756 -  sat-sync unhandled exception 1461, 'ORA-01461: can bind a LONG
value only for insert into a LONG columnn'

The short term fix was to reduce char count for the description of the erratum in question even further.  For the long-term fix on the export side, need to make sure the exported content conforms to the schema on import side (errata description is one specific field, this needs to be done in general).

Version-Release number of selected component (if applicable):
Current (5.0.8)

How reproducible:
See example above.

Steps to Reproduce:
1. See example above.
2.
3.
  
Actual results:
See example above.

Expected results:
Regardless of character encoding, the exported content from Hosted should conform to schema on importer side (Satellite). 

Additional info: