Wednesday, August 12, 2009

CRONTAB

requires two parts. The first part is having the crond daemon running. The second part is using the crontab command to create a schedule. The schedule is a list of jobs with times that you'd like to have run.

There are two versions of the command that you will use most of the time.

crontab -e

To edit your crontab file.

crontab -l

To list your crontab file.

crontab -l > crontabbackup.txt

Another useful variation of the -l, list your crontab, allows you to send the schedule to a file.

crontab crontabbackup.txt

If you use the crontab -l option and send the output to a file as was shown in the prior command example, you can take that schedule and import it into another schedule. All you have to do is use crontab and supply your backed up schedule file. This is a great trick for knoppix. The creative use of this format of the command would be import your schedule from a USB thumb drive or a hard drive partion. You could even store the file on a MS Windows partition as long as the file is in linux format verse MS Dos format.

man 5 crontab

Use this man command read about the formatting requirements for your /etc/crontab file.


Note: Two classes of user will use this command.
A user or the "root" user. Although, almost every Linux system, I've ran crontab -e as "root" does not support it.
In other words, if you are Sys Admin (root). Just vi /etc/crontab.

Monday, August 10, 2009

Clonning hot backup restore

Source System (PROD):
(a) P4 3.0 GHz System with 2GB RAM and 200 GB HDD (Redhat Linux AS 4)
/d01 ..- 40 GB (Application Tier Files)
/d02 ..- 10 GB (10g Oracle Home)
/d03 ..- 80 GB (Data Files)
/backup .- 100 GB (NFS mount point Shared on TEST Server)
Hostname: prodserver
Application Version: 11.5.10.2
Database Version: 10.2.0.2 Target System (TEST):
(b) P4 2.6 GHz system with 1.5 GB RAM with 300 GB HDD (Redhat Linux AS 4)
/d01 ..- 40 GB (Application Tier Files)
/d02 ..- 10 GB (10g Oracle Home)
/d03 ..- 80 GB (Data Files)
/backup .- 100GB (NFS Share Directory)
Hostname: testserver
Application Version: 11.5.10.2
Database Version: 10.2.0.2
Note: This target System was previously cloned with cold backup. This is second time cloning with Hot Backup from PRODSERVER.
Stage1: Prerequisites:
========> Apply OUI22 Patch, 5035661 to every IAS Oracle Home
and RDBMS Oracle Home to be cloned.
If you are having 10g Oracle Home,

