Tag Archives: Cleanup

How to Remove an Oracle E-Business Suite Release 12.x Windows Environment

Posted by on September 21, 2011 No comments

How to Remove an Oracle E-Business Suite Release 12.x Windows Environment

The procedure described in this document (Note 567507.1 on Oracle Metalink) lists the steps you must take to remove an E-Business Suite R12 environment or environments from a Windows system.

Step 1. Back up the System and Windows Registry

Refer to Microsoft Article ID 326216:  How to use the backup feature to back up and restore data in Windows Server 2003

Step 2. Alter the Windows Registry

Delete the relevant Oracle components from the Windows registry, as follows.

To delete all Oracle environments on the system:

* Launch the Registry Editor.
* Navigate to the HKEY_LOCAL_MACHINESoftware key.
* Select the Apache Group subkey and delete it.
* Select the Oracle subkey and delete it.
* Navigate to the HKEY_LOCAL_MACHINESystemCurrent Control SetServices.
* Carefully select and delete each service beginning with Oracle.  For example, delete “OraclePROD_<nodename>_ToolsASControl”.
* When you are finished, exit the Registry Editor.

Step 3. Alter Environment Settings

Complete these steps to delete Oracle parameters from the environment.

Navigate to the Environment Variables editing screen according to your system setup.  For example, right-click My Computer and select Properties. From the Advanced tab, click the Environment Variables button.

To remove all Oracle environments from the system:

Select the following system variable if created during the failed installation, and delete it: PERL5LIB.
Select the Path variable, but do not delete it.  Carefully edit it and remove any component with “Oracle” in the name, or that otherwise references the failed install. For example, delete “e:oraclePRODdbtech_st10.2.0bin;”.
Save and exit System Properties.

Step 4. Clean up the Program Menu

Launch the Program menu (Start -> Programs). Delete all Oracle programs groups.

Step 5. Restart your Machine

Step 6. Delete the Oracle Filesystem

Step 7. Delete Programs and Oracle Inventory Entries

To delete the inventory associated with a specific instance:

* Start the Oracle Universal Installer using: Start >> All Programs >> Oracle-<SID>_db102_RDBMS>>Oracle Installation Products>>Universal Installer
* Select Installed Products
* Enable “Show empty homes”

Deinstall the entries in the global inventory associated with the Oracle Applications R12 instance which you removed earlier. For example, for the PROD instance, you would delete:
* * RDBMS ORACLE HOME (e.g. “PROD_DB__oracle_PROD_db_tech_st_10_2_0″)
* * 10gAS ORACLE HOME (e.g.”PROD_WEBOH__oracle_PROD_apps_tech_st_10_1_3”)
* * Developer 10g ORACLE HOME (for example, “PROD_TOOLS__oracle_PROD_apps_tech_st_10_1_2”)
* Exit the Universal Installer

To delete the files associated with all Oracle environments on the system:

* Open a command window and navigate to the C:Program Files directory.
* Delete the Oracle subdirectory.
* If your Oracle Inventory directory was not C:Program FilesOracleInventory and was therefore not deleted in the previous step, locate it and delete it.

Reference:

How to Remove an Oracle E-Business Suite Release 12.x Windows Environment [ID 567507.1]

Cleaning Up the Environment Management Hub

Posted by on January 15, 2009 No comments

How to Clean Up the Environment Management Hub

Problem:

Previous attempt to clean up the EM Hub was not completely successful, the previous Agent IDs (1 & 3) still appear.

Solution:

1. Stop the PSEM Agents on gldbase and glwebapp.

2. Exit the Change Assistant

3. Stop the web server. The application server and batch server may also be stopped.

For Agents, Viewer and Change Assistant:

Delete the files in the following directories:
• Under PS_HOMEPSEMAgent for Agents
• Under PS_HOMEPSEMViewer for the Viewer
• Under the Change Assistant directory for Change Assistant

