REP-3000: Internal error starting Oracle Toolkit
Problem Summary:
================

All the PDF reports are completed with the following Error:

Error:
======

REP-3000: Internal error starting Oracle Toolkit.
REP-3000: Internal error starting Oracle Toolkit.
REP-0069: Internal error
REP-57054: In-process job terminated:Terminated with error:
REP-3000: Internal error starting Oracle Toolkit.

Solution:
=========

As a root user run this in background:
=======================================

1.

ps -efgrep X11

if there is session running then no need to do the 1st step. If not do the following . You can run even from the putty session also.


nohup /usr/lpp/X11/bin/xinit /usr/lpp/X11/bin/mwm -- :1 -vfb -force -x abx -x dbe -x GLX &

export DISPLAY=:1.0
xhost +

2. As a applmgr user

cd $ORACLE_HOME ie)

Edit the following file and check for the display setting and put the correct host entry.

/testapps/apps/tech_st/10.1.2/bin/reports.sh

DISPLAY=doyensys:1.0; export DISPLAY
xhost +

3. Now Bounce the concurrent
Posted by Saravanan at 5:27 AM 0 comments
Labels: Apps Faced Isses and common problems
Tuesday, July 19, 2011
APP-FND-00362: Routine afpbep cannot execute request &REQUEST for program &PROGRAM
Error:
=====

APP-FND-00362: Routine afpbep cannot execute request &REQUEST for program &PROGRAM, because the environment variable &BASEPATH is not set for the application
to which the concurrent program executable &EXECUTABLE belongs.
Shut down the concurrent managers. Set the basepath environment variable for the application. Restart the concurrent managers. (VARIABLE=)Routine AFPEOT cannot construct the name of an executable file for your concurrent request 6945444.
Check that the file name components are correct and valid on your system. Check that the environment for the person who started the concurrent manager

+Executing request completion options... -- 1) PUBLISH -------------+Beginning post-processing of request 6945444 on node TESTSERVER at 19-JUL-2011 15:23:24.Post-processing of request 6988838 failed at 19-JUL-2011 15:33:24 with the error message:The Output Post-processor is running but has not picked up this request. No further attempts will be made to post-process this request, and the request will be marked with Warning status.Setting the profile option Concurrent: OPP Response Timeout to a higher value may be necessary.+--------------------------------------+

Scenario:
=======

There is a Custom Top registered and that top is not set in the ENV while starting the conc.


Request Name :

XXTEST Daily Stock of PRODUCTS

Query to Check whether the Env is set for the Particular request :
===============================================

select variable_name,value from fnd_env_context e ,fnd_concurrent_processes p ,fnd_concurrent_requests r where p.concurrent_process_id =
e.concurrent_process_id and p.concurrent_process_id = r.controlling_manager and e.variable_name like '%CUSTOM_TOP%' and r.request_id = &request_id;

Solution :
=======

Add the respective Top in env file

ie) APPL_TOP/admin/adovars.env

so that while running autoconfig it wont remove every time.

XXTEST_TOP="/u01/apps/apps_st/appl/XXTEST/1.0.0" export XXTEST_TOP

Now Bounce the concurrent

Reference Note ID : 1050646.1
Posted by Saravanan at 4:32 AM 0 comments
Labels: Apps Faced Isses and common problems
Wednesday, October 6, 2010
APP-FND-01542 : This Application Server is not authorized to access this system
Scenario:
=======
When you are trying to access the Front end URL it is not giving some error. So , you are using http://hostname:port/dev60cgi/f60cgi and trying to login to the server which gives the following error.

Error:
=====
“APP-FND-01542 : This Application Server is not authorized to access this system. Please contact your System Administrator. ”

Solution:
=======
Step 1 : Edit the Context file ie) $APPL_TOP/admin/SID_hostname.xml.
Step 2 : Change the Variable : s_appserverid_authentication to be OFF.Step
3 : Run Autoconfig $ cd $COMMON_TOP/admin/scripts/$CONTEXT_NAME$ sh adautocfg.sh

Now, you can test the application login.

Note :
=====

There are three modes of authentication you can configure your applications by setting the parameter
s_appserverid_authentication to ON :
s_appserverid_authentication to Partial
s_appserverid_authentication to SECURE : activates full server security (SECURE mode)
s_appserverid_authentication to OFF : deactivates server security
By default in 11.5.10, this is set to SECURE. In previous 11i versions, this wasset to OFF.
Posted by Saravanan at 12:09 AM 0 comments
Labels: Apps Faced Isses and common problems
Wednesday, June 30, 2010
Change of IP Address for the Oracle Apps R12/11i Server
Scenario
=======

