E-QR: Receive ""Database Driver Error. (30,11)" When Running a Query on Record With Translate Values Defined (Doc ID 1453029.1)

Last updated on AUGUST 18, 2015

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.50 and later
Information in this document applies to any platform.
*** Checked For Relevance On 19-Aug-2015 ***


NOTE: The following scenario is considered a customization beyond the scope of the GCS. The following is only an example and it is not supported by the GCS. Please thoroughly test these customizations in both test and development environments.

When attempting to run a query that contains a field having translate values defined in the record but does not have actual translate values, the following error occurs:


"Database Driver Error. (30,11)."

The issue does not occur when trying to run the same query using Two tier query tool, it does not give any error but also does not fetch any data.

The issue can be reproduced at will with the following steps:
1. Open Application Designer

2. Create a new custom Field, for example XX_REF_STATUS and define the field length as 1

3. Add to the new field created translate values, for example A, B, C

4. Create a new custom record and insert two fields: the new field created (XX_REF_STATUS) and an existing key field (e.g. EMPLID)

5. Build the new record created

6. Insert some sample data to the new record created through the database

7. Add the new record created to the adequate query security tree

8. Go back to the record definition and delete the translate values created (e.g. A,B,C) from the field definition

9. Login to PIA

10. Navigate to Reporting Tools > Query > Query Manager

11. Create a query on this record

12. Run the query in Two tier, Query Manager, Query Viewer and Schedule Query. and notice the following observations:

    12.1. Using Query Scheduler
An error has occurred. You may attempt to sign in again. If your attempt fails, please contact your System Administrator.

   12.2. Using Query Viewer
A blank page opens with no data being fetched.

   12.3. Using Schedule Query Option
When trying to run the same query using Schedule query option it gives the following message and does not fetch any data.

Database Driver Error. (30,11)

   12.4. Two Tier Query Tool
When trying to run the same query using Two tier query tool, it does not give any error but also does not fetch any data.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms