Rename or Move a Datafiles to Different location

***TO MOVE THE DATAFILES TO DIFFERENT LOCATION/PARTITION***

________________________________________________________________________________________________

Scenario1: RENAME AND OR MOVE DATAFILE(S) WITH THE DATABASE SHUT DOWN

________________________________________________________________________________________________

1. If the database is up, shut it down.

2. Copy the datafile to the new name/location at operating system level.

3. Mount the database.

Ø  STARTUP MOUNT

This command will read the control file but will not mount the datafiles.

4. Rename the file inside Oracle.

Ø  ALTER DATABASE RENAME FILE

'/FULL_PATH_OF_OLD_LOCATION/AND_DATAFILE_NAME.DBF'

TO

'/FULL_PATH_OF_NEW_LOCATION/AND_DATAFILE_NAME.DBF';

Do this for all the datafiles that were renamed or moved at the operating system level.

5. Open the database.

Ø  ALTER DATABASE OPEN;

6. Query v$dbfile to confirm that the changes made were correct.

Ø  SELECT * FROM V$DBFILE;

7. Remove the datafile(s) from the old location at the operating system level.

_____________________________________________________________________________________________

Scenario 2:  RENAME AND OR MOVE A LOGFILE

_____________________________________________________________________________________________

1. Shutdown the database.

2. Copy the logfile to the new name/location at operating system level.

3. Mount the database.

Ø  STARTUP MOUNT

4. Rename the file.

Ø   ALTER DATABASE RENAME FILE

      '/FULL_PATH_OF_OLD_LOCATION/AND_REDO_LOG_NAME.LOG'

       TO

      '/FULL_PATH_OF_NEW_LOCATION/AND_REDO_LOG_NAME.LOG';

5. Open the database.

Ø   ALTER DATABASE OPEN;

6. Remove the logfile(s) from the old location at the operating system level.

________________________________________________________________________________________________________

Scenario3: MOVE DATAFILE ONLINE or OPEN STATE or MOVE DATAFILE(S) WITH THE DATABASE OPEN

_________________________________________________________________________________________________________________________

Note: 

Datafiles can be renamed or moved while the database is open. However, the tablespace must be made READ-ONLY. This will allow users to select from the tablespace, but prevents them from doing inserts, updates, and deletes. The amount of time the tablespace is required to be read only will depend on how large the datafile(s) are and how long it takes to copy the datafile(s) to the new location. 

      Making the tablespace read only freezes the file header, preventing updates from being made to the file header. Since this datafile is then at a read only state, it is possible to copy the file while the database is open.

To do this you must follow these steps:

1. Determine how many datafiles are associated with the tablespace.

Ø   SELECT FILE_NAME, STATUS FROM DBA_DATA_FILES

WHERE TABLESPACE_NAME = '<YOUR_TABLESPACE_NAME>';

2. Make sure that all datafiles returned have the status AVAILABLE.

3. Make the tablespace is read only.

Ø   ALTER TABLESPACE <YOUR_TABLESPACE_NAME> READ ONLY;

4. Make sure that the tablespace is defined as read only in the data dictionary.

Ø   SELECT TABLESPACE_NAME, STATUS FROM DBA_TABLESPACES

WHERE TABLESPACE_NAME = '<YOUR_TABLESPACE_NAME>';

TABLESPACE_NAME              STATUS

------------------------------ ------------------------

<YOUR_TABLESPACE_NAME> READ ONLY

5. Copy the datafile(s) to the new location using the operating system copy command. Once the datafile(s) have been copied to the new location compare the sizes of the datafiles. Make sure that the sizes match.

NOTE:

The same method could be used to rename a datafile as a kind of in-place copy.

However, on Windows that fails with a message like:

"Cannot rename USERS01: It is being used by another person or program.

Close any programs that might be using the file and try again."

6. Once the datafiles have been copied to the new location alter the tablespace offline.

Ø    ALTER TABLESPACE <YOUR_TABLESPACE_NAME> OFFLINE;

·          At this point the tablespace is not accessible to users.

7. Once the tablespace is offline you will need to rename the datafile(s) to the new location. This updates the entry for the datafile(s) in the controlfile.

Ø   ALTER DATABASE RENAME FILE

           '/FULL_PATH_OF_OLD_LOCATION/AND_DATAFILE_NAME.DBF'

          TO

        '/FULL_PATH_OF_NEW_LOCATION/AND_DATAFILE_NAME.DBF';