Oracle Apps R12 was installed in the server name DOYENSYS and the ip was 192.168.5.33. Now the Organisation Planned to move the server to the data centre. After Moving the IP has been changed as the following 192.168.1.33.

Problem:
=======

While starting the apps Tier it starts and while opening the front end forms it gives the following error:


500 Internal Server Error

java.lang.NoClassDefFoundError
at oracle.apps.fnd.sso.AppsLoginRedirect.AppsSetting(AppsLoginRedirect.java:126)
at oracle.apps.fnd.sso.AppsLoginRedirect.init(AppsLoginRedirect.java:170)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpApplication.loadServlet(HttpApplication.java:2231)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpApplication.findServlet(HttpApplication.java:4617)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpApplication.findServlet(HttpApplication.java:4541)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpApplication.getRequestDispatcher(HttpApplication.java:2821)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:740)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:451)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.AJPRequestHandler.run(AJPRequestHandler.java:299)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].server.http.AJPRequestHandler.run(AJPRequestHandler.java:187)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:230)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$800(ServerSocketAcceptHandler.java:33)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:831)
at com.evermind[Oracle Containers for J2EE 10g (10.1.3.0.0) ].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)


Solution:
=======

Step 1 : Shut down apps,DB,listener.

Step 2 : edit the host file and put the local ip as the first entry. For ex :( 192.168.1.33 DOYENSYS ).

Step 3 : Start DB and Listener.

Step 4 : Check the ip which is in the FND_NODES table by using the following Query.

select NODE_NAME,SERVER_ADDRESS from fnd_nodes where node_name = upper('doyensys');

NODE_NAME SERVER_ADDRESS
------------------------------ ------------------------------
DOYENSYS 192.168.5.33

Step 5 : It show the old ip.

Step 6 : Run Autoconfig in apps Tier

Step 7 : Now Check the Query again.

select NODE_NAME,SERVER_ADDRESS from fnd_nodes where node_name = upper('uatartha');

NODE_NAME SERVER_ADDRESS
------------------------------ ------------------------------
DOYENSYS 192.168.1.33

Step 8 : Now start apps Tier.


Note id : How to Change IP Address in an Oracle Applications Environment ID 553318.1
Posted by Saravanan at 8:38 AM 0 comments
Labels: Apps Faced Isses and common problems
Tuesday, May 18, 2010
Node id/Server id not found while starting 11i
Problem:
=======
While starting the concurrent the script. says node id not found and the the while opening the forms we get the following error.


Solution:
Step 1 : Stop Apps Tier
Step 2 :

SQL> select server_id from fnd_nodes;
SERVER_ID
----------------------------------------------------------------
Now it shows Nothing.
Step 3: Backup the existing dbc and generate new dbc

/progs2/11i/uat/applmgr/uatappl/fnd/11.5.0/secure/uat_doyensys/uat_doyensys.dbc

mv uat_doyensys.dbc uat_doyensys_old.dbc
Step 4 : Run adgendbc.sh , So that this will generate a new dbc file.

/progs2/11i/uat/applmgr/uatcomn/admin/install/uat_doyensys/adgendbc.sh

sh adgendbc.sh apps apps

Step 5 : Now Run Autoconfig on both nodes.

Step 6 : Now check the Following:

SQL> select server_id from fnd_nodes;
SERVER_ID
----------------------------------------------------------------
SECURE
86CA4A081E008B32E043AC101BF58B3213785653262223406441150570220513
Step 7 : Now start apps.
Posted by Saravanan at 3:07 AM 3 comments
Labels: Apps Faced Isses and common problems
Monday, April 26, 2010
OUTPUT POST PROCESSOR AND WF DOESN'T STARTS AFTER UPGRADE
Problem:

After DB and RUP7 and JRE Upgrade Output Post Processor and WF Doesn't starts

Reason:

AFJVAPRG point to a wrong place.

echo $AFJVAPRG
/usr/java14


Solution:

change as if below in the XML file in apps tier

1. Shut down apps Tier
2. change AFJVAPRG path to /usr/java14/bin/java
3. run autoconfig
4. Start Apps Tier
Posted by Saravanan at 3:08 AM 2 comments
Labels: Apps Faced Isses and common problems
Wednesday, February 17, 2010
ksh[41]: 594110 Segmentation fault(coredump)
Environment :
=============

