Posts

Showing posts from May, 2012

Unable to resolve LABEL - Editing fstab from "Repair Filesystem" prompt - Openfiler (Linux)

I deleted one of my partitions from my openfiler box and forgot to remove the auto boot entry from fstab. While booting the system it stops complaining unable to resolve 'LABEL=/name_of_label' . It happens sometimes we delete a partition and forget to remove automatic boot entry from fstab file. Once system is reboot it stops booting giving  unable to resolve 'LABEL=/name_of_label' message. Then system automatically asks password for maintenance, once password is supplied  a repair filesystem prompt is given . If we try to edit the fstab file in this mode system will complain 'readonly' option is set This error happens because of system trying to mount a partition with the said LABEL which is not actually available, pointing to wrong partition, etc. you can either remove the entry from fstab or you can edit fstab to correct the LABEL or partition. Use this command to remount in read/write mode and then do necessary changes in fstab file

Setting Starting Page on R12 (12.1.3)

Image
Log in and go to preferences  Go to Start Page Area  Select the Responsibility Select the page you want as starting page

APP-FND-01436: List of Values cannot find any values for you to choose error from concurrent request program parameter (R12 12.1.3)

Image
APP-FND-01436: List of Values cannot find any values for you to choose error from concurrent request program parameter After upgrading oracle application 11i(11.5.10.2) to R12(12.1.3) running concurrent program request caused this issue When concurrent program is run for a concurrent request after upgrading to R12 12.1.3 the lov, which is attached to a parameter, gives APP-FND-01436: “List of Values cannot find any values for you to choose”. When the same request is run from oracle applications 11i 11.5.10.2 the same value set is working fine. The value set is based on a table. If you go and test the value set query from the value set definition screen it returns complete successful message yet if you go to the parameter of the concurrent request program form where the particular value set is used it gives you the above error. After searching google and oracle support I found metalink note 1400963.1, EBS R12.1: Parameter for Concurrent Request Using Table Based LOV G