How to submit concurrent program from command promot / shell

We can submit concurrent programs from OS command / shell prompt using CONCSUB utility. Following is the syntax of the same:

CONCSUB <APPS username>/<APPS password>
<responsibility application short name>
<responsibility name>
<username>
[WAIT=N|Y|<n seconds>]
CONCURRENT
<program application short name>
<program name>
[PROGRAM_NAME=”<description>”]
[REPEAT_TIME=<resubmission time>]
[REPEAT_INTERVAL= <number>]
[REPEAT_INTERVAL_UNIT=< resubmission unit>]
[REPEAT_INTERVAL_TYPE=< resubmission type>]
[REPEAT_END=<resubmission end date and time>]
[NLS_LANGUAGE=<language of the request>]
[NLS_TERRITORY=<territory of the request>]
[START=<date>]
[IMPLICIT=< type of concurrent request>
[<parameter 1> … <parameter n>]

Examples:

Active Users
CONCSUB apps/[apps_pwd] SYSADMIN “System Administrator” SYSADMIN WAIT=N CONCURRENT FND FNDSCURS

Prints Environment Variables
CONCSUB apps/[apps_pwd] SYSADMIN “System Administrator” SYSADMIN WAIT=N CONCURRENT FND FNDPRNEV APPL_TOP

Apr 3rd, 2009 | Posted by Tushar Thakker | Filed under Concurrent manager, Oracle, Oracle Applications, Oracle Applications DBA

Oracle Applications Concurrent Request phase codes and status codes

 

Table Name: FND_CONCURRENT_REQUESTS

Column Name: PHASE_CODE
 

Value  Meaning
 C  Completed
 I  Inactive
 P  Pending
 R  Running

 
Table Name: FND_CONCURRENT_REQUESTS

Column Name: STATUS_CODE
 

Value  Meaning
 D  Cancelled
 U  Disabled
 E  Error
 M  No Manager
 R  Normal
 I  Normal
 C  Normal
 H  On Hold
 W  Paused
 B  Resuming
 P  Scheduled
 Q  Standby
 S  Suspended
 X  Terminated
 T  Terminating
 A  Waiting
 Z  Waiting
 G  Warning
Apr 3rd, 2009 | Posted by Tushar Thakker | Filed under Concurrent manager, Oracle, Oracle Applications, Oracle Applications DBA

Oracle SQL hints

/*+ hint */

/*+ hint(argument) */

/*+ hint(argument-1 argument-2) */

All hints except /*+ rule */ cause the CBO to be used. Therefore, it is good practise to analyze the underlying tables if hints are used (or the query is fully hinted.

There should be no schema names in hints. Hints must use aliases if alias names are used for table names. So the following is wrong:

select /*+ index(scott.emp ix_emp) */ from scott.emp emp_alias

better:

select /*+ index(emp_alias ix_emp) */ … from scott.emp emp_alias

Why using hints

Read more…

Apr 2nd, 2009 | Posted by Tushar Thakker | Filed under Applications Performance Tuning, Database Performance Tuning, Oracle, Oracle DBA