Re: Anleitung für Oracle Upgrdae?

Hallo zusammen,

fyi


7.1 Upgrading Databases from Previous Releases Directly to Oracle9i
Release 2 (9.2.0.7)
To upgrade Oracle databases from a previous release directly to Oracle9i
release 2 (9.2.0.7) follow the instructions in OracleMetalink note
214887.1 Upgrading Directly to a 9.2.0 Patch Set.


See Also:

For more information about upgrading a database, see the Oracle9i
Database Migration guide.


7.2 Required Postinstallation Tasks
Complete the following tasks after installing the patch set software:

Check Tablespace Sizes and Set Parameter Values

Upgrade the Database

Download the Latest Version of OPatch

7.2.1 Check Tablespace Sizes and Set Parameter Values
Review the following sections before upgrading a database.

7.2.1.1 Check SYSTEM Tablespace Size
If JServer is part of the installation ensure that there is at least 10
MB of free space allocated to the SYSTEM tablespace.

7.2.1.2 Check XDB Tablespace Size
For RAC installations, ensure that there is at least 50 MB of free space
allocated to the XDB tablespace.

7.2.1.3 Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization
Parameters
Users who have JVM (Java enabled) or JVM and XDB installed on their
9.2.0.1 databases should make sure that the init.ora parameters
SHARED_POOL_SIZE and JAVA_POOL_SIZE are each 150 MB or more before
running the catpatch.sql upgrade script. Failure to do so could result
in an unrecoverable memory failure while running of the script. Please
note that JVM and XML DB was shipped as part of the default 9.2.0.1 seed
database, and will be present unless the user explicitly installed a
9.2.0.1 instance without them.

Set the value of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE
initialization parameters as follows:

Start the database:

SQL> STARTUP

If necessary, enter the following command to determine whether the
system uses an initialization parameter file (initsid.ora) or a server
parameter file (spfiledbname.ora):

SQL> SHOW PARAMETER PFILE;

This command displays the name and location of the server parameter file
or the initialization parameter file.

Determine the current values of these parameters:

SQL> SHOW PARAMETER SHARED_POOL_SIZE
SQL> SHOW PARAMETER JAVA_POOL_SIZE

If the system is using a server parameter file:

If necessary, set the value of the SHARED_POOL_SIZE initialization
parameter to at least 150 MB:

SQL> ALTER SYSTEM SET SHARED_POOL_SIZE='150M' SCOPE=spfile;

If necessary, set the value of the JAVA_POOL_SIZE initialization
parameter to at least 150 MB:

SQL> ALTER SYSTEM SET JAVA_POOL_SIZE='150M' SCOPE=spfile;

If the system uses an initialization parameter file, if necessary change
the values of the SHARED_POOL_SIZE and the JAVA_POOL_SIZE initialization
parameters to at least 150 MB in the initialization parameter file
(initsid.ora).

Shut down the database:

SQL> SHUTDOWN

7.2.2 Upgrade the Database
After you install the patch set, you must perform the following steps on
every database associated with the upgraded Oracle home:

Log in as the Oracle software owner (typically oracle).

For RAC installations, start the Global Services Daemon (GSD) on each
node of the cluster as follows:

$ gsdctl start

Start the Oracle Net listener as follows:

$ lsnrctl start


Note:

For RAC installations, start the listener on each node of the cluster.
If you are using the Oracle OLAP option, make sure that the listener is
running.



For single-instance installations, use SQL*Plus to log in to the
database as the SYS user with SYSDBA privileges:

$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA

For RAC installations:

Start the database as follows, where db_name is the database name:

$ srvctl start database -d db_name

Use SQL*Plus to log in to the database as the SYS user with SYSDBA
privileges:

$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA

Set the CLUSTER_DATABASE initialization parameter to FALSE:

SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;


Note:

If the system uses an initialization parameter file, change the value of
the CLUSTER_DATABASE initialization parameter to FALSE in the
initialization parameter file (initsid.ora).


Exit SQL*Plus and shut down the database:

SQL> EXIT
$ srvctl stop database -d db_name

Use SQL*Plus to log in to the database as the SYS user with SYSDBA
privileges:

$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA

Enter the following SQL*Plus commands:

SQL> STARTUP MIGRATE
SQL> SPOOL patch.log
SQL> @?/rdbms/admin/catpatch.sql
SQL> SPOOL OFF

Review the patch.log file for errors and inspect the list of components
that is displayed at the end of catpatch.sql script.

This list provides the version and status of each SERVER component in
the database.

If necessary, rerun the catpatch.sql script after correcting any
problems.

Restart the database:

SQL> SHUTDOWN
SQL> STARTUP

Run the utlrp.sql script to recompile all invalid PL/SQL packages now
instead of when the packages are accessed for the first time. This step
is optional but recommended.

SQL> @?/rdbms/admin/utlrp.sql

For RAC installations:

Set the CLUSTER_DATABASE initialization parameter to TRUE:

SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;

Note:

If the system uses an initialization parameter file, change the value of
the CLUSTER_DATABASE initialization parameters to TRUE in the
initialization parameter file (initsid.ora).


Restart the database:

