Monday, 29 June 2015

Oracle Database Upgrade step by step 11gR1 to 11gR2

Oracle Database Upgrade Process

1) Must install the new Oracle version in separate ORACLE_HOME to which we are upgrading the database.

2)  Both the old Oracle Version and New/Upgraded Oracle Version software must be installed properly before starting the upgrade.

3)  Take the backup of database before starting the upgrade.

4)  Before starting the upgrade Run the pre upgrade script from new ORACLE_HOME/rdbms/admin

utlu112i.sql      11.2

5)  Run the database upgrade from New Oracle Home using

DBUA  or catupgrd.sql  (Manual Upgrade )

6)      Once the upgrade is complete validate the upgrade using Post Upgrade Script  from new ORACLE_HOME/rdbms/admin/

utlu112s.sql      11.2

Step:-1

My 11gr1 or 11gr2 Oracle_home path

11gr1 ORACLE_HOME=/u01/app/oracle/product/11gr1

11gr1 ORACLE_SID=orcl

11gr2 ORACLE_HOME=/u01/app/oracle/product/11gr2

Step:-2
Preupgrade steps :- 

Run the utlu112i.sql in 11GR1 oracle home.
Copy the preupgrade script to any temp location for example /u01/app/oracle
cp /u01/app/oracle/product/11gr2/rdbms/admin/utlu112i.sql /u01/app/oracle
cd /u01/app/oracle
export ORACLE_HOME=/u01/app/oracle/product/11gr1
export ORACLE_SID=orcl
If you are upgrading to 11gr2 run below script
@utlu112i.sql

SQL> @/u04/app/cognos/product/11.2.0/dbhome_2/rdbms/admin/utlu112i.sql

Step:-3
Purge recyclebin of database. 
 SQL> PURGE DBA_RECYCLEBIN;

           DBA Recyclebin purged.

Step:-4
Gather Schema and Database statistics

 SQL> EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;

           PL/SQL procedure successfully completed.

Step:-5
 SQL> EXEC DBMS_STATS.GATHER_SCHEMA_STATS('SYS');

           PL/SQL procedure successfully completed.


 SQL> !

Step:-6

Shutdown 11gr1 database.

 SQL> shut immediate

Step:-7

Take a complete  backup of datafiles,controlfiles, redo logfiles, Spfile/pfile and password file.

The complete backup of database is needed to revert back if the Database upgrade fails.

Step:-8
Upgrading Database to 11GR2 
Below we are spooling to a log file so that we have the pre upgrade validations stored in upgrade_info.log file that we can refer later.
sql>      spool upgrade_info.log
sql>      @utlu112i.sql
sql>      spool off
The Pre upgrade script suggest any database changes that needs to be done before starting the Database Upgrade using DBUA or catupgrd.sql Script.
The pre upgrade script validates following information:
  • Database version.
  • Tablespace sizes.
  • Updated, renamed and deprecated initialization parameters.
  • Init.ora or Spfile Parameters that needs to be resize before starting the actual upgrade. ( This step should not be ignored)
  • Database Components that will be upgraded or installed
  • SYSAUX tablespace present (if missing).
  • Miscellaneous Warnings
    • Warning for Old Timezone
    • Warning for Stale Optimizer Statistics
    • Warning for EM Database Control Repository
Note: Each of the warning suggested by Pre Upgrade tool must be fixed.
Fix all the issues reported by Pre-upgrade script before starting DBUA
Step:-5
(Two Methods to do the actual Database Upgrade, either use DBUA
or catupgrd.sql (manual method)  which has many steps but it is more flexible)
Oracle recommends using DBUA to upgrade database.
export ORACLE_SID=orcl
Run the DBUA from New 11gr2 ORACLE_HOME/bin
$ cd /u01/app/oracle/product/11gr2/bin
$./dbua
Once the DBUA (Database Upgrade Assistant) GUI starts. Follow below points to upgrade the database. DBUA takes about 60 minutes to complete even for very large databases.
  • Select the Database that needs to be upgraded.
  • If the database name that needs to be upgraded is not present in DBUA,
Add the entry $ORACLE_SID:$ORACLE_HOME:N to /etc/oratab
For Example: ora11g:/u01/app/oracle/product/orcl:N
Note: The $ORACLE_HOME should be the old oracle home that is getting  upgraded.
  • Oracle 11g requires the “Diagnostic Destination”. Set diagnostic destination to oracle base.
  • Select “Do not move Database as part of upgrade”
  • Do not specify Flash Recovery Area option
  • Select “Configure database with Enterprise Manager” or Database Control if required.
  • Select “Recompile Invalid objects at the end of upgrade” options in dbua
  • Do not select the backup option if we have already have taken backup before starting Database Upgrade, Also it is not needed if we already have RMAN backup.
Step:-6

 Post Upgrade Steps
Once the upgrade is complete modify the profile file to use the new ORACLE_HOME
Run the post upgrade script to validate the upgrade using new ORACLE_HOME
SQL> @$ORACLE_HOME/rdbms/admin/utlu112s.sql
SQL> @/u01/app/oracle/product/11gr2/rdbms/admin/utlu112s.sql
SQL> select * from v$version;

BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
PL/SQL Release 11.2.0.1.0 - Production
CORE    11.2.0.1.0      Production
TNS for Linux: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production

****************************END***********************************









Thursday, 25 June 2015

ORA-19575

ORA-19575 During RMAN Backup (Doc ID 1518129.1)

APPLIES TO:

Oracle Server - Enterprise Edition - Version 11.1.0.7 and later
Information in this document applies to any platform.

GOAL

No problem with RMAN execution, just error derived from corrupted archivelog, which RMAN will not backup.
ORA-19575, 00000, "expected %s blocks in file %s, found %s"
// *Cause:  During a backup, restore, copy, or scan operation, the indicated
//          file did not contain as many blocks as were indicated in the file
//          header.
// *Action: The input copy or backup piece is probably corrupt.  If another
//          backup or copy exists of the file that is being restored, then the
//          corrupt file can be deleted from the recovery catalog and the
//          operation can be restarted.


Archivelog dirictory got full, so some archivelogs have been moved to another directory. In the process of moving in and out of the archivelog dir, one archivelog got
corrupted and now RMAN is reporting errors during the backup of the archived redologs.

How to get past this archivelog and astablish a new restore point past this file.

FIX

1) Validate all archivelogs for corruption:
RMAN> validate archivelog all;

2) Move any corrupted archivelog to a temporary directory using an operating system command such as cp
For example:
$ mv /opt/app/oracle/oradata/ORA112/archivelog/2013_01_11/o1_mf_1_84_8gyj98c3_.arc /tmp/.

3) Then run a crosscheck command to update RMAN's repository. Any files that have been moved will now be marked as expired and RMAN will no longer attempt to back them up.
RMAN> crosscheck archivelog all;


4) You can then proceed to take a full database and archivelog backup.
WARNING !!!! Any archivelogs that are corrupted cannot be used for recovery, so the recoverability of the database is comprimised.

disable 'Transparent Huge Pages (THP)' for Oracle Linux 6.5


 Disable Transparent Huge Pages (THP)

When installing Ambari on CentOS6.x using the Cluster Installer Wizard at the Host Checks step, one or more host checks may fail if you have not disabled Transparent Huge Pages on all hosts. Host Checks warns you when a failure occurs. To disable THP:

Add the following command to your /etc/rc.local file:

RHEL6.5

if test -f /sys/kernel/mm/redhat_transparent_hugepage/defrag; then echo never > /sys/kernel/mm/redhat_transparent_hugepage/defrag fi
SLES

if test -f /sys/kernel/mm/transparent_hugepage/defrag; then echo never > /sys/kernel/mm/transparent_hugepage/defrag fi
To confirm, reboot the host. Then, run the following command:

$ cat /sys/kernel/mm/transparent_hugepage/enabled always madvise [never]

Wednesday, 24 June 2015

RC-50014: Fatal: Execution of AutoConfig was failed

AutoConfig is exiting with status 29

ERROR: RC-50014: Fatal: Execution of AutoConfig was failed
Raised by oracle.apps.ad.clone.ApplyApplTop

END: Executed runAutoConfig...

START: Executing /u02/apps/fs1/inst/apps/PREPROD_chintels/admin/install/txkWfClone.sh -nopromptmsg
txkWfClone.sh exited with status 127
ERROR: txkWfClone.sh execution failed, exit code 127

