Learn Oracle Apps DBA

Cloning

2012-06-24T04:39:00.000-07:00

Apps 11i

Multinode to single node

To see if your environment is ready for the Cloning with Rapid Clone, please check the Metalink Note 230672.1.

NOTE: The initial system has ONE APPL_TOP on one node (apps.localdomain) and the DB tier on another node (db.localdomain).

These easy to follow steps will allow you to move or clone Oracle applications from one location to another. This can be essential when moving from a multi-node system to single-node system. It may seem complex, but by approaching such a task one stage at a time it will become much easier under understand this technical process.

1. Maintain Snapshot information (on the APPS node)

adadmin -> 2. Maintain Applications Files menu -> 5. Maintain snapshot information -> 2. Update current view snapshot

2. Prepare the source system database tier for cloning

cd <RDBMS ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>

perl adpreclone.pl dbTier

cd $ORACLE_HOME/appsutil/scripts/VIS_apps
perl adpreclone.pl dbTier

3. Prepare the source system application tier for cloning

cd <COMMON_TOP>/admin/scripts/<CONTEXT_NAME>
perl adpreclone.pl appsTier

cd $COMMON_TOP/admin/scripts/VIS_apps
perl adpreclone.pl appsTier

4. Stop the Apps services if is not already done

$COMMON_TOP/admin/scripts/<CONTEXT_NAME>/adstpall.sh apps/apps

$COMMON_TOP/admin/scripts/VIS_apps/adstpall.sh apps/apps

5. Shutdown the Database and stop the listener

$ORACLE_HOME/appsutil/scripts/<CONTEXT_NAME>/addlnctl.sh stop VIS
$ORACLE_HOME/appsutil/scripts/<CONTEXT_NAME>/addbctl.sh stop immediate VIS

$ORACLE_HOME/appsutil/scripts/VIS_db/addlnctl.sh stop VIS
$ORACLE_HOME/appsutil/scripts/VIS_db/addbctl.sh stop immediate VIS

6. On the target system, create the directory where the Applications will be cloned

    [oracle@linux1 ~]$ su - root
    Password:
    [root@linux1 ~]# mkdir /APPS_11i
    [root@linux1 ~]# chown oracle:dba /APPS_11i

7. Copy the following application tier directories from the source node to the target application tier node:

<APPL_TOP>
<OA_HTML>
<OA_JAVA>
<OA_JRE_TOP>
<COMMON_TOP>/util
<COMMON_TOP>/clone
<COMMON_TOP>/_pages (when this directory exists)
<806 ORACLE_HOME>
<iAS ORACLE_HOME>

Source Node = apps.localdomain Destination Node = linux1.localdomain

/APPS_MI/visappl /APPS/visappl

/APPS_MI/viscomn/html /APPS/viscomn/html

/APPS_MI/viscomn/java /APPS/viscomn/java

/APPS_MI/viscomn/util /APPS/viscomn/util

/APPS_MI/viscomn/clone /APPS/viscomn/clone

/APPS_MI/viscomn/_pages /APPS/viscomn/_pages

/APPS_MI/visora/8.0.6 /APPS/visora/8.0.6

/APPS_MI/visora/iAS /APPS/visora/iAS

The files are copied from the apps node (apps.localdomain) and db node (db.localdomain) to the new node ( linux1.localdomain). This type of cloning is very similar with a single node system to single node system.

8. Copy the DBF files and ORACLE_HOME to the target system

Source Node = db.localdomain	Destination Node = linux1.localdomain
/APPS_DB/visdata	/APPS/visdata
/APPS_DB/visdb	/APPS/visdb

9. Start up the source Applications system database and application tier processes (optional)

10. Configure the target system database server

Connected as ORACLE:

cd <RDBMS ORACLE_HOME>/appsutil/clone/bin
perl adcfgclone.pl dbTier

cd /APPS/visdb/9.2.0/appsutil/clone/bin
perl adcfgclone.pl dbTier

11. Configure the target system application tier server nodes

Connected as APPLMGR:

cd <COMMON_TOP>/clone/bin
perl adcfgclone.pl appsTier

cd /APPS/viscomn/clone/bin
perl adcfgclone.pl appsTier

Attention:

