Oracle在Linux上如何升级

Oracle Database Upgrade on Linux: A Structured Approach
Upgrading Oracle Database on Linux requires meticulous planning to ensure data integrity and minimal downtime. Below is a comprehensive guide covering key methods, steps, and considerations.

Pre-Upgrade Preparation

Before initiating the upgrade, execute these critical tasks to avoid failures:

• Backup Everything: Use RMAN (BACKUP DATABASE FULL) or expdp/impdp to create a full backup of the database and configuration files (e.g., listener.ora, tnsnames.ora). Verify backup integrity to guarantee recoverability.
• Download New Software: Obtain the Oracle Database binaries for your target version from the official website. Ensure compatibility with your Linux distribution (e.g., Oracle Linux 8/9) and architecture (x86_64).
• Install Dependencies: Install required Linux packages (e.g., libaio, libaio-devel, gcc, glibc) using yum or dnf. These are essential for Oracle software installation.
• Check System Requirements: Validate that your Linux system meets the target Oracle version’s hardware/software prerequisites (e.g., memory, disk space, kernel parameters). Adjust parameters (e.g., shmmax, semmsl) in /etc/sysctl.conf if needed.
• Stop Database Services: Shut down all Oracle-related services to prevent data corruption:

  sudo systemctl stop oracle  # Stop Oracle service
  lsnrctl stop              # Stop listener
  sqlplus / as sysdba <<EOF
  SHUTDOWN IMMEDIATE;
  EOF
  

• Set Environment Variables: Configure Oracle-specific variables in the oracle user’s .bash_profile (or equivalent):

  export ORACLE_BASE=/u01/app/oracle
  export ORACLE_HOME=$ORACLE_BASE/product/<target_version>/dbhome_1
  export ORACLE_SID=<your_sid>
  export PATH=$ORACLE_HOME/bin:$PATH
  source ~/.bash_profile  # Apply changes
  

Choosing an Upgrade Method

Oracle offers multiple upgrade paths. Select the one that aligns with your environment and expertise:

1. AutoUpgrade Utility (Recommended)

The most efficient method for automating pre-upgrade checks, execution, and post-upgrade tasks. Ideal for large-scale or complex upgrades.

• Steps:
  • Download autoupgrade.jar from My Oracle Support (Doc ID 2485457.1).
  • Create a configuration file (e.g., upgrade.json) specifying source/target versions, Oracle home paths, and database details.
  • Run the utility:

    java -jar autoupgrade.jar -config upgrade.json -mode analyze  # Simulate upgrade
    java -jar autoupgrade.jar -config upgrade.json -mode upgrade   # Execute upgrade
    

  • Review logs ($ORACLE_HOME/cfgtoollogs/autoupgrade) for errors.
• Benefits: Parallel processing, automated fixup scripts, and support for CDB/PDB conversions.

2. Command-Line Upgrade (Parallel Upgrade Utility)

Offers manual control and parallel processing for experienced DBAs. Suitable for custom upgrade paths or environments where GUI tools are unavailable.

• Steps:
  • Pre-Upgrade Check: Run the Pre-Upgrade Information Tool (preupgrade.jar) to identify issues:

    java -jar $ORACLE_HOME/rdbms/admin/preupgrade.jar -db <ORACLE_SID> -output_dir $ORACLE_HOME/cfgtoollogs/preupgrade
    

    Address warnings/errors in the generated report.
  • Run Upgrade: Use catctl.pl to start the parallel upgrade (adjust parallel threads with -n):

    cd $ORACLE_HOME/rdbms/admin
    ./catctl.pl -d $ORACLE_HOME/dbs -l $ORACLE_HOME/cfgtoollogs/upgrade -n 4 catupgrd.sql
    

  • Post-Upgrade Tasks: Recompile invalid objects (utlrp.sql), run post-upgrade fixups (if any), and verify version:

    sqlplus / as sysdba <<EOF
    SELECT * FROM v$version;
    @?/rdbms/admin/utlrp.sql  # Recompile invalid PL/SQL
    EOF
    

3. Database Upgrade Assistant (DBUA)

A GUI-based tool for step-by-step upgrades. Best for DBAs preferring a visual workflow or first-time upgrades.

• Steps:
  • Launch DBUA from the Oracle home directory:

    cd $ORACLE_HOME/bin
    ./dbua
    

  • Follow the wizard: select the source database, target version, and configure options (e.g., character set, ASM).
  • DBUA automates pre-upgrade checks, execution, and post-upgrade tasks.
• Limitations: Less flexible than command-line methods; requires access to the source Oracle home.

4. Data Pump Export/Import

A data migration approach for upgrading between major versions or when in-place upgrades are not feasible.

• Steps:
  • Export data from the source database:

    expdp system/password@source_db FULL=Y DIRECTORY=DATA_PUMP_DIR DUMPFILE=full_export.dmp LOGFILE=export.log
    

  • Install the target Oracle version on Linux (new Oracle home).
  • Import data into the target database:

    impdp system/password@target_db FULL=Y DIRECTORY=DATA_PUMP_DIR DUMPFILE=full_export.dmp LOGFILE=import.log
    

• Considerations: Longer downtime than in-place upgrades; requires additional storage for dump files.

Post-Upgrade Validation

After the upgrade, perform these checks to ensure success:

• Verify Version: Confirm the database is running the target version:

  sqlplus / as sysdba <<EOF
  SELECT * FROM v$version;
  EOF
  

• Check Component Status: Ensure all database components (e.g., OLAP, Spatial) are valid:

  SELECT COMP_NAME, VERSION, STATUS FROM SYS.DBA_REGISTRY;
  

  All entries should show VALID.
• Recompile Invalid Objects: Run utlrp.sql to recompile any remaining invalid PL/SQL objects.
• Test Functionality: Validate critical applications, backups (RMAN), and performance benchmarks.
• Review Logs: Check $ORACLE_HOME/cfgtoollogs for upgrade errors or warnings.

Key Considerations

• Compatibility: Ensure the target Oracle version supports your Linux distribution (e.g., Oracle 19c/21c/23c for Oracle Linux 8/9).
• Downtime Planning: Schedule upgrades during maintenance windows to minimize impact.
• Testing: Always test upgrades in a non-production environment to identify potential issues.
• Rollback Plan: Keep the source database intact until the upgraded environment is verified.

By following these steps and leveraging Oracle’s recommended tools (e.g., AutoUpgrade), you can achieve a smooth and reliable upgrade of Oracle Database on Linux.