When Runing adconfig.sh on apps tier after clone some time this error.
[AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution. Errors are grouped by directory and phase.
The report format is:
<filename> <phase> <return code where appropriate>
REASON :
1. Received the following error running Autoconfig:
[AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution.  Errors are grouped  by directory and phase.
The report format is:
      <filename>  <phase>  <return code where appropriate>
  [SETUP PHASE]
  AutoConfig could not successfully execute the following scripts:
    Directory: /apps/ifswmisc/common/admin/install/MISC_findvcl2
      txkWfClone.sh           INSTE8_SETUP       1

2. The adconfig.log shows txkWfClone.sh errors with the following:
ERROR at line 1:
ORA-06550: line 10, column 7:
PLS-00201: identifier 'WF_CLONE.DETERMINECLONE' must be declared
ORA-06550: line 10, column 3:
PL/SQL: Statement ignored


CAUSE:

This error means one of the following:
(a) WF_CLONE pkg and/or pkg body doesn't exist in the db or is invalid
or
(b) The DETERMINECLONE method/procedure doesn't exist within WF_CLONE pkg/pkg body.

(c) Some time Permission issue

Solution
1. Please verify if WF_CLONE is valid in the database. If it is not, please
recompile it.
2. If the actions in #1 do not resolve the issue, then do the following:
a. Run the following SQL query:

SQL> select text
2 from all_source
3 where name = 'WF_CLONE' and line < 7;

b. Go to the $FND_TOP/patch/115/sql directory and obtain the version of wfclones.pls
and wfcloneb.pls.
c. Compare the two versions. If they are different, then go to the
$FND_TOP/patch/115/sql directory and recreate the spec/body by running:

- sqlplus apps/<passwd> @WFCLONES.pls
- sqlplus apps/<passwd> @WFCLONEB.pls

3. Rerun AutoConfig.

RC-50013: Fatal: Failed to instantiate driver regclone.drv on R12.2.4

R12 Cloning 'adcfgclone.pl appsTier' fails with error RC-50013: Fatal: Failed to instantiate driver .../regclone.drv (Doc ID 725995.1)

Log file detailed:-
AutoConfig is exiting with status 1

ERROR: RC-50013: Fatal: Instantiate driver did not complete successfully.
/u02/apps/fs1/EBSapps/10.1.2/appsutil/driver/regclone.drv

ERROR: RC-50004: Fatal: Error occurred in ApplyAppsTechStack:


RC-50013: Fatal: Failed to instantiate driver /u02/apps/fs1/EBSapps/10.1.2/appsutil/driver/regclone.drv

APPLIES TO:

Oracle Applications Manager - Version 12.0.6 to 12.1.3 [Release 12 to 12.1]
IBM AIX on POWER Systems (64-bit)
HP-UX Itanium (32-bit)
***Checked for relevance on 10-Dec-2013*** 

SYMPTOMS

When attempting to clone using "perl adcfgclone.pl appsTier"
The following error occurs:

...
  /      3% completed       RC-50004: Fatal: Error occurred in ApplyAppsTechStack:
RC-50013: Fatal: Failed to instantiate driver <10.1.2 ORACLE_HOME>/appsutil/driver/regclone.drv

ERROR while running Apply...
<Date Time>

 ERROR: Failed to execute <$COMMON_TOP>/clone/bin/adclone.pl
...

In the logfile $INST_TOP/admin/log/ApplyAppsTier_<DATE_TIME>.log following details are reported :

...

script returned:
****************************************************
Timed out( 3750000 ): Interrupted Exception

Beginning OUI CLI cloning for s_tools_oh <Date Time>
<10.1.3 ORACLE_HOME>/jdk/bin/java -classpath <COMMON_TOP>/clone/jlib/java:<10.1.2 ORACLE_HOME>/oui/jlib/OraInstaller.jar:<COMMON_TOP>/clone/jlib/xmlparserv2.jar:<COMMON_TOP>/clone/jlib/ojdbc14.jar  oracle.apps.ad.clone.util.OracleHomeCloner  -OUICLI -e  <INST_TOP>/appl/admin/<CONTEXT_NAME>.xml -nolink -oaVar s_tools_oh -homestub tools -log <INST_TOP>/admin/log/ohclone.log
running OUI CLI home cloning:
<10.1.2 ORACLE_HOME>/oui/bin/runInstaller -debug -clone -silent -force -nolink -waitForCompletion -invPtrLoc /var/opt/oracle/oraInst.loc session:ORACLE_HOME=/<10.1.2 ORACLE_HOME> oracle.as.j2ee.top:s_asInstanceName=<SID>_TOOLS__apps_oracle_apps_tech_st_10_1_2 oracle.as.j2ee.top:s_adminName=ias_admin oracle.as.j2ee.top:s_adminPassword=welcome ORACLE_HOME_NAME=<SID>_TOOLS__apps_oracle_apps_tech_st_10_1_2 -J-Doracle.installer.noLink=true

...

CAUSE

During the Configuration of the APPS-Tier Technology Stack the opmn process tries to stop the Services. As opmn is not used in this case for the 10.1.2 ORACLE_HOME it should not have been started. The OUI (Oracle Universal Installer) is waiting for a failure or error of the opmn, which is not happening. As a result the OUI Cloning process is failing with a timeout, without touching the Technology Stack.

This issue is reported in unpublished Bug 5697740 - 'OPMN START FAILED DURING OH10.1.2 CLONING.'

SOLUTION

To implement the solution/workaround, please execute the following steps :

Workaround 1 :
1. Start the adcfgclone again :
1. Start the adcfgclone again :
2. When it appears to hang again, check if opmn processes have been started :
ps -ef | grep opmn
If following result is presented, please follow next steps :
<user> <PID> 28462  0 <Time> pts/ta   0:00 <10.1.2 ORACLE_HOME>/opmn/bin/opmn -a -q ping
<user> <PID> 28459  0 <Time> pts/ta   0:00 <10.1.2 ORACLE_HOME>/opmn/bin/opmnctl stopall
<user> <PID> 28459  0 <Time> pts/ta   0:00 <10.1.2 ORACLE_HOME>/opmn/bin/opmnctl status

3. Kill the "opmn -a -q ping" and the "opmnctl stopall" using the PID's presented in step 2 :
3.1 kill -9 <PID of opmn -a -q ping>
3.2 kill -9 <PID of opmnctl stopall>
3.3 kill -9 <PID of opmnctl status>

The clone should continue now, in case it appears to hang again check if the opmn processes are started again and kill them until the clone continues.


Workaround 2:
1 - cat <10.1.2 ORACLE_HOME>/opmn/conf/opmn.xml | grep remote (and write down the remote number)

2 - edit <10.1.2 ORACLE_HOME>/opmn/conf/ons.conf

Change :

nodes=ap6004bld.us.oracle.com:15007

Into:

nodes=<AppsTier Hostname>:<Remote port number from 1>

3 - execute perl  adcfgclone.pl appsTier again

Oracle Apps R12.2.4 Cloning Step by step

Cold Cloning Steps (Multi User & Single Node)

Step:-1
Prepare the Source System for database tier and application tier

Execute the following commands to prepare the Source System for cloning: 

Note: Ensure all the processes in the Source System are up before proceeding with the following two steps.

Prepare the Source System database tier for cloning 
Log on to the Source System as the DB_user.

Source the Database tier environment file.

Execute the following commands:

$ cd <RDBMS ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>
$ perl adpreclone.pl dbTier

Step:-2
Prepare the Source System application tier for cloning

Log on to the primary node of the Source System as the apps_user.
Source the environment file of the Run Edition File system.

You can use the following command to confirm that the environment variable FILE_EDITION points to the Run Edition File System:
$ echo $FILE_EDITION
It should return the value:
run
Execute the following commands:
$ cd <INST_TOP>/admin/scripts
$ perl adpreclone.pl appsTier

Note: If you apply a new Rapid Clone or AutoConfig update to the system, you must execute adpreclone.pl again on the database tier and applications tier to apply the new files into the clone directory structures to be used during the cloning configuration stage. Furthermore, if you patch Oracle Fusion Middleware or make configuration changes to the Oracle E-Business Suite WebLogic Domain, you must execute adpreclone.pl again on the applications tier to rebuild the Oracle Fusion Middleware home.

As of Release 12.2, the adpreclone.pl process on the application tier creates a complete compressed archive of the Oracle Fusion Middleware and its components as follows:

A compressed archive of the Oracle WebLogic Server home,
Oracle Web Tier Utilities home, Oracle Common Utilities home and the Oracle E-Business Suite home:
<COMMON_TOP>/clone/FMW/FMW_Home.jar

A compressed archive of the Oracle E-Business Suite WebLogic domain:
<COMMON_TOP>/clone/FMW/WLS/EBSdomain.jar

The Oracle E-Business Suite WebLogic domain's configuration template:
<COMMON_TOP>/clone/FMW/WLS/plan/moveplan.xml

A compressed archive of the Oracle Web Tier/Oracle HTTP Server configuration instance:
<COMMON_TOP>/clone/FMW/OHS/ohsarchive.jar

The Oracle HTTP Server configuration instance's configuration template:
<COMMON_TOP>/clone/FMW/OHS/moveplan.xml

Shut down the application processes (Windows platform only) 

Log on to Run Edition File System in the Source System as the apps_user, and shut down all the application processes.

Step:-3
Copy both database tier and application tier nodes from the Source System to the Target System

Copy the application tier file system from the Source node to the Target node by executing the following steps in the order listed. Ensure the application tier files copied to the Target System are owned by the Target apps_user, and that the database node files are owned by the Target oracle user.

Note: In the copying tasks below, UNIX users should ensure that the symbolic links (soft links) are preserved when copying. On most UNIX platforms, you can accomplish this with the cp -RH command. Consult the UNIX man page for the cp command to check the parameters available on your platform.

For example:
$ scp -r /source_dest_dir/db 192.168.1.100-(target):/u01/


Alternatively, you can use the tar command to compress the directories into a temporary staging area. UNIX users should ensure that the symbolic links (soft links) are preserved when compressing. On most UNIX platforms, this is the default behavior of the tar command. Consult the UNIX man page for the tar command to check the parameters available on your platform.

In addition, verify the permissions of the executables under ORACLE_HOME/bin that can potentially be owned by root, such as nmo, nmhs, and nmb.

Copy the database node file system

Log on to the Source System database node as the oracle user, and then:

Perform a normal shut down of the Source System database.

Copy the database (.dbf) files from the Source System to the Target System.

Copy the Source System database ORACLE_HOME to the Target System.

Start the Source applications system database and application tier processes.

Copy the application tier file system from the Source "Run Edition File System" to the Target "Run Edition File System"

Log on to Run Edition File System in the Source System application tier nodes as the apps_user.

Copy the following application tier directories from the Source Node to the Target Run Edition File System application tier node:
WHAT NEEDS TO BE COPIED
----------------------------
Choose only RUN FILE SYSTEM for copying




<APPL_TOP>

<COMMON_TOP>

<OracleAS Tools 10.1.2 ORACLE_HOME>
The same operating system user must own both the Run Edition and Patch Edition File Systems.

Note: In Release 12.2, you can set the base directory to any desired location. However, the subdirectory structure cannot be changed because of dependencies on both the WLS domain and the dual file system required for online patching. Also, the base directory must be the same across all nodes in multi-node configurations.

Dual File System Directory Structure 

In Release 12.2, the following directory structure exists to support the Run Edition and Patch Edition File Systems: 

Note: <s_base> and <sid> are user-defined values.
<s_base>/<sid>/fs1 (for example, /u02/apps/fs1)

<s_base>/<sid>/fs2 (for example, /u02/apps/fs2)

Two environment variables, $RUN_BASE and $PATCH_BASE, store these locations. The function (run or patch) of these two file systems is not static, and their values switch every time when a cut over phase is complete.

Note: As Rapid Clone will create a replica of the Source Node, if the Source Run Edition File System is the first file system (fs1), the Target Run Edition File System will also be the first file system (fs1). Similarly, if the Source Run Edition File System is the second file system (fs2), then the Target Run Edition File System will also be the second file system (fs2). Therefore, when you perform a cloning task, you always clone and copy the Source Run Edition File System to create the Target Run Edition File System, but the directory location of the Run Edition File System can be pointing either to <s_base>/<sid>/fs1 or <s_base>/<sid>/fs2 based on the Source Run Edition File System base directory.

When copying the files, use the values of $RUN_BASE and $PATCH_BASE variables to determine if the Run Edition File System should be copied to fs1 or fs2.

The Source Run Edition File System has the following values:

$RUN_BASE=/u02/apps/fs2

$PATCH_BASE=/u02/apps/fs1

The Target <s_base> directory will be /d05/test. Copy the Source Run Edition File System into the Target /d05/test/fs2 directory to initially act as Run Edition File System.

Step:-4
Configure the Target System

Run the following commands to configure the Target System. You will be prompted for specific Target System values such as SID, paths, and ports.

Configure the Target System Database Tier

Log on to the Target System as the oracle user and enter the following commands:
$ cd <RDBMS ORACLE_HOME>/appsutil/clone/bin
$ perl adcfgclone.pl dbTier

Login with DB_User
[root@sujeet /]# su ora-db

[ora-db@sujeet /]$ cd /u01/db/11.2.0/appsutil/clone/bin/

[ora-db@sujeet bin]$ perl adcfgclone.pl dbTier

                     Copyright (c) 2011 Oracle Corporation
                        Redwood Shores, California, USA
                        Oracle E-Business Suite Rapid Clone
                                 Version 12.2
                      adcfgclone Version 120.63.12020000.7.1202010.2

Enter the APPS password : ******

Running:

Target System Hostname (virtual or normal) [sujeet] : sujeet

Target System Database SID : Airtel

Target System Base Directory : /u01/db

Target System utl_file_dir Directory List : /tmp

Number of DATA_TOP's on the Target System [1] :

Target System DATA_TOP Directory 1 [/data01/PRE/db/data] : /u01/db/data

Target System RDBMS ORACLE_HOME Directory [/u01/db/11.2.0] :

Do you want to preserve the Display [test:0.0] (y/n)  : n

Target System Display [sujeet:0.0] :

Do you want the target system to have the same port values as the source system (y/n) [y] ? : n

Target System Port Pool [0-99] : 15

APPS Password : Log file located at /u01/db/11.2.0/appsutil/log/Airtel_sujeet/ApplyDBTier_06232239.log
  \     50% completed

Completed Apply...
Tue Jun 23 22:48:04 2015

Starting database listener for Airtel:
Running:
/u01/db/11.2.0/appsutil/scripts/Airtel_sujeet/addlnctl.sh start Airtel
Logfile: /u01/db/11.2.0/appsutil/log/Airtel_sujeet/addlnctl.txt

You are running addlnctl.sh version 120.4
Starting listener process Airtel ...
Listener Airtel has already been started.
addlnctl.sh: exiting with status 0
addlnctl.sh: check the logfile /u01/db/11.2.0/appsutil/log/Airtel_sujeet/addlnctl.txt for more information ...

[ora-db@sujeet bin]$
[ora-db@sujeet 11.2.0]$ . Airtel_sujeet.env
[ora-db@sujeet 11.2.0]$ sqlplus / as sysdba

SQL*Plus: Release 11.2.0.3.0 Production on Tue Jun 23 23:06:27 2015

Copyright (c) 1982, 2011, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL>
SQL> select * from v$version;

BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE    11.2.0.3.0      Production
TNS for Linux: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production


Step:-5





Configure the Target System application tier server nodes 

Log on to the Run Edition File System in the Target System as the applmgr_user and enter the following commands:
$ cd <COMMON_TOP>/clone/bin
$ perl adcfgclone.pl appsTier

[root@sujeet /]# su applchintels <application_User>

[applmgr@sujeet /]$ cd /apps_base/apps/fs1/EBSapps/comn/clone/bin

RUN perl adcfgclone.pl appsTier

Step:-6

[applmgr@sujeet bin]$ perl adcfgclone.pl appsTier

                     Copyright (c) 2011 Oracle Corporation
                        Redwood Shores, California, USA
                        Oracle E-Business Suite Rapid Clone
                                 Version 12.2
                      adcfgclone Version 120.63.12020000.41

Enter the APPS password : *************
Running:
Enter the Weblogic AdminServer password : *********
Running:
Do you want to add a node (yes/no) [no] : no

Running:

Target System File Edition type [run] : run

Provide the values required for creation of the new APPL_TOP Context file.

Target System Hostname (virtual or normal) [sujeet] : sujeet

Target System Database SID : Airtel

Target System Database Server Node [sujeet] :

Target System Database Domain Name [sujeet.com] :

Target System Base Directory : /u02/apps

Target System Base Directory set to /u02/apps

Target System Current File System Base set to /u02/apps/fs1

Target System Other File System Base set to /u02/apps/fs2

Target System Fusion Middleware Home set to /u02/apps/fs1/FMW_Home

Target System Web Oracle Home set to /u02/apps/fs1/FMW_Home/webtier

Target System Appl TOP set to /u02/apps/fs1/EBSapps/appl

Target System COMMON TOP set to /u02/apps/fs1/EBSapps/comn

Target System Instance Home Directory [u02/apps] :

Target System Instance Top set to /u02/apps/fs1/inst/apps/Airtel_sujeet

Do you want to preserve the Display [test:0.0] (y/n)  : n

Target System Display [sujeet:0.0] :

Target System Root Service [enabled] :

Target System Web Administration [enabled] :

Target System Web Entry Point Services [enabled] :

Target System Web Application Services [enabled] :

Target System Batch Processing Services [enabled] :

Target System Other Services [enabled] :

Do you want the target system to have the same port values as the source system (y/n) [y] ? : n

Target System Port Pool [0-99] : 11
Checking the port pool 11

UTL_FILE_DIR on database tier consists of the following directories.

1. /usr/tmp
2. /tmp
3. /u01/db/11.2.0/appsutil/outbound/Airtel_sujeet
4. /usr/tmp

Choose a value which will be set as APPLPTMP value on the target node [1] : 1

 100% completed       

Completed Apply...
Thu Jun 25 17:56:34 2015

 Executing command: /u02/apps/fs1/EBSapps/10.1.2/bin/sqlplus @/u02/apps/fs1/EBSapps/appl/ad/12.0.0/patch/115/sql/truncate_ad_nodes_config_status.sql


Do you want to startup the Application Services for PREPROD? (y/n) [n] : y





Step:-7

RUN adpreclone on TARGET RUN FILESYSTEM

[applmgr@sujeet ~]$ cd /u02/apps/fs1/EBSapps/appl
[applmgr@sujeet appl]$ . Airtel_sujeet.env 
[applmgr@sujeet appl]$ cd $ADMIN_SCRIPTS_HOME

[applmgr@sujeet scripts]$ perl adpreclone.pl appsTier

Copyright (c) 2011, 2014 Oracle Corporation
                        Redwood Shores, California, USA

                        Oracle E-Business Suite Rapid Clone

                                 Version 12.2

                   Enter the APPS User Password: *******

Enter the Weblogic AdminServer password : *******

  /     20% completed       

Completed Stage...

Step:-8

SHUTDOWN THE APPLICATION which is running on RUN FILESYSTEM

[applmgr@sujeet scripts]$ ./adstpall.sh apps/apps

You are running adstpall.sh version 120.22.12020000.7

Enter the WebLogic Server password: ********

[applmgr@sujeet scripts]$ ps -ef |grep FNDLIBR
503      25991  4863  0 20:52 pts/1    00:00:00 grep FNDLIBR

Step:-9

COPY THE TARGET RUN FILESYSTEM to TARGET PATCH FILESYSTEM
----------------------------------------------------------------

/u02/apps/fs2/<----Here We need to copy EBSapps from /u02/apps/fs1/

[applmgr@sujeet fs2]$ cd /u02/apps/fs1/
[applmgr@sujeet fs1]$ cp -r EBSapps/ /u02/apps/fs2/

Check EBSapps properly copy or not?

 Go to FS2 location and check it.

[applmgr@sujeet ~]$ cd /u02/apps/fs2

[applmgr@sujeet fs2]$ ll
total 4
drwxr-xr-x 4 applmgr dba 4096 Jun 25 20:55 EBSapps

[applmgr@sujeet fs2]$ du -sh EBSapps/
30G     EBSapps/

Step:-10

UNSET the application Enviroment.Previously we have executed env.

[applmgr@sujeet~]$ vi .bash_profile

Before we run adcfgclone.pl dont run any env's, Directly go to

 /u02/apps/fs2/EBSapps/comn/clone/bin/ and execute adcfgclone.pl

Step:-11

Once Finished copying START CONFIGURING TARGET PATCH FILESYSTEM
---------------------------------------------------------------------

[applmgr@sujeet ~]$ cd /u02/apps/fs2/EBSapps/comn/clone/bin
[applmgr@sujeet bin]$ perl adcfgclone.pl appsTier

                     Copyright (c) 2011 Oracle Corporation
                        Redwood Shores, California, USA

                        Oracle E-Business Suite Rapid Clone

                                 Version 12.2

                      adcfgclone Version 120.63.12020000.41

Enter the APPS password : *******
Running:
Enter the Weblogic AdminServer password : *********

Do you want to add a node (yes/no) [no] : no
Running:
Target System File Edition type [run] : patch

Enter the full path of Run File System Context file : /u02/apps/fs1/inst/apps/Airtel_sujeet/appl/admin/Airtel_sujeet.xml

Provide the values required for creation of the new APPL_TOP Context file.

Target System Fusion Middleware Home set to /u02/apps/fs2/FMW_Home

Target System Web Oracle Home set to /u02/apps/fs2/FMW_Home/webtier

Target System Appl TOP set to /u02/apps/fs2/EBSapps/appl

Target System COMMON TOP set to /u02/apps/fs2/EBSapps/comn

Target System Instance Top set to /u02/apps/fs2/inst/apps/Airtel_sujeet

Target System Port Pool [0-99] : 12

UTL_FILE_DIR on database tier consists of the following directories.

1. /usr/tmp
2. /tmp
3. /u01/db/11.2.0/appsutil/outbound/PREPROD_chintels
4. /usr/tmp
Choose a value which will be set as APPLPTMP value on the target node [1] : 

  |    100% completed       

Completed Apply...
Thu Jun 25 22:04:38 2015

Looking for incomplete CLONE record in ad_adop_session_patches table

The CLONE record status is no rows selected

Step:-12
Once we are done with everything. Start the application Tier using adstral.sh

This time set the env to RUN File System

[applmgr@sujeet ~]$ . .bash_profile 

[applmgr@sujeet ~]$ cd $ADMIN_SCRIPTS_HOME 

[applmgr@sujeet scripts]$ pwd
/u02/apps/fs1/inst/apps/Airtel_sujeet/admin/scripts

[applmgr@sujeet scripts]$ ./adstrtal.sh apps/apps

Enter the Weblogic AdminServer password : *********


[applmgr@sujeet scripts]$ ps -ef|grep FNDLIBR
503      20958 20953  0 22:23 pts/1    00:00:00 FNDLIBR                                                                                                                                                
503      21212 21118  0 22:24 ?        00:00:00 FNDLIBR  

Now Database & Application is UP & Running..

Step:-13

Open Login page.

URL:- 192.168.1.100:8011




*******************************END**********************************************

Tuesday, 23 June 2015

Uninstalling Oracle VM Manager 3.3.1

Before you uninstall Oracle VM Manager, make sure both the Oracle VM Manager Command Line Interface and Oracle VM Manager are shut down:

[root@test ~]# service ovmcli stop

Stopping Oracle VM Manager CLI                             [  OK  ]

[root@test ~]# service ovmm stop

Stopping Oracle VM Manager                                 [  OK  ]

You perform the uninstall using the Oracle VM Manager installation script. You must start the installer from the installation media; you cannot perform an uninstall without the installation media as there is no installer located on the Oracle VM Manager host computer.

Mount Oracle VM manager media iso image.

[root@test ~]# cd /media/
[root@test media]# ls
NTFS  OVMManagerInstaller3.3.2_b1072
[root@test media]# cd OVMManagerInstaller3.3.2_b1072/
[root@test OVMManagerInstaller3.3.2_b1072]# ls
components       EULA     oracle-validated.params  OvmSDK_3.3.2.1072.zip  TRANS.TBL
createOracle.sh  LICENSE  ovmm-installer.bsx       runInstaller.sh

[root@test OVMManagerInstaller3.3.2_b1072]# ./runInstaller.sh -i Uninstall -y

Oracle VM Manager Release 3.3.2 Installer

Oracle VM Manager Installer log file:
/var/log/ovmm/ovm-manager-3-install-2015-06-23-133951.log


Uninstall Oracle VM Manager

DB component : MySQL RPM package
MySQL RPM package installed by OVMM was found...
Removing MySQL RPM package installation ...

Product component : Java in '/u01/app/oracle/java/'
Java is installed ...

Removing Java installation ...

Product component : Oracle VM Manager in '/u01/app/oracle/ovm-manager-3/'
Oracle VM Manager is installed ...
Removing Oracle VM Manager installation ...

Product component : Oracle WebLogic Server in '/u01/app/oracle/Middleware/'
Oracle WebLogic Server is installed

Removing Oracle WebLogic Server installation ...
Service ovmm is deleted.
Service ovmcli is deleted.

Uninstall completed ...






Sunday, 21 June 2015

how to integrate oracle vm manager to oracle vm server

Integrate oracle vm manager to oracle vm server 3.3.1


Use Oracle VM Manager to manage Oracle VM Servers. Do not manage Oracle VM Servers directly using the Oracle VM Server command line unless directed to do so by a My Oracle Support document, or by Oracle Support.
A server pool must contain at least one Oracle VM Server. After installing an Oracle VM Server, you must discover it in Oracle VM Manager before it can be added to a server pool.
Before you discover Oracle VM Servers and add them to a server pool, you must:
  • Identify the IP address of the Oracle VM Server(s). If you installed Oracle VM Server with a static IP address (recommended), this is the IP address you use. If you installed Oracle VM Server with a dynamic IP address, log onto the Oracle VM Server and determine the IP address.
  • Identify the password to access the Oracle VM Agent installed on the Oracle VM Server.

Discovering Oracle VM Servers

When an Oracle VM Server is installed and starts up, it listens for Oracle VM Manager server pool discovery events. Before you can add an Oracle VM Server to a server pool, it must first be discovered.

To discover an Oracle VM Server:

Click the Servers and VMs tab.
Click Discover Servers Discover Servers icon in the toolbar. The Discover Servers dialog box is displayed.

Note:- You can also use the Discover Servers... subtab in the Tools and Resources tab to discover Oracle VM Servers. The fields in that screen are identical to those discussed in this procedure.





Enter information about the Oracle VM Server(s) to be discovered:

Oracle VM Agent Port: The port on which the Oracle VM Agent is listening. This is most likely the default port8899.

Oracle VM Agent Password: The password to connect to the Oracle VM Agent. The password must be the same on all Oracle VM Servers.

IP Addresses/DNS Hostnames: Enter the IP address(es), IP ranges or DNS hostnames of the Oracle VM Server(s) to be discovered. You can paste a list of multiple IP addresses or multiple DNS hostnames. If you enter an IP range it must be in the format 192.168.10.2-10. For example, if you enter 192.168.10.2-4 Oracle VM Manager will discover 192.168.10.2, 192.168.10.3 and 192.168.10.4. IP addresses, IP ranges and DNS host names must be entered on separate lines.

Click OK.

The Oracle VM Servers are discovered and added to the Unassigned Servers folder. The newly discovered Oracle VM Server contains some basic information about itself, and about any immediate connectivity to a shared SAN, but it is considered to be in an unconfigured state. The Oracle VM Server cannot be used to perform any virtual machine, or active cluster operations. Physical network and storage configuration can be performed, and any subsequent storage discovery operations may also be performed.
When an Oracle VM Server is discovered, it is configured to use the Oracle VM Manager host computer as the Network Time Protocol (NTP) time source. This ensures that all Oracle VM Servers are in sync with each other in the Oracle VM Manager environment.

The Utilization % column in the Servers perspective in the management pane does not report the utilization statistics of an Oracle VM Server that is in the Unassigned Servers folder. This field does not report utilization statistics unless an Oracle VM Server is included in a server pool.

Note:-
Discovered Oracle VM Servers do not use a Virtual IP address until they are properly configured by being included in a server pool.

When an Oracle VM Server has been discovered, it can be added to a server pool.

Adding an Oracle VM Server to a server pool.



Reference:-

http://docs.oracle.com/cd/E35328_01/E35332/html/vmusg-servers-manage.html