Home » RDBMS Server » Server Administration » update props$ set value$ (oracle 10g Enterprise, 10.2.0.1.0, Windows XP)
update props$ set value$ [message #547908] Sun, 18 March 2012 20:25 Go to next message
kevinlky
Messages: 5
Registered: October 2011
Location: Singapore
Junior Member
Since the past, our developer uses this command
"update props$ set value$ set = 'ZHS16GBK' where name='NLS_CHARACTERSET' ;" and
update props$ set value$='WE8MSWIN1252' where name='NLS_CHARACTERSET';
to update the sys table which is not supported by oracle.

However, I decided to use CSSCAN to scan through the database and see if the new characterset will work.

But before using CSSCAN, I will like to know which characterset to set back as our developer does not know which is the original characterset.
Re: update props$ set value$ [message #547909 is a reply to message #547908] Sun, 18 March 2012 20:34 Go to previous messageGo to next message
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
Senior Member
>I will like to know which characterset to set back as our developer does not know which is the original characterset.
We don't know what was in YOUR database.

Re: update props$ set value$ [message #547910 is a reply to message #547909] Sun, 18 March 2012 20:43 Go to previous messageGo to next message
kevinlky
Messages: 5
Registered: October 2011
Location: Singapore
Junior Member
Hi BlackSwan, thanks for you reply.

Our DB consist of a mixture of chinese and english character.

In the ZHS16GBK, we are able to see the chinese character and english character. However, when script is execute, it will return error on unable to compile and when dumb are imported from other source, the character for the new dumb will be jumbled and not able to read.

Only when we set back to WE8MSWIN1252, script will be able to run and import are able to execute but data will be jumbled.
Re: update props$ set value$ [message #547918 is a reply to message #547910] Mon, 19 March 2012 00:21 Go to previous messageGo to next message
Michel Cadot
Messages: 68641
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
You cannot switch back and forth between the 2 character sets you mentioned.
They are incompatible just by the length of each code points: 2 bytes vs 1 byte.

Regards
Michel

[Edit: typo]

[Updated on: Mon, 19 March 2012 01:51]

Report message to a moderator

Re: update props$ set value$ [message #547921 is a reply to message #547918] Mon, 19 March 2012 00:28 Go to previous messageGo to next message
kevinlky
Messages: 5
Registered: October 2011
Location: Singapore
Junior Member
Hi Michel Cadot,

Thanks for the pointer. However, I decided to create a new DB with AL32UTF8 Characterset and after that I will do a expdp from the existing DB and impdp to the new DB. Will that solve the issue? And which characterset should I set to expdp?
Re: update props$ set value$ [message #547931 is a reply to message #547921] Mon, 19 March 2012 01:53 Go to previous messageGo to next message
Michel Cadot
Messages: 68641
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Quote:
Will that solve the issue?

Yes if the data are correct, no if you scrambled them some inappropriate character set changes.

Quote:
which characterset should I set to expdp? Report message to a moderator


The one of your database.

Regards
Michel
Re: update props$ set value$ [message #548378 is a reply to message #547908] Wed, 21 March 2012 12:46 Go to previous messageGo to next message
KKVG
Messages: 1
Registered: March 2012
Junior Member
it is good to use unicode, i think it will reach your requirements or initial stage supplementary characters
Re: update props$ set value$ [message #548399 is a reply to message #547931] Wed, 21 March 2012 22:01 Go to previous messageGo to next message
kevinlky
Messages: 5
Registered: October 2011
Location: Singapore
Junior Member
Hi Michel Cadot,

Just went to look through the alert log and found out that the original character set it WE8MSWIN1252.

The issue that i'm facing now is when the character set is set to WE8MSWIN1252, using toad 9 i'm able to read the data. But reading through with toad 10, the data will jumbled up.
Re: update props$ set value$ [message #548403 is a reply to message #548399] Thu, 22 March 2012 00:06 Go to previous message
Michel Cadot
Messages: 68641
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Through away TOAD it is a b...
Use SQL*Plus.

Regards
Michel

[Updated on: Thu, 22 March 2012 00:07]

Report message to a moderator

Previous Topic: TO KNOW USED SPACE OF DATA FILE
Next Topic: user dump
Goto Forum:
  


Current Time: Fri Apr 19 02:35:11 CDT 2024