cancel
Showing results for 
Search instead for 
Did you mean: 

Oracle 11g upgrade

Former Member
0 Kudos

Dear Friends,

Thanks for yours valuable help for my all queries.

I am upgrading Oracle 11g on my APO test server.

Previously It was on HP-UX 11 i v2 and Oracle 10.2.0.2.

Now We have upgraded OS 11i v3 and Oracle 10.2.0.4. SAP application is runing fine.

Now I have started to upgrade Oracle 11g from Oracle 10.2.0.4. I have installed Oracle 11g software and new Oralce home /oracle/DVP/11202 has been created and I have strted upgrade and getting the error below.

jkeccbc:oradvp 2> setenv ORACLE_HOME /oracle/DVP/11202

jkeccbc:oradvp 3> setenv ORACLE_SID DVP

jkeccbc:oradvp 4> setenv PATH /oracle/DVP/11202/bin:$PATH

jkeccbc:oradvp 5> setenv TNS_ADMIN /oracle/DVP/11202/network/admin

jkeccbc:oradvp 6>

SQL> startup upgrade

ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance

ORACLE instance started.

Total System Global Area

5845950464 bytes

Fixed Size

2191760 bytes

Variable Size

2936016496 bytes

Database Buffers

2902458368 bytes

Redo Buffers

5283840 bytes

ORA-00205: error in identifying control file, check alert log for more info

SQL>

SQL> spool patch.log

SQL> @/oracle/DVP/11202/rdbms\admin\catupgrd.sql

SP2-0310: unable to open file "/oracle/DVP/11202/rdbmsadmincatupgrd.sql"

SQL> @/oracle/DVP/11202/rdbms/admin/catupgrd.sql

DOC>#######################################################################

DOC>#######################################################################

DOC>

DOC> The first time this script is run, there should be no error messages

DOC> generated; all normal upgrade error messages are suppressed.

DOC>

DOC> If this script is being re-run after correcting some problem, then

DOC> expect the following error which is not automatically suppressed:

DOC>

DOC> ORA-00001: unique constraint (<constraint_name>) violated

DOC> possibly in conjunction with

DOC> ORA-06512: at "<procedure/function name>", line NN

DOC>

DOC> These errors will automatically be suppressed by the Database Upgrade

DOC> Assistant (DBUA) when it re-runs an upgrade.

DOC>

DOC>#######################################################################

DOC>#######################################################################

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>#

no rows selected

DOC>######################################################################

DOC>######################################################################

DOC> The following statement will cause an "ORA-01722: invalid number"

DOC> error if the database server version is not correct for this script.

DOC> Perform "ALTER SYSTEM CHECKPOINT" prior to "SHUTDOWN ABORT", and use

DOC> a different script or a different server.

DOC>######################################################################

DOC>######################################################################

DOC>#

no rows selected

DOC>#######################################################################

DOC>#######################################################################

DOC> The following statement will cause an "ORA-01722: invalid number"

DOC> error if the database has not been opened for UPGRADE.

DOC>

DOC> Perform "ALTER SYSTEM CHECKPOINT" prior to "SHUTDOWN ABORT", and

DOC> restart using UPGRADE.

DOC>#######################################################################

DOC>#######################################################################

DOC>#

SELECT TO_NUMBER('MUST_BE_OPEN_UPGRADE') FROM v$instance

*

ERROR at line 1:

ORA-01722: invalid number

Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

jkeccbc:oradvp 7> spool off

spool: Command not found.

jkeccbc:oradvp 8> sqlplus "/as sysdba'

Unmatched ".

jkeccbc:oradvp 9> sqlplus "/as sysdba"

SQL*Plus: Release 10.2.0.4.0 - Production on Tue Sep 13 10:30:21 2011

Copyright (c) 1982, 2007, Oracle. All Rights Reserved.

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> spool off

not spooling currently

SQL> shutdown

ORA-01507: database not mounted

ORACLE instance shut down.

SQL> startup

ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance

ORACLE instance started.

Total System Global Area

5845950464 bytes

Fixed Size

2191760 bytes

Variable Size

2936016496 bytes

Database Buffers

2902458368 bytes

Redo Buffers

5283840 bytes

ORA-00205: error in identifying control file, check alert log for more info

SQL>

Regards

