When we were trying to apply patch we saw something peculiar in the application process. The application was working well until that moment. Even though we didnt need to state "workers" parameter during the process, we were failing because we didn't enter it.
-------------------------------------------
]$ adop phase=prepare
Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
Please wait. Validating credentials...
RUN file system context file: /u01/install/APPS/fs1/inst/apps/$SID_$HOSTNAME/appl/admin/$SID_$HOSTNAME.xml
PATCH file system context file: /u01/install/APPS/fs2/inst/apps/$SID_$HOSTNAME/appl/admin/$SID_$HOSTNAME.xml
Execute SYSTEM command : df /u01/install/APPS/fs2
Worker count determination...
[UNEXPECTED]Invalid Worker Count: 0
[UNEXPECTED]Only a maximum of 1 workers can be invoked
[UNEXPECTED]Error while validating worker count
Log file: /u01/install/APPS/fs_ne/EBSapps/log/adop/adop_20150121_040942.log
[STATEMENT] Please run adopscanlog utility, using the command
"adopscanlog -latest=yes"
to get the list of the log files along with snippet of the error message corresponding to each log file.
adop exiting with status = 2 (Fail)
-------------------------------------------
Solution:
Actually this problem faded once we were able to patch things with the following method below but we didnt understand what has caused this issue. Maybe they will find it later on.
This problem can only be handled by giving an additional property which is "workers"
adop phase=prepare workers=2
References:
1- Adworker Problem - https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=362105903059544&id=1575085.1&displayIndex=1&_afrWindowMode=0&_adf.ctrl-state=dceackd46_774#SYMPTOM
We have changed the value but prepare phase got error out because somewhere internally it is changing value from new to old.
YanıtlaSil