Kbase P131452: Why does a database converted to Utf-8 still show an iso8859-1 cpinternal in it's log file?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
14/05/2008 |
|
Status: Unverified
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
OpenEdge Database Category: Configuration
SYMPTOM(s):
An Utf-8 converted database still shows iso8859-1 cpinternal in the log
CAUSE:
The database startup is reading the DLC/startup.pf file, which is still shows a cpinternal of 1so8859-1
FIX:
Start the database up with a -pf DLC/prolang/utf/utf8.pf. The command line parameters will be read last.