Announcement

Collapse
No announcement yet.

[INSTRUCTIONS] Restoring OTM to another server

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    [INSTRUCTIONS] Restoring OTM to another server

    Hello all,

    Going through my email - I ran across a doc from a friend, Alan, who had given some directions on the changes that need to be made to OTM after restoring it to another server. While this isn't supported by Oracle, the directions may give you enough information to go at it alone.

    I've checked and he's allowed me to share it here on the forums. Hopefully others will find it useful Thanks Alan

    Changes required after restore of OTM to a new server.

    1. Create groups oracle & otm using the same UID & GID as what's used in prod.

    Code:
    groupadd -g 501 otm
useradd -u 501 -g otm otm
groupadd -g 502 dba
useradd -u 502 -g dba oracle
    2. Modify the Oracle sid in /home/otm/.bash_profile and make sure the following lines are in the .bash_profile

    change
    export ORACLE_SID=OTMPROD
    to
    export ORACLE_SID=OTMTEST

    make sure the following lines are in the .bash_profile file.

    Code:
    export ORACLE_HOME=/u01/app/oracle/product/10.2.0/client_1
export ORACLE_SID=OTMTEST
PATH=$PATH:$HOME/bin:$ORACLE_HOME/bin
/opt/otm55prod/install/gc3env.sh
    As the oracle user modify file /u01/app/oracle/product/10.2.0/client_1/network/admin/tnsnames.ora add the following.

    Code:
    OTMTEST =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = dbserver.company.com)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SID=otmtest)
    )
  )
    4. Test the database connection

    Code:
    [[email protected] ~]$ tnsping otmtest

TNS Ping Utility for Linux: Version 10.2.0.1.0 - Production on 02-AUG-2007 14:27:00

Copyright (c) 1997, 2005, Oracle.  All rights reserved.

Used parameter files:
/u01/app/oracle/product/10.2.0/client_1/network/admin/sqlnet.ora

Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = dbserver.company.com)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SID=otmtest)))
OK (10 msec)
    5. Modify /opt/otm55prod/glog/config/glog.properties

    change

    appserver=otmserver.company.com
    to
    appserver=otmserver2.company.com

    webserver=otmserver.company.com
    to
    webserver=otmserver2.company.com

    glog.webserver.URL=https://otmserver.company.com:443$glog.webserver.urlprefix $
    to
    glog.webserver.URL=https://otmserver2.company.com:443$glog.webserver.urlprefi x$

    dbserver=dbserver.company.com
    to
    dbserver=dbserver.company.com

    glog.database.sid=otmprod
    to
    glog.database.sid=otmtest

    glog.database.connectstring=otmprod
    to
    glog.database.connectstring=otmtest

    6. Modify /opt/otm55prod/weblogic/config/gc3domain/config.xml.template

    change

    TestTableName="dual" URL="jdbcracle:thin:@dbserver.company.com:1521tmprod"/>
    to
    TestTableName="dual" URL="jdbcracle:thin:@dbserver.company.com:1521tmtest"/>

    JDBCLoggingEnabled="false" ListenAddress="192.168.0.1"
    to
    JDBCLoggingEnabled="false" ListenAddress="192.168.1.1"

    7. Modify /opt/otm55prod/weblogic/config/gc3domain/weblogic.conf

    wrapper.app.parameter.8=t3://otmserver.company.com:7001
    to
    wrapper.app.parameter.8=t3://otmserver2.company.com:7001


    8. Modify /opt/otm55prod/tomcat/conf/server.xml

    to

    9. Modify /opt/otm55prod/apache/conf/httpd.conf

    Listen 192.168.0.1:80
    Listen 192.168.0.1:443

    to

    Listen 192.168.1.1:80
    Listen 192.168.1.1:443

    10. ** VERY IMPORTANT** Modify /opt/otm55prod/apache/conf/workers.properties

    worker.ajp13.host=192.168.0.1
    to
    worker.ajp13.host=192.168.1.1


    11. Modify /opt/otm55prod/install/apache/glogweb-wl

    $JAVA_HOME/bin/java glog.util.admin.WaitForServer otmserver.company.com 7001
    to
    $JAVA_HOME/bin/java glog.util.admin.WaitForServer otmserver2.company.com 7001

    $JAVA_HOME/bin/java glog.util.admin.WaitForServer otmserver.company.com 8009
    to
    $JAVA_HOME/bin/java glog.util.admin.WaitForServer otmserver2.company.com 8009

    12. Modify /opt/otm55prod/install/weblogic/glogapp-wl

    $JAVA_HOME/bin/java glog.util.admin.WaitForServer dbserver.company.com 1521
    to
    $JAVA_HOME/bin/java glog.util.admin.WaitForServer dbserver.company.com 1521

    13. Remove the file root.sh.ran

    Code:
    rm /opt/otm55prod/install/root.sh.ran
    14) Execute root.sh as root

    Code:
    [[email protected]]# /opt/otm55prod/install/root.sh
------------------------------------------------------
root.sh
------------------------------------------------------
Ensure that all commands in this file run successfully
to ensure that GC3 is setup correctly. Please resolve
any errors before proceeding.
------------------------------------------------------
    14. As the otm user run the following database scripts.

    Running OTM scripts

    a. Change to the /glog/oracle/script8 directory on the OTM Application
    server.

    Code:
    [[email protected] ~]$ cd /opt/otm55prod/glog/oracle/script8

start sql*plus as user GLOGOWNER

[[email protected] script8]$ sqlplus glogowner/[email protected]
    from the sql*plus prompt run:

    @create_vpd_package.sql
    @glogowner_grants.sql
    @create_public_synonyms.sql
    @create_logon_triggers (enter connection string when prompted)

    b. In SQL*Plus, as user ARCHIVE run:

    Code:
    [[email protected] script8]$ sqlplus archive/[email protected]
    @archive_grants

    c. In SQL*Plus, as user REPORTOWNER run:

    Code:
    [[email protected] script8]$ sqlplus reportowner/[email protected]
    @reportowner_grants.sql
    @create_public_synonyms.sql
    @recompile_invalid_objects.sql

    After running the “recompile_invalid_objects.sql” script, you should see the following on the screen:
    Invalid objects after Recompile...
    0
    If the number of invalid objects is not zero, run the recompile_invalid_objects.sql script again.



    d. In SQL*Plus, as user GLOGOWNER run:

    Code:
    [[email protected] script8]$ sqlplus glogowner/[email protected]
    @aq_setup.sql
    @recompile_invalid_objects.sql

    After running the recompile_invalid_objects.sql script, you should see the following on the screen:
    Invalid objects after Recompile...
    0

    Setup Security Roles

    e. Change to the /gc3/glog/oracle directory on the OTM Application server.

    Code:
    [[email protected] ~]$ cd /opt/otm55prod/glog/oracle
    f. In SQL*Plus as the GLOGOWNER user, run:

    Code:
    [[email protected] script8]$ sqlplus glogowner/[email protected]
    @insert_security_roles.sql


    15. Start otm as root and monitor the logs for normal startup
    Personally, I've gotten to the point where I can re-install OTM in short notice, so I prefer that route -- but it's always good to have options!

    Hope this helps!
    --Chris
    Tags: instructions, otm, restore, restoring, server
  • #2
    Re: [INSTRUCTIONS] Restoring OTM to another server

    Does anyone have any experience with these instructions? I am looking at moving my installation to a new server, but I am unclear as to why I couldn't just change properties files to new server names/IPs and just be done with it...I didn't know that there was that much server-specific information stored in the DB.
    Any insights definitely appreciated!
    Cheers,
    Rick

    Comment

    • #3
      Re: [INSTRUCTIONS] Restoring OTM to another server

      Just for further info....this new server will be a cloned Solaris container, and will be an exact copy of my existing server, obviously with new hostname/IP, and a new DB which is also an exact copy, with a different name
      -Rick

      Comment

      • #4
        Re: [INSTRUCTIONS] Restoring OTM to another server

        So....followed all instructions above, but....
        when I try to start, first thing my appserver does is go after my old database....I've done a pretty exhaustive search for either of the old dbname, the old dbhost, or the old db IP address, with zero result.....damn!

        Comment

        • #5
          Re: [INSTRUCTIONS] Restoring OTM to another server

          Hi,
          Did you check you glog.properties file in app and web server

          Comment

          Previous template Next
          Working...
          X