If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

It looks like an incomplete upgrade scenario, this is consistent with having upgraded Oracle codeset but not having upgraded Oracle instance. Each individual instance has to be upgraded after upgrading Oracle codeset.

If this is the case double-check Oracle upgrade README file for proper procedure.

Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

Step 1: Decide on Your Instance's System Identifier (SID) The first step in creating the database is to determine the System Identifier (SID).
This is what the environment will be set to when your database starts up
and shuts down, and what the instance processes will have in their names as unique identifiers.

My Instance name is called cat1020 you can use whatever you want. So
wherever you see cat1020 replace with your name. Of course, use file system
paths that are relavant to your machine.

Step 3: Connect to and Start the Instance
Connect to the instance as SYSDBA either using operating system authentication or the password file method of authentication and start up the instance using the STARTUP command.

>sqlplus '/ as sysdba'

NOTE: If your parameter file is not in the default location or is not named init.ora, you may need to specify the PFILE clause in the STARTUP command for the instance to start. Because you do not yet have a database attached to the instance, you need to start up the instance in NOMOUNT state:

SQL> startup nomount; The instance is now started and ready for the CREATE DATABASE command.

Step 6: Create a Server Parameter File
This step is optional, although highly recommended by Oracle. Your Oracle database was created by starting the instance with a parameter file, or PFILE. Because it is editable, you can migrate, easily, your new database to using a server parameter file. Creation of the server parameter file (or spfile) is accomplished by issuing the following statement: