Go to main content

Oracle® Solaris Cluster Data Service for Oracle E-Business Suite up to Release 12.1 Guide

Exit Print View

Updated: April 2016
 
 

Verifying the Installation and Configuration of Oracle E-Business Suite up to Release 12.1

This section contains the procedure you need to verify the installation and configuration of Oracle E-Business Suite up to release 12.1.

For Oracle E-Business Suite software starting with release 12.2, follow procedures in Oracle Solaris Cluster Data Service for Oracle E-Business Suite as of Release 12.2 Guide .

How to Verify the Installation and Configuration of Oracle E-Business Suite up to Release 12.1

This procedure does not verify that your application is highly available because you have not yet installed your data service.

Perform this procedure on one node or zone of the cluster unless a specific step indicates otherwise.

  1. On a cluster member, become an administrator that provides solaris.cluster.modify authorization.
  2. Mount the highly available local file system.

    Perform this step from the global zone on one node of the cluster.

    • If a non-ZFS highly available local file system is being used for the Oracle E-Business Suite up to release 12.1 files, perform the following step.
      Note -  Ensure that the node has ownership of the disk set. 
      # metaset -s disk-set -t
      • If the global zone is being used for Oracle E-Business Suite up to release 12.1, type: 
        # mount highly-available-local-filesystem
    • If a ZFS highly available local file system is being used for Oracle E-Business Suite up to release 12.1, perform the following step.
      • If the global zone is being used for Oracle E-Business Suite up to release 12.1, type the following command. 
        # zpool import -R / HAZpool
  3. Plumb the Oracle E-Business Suite up to release 12.1 logical hostname.
    Note -  If you are using Parallel Concurrent Processing, omit this step. Parallel Concurrent Processing requires physical hostnames.

    If you are using Clustered OPMN OC4J instances, omit this step. Clustered OPMN OC4J instances require physical hostnames.

    Perform this step for each logical hostname being used by Oracle E-Business Suite up to release 12.1.

    If the global zone is being used for Oracle E-Business Suite up to release 12.1, type the following command.

    #  ifconfig interface addif logical-hostname up
  4. Start Oracle E-Business Suite up to release 12.1.
    Note -  If you installed Parallel Concurrent Processing, you installed batch services on the physical hostname. Therefore, to start the Concurrent Manager, you must specify the physical-host pathname for the admin scripts. To start other application-tier components that you installed by using a logical host, you must use the logical-host pathname for the admin scripts.

    If you installed Clustered OPMN OC4J instances, you installed on the physical hostname. Therefore, to start the Clustered OPMN OC4J instance, you must specify the physical-host pathname for the admin scripts. To start other application-tier components that you installed by using a logical host, you must use the logical-host pathname for the admin scripts.

    • For Oracle E-Business Suite up to release 12.1, perform the following commands. 
      # su - oradb-user
