Wednesday, 27 January 2016

WFLOAD Command to download/upload Oracle Workflow




WFLOAD Command to download Oracle Workflow

Syntax-
WFLOAD <apps/pwd>@<connectstring> 0 Y DOWNLOAD FILE_NAME.wft item_type

Modes-
UPGRADE – Protection and Customization levels of data
UPLOAD  - Only protection level of data.Not supporting customisation
FORCE   - Force upload, protection or customization not supported
For example-
WFLOAD apps/passed123@DEVL 0 Y DOWNLOAD APEXP_TEMP.wft APEXP


WFLOAD Command to upload Oracle Workflow

Syntax-
WFLOAD <apps/pwd>@<connectstring> 0 Y {UPLOAD | UPGRADE | FORCE} FILE_NAME.wft

For Example-
WFLOAD apps/passed123@DEVL 0 Y UPLOAD APEXP_TEMP.wft


Seeded Workflow Files Location

You can also download seeded workflow definition files directly from below directory-

$<Application_TOP>/patch/115/import/<LANG>

For example- Account Payables workflow file can be found at-
$AP_TOP/patch/115/import/US 
 
Thanks 
Srini

Refreshing VS Cloning an e-Business Suite Environment


Just a quick note on refreshing vs cloning, what each of them means and when you should perform them.

What is Refreshing?

A refresh is where the data in the target environment has been synchronized with a copy of production. This is done by taking a copy of the production database and restoring it to the target environment.

What is Cloning?

Cloning means that an identical copy of production has been taken and restore to the target environment. This is done by taking both a copy of the production database as well as all of the application files.

When should you Clone or Refresh?

There are a couple of scenarios when cloning should be performed:

1. Building a new environment.
 
2. Patches or other configuration changes have been made to the target environment so that they are now out of sync.

3. Beginning of development cycles. Before major development efforts take place, its wise to re-clone dev, test environments so that your 100% positive that the environments are in sync.

There is only one scenario in which you should refresh an environment:

1. Your 100% confident that the environments are in sync and need an updated copy of the production data in order to reproduce issues.

Technically, if proper change control processes are being followed, test and production environments should be identical. So in the case of test, you should be able to get away with performing refreshes. However, to ease concerns and for comfort levels, test environments are usually re-cloned at the beginning of new development cycles as well.

Thanks
Srini

File System ARCHITECTURE in R12



File System ARCHITECTURE

R12  File System COMPLETE ARCHITECTURE






INST_TOP in R12

INST TOP directory:

(applmgr) - ls
 
 admin/ appl/ certs/ logs/ ora/ out/ pids/ portal/ rgf/
 
(applmgr) -



The Whys and wherefores:

You may get a question why is the change??

There is a need to separate

Code
Data
Config

To ease maintenance of the system. To avoid NFS/MUTEX related issues. Above issue will get resolved if the configuration/lcck files are stored in local system. Another advantage is to gain performance accessing local file system is better than NFS file system.

This directory $INST_TOP got introduced newly in R12. Instance top contains all the config files, log files, ssl certificates, document root etc. Addition of this directory makes the middle-tier more organised, since data is kept separate from config/log files. Another advantage is that, multiple instances can easily share the same middle tier. To create a new instance that shares an existing middle-tier, just create a new instance_top with proper config files and NFS mount the middle tier in the server.
INSTANCE TOP - STRUCTURE
$INST_TOP: APPS_BASE/inst/apps/CONTEXT_NAME/
/admin

    /scripts
ADMIN_SCRIPTS_HOME: Find all AD scripts here
/appl
APPL_CONFIG_HOME. For standalone envs, this is set to $APPL_TOP
    /fnd/12.0.0/secure
FND_SECURE: dbc files here
    /admin
All Env Config files here
/certs
SSL Certificates go here
/logs
LOG_HOME: Central log file location. All log files are placed here (except adconfig)
/ora
ORA_CONFIG_HOME
    /10.1.2
'C' Oracle home config, Contains tnsnames and forms listener servlet config files
    /10.1.3
Apache & OC4J config home, Apache, OC4J and opmn
This is the 'Java' oracle home configuration for OPMN, Apache and OC4J
/pids
Apache/Forms server PID files here
/portal
Apache's DocumentRoot folder

AD SCRIPTS
$ADMIN_SCRIPTS_HOME: $INST_TOP/admin/scripts
adautocfg.sh run autoconfig     
adstpall.sh stop all services
adstrtal.sh start all services
adapcctl.sh start/stop/status Apache only
adformsctl.sh start/stop/status OC4J Forms
adoacorectl.sh start/stop/status OC4J oacore
adopmnctl.sh start/stop/status opmn
adalnctl.sh start/stop RPC listeners (FNDFS/FNDSM)
adcmctl.sh start/stop Concurrent Manager
gsmstart.sh start/stop FNDSM
jtffmctl.sh start/stop Fulfillment Server
adpreclone.pl Cloning preparation script
adoafmctl.sh adoafmctl.sh to start/stop/status OC4J oafm
(webservice, mapviewer)
adexecsql.pl Execute sql scripts that update the profiles in an AutoConfig run
java.sh Call java executable with additional args, (used by opmn, Conc. Mgr)