Windows user only: add <806 ORACLE_HOME>\bin to the system path before running this step
When you run adcfgclone.pl on appsTier as APPLMGR, APPLMGR must have write permission to the oraInventory

12. Finishing Tasks

Log in to the target system application tier node as the APPLMGR user.Run the following tasks in adadmin for all products to generate JAR files, generate message files, relink executables copy files to destination

13. Clean up of the target system

Remove the temporary directory [COMMON_TOP]/clone/appl to reduce disk space usage.

R12

Clone Oracle Apps R12 Short Steps

Pre-Clone Steps:

On the DB server:

· cd $ORACLE_HOME/appsutil/scripts/

· perl adpreclone.pl dbTier

· Check the log file under

· $ORACLE_HOME/appsutil/log//StageDBTier_06201503.log

On the apps tier server:

· cd $ADMIN_SCRIPTS_HOME

· perl adpreclone.pl appsTier

· Check the log file $APPL_TOP/admin/log/

Clone Steps:

Copy the source apps tier file system to the target system.

· APPL_TOP.

· COMMON_TOP

· ORACLEAS_10.1.2_ORACLE_HOME

· ORACLEAS_10.1.3_ORACLE_HOME

Copy source system database tier file system to the target system. As user oracle:

· Shutdown normal the source system database.

· Copy the database (.dbf) files plus ORACLE_HOME to the target system.

On the target Database system

· cd $ORACLE_HOME/appsutil/clone/bin

· perl adcfgclone.pl dbTier

· Verify errors the log $ORACLE_HOME/appsutil/log/

On the target apps system

· $cd $COMMON_TOP/clone/bin

· $perl adcfgclone.pl appsTier

· Verify the errors the log. $APPL_TOP/admin//log

· Once clone is finished. If you have customized environment then change post clone profile options, utl_file_dir etc.

EBS R12 RAC TO RAC Clone

1- OC must be installed and running on all DB nodes.

2- Execute the following on all appTier and dbTier Source nodes.

$ cd $ORACLE_HOME/appsutil/scripts/[context_name]

$ perl adpreclone.pl dbTier

3- On the primary oracle RAC node execute:

$ cd [ORACLE_HOME]/appsutil/clone/bin

$ perl adclone.pl

java=[JDK 1.5 Location]

mode=stage

stage=[Stage Directory]

component=database

method=RMAN

dbctx=[RAC DB Context File] -- Full Path to the existing Oracle RAC database context file

showProgress

This will generate directoris. Go to [stage]/data/stage u will find rman iamge-copies like

"1jj9c44g_1_1" those files and the file "backup_controlfile.ctl" must be moved to the target system

5- Archive the database home as follow:

$ cd $ORACLE_HOME/..

$ tar -cvzf rac_db_oh.tgz [DATABASE TOP LEVEL DIRECTORY]

This archive must be transfered to the whole RAC nodes to be used on the target system.

6- On the target system extract the archived home as:

$ tar -xvzf rac_db_oh.tgz

7- Create pairs file on the first node as follow:

[NEW_ORACLE_HOME]/appsutils/clone/pairsfile.txt

it will contains the folow

s_undo_tablespace=[UNDOTBS1 for Initial Node]

s_dbClusterInst=[Total number of Instances in a cluster e.g. 2]

s_db_oh=[Location of new ORACLE_HOME]

8- Create the context file for the primary node as follow:

$ cd $[NEW_ORACLE_HOME]/appsutil/clone/bin

$ perl adclonectx.pl

contextfile=[PATH to OLD Source RAC contextfile.xml]

template=[NEW ORACLE_HOME]/appsutil/template/adxdbctx.tmp

pairsfile=[NEW ORACLE_HOME]/appsutil/clone/pairsfile.txt

initialnode

9- Restore database on the target system primary node as follow:

$ cd $[NEW_ORACLE_HOME]/appsutil/clone/bin

$ perl adclone.pl

java=[JDK 1.5 Location]

component=dbTier

mode=apply

stage=[NEW_ORACLE_HOME]/appsutil/clone

method=CUSTOM

dbctxtg=[Full Path to the Target Context File]

rmanstage=[Location of the RMAN dump files... i.e. RMAN_STAGE/data/stage]

rmantgtloc=[Shared storage loc for datafiles...ASM diskgroup / NetApps NFS mount / OCFS mount point]

