To check Oracle EBS/APPS Version
Run following SQL from apps user :
select RELEASE_NAME from fnd_product_groups;
You should see output like :
RELEASE_NAME
-----------------------
11.5.10.2
Below are keyboard shortcut keys in Oracle Apps 11i. Use these to flaunt your skills in apps..
Trust me when you do this in front of clients it works like magic 🙂
Go to the path :
/u88/appprodinst/apps/ListenerName_ServerName/admin/scripts
Run Command from Bash
bash-3.00$ ./adstpall.sh
Go to the path :
/u77/oraprod/prod/db/tech_st/11.1.0/appsutil/scripts/ListenerName_serverName
bash-3.00$ ./addbctl.sh stop
If its taking to much time. You can use this command on extreme cases only :
ps -ef|grep pmon
Than Stop Listener :
bash-3.00$ ./addlnctl.sh stop ListenerName
————–
Go to the path :
/u77/oraprod/prod/db/tech_st/11.1.0/appsutil/scripts/ListenerName_serverName
bash-3.00$ ./addbctl.sh start
Go to the path :
/u88/appprodinst/apps/ListenerName_ServerName/admin/scripts
Run Command from Bash
bash-3.00$ ./adstrtal.sh
This is one of the generic error and there could be multiple reasons, even a bug. Mostly and commonly it is seen in Inventory Module. For example, while you perform Subinventory transfer or Mis transaction then that through “Transaction processor error” or when you perform Inter-Organization Transfer then that through “Transaction processor error“.
Solutions :
1 ) For starters you can check Tablespace, sometimes they are full due to which this kind of issue may occur.
2 ) Check Managers from System Administrator Responsibility
3 ) Check is ‘Receiving Transaction Manager‘ from system administrator responsibility is working or not.
4 ) Check RCV: Processing Mode profile option to immidiate and then restart+activate ‘Receiving Transaction Manager‘ from system administrator responsibility
5 ) Shutdown the Oracle Application & Oracle Database. After doing that start the Database again and once the database is started wait for 5 mins and than start the Application again.
Try all these solutions one by one & hopefully if might resolve the issue. But do it on your own risk !! 😀