Non text filters in Oracle Text 9.2 (W2K)

It appears that the INSO filters do not work very well - certainly not out of the box. Other than the plain text files I have not been able to index any other documents. Judging by the amount of traffic on this I don't hold up much hope, since I am getting the ubiquitous(undebuggable!!):
ORA-20000: Oracle Text error:
DRG-11207: user filter command exited with status 1
ORA-06512: at "CTXSYS.DRUE", line 157
ORA-06512: at "CTXSYS.CTX_DOC", line 609
ORA-06512: at line 3
This is a show stopper for us since we have no control of the documents and really require close to 100% coverage of at least the supported types -- what are the experiences of folks here in general -- should we abandon this now?
-- simon (mailto:[email protected])

Simon -
do you know what files are causing the errors?
the INSO filter tends to give this error if it tries to process XML files. In the current version, you will need to identify XML files in some other manner (eg by file extension when loading) and use a FORMAT column to mark these rows as TEXT - which will cause the filter to ignore them and they will be indexed as plain text.
In a future version the INSO filter will automatically recognize and skip XML files, which should solve the problem.
- Roger

Similar Messages

Error in Get Next Non-Text Sibling for XML without CR at end of tag

Hallo all,
I'm having a strange error parsing XML files with labview. I have an XML file in one single line, without CR at end of each tag. A normal browser or XML parsing tool is capable to read it, but not with Labview.
The error I have is with "Get Next Non-Text Sibling.vi", which internally fails to read Type property (Error -2630, Property Node (arg 1) in NI_XML.lvlib:Get Next Non-Text Sibling.vi->XML Get Siblings Childs Nodes.vi->Encode data to label (Path).vi).
Labview XML parser works if I add a CR at each tag/node.
I'm quite sure this is a labview bug. A workaround I have found is to open the file, then save the file with Save File (Pretty Print) method and reopen it again, but it is time-consuming and I would like to avoid it.
Regards,
Daniele
Solved!
Go to Solution.
Attachments:
xmlwithnoCR.xml.txt ‏1 KB

Which node do you pass to XML Get Siblings Child Nodes.vi ? That is also important.
I can imagine the following scenario causing your problem: Your input node has a child node C,, but this child node has no siblings. Get Next Non-Text Sibling.vi will fail in this case. If you put a <CR> at the right position in your XML you create a text node with content <CR>. If this text node is a sibling of child C then Get Next Non-Text Sibling.vi still won't return anything but no error should occur. IMHO this is expected behavior. You can however implement your own version of Get Next Non-Text Sibling.vi. Use the Next Sibling property and check if it returns a valid refnum.

Bug in NI_XML.lvlib:Get First Non-Text Child.vi

This VI fails to handle the output of the first Property Node on its block diagram. Here's a screenshot of the BD in LV 2013 SP1:
Here's a fixed version:

I agree with David, but I hesitate to call it a bug. Spewing meaningless errors into unrelated parts of your code is on the NI-sanctioned Error-handling Greatest Hits album so it is probably intentional.
There are 4 scenarios here to consider:
1) Bad reference passed in
2) Good reference, no child nodes
3) Good reference, no non-text child nodes
4) Good reference, 1 or more non-text child nodes.
What are the outputs:
1) Error message from first PN, boolean false, NotARefnum
2) Error message from second PN, boolean false, NotARefnum
3) No Error, boolean false, NotARefnum
4) No Error, boolean true, valid Refnum
How is an outsider suppposed to know from the error messages which of 1 & 2 happened? You have to know what goes on inside and see which node threw the error. Having to know the insides of a VI to decipher an error message is not good API design IMO.
What should happen in my opinion is the following:
Input check, invalid refnum throws an error clearly indicating "Bad refnum input"
The output refence would only be valid in case 4, so the boolean is redundant, but I would include it as a usability measure. No errors should be thrown in cases 2-4, no text nodes versus no nodes at all is almost certainly a distinction without a difference in this case.
David's fix cleans up the unhelpful error message being thrown during an unsuccessful search of a valid refnum. I would add an input validation check in the interest of providing a useful error message and not the "random property called with bad reference" error.

Verizon Webmail Long Non-text windows do not have vertical scrollbar

When I get a non-text message in Verizon Webmail that requires me to scroll down to see it all, there is no vertical scrollbar. When I display this same message in IE9, the scrollbar appears. I think this is another problem in V30/V31 as I did not see this problem before upgrading.

