[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 984
  • Last Modified:

After upgrading App and Db server Application received ORA-24813

Hello.  We have a client/server setup to run our application.  Our Application runs on an HPUX Itanium server dedicated soley to run the application.  And, we have a database specific only server where the we have our database running.  The Application makes connections to the database server thru sqlnet tnsnamse.ora listener.ora configuration.

As of last Friday Oracle release software running on the aforementioned Application and Database servers.  Then I upgraded software on both servers  to Oracle on both the Application server and the Database server.  The noted Oracle Database was upgraded to Oracle release as well.

When performing a task such as taking an order with our Application we received the following error message:

ORA-24813: cannot send or receive an unsupported LOB

Then, when the user tried again they are able to complete the task without getting the aforementioned message.  We've seen this pattern happen twice now.  Error occurs and the user tried again the the error seems to stop occuring.  It seems the error stop occurring for the individual user once it occurs the first time.

Looking up information and the description on the ORA-24813 message indicates that  an Oracle version mismatch between the Application and Database server may be the reason for this message occurring.    But, we're sure that we're running Oracle on the Application Unix server and Oracle on the database as I upgraded the software on both of these servers to Oracle software plus the database to Oracle

I'm trying to determine if this error message indicates an issue is present or if the current pattern that we're seeing whereby the message occurs once for a user and not again indicates some sort of caching memory issue whereby the User's App is still pointing to Oracle software etc then it gets cleared and the error message no longer occurs.  Thanks for your help.  Any questions please let us know.
2 Solutions
check  the ORACLE_HOME and make sure its pointing to the right place.
Did you run UTLRP.SQL after upgarding?

May be the reason fot this is that there are invalid packages
because of the change of the Oracle Catalog. After the first call
to such package/procedure/function it will be recompiled automatically
and the message will not appear again.

You can recompile invalid packages with the utlrp.sql SQL script that is supplied with Oracle. This script is maintained in the $ORACLE_HOME/rdbms/admin directory on your database server. You can also manually recompile packages if you prefer. Here is an example of calling the utlrp.sql script to recompile invalid database objects:


Once all SYS and SYSTEM packages are valid, you are ready to install the replication objects.  If you are in Oracle8i and earlier, you will use SVRMGRL and connect with INTERNAL.  If you are in Oracle9i and later, use SQL*Plus to connect to SYS, using the as sysdba syntax as seen here:

C:>sqlplus sys as sysdba

puyojrAuthor Commented:
Hello.  Thanks for the input.  We've checked and our $ORACLE_HOME is pointing to the Oracle software directory patch where the Oracle software was upgraded.  This would be for the Application and Database server.   The @?/rdbms/admin/utlrp.sql was run after the upgrade.  We just checked and the only invalid objects that exist our for synonyms for old unused schema owners that were used for testing.  Thanks.
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.


Use a version of the Oracle that supports the LOB on both the client and the server.

LOBs should be supported in 10g family.

I am worried by your statement  -----> " to Oracle on both the Application server "

Such version of OAS doesn't exist.

But if you ment please be aware that this is
brand new OAS family with reduced functionality and with
many bugs.

I recommend you to reinstall your previous (and possibly good running!)
version of OAS. There is no corespondence between the versions of
OAS family and Oracle Server family, so when you upgrade the server to
next upgrade, this doesn't mandate you to upgrade the application server.

Next advise  - never use for production starter versions of new Oracle products.
Possibly you will run into bugs.
puyojrAuthor Commented:
Thanks for the input.

For clarification on our Application server we are not running Oracle Application Server software (OAS) but Oracle Client release software. Our third party Application, not related to Oracle, runs on our Application unix server and utilizes Oracle client (could also use Enterrprise rdbms) software (library files, other sqlnet etc).

In the past 5 days we have not received the noted message noted in this inquiry.  We speculate that after the upgrade some of the clients accessing the application had the $ORACLE_HOME setting in cahce memory set to point to Oracle software as opposed to the Oracle software.  We will continue to monitor.   Thanks for you help.  This is a fine helpful site.  

Featured Post

Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now