Search This Blog

Friday, June 29, 2012

Oracle Applications Idle Session Timeout

What is Session Idle time?

If Oracle Apps client is idle for some time (Eg. Application user goes for a coffee break) session during that time is called as Idle Session & because of security reason, performance issues and to free up system resource Oracle Applications terminates client session (both forms & self service) after idle time value is reached to the one mentioned in configuration file.

To enter into application, profile option "ICX Session Timeout" is used.

ICX Session Time out mentioned in profile option ICX: Session Timeout is in minutes, so ICX session timeout=30

From where ICX: Session Timeout & session.timeout get values?

Autoconfig determines value for profile option "ICX: Session Timeout" and "session.timeout" from entry in context file ($APPL_TOP/admin/SID_hostname.xml) with parameter s_sesstimeout where value mentioned is in milliseconds so profile option ICX: Session Timeout value should be s_sesstimeout/ (1000 * 60) which means here its 10 Minutes. This value is also set in in $IAS_ORACLE_HOME/Apache/Jserv where number mentioned is in milli second i.e. 600000 (equal to 10 Minutes) session.timeout = 600000.

Eg.  Session Timeout is in minutes, so ICX session timeout=480 is 8Hrs.

Wednesday, June 6, 2012

Drop Tablespace and Datafiles associated with it.

1. Ouery to Drop a Tablespace.


2.Query To delete the tablespace & datafiles associated with a tablespace


Oracle Docs Link For reference:

Location for Apache Log File &Apache Errors

Apache Logfile Location: "$IAS_ORACLE_HOME/Apache/Apache/logs/"

check for the errors in Apache log file.

Some Important HTTP Status Codes:
  • 200 OK
  • 201 Created
  • 202 Accepted
  • 400 Bad Request
  • 401 Unauthorized
  • 402 Payment Required
  • 403 Forbidden
  • 404 Not Found
  • 405 Method Not Allowed
  • 406 Not Acceptable
  • 407 Proxy Authentication Required
  • 408 Request Timeout
  • 409 Conflict
  • 424 Locked
  • 500 Internal Server Error
  • 501 Not Implemented
  • 502 Bad Gateway
  • 503 Service Unavailable
  • 504 Gateway Timeout
  • 505 HTTP Version Not Supported
  • 507 Insufficient Storage

Use the following programs to verify the installation and check that the servlets are functioning.

1. http//:/servlets/IsItWorking (11.5.10) This may fail with:

403 Forbidden You don't have permission to access /servlets/IsItWorking on this server.

This is due to enhanced security delivered with the autoconfig templates..

2. http://:/servlets/Hello

If this fails, this indicates an issue with your Jserv set-up.
You then need to follow Note:230688.1

3. Validate the jsp pages


If this fails , this indicates an issue with your Jserv set-up. You then need to follow Note:230688.1
Check that the CGI environment and mod_plsql is functioning.

4. If you are unable to run the procedure below because of an 'internal error' or a 'cannot find host' or a similar error, then it could indicate that there is a problem with the PLSQL Configuration.

a. Run the following URL:   http://:/pls//FND_WEB.PING

For example:

This should output the results of running FND_WEB.PING package