ADPATCH Options

ADPATCH Options

After having talked about the best practices related to applications patching. In today’s post i will talk about some  frequently used options with adpatch. It is important to note here that the options described here are for information purposes only and you must understand them completely before using them on your system. Also any special instructions specified in the patch readme file automatically overrides the information cointained in this post.

You can execute adpatch by logging in as the applications OS user and sourcing the appropriate environment file.

#su – applmgr

$cd SAMAPPL

$. ./APPSORA.env

$adpatch

By default adpatch does not take any clause, but there are some clauses that you could use with adpatch

Running a patch in test mode
You can use the apply clause with adpatch to specify weather to run the patch in TEST mode or not, when you run the patch in  test mode it does not do any changes but runs generates a log fiule with all the actions it would have performed.

$adpatch apply=n|y
The default is apply=y

Pre-install Mode
You can also run a patch in pre install mode, this would be done normally during an upgrade or consolidated update. When a patch is applied in a preinstall mode the all the AD utilities are updated before the upgrade or update.

$adpatch preinstall=y
The default is preinstall=n

Other Options with adpatch
You can use the options clause to specify some of the other options available with adpatch.

Autoconfig

You can use the options=noautoconfig top specify autopatch that you do not wish to run autoconfig as a part of the patch  application. This can be useful when applying a large number of patches when they are not merged. By default autoconfig is run  as a part of adpatch.

$adpatch options=noautoconfig

Checkfile
The chekfile option of adpatch tells adpathc to check for already executed exec, SQL, and exectier commands.You can use  options=nocheckfile skips this check, however this can cause performance overheds so should be used only when specified.

$adpatch options=nocheckfile

Compile Database

By defaulty autopatch compiles the invalid objects after the patch application, in case you wish not to do so you can specify  options=nocompiledb along with autopatch.

$adpatch options=nocompiledb

Compile JSP
By defaulty autopatch compiles the java server pages (jsp) after the patch application, in case you wish not to do so you can specify options=nocompilejsp along with autopatch.

$adpatch options=nocompilejsp

Copy Portion
If you wish adpatch not to execute the commands present in the copy driver portion of the patch you can use the  options=nocopyportion.

$adpatch options=nocopyportion

Database Portion
If you wish adpatch not to execute the commands present in the database driver portion of the patch you can use the options=nodatabaseportion.

$adpatch options=nodatabaseportion

Generate Portion

If you wish adpatch not to execute the commands present in the generate driver portion of the patch you can use the options=nogenerateportion

$adpatch options=nogenerateportion

Maintenance Mode

If you wish to apply a patch regardless of the system being in maintenance mode you can use options=hotpatch.

$adpatch options=hotpatch

Integrity Check
If you wish to check the integrity of the patch you can use the options=integrity. Since metalink patches are pre checked for  their integrity it is generally not required to do an explicit check and the default value is nointegrity.

$adpatch options=integrity

Maintain MRC
You can use the maintainmrc option to specify weather you wish adpatch to execute the Maintain MRC schema as a part of the patch application or not. By default maintain MRC is done for standard patches and is disbaled for tarnslation and documentation patches.

$adpatch options=nomaintainmrc

Pre requisite Patch Check
If you wish adpatch not to check for pre requisite patches before application of the main patch you can use options=noprereq.By default pre requsite checking is enabled.

$adpatch options=noprereq

Validate Schemas
If you wish adpatch to explicitly validate all the registed schems by making a connection you can use options=validate. By  default this validation is not performed.

$adpatch options=validate

Java Classes

If you wish adpatch not to copy new java classes from the patch you can use options=nojcopy.By default java classes are copied.

$adpatch options=nojcopy

Force Copy

By default adpatch copies the files without check the version of the existing files already present on the system.If you do  not wish the newer version of the file to be replaced by the older version contained in the patch use options=noforcecopy.

$adpatch options=noforcecopy

Relinking
If you wish adpatch not do perform relinking you can use options=nolink.

$adpatch options=nolink

Generate Forms
If you wish adpatch not to generate the forms files you can specify options=nogenform.

$adpatch options=nogenform

Generate Reports
If you wish adpatch not to generate the report files you can specify options=nogenrep.

$adpatch options=nogenrep

You could specify multiple options at the command line using the , delimiter.

$adpatch options=hotpatch,nojcopy

Posted by Sam at 05:48 PM | Permalink | Comments (8) | TrackBacks (0)

January 02, 2007

Getting Familiar with RTCCTL

Getting Familiar with RTCCTL

One of the components that comes with Oracle Collaboration Suite is the Real Time Collaboration or RTC. The two main components of Real-Time Collaboration are

• Oracle Web Conferencing


• Oracle Messenger

Other than using OPMNCTL as described in my previous post to manage the services of Oracle Collaboration Suite, Oracle has also provided a utility rtcctl which can be used to manage the specific components which relate to Oracle Web Conferencing and Oracle Messenger. The rtcctl is a command-line utility which provides an interface to configure and administer your

Real-Time Collaboration components. This configuration and administration for RTC components is done through a set of properties which control the behavior of your RTC environment.

The rtcctl utility is located in the $ORACLE_HOME/imeeting/bin directory in your Oracle Collaboration Suite middle tier servers.

The RTCCTL utility allows you to

• View the status of the process related to Real-Time Collaboration.


• Start and stop all or specific components.


• View the value of Real-Time Collaboration specific components.


• Set the value of Real-Time Collaboration specific components.


• To view and Modify an RTC user’s Access.


• Creating and Using a Broadcast Group.

To get the status of RTC
The getstate command executed within rtcctl show you the status of the components related to Real-Time Collaboration

rtcctl> getstate

ID      COMPONENT_NAME TYPE      STATUS         NUM_PROCS

