Upgrade Oracle 11.2.0.1 to Oracle11.2.0.4 under Centos7.0
Background : system x86_64; Oracle software does not install grid, asm, and rac; there are two instances running on the machine (corresponding to two databases)
Prepare :
Download p13390677_112040_Linux-x86-64_1of7.zip ; p13390677_112040_Linux-x86-64_2of7.zip , upload the two files to centos7.0, unzip, enter the databse folder, and run runInstaller
Start :
Pre1. It is recommended to install to another path in step 6, so that you can still use the original software to start the original oracle databse losslessly after the upgrade error;
Pre.2 If necessary, you can back up databse first, set databse to read-only mode, and empty the recycle bin to speed up the upgrade;
Do not make a mistake in the order of Step 3 and Step 4 in Pre.3, otherwise you may not be able to search for other databases (for example, the database is moved in Step 10.3.5);
Finally, similar to the installation process, the entire upgrade process is divided into two parts: the first part upgrades the software; the second part upgrades the database. In addition, at the end of this article, it also records how to upgrade the second database after the upgrade, check all the upgrade-related tasks such as monitoring and configuration of environment variables, until the database can be accessed normally remotely.
1. Upgrade software
Step1
Uncheck i wish..., next
Click Yes
Step2
Since there is no OS account, choose Skip...,next
Step3
Choose upgrade..., next
Step4
Select the language to run oracle database, next
Step5
Choose enterprise..., next
Step6
The software installation path is modified to 11.2.0.4 (the advantage is that the upgrade error occurs, and the original software can still be used to start the original database without loss), next
Step7
If the oper group is configured, please choose to regroup. I did not configure it when installing oracle db, so I chose the dba group, next
Step8
Check dependent parameters or packages. If the package parameters are wrong or the package cannot be fixed automatically, you need to manually download the package or modify the parameter fixed
Step9
After checking in Step8, automatically enter step9, click install
Step10
Start to upgrade software
Among them, encountered an error:
Solution:
The / opt / the Oracle / Product / 11.2.0.4 /sysman/lib/ins_emagent.mk file $ (MK_EMAGENT_NMECTL) amended as: $ (MK_EMAGENT_NMECTL) -lnnz11; click on the "retry".
Step10.1
Follow the prompts to execute the script, enter all y to rewrite
Step10.2
Custom configuration monitoring, service, next
Next
Click ok, modify the monitor name, next
Next
The production library recommends not to use the default port, modify it to 15021, next
Select no no longer configure monitoring, click next
Select start the newly configured monitor, next
The monitoring configuration is complete, next
Do you want to configure tnsname.ora? Choose no, (you will modify the file or netmgr configuration later), next
At this point, Step10.2 Netca configuration is complete, click Finish
At this point, the database software upgrade is completed, and the database upgrade is performed below.
Two, upgrade the database
Step10.3.1
Click Next
Step10.3.2
Select the database to be upgraded, next
Note: Only one database can be upgraded at a time, and the dbua upgrade can be run after the upgrade is complete.
Step10.3.3
Click yes
Step10.3.4
Select all, click next
Step10.3.5
Move database...，next
Step10.3.6
Not equipped with asm, so choose use common..., next
Note: If you did not select move database in the previous step, you can add the 11.2.0.4 folder to store data under the original path in this step to avoid overwriting the original data. This article operates as shown in the figure above.
Step10.3.7
Set up quick recovery area, next
Step10.3.8
Choose which one or all of the monitors to register to the oracle system, I choose the newly configured LSNR, next
Step10.3.9
Display related configuration information, finish
Step11
Start to upgrade the database
Go to the figure below, the data upgrade is complete, click ok
Upgrade results, the steps can be configured database passwords and restore database (restore to the old version of the database), click close to complete
Click close to end
-
Upgrade the second database
Run /opt/oracle/product/ 11.2.0.4 /bin/dbua under the Oracle account , select the database to be upgraded, and repeat the steps in the second part.
-
Configure environment variables
Under the oracle account:
1.[oracle@localhost ~]$ cd ~
2.[oracle@localhost ~]$ vi .bash_profile
Modify ORACLE_HOME to the upgraded path, see Step6 in this article: ORACLE_HOME=/opt/oracle/product/11.2.0.4
- [oracle@localhost ~]$ source .bash_profile
-
Check whether it works
[oracle@localhost ~]$ echo $ORACLE_HOME
/opt/oracle/product/11.2.0.4
-
sqlplus / as sysdba login to check if it is version 11.2.0.4
As shown in the figure above, the 11.2.0.4 database is opened using 11.2.0.1 software. Description .bash_profile is not effective. Execute exec bash --login under /home/oracle to log in again with sqlplus / as sysdba
As above, use 11.2.0.4software to open 11.2.0.4database successfully
Make sure that this step is completed normally. If it does not work, please close all instances before executing the command to make .bash_profile effective.
-
Check whether the database and monitoring are normal
Check monitoring:
It shows that the old listening file is still used (although it does not affect the use of data, it is recommended to modify the listening file under the path of the new version). Check whether the updated software generates a monitoring file, and check the host name (used for new monitoring):
The database can still be opened using the old listening file
No monitoring file (Note: The 10.3.8 registration seems to be registered in the old monitoring file, I didn't pay much attention), and the oracle account executes netmgr and creates a new monitoring:
Set the listener name
New listening address
Fill in the hostname and modify the listening port
Configure service for catdb and vxdb respectively
Save network configuration
Click X in the upper right corner to close
Execute lsnrctl reload to reload the listening file
Execute lsnrctl stop to close the monitor
Execute lsnrctl start to start monitoring
Execute lsnrctl status to view the monitoring status
Status is UNKNOWN, indicating that the monitoring is static registration
-
carry out
Remote connection test:
Both instances are successfully connected.
At this point, all configurations are complete, and the oracle database upgrade is complete.
