Loading Java stored procedures in Oracle© Databases with the loadjava utility you may encounter errors with error messages: “ORA-01536: space quota exceeded for tablespace ‘USERS” Such error indicates that the schema where the Java classes needed for the stored procedure has surpassed its tablespace quota. The easiest way to overcome this error and continue with […]
Oracle
OraSFTP connection refused
When trying to establish connection to a remote SFTP server from within Oracle Database using our product OraSFTP you may encounter connection refused error with stack trace similar to the one presented below: ORA-29532: Java call terminated by uncaught Java exception: java.sql.SQLException: SFTPException : There was a problem while connecting to <host>:<port>[recv() failed, errno = […]
OraSFTP v 1.2.6 now supports current remote folder
DidiSoft OraSFTP prior to version 1.2.6 were limited to either absolute paths or paths relative from the current user remote home directory. As of version 1.2.6 the current remote folder can be changed this way allowing for easy traversing and manipulation of complex remote folder structures. The new methods that support this functionality are: ORA_SFTP.CURRENT_DIRECTORY […]
OraRSA 1.1 offering various SHA based signings
DidiSoft OraRSA version 1.1 was released today. It offers to customize the digital signature algorithm in contrast to version 1.0 where only SHA1withRSA was available. How to use the new algorithms? In order to use the new algorithms, you must specify the algorithm needed as the last parameter of the ORA_RSA.SIGN and ORA_RSA.VERIFY methods. Available values […]
IdNotFoundException
Executing procedures from the dbms_java Oracle PL/SQL package may result in a strange IdNotFoundException like: ORA-29532: Java call terminated by uncaught Java exception: oracle.aurora.vm.IdNotFoundException: user : user or role id does not exist This is very common when granting java.io.FilePermission: call dbms_java.grant_permission(‘user’, ‘java.io.FilePermission’, ‘C:/MyFolder/ora-pgp-1.1.0.jar’, ‘read’); If you experience such error try changing the user(schema) name to Uppercase.