Recent content by Greg Stevenson

as Firstname.LastName@MyCompany.com with no quotes. This works fine in 3.x. In 4.x I have found that the above will work if surrounded in double quotes but that a simple username like "MyUsername" will not work if it has double quotes. What's the rule for passing a username to Oracle. Do I have...

In DOA 3.x, I can log into a DB that has a username like "Firstname.LastName@MyCompany.com". However in 4.x, this now results in a "ORA-12154: TNS:could not resolve the connect identifier specified." error. Same results in recent PL/SQL Developer versions vs. older version. Looking at LogIn...

Marco, There are apparently still issues even with 7.0.3. The item below is from one of our DBAs using 7.0.3 . It may just be a result of the VCL not having unicode support. --Greg Here are the steps to reproduce the ORA-1480 error on an Oracle Database using NLS_LANG AL32UTF8. All of these...

Sorry for the double post, copy did not take and pasted old post that was still on the clipboard and uploaded without previewing it first. Anyway, both client and server set to UTF-8. For now we put a switch in like PL/SQL Developer has, but are hoping for something more automatic that works...

We are checking to make sure the client and the server are both using UTF-8. SQL*Plus does not seem to have the issue so I don't think it's directly related to OCI. Changing the column from a varChar 4000 to a clob seems to fix the issue for PL/SQL Developer, but not for our client...

We are checking to make sure the client and the server are both using UTF-8. SQL*Plus does not seem to have the issue so I don't think it's directly related to OCI. Changing the column from a varChar 4000 to a clob seems to fix the issue for PL/SQL Developer, but not for our client...

Marco, We are encountering the same issue and it also exists in PL/SQL developer (and possibly SQL+), but not Toad or iSQL. Below is the support info from PL/SQL developer. (I know its not current but should but recent enough for this not to be an issue.) It does seem that something is pushing...

Never mind. I could not reproduce and developer double checked and realized he was using old DOA dcus. However, I was wondering about how the registry NLS_LANG entries effect the bytesPerCharacter stuff. On various systems we still get ORA-03127 errors on various clobs that we can get to work by...

We are finally getting serious about multi-lingual support. I was just informed that we can read UTF8 data correctly, but if we write a CLOB it is corrupted when it gets read back (I think everything in the test clob should be plain ASCII characters) I check our current version which is //...

The LOBField does seem to work so I can us that. But it seems that if CLOBs work with AsString (or FieldAsString) that BLOBS should as well. In anycase, I can keep working on this project now so thanks. --Greg

Running a TOracleQuery that returns a blob using FieldAsString returns a string of the correct length but it is all nulls. Same query in a PL/SQL SQL window and the Data Editor shows the correct info. TOracleDataset also seems to get it right. Tried variants, GetLongField, FieldData with similar...

Thanks Marco. Haven't heard back from our DBA yet, but I'm sure the explaination you gave is what they were looking for. --Greg

Marco, From my DBA in response to your reply above (I hate being the middle-man): That doesn

Marco, We just recently encountered this at one of our customer sites as well. Anything new to add regarding this issue? Has it been determined to be an Oracle Issue? Our main DBA would like a little more detail (in Oracle terms) of what you mean by the optimize flag "When enabled, a...

Came accross an issue that exists in at least Versions 3.4.6.1 and 4.0.6.2. This is the scenario I see via the Oracle Monitor. I do a select (in a series of queries) where one or more of the columns contain lobs. The select returns with X rows, but apparently the lob fetches occur asychonously...