10 Replies Latest reply: Feb 9, 2013 6:07 AM by Srini Chavali-Oracle RSS

    Re: upgrade 11.2

    864103
      Hi expert ,

      i have oracle database 11.2.0.2.0 G under RHEL 6.3 , now i need to upgrade it to 11.2.0.2.0 G
      i run the below script but it's not work :
      Connected to:
      Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
      With the Partitioning, OLAP, Data Mining and Real Application Testing options
      
      SQL> select status from v$instance;
      
      STATUS
      ------------
      OPEN MIGRATE
      
      SQL> @/home/oracle/app/oracle/product/11.2.0/dbhome_1/rdbms/admin/utlu112i.sql
      DECLARE
      *
      ERROR at line 1:
      ORA-00600: internal error code, arguments: [qcisSetPlsqlCtx:tzi init], [], [],
      [], [], [], [], [], [], [], [], []
      SQL> select status from v$instance;
      
      STATUS
      ------------
      OPEN MIGRATE
      
      SQL> @/home/oracle/app/oracle/product/11.2.0/dbhome_1/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>    Shutdown ABORT and use 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 a "SHUTDOWN ABORT"  and
      DOC>   restart using UPGRADE.
      DOC>#######################################################################
      DOC>#######################################################################
      DOC>#
      
      no rows selected
      
      DOC>#######################################################################
      DOC>#######################################################################
      DOC>     The following statement will cause an "ORA-01722: invalid number"
      DOC>     error if the Oracle Database Vault option is TRUE.  Upgrades cannot
      DOC>     be run with the Oracle Database Vault option set to TRUE since
      DOC>     AS SYSDBA connections are restricted.
      DOC>
      DOC>     Perform a "SHUTDOWN ABORT", relink the server without the Database
      DOC>     Vault option (but with the OLS option), and restart the server using
      DOC>     UPGRADE.
      DOC>
      DOC>     Restriction is for:
      DOC>     1) When source database has no DV installed.
      DOC>     OR
      DOC>     2) When source database has DV installed and DV version is prior to 11.2.
      DOC>
      DOC>#######################################################################
      DOC>#######################################################################
      DOC>#
      
      no rows selected
      
      DOC>#######################################################################
      DOC>#######################################################################
      DOC>   The following statement will cause an "ORA-01722: invalid number"
      DOC>   error if Database Vault is installed in the database but the Oracle
      DOC>   Label Security option is FALSE.  To successfully upgrade Oracle
      DOC>   Database Vault, the Oracle Label Security option must be TRUE.
      DOC>
      DOC>   Perform a "SHUTDOWN ABORT", relink the server with the OLS option
      DOC>   (but without the Oracle Database Vault option) and restart the server
      DOC>   using UPGRADE.
      DOC>#######################################################################
      DOC>#######################################################################
      DOC>#
      
      no rows selected
      
      DOC>#######################################################################
      DOC>#######################################################################
      DOC>   The following statement will cause an "ORA-01722: invalid number"
      DOC>   error if bootstrap migration is in progress and logminer clients
      DOC>   require utlmmig.sql to be run next to support this redo stream.
      DOC>
      DOC>   Run utlmmig.sql
      DOC>   then (if needed)
      DOC>   restart the database using UPGRADE and
      DOC>   rerun the upgrade script.
      DOC>#######################################################################
      DOC>#######################################################################
      DOC>#
      
      no rows selected
      
      DOC>#######################################################################
      DOC>#######################################################################
      DOC>   The following statement will cause:
      DOC>   - "ORA-00942: table or view does not exist" ; or
      DOC>   - "ORA-00904: "TZ_VERSION": invalid identifier"" ; or
      DOC>   - "ORA-01722: invalid number"
      DOC>     if the pre-upgrade utility (utlu112i.sql) has not been run to:
      DOC>     a) create and update registry$database table to include the current
      DOC>        database timezone file version used in the old release; or
      DOC>     b) do inserts into sys.props$.
      DOC>
      DOC>     o Action:
      DOC>       Shutdown ABORT and revert to the original ORACLE_HOME.  Then run
      DOC>       utlu112i.sql to populate registry$database with the database timezone
      DOC>       file version used by the lower version database and to populate
      DOC>       sys.props$ with Day Light Saving Time (DST) properties information.
      DOC>
      DOC>   OR
      DOC>   - An "ORA-01722: invalid number"
      DOC>     if the old release uses a timezone file version newer than 8 (shipped with
      DOC>     11.2) but the new release has not been patched yet.
      DOC>
      DOC>     o Action:
      DOC>       Shutdown ABORT and patch new ORACLE_HOME to the same timezone file
      DOC>       version as used in the old ORACLE_HOME.
      DOC>
      DOC>
      DOC>#######################################################################
      DOC>#######################################################################
      DOC>#
      SELECT TO_NUMBER('MUST_BE_SAME_TIMEZONE_FILE_VERSION')
                       *
      ERROR at line 1:
      ORA-01722: invalid number
      
      {code}
      
      please advice