·          You will need to do this for all datafiles associated with this tablespace.

You can use the ALTER TABLESPACE ... RENAME DATAFILE syntax as well.

8. Once the alter database statement has been processed for the datafile(s) you can bring the table space online.

Ø  ALTER TABLESPACE <YOUR_TABLESPACE_NAME> ONLINE;

9. After you bring the tablespace back online you can make the tablespace read/write again.

Ø   ALTER TABLESPACE <YOUR_TABLESPACE_NAME> READ WRITE;

10. You can check the status of the tablespace to make sure it is read/write.

You can also verify that the controlfile has been updated by doing the following:

Ø  ALTER DATABASE BACKUP CONTROLFILE TO TRACE;

This will produce a readable copy of the contents of your controlfile which will be placed in your user_dump_dest directory.

Optionally, you can query V$DATAFILE, which gets information from the controlfile as well.

11. Remove the datafile(s) from the old location at the O/S level.

To Clear the IPC Resources

Clear the IPC Resources using TUXEDO Command

Steps to clean IPC resources:

1) Identify the absolute path to PSTUXCFG file:
- it should be [PS_HOME]/appserv/[DOMAIN_NAME]/PSTUXCFG
- can also be found in psappsrv.ubb file, *MACHINES section and look for TUXCONFIG value.
Ex. TUXCONFIG="D:\PS\appserv\CRM\PSTUXCFG"

2) List all IPC resources used by the BEA Tuxedo system:
- open a command prompt line and go to [TUX_HOME]/bin
- run the following command:
"tmipcrm -n [TUXCONFIG]" (Ex. tmipcrm -n D:\PS\appserv\CRM\PSTUXCFG)

Result:
----------------------------------------------------------------------------------
Looking for IPC resources in TUXCONFIG file D:\PS\appserv\CRM\PSTUXCFG
The following IPC resources were found:

  Message Queues:
        2049
         ...
  Shared Memory:
        151
         ...
  Semaphores:
        17409
----------------------------------------------------------------------------------
Note: This command will not work unless you have set the TUXCONFIG environment variable correctly or specified the appropriate TUXCONFIG file on the command line.

3) Clean/remove all IPC resources used by the BEA Tuxedo system:
- open a command prompt line and go to [TUx_HOME]/bin
- run the following command:
"tmipcrm -y [TUXCONFIG]" (Ex. tmipcrm -y D:\PS\appserv\CRM\PSTUXCFG)

Result:
----------------------------------------------------------------------------------
Looking for IPC resources in TUXCONFIG file D:\PS\appserv\CRM\PSTUXCFG
The following IPC resources were found:
  Message Queues:
        2049
         ...
  Shared Memory:
        151
         ...
  Semaphores:
        17409
         ...
Removing IPC resources ...

WARN: removal of msg id 0 failed
done!

OEM11g & PEOPLESOFT 8.51 PLUG-IN INSTALATION GUIDE

OEM11g & PEOPLESOFT 8.51 PLUG-IN INSTALLATION GUIDE

Pre-Requisites Software’s List:-

OEM Sever requisites:-

Windows 32bit Server:-

1.       Oracle database 11gR1 32bit (Or Above version)

2.       Weblogic11gR1  10.3.2

3.       Oracle® Enterprise Manager Grid Control 11g Release 1 (11.1.0.1.0)

4.       Oracle Management Agent (11.1.0.1.0) for Microsoft Windows x86.

5.       PeopleSoft Environment Management Plug-in for Oracle Enterprise Manager (Version: 8.51.0.1.0)

Windows 64bit Server:-

1.       Oracle database 11gR1 (Or Above version)

2.      Java SE Development Kit 6u18 64 bit

3.       Oracle Web Logic Server 11gR1 (10.3.2) - Package Installer (Generic)

4.        Oracle® Enterprise Manager Grid Control 11g Release 1 (11.1.0.1.0) x86

5.       Oracle Management Agent (11.1.0.1.0) for Microsoft Windows x86-64

6.       PeopleSoft Environment Management Plug-in for Oracle Enterprise Manager (Version: 8.51.0.1.0)

Linux 32 bit Server:-

1.       Oracle Database 11g Release 2 (11.2.0.1.0) Linux x86

2.      Oracle Web Logic Server 11g Release 1 (10.3.2) Linux x86

3.      Oracle Enterprise Manager Grid Control 11g Release 1 (11.1.0.1.0) Linux x86

