Hi Daniel,
Coba refer artikel ini dari metalink :
Subject: Unable To Start OPMN Managed Process Doc ID:
Note:331969.1 Type: PROBLEM Last Revision Date: 23-AUG-2005
Status: MODERATED function setmlsrch (s) { if
(typeof(top.query) != "undefined")
top.query.document.forms[0].p_text.value=s; } In this Document
Symptoms
Changes
Cause
Solution
---------------------------------
This document is being delivered to you via Oracle Support's Rapid
Visibility (RaV) Rapid Visibility (RaV) process, and therefore has not been
subject to an independent technical review.
Applies to: Oracle Application Server 10g Enterprise Edition - Version:
9.0.4.0 to 10.1.2.0
Oracle Containers for J2EE - Version: 9.0.4.1.0
This problem can occur on any platform.
Symptoms An OPMN managed process, such as an OC4J instance, isn't
available and can't be stopped or started using "opmn" commands. "opmnctl
status -l" shows the process as always being in a status of "Stop" and the
fuctionality of the managed process insn't available. The ipm.log shows that
OPMN is constantly trying to stop but never start the managed process.
For example, the OC4J_SECURITY isn't available and acessing SSO related
pages from the browser results in the following error being returned to the
browser:
Internal Server Error
=====================
The server encountered an internal error or misconfiguration
and was unable to complete your request. Please contact the
server administrator, [EMAIL PROTECTED] and inform them of the
time the error occurred, and anything you might have done that
may have caused the error.
More information about this error may be available in the server
error log.
The "opmnctl status" command shows:
% opmnctl status
Processes in Instance: myas_infra.myhost.myfdomain.com
-------------------+--------------------+-------+---------
ias-component | process-type | pid | status
-------------------+--------------------+-------+---------
OID | OID | 7504 | Alive
HTTP_Server | HTTP_Server | 7500 | Alive
OC4J | OC4J_SECURITY
| 18297 | Stop
dcm-daemon | dcm-daemon | 24676 | Alive
LogLoader | logloaderd | N/A | Down
The OC4J log for the OC4J_SECURITY instance (i.e. located at
${ORACLE_HOME}/opmn/logs) shows:
Error: Unable to find java:comp/ServerAdministrator: Lookup error:
javax.naming.Authentication
Exception:Invalid username/password for default (admin); nested exception is:
javax.naming.AuthenticationException: Invalid username/password for default
(admin)
com.evermind.client.orion.AdminCommandException: Unable to find
java:comp/ServerAdministrator:
Lookup error: javax.naming.
The "ipm.log" (located at ${ORACLE_HOME}/opmn/logs) shows:
05/08/08 11:53:54 [4] Stopping Process: OC4J~OC4J_SECURITY~default_island~1
(82772520:18297)
05/08/08 11:53:54 [4] [libopmnoc4j] Forcefully Terminating Process:
OC4J~OC4J_SECURITY~default_island~1 (82772520:18297)
05/08/08 11:57:54 [4] Stopping Process: OC4J~OC4J_SECURITY~default_island~1
(82772520:18297)
05/08/08 11:57:54 [4] [libopmnoc4j] Forcefully Terminating Process:
OC4J~OC4J_SECURITY~default_island~1 (82772520:18297)
05/08/08 12:03:54 [4] Stopping Process: OC4J~OC4J_SECURITY~default_island~1
(82772520:18297)
05/08/08 12:03:54 [4] [libopmnoc4j] Forcefully Terminating Process:
OC4J~OC4J_SECURITY~default_island~1 (82772520:18297)
05/08/08 12:11:54 [4] Stopping Process: OC4J~OC4J_SECURITY~default_island~1
(82772520:18297)
...
Changes The server may have failed and rebooted unexpectedly resulting
in all the OPMN managed processes that were running before the server crash
having died abnormally. Cause On being restarted after a failure, OPMN
uses information in the ${ORACLE_HOME}/opmn/states directory to attempt
recovery. From the various files in the "states" directory it determines if a
process ID (PID) of a processes it was managing before the abnormal exit is
still running.
If such a process is found, OPMN will first attempt to reconnect to the
process and determine it's condition (with an appropriate OPMN "ping"
message). In the event a managed process cannot be contacted it will attempt
to terminate the process (first gracefully and then using "kill -9") and
restart it.
In rare cases following a restart, it is possible that by pure chance:
a process exists which matches the PID of a previously managaged OPMN process
(ie a current PID matches one listed in a file within the
$ORACLE_HOME/opmn/states directory).
the process running with this PID is NOT an OPMN managed process nor owned
by the operating system account that was used to install Application Server
and which governs the permissions of the current OPMN process.
As a result OPMN cannot communicate meaningfully with the OPMN managed
process.
In the case of a managed OC4J instance, the rogue process is not
responding to RMI requests which result in the following error message in the
respective OC4J log file:
Error: Unable to find java:comp/ServerAdministrator: Lookup error:
javax.naming.AuthenticationException:
Invalid username/password for default (admin); nested exception is:
javax.naming.AuthenticationException: Invalid username/password for default
(admin)
com.evermind.client.orion.AdminCommandException: Unable to find
java:comp/ServerAdministrator:
Lookup error: javax.naming.
NOTE:
The above information looks as if it has been logged by the OC4J process
itself, which is misleading since the running PID is not an OC4J process.
However, the OPMN administration command is itself an RMI client program and
therefore logs it's diagnostics to the same log file as the server which is
why the above entries appear.
After three failed OPMN forward pings, OPMN detects that the OC4J
instance is not responding.
It then tries to issue an "opmnctl stopproc process-type=OC4J_SECURITY"
command, which will also fail since there is nothing listening for RMI
connections at the expected RMI port. OPMN next tries to forcefully kill the
process but, as the rogue process was not started by the same O/S account,
OPMN does not have appropriate priviliges and the "kill -9" it invokes is
unsuccessful.
At this point, OPMN will make no further attempt to communicate with the
process and is left with no option other than continuously trying
(unsuccessfully) to to kill the rogue PID, a behavior which can be validate
from information in the "ipm.log" file.
Solution To implement the solution, please execute the following
steps:
Fully stop opmn and all oc4j instances.
At this point there will be no oc4j managed processes running, so there
should be need for no files in $ORACLE_HOME/opmn/logs/state directory, so it
should be safe to remove these.
For safety, rename the current $ORACLE_HOME/opmn/logs/state directory and
create a new empty state directory in it's place:
% cd $ORACLE_HOME/opmn/logs
% mv state state.old
% mkdir state
Restart OPMN and the desired OPMN managed processes:
% opmnctl start
% opmnctl startproc process-type=OID
% opmnctl startproc process-type=HTTP_Server
% opmnctl startproc process-type=OC4J_SECURITY
Confirm that all processes have started correctly using "opmnctl status -l"
The OC4J process should have a status of "Alive" and it's port section should
show valid ports for ajp, rmi and jms.
After confirming all processes have started and validating that the
functionality of all opmn managed processes, the "state.old" directory can
then be removed.
NOTE:
This behavior is unlikely to occur with Application Server version 10.1.3
onward, where OPMN checks to see if any files in the opmn/states directory
preceded the last system startup.
Andrew
[EMAIL PROTECTED] wrote: saya sudah
cek, privilleges untuk folder tersebut.
semua folder yang berada di dalam folder ORACLE HOME Infrastructure saya,
ownernya = oracle group = oinstall
saya startup infra menggunakan user oracle
process di back ground juga tidak ada.
setelah saya lihat file log nya
di [ORACLE HOME]/opmn/logs/ipm.log
muncul error seperti ini :
06/06/15 09:38:50 [4] Request 27 Started. Command: start
06/06/15 09:58:52 [4] Starting Process:
OC4J~OC4J_SECURITY~default_island~1 (432996420:0)
06/06/15 09:58:54 [4] Request 27 Completed. Command: start
06/06/15 09:58:54 [4] Stopping Process:
OC4J~OC4J_SECURITY~default_island~1 (432996420:5102)
06/06/15 09:58:54 [4] [libopmnoc4j] Process Stop Error:
OC4J~OC4J_SECURITY~default_island~1 (432996420:5102)
06/06/15 09:58:54 [4] [libopmnoc4j] Forcefully Terminating Process:
OC4J~OC4J_SECURITY~default_island~1 (432996420:5102)
06/06/15 09:58:56 [4] Process Stopped: OC4J~OC4J_SECURITY~default_island~1
(432996420:5102)
saya coba cek juga di file [ORACLE HOME]/opmn/logs/orcl10g
muncul error seperti ini
--------
06/06/14 16:20:38 Dependency check
--------
Error - ORA-28000: the account is locked
orcl10g is available
SUCCEEDED
sebagai tambahan SID = orcl10g
Saya juga sudah coba unock user nya dengan oidpasswd.
gimana cara trace apa yang dijalankan saat menjalankan OC4J_SECURITY yah ?
Thnx
Daniel
nsubscribe
We Made
Changes
Your Yahoo! Groups email is all new.
Learn More
Share Feedback
Recent Activity
18
New Members
Visit Your Group
SPONSORED LINKS
Membership database software
Database mortgage software
Pda database software
Database management software
Oracle database administration
Oracle database management
.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
[Non-text portions of this message have been removed]
------------------------ Yahoo! Groups Sponsor --------------------~-->
See what's inside the new Yahoo! Groups email.
http://us.click.yahoo.com/2pRQfA/bOaOAA/yQLSAA/PhFolB/TM
--------------------------------------------------------------------~->
--
-----------I.N.D.O - O.R.A.C.L.E---------------
Keluar: [EMAIL PROTECTED]
Website: http://indo-oracle.blogspot.com
Mirror: http://indooracle.wordpress.com
-----------------------------------------------
Bergabung dengan Indonesia Thin Client User Groups,
Terminal Server, Citrix, New Moon Caneveral, di:
http://indo-thin.blogspot.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/indo-oracle/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