Ganesh Datt Tiwari

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

Helpful answers

Former Member
0 Kudos

what about the pre_upgrade_status.sql? did you run it? the output?

ORA-32004> is not a problem

ORA-00205> must be investigated

SP2-0310: unable to open file "/oracle/DVP/11202/rdbmsadmincatupgrd.sql > check the file

the other errors are a subsequence.

Did you check all the prerequisite of the Upg (HP parameter....link library on oraclehome...

ciao

Cristian

Former Member
0 Kudos

Hi Ciao,

Thanks for your valuable help.

I have run pre-upgrade script and made some chenges accordingly like hidden parameters and othrs.

During installation I have not received any error or warrning.

But it is giving the error during startup upgrade "Control file can not be identify"

I have checked the parameter control_files value is /oracle/DVP/11202/dbs/ora_control which is not in the same directory.

Regards

Ganesh Datt Tiwari

Former Member
0 Kudos
I have not copy the pfile from 10g to 11g.
I have seen your link. now i will try that.
Please confirm one thing that Oracle 11g client installation should be done before starting upgrade ?

Are you following the standard Installation/Upgrade guide?

Each and every step/execution is documented with commands.

*Manual upgrade is not a recommended method for beginners

Regards,

Nick Loy

Former Member
0 Kudos

Hello,

So you started the upgrade using, SQL> startup upgrade. But it seems that the oracle is not able to find the control file. Can you have a look into alertSID.log file for the exact error ?

I think alertSID.log file exists in the path /oracle/SID/saptrace/background

Thanks

Former Member
0 Kudos

Hi,

Could you post the error information from the alert<sid>.log? Should be at /oracle/SID/saptrace.

ORA-00205: error in identifying control file, check alert log for more info

The system could not find a control file of the specified name and size.

Check that ALL control files are online and that they are the same files that the system created at start time.

Regards,

Srikishan

Former Member
0 Kudos

Hi Shrikishan,

Thanks for your valuable help.

I have checked the parameter control_files, it is showing value as /oracle/DVP/11202/dbs/ora_control1, There is no file ora_control1.

Please see the below log. I have checked the parameter of ADR which is not in init.ora file.

Fri Sep 09 15:41:23 2011

ERROR: ORA-48178 encountered when checking if the process is able to

ERROR: create the ADR schema in the specified ADR Base directory [/oracle/DVP/saptrace]

ERROR: The ORA-48178 error is caused by the ORA-48122 error.

ORA-48122: error with opening the ADR block file [/oracle/DVP/saptrace/diag/rdbms/dvp/DVP/metadata/ADR_INTERNAL.mif] [0]

ORA-27037: unable to obtain file status

HPUX-ia64 Error: 251: Function is not available

Additional information: 46

ERROR: Check if the directory is readable and check if the OS version is supported for ADR.

ERROR: The process will switch back to the pre-ADR method of tracing and logging.

Fri Sep 09 15:42:06 2011

ERROR: ORA-48178 encountered when checking if the process is able to

ERROR: create the ADR schema in the specified ADR Base directory [/oracle/DVP/saptrace]

ERROR: The ORA-48178 error is caused by the ORA-48122 error.

ORA-48122: error with opening the ADR block file [/oracle/DVP/saptrace/diag/rdbms/dvp/DVP/metadata/ADR_INTERNAL.mif] [0]

ORA-27037: unable to obtain file status

HPUX-ia64 Error: 251: Function is not available

Additional information: 46

ERROR: Check if the directory is readable and check if the OS version is supported for ADR.

ERROR: The process will switch back to the pre-ADR method of tracing and logging.

Fri Sep 09 15:57:52 2011

ERROR: ORA-48178 encountered when checking if the process is able to

ERROR: create the ADR schema in the specified ADR Base directory [/oracle/DVP/saptrace]

ERROR: The ORA-48178 error is caused by the ORA-48122 error.

ORA-48122: error with opening the ADR block file [/oracle/DVP/saptrace/diag/rdbms/dvp/DVP/metadata/ADR_INTERNAL.mif] [0]

ORA-27037: unable to obtain file status

HPUX-ia64 Error: 251: Function is not available

Additional information: 46

ERROR: Check if the directory is readable and check if the OS version is supported for ADR.

ERROR: The process will switch back to the pre-ADR method of tracing and logging.

Fri Sep 09 15:58:47 2011

ERROR: ORA-48178 encountered when checking if the process is able to

ERROR: create the ADR schema in the specified ADR Base directory [/oracle/DVP/saptrace]

ERROR: The ORA-48178 error is caused by the ORA-48122 error.

ORA-48122: error with opening the ADR block file [/oracle/DVP/saptrace/diag/rdbms/dvp/DVP/metadata/ADR_INTERNAL.mif] [0]

ORA-27037: unable to obtain file status

HPUX-ia64 Error: 251: Function is not available

Additional information: 46

ERROR: Check if the directory is readable and check if the OS version is supported for ADR.

ERROR: The process will switch back to the pre-ADR method of tracing and logging.

Fri Sep 09 16:05:18 2011

ERROR: ORA-48178 encountered when checking if the process is able to

ERROR: create the ADR schema in the specified ADR Base directory [/oracle/DVP/saptrace]

ERROR: The ORA-48178 error is caused by the ORA-48122 error.

ORA-48122: error with opening the ADR block file [/oracle/DVP/saptrace/diag/rdbms/dvp/DVP/metadata/ADR_INTERNAL.mif] [0]

ORA-27037: unable to obtain file status

HPUX-ia64 Error: 251: Function is not available

Additional information: 46

ERROR: Check if the directory is readable and check if the OS version is supported for ADR.

ERROR: The process will switch back to the pre-ADR method of tracing and logging.

Fri Sep 09 16:07:12 2011

ERROR: ORA-48178 encountered when checking if the process is able to

ERROR: create the ADR schema in the specified ADR Base directory [/oracle/DVP/saptrace]

ERROR: The ORA-48178 error is caused by the ORA-48122 error.

ORA-48122: error with opening the ADR block file [/oracle/DVP/saptrace/diag/rdbms/dvp/DVP/metadata/ADR_INTERNAL.mif] [0]

ORA-27037: unable to obtain file status

HPUX-ia64 Error: 251: Function is not available

Additional information: 46

ERROR: Check if the directory is readable and check if the OS version is supported for ADR.

ERROR: The process will switch back to the pre-ADR method of tracing and logging.

Fri Sep 09 17:41:52 2011

ERROR: ORA-48178 encountered when checking if the process is able to

ERROR: create the ADR schema in the specified ADR Base directory [/oracle/DVP/saptrace]

ERROR: The ORA-48178 error is caused by the ORA-48122 error.

ORA-48122: error with opening the ADR block file [/oracle/DVP/saptrace/diag/rdbms/dvp/DVP/metadata/ADR_INTERNAL.mif] [0]

ORA-27037: unable to obtain file status

HPUX-ia64 Error: 251: Function is not available

Additional information: 46

ERROR: Check if the directory is readable and check if the OS version is supported for ADR.

ERROR: The process will switch back to the pre-ADR method of tracing and logging.

Fri Sep 09 17:42:21 2011

ERROR: ORA-48178 encountered when checking if the process is able to

ERROR: create the ADR schema in the specified ADR Base directory [/oracle/DVP/saptrace]

ERROR: The ORA-48178 error is caused by the ORA-48122 error.

ORA-48122: error with opening the ADR block file [/oracle/DVP/saptrace/diag/rdbms/dvp/DVP/metadata/ADR_INTERNAL.mif] [0]

ORA-27037: unable to obtain file status

HPUX-ia64 Error: 251: Function is not available

Additional information: 46

ERROR: Check if the directory is readable and check if the OS version is supported for ADR.

ERROR: The process will switch back to the pre-ADR method of tracing and logging.

Former Member
0 Kudos

Hi,

Did you copy the initialization file (pfile) from Oracle 10 home to 11 home?

Check link http://onlineappsdba.com/index.php/2009/01/22/upgrade-oracle-database-10g-to-11g-r1-111x/ steps 1.7/1.8

Regards,

Srikishan

Former Member
0 Kudos

Hi Srikishan,

Thanks for your valuable help.

I have not copy the pfile from 10g to 11g.

I have seen your link. now i will try that.

Please confirm one thing that Oracle 11g client installation should be done before starting upgrade ?

Regards

Ganesh Datt Tiwari