As a test to see whether a Reset might help, you could try this (takes about 3 minutes):
'''Create a new Firefox profile'''
A new profile will have your system-installed plugins (e.g., Flash) and extensions (e.g., security suite toolbars), but no themes, other extensions, or other customizations. It also should have completely fresh settings databases and a fresh cache folder.
Exit Firefox and start up in the Profile Manager using Start > search box (or Run):
firefox.exe -P
''Do not delete anything here.''
Any time you want to switch profiles, exit Firefox and return to this dialog.
Click the Create Profile button, choose a name like Aug7, and skip the option to change the folder location. Then start Firefox in the new profile you created.
Does Verizon mail work differently in the new profile?
When returning to the Profile Manager, you might be tempted to use the Delete Profile button. But... it's a bit too easy to accidentally delete your "real" profile, so I recommend resisting the temptation. If you do want to clean up later, I suggest making a backup of all your profiles first in case something were to go wrong.

Stripping non text characters

I am generating a fixed format file from data out of a MSSQL DB ( that i have read only permissions) that is an import file to another program ( which i also don't have access to source code) . My problem is that some of the DB data has non text characters which causes the program that is accepting the data to throw
java.io.IOException: java.lang.IllegalArgumentException: The char '0x19' in 'whatEver String that has a bad character' is not a valid XML character
My solution was
 for( int i = 0; i < myString.length(); i++){
 b = (byte)myString.charAt(i);
 if( b > 31 && b <127)
 sb.append( blk.charAt( i));
 }

Better solution: Get the encoding right. At some point your code (or some other application) does some conversion from binary (byte[]/InputStream/OutputStream/...) to text (char[]/Reader/Writer/String/...). That place does so incorrectly.
Find out the encoding of the binary data and apply that when transforming.
Read [this excellent introduction into Unicode|http://www.joelonsoftware.com/articles/Unicode.html].

Java.sql.SQLException: Non supported character set: oracle-character-set-860

Hi,
I am working on resultset.updateRow() and found some problem.
I've tried the same jsp page on 2 WebLogic server
one is on a Solaris Platfoem and another is on a NT platform
On NT Platform it seems to be OK and update the database successfully.
On Solaris, on error message on WebLogic log but error found in the JDBC log
java.sql.SQLException: Non supported character set: oracle-character-set-860
P.S. both jsp page connection to the same database server Oracle 8
The testing JSP page:
<%@ page language="java" import="java.sql.*, oracle.jdbc.driver.*,
java.util.*, javax.sql.*" %>
<html>
<head>
<title>Weblogic Oracle Testing - Store Procedure</title>
<meta http-equiv="Content-Type" content="text/html; charset=big5">
</head>
Oracle Connection Testing
 
<body bgcolor="#FFFFFF">
<%
Connection conn = null;
Statement stmt = null;
ResultSet rs = null;
String sql;
Driver myDriver =
(Driver)Class.forName("oracle.jdbc.driver.OracleDriver").newInstance();
try {
conn=DriverManager.getConnection("jdbc:oracle:thin:sa/z0y1z2y3@oradev01:1521
:DEV01a");
DatabaseMetaData DBMetaData = conn.getMetaData();
boolean support1 =
DBMetaData.supportsResultSetType(ResultSet.TYPE_SCROLL_SENSITIVE);
boolean support2 =
DBMetaData.supportsResultSetType(ResultSet.CONCUR_UPDATABLE);
%>
<%=support1%>
<%=support2%>
<%
//create a statement
stmt = conn.createStatement(ResultSet.TYPE_SCROLL_INSENSITIVE,
ResultSet.CONCUR_UPDATABLE);
//execute a query
rs = stmt.executeQuery("SELECT tbl_web_trx_hdr.* FROM tbl_web_trx_hdr");
int concurrency = rs.getConcurrency();
int type = rs.getType();
%>
concurrency: <%=concurrency%>
type: <%=type%>
<%
rs.moveToInsertRow();
rs.updateString("org_idx", "CCC");
rs.updateString("trx_num", "ABC2");
rs.updateDate("trx_dte", java.sql.Date.valueOf("2001-06-01"));
rs.updateString("description", "123");
rs.insertRow();
rs.updateRow();
} catch (SQLException e)
{ System.out.println("SQLMessage: " + e.getMessage());
finally
{ rs.close();
stmt.close();
conn.close(); }
%>
</body>
</html>
Please help
regards,
Fannie

yupp finally i got the solution. . .
I was using connection from tomcat connection pooling.
Hence, even though i was setting the classes12.jar and nls_charset12.jar in the classpath and compiling, -In runtime tomcat was using its own classes in the common/lib folder. . .(which might not support oracle-character-set-178.)
So just added this jars into the common/lib of tomcat instead of web-inf/lib of my project
and things began working. . .
Thanks for the hint jshell. . .

Non supported character set: oracle-character-set-41

Hi everyone,
I have a issue while passing a VARRAY from my Java Class to Stored Procedure.
TYPE ERR_DATA_ARRAY AS VARRAY(100) OF VARCHAR2(1000);
In my code i have used ArrayDescriptor and ARRAY class of oracle.
When i run my program in eclipse i get following exception:-
java.sql.SQLException: Non supported character set: oracle-character-set-41
at oracle.gss.util.NLSError.throwSQLException(NLSError.java:46)
at oracle.sql.CharacterSetUnknown.failCharsetUnknown(CharacterSetFactoryThin.java:171)
at oracle.sql.CharacterSetUnknown.convert(CharacterSetFactoryThin.java:135)
at oracle.sql.CHAR.<init>(CHAR.java:159)
at oracle.sql.CHAR.<init>(CHAR.java:183)
at oracle.jdbc.oracore.OracleTypeCHAR.toDatum(OracleTypeCHAR.java:161)
at oracle.jdbc.oracore.OracleType.toDatumArray(OracleType.java:166)
at oracle.jdbc.oracore.OracleTypeCHAR.toDatumArray(OracleTypeCHAR.java:208)
at oracle.sql.ArrayDescriptor.toOracleArray(ArrayDescriptor.java:1517)
at oracle.sql.ARRAY.<init>(ARRAY.java:117)
at com.niit.slims.common.ejb.Array_test.test(Array_test.java:52)
at com.niit.slims.common.ejb.Array_test.main(Array_test.java:20)
I have added ojdbc14.jar.And my working jdk is jdk1.4.
Plz help
Edited by: user10569173 on Dec 8, 2011 3:58 AM

I am not an expert here,
but it seems that since you are using ojdbc14.jar you may actually need the
nls_charset12.jar
instead of the one I suggested previously.
Regards
Peter

Java.sql.SQLException: Non supported character set: oracle-character-set-17

Hi,
i am trying to execute an Oracle procedure from JDBC. The procedure accepts a Nested table as an input parameter. Definition of the nested table is given below.
Database – Oracle 10g.
Application Server – JBOSS 4.2.1
I get the following exception._
java.sql.SQLException: Non supported character set: oracle-character-set-178
at oracle.gss.util.NLSError.throwSQLException(NLSError.java:46)
I. JDBC Code_
Session s = HibernateUtil.getSession();
Transaction tr = s.beginTransaction();
con=s.connection();
oraConn = (OracleConnection) con.getMetaData().getConnection();
TableObject obj=new TableObject();
obj.setId(new Integer(123));//Tested ok, stroing in DB
obj.setDescr("test"); // this line throwing error
obj.setCre_user(new Integer(456));
obj.setUpd_user(new Integer(789));
obj.setXfr_flag("Y");
ArrayList al=new ArrayList();
al.add(obj);
Object[] objAray = al.toArray();
ArrayDescriptor arrayDescriptor =ArrayDescriptor.createDescriptor("T_TEST_SYN", oraConn);
ARRAY oracleArray = new ARRAY(arrayDescriptor, oraConn, objAray);
cs = (OracleCallableStatement)oraConn.prepareCall("call PKG_OBJ_TEST.accept_ui_input(?) ");
cs.setArray(1, oracleArray);
cs.execute();
tr.commit();
public class TableObject implements SQLData{
private String sql_type = "T_OBJ_TEST";
private int id;
private String descr;
//private Date cre_date;
private int cre_user;
//private Date upd_date;
private int upd_user;
private String xfr_flag;
public TableObject()
public TableObject (int id,String descr,int cre_user,int upd_user,String xfr_flag)
// this.sql_type = sql_type;
this.id = id;
this.descr = descr;
// this.cre_date=cre_date;
this.cre_user=cre_user;
//this.upd_date=upd_date;
this.upd_user=upd_user;
this.xfr_flag=xfr_flag;
public String getSQLTypeName() throws SQLException {
return "T_OBJ_TEST";
public void readSQL(SQLInput stream, String typeName) throws SQLException {
//sql_type = typeName;
id=stream.readInt();
descr=stream.readString();
//cre_date=stream.readDate();
cre_user=stream.readInt();
//upd_date=stream.readDate();
upd_user=stream.readInt();
xfr_flag=stream.readString();
public void writeSQL(SQLOutput stream) throws SQLException {
try {
stream.writeInt(this.id);
System.out.println("Iddddd");
stream.writeString(this.descr);
System.out.println("Desccccccccccccccc"+":"+descr);
//stream.writeDate(cre_date);
stream.writeInt(this.cre_user);
System.out.println("userrrrrrrrrrrr");
//stream.writeDate(upd_date);
stream.writeInt(this.upd_user);
System.out.println("upd uiserrrrrrrrrrr");
stream.writeString(this.xfr_flag);
System.out.println("flagggggggggggggggggggg"+xfr_flag);
}catch (SQLException se) {
System.out.println("Table object sql exception");
se.printStackTrace();
catch (Exception e) {
System.out.println("Table object exception");
* @return the id
public int getId() {
return id;
* @param id the id to set
public void setId(Object obj) {
Integer iobj= (Integer)obj;
this.id =iobj.intValue();
* @return the descr
public String getDescr() {
System.out.println("getDescr "+descr);
return descr;
* @param descr the descr to set
public void setDescr(Object obj) {
System.out.println("setDescr "+obj);
String sobj = (String)obj;
this.descr=sobj.toString();
System.out.println("setDescr "+obj);
* @return the cre_user
public int getCre_user() {
return cre_user;
* @param cre_user the cre_user to set
public void setCre_user(Object obj) {
Integer iobj=(Integer)obj;
this.cre_user = iobj.intValue();
* @return the upd_user
public int getUpd_user() {
return upd_user;
* @param upd_user the upd_user to set
public void setUpd_user(Object obj) {
Integer iobj=(Integer)obj;
this.upd_user = iobj.intValue();
* @return the xfr_flag
public String getXfr_flag() {
return xfr_flag;
* @param xfr_flag the xfr_flag to set
public void setXfr_flag(Object obj) {
this.xfr_flag = (String)xfr_flag;
II. Oracle database object details
Details of Object and Nested table created in the database.
T_TEST_SYN is a public synonym created for t_tab_obj_test
CREATE OR REPLACE TYPE t_obj_test as object (
id number(10),
descr varchar2(100),
--cre_date date,
cre_user number(10),
--upd_date date,
upd_user number(10),
xfr_flag varchar2(1),
CONSTRUCTOR FUNCTION t_obj_test ( id IN NUMBER DEFAULT NULL,
descr IN varchar2 default null,
--cre_date in date      default null,
cre_user in number default null,
--upd_date in date      default null,
upd_user in number default null,
xfr_flag in varchar2 default null ) RETURN SELF AS RESULT ) ;
CREATE OR REPLACE TYPE BODY t_obj_test as
CONSTRUCTOR FUNCTION t_obj_test ( id IN NUMBER DEFAULT NULL,
descr IN varchar2 default null,
--cre_date in date      default null,
cre_user in number default null,
--upd_date in date      default null,
upd_user in number default null,
xfr_flag in varchar2 default null ) RETURN SELF AS RESULT IS
BEGIN
SELF.id := id ;
SELF.descr := descr ;
--SELF.cre_date := cre_date ;
SELF.cre_user := cre_user ;
--SELF.upd_date := cre_date ;
SELF.upd_user := cre_user ;
SELF.xfr_flag := xfr_flag ;
RETURN ;
END ;
END ;
CREATE OR REPLACE TYPE t_tab_obj_test AS TABLE OF t_obj_test ;
CREATE OR REPLACE PACKAGE BODY PKG_OBJ_TEST AS
PROCEDURE accept_ui_input ( p_tab_obj_test in T_TAB_OBJ_TEST ) IS
BEGIN
FOR row IN p_tab_obj_test.First .. p_tab_obj_test.LAST
LOOP
INSERT INTO OBJ_TEST ( ID,
DESCR,
CRE_DATE,
CRE_USER,
UPD_DATE,
UPD_USER,
XFR_FLAG )
VALUES ( p_tab_obj_test(row).ID,
p_tab_obj_test(row).DESCR,
NULL,
p_tab_obj_test(row).CRE_USER,
NULL,
p_tab_obj_test(row).UPD_USER,
p_tab_obj_test(row).XFR_FLAG ) ;
END LOOP ;
COMMIT ;
END accept_ui_input ;
END PKG_OBJ_TEST;
/

Check your CLASSPATH enviroment variable. Try to add something like c:\Ora10g\jlib\orai18n.jar.
From "JDBC Developers Guide and Reference":
orai18n.jar
Contains classes for globalization and multibyte character sets support
This solved the same error in my case.

Non supported character set: oracle-character-set-560

Hi,
I created a page and its working fine. In another database when i create a page error occurs as
Non supported character set: oracle-character-set-560
Thanks in Advance,
Jegan

Hi,
Refer to the thread...Non supported character set: oracle-character-set-46??? - pls help!
it has the solution for this...
Thanks,
Gaurav

Non supported character set: oracle-character-set-46??? - pls help!

Hello,
I'm running Hello World example. Could you please help me to resolve "Non supported character set: oracle-character-set-46" error i got?!?!
This seems to be nls_character problem but somehow i can't figure out what and where should be changed to solve the issue :( .
thnks,

Hello all,
thanks for nothing!
Actually i resolved issue. But still i don't understand the problem and why solution i did worked out.
Here is the solution i hope that for somebody somehow it will be usefull:
1) open ... jdevbin\jdev\lib\ext\jrad\config\jrad.properties
2) and comment out both rows:
#JRAD.APPS_JDBC_LIB14={JRAD.APPS_LIBRT_DIR}/ojdbc14.jar;{JRAD.APPS_LIBRT_DIR}/nls_charset12.zip
#JRAD.APPS_JDBC_LIB13={JRAD.APPS_LIBRT_DIR}/classes12.jar;{JRAD.APPS_LIBRT_DIR}/nls_charset12.zip
3)closed jdeveloper and opened again
brgds.

Non supported character set: oracle-character-set-171' in java XSU

I cannt update object type CHAR data in table cause Non
supported character set: oracle-character-set-171'
NLS lang UTF-8
database language WIN-1251

I think it is a bug at JDBC-OCI Driver.
Now I am useing setPlsqlIndexTable to transfer
a var to PLSQL procedure, and want to
retrieve it from out parameter.
When I transfer English characters, it can
work correctly, but if I transfer Japnese or
Chinese characters, the disorderly characters
were returned. I have not resolved this problem
yet. Who can tell me how to resolve it.

SQLException: Non supported character set: oracle-character-set-178

Hello,
I run a j2ee application on the Sun J2EE Application server.
I migrated to 0racle 9.2.0.3.
I have an ejb making a connexion with the oci driver
and in it I manipulate XMLType:
PreparedStatement pst = cnx.prepareStatement(sql);
XMLType xt = XMLType.createXML(cnx, "<ENTETE></ENTETE>");
pst.setObject(1, xt);
I've got an exception on the setObject method :
java.sql.SQLException: Non supported character set: oracle-character-set-178
at oracle.gss.util.NLSError.throwSQLException(NLSError.java:46)
at oracle.sql.CharacterSetUnknown.failCharsetUnknown(CharacterSetFactory
Thin.java:171)
at oracle.sql.CharacterSetUnknown.convert(CharacterSetFactoryThin.java:1
35)
at oracle.xdb.XMLType.getBytesString(XMLType.java:1687)
at oracle.xdb.XMLType.getBytesValue(XMLType.java:1623)
at oracle.xdb.XMLType.toDatum(XMLType.java:431)
at oracle.jdbc.driver.OraclePreparedStatement.setORAData(OraclePreparedS
tatement.java:2745)
at oracle.jdbc.driver.OraclePreparedStatement.setObject(OraclePreparedSt
atement.java:3208)
I have the nsl_charset12.zip , ojdbc14.jar,xdb.jar,xmlparserv2.jar in the J2EE_CLASSPATH of my server.
Does any one have an idea.
Thanks , Edwige

(*bump*)
Almost the exact same problem here...
"conn" is an object of type OracleConnection
"cst" is an object of type "CallableStatement"
"xml" is a String holding a well-formed XML document (say, "<foo><bar>value</bar></foo>")
XMLType xt = XMLType.createXML(conn, xml);
cst.setObject(1, xt); // BOOM! Non supported character set: oracle-character-set-178
Other relevant details:
Using the 9.2.0.3 JDBC thin client (ojdbc14.jar)
Using the newest nls_charset12.zip (in the 9.2.0.3 download section under the "1.2/1.3" heading.
JDK1.4.1_03 (04?)
Oracle itself is 9.2.0.3
database charset is 'WE8MSWIN1252' (yeah, I fought with the DBA and lobbied for UTF-8, but obviously he won that battle... sigh...)
Also relevant... prior to a few days ago, it worked. Then, the DBA did an upgrade and the charset errors began. It's hard to get a straight answer from him because his English isn't very good, but my guess is that he updated it from 9.2.0.1 to 9.2.0.3.

Migrating from non-loggin Informix to Oracle (use of transactions)

I wonder what happens when I migrate an Informix non-logging database to Oracle. Since my database doesn't use transaction (that's to say: a single DML sentence define a transaction and ttransactions using begin/commit/rolback trans are not used), applications are written with no transaction philosophy. But Oracle is ANSI-compliant and then when I execute a DML sentence, a transaction begin and it'll finish until I send commit or logout. Then, even when migration is ok, my applications will create very large transactions.

Hi Oscar,
Without actually viewing the Client application code, I can only make general assumptions..
You will have to change the client code anyway in order for it to work with Oracle e.g. Informix E/SQL -> Oracle Pro*C. The E/SQL Client code will have to be updated to reflect various changes in the DB environment; for example:
1. The use of REF CURSORS (passing them back to the client code)
2. Changes to the hardcoded Informix SQL statements to make them Oracle friendly (especially OUTER joins if you migrating to Oracle 8i)
3. Altering any E/SQL code that dynamically builds SQL statements (to make sure these SQL statements are syntactically correct in the Oracle model).
4. DB Connection methodologies.
5. Changing Informix #include files to reference equivalent Oracle #includes
6. Differences in date structs and how E/SQL and Pro*C handle dates (Oracle did not support milliseconds until 9i)
7. Exception handling.
8. Datatype changes between Informix and Oracle.
Again, there is no simple solution. A migration project that migrated the DB and Applications 'in tandem' would make it easier to remove logic from the client code and place it in the server (always a good thing) but this may not be feasable in your case.

Migrating from non-logging Informix to Oracle (use of transactions)

I wonder what happens when I migrate an Informix non-logging database to Oracle. Since my database doesn't use transaction (that's to say: a single DML sentence defines a transaction and transactions using begin/commit/rolback trans are not used), applications are written with no transaction philosophy. But Oracle is ANSI-compliant and then when I execute a DML sentence, a transaction begin and it'll finish until I send commit or logout. Then, even when migration is ok, my applications will create very large transactions.
What should I do? Is there some parameter to configure Oracle in such way it create single-DML transaction (I heard there's something like that in SQL*Plus, but I'm not sure)? Or should I rewrite applications sending commits after every sentence (The worst case, I think)?
Thanks in advance
Omar Muqoz

Hi Oscar,
Without actually viewing the Client application code, I can only make general assumptions..
You will have to change the client code anyway in order for it to work with Oracle e.g. Informix E/SQL -> Oracle Pro*C. The E/SQL Client code will have to be updated to reflect various changes in the DB environment; for example:
1. The use of REF CURSORS (passing them back to the client code)
2. Changes to the hardcoded Informix SQL statements to make them Oracle friendly (especially OUTER joins if you migrating to Oracle 8i)
3. Altering any E/SQL code that dynamically builds SQL statements (to make sure these SQL statements are syntactically correct in the Oracle model).
4. DB Connection methodologies.
5. Changing Informix #include files to reference equivalent Oracle #includes
6. Differences in date structs and how E/SQL and Pro*C handle dates (Oracle did not support milliseconds until 9i)
7. Exception handling.
8. Datatype changes between Informix and Oracle.
Again, there is no simple solution. A migration project that migrated the DB and Applications 'in tandem' would make it easier to remove logic from the client code and place it in the server (always a good thing) but this may not be feasable in your case.

Oracle.sql.ARRAY error "Non supported character set: oracle-character-set-"

Hi Folks,
I am getting error :
java.sql.SQLException: Non supported character set: oracle-character-set-178
at oracle.gss.util.NLSError.throwSQLException(NLSError.java:46)
in the following code :
Object[] arrayToPassToDB=new Object[7];
ArrayDescriptor arraydesc = ArrayDescriptor.createDescriptor(arrayDesc,con);
ARRAY array = null;
array = new ARRAY(arraydesc, con, arrayToPassToDB);
i am using jdk1.6 and oracle 10g.
I have copied the orai18n.jar and ojdbc6.jar in WEB-INF\lib directory of my project and also in the Tomcat\lib directory.
can you please help me?
Thanks in advance.

java.sql.SQLException: Non supported character set:oracle-character-set-178

Non text filters in Oracle Text 9.2 (W2K)

Similar Messages

Maybe you are looking for