Hi - I am a new user currently utilizing TOAD for Oracle 10.6. During the course of a query run, I am getting the following error:
Access violation at address 612C7C1F in module ‘oranls.dll.’ Will an upgrade resolve this error?
Thank you
Looks like you have an Oracle client issue – not a toad problem. So while an upgrade of toad might help – I would suggest getting your Oracle client right first
so that you don’t upgrade for not.
From: kevin.snow [mailto:bounce-kevinsnow@toadworld.com]
Sent: Tuesday, August 27, 2013 8:12 AM
Subject: [Toad for Oracle - Discussion Forum] Access violation at address 612C7C1F
Access violation at address 612C7C1F
Thread created by kevin.snow
Hi - I am a new user currently utilizing TOAD for Oracle 10.6. During the course of a query run, I am getting the following error:
Access violation at address 612C7C1F in module ‘oranls.dll.’ Will an upgrade resolve this error?
Thank you
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or
Unsubscribe from Toad for Oracle - General notifications altogether.
Toad for Oracle - Discussion Forum
Flag
this post as spam/abuse.
Hi Kevin,
Hi - I am a new user currently utilizing TOAD for Oracle 10.6. During
the course of a query run, I am getting the following error:Access violation at address 612C7C1F in module 'oranls.dll.' Will an
upgrade resolve this error?
If I remember correctly, this sounds like your database is using unicode character set(s) and your client is possibly 9i. The OCI interface at 9i was slightly unstable in the unicode department and causes no end of problems.
I've had them myself and seen exceptions in the oranls.dll file you reference.
Can you confirm whether you are using a 9i client? And what is the version of the database you are having the problem with? Are you able to see the characterset settings at all? If not, can you ask your DBA to advise you what they are?
Thanks.
Cheers,
Norm.
-- Cheers,
Norm. [TeamT]
Thank you for your prompt reply.
Hi, Norm - Yes, client version is 9i. According to the DBA, the character set is not Unicode, but WE8ISO8859P1. Would a possible solution be to upgrade the client version? Thanks again for your help.
Evening Kevin,
Is the database 9i also?
The character set is definitely not Unicode, but maybe the National Character Set might be.
The failure in the oranls DLL is indicating a Unicode problem in the national character set.
Upgrading to a 10 or 11 client might help, yes.
Cheers,
Norm. [TeamT]
Sent from my HTC