Alok Giri Oracle

AG Upgrade 9i to 11g (Manually) The following for upgrading a 9.2.0.8 DB to 11.2 version on Solaris Required packges for installing 11g software: (see equivalent)   -------------------------------------------- unixODBC-devel-2.2.11 libaio-devel-0.3.105   elfutils-libeif-devel-0.97 gcc.. .. etc Install 11g software in new ORACLE HOME... /apps/oracle/product/db11gR2 happens to be mine.. Note ID: 429825.1 Database Upgrade steps from 9i to 11g: -------------------------------------------------------- Step 1: ------- Log in to the system as the owner of the new 11gR2 ORACLE_HOME and copy the following files from the 11gR1 ORACLE_HOME/rdbms/admin directory to a directory outside of the Oracle home, such as the $HOME/migration in my case: mkdir $HOME/migration cp $ORACLE_BASE/product/db11gR2/rdbms/admin/utlu11*i.sql $HOME/migration cp $ORACLE_BASE/product/db11gR2/rdbms/admin/utltzuv2.sql $HOME/migration Step 2: ------- $ sqlplus "/ as sysdba" SQL...

Upgrading to Oracle Database 11g Compatibility Matrix Minimum Version of the database that can be directly upgraded to Oracle 11g Release 1 The following database version will require an indirect upgrade path. This post is about upgrading the Oracle database from 10g to 11g. This post is based on metalink note ID 429825.1 Below steps are the one which are tried and successfully implemented on linux RHEL 4. For Oracle database 10g, we need REHL 3, but for 11g version the minimum OS level for linux is RHEL 4. I have given the list of patches for RHEL 3.0 and RHEL 4.0 PACKAGES Red Hat Enterprise Linux 3.0 and Asianux 1.0: make-3.79.1 gcc-3.2.3-34 glibc-2.3.2-95.20 compat-db-4.0.14-5 compat-gcc-7.3-2.96.128 compat-gcc-c++-7.3-2.96.128 compat-libstdc++-7.3-2.96.128 compat-libstdc++-devel-7.3-2.96.128 openmotif21-2.1.30-8 setarch-1.3-1 Red Hat Enterprise Linux 4.0 and Asianux 2.0: binutils-2.15.92.0.2-13.EL4 compat-db-4.1.25...

Step 1:   Create stream administration user in both databases. create user streamadmin identified by streamadmin default tablespace users; Step 2:   Required grants to the user streamadmin. grant dba,select_catalog_role to streamadmin; exec dbms_streams_auth.grant_admin_privilege('streamadmin',true); Step 3:   We will use default SCOTT schema for seting up this replication. Step 4:   Check database paramters required for setting up stream replication For our example: DB 1: Name: TEST1 Global Name should be true SQL> show parameter global_name NAME TYPE VALUE ------------------------------------ ----------- -------------------------- global_names boolean TRUE SQL> select * from global_name; GLOBAL_NAME ----------------------------------------------- TEST1.REGRESS.RDBMS.DEV.US.ORACLE.COM SQL> show parameter job_queue NAME TYPE VALUE ------------------------------------ ----------- ------ job_queue_processes integer 10 SQL> ...

Manual upgrade from 9i to 10g Release 2 This procedure describes the steps necessary to manually upgrade a database from 9.2.x to 10.2.x. It assumes that you have already installed 10g onto the server. Of course, it is essential that you take a backup of your database before attempting any upgrade. 1. Compile any invalid objects @?/rdbms/admin/utlrp.sql 2. Create a sysaux tablespace Having a sysaux tablespace is a requirement in 10g. So, if you haven't already got one, create one now. create tablespace sysaux datafile '<file_name>' size 512M extent management local segment space management auto / 3. Run utlu102i.sql This utility script checks that the database is ready to be upgraded to 10g. It also identifies any actions that need to be taken. The script is located in the 10g oracle home, so you will need to specify the full path to it. @/u01/app/oracle/product/10.2.0/db_1/rdbms/admin/utlu102i.sql Review the output and make any necessary alterations. Make a note of ...

DG Broker setup by Alok Primary Database: prim_alok Standby Database: stanby_alok On both Primary as well as Standby database start the Data Guard Broker process SQL> ALTER SYSTEM SET DG_BROKER_START=TRUE SCOPE=BOTH;   System altered. Edit the listener.ora on both nodes to add a static entry for DGMGRL This is to prevent the ORA-12154 error which can be observed on startup of the standby database after performing a switchover. Ensure that the GLOBAL_DBNAME is set to db_unique_name_DGMGRL.db_domain SID_LIST_LISTENER =   (SID_LIST = (SID_DESC =         (GLOBAL_DBNAME = prim_alok_dgmgrl)         (ORACLE_HOME = /u01/oracle/product/11.1.0/db_1)         (SID_NAME = genoa1)         ) ) Create the configuration genoa1:/u01/oracle> dgmgrl DGMGRL for IBM/AIX RISC System/6000: Version 11.1.0.7.0 - 64bit Production   Copyright (c) 2000, ...