For any database, the superset check is pretty quick. It just grabs the
current database character set and the new database character set and checks
whether the new character set is a strict binary superset (the globalization
guide has an appendix that lists the valid supersets). Oracle never has to
look at your data.
There is an undocumented clause INTERNAL_USE that you can use to force the
character set change, but I would classify that as an incredibly high risk
operation (and the fact that the clause itself tells you that it is for
internal use should amplify that warning). Recreating a database with no
data is trivial in comparison to the pain and testing that should go in to
using this clause.
Justin Cave
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC
-- --Original Message-- --
From: oracle-l-bounce@(protected) [mailto:oracle-l-bounce@(protected)]
On Behalf Of Mark W. Farnham
Sent: Friday, July 30, 2004 8:46 AM
To: oracle-l@(protected)
Subject: RE: Changing Character Set
OP did write "new " database, so I think that means no user data is at risk.
But I 'm not sure whether you can even skip the binary superset check for the
Oracle data dictionary and things they load in support of the products. I
wonder whether less time and effort and more certainty would be to simply
recreate the database. Has anyone already done this? Of course one "it
worked okay, no problems " only covers that specific case. Without an
engineering certainty of what might go wrong, there would have to be a
pretty big overhead avoided to justify the testing overhead. For a new
database the superset check should be pretty short, right?
mwf
-- --Original Message-- --
From: oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected)]On Behalf Of Justin Cave
Sent: Friday, July 30, 2004 9:57 AM
To: oracle-l@(protected)
Subject: RE: Changing Character Set
I 'm not sure whether you intended to send a different Metalink note, but
234381.1 covers how to move an Oracle 7 database with the AL24UTFFSS to 9i
with a character set AL32UTF8 by going through 8i (since AL24UTFFSS isn 't a
valid character set in 9i).
In almost every case, you would not want to skip the superset check. When
you change the database character set, Oracle is only updating the internal
data structures, it is not updating any of the actual data in the database.
Without the binary superset check, you can very, very easily corrupt some or
all of your data.
Justin Cave
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC
-- --Original Message-- --
From: oracle-l-bounce@(protected) [mailto:oracle-l-bounce@(protected)]
On Behalf Of Fuad Arshad
Sent: Friday, July 30, 2004 7:16 AM
To: oracle-l@(protected)
Subject: Re: Changing Character Set
metalink Note:234381.1 can help you do this Ken Payton
<Ken.Payton@(protected) > wrote:Does anyone know how to switch off the
superset check when changing the = national character set. I would like to
change the character set of a = new database without rebuilding it and I am
receiving ORA-12714 (See ORA-12714.ora-code.com): invalid = national character set specified.
-- --Original Message-- --
From: oracle-l-bounce@(protected)
[mailto:oracle-l-bounce@(protected)]On Behalf Of Tim Gorman
Sent: Friday, July 30, 2004 5:38 AM
To: oracle-l@(protected)
Subject: Re: Lost PERFSTAT bridge scripts Found it
Larry,
Thanks for the post of Mr Hurley 's material. Especially useful is the = use
of AUTONOMOUS TRANSACTION pragma, although I 've not found it to be
necessary...
I can understand performing a STATSPACK.SNAP before database shutdown, = to
"flush " any values to disk before they are lost, but I am at a loss to
understand the reason to perform a STATSPACK.SNAP in an AFTER STARTUP
database-event trigger?
-Tim
on 7/29/04 1:49 PM, Wolfson Larry - lwolfs at = lawrence.wolfson@(protected)
wrote:
> Guess I didn 't get specific enough on Google the first time.
>
> Sorry
>
> http://www.quest-pipelines.com/pipelines/dba/tips03.htm#january
>
> January 's Tip of the Month
>
> Automatic Statspack Snapshots at Shutdown and Startup Compliments of
>Darryl Hurley, Pipeline SYSOP (dhurley@(protected)) Oracle?s
>Statspack utility provides a straightforward method of monitoring
> database performance statistics. The process is simple; take interval
> snapshots of performance indicators and then run reports to see how much the
> indicators have changed during the interval(s).
>
> Problems arise when intervals span an Oracle shutdown because comparing
> interval values across them is illogical. Here?s an example:
>
> 10:00 PM Statspack Snapshot #33 shows Physical Reads = 100000
> 10:15 PM Database Shutdown
> 10:20 PM Database Restarted
> 11:00 PM Statspack Snapshot #34 shows Physical Reads = 100 At
>this point a StatsPack Report comparing snapshot #33 to snapshot #34
> would claim that ?99900 physical reads had occurred. Actually the report
> would begin with this self-explanatory text:
>
> ERROR: Snapshots chosen span an instance shutdown: RESULTS ARE INVALID
> It?s impossible to report across a shutdown, but it is possible to
>reduce
> the lost periods of time (10:00 to 10:15 and 10:20 to 11:00 in our example)
> by automatically performing snapshots before shutdown and after startup.
> It?s easily done with BEFORE-SHUTDOWN and AFTER-STARTUP triggers.
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected) put
'unsubscribe ' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected) put
'unsubscribe ' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected) put
'unsubscribe ' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected) put
'unsubscribe ' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected) put
'unsubscribe ' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe ' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