4.      Oracle Management Agent (11.1.0.1.0) for Linux x86

5.       PeopleSoft Environment Management Plug-in for Oracle Enterprise Manager (Version: 8.51.0.1.0)

Linux 64 Bit Server:-

     

1.       Oracle database 11gR1 (Or Above version)

2.       Oracle Database 11g Release 2 for Linux 64-bit

3.      Java SE Development Kit 6u18 64 bit

4.      Oracle Web Logic Server 11gR1 (10.3.2) - Package Installer (Generic)

5.      Oracle Enterprise Manager Grid Control 11g Release 1 Linux x86-64.

6.      Oracle Management Agent (11.1.0.1.0) for Linux x86-64

7.       PeopleSoft Environment Management Plug-in for Oracle Enterprise Manager (Version: 8.51.0.1.0)

** N.B : Web logic 10.3.2 is mandatory for OMS11g installation otherwise OMS Configuration could be failed. Same configuration we can use in case of windows 64 bit OS.

Installation Steps:

OEM REPOSITORY CREATION:

1.      Install Oracle Database 11g software.

2.      Create OEM database repository (new database).

3.      Configure the listener and tnsaname.ora files

4.      Perform the following changes in repository database:-

SQL> conn sys/<password>@<SID> as sysdba
SQL> alter SYSTEM SET open_cursors = 500 SCOPE=BOTH;
SQL> alter system set "_optimizer_distinct_agg_transform"=false scope=spfile;
SQL> alter system set log_buffer=10485760 scope=spfile;
SQL> alter system set processes = 500 scope=spfile;
SQL> alter system set session_cached_cursors=200 scope=spfile;
SQL > alter database datafile <location datafile> resize 200M;

5.      Check the table space  TEMP and UNDOTBS   auto extensible or not

SQL> select count(*) from  dba_temp_files where tablespace_name='TEMP' and AUTOEXTENSIBLE  <> 'YES';

SQL > select count(*) from dba_data_files where tablespace_name='UNDOTBS' and AUTOEXTENSIBLE <> 'YES';

If the output is 0 then the tablespace is autoextensible. If the result it not 0, then alter TEMP & UNDO table space autoextent ON

6.       Remove existing SYSMAN schema : Goto Command prompt

                   $<ORACLE_HOME>/bin/emca -deconfig dbcontrol db -repos drop -SYS_PWD <sys pasword> -SYSMAN_PWD <sysman password>

       Example: emca -deconfig dbcontrol db -repos drop -SYS_PWD password123 -SYSMAN_PWD password123

7.       Ensure that you check the network configuration to verify that the host on which you are installing resolves to a unique host name and a static IP address that are visible to other hosts in the network.

Example: 180.151.61.173 EMServer1.server emserver

WEB LOGIC INSTALLATION:

1.       Install weblogic10.3.2.

2.       In case of 64 bit OS install JDK 64 bit in host machine  and then install web logic 10.3.2 Generic.jar.

OEM INSTALLATION:

1.       Install OEM 11g.

2.       Enter the weblogic User Name : weblogic

Password: password123

Node Manage User Name (By default): Node Manager

Password: password123

3.       Enter the EM Grid repository (database) details.

Database Host name: Enter static IP Address    Port: 1521 (Listener port number)

SID: EMREP (Database Name)

4.       Enter SYSMAN password and click next.

5.       Enter registration password. And select the “Allow only secure agents to communicate with the OMS” and “Allow only secure access to the console” option and click Next.

6.       Keep default port numbers and click next and click install button.

7.       On the End of Installation screen, you should see information pertaining to the installation of Enterprise Manager.

OEM Installation Log file locations:

Review the log files in the following locations:

1. Repository Configuration Assistant: 

$<ORACLE_HOME>/cfgtoollogs/cfgfw/emmdscreate_<timestamp>.log

$<ORACLE_HOME>/sysman/log/schemamanager/m_<timestamp>/m_<timestamp>.<ACTION>/

(ORACLE_HOME refers to the Oracle home of the OMS. <ACTION> refers to any of the schema actions,)

2. MDS Schema Configuration Assistant:

$<ORACLE_HOME>/cfgtoollogs/cfgfw/emmdscreate_<timestamp>.log

For more information, review the following log files:

$<ORACLE_HOME>/sysman/log/schemamanager/m_<timestamp>/m_<timestamp>.CREATE/mds.log