SQL> SHUTDOWN
SQL> STARTUP

If you are using the Oracle Recovery Manager catalog, enter the
following command:

$ rman catalog username/password@alias
RMAN> UPGRADE CATALOG;

If Oracle Internet Directory release 9.2.0 is installed in the Oracle
home, run the following shell script:


Note:

Make sure that the database and database listener are running, and all
parameters for the oidpatchca.sh script are specified before running the
script.


$ORACLE_HOME/bin/oidpatchca.sh
-connect Connect_String
-lsnrport Listener_Port
-systempwd SYSTEM_Password
-odspwd ODS_Password
-sudn Super-User_DN
-supwd Super-User_Password
-dippwd Password_to_register_DIP_Server

In the preceding example, Password_to_register_DIP_Server must conform
to the password policy in the Oracle Internet Directory server.

7.2.3 Download the Latest Version of OPatch
You must install OPatch version 1.0.0.0.53 in order to apply patches on
top of 9.2.0.7. Download and unzip patch 2617419.


See Also:

OracleMetaLink Note 224346.1 and Note 189489.1 for more information.


7.3 mod_plsql Postinstallation Steps
Complete the following steps only if mod_plsql is installed. The
following steps should be repeated with all the database instances
associated with this 9.2.0.7 Oracle home.

Run owa_patch.sql to update owa packages from mod_plsql patch directory:

Change to the $ORACLE_HOME/Apache/modplsql/patch directory. For example,

$ cd $ORACLE_HOME/Apache/modplsql/patch
Connect to the database instance as sysdba:

$ sqlplus " / as sysdba"
SQL> @@owa_patch.sql
Check owa_patch_sid.log file for any errors.

Run the utlrp.sql script to recompile all invalid PL/SQL packages now
instead of when the packages are accessed for the first time. This step
is optional but recommended.

SQL> @?/rdbms/admin/utlrp.sql

8 Removing the Patch Set Software
Starting in 9.2.0.7.0, there is a new script called catbkout.sql. This
script enables the user to restore the Oracle9i installation of the
database back to the original 9.2 patch release (as long as it is
9.2.0.4 or greater) that the user backed up before applying the patch
set. Perform the following steps for backing out from the 9207 patch
release:

Before restoring the Oracle home to the original release, perform the
following steps:

$ sqlplus /nolog
SQL> connect / AS SYSDBA
SQL> SHUTDOWN
SQL> STARTUP MIGRATE
SQL> SPOOL catbkout.out
SQL> @?/rdbms/admin/catbkout.sql
SQL> SHUTDOWN IMMEDIATE

Restore the Oracle9i installation and Central Inventory (see
/etc/oraInst.loc/etc/oraInst.loc) that you backed up before applying the
patch set

After restoring the original Oracle home, perform the following steps:

$ sqlplus /nolog
SQL> connect / AS SYSDBA
SQL> STARTUP MIGRATE
SQL> SPOOL catpatch.out
SQL> @?/rdbms/admin/catpatch.sql

If Oracle Spatial is installed with the database, perform the following
steps:

SQL> alter session set current_schema = mdsys;
SQL> @?/md/admin/prvtsidx.plb
SQL> @?/md/admin/prvt3glh.plb
SQL> @?/md/admin/prvt3gl.plb
SQL> alter session set current_schema = sys;

Shut down the database:

SQL> SHUTDOWN IMMEDIATE

Start the database and recompile the remaining invalid objects:

SQL> STARTUP
SQL> @?/rdbms/admin/utlrp.sql

Review catbkout.out and catpatch.out for errors



--
Posted via Mailgate.ORG Server - http://www.Mailgate.ORG
.

Relevant Pages

  • ORA-01092: ORACLE instance terminated. Disconnection forced
    ... I know that Oracle recommends AUTO, but I just want to test ... SQL> CREATE TABLESPACE "RBS01" ... Database mounted. ... SQL> CREATE ROLLBACK SEGMENT rollback1 TABLESPACE rbs01 ...
    (comp.databases.oracle.server)
  • Re: Suggestoins for Local DB to use with Shareware
    ... I use Access for all my small installations. ... Even if the customer doesn't have Access installed, ... The DB should fully support SQL. ... a .NET v1.1 app that used the ubiquious NorthWind database in either MS ...
    (borland.public.delphi.non-technical)
  • Re: What so special about PostgreSQL and other RDBMS?
    ... That's exactly the link the licence agreement for the database points to when it ... comes to what wecan expect for paying support. ... > "Oracle may provide additional releases or versions of its programs ... If the requirements are volatile I'd do a long term contract detailing what ...
    (comp.lang.php)
  • Re: OOP/OOD Philosophy
    ... > Because if you don't Oracle will print something you don't want to see. ... The database should not print anything at all. ... > Great but this discussion was about Standand SQL. ... Transactions and locking work together. ...
    (comp.object)
  • Re: Connecting to an Oracle database
    ... If you have SQL*PLUS (Oracle product) installed on your system you can use ... If you have only one database installed on your system, ... > with data from the cusotmers old programs when making installations. ... It is not possible to use Toad for reading large ...
    (borland.public.delphi.database.ado)