$ cd db-base-directory/SID/db/tech_st/*/appsutil/scripts/SID_db-logical-hostname
$ ./addbctl.sh start
$ ./addlnctl.sh start SID
$ exit
# su - oraapp-user
$ cd app-base-directory/inst/apps/SID_app-logical-hostname/admin/scripts
$ ./adstrtal.sh apps/apps
$ exit
  5. Test that a client can access Oracle E-Business Suite up to release 12.1.
    • For Oracle E-Business Suite up to release 12.1, perform the following steps.
      1. Log into Oracle E-Business Suite up to release 12.1.

        http://ebs-logical-host.domainname:8000

      2. Verify that you can successfully log in and navigate through Oracle E-Business Suite up to release 12.1.
  6. Stop Oracle E-Business Suite up to release 12.1.
    Note -  If you installed Parallel Concurrent Processing, you installed batch services on the physical hostname. Therefore, to stop the Concurrent Manager, you must specify the physical-host pathname for the admin scripts. To stop other application-tier components that you installed by using a logical host, you must use the logical-host pathname for the admin scripts.

    If you installed Clustered OPMN OC4J instances, you installed on the physical hostname. Therefore, to stop the Clustered OPMN OC4J instance, you must specify the physical-host pathname for the admin scripts. To stop other application-tier components that you installed by using a logical host, you must use the logical-host pathname for the admin scripts.

    • For Oracle E-Business Suite up to release 12.1, perform the following commands. 
      # su - oraapp-user
$ cd app-base-directroy/inst/apps/SID_app-logical-hostname/admin/scripts
$ .adstpall.sh apps/apps
$ exit
# su - oradb-user
$ cd db-base-directory/SID/db/tech_st/*/appsutil/scripts/SID_db-logical-hostname
$ ./addlnctl.sh stop SID
$ ./addbctl.sh stop immediate
  7. Unmount the highly available local file system.

    Perform this step only in the global zone.

    • To unmount a non-ZFS highly available local file system that is being used for Oracle E-Business Suite up to release 12.1, perform one of the following steps.
      • If the global zone is being used for Oracle E-Business Suite up to release 12.1, type the following command. 
        # umount highly-available-local-filesystem
      • If an Oracle Solaris zone is being used for Oracle E-Business Suite up to release 12.1, unmount the highly available local file system from the zone. 
        # umount /zonepath/root/highly-available-local-filesystem
    • If a ZFS highly available file system is being used for Oracle E-Business Suite up to release 12.1, type the following command. 
      # zpool export -f HAZpool
  8. Unplumb the Infrastructure logical IP address.

    Perform this step for each logical hostname being used by Oracle E-Business Suite up to release 12.1.

    # ifconfig interface removeif logical-hostname
  9. Relocate the shared storage to another node and mount the highly available local file system.

    Perform this step on another node of the cluster.

    • If a non-ZFS highly available local file system is being used for the Oracle E-Business Suite up to release 12.1 files, perform the following step.
      Note -  Ensure that the node has ownership of the disk set. 
      # metaset -s disk-set -t
      • If the global zone is being used for Oracle E-Business Suite up to release 12.1, type the following command. 
        # mount highly-available-local-filesystem
    • If a ZFS highly available file system is being used for Oracle E-Business Suite up to release 12.1, perform the following step.
      • If the global zone is being used for Oracle E-Business Suite up to release 12.1, type the following command. 
        # zpool import -R / HAZpool
  10. Plumb the Oracle E-Business Suite up to release 12.1 logical hostname.

    Perform this step on another node of the cluster for each logical hostname being used by Oracle E-Business Suite up to release 12.1.

    • If the global zone is being used for Oracle E-Business Suite up to release 12.1, type the following command. 
      # ifconfig interface addif logical-hostname up
  11. Start Oracle E-Business Suite up to release 12.1.
    Note -  If you installed Parallel Concurrent Processing, you installed batch services on the physical hostname. Therefore, to start the Concurrent Manager, you must specify the physical-host pathname for the admin scripts. To start other application-tier components that you installed by using a logical host, you must use the logical-host pathname for the admin scripts.

    If you installed Clustered OPMN OC4J instances, you installed on the physical hostname. Therefore, to start the Clustered OPMN OC4J instance, you must specify the physical-host pathname for the admin scripts. To start other application-tier components that you installed by using a logical host, you must use the logical-host pathname for the admin scripts.

    • For Oracle E-Business Suite up to release 12.1, perform the following: 
      # su - oradb-user
$ cd db-base-directory/SID/db/tech_st/*/appsutil/scripts/SID_db-logical-hostname
$ ./addbctl.sh start
$ ./addlnctl.sh start SID
$ exit
# su - oraapp-user
$ cd app-base-directory/inst/apps/SID_app-logical-hostname/admin/scripts
$ ./adstrtal.sh apps/apps
$ exit
  12. Test that a client can access Oracle E-Business Suite up to release 12.1.
    • For Oracle E-Business Suite up to release 12.1, perform the following:
      1. Log into Oracle E-Business Suite up to release 12.1.

        http://ebs-logical-host.domainname:8000

      2. Verify that you can successfully log in and navigate through Oracle E-Business Suite up to release 12.1.
  13. Stop Oracle E-Business Suite up to release 12.1.
    Note -  If you installed Parallel Concurrent Processing, you installed batch services on the physical hostname. Therefore, to stop the Concurrent Manager, you must specify the physical-host pathname for the admin scripts. To stop other application-tier components that you installed by using a logical host, you must use the logical-host pathname for the admin scripts.

    If you installed Clustered OPMN OC4J instances, you installed on the physical hostname. Therefore, to stop the Clustered OPMN OC4J instance, you must specify the physical-host pathname for the admin scripts. To stop other application-tier components that you installed by using a logical host, you must use the logical-host pathname for the admin scripts.

    • For Oracle E-Business Suite up to release 12.1, perform the following commands. 
      # su - oraapp-user
$ cd app-base-directroy/inst/apps/SID_app-logical-hostname/admin/scripts
$ .adstpall.sh apps/apps
$ exit
# su - oradb-user
$ cd db-base-directory/SIDdb/tech_st/*/appsutil/scripts/SID_db-logical-hostname
$ ./addlnctl.sh stop SID
$ ./addbctl.sh stop immediate
  14. Unmount the highly available local file system.

    Perform this step in the global zone only.

    • To unmount a non-ZFS highly available local file system that is being used for Oracle E-Business Suite, perform the following step.
      • If the global zone is being used for Oracle E-Business Suite up to release 12.1, type the following command. 
        # umount highly-available-local-filesystem
    • If a ZFS highly available file system is being used for Oracle E-Business Suite up to release 12.1, type the following command. 
      # zpool export -f HAZpool
  15. Unplumb the Oracle E-Business Suite up to release 12.1 logical hostname.

    Perform this step for each logical hostname being used by Oracle E-Business Suite up to release 12.1.

    # ifconfig interface removeif logical hostname
Copyright © 2006, 2016, Oracle and/or its affiliates. All rights reserved. 
Previous
Next