envmetadata/PersistentStorage/
envmetadata/scratchpad
envmetadata/data/ids/
envmetadata/transactions/ (if it exists)
envmetadata/data/search-results.xml (just for Agents and CA)

For HUB:

Delete the files in the following directories:
• Under PS_HOMEwebservfsdmoapplicationspeoplesoftPSEMHUB

PSEMHUBenvmetadataScratchpad
PSEMHUBenvmetadataPersistentStorage
PSEMHUBenvmetadatatransactions (if it exists)
PSEMHUBenvmetadatadata*.* (files and directories.don’t delete the data directory itself)

Problem:

After cleaning up Environment Management Hub using the above method, the old Peer IDs still appear in the PSEM Viewer.

Solution:

Bounce the web server (fsdmo-PIA service) on glwebapp.

Reference:

E-CA Refresh and Clean Up of the Environment Management Hub (PSEMHUB) data (Doc ID 622874.1)

Resolving Non-Starting Servers

Posted by on July 18, 2006 No comments

Problem: In Oracle Applications Manager, in Applications Dashboard, on the database is appearing up. The remaining servers are shown as down.

Solution:

  1. Tried stopping and restarting the entire system (stopPROD.sh and startPROD.sh).

Executing service control script:

/emca/PROD/prodcomn/admin/scripts/PROD_linux-blade/adrepctl.sh stop

script returned:

****************************************************
You are running adrepctl.sh version 115.29
Reports Server for PROD is already stopped.
adrepctl.sh: exiting with status 2
.end std out.
.end err out.
****************************************************
Executing service control script:
/emca/PROD/prodcomn/admin/scripts/PROD_linux-blade/adfmcctl.sh stop
script returned:
****************************************************
You are running adfmcctl.sh version 115.16
forms load balancing client for PROD already stopped.
adfmcctl.sh: exiting with status 2
.end std out.
.end err out.
****************************************************
Executing service control script:
/emca/PROD/prodcomn/admin/scripts/PROD_linux-blade/adfmsctl.sh stop
script returned:
****************************************************

Subject:  Summary of Possible Reasons and Solutions for the Problem Where All Concurrent Requests Stuck in Pending Phase Doc ID:  Note:182154.1

2.  When shutting down the concurrent manager are there any FNDLIBR processes still running at the OS level?   If so, do a kill -9 on them.  Then restart the concurrent manager.

Tried this, but CM stopped successfully with no need to kill FNDLIBR.

3.  Rebuild the concurrent manager views.  As applmgr run the following from the OS:

This is non-destructive.

Concurrent Manager views can be rebuild by running the following command at the command line:

Ensure that concurrent manager is shutdown.

FNDLIBR FND FNDCPBWV apps/apps SYSADMIN 'System Administrator' SYSADMIN

Restart the concurrent manager.

Executed the above, but no change.

Executed the code:

update fnd_concurrent_queues
set control_code = 'A'
where concurrent_queue_name = 'FNDCRM';
commit;
SQL> update fnd_concurrent_queues
2  set control_code = 'A'
3  where control_code = 'N'
4  /
SQL> select control_code, target_node, concurrent_queue_name
2  from fnd_concurrent_queues
3  where control_code = 'N'
4  /
C TARGET_NODE                    CONCURRENT_QUEUE_NAME
- ------------------------------ ------------------------------
N                                FNDCRM
N                                FNDSCH
N                                STANDARD
N                                PODAMGR
N                                RCVOLTM
N                                PASMGR
N                                INVMGR
N                                INVTMRPM
N                                IEU_SH_CS
N                                IEU_WL_CS
N                                OAMCOLMGR
C TARGET_NODE                    CONCURRENT_QUEUE_NAME
- ------------------------------ ------------------------------
N                                OAMGCS_LINUX-BLADE

updated /etc/hosts file:

[applmgr@linux-blade etc]$ cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1       localhost.localdomain   localhost
128.x.x.x      linux-blade.domainname  linux-blade
SQL> create table fnd_concurrent_queues_vseeram
2        as select * from fnd_concurrent_queues;