Admin/admin

ORA-00704: bootstrap process failure / ORA-39700

Qhtlr 2009. 4. 22. 15:40

솔라리스 8에 오라클 10.2.0.1 인스톨후 10.2.0.4 패치적용 완료

DB startup시 아래와 같은 메시지의 처리방법

"ORA-00704: bootstrap process failure / ORA-39700: database must be opened with UPGRADE option"

SQL> startup
ORACLE instance started.

Total System Global Area  293601280 bytes
Fixed Size                  2040088 bytes
Variable Size             113254120 bytes
Database Buffers          171966464 bytes
Redo Buffers                6340608 bytes
Database mounted.
ORA-01092: ORACLE instance terminated. Disconnection forced


[alertlog 에러 내용]
Errors in file /volumes/u01/app/oracle/product/10.2.0/admin/orcl/udump/orcl_ora_2350.trc:
ORA-00704: bootstrap process failure
ORA-39700: database must be opened with UPGRADE option
Wed Apr 22 15:30:27 2009
Error 704 happened during db open, shutting down database
USER: terminating instance due to error 704
Instance terminated by USER, pid = 2350
ORA-1092 signalled during: ALTER DATABASE OPEN...

10.7.2 Manually Upgrading a Release 10.2 Database

Complete the following sections to upgrade an Oracle Database 10g release 10.2.0.x to Oracle Database 10g release 10.2.0.4:

  1. Run the Pre-Upgrade Information Tool

  2. Upgrading a Release 10.2 Database

10.7.2.1 Run the Pre-Upgrade Information Tool

If you are upgrading database manually, then you should analyze it by running the Pre-Upgrade Information Tool.

The Pre-Upgrade Information Tool is a SQL script that ships with the new Oracle Database 10g release, and must be copied to and run from the environment of the database being upgraded. In upgrading from 9.2.0.X to 10.2.0.4, run the Pre-Upgrade-Information Tool in the 9.2.0.X environment. In upgrading a database from 10.2.0.X to 10.2.0.4, run the 10.2.0.4 version of the utlu102i.sql script in the environment of the previous 10.2.0.X release, and not in the 10.2.0.4 database.

Complete the following procedure to run the Pre-Upgrade Information Tool:

  1. Start the database in the UPGRADE mode:

    SQL> STARTUP UPGRADE

  2. Set the system to spool results to a log file for later analysis:

    SQL> SPOOL upgrade_info.log

  3. Run the Pre-Upgrade Information Tool:

    SQL> @?/rdbms/admin/utlu102i.sql

  4. Turn off the spooling of script results to the log file:

    SQL> SPOOL OFF

Check the output of the Pre-Upgrade Information Tool in the upgrade_info.log file. The following is an example of the output generated by the Pre-Upgrade Information Tool:

Oracle Database 10.2 Upgrade Information Utility    02-04-2008 11:48:11
.
**********************************************************************
Database:
**********************************************************************
--> name:       X102040
--> version:    10.2.0.1.0
--> compatible: 10.2.0.1
--> blocksize:  8192
.
**********************************************************************
Tablespaces: [make adjustments in the current environment]
**********************************************************************
--> SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 505 MB
.... AUTOEXTEND additional space required: 15 MB
--> UNDOTBS1 tablespace is adequate for the upgrade.
.... minimum required size: 401 MB
.... AUTOEXTEND additional space required: 376 MB
--> SYSAUX tablespace is adequate for the upgrade.
.... minimum required size: 265 MB
.... AUTOEXTEND additional space required: 15 MB
--> TEMP tablespace is adequate for the upgrade.
.... minimum required size: 58 MB
.... AUTOEXTEND additional space required: 38 MB
--> EXAMPLE tablespace is adequate for the upgrade.
.... minimum required size: 69 MB
.
**********************************************************************
Update Parameters: [Update Oracle Database 10.2 init.ora or spfile]
**********************************************************************
WARNING: --> "shared_pool_size" needs to be increased to at least 167772160
WARNING: --> "java_pool_size" needs to be increased to at least 67108864
.
**********************************************************************
Components: [The following database components will be upgraded orinstalled]
**********************************************************************
--> Oracle Catalog Views         [upgrade]  VALID
--> Oracle Packages and Types    [upgrade]  VALID
--> JServer JAVA Virtual Machine [upgrade]  VALID
--> Oracle XDK for Java          [upgrade]  VALID
--> Oracle Java Packages         [upgrade]  VALID
--> Oracle Text                  [upgrade]  VALID
--> Oracle XML Database          [upgrade]  VALID
--> Oracle Workspace Manager     [upgrade]  VALID
--> Oracle Data Mining           [upgrade]  VALID
--> Messaging Gateway            [upgrade]  VALID
--> OLAP Analytic Workspace      [upgrade]  VALID
--> OLAP Catalog                 [upgrade]  VALID
--> Oracle OLAP API              [upgrade]  VALID
--> Oracle interMedia            [upgrade]  VALID
--> Spatial                      [upgrade]  VALID
--> Oracle Ultra Search          [upgrade]  VALID
--> Oracle Label Security        [upgrade]  VALID
--> Expression Filter            [upgrade]  VALID
--> EM Repository                [upgrade]  VALID
--> Rule Manager                 [upgrade]  VALID
PL/SQL procedure successfully completed.

