Showing posts sorted by relevance for query Oracle. Sort by date Show all posts

oracle apps r12 cloning steps using rman Tuesday, August 12, 2014

How to Clone Oracle EBS R12.1

CLONING ORACLE EBS R12.1

P R E C L O N E S T E P S

Step 1

Stop Apps Services

[oracle@erp scripts]$ ./adstpall.sh apps/apps

Step 2

Run adpreclone on DB Node

[oracle@erp~PROD_erp]$ perl adpreclone.pl dbTier

Run adpreclone Apps Node

[oracle@erp~PROD_erp]$ perl adpreclone.pl appsTier

Step 3

Taking Cold Backup using Tar

Stop all apps services

Stop db services

Take Tar Backup

AS=ERP-CLONE -TAR_$(date +%d-%m-%Y).tgz

tar -cvzf /backup/$AS /mk01/oracle

Step 4

(a)

Start Apps Services on ERP

[oracle@erp scripts]$ ./adstrtal.sh apps/apps

(b)

Step 5

Logon to Apps Server

http://erp.domain.com:8000 and follow these steps

click System Administrator -> Concurrent -> Manager -> Administer

make sure all services are running with status 1

Additional Steps (if errors )

If error found in Starting apps services then

1. stop all apps services

2. run adautocfg.sh

P O S T C L O N E S T E P S

oracle@test's password:

STEP 1

Stop Apps services

[oracle@test scripts]$ ./adstpall.sh apps/apps

Stop DB and Listener services

[oracle@erp TEST_erp]$ ./addbctl.sh stop TEST

[oracle@erp TEST_erp]$ ./addlnctl.sh stop immediate

STEP 2

Renaming Existing Directories

[oracle@test]$ mv oracle oracle.old

STEP 3

Moving copied Directories of apps, db , inst and diag

[oracle@test:]$ mkdir -p /mk01/oracle/TEST

[oracle@test]$ mv apps /mk01/oracle/TEST/

[oracle@test]$ mv inst /mk01/oracle/TEST/

[oracle@test]$ mv db /mk01/oracle/TEST/

[oracle@test]$ mv diag /mk01/oracle/PROD/

STEP 4

a) Run adcfgclone for DB on TEST SERVER

[oracle@test]$ cd /mk01/oracle/PROD/db/tech_st/11.1.0/appsutil/clone/bin/

[oracle@test bin]$ perl adcfgclone.pl dbTier

Enter the APPS password :

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

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

Target Instance is RAC (y/n) [n] :

Target System Database SID: TEST

Target System Base Directory : /mk01/oracle/TEST

Target System utl_file_dir Directory List : /usr/tmp

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

Target System DATA_TOP Directory 1 [/mk01/oracle/TEST/db/apps_st/data] :

Target System RDBMS ORACLE_HOME Directory [/mk01/oracle/TEST/db/tech_st/11.1.0] :

Do you want to preserve the Display [null] (y/n) ? : y

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] : 5

b) Run adcfgclone for Apps Node

[oracle@test bin]$ cd /mk01/oracle/TEST/apps/apps_st/comn/clone/bin/

[oracle@test]$ cd /mk01/oracle/TEST/apps/apps_st/comn/clone/bin

[oracle@testbin]$ perl adcfgclone.pl appsTier

Enter the APPS password :

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

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

Target System Database SID: TEST

Target System Database Server Node [test] :

Target System Database Domain Name [domain.com] :

Target System Base Directory : /mk01/oracle/TEST

Target System Tools ORACLE_HOME Directory [/mk01/oracle/TEST/apps/tech_st/10.1.2] :

Target System Web ORACLE_HOME Directory [/mk01/oracle/TEST/apps/tech_st/10.1.3] :

Target System APPL_TOP Directory [/mk01/oracle/TEST/apps/apps_st/appl] :

Target System COMMON_TOP Directory [/mk01/oracle/TEST/apps/apps_st/comn] :

Target System Instance Home Directory [/mk01/oracle/TEST/inst] :

Target System Root Service [enabled] :

Target System Web Entry Point Services [enabled] :

Target System Web Application Services [enabled] :

Target System Batch Processing Services [enabled] :

Target System Other Services [disabled] :

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

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] : 5

UTL_FILE_DIR on the database tier consists of the following directories.

1. /usr/tmp

2. /usr/tmp