Environment : IBM AIX 5.3
apps : 11.5.8
DB : 9.2.0.6


Scenario:
=======

While Cloning the database to a new server which is configured newly, DB and Apps Cloned successfully, But while starting the concurrent and all other services the concurrent startup and immediately goes down with the following error:

Error Faced :
===========

Check that your system has enough resources to start a concurrent manager process. Contact your syst : 25-JAN-2010 12:26:42
Starting STANDARD Concurrent Manager : 25-JAN-2010 12:26:42

FS-NCROINT FAILED Service Manager FNDSM_DOYENDB_PROD could not initialize. The Service Manager has been unable to verify its environment and create its log file.

Routine AFPEIM encountered an error while starting concurrent manager STANDARD with library /db/oracle/prodappl/fnd/11.5.0/bin/FNDLIBR.

Check that your system has enough resources to start a concurrent manager process. Contact your syst : 25-JAN-2010 12:26:42
Starting STANDARD Concurrent Manager : 25-JAN-2010 12:26:42
ksh[41]: 594110 Segmentation fault(coredump)

The PROD_0125@PROD internal concurrent manager has terminated with status 139 - giving up.


Note :
=====
core file getting generated also in the $APPLCSF/scripts/PROD and if the GSM is made to N , The concurrent is running fine. But when it is set to Y, Then concurrent Goes Down

Solution:
=========

These Error is Known as Memory Leake Error. Metalink has came up with the following Patch.

patch 3263843
Posted by Saravanan at 11:23 AM 5 comments
Labels: Apps Faced Isses and common problems
Monday, April 20, 2009
File server could not verify its initialization parameters
Error:

Error Viewing CM log files - File server could not verify its initialization parameters


Cause:

The issue is because of the syntax error in listener.ora file on apps side. Go to TNS_ADMIN directory and in the listener file , If you check the parameter APPLFSTT in appmgr side , you will see there is a space between the value. So FNDFS cannot interpret the space between the value

Solution:


Workaround:

Remove the space between the values and bounce apps listener.

Permanent Fix:

As per metalink note ID 304568.1, apply patch 4244610 to the environment.
Posted by Saravanan at 12:35 AM 1 comments
Labels: Apps Faced Isses and common problems
Tuesday, March 31, 2009
Workflow Agent Listener Service startup problem
Scenario:
---------

When we add the Resposibility to the user and save the changes, It does not take effect, Due to the Workflow Agent Listener Service, Work Flow Mailer Service and Document Web Services Service is Not up and also If we try to restart from Concurrent --> Administer --> Workflow Agent Listener Service --> Restart, It keep on Says restarting But Not Starts.

Cause :
-------

The Path for appsborg2.zip may not be added in AF_CLASSPATH in the XML file.

Soultion:

1. Check whether the GSM is Up and Running in the system --> Profile option or using the Following Query :

select DECODE(b.profile_option_value, 'Y', 'Enabled', 'Disabled') DETAILS
from fnd_profile_options a, fnd_profile_option_values b
where a.APPLICATION_ID = b.APPLICATION_ID
and a.PROFILE_OPTION_ID = b.PROFILE_OPTION_ID
and a.PROFILE_OPTION_NAME = 'CONC_GSM_ENABLED';

2. Check whether the Service Manager is up and Running by the following Query :

select CONCURRENT_QUEUE_NAME, ENABLED_FLAG, MAX_PROCESSES, RUNNING_PROCESSES
from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME like 'FNDSM%';

3. Check the Path for AF_CLASSPATH by

echo $AF_CLASSPATH and check whether it show the appsborg2.zip

Note : It may show appsborg.zip But Not appsborg2.zip .

4. Check the $AF_CLASSPATH in the XML file. If appsborg2.zip is Not there then add that path in the xml file before the appsborg.zip

For Example :

AF_CLASSPATH=/DBA/oracle/dbacomn/util/java/1.5/jdk1.5.0_11/lib/rt.jar:/DBA/oracle/dbacomn/util/java/1.5/jdk1.5.0_11/lib/i18n.jar:/DBA/oracle/dbacomn/java/appsborg2.zip:/DBA/oracle/dbacomn/java/appsborg.zip:/DBA/oracle/dbacomn/java/apps.zip:/DBA/oracle/dbaora/8.0.6/forms60/java:/DBA/oracle/dbacomn/java

