Archive

Archive for September, 2009

to calculate the required network bandwidth based on the redo generation rate on the primary database

September 23rd, 2009 sam No comments

The formula used (assuming a conservative TCP/IP network overhead of 30%) for calculating the network bandwidth is :

Required bandwidth = ((Redo rate bytes per sec. / 0.7) * 8) / 1,000,000 = bandwidth in Mbps

Let us assume the redo rate is a 500 KB/sec.

Required bandwidth = ((Redo rate bytes per sec. / 0.7) * 8) / 1,000,000 = bandwidth in Mbps
Required bandwidth = ((512000/0.7) * 8) /1,000,000
Required bandwidth = 4.85 Mbps

Categories: DBA Tags:

Remove Portal Schema from 11i

September 23rd, 2009 sam No comments

You may remove Oracle Portal 3.0.9 only if you are not using Oracle Portal with
E-Business Suite 11i or if you have migrated existing Oracle Portal 3.0.9 functionality
to Oracle Portal 10g .
It is recommended that the removal of Oracle Portal 3.0.9 be done only after the
migration to Oracle Portal 10g. To remove Oracle Portal 3.0.9 objects from your
E-Business Suite 11i database, follow the steps below.
1. Remove Oracle Portal 3.0.9 dependencies from schema CTXSYS
Download Portal patch 3497474 and follow the instructions in the Readme.
This patch removes Portal 3.0.9 dependencies from schema CTXSYS.

2. Remove Oracle Portal 3.0.9 dependencies from the Oracle Applications schema
Download Oracle Applications patch 43695277 and follow the instructions in the Readme.
This patch removes Portal 3.0.9 dependencies from the Oracle Applications schema.

3. Deinstall Oracle Portal 3.0.9 schemas from your E-Business Suite 11i database
Deinstall the Oracle Portal 3.0.9 and Oracle Login Server schemas in the database using the
Oracle Portal Configuration Assistant.
3.1. Run the shell script $IAS_ORACLE_HOME/assistants/opca/launch.sh to
start the Oracle Portal Configuration Assistant.
Window Step 1 of 6: Installation Options appears.
Click the option to Deinstall Oracle Portal and the Login Server.
3.2. Follow the instructions on the remaining screens to complete the
deinstallation.
3.3. Verify Oracle Portal and Oracle Login Server schemas have been removed.
Start SQL*Plus and verify that no rows are returned from the following query:
% sqlplus
SQL> connect system/<system_password> as sysdba
SQL> select username from all_users
SQL> where username like ‘PORTAL%’
SQL> /
You have successfully removed Oracle Portal 3.0.9 from your E-Business Suite 11i database.

Categories: Uncategorized Tags:

Perosnalize Login in EBS

September 22nd, 2009 sam No comments

1. Attributes of the login page
It is possible to control the display of some attributes of the login page, for instance user name or password hints, language switchers, forgot password link, corporate policy message, etc.
For this, you need to set the profile option ‘Local Login Mask’ (FND_SSO_LOCAL_LOGIN_MASK) with a number being the sum of the mask values described in the table below:

Description Mask value
Hint for Username (USERNAME_HINT) 01
Hint for Password (PASSWORD_HINT) 02
Cancel button (CANCEL_BUTTON) 04
Forgot Password link (FORGOT_PASSWORD_URL) 08
Registration link (REGISTER_URL) 16
Language Images (LANGUAGE_IMAGES) 32
Corporate Policy Message (SARBANES_OXLEY_TEXT) 64
* For instance the value 32 (default) displays only the language icons and value 127 will show all the attributes on the page.

* The change takes effect immediately after re-login to E-Business Suite.

2. Message texts
It is possible to modify or add text on the login page by changing the value of some messages.
The following table shows the related messages and their default value:
Description Default value
FND_SSO_WELCOME Login
FND_SSO_EBIZ_SUITE E-Business Suite
FND_SSO_COPYRIGHT_TEXT Copyright (c) 2007, Oracle. All rights reserved.
FND_SSO_SARBANES_OXLEY_TEXT Corporate Policy Message

To change the value of a message:
1. Go to “Application Developer” responsibility
2. Select “Messages” from the menu
3. Query  the message name and then enter your message text in the
“Current Message Text” field
4. Save changes and exit
5. Clear cache and bounce Apache to see the change

* Note that some messages can be used elsewhere that in the login page and can be updated by a patch
* If you want to change also the default branding ‘E-Business Suite’ on other pages, to match the text on the login page (defined by FND_SSO_EBIZ_SUITE message), then follow the steps below:
a. Login with System Administrator responsibility
b. Navigate: Application —> Function
c. Query the function ‘FWK_HOMEPAGE_BRAND’
d. Replace the value of the ‘User Function Name’ with the desired text
c. Logout and login to see the change (you shouldn’t need to clear caches and bounce apache)

* The ‘FND_SSO_SARBANES_OXLEY_TEXT’ message is only displayed when the mask
value 64 is added to the profile option ‘Local Login Mask’.
3. Corporate branding logo
The Oracle logo is displayed on various E-Business Suite pages and can be changed by setting the ‘Corporate Branding Image for Oracle Applications’  (FND_CORPORATE_BRANDING_IMAGE) profile option to the full path name of an image file (.gif) that contains your corporate image.
However it is not possible to use this method for AppsLocalLogin.jsp since it is hard coded with the Oracle logo image file ‘FNDSSCORP.gif’.
The non supported solution consists in:
1. Go to the $OA_HTML directory
2. Backup the AppsLocalLogin.jsp file
3. Copy your own corporate branding image under $OA_MEDIA directory
4. Edit the AppsLocalLogin.jsp file :

from :
ImageBean imgBean1 = new ImageBean(“/OA_MEDIA/FNDSSCORP.gif”, FND_ORACLE_LOGO);
to :
ImageBean imgBean1 = new ImageBean(“/OA_MEDIA/<your image file name>”, FND_ORACLE_LOGO);
5. Clear caches and bounce Apache to see the change

4. Other modifications

AppsLocalLogin.jsp being a Java Server Page you can change the HTML or Java code (for instance with JDeveloper), create you own messages in the Messages Dictionary thru AOL responsibility, etc., if you want to add other customizations. This is considered a customization and thus not supported by Oracle. If you apply patches replacing AppsLocalLogin.jsp the file will be overwritten.

Categories: Uncategorized Tags:

Concurrent Manager Scripts

September 22nd, 2009 asra No comments

Few Oracle Applications DBAs understand that sophisticated data dictionary queries can be run to reveal details about the workings within each Concurrent Manager. Oracle provides several internal tables that can be queried from SQL*Plus to see the status of the concurrent requests, and the most important are FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS.

Oracle supplies several useful scripts, (located in $FND_TOP/sql directory), for monitoring the concurrent managers:

afcmstat.sql

Displays all the defined managers, their maximum capacity, pids, and their status.

afimchk.sql

Displays the status of ICM and PMON method in effect, the ICM’s log file, and determines if the concurrent manger monitor is running.

afcmcreq.sql

Displays the concurrent manager and the name of its log file that processed a request.

afrqwait.sql

Displays the requests that are pending, held, and scheduled.

afrqstat.sql

Displays of summary of concurrent request execution time and status since a particular date.

afqpmrid.sql

Displays the operating system process id of the FNDLIBR process based on a concurrent request id. The process id can then be used with the ORADEBUG utility.

afimlock.sql

Displays the process id, terminal, and process id that may be causing locks that the ICM and CRM are waiting to get. You should run this script if there are long delays when submitting jobs, or if you suspect the ICM is in a gridlock with another oracle process.

Categories: Apps DBA Tags: