Oracle 10.2 upgrade problems

From: frankie <frankies_at_gmx.ch>
Date: 11 Apr 2006 08:07:04 -0700
Message-ID: <1144768024.102608.181720@e56g2000cwe.googlegroups.com>

Hi,
On a Windows test environment Oracle 10.1 is installed (one instance with one database). I tried to update it to 10.2 now, according to Oracle's upgrade guide
(http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14238/toc.htm)

I could install the new release (10.2) without problems, but as soon as I tried to upgrade the database using the "Database upgrade Assistant", I get the following errors:

ORA-00604: error occurred at recursive SQL level 1 ORA-02248: invalid option for ALTER SESSION

I was thinking that there is something wrong with my old release (10.1) and decided therefore to create a new database, instead of upgrading the old one.
But when I tried to create a new database in 10.2 (using the 10.2
"Database Configruation Assistant") I ran into exactly the same error.

Does anybody know this problem? The old release (10.1) works correctly, but as soon as I would like to use 10.2 it throws the above errors.

Your help would be much appreciated
Best regards
Franc

Below the log-file created during the upgrade from 10.1 to 10.2 by
"Database upgrade Assistant"

******************************************Begin of
file***************************************************

Connected.
Connected.

1
Database closed.
Database dismounted.
ORACLE instance shut down.
select count(*) from v$instance
*
FEHLER in Zeile 1:
ORA-01034: ORACLE not available

ORA-00604: error occurred at recursive SQL level 1 ORA-02248: invalid option for ALTER SESSION ERROR:
ORA-01012: Nicht angemeldet

Bei einer nicht hochgefahrenen Instance angemeldet. Rem
Rem $Header: catupgrd.sql 14-mar-2005.12:53:30 rburns Exp $ Rem
Rem catupgrd.sql
Rem
Rem Copyright (c) 1999, 2005, Oracle. All rights reserved. Rem
Rem NAME
Rem catupgrd.sql - CATalog UPGraDe to the new release Rem
Rem DESCRIPTION

Rem	This script is to be used for upgrading an 8.1.7, 9.0.1, 9.2
Rem	or 10.1 database to the new release.  This script provides a direct
Rem	upgrade path from these releases to the new Oracle release.
Rem
Rem	 The upgrade is partitioned into the following 5 stages:
Rem	   STAGE 1: call the "i" script for the oldest supported release:
Rem 		This loads all tables that are necessary
Rem 		to perform basic DDL commands for the new release
Rem	   STAGE 2: call utlip.sql to invalidate PL/SQL objects
Rem	   STAGE 3: Determine the original release and call the
Rem 		c0x0x0x0.sql for the release.  This performs all
Rem 		necessary dictionary upgrade actions to bring the
Rem 		database from the original release to new release.
Rem	   STAGE 4: call the a0x0x0x0.sql for the original release:
Rem 		This performs all necessary upgrade using
Rem 		anonymous blocks.
Rem	   STAGE 5: call cmpdbmig.sql
Rem 		This calls the upgrade scripts for all of the
Rem 		components that have been loaded into the database

Rem
Rem NOTES
Rem

Rem	 * This script needs to be run in the new release's environment
Rem	   (after installing the release to which you want to upgrade).
Rem	 * You must be connected AS SYSDBA to run this script.

Rem
Rem MODIFIED (MM/DD/YY)

Rem    rburns	   03/14/05 - dbms_registry_sys timestamp
Rem    rburns	   02/27/05 - record action for history
Rem    rburns	   10/18/04 - remove catpatch.sql
Rem    rburns	   09/02/04 - remove dbms_output compile
Rem    rburns	   06/17/04 - use registry log and utlusts
Rem    mvemulap    05/26/04 - grid mcode compatibility
Rem    jstamos	   05/20/04 - utlip workaround
Rem    rburns	   05/17/04 - rburns_single_updown_scripts
Rem    rburns	   01/27/04 - Created

Rem

Rem Exit immediately if there are errors in the initial checks Rem

WHENEVER SQLERROR EXIT; DOC

DOC>######################################################################
DOC>######################################################################
DOC>	The following statement will cause an "ORA-01722: invalid number"
DOC>	error if the user running this script is not SYS.  Disconnect
DOC>	and reconnect with AS SYSDBA.
DOC>######################################################################
DOC>######################################################################

DOC>#

SELECT TO_NUMBER('MUST_BE_AS_SYSDBA') FROM DUAL
2  WHERE USER != 'SYS';
SELECT TO_NUMBER('MUST_BE_AS_SYSDBA') FROM DUAL

*
FEHLER in Zeile 1:
ORA-01012: not logged on

******************************************End of
file******************************************************

Received on Tue Apr 11 2006 - 10:07:04 CDT