LOG FILES
Location of various log files
AD Script log files (adapcctl.sh,...) $INST_TOP/logs/appl/admin/log
CM Log Files ($APPLCSF/$APPLLOG) $INST_TOP/logs/appl/conc/log
AD tools log files (adpatch, ...) $APPL_CONFIG_HOME/admin/$TWO_TASK/log
OPMN Log Files (Text & ODL) $INST_TOP/logs/ora/10.1.3/opmn
Apache Log Files (Text & ODL) $INST_TOP/logs/ora/10.1.3/Apache
OC4J Log Files (Text) $INST_TOP/logs/ora/10.1.3/j2ee/oacore/
OC4J Log Files (ODL) $INST_TOP/logs/ora/10.1.3/j2ee/oacore/log/oacore_default_group_1/oc4j

SSL CERTIFICATES
$INST_TOP/certs
/Apache/ewallet.p12
 
/opmn/cwallet.sso
 
/opmn/ewallet.p12
 
certs is the default directory for SSL or any other certificate files
used by this instance. To use a centrally staged certificate, change
the appropriate context file and run autoconfig

All DBA Views




 DBA Views 


Storage Information
DBA_EXTENTS, DBA_FREE_SPACE, DBA_OBJECTS,
DBA_OBJECT_SIZE, DBA_SEGMENTS, DBA_TABLESPACES,
DBA_ROLLBACK_SEGS, DBA_UNDO_EXTENTS

Operating System
DBA_DATA_FILES, DBA_EXP_FILES, DBA_TEMP_FILES

Privileges
DBA_COL_PRIVS, DBA_PROFILES, DBA_ROLES,
DBA_ROLE_PRIVS, DBA_SYS_PRIVS, DBA_TAB_PRIVS,
DBA_UPDATABLE_COLUMNS

Indexes
DBA_INDEXES, DBA_IND_COLUMNS,
DBA_IND_EXPRESSIONS, DBA_IND_PARTITIONS

Tables/Views
DBA_TABLES, DBA_TAB_COLUMNS, DBA_TAB_PARTITIONS,
DBA_TAB_COMMENTS,
DBA_UNUSED_COL_TABS, DBA_VIEWS

Constraints
DBA_CONSTRAINTS, DBA_CONS_COLUMNS

Triggers
DBA_TRIGGERS, DBA_TRIGGER_COLS,
DBA_INTERNAL_TRIGGERS

Materialized Views
DBA_MVIEW_AGGREGATES, DBA_MVIEW_ANALYSIS,
DBA_MVIEW_DETAIL_RELATIONS, DBA_MVIEW_JOINS,
DBA_MVIEW_KEYS

Partitions
DBA_PART_COL_STATISTICS, DBA_PART_HISTOGRAMS,
DBA_PART_INDEXES, DBA_PART_KEY_COLUMNS,
DBA_PART_LOBS, DBA_PART_TABLES,
DBA_IND_SUBPARTITIONS, DBA_LOB_PARTITIONS,
DBA_LOB_SUBPARTITIONS

Objects, Methods and Types
DBA_OBJECT_TABLES, DBA_METHOD_PARAMS,
DBA_METHOD_RESULTS, DBA_TYPES, DBA_TYPE_ATTRS,
DBA_TYPE_METHODS, DBA_DIMENSIONS, DBA_LOBS

Operators
DBA_OPANCILLARY, DBA_OPARGUMENTS,
DBA_OPBINDINGS, DBA_OPERATORS

Summaries
DBA_SUMMARIES, DBA_SUMMARY_AGGREGATES,
DBA_SUMMARY_DETAIL_TABLES, DBA_SUMMARY_JOINS,
DBA_SUMMARY_KEYS

Miscellaneous
DBA_DB_LINKS, DBA_SOURCE, DBA_SEQUENCES,
DBA_SYNONYMS, DBA_USERS, DBA_OUTLINES,
DBA_JOBS, DBA_JOBS_RUNNING, DBA_LIBRARIES,
DBA_PENDING_TRANSACTIONS, DBA_RULESETS,
DBA_OUTLINE_HINTS, DBA_POLICIES,
DBA_SUBPART_KEY_COLUMNS, DBA_TS_QUOTAS,
DBA_JAVA_POLICY, USER_JAVA_POLICY

Dynamic Performance Views

