Inconsistent ADT attribute error

Question

Hi,
In our project we are using Object types which is used by PL/SQL. The in and out parameter of procedures will be of this type. These objects types are of nested types. These procedures are accessed by Java, in which java have Transfer Objects, and these TO's are mapped with the in and out parameters of oracle types.
Currently what we have is a schema called CDSS_LIVE, which own all the objects like tables, views, packages and types. When java access the procedures of CDSS_LIVE they are able to map the the out parameter which is of oracle types with the TO(transfer object). Now for security reasons we have created a schema/user called CDSS_USER, which has CRUD (E) privileges on CDSS_LIVE. Public synonym is created for the objects owned by CDSS_LIVE and CDSS_USER access the objects of CDSS_LIVE through these synonyms.
When java changes the data source as CDSS_USER and access the procedure of CDSS_LIVE, while mapping the out parameter of the procedure with the TO it throws an internal error as "Inconsistent ADT attribute".
We couldn't figure out what could be the reason for the error. Is there any thing to be changed in the oracle types, is these synonyms creatiug the problem or whether the read and write Sql of java need to be changed?Please help on this.
Many Thanks.

Answer 1

Hi,
Herewith i have attached the sample java code for your reference.
connection = getConnection();
//Mapping TO's with Oracle SQL Types
map = connection.getTypeMap();
map.put(SapphireConstants.KEYVALUE_TY, KeyValueSQLTO.class);
map.put(SapphireConstants.ROLE_TY, RoleSQLTO.class);
map.put(SapphireConstants.SCREENS_TY, ScreensSQLTO.class);
map.put(SapphireConstants.MENUS_TY, MenusSQLTO.class);
map.put(SapphireConstants.WORKITEM_TY, WorkItemSQLTO.class);
connection.setTypeMap(map);
//Calling the procedure
callableStatement = connection.prepareCall(
"{call PKG_ADMIN.PROC_GET_ROLE_INFO(?,?,?,?)}");
//Setting the Procedure in out parameters.
callableStatement.setString(1, roleCode);
callableStatement.setString(2, userId);
callableStatement.setString(3, mode);
callableStatement.registerOutParameter(4, Types.STRUCT,
SapphireConstants.ROLE_TY);
callableStatement.execute();
objRoleSQLTO = (RoleSQLTO) callableStatement.getObject(4);
This is how we are invoking the procedure. Hope this would help you to analyse the issue.
KEYVALUE_TY and other TY's are the object types in oracle. Now these types are owned by CDSS_LIVE, and has public synonym with the same name and CDSS_USER access these types through synonyms.
Thanks