Note : Backup the XML file before Editing.

5. Now Run the Autoconfig .

6. Now If possible Bouce the appsTier and check for the Workflow Agent Listener Service. It will be started.

Refered Note id :

How to Troubleshoot when the Workflow Services Go Down
Doc ID: 564394.1
Posted by Saravanan at 3:53 AM 1 comments
Labels: Apps Faced Isses and common problems
Tuesday, March 24, 2009
Cannot login from the personal homepage in 11i
Problem Scenario:
=================

when accessing through the Normal URL we cannot access the forms. But while we access forms directly through the dev60cgi/f60cgi URL we can access.

Normal URL : http://oratest.doyensys.com:8000/
Forms Direct URL : http://oratest.doyensys.com:8000/dev60cgi/f60cgi

Solution:
=========

1. Login Via Forms Direct URL and login as a system Admin responsibility.
2. Navigate to PROFILE --> system.
3. Query for %FORMS%LAUNCH% in the Profile and click Find.




4. You will find the Profile option name as ICX:Forms Launcher and the Value for site level is http://oratest.doyensys.com:8000/dev60cgi/f60cgi


5. If there is any other thing at responsibility level, Remove that. It should be at site level only.

Note : If you are using RAC Node, Then if the site level value is set to single Node then it wont works . For example your test Node has two apps node named
oraapptest1 and oraapptest2 but when it navigates it should be oratest as a instance name.
So, In site level if it is set to
http://oraapptest1.doyensys.com:8000/dev60cgi/f60cgi , Then it won't Launch the forms.
It should be http://oratest.doyensys.com:8000/dev60cgi/f60cgi in site Level.
So that it will Automatically Navigates to Oraapptest1 or oraapptest2 Nodes.

Reference:
-------------
145019.1 - Database Login Failed" When Tying to Login From Personal Homepage

Posted by Saravanan at 10:53 PM 1 comments
Labels: Apps Faced Isses and common problems
Friday, February 20, 2009
ORA-01502: Index is in unusable state

Scenario:

After Moving the Index and Tables from APPS_TS_QUEUES tablespace to other and when open the forms to run a request it shows the following Error.

Error :

While compiling the flexfields, the procedure wf_event.raise failed with following
parameters:
event_name = oracle.apps.fnd.flex.dff.compiled
event_key = FND.$SRS$.FNDSCURS

The error raised is:

ORA-00604: error occurred at recursive SQL level 1
ORA-01502: index 'APPLSYS.SYS_C00169351' or partition of such index is in unusable state


Solution:
=======
select index_name,status from dba_indexes where tablespace_name='APPS_TS_QUEUES' and STATUS != 'VALID';
Now It shows the Index which are all unusable. So rebuild the following indexes by

select 'alter index 'owner'.'index_name' rebuild;' from dba_indexes where tablespace_name='APPS_TS_QUEUES' and STATUS != 'VALID';
Note: This query shows the output to alter all the indexes that are unusable in the particular tablespace . SO take the outpu of the above query and save it as .sql and run the following sql to make it valid state. Now try running the concurrent Request
Posted by Saravanan at 4:26 AM 0 comments
Labels: Apps Faced Isses and common problems
Saturday, October 18, 2008
Report completed with error
Error :
=====

While runnig a request all the request are completed with error in RHEL 4 update 5 in 11.5.10.2


Error Reports:
===========


APPLLCSP Environment Variable set to :

XML_REPORTS_XENVIRONMENT is :
/oracle/app/apps/sarora/8.0.6/guicommon6/tk60/admin/Tk2Motif_UTF8.rgb

XENVIRONMENT is set to: /oracle/app/apps/sarora/8.0.6/guicommon6/tk60/admin/Tk2Motif_UTF8.rgb


Current NLS_LANG and NLS_NUMERIC_CHARACTERS Environment Variables are :
American_America.UTF8

'.,'

Spawned Process 12429
ar60run: relocation error: /oracle/app/apps/sarora/8.0.6/network/jre11/lib/i686/native_threads/libjava.so: symbol __libc_wait, version GLIBC_2.0 not defined in file libc.so.6 with link time reference

Program exited with status 127
Concurrent Manager encountered an error while running Oracle*Report for your concurrent request 2729840.


Solution :
========

1. Apply the rpm compat-libcwait-2.1-1.i386.rpm