10007   rtc-connmgr    connmgr   UP             2

10000   rtc-confsvr    confsvr   UP             4

10006   rtc-imrtr      imrtr     ACTIVE-OK      1

10008   rtc-voiceproxy voiceproxyUP             1

10004   rtcpm          rtcpm     UP             1

10003   rtc-rdtr       rdtr      UP             1

10002   rtc-mx         mx        UP             1

Setting RTC porperty Values
The getProperties command show a list of properties that are applicable to the current instance of RTC

rtcctl> getProperties

ApacheProtocolSecure=”false”

ApacheWebHost=”samlnx.appsdbablog.com”

ApacheWebPort=”7780″

ApacheWebSecurePort=”8250″

DefaultTimeZoneName=”America/Los_Angeles”

EmailEnabled=”false”

IMDomainNames=”["appsdbablog.com"]”

RTCSSLSupportEnabled=”false”

SmtpHost=”samlnx.appsdbablog.com”

SmtpPort=”25″

VoiceDialinPrefix=”"

To get a the value of a specific property you could use the getpropety command with the -pname clause which refers to the property name

rtcctl> getproperty -pname IMDomainNames

The effective value for instance of the property “IMDomainNames” is “["appsdbablog.com"]”

The getproperties command along with the -maxlevel all clause displays a complete list of all RTC related properties.

The setProperty command allows you to set the value for a specific property

rtcctl> setProperty -pname property-name -pvalue property-name

You can use the rtcctl utility to configure and administer multiple instances of RTC running at your site.

To set properties at an instance level you can use the -i clause and to set it at a system level use the -system clause. By default the properties are set at the system level.

Startup and Shutdown Of RTC Services
The stop command shutsdown down all RTC managed process

rtcctl> stop

rtcctl> getstate

ID      COMPONENT_NAME TYPE      STATUS         NUM_PROCS

10007   rtc-connmgr    connmgr   DOWN           0

10000   rtc-confsvr    confsvr   DOWN           0

10006   rtc-imrtr      imrtr     DOWN           0

10008   rtc-voiceproxy voiceproxyDOWN           0

10004   rtcpm          rtcpm     DOWN           0

10003   rtc-rdtr       rdtr      DOWN           0

10002   rtc-mx         mx        DOWN           0

The start command startsup up the RTC managed processes

rtcctl> start

rtcctl> getstate

ID      COMPONENT_NAME TYPE      STATUS         NUM_PROCS

10007   rtc-connmgr    connmgr   UP             2

10000   rtc-confsvr    confsvr   UP             4

10006   rtc-imrtr      imrtr     ACTIVE-OK      1

10008   rtc-voiceproxy voiceproxyUP             1

10004   rtcpm          rtcpm     UP             1

10003   rtc-rdtr       rdtr      UP             1

10002   rtc-mx         mx        UP             1

Individual components can be started and stopped either by using the component type or the component name clause along with the start or stop command.

rtcctl> stop -cname rtc-confsvr
The stops the rtc-confsvr component.

rtcctl> start -ctype confsvr
This starts the confsvr type component.

RTC user Management
The modifyRole command can be used to modify the existing role of user

rtcctl> modifyRole -username sam -rolename businessadmin

Broadcast Groups
You can also use the RTCCTL utility to create broadcast groups.

rtcctl> addGroup -groupname APPS_DBA_SUPPORT -type A -owner sam@appsdbablog.com -subscription S -permission R  -groupdisplayname “DBA Support Team”

Add group ‘APPS_DBA_SUPPORT’, type = A, owner = sam@appsdbablog.com, subscription = S, permission = R, groupdisplayname = DBA Support Team

You can user the -permission = O to create a open group which does not require approval for joining

The getGroups command displays the available groups in the system

rtcctl> getGroups

Groups:
Group IM Address: apps_dba_support@groups.appsdbablog.com
Group Display Name: DBA Support Team

Owner IM Address: sam@appsdbablog.com
Type: A

Subscription Type: S

Subscription Permission: R

Number of Members: 0

You can use the addGroupMember to add a new member to this group explicitly

rtcctl> addGroupMember -groupname APPS_DBA_SUPPORT -username samtest

Add Member ‘samtest’ to group ‘APPS_DBA_SUPPORT’

Similarly the deleteGroupMember command removes a user from the group explicilty.

The deleteGroup command can be used to delete an existing group

rtcctl> deleteGroup -groupname APPS_DBA_SUPPORT

Delete group ‘APPS_DBA_SUPPORT’

Getting real Time Statistics
The getMonitorStats command allows you to get real time statistics of your RTC environment.

rtcctl> getMonitorStats

Instance – OCSMI_home.samlnx.appsdbablog.com:

Component Name: rtc-confsvr, Component Type: confsvr

SERVICE_NAME                                 TMTGS CMTGS CLTS TMEM    UMEM

confsvr:OCSMI_home.samlnx.appsdbablog.com.rtc-confsvr.00     0     0    4,100K  2,620K

confsvr:OCSMI_home.samlnx.appsdbablog.com.rtc-confsvr.10     0     0    4,092K  2,782K

confsvr:OCSMI_home.samlnx.appsdbablog.com.rtc-confsvr.20     0     0    4,092K  2,800K

confsvr:OCSMI_home.samlnx.appsdbablog.com.rtc-confsvr.30     0     0    4,092K  2,588K

Component Name: rtc-imrtr, Component Type: imrtr presence

Testing RTC
Th runTest command allows you to run a series of tests against your RTC environment to test the configuration.

rtcctl> runtests

Instance – OCSMI_home.samlnx.appsdbablog.com:

TEST NAME      SUCCESS

mtgtest        true

dbtest         true

apptest        true

proxytest      false

emailtest      false

imtest         true

servletAccessTesttrue

ADPATCH Options