Startup Oracle DB with different version of excutable..!?

[Warren_9]

Hiya,

I've an Oracle DB in version 7.2.0 but lost the oracle executables.....

is it possible to use other verison of oracle executable to open and mount the DB?

The oldest oracle i can found is 7.2.3!
if not, any suggestion to startup the DB??

THX,
Warren

[Luk Vandenbussche]

Hi Warren,

I it will work if you have the init.ora file.
But I would take a backup of all datafiles before trying this action

[Warren_9]

hi,

actually, the $ORACLE_HOME was lost and also the init.ora and the listener configure.

Can i use the default parameters to startup the DB? of course i need to point to the correct control files in the init.ora

THX,
Warren

[Luk Vandenbussche]

Hi Warren,

I should work with the default parameters in init.ora

[Yogeeraj_1]

hi,

before you try anything, please do a full backup.

if you have a copy of the database controlfile, maybe you can get back to operations quite easily...

is your database still up?

kind regards
yogeeraj

[Frank de Vries]

Technically you can do it,
your version is not to far off.

first you can go to nomount state to debug
your new init.ora file.
Once you have achieved that you can
check the control file(s) by going
to mount state.
You may need to run the catproc again !!
(it doesn't do any harm anyway if you do)
from there you can open with a
open resetlogs.

Good luck

[Indira Aramandla]

Hi Warren,

Yes it should work with the default parameters in init.ora. As you mentioned change the parameter file to point to the correct location of the control files, and also check the number and the names of the rollback segments defined are the same as defined in the database.

And as Yogeeraj mentioned, it is good to take a full backup of the DB.


IA

[Warren_9]

Hi all,

Thanks for the reply!

The DB is restored from tape but ppl didn't perform any backup on the oracle executables..!!

I also post the question in a oracle forum and 1 reply said that it need to start the DB in upgrade/migrate mode, any idea?

I need to make sure the procedure and it will work

MANY THX!!
Warren.

[Warren_9]

....

If I don't know the name of the RBS, could I startup the DB in nomount and re-create a new group of RBS?

THX.
Warren

[Indira Aramandla]

Hi Warren,

If you do not know the rollback segment names and the number of them, then you can comment this line in the init.ora file before starting the database.



IA

[Indira Aramandla]

Hi Warren,

When you say the DB has been restored from tape, can you startup the database. Or was it the Oracle software and all the config, parameter files restored from tape.

This is what metalink says about startup migrate.

STARTUP MIGRATE should only be used when a database instance is being migrated to a different version or when a patch is being applied. Further, once the
migration or patch has been successfully applied, the instance should be shutdown and restarted in normal mode.

STARTUP MIGRATE was introduced in 9.2 as a mechanism to be sure that most
everything that needs to be done to run an upgrade script or a patch script is done automatically. In the past, customers were expected to adjust certain initialization parameters prior to beginning an upgrade or applying a a patch, but most of this is now done automatically by STARTUP MIGRATE.

When a customer starts a database in MIGRATE mode, the following ALTER SYSTEM commands will be set automatically:

ALTER SYSTEM ENABLE RESTRICTED SESSION;
ALTER SYSTEM SET "_SYSTEM_TRIG_ENABLED"=FALSE SCOPE=MEMORY;
ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0 SCOPE=MEMORY;
ALTER SYSTEM SET AQ_TM_PROCESSES=0 SCOPE=MEMORY;
ALTER SESSION SET NLS_LENGTH_SEMANTICS=BYTE;



IA

[Warren_9]

so... startup migrate will not work coz my DB version is 7.2... not 9.2!!

[Eric Antunes]

Hi Warren,

Are you able to start it after comenting the rollback_segments part?

#rollback_segments = (RBS01,RBS02,...)

Best Regards,

Eric Antunes

[Frank de Vries]

that's right upgrade/migrade mode is not
applicable to version 7.2.x,
but there is a point about the upgade
that is worth mentioning.

When you have installed back your
executables you will have a number
of catalog scripts in
$ORACLE_HOME/rdbms/admin
like cat7.2.1.sql,cat7.2.3
You should run them in sequence starting from
the version you came from right upto
the version of your executables.

Once in mount state you will be in fact upgrading. But check first what the number of
cat scripts are (I do not have version 7 so
I cannot check) but it will show for itself

Same applies to catproc but is less fussy.

regards;

[Chris Loggans]

Oracle will not start up if it does not know where the control files are located. If you use the generic init.ora settings, at a minimum I would modify the CONTROL_FILES parameter and possibly the DB_BLOCK_SIZE parameter.

An easier solution to all of this would be to recreate a blank database and import the data from an export file. (Hopefully you have one :)

Thanks,
-Chris