Instance Level Tuning

v$GLOBAL_TRANSACTION, v$OBJECT_DEPENDENCY,
 v$SHARED_POOL_RESERVED, v$SORT_SEGMENT,
v$SYSTEM_CURSOR_CACHE, v$SORT_USAGE, v$STATNAME,
v$SYSSTAT, v$SYSTEM_EVENT, v$TRANSACTION, v$LATCH,
v$LIBRARYCACHE, v$ROLLSTAT, v$ROWCACHE,
vRSGASTAT, v$SQLAREA, v$SQLTEXT, v$WAITSTAT

Recovery Based Views
v$ARCHIVE, v$ARCHIVE_DEST, v$BACKUP_CORRUPTION,
v$BACKUP_DEVICE, v$BACKUP_REDOLOG,
v$DELETED_OBJECT, v$RECOVERY_LOG, v$RECOVER_FILE,
v$ARCHIVED_LOG, v$BACKUP, v$BACKUP_DATAFILE,
v$BACKUP_PIECE, v$BACKUP_SET,
v$RECOVERY_FILE_STATUS, v$RECOVERY_STATUS,
v$DATABASE_BLOCK_CORRUPTION,
v$DATABASE_INCARNATION

Cache Views
v$CACHE, 
v$LIBRARYCACHE, 
v$SUBCACHE,
v$DB_OBJECT_CACHE, 
v$ROWCACHE

Control File Views
v$CONTROLFILE, 
v$CONTROLFILE_RECORD_SELECTION

Cursor and SQL Views
v$SYSTEM_CURSOR_CACHE, v$OPEN_CURSOR, v$SQLAREA,
v$SQL, v$SQLTEXT, v$SQLTEXT_WITH_NEWLINES,
v$SQL_CURSOR, v$SQL_BIND_METADATA,
v$SQL_SHARED_MEMORY, v$SQL_BIND_DATA,
v$SQL_WORKAREA, v$SQL_WORKAREA_ACTIVE

Security Views
v$ENABLEDPRIVS, v$PWFILE_USERS

Session Views
v$ACCESS, v$MYSTAT, v$PROCESS, v$SESSION ,
v$SESSION_CONNECT_INFO, v$SESSION_CURSOR_CACHE,
v$SESSION_EVENT, v$SESSION_LONGOPS,
v$SESSION_OBJECT_CACHE, v$SESSION_WAIT, v$SESSTAT
(needs v$statname, v$session join), v$SESS_IO

Latch and Lock Views
v$BUFFER_POOL, v$CACHE_LOCK, v$CLASS_PING,
v$DLM_CONVERT_LOCAL, v$DLM_CONVERT_REMOTE,
v$DLM_LATCH, v$DLM_MISC, v$ENQUEUE_LOCK,
v$EVENT_NAME, v$FALSE_PING, v$FILE_PING, v$LATCH,
v$LATCHHOLDER, v$LATCHNAME, v$LATCH_CHILDREN,
v$LATCH_MISSES, v$LATCH_PARENT, v$LOCK,
v$LOCK_ACTIVITY, v$LOCK_ELEMENT, v$LOCKED_OBJECT,
v$LOCKS_WITH_COLLISIONS, v$PING, v$RESOURCE,
v$RESOURCE_LIMIT, v$TRANSACTION_ENQUEUE, v$LOCK

Instance Views
v$ACTIVE_INSTANCES, v$BGPROCESS, v$BH,
v$COMPATIBILITY, v$COMPATSEG, v$COPY_CORRUPTION,
v$DATABASE, v$DATAFILE, v$DATAFILE_COPY,
v$DATAFILE_HEADER, v$DBFILE, v$DBLINK, v$DB_PIPES,
v$INSTANCE, v$LICENSE, v$OFFLINE_RANGE, v$OPTION,
v$ROLLSTAT, v$SGA, v$SGA_STAT, v$TABLESPACE,
v$TRANSACTION, v$UNDOSTAT, v$VERSION

Fixed Views
v$FIXED_TABLE, v$FIXED_VIEW_DEFINITION,
v$INDEXED_FIXED_COLUMN

Miscellaneous Views
v$TIMER, v$TYPE_SIZE, v$SEQUENCES
MTS and Parallel Server Views
v$CIRCUIT, v$DISPATCHER, v$DISPATCHER_RATE, v$MTS,
v$QUEUE, v$REQDIST, v$SHARED_SERVER, v$THREAD

File Mapping
v$MAP_LIBRARY, v$MAP_FILE, v$MAP_FILE_EXTENT,
v$MAP_ELEMENT, v$MAP_EXT_ELEMENT,
v$MAP_SUBELEMENT, v$MAP_COMP_LIST,
v$MAP_FILE_IO_STACK


Thanks
Srini