Re: change character set i Oracle 7.3.2

Good question. There shouldn't be any difference in either case. But I can't say for sure. I mean, I used two solutions, official (yes, it's export/import), you create another database with needed characterset, export your original database and import it into the new one. I also used my hack (update props$ ...) and it works fine, if target charset is a superset of the original charset. This is your case, WE8ISO8859P1 is a superset of ASCII.

In article <h4x96.1580$cF.35089_at_news1.nokia.com>,   "Anders Blomkvist" <anders.blomkvist_at_nokia.com> wrote:
> I am a little bit confused. The offical way Sybrand meantioned, is
 that the
> exp/imp procedure? What differs from that and one of these hacks, ie
 what
> will the differences be in the database afterwards? Will the data be
 stored
> differently in the database if a do an exp/imp than if I only do one
 of
> these hacks?
>
> BR,
> Anders
>
> "Alex Filonov" <afilonov_at_pro-ns.net> wrote in message
> news:945tao$b91$1_at_nnrp1.deja.com...
> > One more hack. It's easier, but more dangerous. If you set a
> > non-existing charset, database won't start:
> >
> > under user sys:
> >
> > update props$
> > set value='WE8ISO8859P1'
> > where name = 'NLS_CHARACTERSET';
> >
> > Shutdown, then restart the database. You'd better make a backup
 before.
> >
> >
> > In article <9455vi$c2vst$5_at_ID-62141.news.dfncis.de>,
> > "Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote:
> > > This method is, of course, completely *unsupported* and dangerous:
 you
> > > shouldn't definitely hack your export.
> > >
> > > The only reason to go ahead in this direction is your 7.3.2
 version
 has been
> > > desupported, so unless you have an extended support contract,
 there's
 not
> > > much difference whether you go the official route, or use the hack
 as
> > > outlined below.
> > >
> > > Regards,
> > >
> > > Sybrand Bakker, Oracle DBA
> > >
> > > "Anders Blomkvist" <anders.blomkvist_at_nokia.com> wrote in message
> > > news:iAj96.20634$oL4.427350_at_news2.nokia.com...
> > > > Hmm, do i still have to drop the database and change the charset
 in
 oracle?
> > > >
> > > > /Anders
> > > >
> > > > "BVB" <bart.van.den.bosch_at_ordab.com> wrote in message
> > > > news:979747884.269917_at_localhost...
> > > > >
> > > > > Before importing the dump file, change its third byte (with a
 hex-editor)
> > > > > from $01 (code for US7ASCII) to $1F (WE8ISO8859P1).
> > > > > The exp and imp parameters doesn't matter.
> > > > >
> > > > > Bart
> > > > >
> > > > >
> > > > > Anders Blomkvist <anders.blomkvist_at_nokia.com> wrote in message
> > > > > news:Uxi96.20620$oL4.427327_at_news2.nokia.com...
> > > > > > What is the best way to change character set i an Oracle
 v7.3.2
 database
> > > > > > from US7ASCII to WE8ISO8859P1?
> > > > > > I am pretty sure about the procedure:
> > > > > >
> > > > > > 1) Export data
> > > > > > 2) Drop database
> > > > > > 3) Create basic database with new character set
> > > > > > 4) Import data
> > > > > >
> > > > > > But how should the exp command look like?
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
> > Sent via Deja.com
> > http://www.deja.com/
>
>

Sent via Deja.com
http://www.deja.com/ Received on Thu Jan 18 2001 - 22:23:08 CST