Script to Collect DB Upgrade/Migrate Diagnostic Information (dbupgdiag.sql) [ID 556610.1] -优快云博客

本文链接：https://blog.youkuaiyun.com/leishifei/article/details/6432185

本文介绍了一款用于诊断Oracle数据库升级前后状态的脚本dbupgdiag.sql。该脚本可帮助用户创建诊断日志文件，以便分析升级过程中的变化与潜在问题。适用于Oracle Server Enterprise Edition 9.2.0.1到11.2.0.1版本。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

Script to Collect DB Upgrade/Migrate Diagnostic Information (dbupgdiag.sql) [ID 556610.1]

		Modified 20-JAN-2011 Type SCRIPT Status PUBLISHED

In this Document
  Purpose
  Software Requirements/Prerequisites
  Configuring the Script
  Running the Script
  Caution
  Script
  Script Output
  References

Applies to:

Oracle Server - Enterprise Edition - Version: 9.2.0.1 to 11.2.0.1 - Release: 9.2 to 11.2
Information in this document applies to any platform.
Oracle Server Enterprise Edition - Version: 9.2.0.1 to 11.2.0.1

Purpose

This script is intended to provide a user friendly output to diagnose the status of the database either before (or) after upgrade. The script will create a file called db_upg_diag_<sid>_<timestamp>.log.

Software Requirements/Prerequisites

The script needs to be run in SQL*Plus both before the upgrade on the source database and after the upgrade on the upgraded database as SYS user.

This will help to determine the status of the database before and after upgrade.

Configuring the Script

Download and save the script as dbupgdiag.sql. The script needs no additional configuration.

Running the Script

Connect as sysdba and execute the script

cd <location of the script>
$ sqlplus / as sysdba
sql> alter session set nls_language='American';
sql> @dbupgdiag.sql
sql> exit

Caution

This script is provided for educational purposes only and not supported by Oracle Support Services. It has been tested internally, however, and works as documented. We do not guarantee that it will work for you, so be sure to test it in your environment before relying on it.
Proofread this script before using it! Due to the differences in the way text editors, e-mail packages and operating systems handle text formatting (spaces, tabs and carriage returns), this script may not be in an executable state when you first receive it. Check over the script to ensure that errors of this type are corrected.

Script

Download the script from here

Execute the script before and after upgrade and provide the resultant log files to Oracle Support for analysis purposes.

Script Output

SQL> @dbupgdiag.sql

Enter location for Spooled output as Parameter 1:

Enter value for 1: /tmp

                          *** Start of LogFile ***

  Oracle Database Upgrade Diagnostic Utility       07-01-2008 12:17:30

...
...

Script output
...
...

                             *** End of LogFile ***

Upload db_upg_diag_orcl102_01-Jul-2008_1217.log from "/tmp" directory

To view the Sample log file click here.

References

NOTE:1030426.6 - How to Clean Up Duplicate Objects Owned by SYS and SYSTEM Schema
NOTE:397770.1 - How to Check if the Oracle JVM is Installed Correctly in the Database
NOTE:412271.1 - ORA-600 [22635] and ORA-600 [KOKEIIX1] Reported While Upgrading Or Patching Databases To 10.2.0.3
NOTE:456949.1 - Script to Check the Status of the JVM within the Database
NOTE:579523.1 - ORA-600 [22635], ORA-600 [KOKEIIX1], ORA-7445 [KOPESIZ] and OCI-21500 [KOXSIHREAD1] Reported While Upgrading To 11.1.0.6 Or 11.1.0.7

Attachments

Sample logfile generated by dbupdiag.sql (7.3 KB)

Script to Collect DB Upgrade/Migrate Diagnostic Information (13.28 KB)

Related

Products