ERROR: OPatch failed because of Path problem.Some commands below are not in your path: Command= fuser

Oracle Interim Patch Installer version 1.0.0.0.64
Copyright (c) 2011 Oracle Corporation. All Rights Reserved..

Oracle recommends you to use the latest OPatch version
and read the OPatch documentation available in the OPatch/docs
directory for usage. For information about the latest OPatch and
other support-related issues, refer to document ID 293369.1
available on My Oracle Support (https://myoraclesupport.oracle.com)

Oracle Home           : /apps/upgmgr/tech_st/10.1.2
Oracle Home Inventory : /apps/upgmgr/tech_st/10.1.2/inventory
Central Inventory     : /apps/upgmgr/inst/apps/NJVCUPG_oralnxaptst/admin/oraInventory
   from               : /apps/upgmgr/tech_st/10.1.2/oraInst.loc
OUI location          : /apps/upgmgr/tech_st/10.1.2/oui
OUI shared library    : /apps/upgmgr/tech_st/10.1.2/oui/lib/linux/liboraInstaller.so
Java location         : /apps/upgmgr/tech_st/10.1.2/jdk/jre/bin/java
Log file location     : /apps/upgmgr/tech_st/10.1.2/.patch_storage//*.log

Some commands below are not in your path:
  Command= fuser
  Extra Search Path= /sbin/fuser, /usr/sbin/fuser
  Path= /apps/upgmgr/inst/apps/NJVCUPG_oralnxaptst/admin/scripts:/apps/upgmgr/tech_st/10.1.3/perl/bin:/apps/upgmgr/tech_st/10.1.2/bin:/apps/upgmgr/apps_st/appl/fnd/12.0.0/bin:/apps/upgmgr/apps_st/appl/ad/12.0.0/bin:/apps/upgmgr/tech_st/10.1.3/appsutil/jdk/jre/bin::/apps/upgmgr/tech_st/10.1.2/bin:/usr/bin:/usr/sbin:/apps/upgmgr/tech_st/10.1.3/appsutil/jdk/jre/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/apps/upgmgr/bin:/apps/upgmgr/tech_st/10.1.2/OPatch:/apps/upgmgr/tech_st/10.1.3/appsutil/jdk/bin:/apps/upgmgr/tech_st/10.1.3/ant/bin:/apps/upgmgr/bin

ERROR: OPatch failed because of Path problem.

Solution:

I installed the psmisc package that includes the fuser program

Upgrading JDK To 7_45 - Step 3.7 Rebuild Forms Reports: Error: Collect2: Ld Returned 1 Exit Status

While Rebuild Forms and Reports Executables  Error libjvm.so: undefined reference to `pthread_cond_timedwait@GLIBC_2.3.2'

1) All required patches per Note 1467892.1 have been applied

Critical patch to be applied is 16271876 PROVIDE LIBJVM-STUB.SO FOR RELINKING OF FORMS WITH JDK 1.7

2)  Confirm the following reflects correct information:

$ $ADJVAPRG -version
$ echo $CLASSPATH
$ $AFJVAPRG -version
$ echo $AF_CLASSPATH

applmgr@xxxx:/u01/xxxx/applmgr/apps/tech_st/10.1.2/forms/lib>$ADJVAPRG -version
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) Server VM (build 23.25-b01, mixed mode)


applmgr@xxxx:/u01/xxx/applmgr/apps/tech_st/10.1.2/reports/lib>$AFJVAPRG -version
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) Server VM (build 23.25-b01, mixed mode)

3) Please create the below softlink:

cd $ORACLE_HOME/lib/stubs
ln -s libjvm-1.7-stub.so libjvm.so

Retry the make command.

(Doc ID 1569998.1)

OID start and Stop Locations

To start DB, follow the steps in the order given below:

1. Set the environment variables (if they are not already set) by executing the below commands:
    a. export ORACLE_HOME = /app/oracle/product/11.2.0/dbhome_1. Path of the base directory of database
    b. export PATH = /app/oracle/product/11.2.0/dbhome_1/bin: $PATH.  The bin  directory of ORACLE_HOME
    c. export LD_LIBRARY_PATH=/app/oracle/product/11.2.0/dbhome_1/lib. The lib folder of ORACLE_HOME
    d. export ORACLE_SID=orcl. Database SID
PS: All these variables can be permanently set in the session by writing these commands to ".profile" file of the unix user.
2. Start the database listener by executing the below command:
    a. lsnrctl start
    b.startup

OID Services Start Location:

Steps to Start OID using OPMN

1. Set the environment variables required to start OID by executing the below commands:

    a. export ORACLE_HOME=/home/oracle/Oracle/Middleware/Oracle_IDM1. Path of the base directory of Oracle Internet Directory

    b. export ORACLE_INSTANCE=/home/oracle/Oracle/Middleware/asinst_1. Path of the instance directory created while installation
    c. export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/ldap/bin:$ORACLE_INSTANCE/bin:$PATH. 
    d. export TNS_ADMIN=$ORACLE_INSTANCE/config
PS: Make sure the first directory of PATH variable is always bin directory of ORACLE_HOME as defined above. You might get errors while executing ldap commands if this is not maintained.
2. Start OID by executing
    a. opmnctl startall
You can check the status of OID by executing opmnctl status to verify if the status is Alive i.e., if OID is started.
3.Stop OID by executing
opmnctl stopall

Example:

[oemora@lnxdbtst > /apps/oemora]$ export ORACLE_HOME=/apps/oemora/Oracle/Middleware/Oracle_IDM1
[oemora@lnxdbtst > /apps/oemora]$ export ORACLE_INSTANCE=/apps/oemora/Oracle/Middleware/asinst_1
[oemora@lnxdbtst > /apps/oemora]$ export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/ldap/bin:$ORACLE_INSTANCE/bin:$PATH
[oemora@lnxdbtst > /apps/oemora]$ export TNS_ADMIN=$ORACLE_INSTANCE/config
[oemora@lnxdbtst > /apps/oemora]$ cd $ORACLE_INSTANCE
[oemora@lnxdbtst > /apps/oemora/Oracle/Middleware/asinst_1]$ ls
auditlogs  bin  config  diagnostics  EMAGENT  OHS  OID  OVD  tmp
[oemora@lnxdbtst > /apps/oemora/Oracle/Middleware/asinst_1]$ cd bin
[oemora@lnxdbtst > /apps/oemora/Oracle/Middleware/asinst_1/bin]$ ls
opmnctl
[oemora@lnxdbtst > /apps/oemora/Oracle/Middleware/asinst_1/bin]$ opmnctl status

Processes in Instance: asinst_1
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status
---------------------------------+--------------------+---------+---------
ohs1                             | OHS                |   31898 | Alive
ovd1                             | OVD                |   31897 | Alive
oid1                             | oidldapd           |   32217 | Alive
oid1                             | oidldapd           |   32245 | Alive
oid1                             | oidmon             |   31896 | Alive
EMAGENT                          | EMAGENT            |   31895 | Alive


[oemora@lnxdbtst > /apps/oemora/Oracle/Middleware/asinst_1/bin]$

Steps to start Web logic Admin and Managed Server

1. To start Weblogic Admin Server, Navigate to /bin directory and execute:

    a. ./startWeblogic

2. To start Managed Server, Navigate to /bin directory and execute:

   a. ./startManagedWeblogic

[oemora@lnxdbtst > /apps/oemora/Oracle/Middleware/user_projects/domains/base_domain/bin]$ ls -ltr

total 68

drwxr-x--- 2 oemora oemora  4096 Jul 21 16:25 service_migration

drwxr-x--- 2 oemora oemora  4096 Jul 21 16:25 server_migration

drwxr-x--- 2 oemora oemora  4096 Jul 21 16:25 nodemanager

-rwxr-x--- 1 oemora oemora  1979 Jul 21 16:25 stopWebLogic.sh

-rwxr-x--- 1 oemora oemora  5697 Jul 21 16:25 startWebLogic.sh

-rwxr-x--- 1 oemora oemora  2415 Jul 21 16:25 stopManagedWebLogic.sh

-rwxr-x--- 1 oemora oemora  3203 Jul 21 16:25 startManagedWebLogic.sh

-rwxr-x--- 1 oemora oemora 16132 Jul 21 16:25 setDomainEnv.sh

-rw------- 1 oemora oemora 20100 Oct 20 06:18 nohup.out