3. /mk01/oracle/TEST/db/tech_st/11.1.0/appsutil/outbound/TEST_erp

4. /usr/tmp

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

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

Starting application Services for ERP:

Running:

/mk01/oracle/TEST/inst/apps/TEST_erp/admin/scripts/adstrtal.sh –nopromptmsg

STEP6

Verify URL (if errors)

Go to Browser and open this page

http://test.domain.com:8005/OA_HTML/AppsLogin

STEP7

Verify URL (if errors)

If an error is found in Starting apps services then:-

1. Stop all Apps Services

2. Run adautocfg.sh

3. Start apps services

Natural DBA

how to apply patch in oracle apps r12 2 Tuesday, August 12, 2014

How to Apply a Patch in Oracle Apps R12

How to apply apps patch using adpatch R12

STEP 1 : Download the patch. From your pc and transfer it to Linux server
*login to oracle metalink.(www.metalink.oracle.com)
*Select the patches option then select the search type.
*Query for patch by writing the patch no. & platform on which you want to download the patch.
*Click download
If you have downloaded the patch at desktop then move it to directory where you want it to unzip. With winscp or whatever software
Winscp download link
http://winscp.net/eng/download.php#download

STEP 2 :Unzip the patch. And set the permission

su root

cd /u01/patch

unzip p16213642_R12.AP.B_R12_LINUX.zip

chown oracle:dba 16213642

STEP 3: Before applying a patch you must check whether the patch is already there or not. For this we query the database:

su oracle

cd /d01/oracle/PROD/db/tech_st/11.1.0/

. ./Test_test.env

sqlplus apps/<apps password

SELECT * FROM AD_APPLIED_PATCHES WHERE PATCH_NAME='16000686';

SELECT * FROM AD_BUGS WHERE BUG_NUMBER=16000686

STEP 4: Enable the Maintenance Mode.For This:

#su oracle

# . ./ APPSTEST_test.env

#adadmin

Here you will need system and apps password in order to enter the ad administration utility

Output
AD Administration Main Menu
   --------------------------------------------------
  1.    Generate Applications Files menu
  2.    Maintain Applications Files menu
  3.    Compile/Reload Applications Database Entities menu
  4.    Maintain Applications Database Entities menu
  5.    Change Maintenance Mode
  6.    Exit AD Administration

Select option 5. The status of maintenance mode is displayed at the top of change maintenance mode menu.Again it will show following options & ask for choice:
1.Enable Maintenance mode.
2.Disable Maintenance mode.
3.Return to Main Menu.
Select option 1. Then return to console.

Stop The application Tier

STEP 5: Run autopatch from the patch directory by entering the following command:

su oracle

[oracle@test]$cd /u01/patch/16213642/

[oracle@test appl]$adpatch

Note: - below red color will highlighted lines you will have to fill
Out put
Copyright (c) 2002 Oracle Corporation

Redwood Shores, California, USA

Oracle Applications AutoPatch

Version 12.0.0

NOTE: You may not use this utility for custom development

unless you have written permission from Oracle Corporation.

Attention: AutoPatch no longer checks for unapplied pre-requisite patches.

You must use OAM Patch Wizard for this feature. Alternatively, you can

review the README for pre-requisite information.

Your default directory is '/u01/finsys/apps/apps_st/appl'.

Is this the correct APPL_TOP [Yes] ?

AutoPatch records your AutoPatch session in a text file

you specify. Enter your AutoPatch log file name or press [Return]

to accept the default file name shown in brackets.

Filename [adpatch.log] : 16213642.log

You can be notified by email if a failure occurs.

Do you wish to activate this feature [No] ?

Please enter the batchsize [1000] :

Please enter the name of the Oracle Applications System that this

APPL_TOP belongs to.

The Applications System name must be unique across all Oracle

Applications Systems at your site, must be from 1 to 30 characters

long, may only contain alphanumeric and underscore characters,

and must start with a letter.

Sample Applications System names are: "prod", "test", "demo" and

"Development_2".

Applications System Name [TEST] : TEST *

NOTE: If you do not currently have certain types of files installed

in this APPL_TOP, you may not be able to perform certain tasks.

Example 1: If you don't have files used for installing or upgrading

the database installed in this area, you cannot install or upgrade

the database from this APPL_TOP.

Example 2: If you don't have forms files installed in this area, you cannot

generate them or run them from this APPL_TOP.

Example 3: If you don't have concurrent program files installed in this area,