or

2. Put the following line in .bash_profile in root as well as oracle :

LD_ASSUME_KERNEL=2.4.19
export LD_ASSUME_KERNEL
Posted by Saravanan at 11:17 AM 1 comments
Labels: Apps Faced Isses and common problems
Language error in Apps Report output
For the Language Problem in oracle apps:

/oracle/app/apps/testora/8.0.6/guicommon6/tk60/admin

vi Tk2Motif_UTF8.rgb

!Tk2Motif*fontMapCs: iso8859-2=EE8ISO8859P2
Tk2Motif*fontMapCs: iso8859-1=UTF8

Note :

Here the commented line may be changed. so do the following as mentioned above.
Posted by Saravanan at 11:14 AM 0 comments
Labels: Apps Faced Isses and common problems
The field PARAMETER.CONFIG could not be located or read
Problem Description:

When we login to apps it is not connecting but both database and apps are up and running.

Error :

"The field PARAMETER.CONFIG could not be located or read."
The adapcctl.log carries the following errors:
Cannot read value from field PARAMETER.CONFIG
Cause: The field PARAMETER.CONFIG could not be located or read.

Making AOL/J Test

ERROR:validateLogin returned false: failed to login as sysadmin, please try again.
AOLJ_JAVA_EXCEPTION (MESSAGE=Not able to create new database connection: FNDSECURITY_APPL_USERID_INVALID)
SECURITY_INVALID_DBC_PARAMETER (PARAMETER=GUEST_USER_PWD) (FILE=/progs/11i/prod/applmgr/prodappl/fnd/11.5.0/secure/prod_atlas/prod.dbc) (ROUTINE=AppsConnectionManager.makeGuestConnection)
FNDSECURITY_APPL_USERID_INVALID
SECURITY_APPL_USERID_INVALID
AOLJ_JAVA_EXCEPTION (MESSAGE=Profiles: getJDBCConnection() == null)
AOLJ_JAVA_EXCEPTION (MESSAGE=Not able to create new database connection: FNDSECURITY_APPL_USERID_INVALID)
SECURITY_INVALID_DBC_PARAMETER (PARAMETER=GUEST_USER_PWD) (FILE=/progs/11i/prod/applmgr/prodappl/fnd/11.5.0/secure/prod_atlas/prod.dbc) (ROUTINE=AppsConnectionManager.makeGuestConnection)
FNDSECURITY_APPL_USERID_INVALID
SECURITY_APPL_USERID_INVALID

Cause:

There is a problem with Guest user. So proceed checking Guest user.

Step 1 :

SQL> select fnd_web_sec.validate_login('GUEST','GUEST') from dual;
FND_WEB_SEC.VALIDATE_LOGIN('GUEST','GUEST')
--------------------------------------------------------------------------------
Y

SQL> select profile_option_value from fnd_profile_option_values where profile_option_id = 3805;
PROFILE_OPTION_VALUE
--------------------------------------------------------------------------------
GUEST/GUEST


Fix :

Check the FND_USER table and check the end_date column for the Guest user. It will be end dated. So to make it null do the following.

Login as apps user.

Back up your FND_USER TABLE

Run the following command

update fnd_user set end_date=null where user_name='GUEST';

Now Run the autoconfig.

Start Apps.
Posted by Saravanan at 11:09 AM 1 comments
Labels: Apps Faced Isses and common problems
FRM-92150 Web client version too new
Error:

While we click the responsibility, the form. opens at that time the following error comes:

FRM-92150 Web client version too new

Solution:
========

1. Remove all folder named Java, Jinit etc and go to the program file in that delete the oracle folder itself because it contains Jar files only.

2. From control panel add/remove Programs remove java versions.

3. Clear the temp, cache etc.

4. Go to Regedit

A) HKEY_CURRENT_USER -> software - >ORACLE // remove that oracle folder itself.

B) HKEY_LOCAL_MACHINE -> software -> ORACLE // remove that oracle folder.

5. Now clear and check all jar files are removed.

6. Go to internet properties --> securities --> In that Local Internet option --> custom level -->Low and ok.

7. Now restart the PC and go to that responsibilty and click . New Jar files will be downloaded and it will be proper.

Note:

This Jar files are loaded from the apps server in the location COMMON_TOP/util/jinitiator.jinit.exe

