Problem with starting concurrent process post-cloning, applying patch 6372396
Hi all!
I'm working with a cloned EBS system on HPUX. We have done this process many times before, but this time around the concurrent processes did not start up when the concurrent manager was re-started. The internal manager starts but doesn't start the other processes.
I found a patch that sounded like it might apply that addressed a known bug in 11.5.10 which is the version we're on. But now I can't perform the post-patch steps because there is one step that zips up all of the new binaries installed in the apps layer so that they can be moved to the database layer. I guess there is no 'zip' utility on the server for the admkappsutil.pl process to access. I get a similar error to the one reported in note
I'm working with a cloned EBS system on HPUX. We have done this process many times before, but this time around the concurrent processes did not start up when the concurrent manager was re-started. The internal manager starts but doesn't start the other processes.
I found a patch that sounded like it might apply that addressed a known bug in 11.5.10 which is the version we're on. But now I can't perform the post-patch steps because there is one step that zips up all of the new binaries installed in the apps layer so that they can be moved to the database layer. I guess there is no 'zip' utility on the server for the admkappsutil.pl process to access. I get a similar error to the one reported in note
Tagged:
0