For scping large files, it is best to let them run in the background.
follow the steps below to transfer files using SCP command in the background
1) execute the normal scp command, eg:
$ scp localfile.tar.bz2 user@server.ch:/path/on/server/
2) after confirming the key and authentificating (if necessary), you can "stop" the job by pressing : ctrl + Z
[1]+ Stopped scp localfile.tar.bz2 user@server.ch:/path/on/server/
3) then you can proceed the job in the background by typing
$ bg
[1]+ scp localfile.tar.bz2 user@server.ch:/path/on/server/ &
4) finally, to make sure the process is working in background, issue the “jobs” command
$ jobs
[1]+ Running scp localfile.tar.bz2 user@server.ch:/path/on/server/ &
Now the session can be exited with the file transfer unaffected.
Wednesday, June 3, 2009
How to recover and open the database if the archivelog required for recovery is either missing, lost or corrupted?
The assumption here is that we have exhausted all possible locations to find another good and valid copy or backup of the archivelog that we are looking for, which could be in one of the following:
- directories defined in the LOG_ARCHIVE_DEST_n
- another directory in the same server or another server
- standby database
- RMAN backup
- OS backup
If the archivelog is not found in any of the above mentioned locations, then the approach and strategy on how to recover and open the database depends on the SCN (System Change Number) of the datafiles, as well as, whether the log sequence# required for the recovery is still available in the online redologs.
For the SCN of the datafiles, it is important to know the mode of the database when the datafiles are backed up. That is whether the database is open, mounted or shutdown (normally) when the backup is taken.
If the datafiles are restored from an online or hot backup, which means that the database is open when the backup is taken, then we must apply at least the archivelog(s) or redolog(s) whose log sequence# are generated from the beginning and until the completion of the said backup that was used to restore the datafiles.
However, if the datafiles are restored from an offline or cold backup, and the database is cleanly shutdown before the backup is taken, that means that the database is either not open, is in nomount mode or mounted when the backup is taken, then the datafiles are already synchronized in terms of their SCN. In this situation, we can immediately open the database without even applying archivelogs, because the datafiles are already in a consistent state, except if there is a requirement to roll the database forward to a point-in-time after the said backup is taken.
The critical key thing here is to ensure that all of the online datafiles are synchronized in terms of their SCN before we can normally open the database. So, run the following SQL statement, as shown below, to determine whether the datafiles are synchronized or not. Take note that we query the V$DATAFILE_HEADER, because we want to know the SCN recorded in the header of the physical datafile, and not the V$DATAFILE, which derives the information from the controlfile.
select status, checkpoint_change#, to_char(checkpoint_time, 'DD-MON-YYYY HH24:MI:SS') as checkpoint_time, count(*) from v$datafile_header group by status, checkpoint_change#, checkpoint_time order by status, checkpoint_change#, checkpoint_time;
The results of the above query must return one and only one row for the online datafiles, which means that they are already synchronized in terms of their SCN. Otherwise, if the results return more than one row for the online datafiles, then the datafiles are still not synchronized yet. In this case, we need to apply archivelog(s) or redolog(s) to synchronize all of the online datafiles. Take note of the CHECKPOINT_TIME in the V$DATAFILE_HEADER, which indicates the date and time how far the datafiles have been recovered.
The results of the query above may return some offline datafiles. So, ensure that all of the required datafiles are online, because we may not be able to recover later the offline datafile once we open the database in resetlogs. Even though we can recover the database beyond resetlogs for the Oracle database starting from 10g and later versions due to the introduction of the format "%R" in the LOG_ARCHIVE_FORMAT, it is recommended that you online the required datafiles now than after the database is open in resetlogs to avoid any possible problems. However, in some cases, we intentionally offline the datafile(s), because we are doing a partial database restore, or perhaps we don't need the contents of the said datafile.
You may run the following query to determine the offline datafiles:
select file#, name from v$datafile where file# in (select file# from v$datafile_header where status='OFFLINE');
You may issue the following SQL statement to change the status of the required datafile(s) from "OFFLINE" to "ONLINE":
alter database datafile online;
If we are lucky that the required log sequence# is still available in the online redologs and the corresponding redolog member is still physically existing on disk, then we may apply them instead of the archivelog. To confirm, issue the following query, as shown below, that is to determine the redolog member(s) that you can apply to recover the database:
set echo on
feedback on
pagesize 100
numwidth 16
alter session set nls_date_format = 'DD-MON-YYYY HH24:MI:SS';
select LF.member, L.group#, L.thread#, L.sequence#, L.status, L.first_change#, L.first_time, DF.min_checkpoint_change# from v$log L, v$logfile LF, (select min(checkpoint_change#) min_checkpoint_change# from v$datafile_header where status='ONLINE') DF where LF.group# = L.group# and L.first_change# >= DF.min_checkpoint_change#;
If the above query returns no rows, because the V$DATABASE.CONTROLFILE_TYPE has a value of "BACKUP", then try to apply each of the redolog membes one at a time during the recovery. You may run the following query to determine the redolog members:
select * from v$logfile;
If you have tried to apply all of the online redolog members instead of an archivelog during the recovery, but you always received the ORA-00310 error, as shown in the example below, then the log sequence# required for recovery is no longer available in the online redolog.
ORA-00279: change 189189555 generated at 11/03/2007 09:27:46 needed for thread 1
ORA-00289: suggestion : +BACKUP ORA-00280: change 189189555 for thread 1 is in sequence #428 Specify log: {=suggested filename AUTO CANCEL} +BACKUP/prmy/onlinelog/group_2.258.603422107
ORA-00310: archived log contains sequence 503; sequence 428 required
ORA-00334: archived log: '+BACKUP/prmy/onlinelog/group_2.258.603422107'
After trying all of the possible solutions mentioned above, but you still cannot open the database, because the archivelog required for recovery is either missing, lost or corrupted, or the corresponding log sequence# is no longer available in the online redolog, since they are already overwritten during the redolog switches, then we cannot normally open the database, since the datafiles are in an inconsistent state. So, the following are the 3 options available to allow you to open the database:
Option#1: Force open the database by setting some hidden parameters in the init.ora. Note that you can only do this under the guidance of Oracle Support with a service request. But there is no 100% guarantee that this will open the database. However, once the database is opened, then we must immediately rebuild the database. Database rebuild means doing the following, namely: (1) perform a full-database export, (2) create a brand new and separate database, and finally (3) import the recent export dump. This option can be tedious and time consuming, but once we successfully open the new database, then we expect minimal or perhaps no data loss at all. Before you try this option, ensure that you have a good and valid backup of the current database.
Option#2: If you have a good and valid backup of the database, then restore the database from the said backup, and recover the database by applying up to the last available archivelog. In this option, we will only recover the database up to the last archivelog that is applied, and any data after that are lost. If no archivelogs are applied at all, then we can only recover the database from the backup that is restored. However, if we restored from an online or hot backup, then we may not be able to open the database, because we still need to apply the archivelogs generated during the said backup in order to synchronize the SCN of the datafiles before we can normally open the database.
Option#3: Manually extract the data using the Oracle's Data Unloader (DUL), which is performed by Oracle Field Support at the customer site on the next business day and for an extra charge. If the customer wants to pursue this approach, we need the complete name, phone# and email address of the person who has the authority to sign the work order in behalf of the customer.
- directories defined in the LOG_ARCHIVE_DEST_n
- another directory in the same server or another server
- standby database
- RMAN backup
- OS backup
If the archivelog is not found in any of the above mentioned locations, then the approach and strategy on how to recover and open the database depends on the SCN (System Change Number) of the datafiles, as well as, whether the log sequence# required for the recovery is still available in the online redologs.
For the SCN of the datafiles, it is important to know the mode of the database when the datafiles are backed up. That is whether the database is open, mounted or shutdown (normally) when the backup is taken.
If the datafiles are restored from an online or hot backup, which means that the database is open when the backup is taken, then we must apply at least the archivelog(s) or redolog(s) whose log sequence# are generated from the beginning and until the completion of the said backup that was used to restore the datafiles.
However, if the datafiles are restored from an offline or cold backup, and the database is cleanly shutdown before the backup is taken, that means that the database is either not open, is in nomount mode or mounted when the backup is taken, then the datafiles are already synchronized in terms of their SCN. In this situation, we can immediately open the database without even applying archivelogs, because the datafiles are already in a consistent state, except if there is a requirement to roll the database forward to a point-in-time after the said backup is taken.
The critical key thing here is to ensure that all of the online datafiles are synchronized in terms of their SCN before we can normally open the database. So, run the following SQL statement, as shown below, to determine whether the datafiles are synchronized or not. Take note that we query the V$DATAFILE_HEADER, because we want to know the SCN recorded in the header of the physical datafile, and not the V$DATAFILE, which derives the information from the controlfile.
select status, checkpoint_change#, to_char(checkpoint_time, 'DD-MON-YYYY HH24:MI:SS') as checkpoint_time, count(*) from v$datafile_header group by status, checkpoint_change#, checkpoint_time order by status, checkpoint_change#, checkpoint_time;
The results of the above query must return one and only one row for the online datafiles, which means that they are already synchronized in terms of their SCN. Otherwise, if the results return more than one row for the online datafiles, then the datafiles are still not synchronized yet. In this case, we need to apply archivelog(s) or redolog(s) to synchronize all of the online datafiles. Take note of the CHECKPOINT_TIME in the V$DATAFILE_HEADER, which indicates the date and time how far the datafiles have been recovered.
The results of the query above may return some offline datafiles. So, ensure that all of the required datafiles are online, because we may not be able to recover later the offline datafile once we open the database in resetlogs. Even though we can recover the database beyond resetlogs for the Oracle database starting from 10g and later versions due to the introduction of the format "%R" in the LOG_ARCHIVE_FORMAT, it is recommended that you online the required datafiles now than after the database is open in resetlogs to avoid any possible problems. However, in some cases, we intentionally offline the datafile(s), because we are doing a partial database restore, or perhaps we don't need the contents of the said datafile.
You may run the following query to determine the offline datafiles:
select file#, name from v$datafile where file# in (select file# from v$datafile_header where status='OFFLINE');
You may issue the following SQL statement to change the status of the required datafile(s) from "OFFLINE" to "ONLINE":
alter database datafile
If we are lucky that the required log sequence# is still available in the online redologs and the corresponding redolog member is still physically existing on disk, then we may apply them instead of the archivelog. To confirm, issue the following query, as shown below, that is to determine the redolog member(s) that you can apply to recover the database:
set echo on
feedback on
pagesize 100
numwidth 16
alter session set nls_date_format = 'DD-MON-YYYY HH24:MI:SS';
select LF.member, L.group#, L.thread#, L.sequence#, L.status, L.first_change#, L.first_time, DF.min_checkpoint_change# from v$log L, v$logfile LF, (select min(checkpoint_change#) min_checkpoint_change# from v$datafile_header where status='ONLINE') DF where LF.group# = L.group# and L.first_change# >= DF.min_checkpoint_change#;
If the above query returns no rows, because the V$DATABASE.CONTROLFILE_TYPE has a value of "BACKUP", then try to apply each of the redolog membes one at a time during the recovery. You may run the following query to determine the redolog members:
select * from v$logfile;
If you have tried to apply all of the online redolog members instead of an archivelog during the recovery, but you always received the ORA-00310 error, as shown in the example below, then the log sequence# required for recovery is no longer available in the online redolog.
ORA-00279: change 189189555 generated at 11/03/2007 09:27:46 needed for thread 1
ORA-00289: suggestion : +BACKUP ORA-00280: change 189189555 for thread 1 is in sequence #428 Specify log: {
ORA-00310: archived log contains sequence 503; sequence 428 required
ORA-00334: archived log: '+BACKUP/prmy/onlinelog/group_2.258.603422107'
After trying all of the possible solutions mentioned above, but you still cannot open the database, because the archivelog required for recovery is either missing, lost or corrupted, or the corresponding log sequence# is no longer available in the online redolog, since they are already overwritten during the redolog switches, then we cannot normally open the database, since the datafiles are in an inconsistent state. So, the following are the 3 options available to allow you to open the database:
Option#1: Force open the database by setting some hidden parameters in the init.ora. Note that you can only do this under the guidance of Oracle Support with a service request. But there is no 100% guarantee that this will open the database. However, once the database is opened, then we must immediately rebuild the database. Database rebuild means doing the following, namely: (1) perform a full-database export, (2) create a brand new and separate database, and finally (3) import the recent export dump. This option can be tedious and time consuming, but once we successfully open the new database, then we expect minimal or perhaps no data loss at all. Before you try this option, ensure that you have a good and valid backup of the current database.
Option#2: If you have a good and valid backup of the database, then restore the database from the said backup, and recover the database by applying up to the last available archivelog. In this option, we will only recover the database up to the last archivelog that is applied, and any data after that are lost. If no archivelogs are applied at all, then we can only recover the database from the backup that is restored. However, if we restored from an online or hot backup, then we may not be able to open the database, because we still need to apply the archivelogs generated during the said backup in order to synchronize the SCN of the datafiles before we can normally open the database.
Option#3: Manually extract the data using the Oracle's Data Unloader (DUL), which is performed by Oracle Field Support at the customer site on the next business day and for an extra charge. If the customer wants to pursue this approach, we need the complete name, phone# and email address of the person who has the authority to sign the work order in behalf of the customer.
Tuesday, June 2, 2009
New Rapid Install StartCD (12.0.4.9) for Release 12 Now Available
Oracle E-Business Suite Release 12.1.1 was released several weeks ago. We're pretty excited about this release and strongly encourage everyone evaluating R12 to consider 12.1.1. However, if you're still building test environments on the 12.0 codeline, you should be aware that a new Rapid Install startCD has been released for Apps 12.0.4. The latest startCD is available for immediate download: 7308107 - Rapid Install StartCD 12.0.4.9
Entering the following command shows the exact version for RapidWiz:
startCD/Disk1/rapidwiz/rapidwiz -version
What's New?
This startCD 12.0.4.9 update includes fixes for the following issues:
8472966: Incorrect oraparam templates used on HP Itanium
8438231: Missing templates of oraparam.ini for HP Platforms from 12.0.4.8 startCD
8409402: adrunias.sh $osversion only checks for AIX 6.1.0.0 and not 6.1.2.0
8255719: Need to copy adlicnse.sql to the shiphome
7037890: Licence Manager not showing UK as enabled after fresh 12.0.0 install
Entering the following command shows the exact version for RapidWiz:
startCD/Disk1/rapidwiz/rapidwiz -version
What's New?
This startCD 12.0.4.9 update includes fixes for the following issues:
8472966: Incorrect oraparam templates used on HP Itanium
8438231: Missing templates of oraparam.ini for HP Platforms from 12.0.4.8 startCD
8409402: adrunias.sh $osversion only checks for AIX 6.1.0.0 and not 6.1.2.0
8255719: Need to copy adlicnse.sql to the shiphome
7037890: Licence Manager not showing UK as enabled after fresh 12.0.0 install
Context Variables
This note gives list of Context Variables with details in short for
Oracle Applications Release 12.
1. System :
System Name (s_systemname)
Name of the Oracle Applications system which this context points to.
Database SID (s_dbSid)
Database SID for the system.
Database Name (s_dbGlnam)
Global Database name for the system. The value of this variable shall be the
same as the Database SID on non-RAC environments. On RAC-environments, this
name would be the same for all cluster nodes while the Database SID would be
different for each cluster node.
Database SID in Lower Case (s_dbSidLower)
Database SID in lower case for the system.
2. System Configurations (oa_system_config) :
TIER_DB (s_isDB)
(YES/NO) Is Database Server enabled in this context?
TIER_ADMIN (s_isAdmin)
(YES/NO) Is Admin Server enabled in this context?
TIER_WEB (s_isWeb)
TIER_WEBDEV (s_isWebDev)
(YES/NO) Is Web Server enabled in this context?
TIER_FORMS (s_isForms)
TIER_FORMSDEV (s_isFormsDev)
(YES/NO) Is Forms Server enabled in this context?
TIER_NODE (s_isConc)
TIER_NODEDEV (s_isConcDev)
(YES/NO) Is Concurrent Processing Server enabled in this context?
TechStack Config Option (s_techstack)
Techstack Config Option. This is automatically supplied to Autoconfig.
Since R12 supports only the 10.1.3 techstack, this variable can take only
the value 'as1013'.
Automatic NetService Files Generation Config Option (s_tnsmode)
The tnsnames.ora file is generated from the database when this option is
set to 'generateTNS'.
Applications version (s_apps_version)
This stores the applications version.
Apache mode (s_apache_mode)
This variable is used to specify whether Apache should be run in the 'Normal'
mode or in the 'Restricted' mode. Apache Restricted Mode is used when Oracle
Applications need to be brought down for maintenance purposes. In this mode,
during downtime normal users would be redirected to a standard 'downtime' URL
displaying the downtime details while the privileged users like System
Administrators would be able to monitor patches through OAM. This variable
should be in sync with 's_restricted_mode_comment'. For running Apache in the
NORMAL mode set this variable to NORMAL and 's_restricted_mode_comment' to #.
For RESTRICT mode set this variable to RESTRICT and
's_restricted_mode_comment' to null value.
3. Users (oa_users) :
Database 'SYS' User (s_sys_user)
The Database 'SYS' User
Applications 'APPS' User (s_apps_user)
The Applications 'APPS' User
Applications 'APPLSYS' User (s_applsys_user)
The Applications 'APPLSYS' User.
Applications 'GUEST' User (s_guest_user)
The Applications 'GUEST' User
Applications 'GUEST' Password (s_guest_pass)
The Applications 'GUEST' Password.
Applications 'GWYUID' User (s_gwyuid_user)
The Applications 'GWYUID' User.
Applications 'GWYUID' Password (s_gwyuid_pass)
The Applications 'GWYUID' Password.
4. Customer Info (customer_info) :
Customer Metalink ID (s_metalink_id)
Metalink ID of the Customer
Customer Country Code (s_country_code)
Customer Country Code. This variable is used while configuring the
Oracle Configuration Manager.
5. Language Settings (nls_settings) :
Default Territory (s_defterr)
Defines the NLS territory which determines cultural conventions such as
local time, date, numeric, and monetary conventions.
By default, this value is set to 'America'.
Base Language (s_base_lang)
Base Language for the Oracle Applications System. By default, this variable
is set to 'American English'. For a list of all supported languages, please
refer to the Oracle Applications Installation Manual.
Environment Languages (s_env_langs)
variable contains the list of all languages supported on the particular
environment. This includes the Base Language as well as all the Installed
Languages. For a list of all supported languages, please refer to the Oracle
Applications Install Manual.
6. Applications Configuration (oa_shared_config) :
Configuration Home (s_config_home)
This variable is used to specify the top level directory to which AutoConfig
will instantiate the instance specific configuration files in a shared file
system architecture.
Configuration Home for APPL_TOP files (s_appl_config_home)
This variable is used to specify the top level directory to which AutoConfig
will instantiate the instance specific configuration files related to
APPL_TOP in a shared file system architecture.
Configuration Home for ORACLE_HOME files (s_ora_config_home)
This variable is used to specify the toplevel directory to which AutoConfig
will instantiate the instance specific configuration files related to
ORACLE_HOME in a shared file system architecture.
Common Log File Location (s_logs_dir)
This variable is used to specify the top level directory to which the
application services will write instance specific log files in a shared file
system architecture.
Common PID File Location (s_pids_dir)
This variable is used to specify the top level directory to which the
application services will write instance specific Process ID files in a shared
file system architecture.
7. Database Server (oa_db_server) :
Database Server Host (s_dbhost)
Database Server Host
Fully Qualified Database Server Domain Name (s_dbdomain)
Fully Qualified Domain Name for the Database Server.
Database SID (s_db_serv_sid)
The SID for the database on the database server.
Database Character Set (s_dbcset)
Character set of the Applications database.
8. Admin Server (oa_admin_server) :
Admin Server Host (s_admhost)
Admin Server Host.
Fully Qualified Administration Server Domain Name (s_admdomain)
Fully Qualified Domain Name for the Administrator Server.
9. Concurrent Processing Server (oa_cp_server) :
Concurrent Processing Host (s_cphost)
Concurrent Processing Host
Fully Qualified Concurrent Processing Server Domain Name (s_cpdomain)
Fully Qualified Domain Name for the Concurrent Processing Server.
AF_LD_LIBRARY_PATH (s_conc_java_ldlib)
This variable is used to set the LD_LIBRARY_PATH for Java concurrent programs.
Concurrent Processing Password Type (s_cp_password_type)
The Concurrent Processing Password Type parameter indicates which username and
password will be supplied by the user when Concurrent Processing is started from
the command line. Allowed values are {AppsSchema, AppsUser}.
Concurrent Processing Reviver Process (s_cp_reviver)
Enable/Disable Concurrent Processing Reviver Process. Concurrent Processing
Reviver Process will recover the Concurrent Manager from a Network/Database
failure. Allowed values are {enabled, disabled}.
Reviver Process PID Directory Location (s_fndreviverpiddir)
This variable specifies the path where ICM reviver process pid file will be
created. Oracle recommends using a local disk as the PID file location because
the reviver process may run when the network is down.
10. Oracle Workflow Java Mailer (oa_workflow_server) :
Oracle Workflow Java Mailer IMAP Host (s_javamailer_imaphost)
Oracle Workflow Java Mailer IMAP Host.
Oracle Workflow Java Mailer IMAP domain (s_javamailer_imapdomainname)
Oracle Workflow Java Mailer domain.
Oracle Workflow Admin Role (s_wf_admin_role)
Role name of the Oracle Workflow Administrator.
Oracle Workflow Java Mailer IMAP ReplyTo Address (s_javamailer_reply_to)
Oracle Workflow Java Mailer IMAP ReplyTo Address.
Oracle Workflow Java Mailer IMAP User Name (s_javamailer_imap_user)
Oracle Workflow Java Mailer IMAP User Name.
SMTP Server Host (s_smtphost)
SMTP Server Host.
Fully Qualified Email Server Domain Name (s_smtpdomainname)
Fully Qualified Domain Name for the Email Server.
11. Forms Server (oa_forms_server) :
Forms Server Host (s_formshost)
Forms Server Host
Fully Qualified Forms Server Domain Name (s_formsdomain)
Fully Qualified Domain Name for the Forms Server.
Forms Server FND_TOP (s_formsfndtop)
Location of the FND_TOP on the Forms Server
Forms Runtime Executable Name (s_frmRuntime)
Name of the Forms runtime executable.
Forms CGI Runtime Executable Name (s_frmRunCGI)
Name of the Forms CGI startup executable.
Forms Connection Mode (s_frmConnectMode)
Forms Connection Mode. Allowed Values are {socket, servlet}. By default, the
value of this variable is set to 'servlet' since the servlet mode would be used
by default for connecting to the Forms server.
Format for the reports job output (s_desformat)
This variable sets the format for the reports job output, i.e. html/RTF/PDF.
Maximum number of network retries after network disconnect (s_frmNetworkRetries)
Number of times the client should attempt to connect to the forms server if the
network is interrupted
Is Chronos logging Enabled (s_isChronosEnabled)
Enable/Disable Chronos logging. Allowed values are {true, false}. Setting this
to 'true' enables Chronos Logging and setting it to ''false' disables it.
By default, this value is set to true.
Chronos URL (s_chronosURL)
If chronos logging is enabled, This value should be set to
http[s]://.:/oracle_smp_chronos
/oracle_smp_chronos_sdk.gif, where webCacheHost, webCacheDomain and webCachePort
are respectively the hostname, domain and port of the webcache instance.
Forms runtime file directory location (s_forms_trace_dir)
This variable is used to specify the location of dump files produced as a result
of a crash of any of the forms runtime executables. The dump files contains
diagnostic information concerning what was happening when the process crashed.
Forms Servlet JVM Options (s_forms_jvm_options)
Forms Servlet JVM Options
Forms OC4J Options (s_forms_oc4j_options)
This variable is used to specify the system properties that should be passed to
the Forms OC4J on instance startup.
Forms Heartbeat (s_forms_heartbeat)
Time in minutes to wait before the heartbeat message is sent by the Forms Client
to the server to keep the connection alive.
FORMS OC4J Instance Start Parameters (s_forms_jvm_start_options)
The value of this variable contains the parameters that are passed to the JVM
when starting the FORMS OC4J instance.
FORMS OC4J Instance Stop Parameters (s_forms_jvm_stop_options)
The value of this variable contains the parameters that are passed to the JVM
when stopping the FORMS OC4J instance.
Maximum block time (in milliseconds) for listener servlet (s_forms_maxblocktime)
Maximum block time (in milliseconds) for listener servlet
Forms Servlet URL (s_forms_servlet_serverurl)
For the Servlet mode, this variable should be set to the Forms Servlet URL.
For the Forms Socket Mode, this variable should be set to null.
Number of frmweb process (s_frmsrv_nprocs)
Specifies the number of frmweb process that are invoked at Forms Server startup
Forms Servlet Comment (s_forms_servlet_comment)
Removing the # enables starting of jserv processes for the forms group
Use session cookie (s_form_session_cookie)
Depending on the value of this variable, the Forms servlet uses session cookie
to maintain the state of the session. Allowed values are {true, false}.
If set to 'true', the session cookie is used to maintain the state of the
session, else not.
Number of JVMs for FORMS OC4J Instance (s_forms_nprocs)
Specifies the number of JVM processes serving the forms OC4J Instance.
Forms OC4J log rotation time (s_forms_oc4j_log_rotation_time)
This parameter is used to specify the time interval in seconds for rotating the
Forms OC4J log files.
Forms OC4J log rotation size (s_forms_oc4j_log_rotation_size)
This variable specifies the size of the log file in Kilo Bytes when Forms OC4J
will rotate its log file. The default value for this variable is set to 10000KB.
Enable FORMS OC4J Access log (s_forms_oc4j_enable_access_log)
This variable is used to enable/disable OC4J access log for FORMS application.
Setting the value of this variable to 'TRUE' will enable the access log.
12. OACORE OC4J (oacore_server) :
OACORE OC4J Instance Start Parameters (s_oacore_jvm_start_options)
The value of this variable contains the parameters that are passed to the JVM
when starting the OACORE OC4J instance.
Oacore OC4J Options (s_oacore_oc4j_options)
This variable is used to specify the system properties that should be passed to
the oacore OC4J on instance startup.
OACORE OC4J Instance Stop Parameters (s_oacore_jvm_stop_options)
The value of this variable contains the parameters that are passed to the JVM
when stopping the OACORE OC4J instance.
OACORE OC4J Instance Prepend LD_LIBRARY_PATH (s_oacore_prepend_ld_lib_path)
This variable is used to specify path to the libraries that need to be prepended
to the existing LD_LIBRARY_PATH for the OACORE OC4J Instance.
For UNIX platforms, use ':' at the end of the directory list and to separate a
list of directories. For Windows platforms, use ';' at the end of the directory
list and to separate a list of directories
Prepend OACORE OC4J Classpath (s_oacore_prepend_classpath)
This variable is used to specify one or more directories that contain custom
libraries to be included in the OC4J classpath before the inclusion of JAVA_TOP.
Append OACORE OC4J Classpath (s_oacore_append_classpath)
This variable is used to specify one or more directories that contain custom
libraries to be included in the OC4J classpath after the inclusion of JAVA_TOP.
OACORE OC4J Instance LD_LIBRARY_PATH (s_oacore_ld_lib_path)
This variable is used to specify LD_LIBRARY_PATH for the OACORE OC4J Instance.
Load CZ Servlet (s_load_cz_servlet)
This variable is used to determine whether Oracle Configurator servlet classes
defined in orion-web.xml need to be loaded when OC4J server starts. The default
value is set to '1' which means that the servlet is loaded. If you wish to
disable this feature set the value '-1' .
Start Email Center Outbox Processor (s_load_emailcenter_servlet)
This variable is used to determine whether the Email Center Outbox Processor is
started when the OC4J server starts. The Outbox Processor is controlled via the
InitializationServlet class defined in orion-web.xml. The default value is '-1'
which means that the servlet is not loaded. If you wish to enable this feature
set the value to '1'.
Number of JVMs for OACORE OC4J Instance (s_oacore_nprocs)
Specifies the number of JVM processes serving the oacore OC4J Instance.
Oacore OC4J log rotation time (s_oacore_oc4j_log_rotation_time)
This variable is used to set the time interval in seconds for rotating the
Oacore OC4J log files.
Oacore OC4J log rotation size (s_oacore_oc4j_log_rotation_size)
This variable specifies the size of the log file in Kilo Bytes when oacore OC4J
will rotate its log file. The default value for this variable is set to 10000KB.
Enable OACORE OC4J Access log (s_oacore_oc4j_enable_access_log)
This variable is used to enable/disable OC4J access log for OACORE application.
Setting the value of this variable to 'TRUE' will enable the access log.
13. Discoverer (oa_disco_server)
External Integrated Discoverer URL (s_disco_url)
Set the value of this variable to the appropriate external integrated 10G
Discoverer URL. An acceptable value for this parameter is a URL that includes
protocol, host, domain and port.
Discoverer URL Prefix (s_disco_eul_prefix)
14. Metrics Server (oa_met_server) :
Metrics Server Host (s_methost)
Metrics Server Host
Fully Qualified Metrics Server Domain Name (s_metdomain)
Fully Qualified Domain Name for the Metrics Server.
Metrics Server Load Balancing Host (s_leastloadedhost)
Metrics Server Load Balancing Host
Metrics Server Error URL (s_meterrorurl)
Metrics Server Error URL
15. Oracle MWA Server (oa_mwa_server) :
MSCA Log Level (s_mwaLogLevel)
Different log levels can be set for obtaining more debug information.
MSCA Log Rotate (s_mwaLogRotate)
Enable log rotation of files based on size (Yes/No).
MSCA Log File Size (s_mwaLogFileSize)
MSCA Log File Size. If log rotation is enabled, then rotation occurs when log
file exceeds this size.
MSCA Drop Connection Timeout (s_mwaDropConnectionTimeout)
MSCA Drop Connection Timeout. MSCA Server allows a client that was disconnected
to reconnect within the time mentioned below in minutes.
MSCA Stale Session Timeout (s_mwaStaleSessionTimeout)
MSCA Stale Session Timeout. MSCA Server disconnects a client after the client
is idle for mwa.StaleSessionTimeout minutes.
MSCA Dispatcher Thread Count (s_mwaDispatcherThreadCount)
Specify number of worker threads to start from the dispatcher process
MSCA Dispatcher Clients Per Worker (s_mwaDispatcherClientsPerWorker)
Specify number of clients that each dispatcher worker thread can handle
MSCA Compatibility Setting for JVM (s_mwaJVMb)
MSCA Compatability Setting for JVM
MSCA LOV activation by ENTER (s_mwaActivateLOVByEnter)
Used to specify whether user would like to retain old LOV behavior, i.e. LOV
will be activated by ENTER or not
Show Change Responsibility and Change Organization on submenus
(s_mwaSubmenuChangeOrgResp)
Specifies whether Change Responsibility and Change Organization menu items
should appear on submenus; if TRUE, then these menu items will appear on the
main menu and submenus; if FALSE, then these menu items will only appear on
the main menu; the default value is FALSE.
16. Oracle Web Server (oa_web_server) :
Web Server Host (s_webhost)
Web Server Host.
External URL for Third Party Access to E-Business Suite (s_external_url)
This is the URL that third party tools use to connect to the E-Business Suite.
Oracle HTTP Server Directory Index Page (s_directory_index)
This directive sets the list of resources to look for, when the client requests
an index of the directory by specifying a / at the end of the directory name.
You can specify multiple values separated by space for this variable and the
server will return the first one it finds.
Web Host entry point (s_webentryhost)
The Host machine that accepts the http requests.
Web domain entry point (s_webentrydomain)
The domain of the host machine that accepts the http requests.
Location for Lock files and pid files (s_lock_pid_dir)
Location for Lock and pid files to be used for NetApp setup.
Fully Qualified Web Server Domain Name (s_webdomain)
This variable is used to set the fully qualified domain name of the web server.
Server IP Address (s_server_ip_address)
This is the IP address of the Web Host entry point (s_webentry_host) when
configuring according to Oracle MetaLink Note 380490.1 or 380489.1. This value
will be used by the dbc generation utility when registering this Web Host entry
point with Oracle E-Business Suite.
Oracle HTTP Server Process ID File (s_web_pid_file)
Complete path to the Oracle HTTP Server Process ID File.
URL Protocol (s_url_protocol)
URL Protocol to be used. Allowed Values are {http, https}.
Web SSL Directory (s_web_ssl_directory)
Web SSL Directory.
Local URL Protocol (s_local_url_protocol)
Local URL Protocol. Allowed values {http, https}.
SSLCertificateChainFile (s_web_ssl_certchainfile)
File of PEM-encoded Server CA Certificates.
Name of the wallet file used by webservices (s_websrv_wallet_file)
This is the name of the wallet file used by webservices.
Enable/disable SSL terminator configuration (s_enable_sslterminator)
This variable is used to enable/disable the inclusion of the configuration file
used for SSL terminated environments. By default the value of this variable is
set to '#' which indicates that the configuration file is not included in the
server configuration. To enable, the pound sign '#' must be removed
Sun Plugin version (s_sun_plugin_ver)
Sun Plugin Version.
Sun Desktop Plugin Type (s_sun_plugin_type)
Type of Sun desktop plug-in used for running Forms on desktop clients.
By default, the plugin type is 'jdk' since only 'jdk' is supported in R12.
Sun JDK CLSID (s_sun_clsid)
Class ID for referencing the JDK.
JInitiator version (dots) (s_jinit_ver_dot)
JInitiator version (dot separated syntax)
JInitiator version (commas) (s_jinit_ver_comma)
JInitiator version (comma separated syntax)
JInitiator CLSID (s_jinit_clsid)
CLSID for referencing the JInitiator.
Fully Qualified Proxy Server Host Name (s_proxyhost)
Fully Qualified Proxy Server Host Name.
Proxy Server Port (s_proxyport)
Proxy Server Port.
Fully Qualified Proxy Bypass Domains (s_proxybypassdomain)
Fully Qualified Domains which can bypass the Proxy Server.
Nodes in cluster configuration (s_oc4j_cluster_nodes)
It is a list of Servers that are participating in the cluster configuration.
For example, if two node exists in the configuration, then value will be
appstier1.company.com:6000,appstier2.company.com:6000
on both the application tier servers.
URL for Applications Portal (s_apps_portal_url)
URL for Applications Portal.
List of nodes that have access to Portlet Provider URLs (s_trusted_portals
Enter space separated values consisting of node names or fully qualified node
names or IP addresses of client machines which will be allowed to access
Portlet Provider URLs
Sysadmin Mail ID (s_sysadmin_mail)
Sysadmin Mail ID.
Cookie Domain (s_cookie_domain)
Specific Domain to which the Cookies will be accesible.
Session toplevel domain comment (s_topleveldomain_comment)
Users of Oracle Portal should uncomment this variable.
IANA Characterset (s_iana_cset)
IANA Characterset used by Oracle HTTP Web Server.
Login Page URL (s_login_page)
URL to the Login Page.
Oracle HTTP Server Listen Parameter. (s_http_listen_parameter)
This variable is used to set the Oracle HTTP Server Listen Directive
in httpd.conf. The default value for this variable is set to the value of the
context variable %s_webport% which means that all network interfaces configured
on the web server machine will listen on this port. If there is a requirement
that only one network interface should listen on the specified port then the
value of this variable should be changed to IP:port combination or the value
of s_webhost.s_webdomain:port
Oracle HTTPS Server Listen Parameter. (s_https_listen_parameter)
This variable is used to set the Oracle HTTPS Server Listen Directive
in ssl.conf. The default value for this variable is set to the value of the
context variable %s_webssl_port% which means that all network interfaces
configured on the web server machine will listen on this port. If there is a
requirement that only one network interface should listen on the specified port
then the value of this variable should be changed to IP:port combination or the
value of webhost.webdomain:port
HTTP Server core file location (s_core_dest)
Location where the HTTP Server can dump the core file.
Maximum Number of clients that can connect (s_maxclients)
This directive sets the limit on the number of Simultaneous HTTP requests that
can be supported. The maximum allowed value for MaxClients is 8192.
Enable Keep-Alive connections (s_keepalive)
The persistent connection feature of HTTP/1.1 to provide long-lived HTTP
sessions which allow multiple requests to be sent over the same TCP connection.
OHS timeout (s_keepalive_timeout)
This directive sets the number of seconds OHS will wait for a subsequent request
before closing the connection.
Number of requests that an individual http process will handle
(s_maxrequests_perchild)
This directive sets the number of requests that an individual http child server
process would handle. The maximum allowed value for this variable depends on the
capacity of the system and also on the number of simultaneous users. By default,
the value of this variable is set to '0'.
Number of http requests allowed per connection (s_maxkeepalive_requests)
This directive sets the number of http requests allowed per connection when
KeepAlive directive is set to ON. The maximum allowed value for this variable
depends on the capacity of the system and also on the number of simultaneous
users. By default, this is set to '0'.
Number of minimum idle http server processes (s_minspare_servers)
This directive sets the desired minimum number of idle http server processes.
Number of maximum idle http server processes (s_maxspare_servers)
This directive sets the desired maximum number of idle http server processes.
Help Web Agent (s_help_web_agent)
If HELP_WEB_AGENT profile is set, the value is used for the construction of all
Help related URLs. This allows multiple application installations to share a
common help system. Optional override.
Custom SQL location (s_customsql_path)
Custom SQL reports feature within OAM lets users generate HTML and text reports
based on the SQL scripts they register.
Jserv Session Timeout (s_sesstimeout)
Time in milliseconds to wait before an unused session is invalidated.
JInitiator Progress Dialog (s_java_showprogress)
Feature to show the progress of downloading of JInitiator JAR files.
Ohs log rotation time (s_ohs_log_rotation_time)
This variable specifies the Hour of day when opmn process will rotate its
log file. By default, this is set to '0' which means that the log will be
rotated exactly at midnight.
Opmn log rotation time (s_opmn_log_rotation_time)
This variable specifies the Hour of day when opmn process will rotate its
log file. By default, this is set to '0' which means that the log will be
rotated exactly at midnight.
Opmn log rotation size (s_opmn_log_rotation_size)
This variable specifies the size of the log file in Kilo Bytes when opmn will
rotate its log file. The default value for this variable is set to 1500000 KB
Load OXTA Servlet (s_load_oxta_servlet)
This variable is used to enable/disable loading of the Oracle XML Transport
Agent servlet when oc4j starts up. To enable loading of this servlet, set this
variable to '1'. To disable loading of this servlet, set this variable to '-1'.
By default, the value is set to '1'
Connection pool size for OXTA servlets (s_oxtainpool_size)
Size of the connection pool the OXTA servlets will get connection from when
serving incoming requests. Setting this to a very high value would result in
performance degradation while setting to very low values may result in the OXTA
requests to wait longer for getting a connection. By default, its value is '1'.
JDBC driver file name (s_txk_jdbc_zip)
JDBC driver name.
Long Running JVM (s_long_running_jvm)
Indicates that JVM is expected to have a long lifespan if this value is true.
XML Parser Path (s_xmlparser)
Complete path to the Oracle XML Parser java archive file.
Maximum jdbc pool size (s_fnd_max_jdbc_connections)
fnd_max_jdbc_connections is the maximum jdbc pool size. This is the sum of the
number of available connections and the number of locked connections.
FND JDBC Statement Cache Size (s_fnd_jdbc_stmt_cache_size)
This parameter controls how many parsed SQL statements are retained in the JDBC
cache. Re-execution of statements stored in the JDBC statement cache will not
require a reparse operation and will therefore be highly optimized. It should
not be increased to an extreme value because maintaining this cache takes up
memory in the JVM. We would recommend a value between 200 and 400.
DBC File Name (s_dbc_file_name)
This variable sets the value for the DBC file name. Make sure that you enter
the file name without the extension.
Apps JDBC URL (s_apps_jdbc_connect_descriptor)
Configure this variable only when you have an Oracle RAC Database instance.
Please see Oracle MetaLink Note 388577.1 for more information on RAC and
discussion of the value for this variable.
Apps JDBC Connect Alias (s_apps_jdbc_connect_alias)
Configure this variable only when you have an Oracle RAC Database instance.
This variable can have a value of either a load balanced connect descriptor or
an instance specific connect descriptor. Please see Oracle MetaLink
Note 388577.1 for more information.
Application Server Security Authentication (s_appserverid_authentication)
Application Server Security Authentication can take one of the following values
{ON, OFF, SECURE}. OFF - Server security is not checked. Any application server
machine can access the database. ON - Some level of trust is required to access
the database. Either the Application Server is registered with the database or
the module and version ID are known to be trusted. SECURE - Full trust is
required for access to the database. Only registered Application Server machines
and trusted code modules may connect.
Web entry protocol (s_webentryurlprotocol)
This parameter is used to set the web entry url protocol. Acceptable values for
this parameter are http or https.
Apache OptionsLink Directive (s_options_symlinks)
!CAUTION! Oracle recommends not to change the default value of this parameter.
If you change the default value then you will expose yourself to security
vulnerability and performance degradation of your site.
Session Check Frequency (s_sessionCheck_frequency)
Time interval in milli seconds before checking for invalid sessions in a
Servlet zone.
Oracle HTTP Server Timeout (s_ohstimeout)
This parameter stands for the amount of time (in seconds) the Oracle HTTP Server
will wait for certain events(GET,POST,PUT etc) before failing a request
Apache Log Level (s_apache_loglevel)
Possible values include: debug, info, notice, warn, error, crit, alert, emerg.
Oracle HTTP Server Administrator e-mail address (s_ohs_serveradmin)
This is the email address that the server includes in any error messages sent
to the client.
Property dontChunkRequests for HTTPClient.jar (s_httpclient_dontChunkRequests
Indicates the dontChunkRequests property value for HTTPClient.jar.
Possible values are true and false.
Number of outbound threads (s_outbound_threads)
Number of OXTA threads to be used for simultaneous outbound message sending.
Setting this to a very high value would result in performance degradation while
setting to very low values may result in the OXTA requests to wait longer for
getting a connection. By default, the value of this variable is set to '1'.
OXTAOutUseProxy (s_oxta_proxy)
If this property is set to true, the proxy specified by OXTAOutProxyHost and
OXTAOutProxyPort is used to send messages to the destination
OXTAOutProxyHost (s_oxta_proxyhost)
Fully Qualified proxy server hostname for the Oracle XML Transport Agent (OXTA).
OXTAOutProxyPort (s_oxta_proxyport)
Proxy port for the Oracle XML Transport Agent (OXTA).
TrustStoreType (s_ssl_truststoretype)
The keystore file type of the key material used for the trust manager.
KeyStoreType (s_ssl_keystoretype)
The keystore file type of the key material used for the key manager.
TrustStore (s_ssl_truststore)
Location of the key material for the trust manager.
KeyStore (s_ssl_keystore)
Location of the key material for the key manager.
TrustManagerAlgorithm (s_ssl_trustmanageralgorithm)
Default trust manager factory algorithm name as specified in the Java security
properties. If no such property exists, this variable stores an
implementation-specific default.
KeyManagerAlgorithm (s_ssl_keymanageralgorithm)
Default key manager factory algorithm name specified in the Java security
properties. If no such property exists, this variable stores an
implementation-specific default.
Optimizer Home (s_optit_home)
This variable is used to specify the location of the optimizer suite home.
Parameter to enable/disable URL Firewall (s_enable_urlfirewall)
This variable is used to enable or disable the URL Firewall required for DMZ
configurations. By default the value of this variable is set to '#' which
indicates that the URL firewall is disabled. To enable the URL firewall,
the pound sign '#' must be removed
List of nodes that have access to Oracle HTTP Server administration pages.
(s_admin_ui_access_nodes)
This variable is used to set the list of machines that are allowed to access
the administration pages. Enter space separated values consisting of node names
or fully qualified node names or IP addresses of client machines which will be
allowed to access the administration pages.
Minimum buffer size maintained by the pool (s_fnd_jdbc_buffermin)
This is the minimum buffer size that should be maintained by the applications
database connection pool. Acceptable values are positive integers less
than integer:MAX
Maximum buffer size maintained by the pool (s_fnd_jdbc_buffermax)
This is the maximum buffer size that should be maintained by the applications
database connection pool.Acceptable values are positive integers less than
integer:MAX
Time interval to check the buffer size (s_fnd_jdbc_buffer_decay_interval)
This is the time interval in seconds the maintenance thread checks the buffer
size .Acceptable values are positive integers less than integer:MAX
Maximum number of available objects that should be removed in a thread cycle
(s_fnd_jdbc_buffer_decay_size)
This is the maximum number of connections that will be removed during any one
thread cycle .Acceptable values are positive integers less than integer:MAX
Enable/Disable pl/sql query (s_fnd_jdbc_usable_check)
This variable indicates whether a simple pl/sql query should be performed to
check whether the connection is usable before giving a connection to the client.
Acceptable values are true or false
Enable/Disable AOL security context and NLS state check
(s_fnd_jdbc_context_check)
This variable indicates whether the AOL security context and NLS state should
be obtained from the database server session instead of the java client when
the connection is returned to the pool.Acceptable values are true or false
Free pl/sql state (s_fnd_jdbc_plsql_reset)
This variable indicates whether the pl/sql state should be freed before the
applications database connection pool gives the connection to the client.
JDBC process escape (s_jdbc_proc_esc)
This variable is used to enable or disable JDBC escape processing mechanism.
Changing this parameter value has performance implications.
Custom DBC Parameters (s_custom_dbc_params)
This variable holds a space separated custom dbc parameter list of name value
pairs. For e.g. 'param1=value1 param2=value2 param3=value3'. These values will
be seeded in to the dbc file during AutoConfig execution.
17. OAFM OC4J (oafm_server) :
OAFM OC4J Instance Start Parameters (s_oafm_jvm_start_options)
The value of this variable contains the parameters that are passed to the JVM
when starting the OAFM OC4J instance.
OAFM OC4J Options (s_oafm_oc4j_options)
This variable is used to specify the system properties that should be passed to
the OAFM OC4J on instance startup.
OAFM OC4J Instance Stop Parameters (s_oafm_jvm_stop_options)
The value of this variable contains the parameters that are passed to the JVM
when stopping the OAFM OC4J instance.
Number of JVMs for OAFM OC4J Instance (s_oafm_nprocs)
This specifies the number of JVM processes serving the OAFM OC4J Instance.
Enable OAFM OC4J Access log (s_oafm_oc4j_enable_access_log)
This context variable is used to enable/disable OC4J access log for OAFM and
MapViewer application. Setting the value to 'TRUE' will enable the access log.
18. Oracle Fulfillment Server (jtff_server) :
Oracle Fulfillment Server Instance Id (s_ServerInstanceID)
Identifies the One-to-One Fulfillment Server instance that gets started
when jtffmctl.sh is run.
Oracle Fulfillment Maximum Number of Threads (s_MaxBatchThreads)
Specifies the maximum number of threads on the One-to-One Fulfillment Server
that gets started when jtffmctl.sh is run.
Oracle Fulfillment Turnoff Low Priority Monitors (s_TurnOffLowPriorityMonitor)
Specifies that the monitors of low priority be turned off on the One-to-One
Fulfillment Server instance that gets started when jtffmctl.sh is run.
Oracle Fulfillment Server Debug String (s_jto_debug_string)
A comma-separated list indicating the items for which to log debug information
for the Oracle Fulfillment Server.
Oracle Fulfillment Server Log Level (s_jto_log_level)
Logging level for the Oracle Fulfillment Server. For each number specified
from 1-n, the server will write an extra layer of chained exception traces to
the error log. The exceptions are chained together so that the source of the
errors as they occur can be traced.
Oracle Fulfillment Server RightFax Fax Enabler (s_jto_fax_enabler)
Indicates the Java class that the Fulfillment Server is to use for sending
faxes. This class must implement the oracle.apps.jtf.fm.engine.disp.FaxEnabler
interface to be used as a fax enabler.
Oracle Fulfillment Server RightFax Print Enabler (s_jto_print_enabler)
This flag indicates the Java class that the Fulfillment Server is to use for
sending print jobs to the printer. This class must implement the
oracle.apps.jtf.fm.engine.disp.PrintEnabler interface to be used as a
print enabler.
Oracle Fulfillment Server RightFax zip Location (s_jto_rfjava_loc)
RFJavaInt.zip is the zip file containing the Java integration classes provided
by RightFax upon installation. That file should be included the classpath of the
Fulfillment Server in order to successfully dispatch fax or print requests
through RightFax.
JSP cache directory (s_jsp_cache_dir)
This variable is used to set the .jsp cache directory. Please refer to JSP
Developer's guide for more information on the usage of this variable.
Parameter to enable JSR-45 debugging support (s_jsp_jsr45_dbg)
This variable is used to enable JSR-45 debugging support. Valid settings are
file: to generate an SMAP file, class: to embed debugging info in the generated
class, none: to generate no debugging information. Please refer to JSP
Developer's guide for more information on the usage of these variables.
Parameter to enable printing of stack trace (s_jsp_dbg_mode)
This variable is used to enable printing the stack trace when certain runtime
execeptions occur. Valid settings are true: to generate a stack trace,
false: to turn off printing of the stack trace. Please refer to JSP Developer's
guide for more information on the usage of these variables.
Whether JSP-generated classes are automatically reloaded (s_jsp_main_mode)
This variable is used to specify whether JSP-generated classes are automatically
reloaded or JSP pages are automatically retranslated when JSP changes are made.
Valid settings are recompile: container will check the timestamp of the jsp page
since the last load, reload: container will check the timestamp of classes
generated by the jsp translator, justrun: container will not perform any
timestamp checking. Please refer to JSP Developer's guide for more information
on the usage of these variables.
Oracle Fulfillment Server Enabler Classpath (s_jto_enabler_classpath)
A classpath that specifies the location of custom enabler code (if present)
Oracle Fulfillment Server Log Warning Flag (s_jto_show_warnings)
By default, warnings do not show up in the error log. If this flag is not set,
then the first time a warning appears a single message shows up in the events
log signifying that a warning had been issued. The default is 'false'.
Oracle Fulfillment Server Id (s_jto_server_id)
Identifies the One-to-One Fulfillment Server that gets started when
jtffmctl.sh is run.
Classpath to be used by the Oracle Fulfillment Server (s_jto_classpath)
Classpath to be used by the Oracle Fulfillment Server
Oracle Applications Release 12.
1. System :
System Name (s_systemname)
Name of the Oracle Applications system which this context points to.
Database SID (s_dbSid)
Database SID for the system.
Database Name (s_dbGlnam)
Global Database name for the system. The value of this variable shall be the
same as the Database SID on non-RAC environments. On RAC-environments, this
name would be the same for all cluster nodes while the Database SID would be
different for each cluster node.
Database SID in Lower Case (s_dbSidLower)
Database SID in lower case for the system.
2. System Configurations (oa_system_config) :
TIER_DB (s_isDB)
(YES/NO) Is Database Server enabled in this context?
TIER_ADMIN (s_isAdmin)
(YES/NO) Is Admin Server enabled in this context?
TIER_WEB (s_isWeb)
TIER_WEBDEV (s_isWebDev)
(YES/NO) Is Web Server enabled in this context?
TIER_FORMS (s_isForms)
TIER_FORMSDEV (s_isFormsDev)
(YES/NO) Is Forms Server enabled in this context?
TIER_NODE (s_isConc)
TIER_NODEDEV (s_isConcDev)
(YES/NO) Is Concurrent Processing Server enabled in this context?
TechStack Config Option (s_techstack)
Techstack Config Option. This is automatically supplied to Autoconfig.
Since R12 supports only the 10.1.3 techstack, this variable can take only
the value 'as1013'.
Automatic NetService Files Generation Config Option (s_tnsmode)
The tnsnames.ora file is generated from the database when this option is
set to 'generateTNS'.
Applications version (s_apps_version)
This stores the applications version.
Apache mode (s_apache_mode)
This variable is used to specify whether Apache should be run in the 'Normal'
mode or in the 'Restricted' mode. Apache Restricted Mode is used when Oracle
Applications need to be brought down for maintenance purposes. In this mode,
during downtime normal users would be redirected to a standard 'downtime' URL
displaying the downtime details while the privileged users like System
Administrators would be able to monitor patches through OAM. This variable
should be in sync with 's_restricted_mode_comment'. For running Apache in the
NORMAL mode set this variable to NORMAL and 's_restricted_mode_comment' to #.
For RESTRICT mode set this variable to RESTRICT and
's_restricted_mode_comment' to null value.
3. Users (oa_users) :
Database 'SYS' User (s_sys_user)
The Database 'SYS' User
Applications 'APPS' User (s_apps_user)
The Applications 'APPS' User
Applications 'APPLSYS' User (s_applsys_user)
The Applications 'APPLSYS' User.
Applications 'GUEST' User (s_guest_user)
The Applications 'GUEST' User
Applications 'GUEST' Password (s_guest_pass)
The Applications 'GUEST' Password.
Applications 'GWYUID' User (s_gwyuid_user)
The Applications 'GWYUID' User.
Applications 'GWYUID' Password (s_gwyuid_pass)
The Applications 'GWYUID' Password.
4. Customer Info (customer_info) :
Customer Metalink ID (s_metalink_id)
Metalink ID of the Customer
Customer Country Code (s_country_code)
Customer Country Code. This variable is used while configuring the
Oracle Configuration Manager.
5. Language Settings (nls_settings) :
Default Territory (s_defterr)
Defines the NLS territory which determines cultural conventions such as
local time, date, numeric, and monetary conventions.
By default, this value is set to 'America'.
Base Language (s_base_lang)
Base Language for the Oracle Applications System. By default, this variable
is set to 'American English'. For a list of all supported languages, please
refer to the Oracle Applications Installation Manual.
Environment Languages (s_env_langs)
variable contains the list of all languages supported on the particular
environment. This includes the Base Language as well as all the Installed
Languages. For a list of all supported languages, please refer to the Oracle
Applications Install Manual.
6. Applications Configuration (oa_shared_config) :
Configuration Home (s_config_home)
This variable is used to specify the top level directory to which AutoConfig
will instantiate the instance specific configuration files in a shared file
system architecture.
Configuration Home for APPL_TOP files (s_appl_config_home)
This variable is used to specify the top level directory to which AutoConfig
will instantiate the instance specific configuration files related to
APPL_TOP in a shared file system architecture.
Configuration Home for ORACLE_HOME files (s_ora_config_home)
This variable is used to specify the toplevel directory to which AutoConfig
will instantiate the instance specific configuration files related to
ORACLE_HOME in a shared file system architecture.
Common Log File Location (s_logs_dir)
This variable is used to specify the top level directory to which the
application services will write instance specific log files in a shared file
system architecture.
Common PID File Location (s_pids_dir)
This variable is used to specify the top level directory to which the
application services will write instance specific Process ID files in a shared
file system architecture.
7. Database Server (oa_db_server) :
Database Server Host (s_dbhost)
Database Server Host
Fully Qualified Database Server Domain Name (s_dbdomain)
Fully Qualified Domain Name for the Database Server.
Database SID (s_db_serv_sid)
The SID for the database on the database server.
Database Character Set (s_dbcset)
Character set of the Applications database.
8. Admin Server (oa_admin_server) :
Admin Server Host (s_admhost)
Admin Server Host.
Fully Qualified Administration Server Domain Name (s_admdomain)
Fully Qualified Domain Name for the Administrator Server.
9. Concurrent Processing Server (oa_cp_server) :
Concurrent Processing Host (s_cphost)
Concurrent Processing Host
Fully Qualified Concurrent Processing Server Domain Name (s_cpdomain)
Fully Qualified Domain Name for the Concurrent Processing Server.
AF_LD_LIBRARY_PATH (s_conc_java_ldlib)
This variable is used to set the LD_LIBRARY_PATH for Java concurrent programs.
Concurrent Processing Password Type (s_cp_password_type)
The Concurrent Processing Password Type parameter indicates which username and
password will be supplied by the user when Concurrent Processing is started from
the command line. Allowed values are {AppsSchema, AppsUser}.
Concurrent Processing Reviver Process (s_cp_reviver)
Enable/Disable Concurrent Processing Reviver Process. Concurrent Processing
Reviver Process will recover the Concurrent Manager from a Network/Database
failure. Allowed values are {enabled, disabled}.
Reviver Process PID Directory Location (s_fndreviverpiddir)
This variable specifies the path where ICM reviver process pid file will be
created. Oracle recommends using a local disk as the PID file location because
the reviver process may run when the network is down.
10. Oracle Workflow Java Mailer (oa_workflow_server) :
Oracle Workflow Java Mailer IMAP Host (s_javamailer_imaphost)
Oracle Workflow Java Mailer IMAP Host.
Oracle Workflow Java Mailer IMAP domain (s_javamailer_imapdomainname)
Oracle Workflow Java Mailer domain.
Oracle Workflow Admin Role (s_wf_admin_role)
Role name of the Oracle Workflow Administrator.
Oracle Workflow Java Mailer IMAP ReplyTo Address (s_javamailer_reply_to)
Oracle Workflow Java Mailer IMAP ReplyTo Address.
Oracle Workflow Java Mailer IMAP User Name (s_javamailer_imap_user)
Oracle Workflow Java Mailer IMAP User Name.
SMTP Server Host (s_smtphost)
SMTP Server Host.
Fully Qualified Email Server Domain Name (s_smtpdomainname)
Fully Qualified Domain Name for the Email Server.
11. Forms Server (oa_forms_server) :
Forms Server Host (s_formshost)
Forms Server Host
Fully Qualified Forms Server Domain Name (s_formsdomain)
Fully Qualified Domain Name for the Forms Server.
Forms Server FND_TOP (s_formsfndtop)
Location of the FND_TOP on the Forms Server
Forms Runtime Executable Name (s_frmRuntime)
Name of the Forms runtime executable.
Forms CGI Runtime Executable Name (s_frmRunCGI)
Name of the Forms CGI startup executable.
Forms Connection Mode (s_frmConnectMode)
Forms Connection Mode. Allowed Values are {socket, servlet}. By default, the
value of this variable is set to 'servlet' since the servlet mode would be used
by default for connecting to the Forms server.
Format for the reports job output (s_desformat)
This variable sets the format for the reports job output, i.e. html/RTF/PDF.
Maximum number of network retries after network disconnect (s_frmNetworkRetries)
Number of times the client should attempt to connect to the forms server if the
network is interrupted
Is Chronos logging Enabled (s_isChronosEnabled)
Enable/Disable Chronos logging. Allowed values are {true, false}. Setting this
to 'true' enables Chronos Logging and setting it to ''false' disables it.
By default, this value is set to true.
Chronos URL (s_chronosURL)
If chronos logging is enabled, This value should be set to
http[s]://
/oracle_smp_chronos_sdk.gif, where webCacheHost, webCacheDomain and webCachePort
are respectively the hostname, domain and port of the webcache instance.
Forms runtime file directory location (s_forms_trace_dir)
This variable is used to specify the location of dump files produced as a result
of a crash of any of the forms runtime executables. The dump files contains
diagnostic information concerning what was happening when the process crashed.
Forms Servlet JVM Options (s_forms_jvm_options)
Forms Servlet JVM Options
Forms OC4J Options (s_forms_oc4j_options)
This variable is used to specify the system properties that should be passed to
the Forms OC4J on instance startup.
Forms Heartbeat (s_forms_heartbeat)
Time in minutes to wait before the heartbeat message is sent by the Forms Client
to the server to keep the connection alive.
FORMS OC4J Instance Start Parameters (s_forms_jvm_start_options)
The value of this variable contains the parameters that are passed to the JVM
when starting the FORMS OC4J instance.
FORMS OC4J Instance Stop Parameters (s_forms_jvm_stop_options)
The value of this variable contains the parameters that are passed to the JVM
when stopping the FORMS OC4J instance.
Maximum block time (in milliseconds) for listener servlet (s_forms_maxblocktime)
Maximum block time (in milliseconds) for listener servlet
Forms Servlet URL (s_forms_servlet_serverurl)
For the Servlet mode, this variable should be set to the Forms Servlet URL.
For the Forms Socket Mode, this variable should be set to null.
Number of frmweb process (s_frmsrv_nprocs)
Specifies the number of frmweb process that are invoked at Forms Server startup
Forms Servlet Comment (s_forms_servlet_comment)
Removing the # enables starting of jserv processes for the forms group
Use session cookie (s_form_session_cookie)
Depending on the value of this variable, the Forms servlet uses session cookie
to maintain the state of the session. Allowed values are {true, false}.
If set to 'true', the session cookie is used to maintain the state of the
session, else not.
Number of JVMs for FORMS OC4J Instance (s_forms_nprocs)
Specifies the number of JVM processes serving the forms OC4J Instance.
Forms OC4J log rotation time (s_forms_oc4j_log_rotation_time)
This parameter is used to specify the time interval in seconds for rotating the
Forms OC4J log files.
Forms OC4J log rotation size (s_forms_oc4j_log_rotation_size)
This variable specifies the size of the log file in Kilo Bytes when Forms OC4J
will rotate its log file. The default value for this variable is set to 10000KB.
Enable FORMS OC4J Access log (s_forms_oc4j_enable_access_log)
This variable is used to enable/disable OC4J access log for FORMS application.
Setting the value of this variable to 'TRUE' will enable the access log.
12. OACORE OC4J (oacore_server) :
OACORE OC4J Instance Start Parameters (s_oacore_jvm_start_options)
The value of this variable contains the parameters that are passed to the JVM
when starting the OACORE OC4J instance.
Oacore OC4J Options (s_oacore_oc4j_options)
This variable is used to specify the system properties that should be passed to
the oacore OC4J on instance startup.
OACORE OC4J Instance Stop Parameters (s_oacore_jvm_stop_options)
The value of this variable contains the parameters that are passed to the JVM
when stopping the OACORE OC4J instance.
OACORE OC4J Instance Prepend LD_LIBRARY_PATH (s_oacore_prepend_ld_lib_path)
This variable is used to specify path to the libraries that need to be prepended
to the existing LD_LIBRARY_PATH for the OACORE OC4J Instance.
For UNIX platforms, use ':' at the end of the directory list and to separate a
list of directories. For Windows platforms, use ';' at the end of the directory
list and to separate a list of directories
Prepend OACORE OC4J Classpath (s_oacore_prepend_classpath)
This variable is used to specify one or more directories that contain custom
libraries to be included in the OC4J classpath before the inclusion of JAVA_TOP.
Append OACORE OC4J Classpath (s_oacore_append_classpath)
This variable is used to specify one or more directories that contain custom
libraries to be included in the OC4J classpath after the inclusion of JAVA_TOP.
OACORE OC4J Instance LD_LIBRARY_PATH (s_oacore_ld_lib_path)
This variable is used to specify LD_LIBRARY_PATH for the OACORE OC4J Instance.
Load CZ Servlet (s_load_cz_servlet)
This variable is used to determine whether Oracle Configurator servlet classes
defined in orion-web.xml need to be loaded when OC4J server starts. The default
value is set to '1' which means that the servlet is loaded. If you wish to
disable this feature set the value '-1' .
Start Email Center Outbox Processor (s_load_emailcenter_servlet)
This variable is used to determine whether the Email Center Outbox Processor is
started when the OC4J server starts. The Outbox Processor is controlled via the
InitializationServlet class defined in orion-web.xml. The default value is '-1'
which means that the servlet is not loaded. If you wish to enable this feature
set the value to '1'.
Number of JVMs for OACORE OC4J Instance (s_oacore_nprocs)
Specifies the number of JVM processes serving the oacore OC4J Instance.
Oacore OC4J log rotation time (s_oacore_oc4j_log_rotation_time)
This variable is used to set the time interval in seconds for rotating the
Oacore OC4J log files.
Oacore OC4J log rotation size (s_oacore_oc4j_log_rotation_size)
This variable specifies the size of the log file in Kilo Bytes when oacore OC4J
will rotate its log file. The default value for this variable is set to 10000KB.
Enable OACORE OC4J Access log (s_oacore_oc4j_enable_access_log)
This variable is used to enable/disable OC4J access log for OACORE application.
Setting the value of this variable to 'TRUE' will enable the access log.
13. Discoverer (oa_disco_server)
External Integrated Discoverer URL (s_disco_url)
Set the value of this variable to the appropriate external integrated 10G
Discoverer URL. An acceptable value for this parameter is a URL that includes
protocol, host, domain and port.
Discoverer URL Prefix (s_disco_eul_prefix)
14. Metrics Server (oa_met_server) :
Metrics Server Host (s_methost)
Metrics Server Host
Fully Qualified Metrics Server Domain Name (s_metdomain)
Fully Qualified Domain Name for the Metrics Server.
Metrics Server Load Balancing Host (s_leastloadedhost)
Metrics Server Load Balancing Host
Metrics Server Error URL (s_meterrorurl)
Metrics Server Error URL
15. Oracle MWA Server (oa_mwa_server) :
MSCA Log Level (s_mwaLogLevel)
Different log levels can be set for obtaining more debug information.
MSCA Log Rotate (s_mwaLogRotate)
Enable log rotation of files based on size (Yes/No).
MSCA Log File Size (s_mwaLogFileSize)
MSCA Log File Size. If log rotation is enabled, then rotation occurs when log
file exceeds this size.
MSCA Drop Connection Timeout (s_mwaDropConnectionTimeout)
MSCA Drop Connection Timeout. MSCA Server allows a client that was disconnected
to reconnect within the time mentioned below in minutes.
MSCA Stale Session Timeout (s_mwaStaleSessionTimeout)
MSCA Stale Session Timeout. MSCA Server disconnects a client after the client
is idle for mwa.StaleSessionTimeout minutes.
MSCA Dispatcher Thread Count (s_mwaDispatcherThreadCount)
Specify number of worker threads to start from the dispatcher process
MSCA Dispatcher Clients Per Worker (s_mwaDispatcherClientsPerWorker)
Specify number of clients that each dispatcher worker thread can handle
MSCA Compatibility Setting for JVM (s_mwaJVMb)
MSCA Compatability Setting for JVM
MSCA LOV activation by ENTER (s_mwaActivateLOVByEnter)
Used to specify whether user would like to retain old LOV behavior, i.e. LOV
will be activated by ENTER or not
Show Change Responsibility and Change Organization on submenus
(s_mwaSubmenuChangeOrgResp)
Specifies whether Change Responsibility and Change Organization menu items
should appear on submenus; if TRUE, then these menu items will appear on the
main menu and submenus; if FALSE, then these menu items will only appear on
the main menu; the default value is FALSE.
16. Oracle Web Server (oa_web_server) :
Web Server Host (s_webhost)
Web Server Host.
External URL for Third Party Access to E-Business Suite (s_external_url)
This is the URL that third party tools use to connect to the E-Business Suite.
Oracle HTTP Server Directory Index Page (s_directory_index)
This directive sets the list of resources to look for, when the client requests
an index of the directory by specifying a / at the end of the directory name.
You can specify multiple values separated by space for this variable and the
server will return the first one it finds.
Web Host entry point (s_webentryhost)
The Host machine that accepts the http requests.
Web domain entry point (s_webentrydomain)
The domain of the host machine that accepts the http requests.
Location for Lock files and pid files (s_lock_pid_dir)
Location for Lock and pid files to be used for NetApp setup.
Fully Qualified Web Server Domain Name (s_webdomain)
This variable is used to set the fully qualified domain name of the web server.
Server IP Address (s_server_ip_address)
This is the IP address of the Web Host entry point (s_webentry_host) when
configuring according to Oracle MetaLink
will be used by the dbc generation utility when registering this Web Host entry
point with Oracle E-Business Suite.
Oracle HTTP Server Process ID File (s_web_pid_file)
Complete path to the Oracle HTTP Server Process ID File.
URL Protocol (s_url_protocol)
URL Protocol to be used. Allowed Values are {http, https}.
Web SSL Directory (s_web_ssl_directory)
Web SSL Directory.
Local URL Protocol (s_local_url_protocol)
Local URL Protocol. Allowed values {http, https}.
SSLCertificateChainFile (s_web_ssl_certchainfile)
File of PEM-encoded Server CA Certificates.
Name of the wallet file used by webservices (s_websrv_wallet_file)
This is the name of the wallet file used by webservices.
Enable/disable SSL terminator configuration (s_enable_sslterminator)
This variable is used to enable/disable the inclusion of the configuration file
used for SSL terminated environments. By default the value of this variable is
set to '#' which indicates that the configuration file is not included in the
server configuration. To enable, the pound sign '#' must be removed
Sun Plugin version (s_sun_plugin_ver)
Sun Plugin Version.
Sun Desktop Plugin Type (s_sun_plugin_type)
Type of Sun desktop plug-in used for running Forms on desktop clients.
By default, the plugin type is 'jdk' since only 'jdk' is supported in R12.
Sun JDK CLSID (s_sun_clsid)
Class ID for referencing the JDK.
JInitiator version (dots) (s_jinit_ver_dot)
JInitiator version (dot separated syntax)
JInitiator version (commas) (s_jinit_ver_comma)
JInitiator version (comma separated syntax)
JInitiator CLSID (s_jinit_clsid)
CLSID for referencing the JInitiator.
Fully Qualified Proxy Server Host Name (s_proxyhost)
Fully Qualified Proxy Server Host Name.
Proxy Server Port (s_proxyport)
Proxy Server Port.
Fully Qualified Proxy Bypass Domains (s_proxybypassdomain)
Fully Qualified Domains which can bypass the Proxy Server.
Nodes in cluster configuration (s_oc4j_cluster_nodes)
It is a list of Servers that are participating in the cluster configuration.
For example, if two node exists in the configuration, then value will be
appstier1.company.com:6000,appstier2.company.com:6000
on both the application tier servers.
URL for Applications Portal (s_apps_portal_url)
URL for Applications Portal.
List of nodes that have access to Portlet Provider URLs (s_trusted_portals
Enter space separated values consisting of node names or fully qualified node
names or IP addresses of client machines which will be allowed to access
Portlet Provider URLs
Sysadmin Mail ID (s_sysadmin_mail)
Sysadmin Mail ID.
Cookie Domain (s_cookie_domain)
Specific Domain to which the Cookies will be accesible.
Session toplevel domain comment (s_topleveldomain_comment)
Users of Oracle Portal should uncomment this variable.
IANA Characterset (s_iana_cset)
IANA Characterset used by Oracle HTTP Web Server.
Login Page URL (s_login_page)
URL to the Login Page.
Oracle HTTP Server Listen Parameter. (s_http_listen_parameter)
This variable is used to set the Oracle HTTP Server Listen Directive
in httpd.conf. The default value for this variable is set to the value of the
context variable %s_webport% which means that all network interfaces configured
on the web server machine will listen on this port. If there is a requirement
that only one network interface should listen on the specified port then the
value of this variable should be changed to IP:port combination or the value
of s_webhost.s_webdomain:port
Oracle HTTPS Server Listen Parameter. (s_https_listen_parameter)
This variable is used to set the Oracle HTTPS Server Listen Directive
in ssl.conf. The default value for this variable is set to the value of the
context variable %s_webssl_port% which means that all network interfaces
configured on the web server machine will listen on this port. If there is a
requirement that only one network interface should listen on the specified port
then the value of this variable should be changed to IP:port combination or the
value of webhost.webdomain:port
HTTP Server core file location (s_core_dest)
Location where the HTTP Server can dump the core file.
Maximum Number of clients that can connect (s_maxclients)
This directive sets the limit on the number of Simultaneous HTTP requests that
can be supported. The maximum allowed value for MaxClients is 8192.
Enable Keep-Alive connections (s_keepalive)
The persistent connection feature of HTTP/1.1 to provide long-lived HTTP
sessions which allow multiple requests to be sent over the same TCP connection.
OHS timeout (s_keepalive_timeout)
This directive sets the number of seconds OHS will wait for a subsequent request
before closing the connection.
Number of requests that an individual http process will handle
(s_maxrequests_perchild)
This directive sets the number of requests that an individual http child server
process would handle. The maximum allowed value for this variable depends on the
capacity of the system and also on the number of simultaneous users. By default,
the value of this variable is set to '0'.
Number of http requests allowed per connection (s_maxkeepalive_requests)
This directive sets the number of http requests allowed per connection when
KeepAlive directive is set to ON. The maximum allowed value for this variable
depends on the capacity of the system and also on the number of simultaneous
users. By default, this is set to '0'.
Number of minimum idle http server processes (s_minspare_servers)
This directive sets the desired minimum number of idle http server processes.
Number of maximum idle http server processes (s_maxspare_servers)
This directive sets the desired maximum number of idle http server processes.
Help Web Agent (s_help_web_agent)
If HELP_WEB_AGENT profile is set, the value is used for the construction of all
Help related URLs. This allows multiple application installations to share a
common help system. Optional override.
Custom SQL location (s_customsql_path)
Custom SQL reports feature within OAM lets users generate HTML and text reports
based on the SQL scripts they register.
Jserv Session Timeout (s_sesstimeout)
Time in milliseconds to wait before an unused session is invalidated.
JInitiator Progress Dialog (s_java_showprogress)
Feature to show the progress of downloading of JInitiator JAR files.
Ohs log rotation time (s_ohs_log_rotation_time)
This variable specifies the Hour of day when opmn process will rotate its
log file. By default, this is set to '0' which means that the log will be
rotated exactly at midnight.
Opmn log rotation time (s_opmn_log_rotation_time)
This variable specifies the Hour of day when opmn process will rotate its
log file. By default, this is set to '0' which means that the log will be
rotated exactly at midnight.
Opmn log rotation size (s_opmn_log_rotation_size)
This variable specifies the size of the log file in Kilo Bytes when opmn will
rotate its log file. The default value for this variable is set to 1500000 KB
Load OXTA Servlet (s_load_oxta_servlet)
This variable is used to enable/disable loading of the Oracle XML Transport
Agent servlet when oc4j starts up. To enable loading of this servlet, set this
variable to '1'. To disable loading of this servlet, set this variable to '-1'.
By default, the value is set to '1'
Connection pool size for OXTA servlets (s_oxtainpool_size)
Size of the connection pool the OXTA servlets will get connection from when
serving incoming requests. Setting this to a very high value would result in
performance degradation while setting to very low values may result in the OXTA
requests to wait longer for getting a connection. By default, its value is '1'.
JDBC driver file name (s_txk_jdbc_zip)
JDBC driver name.
Long Running JVM (s_long_running_jvm)
Indicates that JVM is expected to have a long lifespan if this value is true.
XML Parser Path (s_xmlparser)
Complete path to the Oracle XML Parser java archive file.
Maximum jdbc pool size (s_fnd_max_jdbc_connections)
fnd_max_jdbc_connections is the maximum jdbc pool size. This is the sum of the
number of available connections and the number of locked connections.
FND JDBC Statement Cache Size (s_fnd_jdbc_stmt_cache_size)
This parameter controls how many parsed SQL statements are retained in the JDBC
cache. Re-execution of statements stored in the JDBC statement cache will not
require a reparse operation and will therefore be highly optimized. It should
not be increased to an extreme value because maintaining this cache takes up
memory in the JVM. We would recommend a value between 200 and 400.
DBC File Name (s_dbc_file_name)
This variable sets the value for the DBC file name. Make sure that you enter
the file name without the extension.
Apps JDBC URL (s_apps_jdbc_connect_descriptor)
Configure this variable only when you have an Oracle RAC Database instance.
Please see Oracle MetaLink Note 388577.1 for more information on RAC and
discussion of the value for this variable.
Apps JDBC Connect Alias (s_apps_jdbc_connect_alias)
Configure this variable only when you have an Oracle RAC Database instance.
This variable can have a value of either a load balanced connect descriptor or
an instance specific connect descriptor. Please see Oracle MetaLink
Note 388577.1 for more information.
Application Server Security Authentication (s_appserverid_authentication)
Application Server Security Authentication can take one of the following values
{ON, OFF, SECURE}. OFF - Server security is not checked. Any application server
machine can access the database. ON - Some level of trust is required to access
the database. Either the Application Server is registered with the database or
the module and version ID are known to be trusted. SECURE - Full trust is
required for access to the database. Only registered Application Server machines
and trusted code modules may connect.
Web entry protocol (s_webentryurlprotocol)
This parameter is used to set the web entry url protocol. Acceptable values for
this parameter are http or https.
Apache OptionsLink Directive (s_options_symlinks)
!CAUTION! Oracle recommends not to change the default value of this parameter.
If you change the default value then you will expose yourself to security
vulnerability and performance degradation of your site.
Session Check Frequency (s_sessionCheck_frequency)
Time interval in milli seconds before checking for invalid sessions in a
Servlet zone.
Oracle HTTP Server Timeout (s_ohstimeout)
This parameter stands for the amount of time (in seconds) the Oracle HTTP Server
will wait for certain events(GET,POST,PUT etc) before failing a request
Apache Log Level (s_apache_loglevel)
Possible values include: debug, info, notice, warn, error, crit, alert, emerg.
Oracle HTTP Server Administrator e-mail address (s_ohs_serveradmin)
This is the email address that the server includes in any error messages sent
to the client.
Property dontChunkRequests for HTTPClient.jar (s_httpclient_dontChunkRequests
Indicates the dontChunkRequests property value for HTTPClient.jar.
Possible values are true and false.
Number of outbound threads (s_outbound_threads)
Number of OXTA threads to be used for simultaneous outbound message sending.
Setting this to a very high value would result in performance degradation while
setting to very low values may result in the OXTA requests to wait longer for
getting a connection. By default, the value of this variable is set to '1'.
OXTAOutUseProxy (s_oxta_proxy)
If this property is set to true, the proxy specified by OXTAOutProxyHost and
OXTAOutProxyPort is used to send messages to the destination
OXTAOutProxyHost (s_oxta_proxyhost)
Fully Qualified proxy server hostname for the Oracle XML Transport Agent (OXTA).
OXTAOutProxyPort (s_oxta_proxyport)
Proxy port for the Oracle XML Transport Agent (OXTA).
TrustStoreType (s_ssl_truststoretype)
The keystore file type of the key material used for the trust manager.
KeyStoreType (s_ssl_keystoretype)
The keystore file type of the key material used for the key manager.
TrustStore (s_ssl_truststore)
Location of the key material for the trust manager.
KeyStore (s_ssl_keystore)
Location of the key material for the key manager.
TrustManagerAlgorithm (s_ssl_trustmanageralgorithm)
Default trust manager factory algorithm name as specified in the Java security
properties. If no such property exists, this variable stores an
implementation-specific default.
KeyManagerAlgorithm (s_ssl_keymanageralgorithm)
Default key manager factory algorithm name specified in the Java security
properties. If no such property exists, this variable stores an
implementation-specific default.
Optimizer Home (s_optit_home)
This variable is used to specify the location of the optimizer suite home.
Parameter to enable/disable URL Firewall (s_enable_urlfirewall)
This variable is used to enable or disable the URL Firewall required for DMZ
configurations. By default the value of this variable is set to '#' which
indicates that the URL firewall is disabled. To enable the URL firewall,
the pound sign '#' must be removed
List of nodes that have access to Oracle HTTP Server administration pages.
(s_admin_ui_access_nodes)
This variable is used to set the list of machines that are allowed to access
the administration pages. Enter space separated values consisting of node names
or fully qualified node names or IP addresses of client machines which will be
allowed to access the administration pages.
Minimum buffer size maintained by the pool (s_fnd_jdbc_buffermin)
This is the minimum buffer size that should be maintained by the applications
database connection pool. Acceptable values are positive integers less
than integer:MAX
Maximum buffer size maintained by the pool (s_fnd_jdbc_buffermax)
This is the maximum buffer size that should be maintained by the applications
database connection pool.Acceptable values are positive integers less than
integer:MAX
Time interval to check the buffer size (s_fnd_jdbc_buffer_decay_interval)
This is the time interval in seconds the maintenance thread checks the buffer
size .Acceptable values are positive integers less than integer:MAX
Maximum number of available objects that should be removed in a thread cycle
(s_fnd_jdbc_buffer_decay_size)
This is the maximum number of connections that will be removed during any one
thread cycle .Acceptable values are positive integers less than integer:MAX
Enable/Disable pl/sql query (s_fnd_jdbc_usable_check)
This variable indicates whether a simple pl/sql query should be performed to
check whether the connection is usable before giving a connection to the client.
Acceptable values are true or false
Enable/Disable AOL security context and NLS state check
(s_fnd_jdbc_context_check)
This variable indicates whether the AOL security context and NLS state should
be obtained from the database server session instead of the java client when
the connection is returned to the pool.Acceptable values are true or false
Free pl/sql state (s_fnd_jdbc_plsql_reset)
This variable indicates whether the pl/sql state should be freed before the
applications database connection pool gives the connection to the client.
JDBC process escape (s_jdbc_proc_esc)
This variable is used to enable or disable JDBC escape processing mechanism.
Changing this parameter value has performance implications.
Custom DBC Parameters (s_custom_dbc_params)
This variable holds a space separated custom dbc parameter list of name value
pairs. For e.g. 'param1=value1 param2=value2 param3=value3'. These values will
be seeded in to the dbc file during AutoConfig execution.
17. OAFM OC4J (oafm_server) :
OAFM OC4J Instance Start Parameters (s_oafm_jvm_start_options)
The value of this variable contains the parameters that are passed to the JVM
when starting the OAFM OC4J instance.
OAFM OC4J Options (s_oafm_oc4j_options)
This variable is used to specify the system properties that should be passed to
the OAFM OC4J on instance startup.
OAFM OC4J Instance Stop Parameters (s_oafm_jvm_stop_options)
The value of this variable contains the parameters that are passed to the JVM
when stopping the OAFM OC4J instance.
Number of JVMs for OAFM OC4J Instance (s_oafm_nprocs)
This specifies the number of JVM processes serving the OAFM OC4J Instance.
Enable OAFM OC4J Access log (s_oafm_oc4j_enable_access_log)
This context variable is used to enable/disable OC4J access log for OAFM and
MapViewer application. Setting the value to 'TRUE' will enable the access log.
18. Oracle Fulfillment Server (jtff_server) :
Oracle Fulfillment Server Instance Id (s_ServerInstanceID)
Identifies the One-to-One Fulfillment Server instance that gets started
when jtffmctl.sh is run.
Oracle Fulfillment Maximum Number of Threads (s_MaxBatchThreads)
Specifies the maximum number of threads on the One-to-One Fulfillment Server
that gets started when jtffmctl.sh is run.
Oracle Fulfillment Turnoff Low Priority Monitors (s_TurnOffLowPriorityMonitor)
Specifies that the monitors of low priority be turned off on the One-to-One
Fulfillment Server instance that gets started when jtffmctl.sh is run.
Oracle Fulfillment Server Debug String (s_jto_debug_string)
A comma-separated list indicating the items for which to log debug information
for the Oracle Fulfillment Server.
Oracle Fulfillment Server Log Level (s_jto_log_level)
Logging level for the Oracle Fulfillment Server. For each number specified
from 1-n, the server will write an extra layer of chained exception traces to
the error log. The exceptions are chained together so that the source of the
errors as they occur can be traced.
Oracle Fulfillment Server RightFax Fax Enabler (s_jto_fax_enabler)
Indicates the Java class that the Fulfillment Server is to use for sending
faxes. This class must implement the oracle.apps.jtf.fm.engine.disp.FaxEnabler
interface to be used as a fax enabler.
Oracle Fulfillment Server RightFax Print Enabler (s_jto_print_enabler)
This flag indicates the Java class that the Fulfillment Server is to use for
sending print jobs to the printer. This class must implement the
oracle.apps.jtf.fm.engine.disp.PrintEnabler interface to be used as a
print enabler.
Oracle Fulfillment Server RightFax zip Location (s_jto_rfjava_loc)
RFJavaInt.zip is the zip file containing the Java integration classes provided
by RightFax upon installation. That file should be included the classpath of the
Fulfillment Server in order to successfully dispatch fax or print requests
through RightFax.
JSP cache directory (s_jsp_cache_dir)
This variable is used to set the .jsp cache directory. Please refer to JSP
Developer's guide for more information on the usage of this variable.
Parameter to enable JSR-45 debugging support (s_jsp_jsr45_dbg)
This variable is used to enable JSR-45 debugging support. Valid settings are
file: to generate an SMAP file, class: to embed debugging info in the generated
class, none: to generate no debugging information. Please refer to JSP
Developer's guide for more information on the usage of these variables.
Parameter to enable printing of stack trace (s_jsp_dbg_mode)
This variable is used to enable printing the stack trace when certain runtime
execeptions occur. Valid settings are true: to generate a stack trace,
false: to turn off printing of the stack trace. Please refer to JSP Developer's
guide for more information on the usage of these variables.
Whether JSP-generated classes are automatically reloaded (s_jsp_main_mode)
This variable is used to specify whether JSP-generated classes are automatically
reloaded or JSP pages are automatically retranslated when JSP changes are made.
Valid settings are recompile: container will check the timestamp of the jsp page
since the last load, reload: container will check the timestamp of classes
generated by the jsp translator, justrun: container will not perform any
timestamp checking. Please refer to JSP Developer's guide for more information
on the usage of these variables.
Oracle Fulfillment Server Enabler Classpath (s_jto_enabler_classpath)
A classpath that specifies the location of custom enabler code (if present)
Oracle Fulfillment Server Log Warning Flag (s_jto_show_warnings)
By default, warnings do not show up in the error log. If this flag is not set,
then the first time a warning appears a single message shows up in the events
log signifying that a warning had been issued. The default is 'false'.
Oracle Fulfillment Server Id (s_jto_server_id)
Identifies the One-to-One Fulfillment Server that gets started when
jtffmctl.sh is run.
Classpath to be used by the Oracle Fulfillment Server (s_jto_classpath)
Classpath to be used by the Oracle Fulfillment Server
Navigation and Forms that will be used while configuring printers
Printer types > Navigate - Install - Printer - Types FNDPRTYP
Printer > Navigate -Install - Printer - Register FNDPRMPR
Print Styles > Navigate - Install - Printer - Style FNDPRRPS
Printer Driver > Navigate - Install - Printer - Driver FNDPRMPD
The following steps to setup printer(s) should be performed in the following
order:
1. Printer types > Navigate - Install - Printer - Types
This window defines a printer type for the new printer.
Any name can be defined, as this field is not a unique id code.
An example for a line printer, name it "LINE" or "LN03" for the model number
of the printer. This name will be associated to the actual printer name when
registering the printer to Oracle Applications.
2. Printer > Navigate -Install - Printer - Register
A printer type must be defined before a new printer can be registered. The
value for printer name will be the operating system printer name.
Then choose the printer type that was defined in the previous step.
3. Printer types > Navigate - Install - Printer - Types
This form is again needed to associate the below printer styles to the
printer type that was defined above.
4. Print Styles > Navigate - Install - Printer - Style
If defining new styles specifically for the new printer, it would be done
here. Please review manual for the specific parameters needed to be defined.
Oracle Applications reports are designed to work with standard shipped styles:
Portrait
Landscape
Landwide
A4
Dynamic Portrait
It is allowed to point to the seeded styles, but for customized
reports, it maybe needed to create a new printer style to accommodate
the custom report(s).
5. Printer Driver > Navigate - Install - Printer - Driver
Oracle does provide the printer drivers for the above Styles, so unless adding
new styles, it should not be required to define one right now.
If defining a new one, must specify a unique printer driver name and a unique
user name for a given platform.
6. Lastly, if any new updates or changes have been made to any of the printer
definitions, the concurrent managers must be bounced to have all changes
take effect.
Printer > Navigate -Install - Printer - Register FNDPRMPR
Print Styles > Navigate - Install - Printer - Style FNDPRRPS
Printer Driver > Navigate - Install - Printer - Driver FNDPRMPD
The following steps to setup printer(s) should be performed in the following
order:
1. Printer types > Navigate - Install - Printer - Types
This window defines a printer type for the new printer.
Any name can be defined, as this field is not a unique id code.
An example for a line printer, name it "LINE" or "LN03" for the model number
of the printer. This name will be associated to the actual printer name when
registering the printer to Oracle Applications.
2. Printer > Navigate -Install - Printer - Register
A printer type must be defined before a new printer can be registered. The
value for printer name will be the operating system printer name.
Then choose the printer type that was defined in the previous step.
3. Printer types > Navigate - Install - Printer - Types
This form is again needed to associate the below printer styles to the
printer type that was defined above.
4. Print Styles > Navigate - Install - Printer - Style
If defining new styles specifically for the new printer, it would be done
here. Please review manual for the specific parameters needed to be defined.
Oracle Applications reports are designed to work with standard shipped styles:
Portrait
Landscape
Landwide
A4
Dynamic Portrait
It is allowed to point to the seeded styles, but for customized
reports, it maybe needed to create a new printer style to accommodate
the custom report(s).
5. Printer Driver > Navigate - Install - Printer - Driver
Oracle does provide the printer drivers for the above Styles, so unless adding
new styles, it should not be required to define one right now.
If defining a new one, must specify a unique printer driver name and a unique
user name for a given platform.
6. Lastly, if any new updates or changes have been made to any of the printer
definitions, the concurrent managers must be bounced to have all changes
take effect.
Monday, June 1, 2009
How to change the standard Oracle logo in R12 Forms ?
To change the logo of Oracle applications perform the following steps:
1.- Open the file $INST_TOP/ora/10.1.2/forms/server/appsweb.cfg
2.- Check the baseHTML and baseHTMLJInitiator variables inside the file. They point to the appsbase.htm file used in the forms (ussually is the same file for both)
3.- Open the file(s) pointed by those variables
4.- Go to the "// Forms Applet Parameters" section related to the client browser you use
5.- Check if there's a line that references to "PARAM name=logo". An example of how that line mustbe for Internet Explorer is:IEhtml += '<' + 'PARAM name=logo value="' + xlogo + '">';
add or change that line according to what you have and what you want.
6.- Go to the "// Oracle Applications default Parameters" section in the same file
7.- Add or edit the definition of xlogo variable. It must be:var xlogo = "%logo%"
8.- Save the file(s)
9.- Locate the variable "logo" in $INST_TOP/ora/10.1.2/forms/server/appsweb.cfg file at the ";
Forms Server Information: servlet, port, machine name and domain" section. If it's not there thenyou can create the line. The variable must point to the .gif file you want to add on the forms.You must put the .gif file in $OA_JAVA/oracle/apps/media and $OA_JAVA paths and point the "logo"variable to your file with:logo=logo_file
10.- Bounce Forms and Apache servers for the changes to take effect11.- Open a new browser window on your client desktop and test the forms.
1.- Open the file $INST_TOP/ora/10.1.2/forms/server/appsweb.cfg
2.- Check the baseHTML and baseHTMLJInitiator variables inside the file. They point to the appsbase.htm file used in the forms (ussually is the same file for both)
3.- Open the file(s) pointed by those variables
4.- Go to the "// Forms Applet Parameters" section related to the client browser you use
5.- Check if there's a line that references to "PARAM name=logo". An example of how that line mustbe for Internet Explorer is:IEhtml += '<' + 'PARAM name=logo value="' + xlogo + '">';
add or change that line according to what you have and what you want.
6.- Go to the "// Oracle Applications default Parameters" section in the same file
7.- Add or edit the definition of xlogo variable. It must be:var xlogo = "%logo%"
8.- Save the file(s)
9.- Locate the variable "logo" in $INST_TOP/ora/10.1.2/forms/server/appsweb.cfg file at the ";
Forms Server Information: servlet, port, machine name and domain" section. If it's not there thenyou can create the line. The variable must point to the .gif file you want to add on the forms.You must put the .gif file in $OA_JAVA/oracle/apps/media and $OA_JAVA paths and point the "logo"variable to your file with:logo=logo_file
10.- Bounce Forms and Apache servers for the changes to take effect11.- Open a new browser window on your client desktop and test the forms.
How to Apply an 11i Patch When adpatch is Already Running
Adpatch is running and fails on one of the workers. To fix this worker andcontinue with the patch installation, a new patch needs to be applied. But only 1 adpatch session can run on an instance at any giventime, The following work around can be used to apply a patch when adpatch is already running.
1. Using the adctrl utility, shutdown the workers.
a. adctrl
b. Select option
3 "Tell worker to shutdown/quit"
2. Backup the FND_INSTALL_PROCESSES table which is owned by the APPLSYS schema
a. sqlplus applsys/
b. create table fnd_Install_processes_back as select * from fnd_Install_processes;
c. The 2 tables should have the same number of records.
select count(*) from fnd_Install_processes_back;
select count(*) from fnd_Install_processes;
3. Backup the AD_DEFERRED_JOBS table.
a. sqlplus applsys/
b. create table AD_DEFERRED_JOBS_back as select * from AD_DEFERRED_JOBS;
c. The 2 tables should have the same number of records.
select count(*) from AD_DEFERRED_JOBS_back;
select count(*) from AD_DEFERRED_JOBS;
4. Backup the .rf9 files located in $APPL_TOP/admin//restart directory.
At this point, the adpatch session should have ended and the cursor should be back at the Unix prompt.
a. cd $APPL_TOP/admin/
b. mv restart restart_back
c. mkdir restart
5. Drop the FND_INSTALL_PROCESSES table and the AD_DEFERRED_JOBS table.
a. sqlplus applsys/
b. drop table FND_INSTALL_PROCESSES;
c. drop table AD_DEFERRED_JOBS;
6. Apply the new patch.
7. Restore the .rf9 files located in $APPL_TOP/admin//restart_back directory.
a. cd $APPL_TOP/admin/
b. mv restart restart_
c. mv restart_back restart
8. Restore the FND_INSTALL_PROCESSES table which is owned by the APPLSYS schema.
a. sqlplus applsys/
b. create table fnd_Install_processes as select * from fnd_Install_processes_back;
c. The 2 tables should have the same number of records.
select count(*) from fnd_Install_processes;
select count(*) from fnd_Install_processes_back;
9. Restore the AD_DEFERRED_JOBS table.
a. sqlplus applsys/
b. create table AD_DEFERRED_JOBS as select * from AD_DEFERRED_JOBS_back;
c. The 2 tables should have the same number of records.
select count(*) from AD_DEFERRED_JOBS_back;
select count(*) from AD_DEFERRED_JOBS;
10. Re-create synonyms
a. sqlplus apps/apps
b. create synonym AD_DEFERRED_JOBS for APPLSYS.AD_DEFERRED_JOBS;
c. create synonym FND_INSTALL_PROCESSES FOR APPLSYS.FND_INSTALL_PROCESSES;
11. Start adpatch, it will resume where it stopped previously.
1. Using the adctrl utility, shutdown the workers.
a. adctrl
b. Select option
3 "Tell worker to shutdown/quit"
2. Backup the FND_INSTALL_PROCESSES table which is owned by the APPLSYS schema
a. sqlplus applsys/
b. create table fnd_Install_processes_back as select * from fnd_Install_processes;
c. The 2 tables should have the same number of records.
select count(*) from fnd_Install_processes_back;
select count(*) from fnd_Install_processes;
3. Backup the AD_DEFERRED_JOBS table.
a. sqlplus applsys/
b. create table AD_DEFERRED_JOBS_back as select * from AD_DEFERRED_JOBS;
c. The 2 tables should have the same number of records.
select count(*) from AD_DEFERRED_JOBS_back;
select count(*) from AD_DEFERRED_JOBS;
4. Backup the .rf9 files located in $APPL_TOP/admin/
At this point, the adpatch session should have ended and the cursor should be back at the Unix prompt.
a. cd $APPL_TOP/admin/
b. mv restart restart_back
c. mkdir restart
5. Drop the FND_INSTALL_PROCESSES table and the AD_DEFERRED_JOBS table.
a. sqlplus applsys/
b. drop table FND_INSTALL_PROCESSES;
c. drop table AD_DEFERRED_JOBS;
6. Apply the new patch.
7. Restore the .rf9 files located in $APPL_TOP/admin/
a. cd $APPL_TOP/admin/
b. mv restart restart_
c. mv restart_back restart
8. Restore the FND_INSTALL_PROCESSES table which is owned by the APPLSYS schema.
a. sqlplus applsys/
b. create table fnd_Install_processes as select * from fnd_Install_processes_back;
c. The 2 tables should have the same number of records.
select count(*) from fnd_Install_processes;
select count(*) from fnd_Install_processes_back;
9. Restore the AD_DEFERRED_JOBS table.
a. sqlplus applsys/
b. create table AD_DEFERRED_JOBS as select * from AD_DEFERRED_JOBS_back;
c. The 2 tables should have the same number of records.
select count(*) from AD_DEFERRED_JOBS_back;
select count(*) from AD_DEFERRED_JOBS;
10. Re-create synonyms
a. sqlplus apps/apps
b. create synonym AD_DEFERRED_JOBS for APPLSYS.AD_DEFERRED_JOBS;
c. create synonym FND_INSTALL_PROCESSES FOR APPLSYS.FND_INSTALL_PROCESSES;
11. Start adpatch, it will resume where it stopped previously.
Subscribe to:
Posts (Atom)