on 08-27-2010 10:57 AM
We are migration our R3 4.70 system from non-unicode to Unicode. Database is Oracle 10.2.0.4.
Do I need to update R3ldctl, R3szchk and R3load to unicode versions on the source system, as they will be doing the conversion during the export?
Or should I keep them as the non-UC versions, ensuring they are only the latest non-UC versions?
I'll be using the Distribution Monitor for the migration process.
thanks,
Stephen
Hi stephen,
You can update latest Non-unicode kernal in your source system and while export you must use Non-Unicode kernal only.
While import you need to use Unicode kernal DVD/CD.
Thanks and Regards,
Jibin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the reply.
If only I had read the Distribution Monitor guide more closely I would have seen that.
I have read in oss note 788942 that I may need to use R3load flags '-dbcodepage 4103 -datacodepage 4103'.
However in the Distribution Monitor guide it says only to use those 2 flags if performing non-uc to non-uc.
I'll be running R3load on Linux for the export and import.
The database resides on an HP Alpha server, and no R3load processes will be running on it.
Unsure which one is correct.
Hi,
As per the Unicode conversion guide.
You use latest Master DVD/CD to export your database in Source system..
While doing export ..input phase you will get the Database Code page you mention your target system codepage (4102 or 4103).
Please read the Unicode conversion guide.
I don't think so...R3load you will get latest version if you use latest master DVD/CD.
Thanks and Regards,
Jibin.
> I'll be running R3load on Linux for the export and import.
> The database resides on an HP Alpha server, and no R3load processes will be running on it.
Actually the mentioned codepage is irrelevant.
If the data is not stored in the target servers codepage it will be converted (which will be a bit slower since bytes need to be swapped).
If it actually would make a big difference then one would need separate installation exports for each system, one for big- and one for little endian.
So don't worry too much about it.
Markus
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.