Changing Character Set

From: Ken Payton <Ken.Payton_at_choicepointprg.net>
Date: Fri, 30 Jul 2004 08:01:15 -0400
Message-ID: <758260AC76ABD64AA3781956D6A50C3D1E83F3@bobwpmsg001.choicepoint.net>

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: invalid = national character set specified. =20

-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Tim Gorman Sent: Friday, July 30, 2004 5:38 AM
To: oracle-l_at_freelists.org
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_at_acxiom.com
wrote:

> Guess I didn't get specific enough on Google the first time.

>=20

> Sorry

>=20

> http://www.quest-pipelines.com/pipelines/dba/tips03.htm#january

>=20

> January's Tip of the Month

>=20

> Automatic Statspack Snapshots at Shutdown and Startup
> Compliments of Darryl Hurley, Pipeline SYSOP (dhurley_at_mdsi.bc.ca)
>=20
> 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).
>=20
> Problems arise when intervals span an Oracle shutdown because =
comparing
> interval values across them is illogical. Here?s an example:

>=20


>   10:00 PM Statspack Snapshot #33 shows Physical Reads =3D 100000

>   10:15 PM Database Shutdown

> 10:20 PM Database Restarted
> 11:00 PM Statspack Snapshot #34 shows Physical Reads =3D 100
>=20
> 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:

>=20

> ERROR: Snapshots chosen span an instance shutdown: RESULTS ARE INVALID
>=20
> 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_at_freelists.org 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_at_freelists.org
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
-----------------------------------------------------------------

Received on Fri Jul 30 2004 - 06:58:01 CDT