Hello, We have an Oracle 11g database that we are going to use with LLBLGenPro (2.5 Final). We have downloaded and installed new Oracle 11 drivers (Oracle 11g ODAC 11.1.0.6.20 with Oracle Developer Tools for Visual Studio - http://www.oracle.com/technology/software/tech/windows/odpnet/index.html). When using the designer we are offered a choice of several database drivers of which two seem interesting Oracle 10g (ODP.NET 10.x) and Oracle 8i/9i/10g (MS Oracle). We tried to connect to our database using ODP.NET 10.x driver but the designer reported the following error after clicking on 'Connect' while creating the project (after few minutes):

ORA-01013: user requested cancel of current operation ORA-06512: at "XDB.XDB#EXTNAME2INTNAME", line 1 ORA-06512: at line 1 ORA-06512: at "SYS.XML_SCHEMA_NAME_PRESENT", line 17

The MS Oracle driver does not return any errors and reads the schema information. We could probably proceed with MS Oracle driver but we would prefer to use the latest Oracle drivers as we assume that they are better the MS ones. As this is our first Oracle and LLBLGenPro experience we would also appreciate if anybody could state their experiences with LLBLGenPro and Microsoft/Oracle drivers.

Thank you

So do you have the ODP.NET 10.x driver installed or only the 11g one?

I only have 11g.

Please post the stacktrace. THe oracle error is of little value without the stacktrace. The ODP.NET using driver uses similar SQL to obtain the meta-data as the MS Oracle using driver does so it's beyond me why this fails.

Could you please tell me how can I do this? I do not know where LLBLGenPro saves any stack trace information.

I have included the screenshot of the error.

First you should use an assembly redirect to the ODP installed on your machine, in the LLBLGenPro config file.

Then try to set the command time out to a higher value than 30 in the Preferences of the designer? (DriverCommandTimeout property)

Some relevant links: http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=10665 http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=10682 http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=6562

He does have odp.net otherwise the exception would be different

I indeed think the timeout has to be higher. Very weird that the error doesn't show any stacktrace as the error has to end up in the general handler. So I think that error is popped up by ODP.NET, not by LLBLGen Pro.

I have increased the timeout to 120 and it works. It does seem to take more time then the MS Oracle driver. In any case I can continue to work.

Thank you very much for your help and speedy response

Regards, Dalibor

The time ODP.NET takes to connect to the DB is indeed horrifically slow. Here we use 10g for testing and indeed connecting to the DB takes 5-10 seconds. What's odd is that it uses the same OCI (oracle client interface) as MS Oracle! So when it's slower, it's due to ODP.NET's own code...