This section contains the procedure you need to verify the installation and configuration.
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.
On a cluster member, become superuser or assume a role that provides solaris.cluster.modify RBAC authorization.
If a zone is being used for Oracle E-Business Suite, ensure that the zone is booted.
Repeat this step on all nodes on the cluster if a zone is being used.
Boot the zone if it is not running.
# zoneadm list -v # zoneadm -z zonename boot |
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 files, perform one of the following steps.
Ensure that the node has ownership of the disk set or disk group.
For Solaris Volume Manager, type:
# metaset -s disk-set -t |
For Veritas Volume Manager, type:
# vxdg -C import disk-group # vxdg -g disk-group startall |
If the global zone is being used for Oracle E-Business Suite, type:
# mount highly-available-local-filesystem |
If a zone is being used for Oracle E-Business Suite, mount the highly available local file system on one of the zones being used.
# mount -F lofs highly-available-local-filesystem \ > /zonepath/root/highly-available-local-filesystem |
If a ZFS highly available file system is being used for Oracle E-Business Suite, perform one of the following steps.
Plumb the Oracle E-Business Suite logical hostname.
Perform this step for each logical hostname being used by Oracle E-Business Suite.
If a zone is being used, log in to the zone.
# zlogin zonename |
Start Oracle E-Business Suite.
If you are using Oracle E-Business Suite version 12 or later, 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 |
If you are using Oracle E-Business Suite version 11.5.10 or earlier, perform the following:
# su - oradb-user $ cd db-base-directory/SID/db/9.2.0/appsutil/scripts/ \ SID_db-logical-hostname $ ./addbctl.sh start $ ./addlnctl.sh start SID $ exit # su - oraapp-user $ cd app-base-directory/SIDcomn/admin/scripts/SID_app-logical-hostname $ ./adstrtal.sh apps/apps $ exit |
Test that a client can access Oracle E-Business Suite by using a Windows Client.
If you are using Oracle E-Business Suite version 12 or later, perform the following:
Log in to Standalone Diagnostics at
http://ebs-logical-host.domainname:8000/OA_HTML/DiagLogin.jsp.
Log in with Userid sysadmin and Password sysadmin. Then click Login.
Click the Basic tab and click Run All.
Some diagnostics tests might fail as Oracle E-Business Suite is not fully configured.
From the Application drop-down menu, select HTML Platform. Then click Run All Groups.
From the Application drop-down menu, select Application Object Library. Then click Run All Groups.
From the Application drop-down menu, select CRM Foundation. Then click Run All Groups.
If you are using Oracle E-Business Suite version 11.5.10 or earlier, perform the following:
Log in to Standalone Diagnostics at
http://ebs-logical-host.domainname:8000/OA_HTML/US/ICXINDEX.htm.
Log in with Userid sysadmin and Password sysadmin. Then click System Admin.
Double-click Requests and double-click Run.
Click OK on Single requests.
Type Active Users in the Name field.
Click OK to submit the request.
Click Refresh Data until you see the message Active Users is Completed.
Click View Output.
Stop Oracle E-Business Suite.
If you are using Oracle E-Business Suite version 12 or later, perform the following:
# 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 |
If you are using Oracle E-Business Suite version 11.5.10 or earlier, perform the following:
# su - oraapp-user $ cd app-base-directory/SIDcomn/admin/scripts/SID_app-logical-hostname $ .adstpall.sh apps/apps $ exit # su - oradb-user $ cd db-base-directory/SID/db/9.2.0/appsutil/scripts/ \ SID_db-logical-hostname $ ./addlnctl.sh stop SID $ ./addbctl.sh stop immediate |
If a zone is being used, log out from the zone.
# exit |
Unmount the highly available local file system.
Perform this step only in the global zone.
Unplumb the Infrastructure logical IP address.
Perform this step for each logical hostname being used by Oracle E-Business Suite.
# ifconfig interface removeif logical-hostname |
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 files, perform one of the following steps.
Ensure that the node has ownership of the disk set or disk group.
For Solaris Volume Manager, type:
# metaset -s disk-set -t |
For Veritas Volume Manager, type:
# vxdg -C import disk-group # vxdg -g disk-group startall |
If the global zone is being used for Oracle E-Business Suite, type:
# mount highly-available-local-filesystem |
If a zone is being used for Oracle E-Business Suite, mount the highly available local file system on one of the zones being used.
# mount -F lofs highly-available-local-filesystem \ > /zonepath/root/highly-available-local-filesystem |
If a ZFS highly available file system is being used for Oracle E-Business Suite, perform one of the following steps.
Plumb the Oracle E-Business Suite logical hostname.
Perform this step on another node of the cluster for each logical hostname being used by Oracle E-Business Suite.
If a zone is being used, log in to the zone.
# zlogin zonename |
Start Oracle E-Business Suite.
If you are using Oracle E-Business Suite version 12 or later, 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 |
If you are using Oracle E-Business Suite version 11.5.10 or earlier, perform the following:
# su - oradb-user $ cd db-base-directory/SID/db/9.2.0/appsutil/scripts/ \ SID_db-logical-hostname $ ./addbctl.sh start $ ./addlnctl.sh start SID $ exit # su - oraapp-user $ cd app-base-directory/SIDcomn/admin/scripts/SID_app-logical-hostname $ ./adstrtal.sh apps/apps $ exit |
Test that a client can access Oracle E-Business Suite by using a Windows Client.
If you are using Oracle E-Business Suite version 12 or later, perform the following:
Log in to Standalone Diagnostics at
http://ebs-logical-host.domainname:8000/OA_HTML/DiagLogin.jsp.
Log in with Userid sysadmin and Password sysadmin. Then click Login.
Click the Basic tab and click Run All.
Some diagnostics tests might fail as Oracle E-Business Suite is not fully configured.
From the Application drop-down menu, select HTML Platform. Then click Run All Groups.
From the Application drop-down menu, select Application Object Library. Then click Run All Groups.
From the Application drop-down menu, select CRM Foundation. Then click Run All Groups.
If you are using Oracle E-Business Suite version 11.5.10 or earlier, perform the following:
Log in to Standalone Diagnostics at
http://ebs-logical-host.domainname:8000/OA_HTML/US/ICXINDEX.htm.
Log in with Userid sysadmin and Password sysadmin. Then click System Admin.
Double-click Requests and double-click Run.
Click OK on Single requests.
Type Active Users in the Name field.
Click OK to submit the request.
Click Refresh Data until you get the message Active Users is Completed.
Click View Output.
Stop Oracle E-Business Suite.
If you are using Oracle E-Business Suite version 12 or later, perform the following:
# 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 |
If you are using Oracle E-Business Suite version 11.5.10 or earlier, perform the following:
# su - oraapp-user $ cd app-base-directory/SIDcomn/admin/scripts/SID_app-logical-hostname $ .adstpall.sh apps/apps $ exit # su - oradb-user $ cd db-base-directory/SIDdb/9.2.0/appsutil/scripts/ \ SID_db-logical-hostname $ ./addlnctl.sh stop SID $ ./addbctl.sh stop immediate |
If a zone is being used, log out from the zone.
# exit |
Unmount the highly available local file system.
Perform this step in the global zone only.
Unplumb the Oracle E-Business Suite logical hostname.
Perform this step for each logical hostname being used by Oracle E-Business Suite.
# ifconfig interface removeif logical hostname |