Normal
0
21
false false false
MicrosoftInternetExplorer4
/ * Style Definitions * / table.MsoNormalTable {mso-style-name: "Table Normal" mso-tstyle-rowband-size: 0; mso-tstyle-colband-size: 0; mso-style-noshow: yes; mso-style-parent: "" mso-padding-alt: 0in 5.4pt 0in 5.4pt; mso-para-margin: 0in; mso-para-margin-bottom: .0001 pt; mso-pagination: widow-orphan; font -size: 10.0pt; font-family: "Times New Roman" mso-ansi-language: # 0400; mso-Fareast-language: # 0400; mso-bidi-language: # 0400;}
To update ( upgrade) a version of an Oracle based mainly four methods:
Use Chart Wizard (DBUA). Is the method suggested in the manuals.
Use scripting or manually (which I always tend to use)
Export / Import
CTAS (in my opinion the most complicated, create dblink, build scripts for the transfer of objects, etc)
This paper
I'll write a step by step procedure to update using the manual method (the 2 listed above):
Pre-Upgrade
1. If the upgrade is on the same team would have to install the software (the motor) 11g in a new home. You can use the same user oracle stream 10g installation and setup environment variables for 11g or you could use a new oracle user (eg Oracle11g).
2. After installing the software the user to connect to oracle 11g installation and copy the file
$ ORACLE_HOME/rdbms/admin/utlu112i.sql to a shared directory (ie / tmp).
3. Users connect to the 10g (eg Oracle) or if using the same user setear environment variables to use the 10g motor to run the script you copied in step 2. This script provides information prior to the upgrade to be used for preparing the current version there are no problems during the upgrade
4. Connect to sqlplus:
$ sqlplus / As sysdba
5. Setear the spool so there is no record of the script
sqlplus> spool upg_info.log
6. Run the script: sqlplus
> @ / tmp/utlu112i.sql;
7. Turn off the spool:
sqlplus> spool off
Example Output Report pre-upgrade information
Below is a typical output of the script on a database called utlu112i.sql ROP10g on a Solaris machine 10.
Oracle Database 11.2 Pre-Upgrade Information Tool 07-26-2010 15:14:36
**********************************************************************
Database:
**********************************************************************
--> name: ROP10G
--> version: 10.2.0.4.0
--> compatible: 10.2.0.1.0
--> blocksize: 8192
--> platform: Solaris[tm] OE (64-bit)
--> timezone file: V4
**********************************************************************
Tablespaces: [make adjustments in the current environment]
--> TEMP tablespace is adequate for the upgrade.
**********************************************************************
--> SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 313 MB
.... AUTOEXTEND additional space required: 83 MB
--> UNDO tablespace is adequate for the upgrade.
.... minimum required size: 121 MB
--> SYSAUX tablespace is adequate for the upgrade.
.... minimum required size: 73 MB
.... AUTOEXTEND additional space required: 23 MB
.... minimum required size: 61 MB
**********************************************************************
**********************************************************************
Update Parameters: [Update Oracle Database 11.2 init.ora or spfile]
**********************************************************************
WARNING: --> "sga_target" needs to be increased to at least 672 MB
Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile]
Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile]
**********************************************************************
-- No renamed parameters found. No changes are required.
**********************************************************************
**********************************************************************
--> "background_dump_dest" replaced by "diagnostic_dest"Components: [The following database components will be upgraded or installed]
--> "user_dump_dest" replaced by "diagnostic_dest"
--> "core_dump_dest" replaced by "diagnostic_dest"
**********************************************************************
**********************************************************************
--> Oracle Catalog Views [upgrade] VALID
--> Oracle Packages and Types [upgrade] VALID **********************************************************************
Miscellaneous Warnings
.... USER SYS has 2 INVALID objects.
Controls are performed with the pre-upgrade tool
invalid objects.
Check if the configuration of SGA meets the minimum requirements in 11g.
- Check if database links with passwords (11g encrypts passwords).
- ensures that there are files that need recovery.
- ensures that there are files in backup mode.
- If the check is enabled RecycleBin if empty (if this completely purged).
Check if timezone files are of type 4 (the files are in $ ORACLE_HOME / oracore / zoneinfo).
Checks for Materialized Views drinks outstanding.
Checks for pending distributed transactions. Once corrected the warnings reported by the previous script can proceed with the upgrade
1. Connect with the owner (user oracle) 10g instance.
1.1 Check that all the processes with the same oracle instance name
$ ps-ef
sqlplus> shutdown transactional
5. If the database is on another computer 11g is to transfer the database files (datafiles, redologs, ControlFiles) to the new computer in the same directory with the same permissions (using unix command scp, ftp, copying any logical mechanism groups, etc). If you perform the upgrade on the same computer and on the same database files do not need to do anything at this point.
6. Connect to the 11g instance with SYSDBA
$ sqlplus / as sysdba
7. Lift 11g database upgrade mode
SQPLUS> STARTUP UPGRADE
8.
9. Run the script to get the pre-upgrade information
SQLPLUS> @? / Rdbms / admin / catupgrd.sql;
10. Disable spooling
SQLPLUS> spool off
11. Utlu112s.sql run the script to see the result of the upgrade.
SQLPLUS> @? / Rdbms/admin/utlu112s.sql
12. Run script to recompile stored procedures utlrp.sql and java classes.
i)
SQLPLUS> @? / Rdbms / admin / utlrp.sql
ii)
SQLPLUS> exec UTL_RECOMP.RECOMP_SERIAL ();
13. Check that all the packages and classes were compiled java
SQLPLUS> select count (1) from dba_invalid_objects.
14. Create spfile from pfile original.
SQLPLUS> create spfile from pfile;
15. Restart the instance normally.
Example Output Report post-upgrade information
Next shows a typical output of the script utlu112i.sql on a team called ROP10g on Solaris 10
SQL> @? / rdbms/admin/utlu112s.sql;
Oracle Database 11.2 Post-Upgrade Status Tool 07-26
14:32:12 -2010
Component Status Version HH: MM: SS Oracle Server
VALID 11.2.0.1.0 00:24:02 Gathering Statistics
.
00:01:32 Total Upgrade Time: 00:25:36
PL / SQL procedure successfully completed.
Post-Upgade
1. Analyze case-sensitive password
SQLPLUS> alter system set SEC_CASE_SENSITIVE_LOGON = false scope = both;
Ideally leave this parameter to true (default), as it strengthens security, but should analyze how some applications ( for example some versions of TOAD can not connect)
2. Setear the COMPATIBLE parameter to 11.2.0
SQLPLUS> alter system set compatible = '11 .2.0 'scope = spfile;
3. Enable thresholds for alerts on tablespaces.
4. Restart the instance
5. Check connection through the listener
6. Depending on the type of backup and use the tool that is sometimes necessary to change the internal identification of the base to be taken as a new base
How to Change the dbid:
SQLPLUS> shutdown Immediate
SQLPLUS> startup
mount
$ nid TARGET = SYS
SQLPLUS> startup mount
SQLPLUS> alter database open RESETLOGS Backup
6 full data base.
0 comments:
Post a Comment