Enabling / Disabling buttons / functions in custom forms.

 

• Attach APPCORE.pll (Intern it will automatically link other related .pll)
• Define parameter (naming convention can be followed)

            (Application Top)_(Form Name)_(Button/Function Name)

 

• Copy Trigger from APPSTAND.fmb

           WHEN_NEW_FORM_Instance

            PRE_FOME

            WHEN_WINDOW_CLOSE

 

• Add following to WHEN_NEW_FORM_INSTANCE

If Not Fnd_Function.Test((Application Top)_(Form Name)_(Button/Function Name)')

Then

                        Set_Item_Property('Blockname.ACTION',Displayed,Property_False);

End If;

System Admin à Application à Function

• Define function (Application Top)_(Form Name)_(Button/Function Name) , select type=SUBFUNCTION , attach original form name.
• Add the function name in related menu
• Exclude function from Responsibility definition.

 

 

Linux How-To

Finding Your Linux Release

This you can get from a static file redhat-release located in the /etc  directory

view /etc/redhat-release
Red Hat Enterprise Linux AS release 4

NFS mounting on Linux

Supposing you want to mount a u01/sam on Node_A to Node_B

Configurations on Node_A
edit the /etc/exports file
vi /etc/exports
add the filesystem to mount
/u01/sam ro Node_B

you can either use the option ro which means read only or in case you wish to allow node_b to write into the filesystem use  the rw option which is read writeable.

The change in exports file takes effect only after the restart of your NFS service daemon. use the service command to do  that.

# service nfs restart
Shutting down NFS mountd:                                  [  OK  ]
Shutting down NFS daemon:                                  [  OK  ]
Shutting down NFS quotas:                                  [  OK  ]
Shutting down NFS services:                                [  OK  ]
Starting NFS services:                                     [  OK  ]
Starting NFS quotas:                                       [  OK  ]
Starting NFS daemon:                                       [  OK  ]
Starting NFS mountd:                                       [  OK  ]

Configuration for Node_B

On Node_B simply create the mount point to hold the shared file system and mount it using the mount command.

#mkdir sam
#mount -t nfs Node_A:/u01/sam /sam

Setting Kernel Parameters

Most oracle products require certain kernel parameters to be set as a pre requisite for installation. Common kernel parameters include parameters for shared memory .

The /etc/sysctl.conf file takes care of your kernel parameters.
#vi /etc/sysctl.conf
kernel.shmmax = 2147483648
kernel.shmmni = 128
kernel.shmall = 2097152
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000

However changes made to this file take effect only after the next reboot.

The sysctl command can be used to set the kernel parameter at runtime in linux.

sysctl -w kernel.shmmax=2147483648

You must however make the change in the /etc/sysctl.conf so that it is permanent.

Increasing the Swap space at runtime

Imagine this, you start the OUI and your pre installation check fails due to insufficient swap space. Now I agree that you  got to check all this before starting the installation but just in case you missed it. You could always increase it on the  fly.

Check the memory on your server

# free -m
             total       used       free     shared    buffers     cached
Mem:          8117       3204       4913          0         77       2648
-/+ buffers/cache:        478       7639
Swap:          101          0        101

Now say you need to increase it by 500 MB for your server, first locate a place you can spare this 500 MB in my case i found  it in /u01

Use the dd command to create a swapfile

#cd /u01
# dd if=/dev/zero of=swapfile bs=1024 count=512000
512000+0 records in
512000+0 records out
# ls -ltr
drwx------   2 root   root     16384 May  1  2006 lost+found
-rw-r--r--   1 root   root 524288000 Nov 28 13:58 swapfile

Next issue the following two commands

# mkswap swapfile
Setting up swapspace version 1, size = 524283 kB
# swapon swapfile

Now check you memory again

# free -m
             total       used       free     shared    buffers     cached
Mem:          8117       2176       5941          0         45       1975
-/+ buffers/cache:        155       7962
Swap:          601          0        601

Bingo! here is your increased SWAP.

To make this change permanent add the line in your etc/fstab
/u01/swapfile swap swap defaults 0 0

Oracle Application 11.5.10 Installation Part#2

Rapid install is used to install Oracle Applications on any machine. With Rapid Install, you can perform these operations:

• Install a new, fully configured Oracle Applications system, including the latest certified Oracle Applications technology stack and all patches, mini-packs, family packs, and other updates available at the time of this release.
• Lay down the file system and configure server processes for an upgraded system
• Install a new database tier or application tier technology stack

Rapid Install employs a wizard that presents the screen flow associated with one of these operations. On the wizard screens, you enter configuration values for your system, and save them in a file (config.txt). When you run Rapid Install, you point it to that file so that it can use the parameters as it performs tasks such as creating the Oracle Applications file system, installing a fresh database, registering products, managing NLS requirements, configuring port connections, and creating and running the start and stop scripts for the database and listeners.

The main Rapid Install engine is AutoConfig. This tool simplifies and standardizes the management of your system configuration. AutoConfig uses the values in the configuration file to set up your system parameters, and then stores that information in a system-specific context file. At any time after the initial installation, you can change these values and run an AutoConfig script to populate the configuration files with the new values (using the Oracle Applications Manager AutoConfig tool). AutoConfig is delivered with and required for a new installation of Release 11.5.10.

Installing New Systems

With Rapid Install, you can set up a new installation using either a complete set of your own system-specific parameters, or a combination of a few key system-specific parameters and the Rapid Install default parameters. Both types (system-specific or express) offer the option of installing either a fresh database — one that is fully configured but contains no transaction data — or a Vision Demo database — one that contains transaction data for a fictitious company to use for training or demonstration purposes.

Upgrading an Existing System

As part of a system upgrade, you enter configuration parameters in the Rapid Install wizard and run Rapid Install as one of the pre-upgrade tasks (performed prior to running AutoUpgrade). It uses the parameters to lay down the file system and install the new technology stack. You must also migrate or upgrade your existing database to Oracle9i as one of the pre-upgrade tasks

Steps before starting Rapid Install

You must follow the steps in this section before you begin the installation. It is also important to be familiar with the other documentation referenced in this section.

Review Installation Plan and Documentation

Rapid Install handles the details of the installation or upgrade based on the information you enter on the Rapid Wizard screens. It’s a good idea to collect and review all the information necessary for responding to the wizard before you begin.

Create Login Accounts

You must set up user login accounts for the installation of both the database tier and the application tier file systems. The way you create login accounts differs somewhat between UNIX users and Windows users.

Install Java Development Kit (JDK)

This release of Oracle Applications requires JDK 1.4.2. Rapid Install installs it automatically on Solaris, Linux, and Windows operating systems. If your installation is on another platform, you must download and install JDK before you continue with the installation or upgrade.

Set Up the Stage Area

As preparation for running Rapid Install, you run a Perl script that creates the install directory and copies the contents of the Release 11i software bundle to the appropriate place in the file system.

Your installation software comes in DVD format. The individual disks included in the

Release 11i software bundle are labeled as follows:

• Start Here - Disk 1
• APPL_TOP - Disk n
• RDBMS - Disk n
• Tools - Disk n
• Databases - Disk n

If you are an NLS customer, you should also have the NLS Supplement - Disk n software for each language (in addition to American English) you plan to install. You should order the NLS Supplement software and have it available before you begin the installation. Rapid Install requires this language-specific software to run to completion.

The stage area created by adautostg.pl looks like this: a top-level directory , with subdirectories startCD, oraApps, oraDB, oraiAS, oraAppDB, and oraNLS/ (only if required).

Starting Rapid Install

Once the stage directory is created, start Rapid Install as described in the following section.

UNIX:

$ cd /u01/Stage11i/startCD/Disk1/rapidwiz

$ ./rapidwiz


Windows:

C:\> f:

F:\> cd Stage11i\startCD\Disk1\rapidwiz

F:\Stage11i\startCD\Disk1\rapidwiz> rapidwiz.cmd