The following are the steps to License a product through License Manager
1. Login to Oracle Applications Manager
2. Click on Site Map (The link near Applications Dashboard link)
3. Click on License Manager
4. Under License heading, click Products
5. Click on blue plus icon of More options
6. Click on the radio button: License Applications Product
7. Click on continue button
8. You'll get a list of all the individual products
9. Check the box on the left of the product you want to license
10. Click on Next button
11. Click on Submit button
12. You'll get a message: Sucessfully licensed the selected product(s). Click OK
13. Logout and login the applications and check the enables products functionality
Tuesday, December 9, 2008
Monday, November 10, 2008
Oracle EBS R12 12.0.6 Release update pack (RUP6) now available
The Oracle E-Business Suite Release 12 12.0.6 Release Update Pack (RUP6) is now available for download from Metalink through patch number 6728000
Thursday, November 6, 2008
Files that can be safely deleted from OMS home to save disk space
Logfiles, can occupy considerable amount of disk space and can sometimes, affect of the disk I/O performance. The following files can be safely deleted from the OMS home periodically to save disk space.
After stopping the GRID Control processes, the traces/logs can be removed from the following
directories:
$ORACLE_HOME/oms10g/sysman/log/*.* directory
$ORACLE_HOME/oms10g/cfgtoollogs/*.* directory
$ORACLE_HOME/oms10g/opmn/logs/*.* directory
$ORACLE_HOME/oms10g/dcm/logs/*.* directory
$ORACLE_HOME/oms10g/Apache/Apache/logs /*.* directory
$ORACLE_HOME/oms10g/webcache/logs/*.* directory
$ORACLE_HOME/oms10g/j2ee/OC4J_EM/log/OC4J_EM_default_island_1/*.* directory
$ORACLE_HOME/oms10g/j2ee/OC4J_EMPROV_default_island_1/*.* directory
$ORACLE_HOME/agent10g/sysman/log//*.* directory
These logs and traces are created again when the application is started.
After stopping the GRID Control processes, the traces/logs can be removed from the following
directories:
$ORACLE_HOME/oms10g/sysman/log/*.* directory
$ORACLE_HOME/oms10g/cfgtoollogs/*.* directory
$ORACLE_HOME/oms10g/opmn/logs/*.* directory
$ORACLE_HOME/oms10g/dcm/logs/*.* directory
$ORACLE_HOME/oms10g/Apache/Apache/logs /*.* directory
$ORACLE_HOME/oms10g/webcache/logs/*.* directory
$ORACLE_HOME/oms10g/j2ee/OC4J_EM/log/OC4J_EM_default_island_1/*.* directory
$ORACLE_HOME/oms10g/j2ee/OC4J_EMPROV_default_island_1/*.* directory
$ORACLE_HOME/agent10g/sysman/log//*.* directory
These logs and traces are created again when the application is started.
Wednesday, November 5, 2008
How To Verify if Autoconfig is Enabled on 11.5.x
There exists a script under /bin named adcfginfo.sh (adcfginfo.cmd on Windows) which can be used to check if autoconfig is enabled in an instance.
Usage:
adcfginfo.sh [help]
adcfginfo.sh contextfile= [show=]
[log=] [appspass=]
This script generates a logfile under $APPL_TOP/admin/$CONTEXT_NAME/log when it is run.
another method to find out if an instance is autoconfig enabled is to open adovars or the environment file inder and check the file's header. If the instance was autoconfig enabled, the file would contain the following header.
############################################################################
#
# AutoConfig automatically generates this file. It will be read and
# overwritten. If you were instructed to edit this file, or if you are not
# able to use the settings created by AutoConfig, refer to Metalink
# document 165195.1 for assistance.
#
############################################################################
One thing to note is that if a file containing this header is manually edited, it is no longer officially autoconfig enabled.
Usage:
adcfginfo.sh [help]
adcfginfo.sh contextfile=
[log=
This script generates a logfile under $APPL_TOP/admin/$CONTEXT_NAME/log when it is run.
another method to find out if an instance is autoconfig enabled is to open adovars or the environment file inder
############################################################################
#
# AutoConfig automatically generates this file. It will be read and
# overwritten. If you were instructed to edit this file, or if you are not
# able to use the settings created by AutoConfig, refer to Metalink
# document 165195.1 for assistance.
#
############################################################################
One thing to note is that if a file containing this header is manually edited, it is no longer officially autoconfig enabled.
Thursday, October 30, 2008
IAS console does not show new 10.1.4.0.1 version after upgrade from 10.1.2.0.2:
This is a problem on all platforms. Oracle says that this is expected behavior. The reason for this being, that OID, SSO and OCA have been upgraded to 10.1.4.0.1 but the core 10g application server components still remain at 10.1.2.0.2. This is reported by bug 6125035. The work around for this is to manually change the version number in the $ORACLE_HOME/config/ias.properties file to 10.1.4.0.1 and bounce iasconsole.
How to find the Oracle XML Publisher (BI Publisher) version in EBS 11i & 12
You can find out the XML Publisher version either from the output of the report or from the MetaInfo.class.
strings $OA_JAVA/oracle/apps/xdo/common/MetaInfo.class|grep -i 'XML Publisher'
strings $OA_JAVA/oracle/apps/xdo/common/MetaInfo.class|grep -i 'XML Publisher'
Steps to De-Install the EM 10g Agent on Windows and Unix
Before uninstalling the Agent, remove the targets from repository associated with the agent:
1. From Grid Control Console remove all targets for the host.
2. Check remove was successfully:
Grid Control Console -> Setup -> Management Services and Repository tab ->In general section click on Deleted Targets ->
The time delete completed must have a date, if not wait 10 minutes.If it still does not have a date, place a check next to the target and click on force delete.
3. After verifying that the targets were deleted, stop the Management Agent.
Go back to the Grid Control UI and remove the host.
Remove the Agent. Check to confirm it was removed successfully.
Click on force delete if necessary.
De-Install the Agent Using OUI
These steps can be performed for an agent that has been installed using any method (agent download script, agent push or manual install using OUI)
For agent on Linux (or any unix flavor like HP,solaris, AIX etc)
1. Stop the agent by running/emctl stop agent
2. Run:/oui/bin/runInstaller
3. The following screen should come up:
4. Select “Deinstall Products” and then select the product you need to de-install.
Click on “Remove” and wait till it completes.
For agent on Windows:
1. Stop the agent first by running:/emctl stop agent
2. Then run setup.exe from/oui/bin
3. The following screen should come up
4. Select “Deinstall Products” and then select the product you need to de-install.
De-Install the Agent Manually
For the Windows Platform:
1. Start the registry editor .From the local machine command prompt , type "regedit"
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Oracle remove the respective agent entry
For example :-
Select and remove HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\Key_agent10g
2.1 Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services. Delete the agent service
2.2 Go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet2\Services. Delete the agent service.
Close the registry editor.
Note: On RAC setup , make sure that the Agent service is deleted on both the nodes . There is no need to stop this "OracleRemExecService" service on Rac as this service get created as part of CRS and database install
3.Clean Up Environment Settings
On Windows NT: Choose Start > Settings > Control Panel > System > Environment.
On Windows 2000 and Windows XP: Choose Start > Settings > Control Panel > System > Advanced > Environment Variables.
In the System Variables section, click the variable PATH in order to modify the value.
Delete the agent home - Click Apply and then click OK.
If there is a CLASSPATH variable under "System Variables", delete the path expressions in the variable that contains the ORACLE_HOME to be removed or some location underneath.Close the Control Panel window.
4. Re-boot the Box
After rebooting you can start the fresh Agent installation
Note- On RAC re-boot both the Nodes
Post-Install Verification
1. Verify that the directory where the agent was previously installed has been removed along with all files.
2. Remove any references to the previously installed agent from the environment settings such as PATH.
3. Confirm that the agent has been removed from the repository:
Log into the repository database via sqlplus as SYSMAN and run the following:
exec mgmt_admin.cleanup_agent(':1830');
1. From Grid Control Console remove all targets for the host.
2. Check remove was successfully:
Grid Control Console -> Setup -> Management Services and Repository tab ->In general section click on Deleted Targets ->
The time delete completed must have a date, if not wait 10 minutes.If it still does not have a date, place a check next to the target and click on force delete.
3. After verifying that the targets were deleted, stop the Management Agent.
Go back to the Grid Control UI and remove the host.
Remove the Agent. Check to confirm it was removed successfully.
Click on force delete if necessary.
De-Install the Agent Using OUI
These steps can be performed for an agent that has been installed using any method (agent download script, agent push or manual install using OUI)
For agent on Linux (or any unix flavor like HP,solaris, AIX etc)
1. Stop the agent by running
2. Run:
3. The following screen should come up:
4. Select “Deinstall Products” and then select the product you need to de-install.
Click on “Remove” and wait till it completes.
For agent on Windows:
1. Stop the agent first by running:
2. Then run setup.exe from
3. The following screen should come up
4. Select “Deinstall Products” and then select the product you need to de-install.
De-Install the Agent Manually
For the Windows Platform:
1. Start the registry editor .From the local machine command prompt , type "regedit"
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Oracle remove the respective agent entry
For example :-
Select and remove HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\Key_agent10g
2.1 Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services. Delete the agent service
2.2 Go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet2\Services. Delete the agent service.
Close the registry editor.
Note: On RAC setup , make sure that the Agent service is deleted on both the nodes . There is no need to stop this "OracleRemExecService" service on Rac as this service get created as part of CRS and database install
3.Clean Up Environment Settings
On Windows NT: Choose Start > Settings > Control Panel > System > Environment.
On Windows 2000 and Windows XP: Choose Start > Settings > Control Panel > System > Advanced > Environment Variables.
In the System Variables section, click the variable PATH in order to modify the value.
Delete the agent home - Click Apply and then click OK.
If there is a CLASSPATH variable under "System Variables", delete the path expressions in the variable that contains the ORACLE_HOME to be removed or some location underneath.Close the Control Panel window.
4. Re-boot the Box
After rebooting you can start the fresh Agent installation
Note- On RAC re-boot both the Nodes
Post-Install Verification
1. Verify that the directory where the agent was previously installed has been removed along with all files.
2. Remove any references to the previously installed agent from the environment settings such as PATH.
3. Confirm that the agent has been removed from the repository:
Log into the repository database via sqlplus as SYSMAN and run the following:
exec mgmt_admin.cleanup_agent('
Subscribe to:
Posts (Atom)