you cannot relink concurrent programs or generate reports from this APPL_TOP.

Do you currently have files used for installing or upgrading the database

installed in this APPL_TOP [YES] ? YES *

Do you currently have Java and HTML files for HTML-based functionality

installed in this APPL_TOP [YES] ? YES *

Do you currently have Oracle Applications forms files installed

in this APPL_TOP [YES] ? YES *

Do you currently have concurrent program files installed

in this APPL_TOP [YES] ? YES *

Please enter the name Oracle Applications will use to identify this APPL_TOP.

The APPL_TOP name you select must be unique within an Oracle Applications

System, must be from 1 to 30 characters long, may only contain

alphanumeric and underscore characters, and must start with a letter.

Sample APPL_TOP Names are: "prod_all", "demo3_forms2", and "forms1".

APPL_TOP Name [oftest] : oftest *

You are about to apply a patch to the installation of Oracle Applications

in your ORACLE database 'TEST'

using ORACLE executables in '/u01/finsys/apps/tech_st/10.1.2'.

Is this the correct database [Yes] ?

AutoPatch needs the password for your 'SYSTEM' ORACLE schema

in order to determine your installation configuration.

Enter the password for your 'SYSTEM' ORACLE schema:*******

The ORACLE username specified below for Application Object Library

uniquely identifies your existing product group: APPLSYS

Enter the ORACLE password of Application Object Library [APPS] :*****

Enter the directory where your Oracle Applications patch has been unloaded
The default directory is [/u01/patch/16213642] :
Please enter the name of your AutoPatch driver file : u16213642.drv

If you don’t see the “autopatch is complete” message at the end of the Autopatch log file, Autopatch did not complete successfully.

STEP 6: Finally exit from maintain mode as above STEP 4
STEP 7: confirm the patch installation status For this we query the database:

su oracle

Run the environment variable db tire

sqlplus apps/<apps password

SQL>select * from AD_BUGS where bug_number=’<patch number>’

Ex:- SQL>select * from AD_BUGS where bug_number=’16213642’

Natural DBA

script Wednesday, October 15, 2014

11g Cold Backup Step By Step

Create a directory to copy your backup-related files to. In this example, we will be using c:\oracle\orabackup\orcl\cold.

2. Log into your database using SQL*Plus. C:\oracle\orabackup\orcl>sqlplus sys as sysdba

3. Using the DBA_DATA_FILES view, determine the data files that you will need to back up.

SQL> SELECT TABLESPACE_NAME, FILE_NAME FROM DBA_DATA_FILES;

TABLESPACE_NAME FILE_NAME

--------------- ----------------------------------------

USERS C:\ORACLE\ORADATA\ORCL\USERS01.DBF

UNDOTBS1 C:\ORACLE\ORADATA\ORCL\UNDOTBS01.DBF

SYSAUX C:\ORACLE\ORADATA\ORCL\SYSAUX01.DBF

SYSTEM C:\ORACLE\ORADATA\ORCL\SYSTEM01.DBF

4. Using the V$LOGFILE view, determine the online redo logs that will require a backup.

SQL> SELECT MEMBER FROM V$LOGFILE;

MEMBER

----------------------------------

C:\ORACLE\ORADATA\ORCL\REDO03.LOG

C:\ORACLE\ORADATA\ORCL\REDO02.LOG

C:\ORACLE\ORADATA\ORCL\REDO01.LOG

5. Using the V$CONTROLFILE view, determine the location of the database control files that will be backed up.

SQL> SELECT NAME FROM V$CONTROLFILE;

NAME

-------------------------------------

C:\ORACLE\ORADATA\ORCL\CONTROL01.CTL

C:\ORACLE\ORADATA\ORCL\CONTROL02.CTL

C:\ORACLE\ORADATA\ORCL\CONTROL03.CTL

6. From the SQL*Plus prompt, shut down the database below SQL

SQL> SHUTDOWN IMMEDIATE;

7. Once the database is shut down, exit SQL*Plus.

SQL> exit

C:\oracle\orabackup\orcl>

8. Using the OS Copy command, copy the database data files, control files, and online redo logs to the backup directory created in step 1. In our example, they are all in the same directory, so this is easy.

C:\oracle\orabackup\orcl>Copy c:\oracle\oradata\orcl\*.*

9. Start SQL*Plus connecting as sys as sysdba. Restart the database with the startup command. You have completed your backup.

C:\oracle\orabackup\orcl> SQLPLUS SYS AS SYSDBA

SQL*Plus: Release 11.1.0.6.0 - Production on Thu Aug 14 19:31:56 2008

Enter password:

Connected to an idle instance.

SQL> STARTUP

ORACLE instance started.

Total System Global Area 397557760 bytes

Fixed Size 1333452 bytes

Variable Size 268437300 bytes

Database Buffers 121634816 bytes

Redo Buffers 6152192 bytes

Database mounted.

Database opened.

Natural DBA

tablespace in backup mode oracle Wednesday, October 15, 2014

How to Take Oracle Database Backup Step by Step

Oracle Hot Backup Restore steps

Oracle 11g Manual Online Hot Backup

In this lab, you will perform an online/hot backup of your database, with the database still running.

1. Create a directory for the backups. In this lab, we use c:\oracle\orabackup\orcl\hot.

We assume that the directory structure c:\oracle\orabackup\orcl is already created from the work you did in Lab 2.1.

C:\>cd oracle\orabackup\orcl

C:\oracle\orabackup\orcl> Mkdir Hot

2. Log into your database using SQL*Plus. Check the log mode the database is in by

querying the LOG_MODE column in V$DATABASE. It should be in ARCHIVELOG mode.

C:\oracle\orabackup\orcl> SQLPLUS SYS AS SYSDBA

SQL> SELECT LOG_MODE FROM V$DATABASE;

LOG_MODE

-----------------

ARCHIVELOG

3. Using the DBA_DATA_FILES view, determine the data files that you will need to back up.

SQL> SELECT TABLESPACE_NAME, FILE_NAME FROM DBA_DATA_FILES;

TABLESPACE_NAME FILE_NAME

--------------- ----------------------------------------

USERS C:\ORACLE\ORADATA\ORCL\USERS01.DBF

UNDOTBS1 C:\ORACLE\ORADATA\ORCL\UNDOTBS01.DBF

SYSAUX / SYSTEM C:\ORACLE\ORADATA\ORCL\SYSAUX01.DBF .. SYSTEM01.DBF

4. Using the V$LOG view; determine which sequence is the current online redo log sequence.

You must ensure that you have this log sequence and all logs generated during the backup

in order to be able to restore the backup.

SQL> SELECT GROUP#, SEQUENCE#, STATUS FROM V$LOG;

GROUP# SEQUENCE# STATUS

---------- ---------- ----------------

1 4 CURRENT

2 2 INACTIVE

3 3 INACTIVE

5. Put the database in hot backup mode with the alter database begin backup command.

SQL> ALTER DATABASE BEGIN BACKUP; Database altered.

6. Copy all database data files (all have an extension of .dbf) to the backup directory created in step 1.

SQL> host C:\oracle\orabackup\orcl>>Copy c:\oracle\oradata\orcl\*.dbf 5 file(s) copied

7. Using the V$LOG view, determine which sequence is the current online redo log sequence. You must ensure that you have this log sequence and all logs generated during the backup to restore the backup. Here, we need log sequences starting with 4 (when we started our backup) and continuing through log Seq7.

SQL> SELECT GROUP#, SEQUENCE#, STATUS FROM V$LOG;

GROUP# SEQUENCE# STATUS

------------- ------------------- --------------

1 7 CURRENT

2 5 INACTIVE

3 6 INACTIVE

8. Take the database out of hot backup mode with ALTER DATABASE END BACKUP;

9. Use the command to force a switch from log sequence 7. ALTER SYSTEM SWITCH LOGFILE;

10. Check the archive-log directory to make sure log-file sequences 4 through 7 have been created.

SQL> SHOW PARAMETER LOG_ARCHIVE_FORMAT

NAME TYPE VALUE

----------------- --------- -----------

log_archive_format string ARC%S_%R.%T

SQL> SHOW PARAMETER LOG_ARCHIVE_DEST_1

11. Copy the archived redo logs to the backup location.

SQL> Host copy c:\oracle\arch\orcl\arc*.* c:\oracle\orabackup\orcl\hot\*.*

12. Check the backup directory to ensure that all the files needed are in place.

SQL> Host dir c:\oracle\orabackup\orcl\hot\*.*

13. This is an optional step. Now that we know our archived redo logs were copied successfully, we can remove them from the archive-log directory if we want.

Natural DBA