Archive for the ‘Oracle’ Category

<BEA-000000> <java.lang.NegativeArraySizeException

17 December 2015 Leave a comment

If you get this error with WebLogic’s admin server

####<2015-12-17 14:30:14 EET> <Critical> <EmbeddedLDAP> <> <AdminSOA> <VDE Replication Thread> <<anonymous>> <> <9f23d04b03212987:b0dda39:151a2d3b538:-8000-0000000000004207> <1450355414644> <BEA-000000> <java.lang.NegativeArraySizeException
	at com.octetstring.vde.EntryChanges.readBytes(
	at com.octetstring.vde.EntryChanges.<init>(
	at com.octetstring.vde.replication.BackendChangeLog.getChange(
> )

chances are that there are corrupted LDAP files in the <domain home>/servers/<server name>/data/ldap/ldapfiles folder. One possible solution is to delete the and changelog.index files (take a backup first of these two files) and restart the admin server.

Categories: Java, ldap, Oracle, WebLogic Tags: , , ,

ORA-01003: no statement parsed

16 September 2015 Leave a comment

Not Java-related but since I started doing a bit of PL/SQL lately and I ran into this problem, I will post this. This error, in my case, was caused by having an Oracle keyword defined as a column name. For example the following

OPEN v_customer_recs FOR
         SELECT sc.EVENT_ID,
                ND.DESCRIPTION AS COMMENT,  -- This will cause the error

will result in a ORA-01003: no statement parsed. The problem is that the COMMENT keyword is used as a column name. If you change this then the error will go away.

Categories: Oracle, PLSQL

Incorrect argument type encountered in function or method invocation. in main

21 November 2012 Leave a comment

I am working with ORACLE SOA & OSB version This error occurs if you use Oracle Business Rules and you forget to pass all the objects defined in your decision function. To elaborate: if in your decision function you have defined as inputs, let’s say, the objects Customer and Address, but in your code you only pass as input the object Customer, then you will get the error message above. To fix it either pass both objects, or remove the unused object from the input settings of your decision function.

The actual error oracle outputs is rather misleading. I spent three hours trying to find out what’s going on.

Categories: Oracle, OSB

ORA-12505: TNS:listener does not currently know of SID given in connect descriptor

9 December 2010 25 comments

I am not sure why I get this error since I can connect to the current SID by using sqlplus but I cannot connect to it by using jdbc with the following url:


After searching for about an hour I found out that you can also use the full blown jdbc url protocol to connect to oracle


This does not explain why the issue happens but at least for now it solves the problem. I will post an update if I find anything else.

Categories: JDBC, Oracle