there is no need of applying this patch.
You need to apply this patch on IAS Oracle Home
(if Database is not 10g)
A. Applying the patch on the iAS $ORACLE_HOME:
====================================================
(a) Unzip the patch into the directory:
$unzip -od /d01/prodora/iAS p5035661_11i_LINUX.zip
(b) Source the Apps environment file :
$. $APPL_TOP/APPSORA.env
(c) Change directory to the /appsoui/setup
$cd $IAS_ORACLE_HOME/appsoui/setup
(d) Execute the perl script OUIsetup.pl:
$perl OUIsetup.pl
NOTE:
In the case of a Multi-Node instance, the above process
should be repeated on the of each Node.
(B) Applying the patch on the RDBMS $ORACLE_HOME:
(This step is not required for my current setup,
because my database version is 10g R2)
(a) Unzip the patch into the directory:
$unzip -od /u01/proddb/9.2.0 p5035661_11i_LINUX.zip
(b) Source the DB environment file :
$. $ORACLE_HOME/PROD_prodserver.env
(c) Change directory to the /appsoui/setup
$cd $ORACLE_HOME/appsoui/setup
(d) Execute the perl script OUIsetup.pl:
$perl OUIsetup.pl
======> Check all other Requirements as Perl, JRE, JDK, ZIP utilities on Source and Target Nodes as per
document .Cloning Oracle Applications Release 11i with Rapid Clone.
=======> Apply the Latest AD Minipack on Application Tier (Latest One is AD.I.5)
=======èpply the Latest Autoconfig Template Patch and Latest Rapidclone Patches to Application Tier (Check Metalink for These Patches)
Stage2: Prepare the Source System (PRODSERVER)
(a) Login into Database Tier as ORACLE user and run the preclone
$cd $ORACLE_HOME/appsutil/scripts/PROD_prodserver
$perl adpreclone.pl dbTier
(b) Login into the Application Tier as APPLMGR User and run the preclone
$cd $COMMON_TOP/admin/scripts/PROD_prodserver
$perl adpreclone.pl appsTier
Stage3: Put the Database in Begin Backup Mode and copy the Database Files
(a) Login into database as sysdba user
$sqlplus ./as sysdba.
Sql> alter database begin backup;
(b) Copy Archive log files created during hot backup to /backup directory.
(c) Copy the All Data files to /backup directory.
(d) Backup the control file to trace.
Sql> alter database backup control file to trace;
Copy this trace file to /backup directory
(e) Copy the current init.ora file to /backup directory
(f) End the Begin Backup Mode.
Sql> alter database end backup.
Stage4: Copy the Application Tier File System Files
(a)Login into the Application Tier as APPLMGR user and copy the APPL_TOP, COMMON_TOP,
IAS ORACLE HOME and 8.0.6 Oracle Home to /backup directory
Stage5: Copy the Source Database files and Application Files to Target server
Copy the parameter file, backup control file and archive log files from /backup directory
to /d01, /d02 and /d03 in target server.
Stage 6: Configure the Target Database (TESTSERVER)
Log on to the target system as the ORACLE user
(1) Configure the
cd /appsutil/clone/bin
perl adcfgclone.pl dbTechStack
(2) Create the target database control file manually
Open the backed up control file
a. remove all lines before the startup nomount statement
b. Modify the REUSE to SET
c. Modify Source DB SID to Target SID (Here PROD to TEST)
d. Modify NORESETLOGS TO RESETLOGS
e. delete all lines after the CHARACTER SET statement
............
CREATE CONTROLFILE SET DATABASE .TEST. NORESETLOGS ARCHIVELOG.
LOGFILEGROUP 1
./d03/log01.log. SIZE 50M,
.
DATAFILE
./d03/system01.dbf.,
./d03/undotbs01.dbf.,
.
CHARACTER SET UTF8;
..................
@ @
On the target system, modify the init.ora to have the target SID and location of the control file and also make sure that init.ora parameters are set for archive log mode On the target system,
starup the database in nomount stage
sql> startup nomount pfile=< Target init.ora path>
sql> @clone.ctl ( here clone.ctl is the control file which we have modified above)
Once control file is created, database will be in mount stage
execute recover command using backup control file after the database is mounted
SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;
After the last archive log has been applied, issue the following command
SQL> alter database open resetlogs;
After opening the database, add temp files to target database
(3) Run the library update script against the database
cd /appsutil/install/
Where is .sl. for HP-UX, .so. for any other UNIX platform and not required for Windows.
(4)Configure the target database (the database must be open)
cd /appsutil/clone/bin
perl adcfgclone.pl dbconfig
where target context file is: /appsutil/.xml
Stage 7 : Configure the Target Application Tier
Logon to the target system as the APPLMGR user and type the following commands
$Cd $COMMON_TOP/clone/bin
$Perl adcfgclone.pl appsTier
Finishing tasks:
(1) Update Profile options
(2) Update Printer Settings
(3) Update the workflow configuration settings
(4) Verify the APPLCSF variable setting
(5) Update the session_cookie_domain value in icx_parameters
For the finishing tasks, check the finishing tasks section of the following document
Cloning Oracle Applications Release 11i with rapid clone Note: 230672.1

Hot backup clonning

step by step procedure for hotbackup clonning.


1.copy the tops

2.unzip tops

tar -zxvf *.tgz

3.go to datatop

remove controlfiles, temp.dbf


4.create control file

5. go to user dump you will have a latest trace file

startup nomount

create controlfile set DATABASE "AFCO" RESETLOGS NOARCHIVELOG

CHANGE THE DIRECOTRY LOCATION

USING :%S#....#...#G

6. go to 10.2.0/dbs/

7.vi initsid.ora

8.controlfiles=/u02/afco/d01/proddata/cntrl01.dbf,/u02/afco/d01/proddata/cntrl02.dbf,/u02/afco/d01/proddata/cntrl03.dbf,

sqlplus "/as sysdba"

sql> recover database using backup controlfile untile cancel;

9.It will ask for archives

10.give the archive in this way

11./u02/afco/Arch/................

12.cancel

13.alter database open resetlogs;

14. alter tablespace temp add tempfile '/u02/afco/d01/proddata/temp01.dbf' size 100m;

15.conn apps/apps

16.select node_name from fnd_nodes;

17.delete from fnd_nodes where node_name in ('AFCOERP','AFCOPREDB');

18.EXIT

19.10.2.0/APPSUTIL/SCRIPTS/

20.sh adautoconfig.sh

apps/apps