Subscribe

SMO clone creation : sealing violation

[ Edited ]

Hi folk,

I encountered exactly the same problem as this post (I don’t think that this problem has been resolved) :

http://communities.netapp.com/message/23803#23803

However, my configuration is different :

  • W2K8R2 guest OS (on vSphere)
  • SDW 6.3 with RDM FC luns
  • Oracle11gR2 and SMO 3.1.

It seems to be an Oracle problem with the JDBC client. I found this on the web, the problem is very similar :

http://stackoverflow.com/questions/4922369/java-security-exception-sealing-violation-while-trying-to-connect-to-database

SMO logs:

2011-03-23 19:20:19,702 [RMI TCP Connection(1)-10.180.255.72] [ERROR]: SMO-13032: Cannot perform operation: Clone Create.  Root cause: ORACLE-10002: Error received from connection to Oracle database NA11: sealing violation: package oracle.jdbc.internal is sealed

com.netapp.oracle.common.OracleException: ORACLE-10002: Error received from connection to Oracle database NA11: sealing violation: package oracle.jdbc.internal is sealed

Anybody has any advices?

Mathias

Re: SMO clone creation : sealing violation

SMO 3.1P1 should resolve this. Available on NOW in mid-April.