Getting Native Error 1019 in Crystal Reports

[Former Member]

When running a report, we are getting the following error:

Logon failed.

Details: ADO Error Code 0x800004005

Source: Microsoft OLE DB Provider for Oracle

Description: ORA-01019: unable to allocate memory in the user side

Native Error: 1019 (Database Vendor Code 1019)

This happens in Crystal Reports 2008, 11 and 2013 when trying to login to a database.  When the user is given administrator rights, it works.  However the user cannot have administrator rights and setting the user as Power User doesn't work either. Is this a database issue or is it a Crystal Reports issue?

Does anyone have any ideas on how to get around this?  Thank you in advance for your assistance and time!

Mark

[Former Member · Accepted solution]

Same error,

this may help

http://stackoverflow.com/questions/12560925/error-while-trying-to-retrieve-text-for-error-ora-01019

it says that uninstalling the oracle client solved the issue. I cannot do that so I'll keep trying another option

[Former Member · Accepted solution]

Ok I SOLVED it

I previously had an old installation for Oracle 9i and Oracle Reports

Later I installed ODT with ODAC for .NET tools, so somehow the ORACLE_HOME variable was pointing to the old installation: "C:\ORANT6i". This registry variable is located on (Windows 7)

- HKEY_LOCAL_MACHINE -> SOFTWARE -> Wow6432Node -> ORACLE -> ORACLE HOMES -> ORACLE1 -> (key) "ORACLE_HOME"

I changed the value of this entry to my instant client folder which is:

"C:\app\rcaballero\product\11.2.0\client_1"

and it finally connected to Crystal Reports. I'm also using TOAD for Oracle and it works as well.

I have to point out that I have read a lot of stuff from SAP people telling you that you should use the Native Oracle Connector because is much better for many reasons. BUT, I struggled for two days trying to figure out why my reports where trying to connect to the database on client machines, being that I was passing an external datasource and the clients shouldn't connect directly to Oracle. Well, I found out that it was because i was using the mentioned Native Oracle connector. I switched to OLE DB provider and I stopped the issue. So be careful with this native connector.

regards

Rodrigo

Other usefull links:

ORA-01019</title> :

[DellSC]

This is specifically an Oracle error, not a Crystal error.  Do a google search on ORA-01019 and see what you find.

-Dell