Re: change character set i Oracle 7.3.2

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/ Received on Wed Jan 17 2001 - 23:01:13 CST