So we can copy from the server to the client also, The above exe.
Posted by Saravanan at 11:02 AM 2 comments
Labels: Apps Faced Isses and common problems
Xlib: No protocol specified
ERROR ENCOUNTERED :

While Running the report ex :Doyen Ennore Activity Report (Daily) and the output is in pdf format the following error is encountered.

Error in the log file:

Xlib: connection to "dbserv2:0.0" refused by server
Xlib: No protocol specified
Xlib: connection to "dbserv2:0.0" refused by server
Xlib: No protocol specified
REP-3000: Internal error starting Oracle Toolkit.
REP-3000: Internal error starting Oracle Toolkit

Solution:

Enter in to the Node where the Report is Running and can also done in all the nodes

STEP 1 : Login as user root.
STEP 2 : export DISPLAY=localhost:0.0
STEP 3 : xhost +
STEP 4 : To Check the Display put the following : echo $DISPLAY
STEP 5 : We can also check by entering in as any other user

ex:oracle or apps user and give xclock. So that it will display clock.

Note :Before settting the DISPLAY check the XML file in APPL_TOP/ADMIN and inside the xml file see the parameter DISPLAY = "hostname:0.0" or some thing . this shold be same as when we give echo $DISPLAY

STEP 6 : Now bounce the concurrent and check for the report it will work fine.
Posted by Saravanan at 10:56 AM 0 comments
Labels: Apps Faced Isses and common problems
After Cloning Apps could not start
Scenario:

1. After cloning and when we start the database and apps it start but when we see the log file in $APPLCSF/log

It shows the following error message

Error:

JSP Error
Exception:java.lang.RuntimeException: Cannot get Connection to the Database
at oracle.apps.fnd.sso.Utils.getConnection(Utils.java:190)
at _oa__html._fndvald._jspService(_fndvald.java:72)
at oracle.jsp.runtime.HttpJsp.service(HttpJsp.java:119)
at oracle.jsp.app.JspApplication.dispatchRequest(JspApplication.java:385)
at oracle.jsp.JspServlet.doDispatch(JspServlet.java:259)
at oracle.jsp.JspServlet.internalService(JspServlet.java:178)
at oracle.jsp.JspServlet.service(JspServlet.java:148)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
at org.apache.jserv.JServConnection.processRequest(JServConnection.java:456)
at org.apache.jserv.JServConnection.run(JServConnection.java:294)
at java.lang.Thread.run(Thread.java:484)

Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

Oracle HTTP Server Powered by Apache/1.3.19 Server at devpserv.sical.in Port 8272

Cause :

In the Pfile the parameter named PROCESS value is very less , So it cannot use all the process and so it starts killing the processes.

Solution:

1.Check the DB, it is not started and though it is started some process are killed.
2.Check $APPLCSF/log and check the files that are last updated. 3.There is a error that max no of connections ORA-
4.Now in the init parameter of database increase the process=400
5.change in the xml file of database and run autoconfig in database side.
Posted by Saravanan at 10:47 AM 1 comments
Labels: Apps Faced Isses and common problems
Tuesday, September 30, 2008
Apps Issues Faced
In order to take trace of a concurrent :


============================

1.concurrent:program -->define --> enable trace.
2.Now save and run the request. And see the udump file.
3.Now take that and put tkprof by
4.tkprof sample01.trc utput=sample.txt
5.Now view the text file by vi editor and in linux, sort the file output by the following command
6.Grep -I total Tkprof outpfile name sort -n +5
7.Now leave the last two consolidated total and look the above highest four count from bottom.
8.Now check the sql which takes the more usage.



====================================================================



possiblities to check and Tune concurrent request:
====================================

1.Go to Concurrent --> Administer -->
2. Now check the the standard manager's Actual and target.
3. Let us assume it is Actual 30 and Target 30.
4. Now check the pending it can be 20
5.check the running column. It should be atleast 10 if it is very less then we need to check the cache.
6. Now go to concurrent:Manager --> Define --> f11 and search for standard manager and see the cache size.
7. If it is very less then change that size to 8 or 9 or 10 and save.8. Also check the workshift --> sleep seconds and processes.
8. keep sleep second to be 30 as average.9. Now check in Concurrent --> Administer -->
9. Check the actual,target and running it should run atleast 10 ata time in the running column of standard manager.

To Administer Concurrent Manager:



To check the Cache Size:


====================================================================================================================
Posted by Saravanan at 1:40 AM 0 comments
Labels: Apps Faced Isses and common problems