srcdbname=[Source RAC system GLOBAL name s_global_database_name]

pwd=[APPS Password]

showProgressode

$ tail -f [ORACLE_HOME]/appsutil/log/$CONTEXT_NAME/ ApplyDatabase_[time].log

10- Check the listener status on target system

$ ps -ef | grep tns

-- listener must be up and running before the autococnfig

11- Run the Autoconfig

$ cd [ORACLE_HOME]/appsutil/scripts/[CONTEXT_NAME]

$ adautocfg.sh appspass=[APPS Password]

12- For the other nodes do the folowing:

A- Uncompress the archived home.

B- Compress the appsutil and move it from the primary node to the other nodes

$ cd [ORACLE_HOME]

$ zip -r appsutil_node1.zip appsutil

C- Update the pairsfile.txt to checnge the parameter s_undo_tablespace:

s_undo_tablespace=[Or UNDOTBS(+1) for additional Nodes]

s_dbClusterInst=[Total number of Instances in a cluster e.g. 2]

s_db_oh=[Location of new ORACLE_HOME]

D- Create a context file:

$ cd [NEW_ORACLE_HOME]/appsutil/clone/bin

$ perl adclonectx.pl

perl adclonectx.pl \

contextfile=[Path to Existing Context File from the First Node]

template=[NEW ORACLE_HOME]/appsutil/template/adxdbctx.tmp

pairsfile=[NEW ORACLE_HOME]/appsutil/clone/pairsfile.txt

addnode

E- Continue cloning as follow:

$ cd [NEW ORACLE_HOME]/appsutil/clone/bin

$ perl adcfgclone.pl dbTechStack [path to the database context file created in previous step]

F- [NEW_ORACLE_HOME]/appsutil/scripts/[CONTEXT_NAME]/addlnctl.sh start LISTENER_[hostname]

this command to run the correct RAC listener.

G- Source the environment file:

$ cd [NEW ORACLE_HOME]

$ ./[CONTEXT_NAME].env

H- Edit the [SID]_APPS_BASE.ora file and change the control file parameter to reflect the

correct control file location on the shared storage.

I- Start the RAC db

$ sqlplus /nolog

SQLPLUS> connect / as sysdba

SQLPLUS> startup

J- Run the autoconfig to generate the tnsnames and listeners files.

$ cd $ORACLE_HOME/appsutil/scripts/$CONTEXT_NAME

$ ./adautocfg.sh appspass=[APPS Password]

To create the database with RAC on the target manually:

$ srvctl add database -d [database_name] -o [oracle_home]

$ srvctl add instance -d [database_name] -i [instance_name] -n [host_name]

$ srvctl add service -d [name] -s [service_name]

Installation of Oracle Apps R12

2012-06-24T04:20:00.000-07:00

This post covers overview of Oracle Apps R12 Multi-node installation (two or more machines)

Things good to know about multi-node / distributed installation
1. Oracle Apps R12 is mainly categorised in to
a) Database Tier – Oracle Database and Database Listener
b) Application/Middle Tier- Oracle Web Server (Apache), Apps Server (OC4J – oacore, oaforms, oafm) and Concurrent Manager

2. Oracle Application Tier consists of following services, which you can run on one or more machines
- Root Service (OPMN)
- WebEntry Point Services (OHS)
- Web Application Services(OC4J- oacore, oafm, forms)
- Batch Processing Services(CM, apps listener, fullfillment)
- Other Services (MWA, Metric client/server)

3. You can install both Database Tier and Application (Middle) Tier on single machine (This type of installation is called as Single Node install)
or
You can install Database Tier on one machine and Application Tier services on one or more machines (This type of installation is called as Multi Node install)

4. If you are installing apps on three machines (like below) then you need to runrapidwiz (Installer for R12) three times . First on database tier and then on application tier.
- Machine 1 – Database & Concurrent Manager
- Machine 2 – Forms Tier
- Machine 3 – Web Tier

5. For multi-node (distributed) installation you get an option to use shared application tier file systems (multiple machine sharing same application tier file system) .

Note* Shared application tier option is not available for windows

6. All APPL_TOPs on multi-node system contain the same files, regardless of particular node’s role (web tier, forms tier, CM). This is also know as unified APPL_TOP.

