Any piece of software has errors. It’s just a fact of life.
Should you encounter problems with AutoUpgrade, you can help us by compiling a zip package. This package contains valuable information that we need to troubleshoot.
Are You Using the Latest Version
- Before generating a zip package, check that you’re using the latest version of AutoUpgrade… Perhaps the issue is already fixed:
java -jar autoupgrade.jar -version - Check the latest version on oracle.com or AutoUpgrade Tool (Doc ID 2485457.1).
- Or, simply get the latest version, and compare:
wget https://download.oracle.com/otn-pub/otn_software/autoupgrade.jar java -jar autoupgrade.jar -version
How To Generate a Zip Package
- You add
-zipto the AutoUpgrade command that failed. - You remove all other parameters except
-config. - Execute the command:
java -jar autoupgrade.jar -config db19.cfg -zip - AutoUpgrade generates a zip package in the current directory and outputs the name of the file in the console.
- You can specify the directory using
-d <dir>.
- You can specify the directory using
What Does It Contain?
It contains:
- All the files from the following locations:
global.global_log_dirglobal.autoupg_log_dir<prefix>.log_dir
- Database alert log
- Data Guard broker log
- Attention log
When creating the zip package, AutoUpgrade doesn’t connect to the database but gathers the information from the file system.
If there are files that you don’t want to include in the package, you can exclude them using -zip_exclusion_list. Check the documentation for details.
One thought on “AutoUpgrade Never Fails, But When It does”