1 of 1 people found this helpful
Hi ....Is this problem occurs for all the Solaris boxes like sol10 ,8,9 (x86 64 ,sparc) boxes?or it is specific to only solaris Sparc servers....one more thing can you extract the last deployed patch info & deploy the same patch on differnt solaris machine to finding the root cause because some times some faulty patch is the cause of system failure but this is very rare so plese confirm the same by deploying it on other box? becuase i have seen such scenario in AIX where if you deploy that particular fileset it will corrupt your box?
& i am sure that your agent is also not responding.....dioes your solaris sparc box contained '/OPT drive?
Please share your finding it will help us to narow down the issue:)
The error you are seeing is coming back from the solaris patch command. I'd suggest having a look around on the internet at some related articles or even contacting Oracle for support:
The job is still running in the commit stage because it never returned after a reboot and BSA is waiting for the agent to respond.