7. It is possible to change single node R12 installation to multi-node configuration after installation. It is possible to add additional application/middle tier (after installation) using cloning. For steps follow Oracle My Support note # 406982.1

.
Oracle Apps R12 Multi-Node/Distributed Installation Steps

1. Install Apps R12 on Database Tier first by running rapidwiz
1.1 Select “Create a new configuration” on Configuration Choice Screen

1.2 On Application Server Node – Change Host Name details (if current host Machine1 is for only database)

1.3 Select Services from list for application tier node, for more info on services

click here

1.4 Click Add Server if you are planning to use more application tier

1.5 Fill Application Tier details and select services
.

1.6 repeat step 1.4 & 1.5 for all application tier nodes
1.7 Install apps on machine1

2. Copy conf_$SID.txtfrom machine1 to all application tier nodes under /tmp. conf_$SID.txt should be in $ORACLE_HOME/appsutil on database tier node ($INSTALL_BASE/ db/ tech_st/ 11.1.0/ appsutil)

3. Install Apps R12 on other machines (any order) by running rapidwiz
3.1 Select “Load the following saved configuration” on Configuration Choice Screen

3.2From browse button select conf_$SID.txt copied from Machine1
3.3 Install apps on Machine2

4. Repeat step 3 on all remaining application tier

References

R12 Installation Guide

Basic unix commands

2012-06-24T04:06:00.000-07:00

Basic File Navigation

The "pwd" command displays the current directory.

root> pwd
/u01/app/oracle/product/9.2.0.1.0

The "ls" command lists all files and directories in the specified directory. If no location is defined it acts on the current directory.

root> ls
root> ls /u01
root> ls -al

The "-a" flag lists hidden "." files. The "-l" flag lists file details.
The "cd" command is used to change directories.

root> cd /u01/app/oracle

The "touch" command is used to create a new empty file with the default permissions.

root> touch my.log

The "rm" command is used to delete files and directories.

root> rm my.log
root> rm -R /archive

The "-R" flag tells the command to recurse through subdirectories.
The "mv" command is used to move or rename files and directories.

