Thursday, September 26, 2013

A User Cannot See Newly Assigned Responsibilities

Issue: a new responsibility has been assigned to user ,but user not able to see the responsibility .

Solution :
1.clear the cache from functional administrator
2.runt the current request 'Workflow Directory Services User/Role Validation'

also can run
"Sync responsibility role data into the WF table."
"Synchronize WF LOCAL tables"

Thursday, June 13, 2013

VirtualBox Commands for Linux

1.Install Dependency Packages for VirtualBox

# yum update
# yum install binutils qt gcc make patch libgomp glibc-headers glibc-devel kernel-headers kernel-devel dkms

2.Install VirtualBox 4.2.10

    # yum install VirtualBox-4.2

3.Rebuild Kernel Modules for VirtualBox 4.2.10

# /etc/init.d/vboxdrv setup
OR
# service vboxdrv setup

4.Start VirtualBox

#VirtualBox

5.Update VirtualBox

# yum update VirtualBox-4.2


6.Remove VirtualBox

# cd /etc/yum.repos.d/
# rm -rf virtualbox.repo
# yum remove VirtualBox-4.2

Enable X11 forwarding




 Enable X11 forwarding

While doing ssh use the option -X to enable X11 forwarding.

$ ssh username@hostname -X
Enable trusted X11 forwarding, by using the -Y option,

$ ssh username@hostname -Y

Oracle virtualbox installation error on linux 5.6 (64 bit)



Oracle virtualbox installation error on linux 5.6 (64 bit) 

The errors while configure oracle virtual box on Linux.
Download VirtualBox for Redhat 5 64bit
Oracle VirtualBox Download

Error 1: 

[root@abc]# rpm -Uvh VirtualBox-4.1-4.1.4_74291_rhel5-1.x86_64.rpm
warning: VirtualBox-4.1-4.1.4_74291_rhel5-1.x86_64.rpm: Header V4 DSA signature: NOKEY, key ID 98ab5139
error: Failed dependencies:
        libSDL-1.2.so.0()(64bit) is needed by VirtualBox-4.1-4.1.4_74291_rhel5-1.x86_64

Solution:- 

========
when you face above error, you should install two rpms like follows [you can get it from your OS DVD (/media/RH../Packages/)]

SDL-1.2.14-2.el6.i686.rpm
SDL-1.2.14-2.el6.x86_64.rpm


[root@acb]# rpm -Uvh SDL-1.2.10-8.el5.i386.rpm
warning: SDL-1.2.10-8.el5.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Preparing...                ########################################### [100%]
   1:SDL                    ########################################### [100%]
[root@abc]# rpm -Uvh SDL-1.2.10-8.el5.x86_64.rpm
warning: SDL-1.2.10-8.el5.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Preparing...                ########################################### [100%]
   1:SDL                    ########################################### [100%]
Again I try to Install VirtualBox,
[root@abc]# rpm -Uvh VirtualBox-4.1-4.1.4_74291_rhel5-1.x86
warning: VirtualBox-4.1-4.1.4_74291_rhel5-1.x86_64.rpm: Header V4 DSA signature:
Preparing...                ########################################### [100%]
   1:VirtualBox-4.1         ########################################### [100%]

Creating group 'vboxusers'. VM users must be member of that group!

No precompiled module for this kernel found -- trying to build one. Messages
emitted during module compilation will be logged to /var/log/vbox-install.log.

Stopping VirtualBox kernel modules [  OK  ]
Uninstalling old VirtualBox DKMS kernel modules [  OK  ]
Trying to register the VirtualBox kernel modules using DKMS [FAILED]
  (Failed, trying without DKMS)
Recompiling VirtualBox kernel modules [FAILED]
  (Look at /var/log/vbox-install.log to find out what went wrong)
This time virtulbox was installed but i got a dkms error. this condition , you need to download
dkms-2.1.1.2-1.el5.rf.noarch.rpm package.
dkms-2.1.1.2-1.el5.rf.noarch.rpm
[root@abc]# rpm -Uvh dkms-2.1.1.2-1.el5.rf.noarch.rpm
warning: dkms-2.1.1.2-1.el5.rf.noarch.rpm: Header V3 DSA signature: NOKEY, key ID 6b8d79                                                                     e6
error: Failed dependencies:
        kernel-devel is needed by dkms-2.1.1.2-1.el5.rf.noarch
Dependencies rpm package need. the above kernel-devel get it from OS DVD.
[root@abc]# rpm -Uvh kernel-devel-2.6.18-238.el5.x86_64.rpm
warning: kernel-devel-2.6.18-238.el5.x86_64.rpm: Header V3 DSA signature: NOKEY, key ID                                                                      37017186
Preparing...                ########################################### [100%]
   1:kernel-devel           ########################################### [100%]
[root@abc]# rpm -Uvh dkms-2.1.1.2-1.el5.rf.noarch.rpm
warning: dkms-2.1.1.2-1.el5.rf.noarch.rpm: Header V3 DSA signature: NOKEY, key ID 6b8d79                                                                     e6
Preparing...                ########################################### [100%]
   1:dkms                   ########################################### [100%]
Again I try to install Oracle Virtulbox
[root@abc]# rpm -Uvh VirtualBox-4.1-4.1.4_74291_rhel5-1.x86_64.rpm
warning: VirtualBox-4.1-4.1.4_74291_rhel5-1.x86_64.rpm: Header V4 DSA signature: NOKEY,                                                                      key ID 98ab5139
Preparing...                ########################################### [100%]
        package VirtualBox-4.1-4.1.4_74291_rhel5-1.x86_64 is already installed