The following sections describe the output of the Pre-Upgrade Information Tool.

Database

This section displays global database information about the current database, such as the database name and release number before the database is upgraded.

Tablespaces

This section displays a list of tablespaces in the current database. For each tablespace, the tablespace name and minimum required size is displayed. In addition, a message is displayed if the tablespace is adequate for the upgrade. If the tablespace does not have enough free space, then space must be added to the tablespace in the current database. Tablespace adjustments must be made before the database is upgraded.

Update/Obsolete/Deprecated Parameters

These sections display a list of initialization parameters in the parameter file of the current database that should be adjusted before the database is upgraded. The adjustments must be made to the Oracle Database 10.2 init.ora or spfile.

Components

This section displays a list of database components that are upgraded or installed when the current database is upgraded.

10.7.2.2 Upgrading a Release 10.2 Database

After you install the patch set, you must perform the following steps on every database associated with the upgraded Oracle home:


Note:

If you do not run the catupgrd.sql script as described in this section and you start up a database for normal operation, then ORA-01092: ORACLE instance terminated. Disconnection forced errors will occur and the error ORA-39700: database must be opened with UPGRADE option will be in the alert log.

  1. Log in as the Oracle software owner user.

  2. For Oracle RAC installations, start listener on each node of the cluster as follows:

    $ srvctl start listener -n node

  3. If you are using Automatic Storage Management, start the Automatic Storage Management instance.

  4. For single-instance installations, start the listener as follows:

    $ lsnrctl start

  5. For single-instance installations, use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:

    $ sqlplus /nolog 
SQL> CONNECT SYS AS SYSDBA
Enter password:SYS_password

    Users of single-instance installations now proceed to step 7.

  6. For Oracle RAC installations:

    1. Use SQL*Plus to log in to the database as the SYS user with SYSDBA privileges:

      $ sqlplus /nolog 
SQL> CONNECT SYS AS SYSDBA
Enter password: SYS_password
SQL> STARTUP NOMOUNT

    2. Set the CLUSTER_DATABASE initialization parameter to FALSE:

      SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;

    3. Shut down the database:

      SQL> SHUTDOWN

  7. Enter the following SQL*Plus commands:

    SQL> STARTUP UPGRADE
SQL> SPOOL patch.log
SQL> @?/rdbms/admin/catupgrd.sql
SQL> SPOOL OFF

  8. Review the patch.log file for errors and inspect the list of components that is displayed at the end of catupgrd.sql script.

    This list provides the version and status of each SERVER component in the database.

  9. If necessary, rerun the catupgrd.sql script after correcting any problems.

  10. Restart the database:

    SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP

  11. Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.

    SQL> @?/rdbms/admin/utlrp.sql

    Note:

    When the 10.2.0.4 patch set is applied to an Oracle Database 10g Standard Edition database, there may be 54 invalid objects after the utlrp.sql script runs. These objects belong to the unsupported components and do not affect the database operation.

    Ignore any messages indicating that the database contains invalid recycle bin objects similar to the following:

    BIN$4lzljWIt9gfgMFeM2hVSoA==$0

    12. 

  12. 

    Run the following command to check the status of all the components after the upgrade:
    SQL> SELECT COMP_NAME, VERSION, STATUS FROM SYS.DBA_REGISTRY;

    

    In the output of the preceding command, the status of all the components should be VALID for a successful upgrade.
    13. 

  13. 

    If you are using the Oracle Recovery Manager catalog, enter the following command:
    $ rman catalog username/password@alias 
RMAN> UPGRADE CATALOG;

    14. 

  14. 

    For Oracle RAC installations:
    

      

    1. 

      Set the CLUSTER_DATABASE initialization parameter to TRUE:
       SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile; 

      2. 

    2. 

      Restart the database:
      SQL> SHUTDOWN IMMEDIATE
SQL> STARTUP

      3. 

    3. 

      Start any database services that you want to use:
      $ srvctl start service -d db_name -s service_name

    15. 

  15. 

    To configure and secure Enterprise Manager follow these steps:
    

    Ensure the database and Listener are operational.
    

      

    • 

      In the case of a single instance, execute
      emca -upgrade db

      • 

    • 

      In the case of Oracle Real Application Clusters (RAC), execute
      emca -upgrade db -cluster


            






  





  



  



  




    


    
    


      

      

        
'Admin/admin'의 다른글

        
    
          
  • 
            
          
    • 
          
  • 현재글ORA-00704: bootstrap process failure / ORA-39700
    • 
          
  • 
            
          
    • 
        

      


      
        
        

          
관련글

          
        

        
      

      
      


        

          댓글 
        


        


      

      

    

    

  

      
  
              

              
              
              

              
              
              

              
							

              

              
              
              

              
              
              

              
              
              

              
              
              

            

            

            
            
            

          

          

          
          
          

        

        
      

      

    

    
      
      

    

    
  


  
티스토리툴바