root> mv [from] [to]
root> mv my.log my1.log
root> mv * /archive
root> mv /archive/* .

The "." represents the current directory.
The "cp" command is used to copy files and directories.

root> cp [from] [to]
root> cp my.log my1.log
root> cp * /archive
root> cp /archive/* .

The "mkdir" command is used to create new directories.

root> mkdir archive

The "rmdir" command is used to delete directories.

root> rmdir archive

The "find" command can be used to find the location of specific files.

root> find / -name dbmspool.sql
root> find / -print | grep -i dbmspool.sql

The "/" flag represents the staring directory for the search. Wildcards such as "dbms*" can be used for the filename.
The "which" command can be used to find the location of an executable you are using.

oracle> which sqlplus

The "which" command searches your PATH setting for occurrences of the specified executable.

File Permissions

The "umask" command can be used to read or set default file permissions for the current user.

root> umask 022

The umask value is subtracted from the default permissions (666) to give the final permission.

666 : Default permission
022 : - umask value
644 : final permission

The "chmod" command is used to alter file permissions after the file has been created.

root> chmod 777 *.log

Owner      Group      World      Permission
=========  =========  =========  ======================
7 (u+rwx)  7 (g+rwx)  7 (o+rwx)  read + write + execute
6 (u+wx)   6 (g+wx)   6 (o+wx)   write + execute
5 (u+Rx)   5 (g+Rx)   5 (o+Rx)   read + execute
4 (u+r)    4 (g+r)    4 (o+r)    read only
2 (u+w)    2 (g+w)    2 (o+w)    write only
1 (u+x)    1 (g+x)    1 (o+x)    execute only

Character eqivalents can be used in the chmod command.

root> chmod o+rwx *.log
root> chmod g+r   *.log
root> chmod -Rx   *.log

The "chown" command is used to reset the ownership of files after creation.

root> chown -R oinstall.dba *

The "-R" flag causes the command ro recurse through any subdirectories.

OS Users Management

The "useradd" command is used to add OS users.

root> useradd -G oinstall -g dba -d /usr/users/my_user -m -s /bin/ksh my_user

The "-G" flag specifies the primary group.
The "-g" flag specifies the secondary group.
The "-d" flag specifies the default directory.
The "-m" flag creates the default directory.
The "-s" flag specifies the default shell.

The "usermod" command is used to modify the user settings after a user has been created.

root> usermod -s /bin/csh my_user

The "userdel" command is used to delete existing users.

root> userdel -r my_user

The "-r" flag removes the default directory.
The "passwd" command is used to set, or reset, the users login password.

root> passwd my_user

The "who" command can be used to list all users who have OS connections.

root> who
root> who | head -5
root> who | tail -5
root> who | grep -i ora
root> who | wc -l

The "head -5" command restricts the output to the first 5 lines of the who command.
The "tail -5" command restricts the output to the last 5 lines of the who command.
The "grep -i ora" command restricts the output to lines containing "ora".
The "wc -l" command returns the number of lines from "who", and hence the number of connected users.

Process Management

The "ps" command lists current process information.

root> ps
root> ps -ef | grep -i ora

Specific processes can be killed by specifying the process id in the kill command.

root> kill -9 12345

uname and hostname

The "uname" and "hostname" commands can be used to get information about the host.

root> uname -a
OSF1 oradb01.lynx.co.uk V5.1 2650 alpha

root> uname -a | awk '{ print $2 }'
oradb01.lynx.co.uk

root> hostname
oradb01.lynx.co.uk

Error Lines in Files

You can return the error lines in a file using.

root> cat alert_LIN1.log | grep -i ORA-

The "grep -i ORA-" command limits the output to lines containing "ORA-". The "-i" flag makes the comparison case insensitive. A count of the error lines can be returned using the "wc" command. This normally give a word count, but the "-l" flag alteres it to give a line count.

root> cat alert_LIN1.log | grep -i ORA- | wc -l

File Exists Check

The Korn shell allows you to check for the presence of a file using the "test -s" command. In the following script a backup log is renamed and moved if it is present.

#!/bin/ksh
if test -s /backup/daily_backup.log
then
  DATE_SUFFIX=`date +"%y""%m""%d""%H""%M"`
  mv /backup/daily_backup.log /backup/archive/daily_backup$DATE_SUFFIX.log
fi

Remove Old Files

The find command can be used to supply a list of files to the rm command.

find /backup/logs/ -name daily_backup* -mtime +21 -exec rm -f {} ;

Remove DOS CR/LFs (^M)

Remove DOS style CR/LF characters (^M) from UNIX files using.

sed -e 's/^M$//' filename > tempfile

The newly created tempfile should have the ^M character removed.

Run Commands As Oracle User From Root

The following scripts shows how a number of commands can be run as the "oracle" user the "root" user.

#!/bin/ksh
su - oracle <<EOF
ORACLE_SID=LIN1; export ORACLE_SID
rman catalog=rman/rman@w2k1 target=/ cmdfile=my_cmdfile log=my_logfile append 
EOF

This is often necessary where CRON jobs are run from the root user rather than the oracle user.

Compress Files

In order to save space on the filesystem you may wish to compress files such as archived redo logs. This can be using either the gzip or the compress commands. The gzip command results in a compressed copy of the original file with a ".gz" extension. The gunzip command reverses this process.

gzip myfile
gunzip myfile.gz

The compress command results in a compressed copy of the original file with a ".Z" extension. The uncompress command reverses this process.

compress myfile
uncompress myfile

General Performance

vmstat

Reports virtual memory statistics.

# vmstat 5 3
procs -----------memory---------- ---swap-- -----io---- --system-- -----cpu------
 r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa st
 0  0      0 1060608  24372 739080    0    0  1334    63 1018 1571 14 11 66 10  0
 0  0      0 995244  24392 799656    0    0  6302   160 1221 1962 10 10 62 18  0
 0  0      0 992376  24400 799784    0    0     1    28  992 1886  3  2 95  0  0
#

free

Reports the current memory usage. The "-/+ buffers/cache:" line represents the true used and free memory, ignoring the Linux file system cache.

# free
             total       used       free     shared    buffers     cached
Mem:       8178884    4669760    3509124          0     324056    1717756
-/+ buffers/cache:    2627948    5550936
Swap:     10289148          0   10289148
#

iostat

Reports I/O statistics.

# iostat
Linux 3.2.10-3.fc16.x86_64 (maggie.localdomain)  03/19/2012  _x86_64_(4 CPU)

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
           2.02    0.23    0.51    0.78    0.00   96.46

Device:            tps    kB_read/s    kB_wrtn/s    kB_read    kB_wrtn
sda               9.23       100.55        62.99    1796672    1125538
dm-0             13.60       100.31        62.99    1792386    1125524
dm-1              0.02         0.08         0.00       1432          0

#

CPU Usage

sar

Collect, report, or save system activity information.

# sar -u 10 8
Linux 2.6.32-100.0.19.el5 (ol5-112.localdomain)  06/27/2011

02:01:09 PM       CPU     %user     %nice   %system   %iowait    %steal     %idle
02:01:19 PM       all      1.01      0.00      0.50      0.00      0.00     98.49
02:01:29 PM       all      2.72      0.00      2.62      0.10      0.00     94.56
02:01:39 PM       all      1.21      0.00      0.60      0.40      0.00     97.79
02:01:49 PM       all      1.00      0.00      0.60      0.10      0.00     98.29
02:01:59 PM       all      1.21      0.00      0.70      0.10      0.00     97.99
02:02:09 PM       all      1.01      0.00      0.40      0.10      0.00     98.49
02:02:19 PM       all      0.80      0.00      0.50      0.20      0.00     98.49
02:02:29 PM       all      2.92      0.00      2.42      0.10      0.00     94.56
Average:          all      1.48      0.00      1.04      0.14      0.00     97.34
#

mpstat

Reports processor related statistics.

# mpstat 10 2
Linux 2.6.32-100.0.19.el5 (ol5-112.localdomain)  06/27/2011

01:59:57 PM  CPU   %user   %nice    %sys %iowait    %irq   %soft  %steal   %idle    intr/s
02:00:07 PM  all    1.21    0.00    0.90    0.20    0.00    0.00    0.00   97.69    980.50
02:00:17 PM  all    0.70    0.00    0.40    0.00    0.00    0.10    0.00   98.79    973.77
Average:     all    0.95    0.00    0.65    0.10    0.00    0.05    0.00   98.24    977.14
#

top

Displays top tasks.

# top
top - 13:58:17 up 2 min,  1 user,  load average: 2.54, 1.11, 0.41
Tasks: 160 total,   6 running, 154 sleeping,   0 stopped,   0 zombie
Cpu(s): 77.1%us, 22.6%sy,  0.0%ni,  0.0%id,  0.0%wa,  0.3%hi,  0.0%si,  0.0%st
Mem:   2058872k total,   879072k used,  1179800k free,    23580k buffers
Swap:  4095992k total,        0k used,  4095992k free,   620116k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 2882 oracle    20   0  610m  64m  56m R 24.9  3.2   0:02.20 oracle
 2927 root      20   0 90328 3832 2604 R 24.6  0.2   0:00.89 Xorg
 2931 oracle    20   0  605m  34m  31m R 11.5  1.7   0:00.35 oracle
 2933 oracle    20   0  605m  34m  30m S  9.8  1.7   0:00.30 oracle
 2888 oracle    20   0  614m  52m  40m S  6.9  2.6   0:00.78 oracle
 2935 oracle    20   0  604m  22m  20m S  6.2  1.1   0:00.19 oracle
 2937 oracle    20   0  604m  19m  17m R  4.6  1.0   0:00.14 oracle
 2688 oracle    -2   0  603m  15m  13m S  4.3  0.8   0:01.08 oracle
 2685 oracle    20   0  603m  15m  13m S  0.7  0.8   0:00.22 oracle
 2939 oracle    20   0  217m 4084 3504 R  0.7  0.2   0:00.02 oracle
 2698 oracle    20   0  604m  18m  16m S  0.3  0.9   0:00.17 oracle
 2702 oracle    20   0  609m  22m  14m S  0.3  1.1   0:00.17 oracle
 2704 oracle    20   0  618m  21m  19m S  0.3  1.1   0:00.21 oracle
 2714 oracle    20   0  603m  20m  18m S  0.3  1.0   0:00.18 oracle
    1 root      20   0 10364  704  588 S  0.0  0.0   0:00.36 init
    2 root      20   0     0    0    0 S  0.0  0.0   0:00.00 kthreadd
    3 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/0
    4 root      20   0     0    0    0 S  0.0  0.0   0:00.00 ksoftirqd/0
    5 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 watchdog/0
    6 root      20   0     0    0    0 S  0.0  0.0   0:00.03 events/0
    7 root      20   0     0    0    0 S  0.0  0.0   0:00.00 cpuset
    8 root      20   0     0    0    0 S  0.0  0.0   0:00.00 khelper
    9 root      20   0     0    0    0 S  0.0  0.0   0:00.00 netns
#

The PID column can then be matched with the SPID column on the V$PROCESS view to provide more information on the process.

SELECT a.username, 
       a.osuser, 
       a.program, 
       spid, 
       sid, 
       a.serial#
FROM   v$session a,
       v$process b
WHERE  a.paddr = b.addr
AND    spid = '&pid';

See the top man page.

Hide Passwords

You may be required to use passwords in scripts calling Oracle tools, like SQL*Plus, Export/Import and RMAN etc. One method to remove the credentials from the script itself is to create a credentials file to hold them. In this case I'm using "/home/oracle/.scottcred", which contains the following.

scott/tiger

Change the permissions to make sure the file is only visible to the owner.

$ chmod 600 /home/oracle/.scottcred

Now replace references to the credentials with the contents of the file.

$ expdp < /home/oracle/.scottcred schemas=SCOTT directory=DATA_PUMP_DIR dumpfile=SCOTT.dmp logfile=expdpSCOTT.log

CRON

There are two methods of editing the crontab file. First you can use the "crontab -l > filename" option to list the contents and pipe this to a file. Once you've editied the file you can then apply it using the "crontab filename".

Login as root
crontab -l > newcron
Edit newcron file.
crontab newcron

Alternatively you can use the "crontab -e" option to edit the crontab file directly.
The entries have the following elements.

field          allowed values
-----          --------------
minute         0-59
hour           0-23
day of month   1-31
month          1-12
day of week    0-7 (both 0 and 7 are Sunday)
user           Valid OS user
command        Valid command or script.

The first 5 fields can be specified using the following rules.

*       - All available values or "first-last".
3-4     - A single range representing each possible from the start to the end of the range inclusive.
1,2,5,6 - A specific list of values.
1-3,5-8 - A specific list of ranges.
0-23/2  - Every other value in the specified range.

The following entry runs a cleanup script a 01:00 each Sunday. Any output or errors from the script are piped to /dev/null to prevent a buildup of mails to root.

0 1 * * 0 /u01/app/oracle/dba/weekly_cleanup > /dev/null 2>&1

Cluster Wide CRON Jobs On Tru64

On clustered systems cron is node-specific. If you need a job to fire once per cluster, rather than once per node you need an alternative approach to the standard cron job. One approach is put forward in the HP best practices document (Using cron in a TruCluster Server Cluster), but in my opinion a more elegant solution is proposed by Jason Orendorf of HP Tru64 Unix Enterprise Team (TruCluster Clustercron).
In his solution Jason creates a file called /bin/cronrun with the following contents.

#!/bin/ksh
set -- $(/usr/sbin/cfsmgr -F raw /)
shift 12
[[ "$1" = "$(/bin/hostname -s)" ]] && exit 0
exit 1

This script returns TRUE (0) only on the node which is the CFS serving cluster_root.
All cluster wide jobs should have a crontab entry on each node of the cluster like.

5 * * * /bin/cronrun && /usr/local/bin/myjob

Although the cron jobs fire on all nodes, the "/bin/cronrun &&" part of the entry prevents the script from running on all nodes except the current CFS serving cluster_root.

NFS Mount (Sun)

The following deamons must be running for the share to be seen by a PC.

/usr/lib/nfs/nfsd -a
/usr/lib/nfs/mountd
/opt/SUNWpcnfs/sbin/rpc.pcnfsd

To see a list of the nfs mounted drives already present type.

exportfs

First the mount point must be shared so it can be seen by remote machines.

share -F nfs -o ro /cdrom

Next the share can be mounted on a remote machine by root using.

mkdir /cdrom#1
mount -o ro myhost:/cdrom /cdrom#1

NFS Mount (Tru64)

On the server machine, if NFS is not currently setup do the following.

Application Manager -> System Admin -> Configuration -> NFS
Select the "Configure system as an NFS server" option.
Accept all defaults.

Create mount point directory.

mkdir /u04/backup

Append the following entry to the "/etc/exports" file.

/u04/backup

Make sure the correct permissions are granted on the directory.

chmod -R 777 /u04/backup

On the client machine, if NFS is not currently setup do the following.

Application Manager -> System Admin -> Configuration -> NFS
Select the "Configure system as an NFS client" option.
Accept all defaults.

Create mount point directory.

mkdir /backup

Append an following entry to the "/etc/fstab" file.

nfs-server-name:/u04/backup     /backup         nfs rw,bg,intr 0 0

Finally, mount the fileset.

mount /backup

At this point you can start to use the mount point from your client machine. Thanks to Bryan Mills for his help with Tru64.

Samba/CIFS Mount (Linux)

Create a directory to use for the mount point.

# mkdir /host

Add the following line to the "/etc/fstab" file.

//192.168.0.4/public /host   cifs rw,credentials=/root/.smbcred,uid=500,guid=500 0 0

Create a file called "/root/.smbcred" with the following contents.

username=myuser
password=mypassword

Change the permissions on the credentials file.

# chmod 600 /root/.smbcred

Mount the share.

# mount /host

PC XStation Configuration

Download the CygWin setup.exe from http://www.cygwin.com.
Install, making sure to select all the X11R6 (or XFree86 in older versions) optional packages.
If you need root access add the following entry into the /etc/securettys file on each server.

<client-name>:0

From the command promot on the PC do the following.

set PATH=PATH;c:cygwinbin;c:cygwinusrX11R6bin
XWin.exe :0 -query <server-name>

The X environment should start in a new window.
Many Linux distributions do not start XDMCP by default. To allow XDMCP access from Cygwin edit the "/etc/X11/gdm/gdm.conf" file. Under the "[xdmcp]" section set "Enable=true".
If you are starting any X applications during the session you will need to set the DISPLAY environment variable. Remember, you are acting as an XStation, not the server itself, so this variable must be set as follows.

DISPLAY=<client-name>:0.0; export DISPLAY

Useful Profile Settings

The following ".profile" settings rely on the default shell for the user being set to the Korn shell (/bin/ksh).
The backspace key can be configured by adding the following entry.

stty erase "^H"

The command line history can be accessed using the [Esc][k] by adding the following entry.

set -o vi

Auto completion of paths using a double strike of the [Esc] key can be configured by adding the following entry.

set filec

Useful Files

Here are some files that may be of use.

Path	Contents
/etc/passwd	User settings
/etc/group	Group settings for users.
/etc/hosts	Hostname lookup information.
/etc/system	Kernel parameters for Solaris.
/etc/sysconfigtab	Kernel parameters for Tru64.
/etc/sysctl.conf	Kernel parameters for Linux.

Architecture

2012-06-24T03:39:00.000-07:00

Oracle Apps R12 File system Architecture

Base Directory: The directory where the Oracle Applications is installed. This is a generic directory.

I will suppose that the Base Directory is /APPS

$ORACLE_HOME (for the database tier): /APPS/db/tech_st/10.2.0

$APPL_TOP: /APPS/apps/apps_st/appl

$COMMON_TOP: /APPS/apps/apps_st/comn

$ORACLE_HOME (for the apps tier): /APPS/apps/tect_st/10.1.2

$IAS_ORACLE_HOME (for the apps tier): /APPS/apps/tect_st/10.1.3

$INST_TOP: /APPS/inst/apps/<SID_localhost> contains certifications, configurations, logs for the servers.

Source Node = apps.localdomain	Destination Node = linux1.localdomain
/APPS_MI/visappl	/APPS/visappl
/APPS_MI/viscomn/html	/APPS/viscomn/html
/APPS_MI/viscomn/java	/APPS/viscomn/java
/APPS_MI/viscomn/util	/APPS/viscomn/util
/APPS_MI/viscomn/clone	/APPS/viscomn/clone
/APPS_MI/viscomn/_pages	/APPS/viscomn/_pages
/APPS_MI/visora/8.0.6	/APPS/visora/8.0.6
/APPS_MI/visora/iAS	/APPS/visora/iAS