It show package already Installed, just remove this rpm package and install it again.
[root@abc]# rpm -e VirtualBox-4.1-4.1.4_74291_rhel5-1.x86_64
[root@abc]# rpm -Uvh VirtualBox-4.1-4.1.4_74291_rhel5-1.x86_64.rpm
warning: VirtualBox-4.1-4.1.4_74291_rhel5-1.x86_64.rpm: Header V4 DSA signature: NOKEY,                                                                      key ID 98ab5139
Preparing...                ########################################### [100%]
   1:VirtualBox-4.1         ########################################### [100%]

Creating group 'vboxusers'. VM users must be member of that group!

No precompiled module for this kernel found -- trying to build one. Messages
emitted during module compilation will be logged to /var/log/vbox-install.log.

Stopping VirtualBox kernel modules [  OK  ]
Uninstalling old VirtualBox DKMS kernel modules [  OK  ]
Trying to register the VirtualBox kernel modules using DKMS [  OK  ]
Starting VirtualBox kernel modules [  OK  ]
[root@abc]#

Rebuild Kerel Modules for VirtualBox 

#service vboxdrv setup
Or /etc/init.d/vboxdrv setup

Start VirtualBox

#VirtualBox
OR
Now Everything was okay.
Go to –> Applications –> System Tools –> Oracle VM VirtualBox

Monday, June 10, 2013

How to add or remove the "About This Page" link on E-Business Suite Framework pages


1.In order to add the "About This page " link ,need to set profile at user level

         Personalize Self-Service Defn =yes
         FND: Diagnostics = Yes
         FND: Personalization Region Link Enabled = YES
         Disable Self-Service Personal = NO (Only at Site)

2.In order to remove  the "About This page " link ,need to set profile at user level

            Personalize Self-Service Defn =No
            FND: Diagnostics = No

Ref:  400042.1

Wednesday, May 8, 2013

Automatic startup and shutdown Oracle R12 on Linux


Automatic start up and shutdown Oracle EBS R12 on Linux
After installation on Linux, when the server restarted, the application will not started automatically.
 To start the application automaticaly, we need to create some scripts.

1. startDB.sh :to start the database,using oracle database user, create a file containing this script:

#! /bin/sh
. /oracle/VIS/db/tech_st/10.2.0/VIS_hostname.env
/oracle/VIS/db/tech_st/10.2.0/appsutil/scripts/VIS_oracle/addbctl.sh start
/oracle/VIS/db/tech_st/10.2.0/appsutil/scripts/VIS_oracle/addlnctl.sh start VIS

Then save it as startDB.sh.

2. stapDB.sh to stop the database using this script:
#! /bin/sh
. /oracle/VIS/db/tech_st/10.2.0/VIS_hostname .env
/oracle/VIS/db/tech_st/10.2.0/appsutil/scripts/VIS_oracle/addbctl.sh stop
/oracle/VIS/db/tech_st/10.2.0/appsutil/scripts/VIS_oracle/addlnctl.sh stop VIS
Then save it as stopDB.sh


3. startAPP.sh To start application use this script as applmgre:
#! /bin/sh
. /oracle/VIS/apps/apps_st/appl/VIS_hostname.env
$ADMIN_SCRIPTS_HOME/adstrtal.sh apps/apps
Then save it as startApps.sh

4.stopAPP.sh To stop application, use this script:
#! /bin/sh
. /oracle/VIS/apps/apps_st/appl/VIS_hostname.env
$ADMIN_SCRIPTS_HOME/adstpall.sh apps/apps

5. As root, create a file on /etc/init.d named startVIS containing this script:
#! /bin/sh
#
# /etc/init.d/R12_VIS
#

### BEGIN INIT INFO
# Provides: Oracle Applications
# Required-Start: $syslog $network $xvfbserver
# Required-Stop:
# Default-Start: 3 5
# Default-Stop: 0 1 2 6
# Description: Start the Oracle Applications server
### END INIT INFO

case "$1" in
start)
su oracle -c "/home/oracle/startDB.sh"
su applmgr -c "/home/applmgr/startAPP.sh"
#rc_status -v
;;
stop)
su applmgr -c "/home/applmgr/stopAPP.sh"
su oracle -c "/home/oracle/stopDB.sh"
#rc_status -v
;;

*)
echo "Usage: $0 {start|stop}"
exit 1
;;
esac

6.to add startVIS to the services list. Use this command as root:
chkconfig --add startVIS

assigned responsibility not appearing in the navigator page during login




Issue :
It is often experienced in Oracle Applications R12 that user has been assigned a responsibility but not able to see it while accessing it. However , everything seems fine with responsibility ,it is not end dated and looks good.

Solution : there is a concurrent request that does sync up of such users and responsibiltity in R12 version.

run concurrent request  'Workflow Directory Services User/Role Validation' with parameters 10000, yes, yes

OR

User data in the FND_USER, FND_RESPONSIBILITY, WF_LOCAL_USER_ROLES, and WF_USER_ROLE_ASSIGNMENTS tables is not valid.  To synchronize data follow the steps below:

1.  Navigate to the define user form (FNDSCAUS).
2.  Query up the user (that is having the issue) and insure the responsibility is NOT end dated.
3.  END DATE the USER (not the responsibility) and save the record.
4.  UNEND DATE the USER and save the record.
5.  Run the request 'Sync responsibility role data into the WF table'.
6.  Run the request "Synchronize WF LOCAL tables".
7.  Run the request "Workflow Directory Services User/Role Validation" (with parameters 10000, yes, yes, yes).
8.  Have the user log off and back on and verify that the responsibility appears.

Ref: 565130.1]