Workaround for multi-byte, Non-ASCII table name in config file (4277632)

If the database is in multi-byte, non ASCII character set (e.g. Japanese or Chinese), config file may contain database object names that are non ASCII. Upon activation, these may generate errors

There may be more than one script in the character set, this may be misinterpreted to a wrong character code    e.g.  in Japanese, NLS_LANG setting of NLS_LANG=Japanese_Japan.JA16SJIS  (which is compatible with MS932 character set on OS.), there are 2 sets of alphabet-like character groups in Japanese, called 'Hiragana' and 'Katakana'.  The problematic Katakana character codes are between '8361' and '837A', and they were uniformly miscalculated, that is, those codes are treated as the actual code - 20

In the config file, for each object to be replicated, schema names and object names should be enclosed within double quote characters