$<ORACLE_HOME>/sysman/log/schemamanager/m_<timestamp>/m_<timestamp>.CREATE/rcu.log

(ORACLE_HOME refers to the Oracle home of the OMS)

3. OMS Configuration Assistant:

If the installer fails AFTER the OMS Configuration Assistant starts running, then review the following log file:

$<ORACLE_HOME>/cfgtoollogs/omsca/omsca_<timestamp>.log

(ORACLE_HOME refers to the Oracle home of the OMS)

4. Agent Configuration Assistant:

$<ORACLE_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

(ORACLE_HOME refers to the Oracle home of the Management Agent)

If secure fails, then review the following log file:

$<ORACLE_HOME>/sysman/log/secure.log

5. Agent Add-On Plug-In

$<ORACLE_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

(ORACLE_HOME refers to the Oracle home of the Management Agent)

6. Repository Upgrade Configuration Assistant

 Review the log files in the following locations:

$<ORACLE_HOME>/cfgtoollogs/cfgfw/emmdscreate_<timestamp>.log

$<ORACLE_HOME>/sysman/log/schemamanager/m_<timestamp>/m_<timestamp>.<ACTION>/

          (ORACLE_HOME refers to the Oracle home of the OMS. <ACTION> refers to any of the schema actions, for example, PREUPGRADE, UPGRADE, TRANSX, and so on.

7. Agent Upgrade Configuration Assistant

$<ORACLE_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

If secure fails, then review the following log file:

$<ORACLE_HOME>/sysman/log/secure.log

       (ORACLE_HOME refers to the Oracle home of the Management Agent)

INSTALLATION TROUBLESHOOTING GUIDE   :  

1.                REPOSITORY CONFIGURATION FAILED :

 Solutions:

     >Go and check the SYSMAN Schema has been deleted from the database permanently.

    > Run this script to remove the $ORACLE_HOME\RDBMS\ADMIN\utlrp.sql.    This Scripts to check the location invalid objects in database

    >Check the database: SQL>SELECT COUNT(*) FROM ALL_USERS WHERE USERNAME IN ('SYSMAN','SYSMAN_MDS');

    > If any of this Schema User exist in database drop the user manually: SQL> drop USER <Username> CASCADE;

 2. MDS SCHEM CONFIGURATION FAILED:

 Solution:  

    >Run the following command in database and Click Retry

       SQL>delete from SCHEMA_VERSION_REGISTRY where COMP_NAME='Metadata Services'

3.       AGENT  CONFIGURATION FAILED :

   Solution:

  > This is due to the static IP address and domain name is missing from host location.  

N.B: With reference to Oracle support document

Document Name: 11g GC Installation in Windows Fails during securing of Agent

 Oracle Support Document ID: [ID 1273470.1]

4. SECURE AGENT FAILED:

 Follow the following steps to secure the agent:

 > Cancel the installation process in the Agent Configuration Assistant and exit of OUI.

 > Go to the directory of Agent:and open the emd.properties

                cd $AGENT_HOME/sysman/config

                vi emd.properties

 > Check that the EMD_URL of Agent and the REPOSITORY URL and write correct, and check that the hostname and port are write in both entries.

> Check the status of agent

$AGENT_HOME/bin/emctl status agent

 > The agent must be down. After, secure the agent with the registration password

                $AGENT_HOME/bin/emctl secure agent

 > The OMS must be UP before you try securing the agent

 > After the secure agent, start the agent

                $AGENT_HOME/bin/emctl start agent

 > Check the communication between the agent and OMS

                $AGENT_HOME/bin/emctl pingOMS

AGENT DEPLOYMENT IN REMOTE MACHINE (PEOPLESOFT SERVER):

There are total eight different way we can configure the or deploy the Agent in remote machine.

1.  Installing Oracle Management Agent Using Shared Oracle Home

2.  Installing Oracle Management Agent on a Cluster Using Agent Deployment Wizard

3.  Cloning Oracle Management Agent Using Agent Cloning Wizard

4.  Installing Oracle Management Agent Using Response File

5.  Installing Oracle Management Agent using agent Download Script

6.  Installing Oracle Management Agent on a Cluster Using Response File or agent Download Script

7.  Installing Oracle Management Agent Using Shared Oracle Home Using nfsagentinstall Script.

Installing Oracle Management Agent Using Response File: -

1.       Extract the Oracle Agent11g

2.       Go to Extracted location and  Modify the additional_agent.rsp file

 RSP file location : <Drive>:\Agent11g\win32\response

Modify the highlighted parameters:

####################################################################

## copyright (c) 1999, 2010 Oracle. All rights reserved.          ##

##                                                                ##

## Specify values for the variables listed below to customize     ##

## your installation.                                             ##

##                                                                ##

## Each variable is associated with a comment. The comment        ##

## identifies the variable type.                                  ##

##                                                                ##

## Please specify the values in the following format:             ##

##                                                                ##

##         Type         Example                                   ##

##         String       "Sample Value"                            ##

##         Boolean      True or False                             ##

##         Number       1000                                      ##

##         StringList   {"String value 1","String Value 2"}       ##

##                                                                ##

## The values that are given as <Value Required> need to be       ##

## specified for a silent installation to be successful.          ##

##                                                                ##

##                                                                ##

## This response file is generated by Oracle Software             ##

## Packager.                                                      ##

###################################################################

RESPONSEFILE_VERSION=2.2.1.0.0

#################################################################################

#Inputs for Oracle Configuration Manager

#################################################################################

#-------------------------------------------------------------------------------

#SECURITY_UPDATES_VIA_MYORACLESUPPORT:<Boolean> Whether security updates are reqi-

#        uired via My Oracle Support

#DECLINE_SECURITY_UPDATES:<Boolean> Whether security updates should be declined.

#MYORACLESUPPORT_USERNAME & MYORACLESUPPORT_PASSWORD:<String> User name and passw-

#        ord for My Oracle Support access, these will be effected only when SECU-

#        RITY_UPDATES_VIA_MYORACLESUPPORT=true

#COLLECTOR_SUPPORTHUB_URL:<String> If there is not direct connection and Support

#        hub is deployed. Need to specify that URL.

#-------------------------------------------------------------------------------

SECURITY_UPDATES_VIA_MYORACLESUPPORT=<Value Unspecified>    # Enter YES

DECLINE_SECURITY_UPDATES=<Value Unspecified>                                   # Enter NO

MYORACLESUPPORT_USERNAME=<Value Unspecified>

MYORACLESUPPORT_PASSWORD=<Value Unspecified>

COLLECTOR_SUPPORTHUB_URL=<Value Unspecified>

################################################################################

#PARAMETERS FOR SOFTWARE UPDATES

################################################################################

#-------------------------------------------------------------------------------

#INSTALL_UPDATES_SELECTION:<String>

# Option 1. If you want to skip the software updates, provide

#      INSTALL_UPDATES_SELECTION="skip"

# Option 2. If you have already downloaded the updates then provide

#      INSTALL_UPDATES_SELECTION="staged"

# If you choose the Option 2 then make sure you also provide STAGE_LOCATION.

#STAGE_LOCATION:<String> Stage location for software updates. It will be effected

#       only when INSTALL_UPDATES_SELECTION is  set to "staged"

#-------------------------------------------------------------------------------

INSTALL_UPDATES_SELECTION="skip"

STAGE_LOCATION=<Value Unspecified>

################################################################################

#PROXY DETAILS FOR SECURITY UPDATES/ SOFTWARE UPDATES

################################################################################

#-------------------------------------------------------------------------------

#PROXY_USER:<String> User name for proxy access.

#PROXY_PWD:<String> Password for proxy access.

#PROXY_HOST:<String> Server providing proxy access.

#PROXY_PORT:<String> Port for proxy access.

#------------------------------------------------------------------------------

PROXY_USER=<Value Unspecified>

PROXY_PWD=<Value Unspecified>

PROXY_HOST=<Value Unspecified>

PROXY_PORT=<Value Unspecified>

################################################################################

#Various inputs required for Installation and Configuration

################################################################################

#-------------------------------------------------------------------------------

#ORACLE_AGENT_HOME_LOCATION:<String> The location of oracle agent home.

#Agent home "agent11g" would be created under the directory specified by

#ORACLE_AGENT_HOME_LOCATION.

#-------------------------------------------------------------------------------

ORACLE_AGENT_HOME_LOCATION=<Value Unspecified>

#-------------------------------------------------------------------------------

#DEINSTALL_LIST:<StringList> List of components to be deinstalled during a

#      deinstall session.The following choices are available. The value should

#      contain only one of these choices.The choices are of the form

#      Internal Name, Version : External name. Please use the internal name and

#      version while specifying the value.

#    oracle.sysman.top.agent, 10.2.0.0.0 : Oracle Management Agent 10.2.0.0.0

#    oracle.sysman.top.em_seed, 10.2.0.0.0 : Oracle Enterprise Manager Repository Database 10.2.0.0.0

#    oracle.sysman.top.oms, 10.2.0.0.0 : Oracle Enterprise Manager Grid Console 10.2.0.0.0

#-------------------------------------------------------------------------------

DEINSTALL_LIST={"oracle.sysman.top.agent","11.1.0.1.0"}

#-------------------------------------------------------------------------------

#b_silentInstall:<Boolean> The user should not change this value

#CLUSTER_NODES:<StringList> This variable represents the cluster node names

#       selected by the user for installation.

#-------------------------------------------------------------------------------

b_silentInstall=true

#CLUSTER_NODES=<Value Unspecified>

#-------------------------------------------------------------------------------

#TOPLEVEL_COMPONENT:<StringList> The top level component to be installed in the

#      current session.Value should contain only one of the following available

#      choices.The choices are of the form Internal Name, Version : External name.

#      Please use the internal name and version while specifying the value.

#    oracle.sysman.top.agent, 10.3.0.0.0 : Oracle Management Agent 10.3.0.0.0

#    Example: TOPLEVEL_COMPONENT = {"oracle.sysman.top.agent","10.3.0.0.0"}

#-------------------------------------------------------------------------------

TOPLEVEL_COMPONENT={"oracle.sysman.top.agent","11.1.0.1.0"}

#-------------------------------------------------------------------------------

#SELECTED_LANGUAGES:<StringList> Languages in which the components will be installed.

#      The following choices are available. The value should contain only one of

#      these choices.The choices are of the form Internal Name : External name.

#      Please use the internal name while specifying the value.

#    en,   : English

#    de,   : German

#    es,   : Latin American Spanish

#    es_MX,   : Mexican Spanish

#    es_ES,   : Spanish

#    fr,   : French

#    fr_CA,   : Canadian French

#    it,   : Italian

#    iw,   : Hebrew

#    ja,   : Japanese

#    ko,   : Korean

#    pt_BR,   : Brazilian Portuguese

#    zh_CN,   : Simplified Chinese

#    zh_TW,   : Traditional Chinese

#Example: SELECTED_LANGUAGES = {"en"}

#-------------------------------------------------------------------------------

#SELECTED_LANGUAGES={"en"}

#-------------------------------------------------------------------------------

#COMPONENT_LANGUAGES:<StringList> Languages in which the components will be installed.

#      The following choices are available. The value should contain only one of

#      these choices.The choices are of the form Internal Name : External name.

#      Please use the internal name while specifying the value.

#    en,   : English

#    de,   : German

#    es,   : Latin American Spanish

#    es_MX,   : Mexican Spanish

#    es_ES,   : Spanish

#    fr,   : French

#    fr_CA,   : Canadian French

#    it,   : Italian

#    iw,   : Hebrew

#    ja,   : Japanese

#    ko,   : Korean

#    pt_BR,   : Brazilian Portuguese

#    zh_CN,   : Simplified Chinese

#    zh_TW,   : Traditional Chinese

#Example: COMPONENT_LANGUAGES = {"en"}

#-------------------------------------------------------------------------------

COMPONENT_LANGUAGES={"en"}

#-------------------------------------------------------------------------------

#OMS_HOST:<String> OMS host info required to connect to OMS

#OMS_PORT:<String> OMS port info required to connect to OMS

#AGENT_REGISTRATION_PASSWORD:<String> Agent Registration Password needed to

#     establish a secure connection to the OMS.

#-------------------------------------------------------------------------------

OMS_HOST=<Value Unspecified>    # Here add host name

OMS_PORT=<Value Unspecified>    # Add Host Port Number

AGENT_REGISTRATION_PASSWORD=<Value Unspecified>  #Enter Agent Registration password which is creation during agent installation

# OEM Server

#-------------------------------------------------------------------------------

#s_agentSrvcName:<String> Sets the agent Service Name and this variable can be

#      used to overrite the agent service name calculated by the install. This is

#      required for only Windows.

#      Example:

#      s_agentSrvcName    = "Oracleagent11gAgent"      ;  default value

#      s_agentSrvcName = "GridAgent"                   ;  User specified value

#-------------------------------------------------------------------------------

#s_agentSrvcName=""

####################################################################################

#Please Don't change the values of these variables

####################################################################################

#-------------------------------------------------------------------------------

#FROM_LOCATION:<String> Complete path to the products.xml.

#b_upgrade:<Boolean> "whether it is Upgrade or not"

#EM_INSTALL_TYPE:<STRING> install type

#-------------------------------------------------------------------------------

FROM_LOCATION="../stage/products.xml"

b_upgrade=false

EM_INSTALL_TYPE="AGENT"

3.     Execute the following command :  Example: C:\> C:\Agent\win32\agent>setup.exe -silent -responseFile C:\Agent\win32\response\additional_agent.rsp

Location of agent may vary as per your software extracted location.

4.       Verify the installed agent:

C:\>$<ORACLE_HOME>/bin/emctl status agent

                         If the status of the Management Agent is down for some reason, then manually start the Management Agent by running the following command from its Oracle home: 

           C:\>$<ORACLE_HOME>/bin/emctl start agent

5.      Navigate to the Oracle home of the Management Agent and run the following command to see a message that confirms that EMD upload completed successfully:

               $<ORACLE_HOME>/bin/emctl upload

6.       Goto OEM Server

           $<ORACLE_HOME>/bin/emctl resync repos -full

Go to EM URL and Check the new updated Agent.

https://EMServer1:7201/em/console  (Console URL vary as per as your domain name)

ORACLE PEOPLE SOFT ENVIRONMENT MANAGEMENT PLUG-IN FOR OMS AND REMOTE AGENT (People-soft Server) 

 Installing the PeopleSoft Environment Management Plug-in extensions on OMS Server (OEM Server):-

1.  Stop the Oracle Management Service using the following command:

$ORACLE_HOME/bin/emctl stop oms

2.  Run one of these commands to start the installer:

>For Windows, select Start, Programs, OMS11g, Oracle Installation Products, and Universal Installer.

            >For all other platforms, open a command shell and change directory to the Oracle Home of the OMS. Change directory to oui/bin, and execute the file runInstaller.

3.  Click next on the Oracle Universal Installer welcome screen.

4.  Click Browse and choose the file products.xml in the directory <INSTALL_DIRECTORY>/Disk1/stage on the Specify Source Location window, and click Next.

5.  On the Select a Product to install window, select the radio button for PeopleSoft Environment Management Plug-in for Enterprise Manager (OMS), and click Next.

6.  On the Oracle Home Location window, ensure these parameters are set correctly, and click Next.

Name:  Select the Oracle HOME of the Oracle Management Service where the PeopleSoft Environment Management Plug-in is to be installed. The default value is the first Oracle HOME (alphabetically) that is stored in the inventory file.

Path:  The path for the Oracle HOME selected above will be populated in this drop-down. You need not change anything in this drop-down list.

7.  On the Repository HostName window, enter the name of the host where the repository (Oracle database) resides, and click Next.

8.  On the Repository Listener Port window, enter the database listener port, such as 1521, and click Next.

9.  On the Repository SID window, enter the SID of the database used for the EM repository, and click Next.

10.  On the Repository Database Administrator Password window, enter the appropriate value in the SYS Password edit box, and click Next.

11. Review and click install.

Installing the PeopleSoft Environment Management Plug-in to the Management Agent:-

1.  Use the following command to stop the Oracle Agent:

emctl stop agent

2.  Launch the Oracle Universal Installer.

Depending on the platform, perform one of the following two actions:

• For Windows, select Start, Programs, Agent 11g, Oracle Installation Products, Uni Installer.

• For all other operating systems platforms, open a command shell and change directory to the Oracle Home of the Agent. Change directory to oui/bin, and execute the file runInstaller.

4.       On the Universal Installer welcome window, click next.

5.   On the Specify Source Location window, click Browse and choose the file, products.xml, in <INSTALL_DIRECTORY>/Disk1/stage, and click Next.

6.   On the Select a Product to install window, select PeopleSoft Environment Management Plug-in (Agent) click next.

7.  On the Specify Oracle Home Location window, specify the following parameters, and click next.

Name: Select the Oracle HOME of the Oracle Agent where the PeopleSoft Environment Management Plug-in is to be installed.

Path: The path for the Oracle HOME selected above will be populated in this drop-down list.

8.  Review the location and click install.

 By: Prasanth Bhaskaran (PeopleSoft Application DBA)