Error in form ora- 00907

hi all
i have work in the oracle form and genrating the dynamic query in the pl/sql block and to accessing in the remote so use the statemet
dbms_sql.parse(src_cur, str,1);
st_cur is cursor define
str is my string pass;
1 insad of dbms_sql.native bas in the remote data are access
way is error is give and what is the solutaion.
help
thanks;

Could you list the exact code you are using as the error is:
ORA-00907: missing right parenthesis
Cause: A left parenthesis has been entered without a closing right parenthesis, or extra information was contained in the parentheses. All parentheses must be entered in pairs.

Similar Messages

  • Login error in forms ora-28009

    Hi ,
    Am trying to login forms 10g as sysdba.But am getting error ora-28009
    username:sys
    password:sys
    connect:oracle causes ora-28009
    username:sys as sysdba or sys/ as sysdba or sys/sys as sysdba
    password:sys
    connect:oracle causes ora-01017
    username:sys/sys@oracle as sysdba causes ora-12154
    BUT if try other users
    username:hr
    pasword:hr
    connect:oracle it works fine.
    i checked connectivity with database,listener all are working fine.
    Please help in connecting to forms 10g and reports 10g as sysdba.
    Thanks.

    ORA-28009:
    connection as SYS should be as SYSDBA or SYSOPER
    Cause: connect SYS/<password> is no longer a valid syntax
    Action: Try connect SYS/<password> as SYSDBA or connect SYS/<password> as SYSOPER
    Therefore, Try this
    in 10G
    C:\>sqlplus
    Enter user-name: / as sysdba
    Prior to Oracle 10g, when you wanted to connect using / AS SYSDBA on the command prompt, you had to put the connection string between double quotes:
    C:\>sqlplus "/ as sysdba"
    To specify the connection string; you need the following format: username/password@instance as SYSDBA.

  • Using DBMS_METADATA.GET_DDL get error: ORA-00907: missing right parenthesis

    Hi,
    I'm trying to extract schema DDL from a database (10.2.0.4.0 - 64bit Enterprise Edition on Solaris 10). I run the query below and get an ORA-00907: missing right parenthesis error.
    SELECT DBMS_METADATA.GET_DDL( REPLACE(object_type,' ','_') AS object_type, object_name) FROM user_objects WHERE object_type NOT IN ('TABLE_PARTITION','INDEX_PARTITION','LOB');
    This is the output when running the above in sqlplus worksheet
    select DBMS_METADATA.GET_DDL( REPLACE(object_type,' ','_') as object_type, object_name) FROM user_objects where object_type not in ('TABLE_PARTITION','INDEX_PARTITION','LOB')
    ERROR at line 1:
    ORA-00907: missing right parenthesis
    removing the where clause gives the following:
    select DBMS_METADATA.GET_DDL( REPLACE(object_type,' ','_') as object_type, object_name) FROM user_objects
    ERROR at line 1:
    ORA-00907: missing right parenthesis
    Any pointers would be gratefully received. I know I could get the DDL out using exp/imp but I want to understand why I'm getting the missing parenthesis error.
    cheers,
    Ewan

    SELECT DBMS_METADATA.GET_DDL( REPLACE(object_type,' ','_') AS object_type, object_name) FROM user_objects WHERE object_type NOT IN You don't need an alias here. Get rid of " AS object_type" and it should work.

  • FOR UPDATE on scrollable cursor and error: ORA-00907: missing right parenthesis

    If change my query to have a FOR UPDATE and make it an updatable scrollable cursor I get an error on the updateRow() command saying "ORA-00907: missing right parenthesis"
    If I remove the FOR UPDATE it works OK.
    The problem I have is trying to update a CLOB from a ResultSet. If I do not upate any other column I get the error saying that the error"
    "ORA-22920: row containing the LOB value is not locked"
    I can get around this by adding FOR UPDATE. But if I add FOR UPDATE and try to update any non-CLOB column I get the 00907 error above.
    Hmmmm. So here is what I can and cannot do:
    - I CAN update the CLOB IF I update another column 1st and NO FOR UPDATE clause.
    - I CAN update the CLOB only if I have FOR UPDATE clause.
    - I CANNOT update just the CLOB without FOR UPDATE.
    - I CANNOT update any non-CLOB column with FOR UPDATE.
    What a pain in the ***! How am I to provide generic access to the applications being built on my DB layer. This is crazy!

    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Andrew Edgar ([email protected]):
    I have this same problem!
    The error occurs when performing updateRow.
    The turning off of auto commit only gets the query to work but not the actual update.
    Will this be fixed in the next version of the Driver?<HR></BLOCKQUOTE>
    Here is the stack Trace I recieved:
    java.sql.SQLException: ORA-00907: missing right parenthesis
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
    at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
    at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543)
    at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1405)
    at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:822)
    at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:1446)
    at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1371)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1900)
    at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:363)
    at oracle.jdbc.driver.UpdatableResultSet.execute_updateRow(UpdatableResultSet.java:2135)
    at oracle.jdbc.driver.UpdatableResultSet.updateRow(UpdatableResultSet.java:1322)

  • FOR UPDATE on updatable cursor and error: ORA-00907: missing right parenthesis

    Anyone run into this? I've searched the message board and bug db to no avail.
    - Using latest Oracle JDBC 2.0 compliant "thin" driver and Oracle 8.1.6 database.
    1) Using prepareStatement specifying an updatable cursor for something like "SELECT FNAME,LNAME FROM USERS FOR UPDATE OF FNAME,LNAME"
    2) Updating FNAME using updateString("FNAME","whatever"), and then calling updateRow() of the ResultSet yields:
    ORA-00907: missing right parenthesis
    If I remove the FOR UPDATE clause then everything works just fine.
    Workarounds/suggestions appreciated!
    Thanks,
    Ryan
    null

    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Andrew Edgar ([email protected]):
    I have this same problem!
    The error occurs when performing updateRow.
    The turning off of auto commit only gets the query to work but not the actual update.
    Will this be fixed in the next version of the Driver?<HR></BLOCKQUOTE>
    Here is the stack Trace I recieved:
    java.sql.SQLException: ORA-00907: missing right parenthesis
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:168)
    at oracle.jdbc.ttc7.TTIoer.processError(TTIoer.java:208)
    at oracle.jdbc.ttc7.Oall7.receive(Oall7.java:543)
    at oracle.jdbc.ttc7.TTC7Protocol.doOall7(TTC7Protocol.java:1405)
    at oracle.jdbc.ttc7.TTC7Protocol.parseExecuteFetch(TTC7Protocol.java:822)
    at oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:1446)
    at oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1371)
    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1900)
    at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:363)
    at oracle.jdbc.driver.UpdatableResultSet.execute_updateRow(UpdatableResultSet.java:2135)
    at oracle.jdbc.driver.UpdatableResultSet.updateRow(UpdatableResultSet.java:1322)

  • Error ORA-00907 with query  SDO_GEOM.SDO_DIFFERENCE

    Hi,
    I have following query:
    SELECT SDO_GEOM.SDO_DIFFERENCE(
    SDO_RELATE(square.geometry, SDO_GEOM.SDO_BUFFER(MDSYS.SDO_GEOMETRY(3001, 1, MDSYS.SDO_POINT_TYPE(424, 1272, 0) , NULL, NULL), 100, 0.05,'unit=m arc_tolerance=0.005'), 'mask=ANYINTERACT querytype=WINDOW') = 'TRUE',
    SDO_RELATE(square.geometry, SDO_GEOM.SDO_BUFFER(MDSYS.SDO_GEOMETRY(3001, 1, MDSYS.SDO_POINT_TYPE(276, 1274, 0) , NULL, NULL), 100, 0.05,'unit=m arc_tolerance=0.005'), 'mask=ANYINTERACT querytype=WINDOW') = 'TRUE',
    0.001
    Always get the ora-00907: a bracket is missing-error.
    Any help is really appreciated. Is there a error in the query?
    Regards Ronald.

    Hi Ronald,
    try following:
    SELECT SDO_GEOM.SDO_DIFFERENCE(
        SELECT square.geometry from square where
          SDO_RELATE (square.geometry, SDO_GEOM.SDO_BUFFER(
              MDSYS.SDO_GEOMETRY(
                3001, 1, MDSYS.SDO_POINT_TYPE(424, 1272, 0) , NULL, NULL
              ), 100, 0.05,'unit=m arc_tolerance=0.005'
            ), 'mask=ANYINTERACT querytype=WINDOW'
          ) = 'TRUE'
        SELECT square.geometry from square where
          SDO_RELATE (square.geometry, SDO_GEOM.SDO_BUFFER(
              MDSYS.SDO_GEOMETRY(
                3001, 1, MDSYS.SDO_POINT_TYPE(276, 1274, 0) , NULL, NULL
              ), 100, 0.05,'unit=m arc_tolerance=0.005'
            ), 'mask=ANYINTERACT querytype=WINDOW'
          ) = 'TRUE'
        0.001   
    FROM DUAL   

  • Between problem: ora-00907

    Dear moderator, this post is duplicate by my mistake, so please delete this one.
    Thank you, and sorry...
    Dear professionals,
    I'm trying to get some results with next code:
    V_Default_Where := 'kadi_pk between to_date('||to_char(:kadipk_par1,'dd.mm.yyyy')||',''dd.mm.yyyy'') and to_date('||to_char(:kadipk_par2,'dd.mm.yyyy')||',''dd.mm.yyyy'')';
    set_block_property('acc_pr_delay',default_where,V_Default_Where);Both fields from the form, kadipk_par1 and kadipk_par1 are date format (dd.mm.yyyy).
    During the execution of query, i got next error: ORA-00907: missing right parenthesis
    When press: CTRL+SHIFT+E, i see this:
    SELECT ssorgj_pr,broj_pr,naziv
    FROM acc_pr_delay
    WHERE kadi_pk between to_date(*01.01.2010*,'dd.mm.yyyy') and to_date(*21.01.2010*,'dd.mm.yyyy')
    to get correct data, it must be: WHERE kadi_pk between to_date(*'01.01.2010'*,'dd.mm.yyyy') and to_date(*'21.01.2010'*,'dd.mm.yyyy')
    (both dates must be in '')
    how to achieve that ?
    Thanks a lot in advance...
    Adnan
    Edited by: adnanBIH on May 10, 2010 11:04 AM

    user2679851 wrote:
    I am sorry, I am a bit wrong
    try this
    'kadi_pk between to_date(to_char('||:kadipk_par1||','||'''dd.mm.yyyy'''||'),'||'''dd.mm.yyyy'''||') and to_date(to_char('||:kadipk_par2||','||'''dd.mm.yyyy'''||'),'||'''dd.mm.yyyy'''||')';Dear,
    DID YOU READ FIRST SENTENCE OF THE FIRST POST ?!
    This thread is DUPLICATE of the post which is answered, already...
    Thanks a lot anyway.
    Adnan

  • URGENT: Form Import FAILED with  Unable to generate UI form: ORA-0650

    I am importing application components from one installation of portal 3.0.9.8 to another installation. Both installed versions of POrtal are the same.
    The application name is PROFILE_APP. I have created this same app with same specifications as in source, in the target portal instance.
    To import, I am using the SQL scripts generated through portal using the "Export" feature available for each component.
    I could successfully import LOV into this app from source to target by running the above generated SQL. When i run the SQL for the form component in the target - i get the following error :
    ...Importing component: ID = 5861481106 Name = WST_USER_PROFILE_V_FRM Owner = WST_PROFILE_PORTAL30_APP Type = FOT
    *** ERROR ***
    wwa_generate_module.transfer_fot_metadata: Unable to generate UI form: ORA-06502: PL/SQL: numeric or value error
    The form worked successfully in the source instance.
    Any help is greatly appreciated.
    Thank you,
    Tanushree.

    Form CustomForm_791b1adc_97fd_4de1_a077_646a418fe59b extends form Microsoft.EnterpriseManagement.ServiceManager.ChangeManagement.Forms.ChangeRequestForm, which already has another extension (CustomForm_3e2fd77f_cfed_40f9_9def_c6735078bf2a).
    you already have a form customization that extends the change request form, and this MP is also importing a different customization to the same form. each form can only have one customization. 

  • "Invalid Cursor" Error in Form

    Hi,
    I wrote a procedure that take a REF CURSOR as an IN OUT argument. This procedure does an "OPEN cursor FOR qry" with a dynamic query:
    OPEN l_cursor FOR
           'SELECT A '||
             'FROM B '||
            'WHERE C = :l_var'
         USING myVar;After calling the procedure, I do a LOOP with FETCH.
    It works well when I use it in SQL*Plus with DBMS_OUTPUT but it returns a "ORA-01001 invalid cursor" error in Forms.
    Any help is welcome!
    Regards,
    Olivier.

    I found a solution on Metalink:
    Note:170881.1
    Note: 1007395.6
    Olivier.

  • Displaying a trigger error in forms

    In a before inserting table trigger, if inserted values are not correct, I raise an error :
    RAISE_APPLICATION_ERROR(-20001,'Error message !');
    What I want is to display this error message in forms instead of the error 40508 - ORACLE error: unable to INSERT record.
    How can I ?

    look at Dbms_Error_Code and Dbms_Error_Text.
    You'll have to parse them, but you can grab the error messages off them.
    Here's a similar question I asked on Metalink... I never received an error there, but the solution was to write an on-error trigger for the block and capture the form errors related to inserts, updates, and deletes. Here's the question though:
    Oracle Forms/Web Forms Technical Forum
    From: ERIC GIVLER 18-Nov-00 15:16
    Subject: "Clean" capture of DBMS Error messages on raise_application_error
    "Clean" capture of DBMS Error messages on raise_application_error
    This is with Forms 4.5 Developer 1.3.2 (32bit)
    Has anyone written forms level triggers, I guess ON-ERROR triggers to properly capture the error messages raised from a database trigger or procedure that uses a RAISE_APPLICATION_ERROR?
    I'd like to display the SAME message that I'm passing to RAISE application error, the message only, without all the other garbage.
    I was thinking of capturing the dbms_error_code and dbms_error_text, and then based on the form error code - kind of like in the example code in the Forms Help. Then, I'd parse these strings and strip off my error message, because the dbms_error_text contains the entire "error stack", ie:
    ORA-20100: SEASON DATES ERROR! Reservations exist in this date range
    ORA-06512: at "SUNTRACK.SEASON_DATES_BR_D", line 19
    ORA-04088: error during execution of trigger 'SUNTRACK.SEASON_DATES_BR_D'
    So... I'd like to just get "SEASON DATES ERROR! Reservations exist in this date range" message
    Questions:
    1. Is there an easy way to do this that I'm missing, or do I have to brute force, look for 'ORA'&#0124; &#0124;dbms_error_code&#0124; &#0124;': ' in my dbms_error_text, strip that off the front, and then grab the error text up to the first LINEFEED, chr(10), found in the dbms_error_text - that just seems a little "kludgy"
    2. Anyone have a nice solution? IT seems like there should be a "standard" on-error trigger that handles this type of situation.
    3. What would be all the form errors that I should look for that could have been the result of an error raised in a trigger???
    ie. frm-40509 (unable to update), frm-40510 (unable to delete
    null

  • How to find trace file error in form

    hai all,
    i have big problem in my form in apps i open the form one error is ocuured,
    i got the trace file and check the error,
    PARSE ERROR #82:len=2903 dep=0 uid=173 oct=3 lid=173 tim=4265689973879 err=904 this is the trace file error meassage,
    how to find this error in form and also this is occured one select statement,how to find this select statement where can be used in form,
    i have one button ,when ever i press the button this error is ocuured,i check this button pl/sql procedure code but in this code not using that sql statement,
    if any one know to find the sql statement through trace file.
    plz give the replay as soon as possible.
    thank's

    The newest SQL Developer can converts the trace to readable format too, I'm not shure if you see the sql statement related to the error then.
    It seems you get ORA-00904 which says you use an invalid coumn in a dml statement.
    Normally such error should pop up in message - do you overwrite the message handling or use exception handling in you form which block this message?
    Easiest way to find this is to compile the form against the target database.
    If this does not give an error, you should check, if you use dynamic sql statements which are wrong.
    If you call database routines from your form, than this could be the errro cause too.

  • ORA-00907: missing right parenthesis when using group by clause with xmlagg

    I have the following query and I am getting ORA 00907 Error when I am using group by clause with the xmlagg function.
    select xmlelement("Mitigation",
                    xmlelement("m_szMethodName",tm.DisplayName),
                    xmlelement("SubstanceInterferenceProtocolList",
                                (select xmlagg(xmlelement("MitigationProtocol",
                                        xmlelement("m_szMethodName",tm.DisplayName),
                                        xmlelement("m_szInterferenceProtocolName",tmp.protocol_name),
                                        xmlelement("m_szInterferenceSubstance",tmp.intf_mtrl_prod_code),
                                        xmlelement("m_ProtocolParameters",
                                            xmlelement("m_szProtocolName",tmp.protocol_name),
                                                xmlelement("m_Consumables",
                                                    xmlelement("Consumable",
                                                        xmlelement("m_szConsumId", xrl.rgnt_pack_name),
                                                        xmlelement("m_szProductCode",xrl.pack_prod_code),
                                                        xmlelement("m_nVolume",tmp.fluid_vol),
                                                        xmlelement("m_szProtocolStep",xps.protocol_step_name))),
                                                    xmlelement("m_ProtParamList",
                                                        xmlagg(
                                                        xmlelement("ParameterValues",
                                                            xmlelement("m_szProtocolName",tmp.protocol_name),
                                                            xmlelement("m_Time",xpsd.parameter_ntime_value))
                                                        group by tmp.ccd_test_id,tmp.intf_mtrl_prod_code)
                    order by tmp.ccd_test_id, tmp.intf_mtrl_prod_code, xps.protocol_step_intprotocolstep )
                    from XPR_tdef_mitigation_protocol tmp, xp_reagentlist xrl,
                    xpr_protocol_settings xps, xpr_protocol_settings_default xpsd
                    where tmp.ccd_test_id = tm.ccd_test_id
                    and tmp.ccd_test_id = xrl.ccd_test_id
                    and tmp.pack_prod_code = xrl.pack_prod_code
                    and tmp.intf_type = 1
                    and xps.protocol_name = xpsd.protocol_name
                    and xps.protocol_step_name = xpsd.protocol_step_name
                    and xps.ps_action_parameterlist = xpsd.ps_action_parameterlist
                    and xps.protocol_name =  tmp.PROTOCOL_NAME
    from XPtoXPRTdef_defn_mapping tm
    where tm.DisplayName = 'SYPH'If I remove the xmlagg clause along with the group by clause, the query runs fine and give me the output.
    But in that XML format of the output is incorrect for my application.
    Could someone help here?

    Hi,
    userAtoZ wrote:
    I have the following query and I am getting ORA 00907 Error when I am using group by clause with the xmlagg function.
    ... xmlagg(
    xmlelement("ParameterValues",
    xmlelement("m_szProtocolName",tmp.protocol_name),
    xmlelement("m_Time",xpsd.parameter_ntime_value))
    group by tmp.ccd_test_id,tmp.intf_mtrl_prod_code)Please don't post unformatted code. When posting any formatted text on this site, type these 6 characters:
    \(small letters only, inside curly brackets) before and after each section of formatted text, to preserve spacing.
    If the code above were formatted well, so that you could match each '(' with its closing ')', it would look something like this:... xmlagg ( xmlelement ( "ParameterValues"
                        , xmlelement ( "m_szProtocolName"
                                       , tmp.protocol_name
                        , xmlelement ( "m_Time"
                                       , xpsd.parameter_ntime_value
    group by tmp.ccd_test_id
                        ,     tmp.intf_mtrl_prod_code
    This is exactly what you posted, only the whitespace has been changed.
    This makes it clear that the GROUP BY is inside the parentheses with the argument to XMLAGG.  You can have an ORDER BY clause there, but not a GROUP BY clause.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

  • 'Order By' in Exists / Not Exists condition causing ORA-00907 in Apex4.1.1

    Hi Guys,
    We have just upgraded from apex 3.2.1 to 4.1.1. on Oracle DB V11.2.0.1, while testing the apps in apex, I come across this problem.
    When I have a page process that has a condition defined.
    When Condition Type is Exists (SQL query returns at least one row) or Not Exists (SQL query returns no rows) and the Expression 1 is a query with an 'Order By' clause, e.g.
    SELECT 123 FROM DUAL
    ORDER BY 1
    When the process is triggered, Apex 3.2.1 would evaluate the condition and run the process just fine, however Apex 4.1.1 would throw an error : ORA-00907: missing right parenthesis
    I totally understand that an Order by clause in an Exists or Not Exists condition is unnecessary and agree that they shouldn't be there in the first place.
    But unfortunately I am dealing with other developers codes and these conditions have been coded like these, probably from copy & paste codes.
    Saying that, I also believe that an Apex upgrade should not stop anything that is working in previous releases without warning or provide a workaround, right?
    I don't know if this affects other types of artifacts that can have a condition in apex when upgrading from 3.2.1, e.g Regions/Items/Computations/Validations etc.
    Does anyone else get this behaviour? and is there an easy solution to fix these?
    Ideally I don't want to go through all processes (and whatever other artifacts might be affected too) in all apps in all workspaces to check the condition type and remove the 'Order By' clause manually.
    Thanks for any advises
    Just did some more testing
    'Computation' , 'Validations', 'Processes' and 'Branches' have the same problem, 3.2.1 takes 'Order By' fine in Exists/Not Exists condition, but 4.1.1 throws error.
    'Regions', 'Buttons', 'Items' have consistent behaviour - both 3.2.1 and 4.1.1 throw error ORA-00907: missing right parenthesis, when page is rendered.
    Edited by: Danny on 25/04/2012 20:07

    Hi Danny,
    that's interesting. I just had a look what happens when you use an EXISTS or NOT EXISTS condition type. The following final SQL statement will be generated with your above example. You can also see that if you run your application in debug mode.
    select count(*) from sys.dual where exists (select 123 from dual order by 1)Executing that statement in SQL*Plus will also show the ORA-00907 error. It appears that the SQL parser doesn't allow an order by clause in an EXIST clause.
    I wonder why this should have worked in previous versions, but I can only suspect that in the past we may just have executed
    select 123 from dual order by 1which can be slightly slower because with the new EXISTS statement the SQL engine can stop processing earlier if it finds a record.
    We try to be backward compatible as much as possible, but I doubt that we will change that back to the way it was before because of the performance penalty 99.9% of our customers would face.
    Possible Workaround: You might be able to use the new "Application Search" to scan your application for "order by" and fix it for all hits where the attribute name is "Expression 1".
    Regards
    Patrick
    My Blog: http://www.inside-oracle-apex.com
    APEX Plug-Ins: http://apex.oracle.com/plugins
    Twitter: http://www.twitter.com/patrickwolf

  • OraOLEDB.Oracle GetRecordSet() throw "ORA-00907: missing right parenthesis"

    Hi,
    I am unfortunately working on an old VB6 app that is constructing a huge (11902 characters) ad-hoc SQL statement which is then passed to the GetRecordSet() method of my DBConnection. The app is using the OraOLEDB.Oracle provider. When the GetRecordSet() method is executed, however, I get the following error:
    ORA-00907: missing right parenthesis
    Now I have grabbed the contents of the string that is passed in to the GetRecordSet() function and have thoroughly examined it and there are no missing parens. Additionally, I am able to execute the select statement in Oracle SQL Developer as well as SQL*Plus, withou difficulty. So I am sure that the string is syntactically correct.
    I am beginning to suspect that something fishy is happening in the provider - perhaps the string is too long and it is getting truncated somewhere?
    Can anyone out there help me out?
    Thanks, Steve

    maybe the conversion you are trying to do is not valid especially in the first one into binary(1).
    check out the conversion table for CAST operator in the SQL REFERENCE of the documentation.

  • Error Generating Form against external application database

    I'm hoping the answer to this is simple, as others in the office can do this without any trouble, but can't remember how they made it work...
    My client has their repository and application schemas in separate databases. When I try and generate a form from the Design Editor, I get the following error:
    CDG-01281 ERROR: Module OASF95110: Oracle Forms binary file for MAINTAIN TARIFF AGREEMENT has NOT been created
    CDG-03418 WARNING: Module Component OASF95110.TARIFF_AGREEMENT: Missing action item to navigate to 'TARIFF_AGREEMENT_PARTNER'
    CDG-03400 WARNING: Module Component Table Usage OASF95110.TARIFF_AGREEMENT.TARIFF_AGREEMENT.TARIFF_AGREEMENT: 'Closed loop' of mandatory foreign keys found
    CDG-01263 ERROR: Module Component Table Usage OASF95110.TARIFF_AGREEMENT.TARIFF_AGREEMENT.TARIFF_AGREEMENT: User-defined condition (Table level Check Constraint TARIFF_AGREEMENT.TRFA_CK1) has an error: PL/SQL: ORA-00942: table or view does not exist
    What I seem to be missing, and have not been able to locate in any documentation, is how to tell Designer to look in a different database for the (already generated) schema objects.
    In a copy of the repository where I have generated the necessary objects into the same database as the repository, the form generates flawlessly...

    Tried that... Turns out the system uses the "Compiler" tab for validation, not for "Form Options" tab - It took a while, but one of the other developers finally remembered what they did and actually compared the screen prints I was providing with what they had in their environment...
    Thanks :)

Maybe you are looking for

  • Documents get shrunk by pdf creator

    I have Acrobat Pro 9 (9.4.3.321) and used to have no problems with the pdf printer. Of late, however, when I create pdf files with it, the original document becomes shrunk down to a ridiculous (and unusable) degree. I don't recall changing any settin

  • Scale of the graphic in interactive report doesn't work in french

    Dear all, I created a calculation column in an interactive report an put the format 9999999D99. When I displayed the information everything is ok. After that I tried to create a graphic with this column. The graphic is the type line The value is this

  • SGTXT field not saved in UD posting doc

    Dear QM guys I want to capture Reason for rejection in GR. We are posting rejection in "To Reserves" field in UD posting screen. Now i am trying to use "Document" near by "To reserves" for capturing Reason. I have changed my screen modification thru

  • I can't open FF and get message: Error: a is undefined

    FF won't open, even if in safe mode. Under FF, I get an error box with the message "Error: a is undefined" the error info is "Source File: http://www.google.com/extern_js/f/CgJlbhICdXMrMFo4ACwrMA44ACwrMBc4ACwrMDw4ACwrMFE4ACwrMFk4ACwrMAo4AEBdmgICcHMsK

  • FPGA module unzip problem

    I downloaded the FPGA module into a controler of a PXI, running XP.  When I tried to unzip it, the upzip operation would fail everytime.  What is causing this?  Is there some kind of requirement to unzip this?  Harddrive size requirement? Kudos and A