ORA-00933 with JDBC thin

Hello
After changing the Oracle DB pilot one provided with CF Enterprise to Oracle thin JDBC I meet a "Command successfully completed" ora-00933 exceptions. The syntax of SQL ist correct code (runs in SQL * more) and it worked fine before. It seems to be related mainly to insert subquery...

Has anyone an idea what goes wrong?
Are there patches / fixes available? (in collaboration with CF8 Fix2, Oracle 10 g 2, W2k3)

Thanks in advance


This is a confirmed bug and there is no work around.

It affects independent and related sql (cfqueryparam).

It will be released as part of the next update rollup (time unknown)

http://zacster.blogspot.com/2008/01/my-CF-Oracle-problem-ora-00933-was.html

Tags: ColdFusion

Similar Questions

  • ORA-00933 with the valid request

    During some tests with valid Oracle 12 c, I encountered the following problem:

    Environment:

    CREATE TABLE( adressen2)

    ADRID NUMBER (10) ALWAYS AS IDENTITY GENERATED,.

    persid NUMBER (10) NOT NULL,

    Strasse, VARCHAR2 (50 CHAR).

    TRO VARCHAR2 (50 CHAR),

    Land NUMBER (5),

    Please VARCHAR2 (8 CHAR),

    adrtyp NUMBER (2),

    Valid PERIOD

    );

    Insert a few lines without using "valid" (means valid)

    INSERT INTO adressen2 (persid, road, please, ort, Land, adrtyp, gueltig_start, gueltig_end)

    VALUES (100073, "Hohestraße 37', 50123', 'Burscheid', 7, 11, to_timestamp ('01.07.2014 ',' DD.)") MM YYYY'), NULL);

    UPDATE adressen2

    SET gueltig_end = to_timestamp ('30.06.2014 ',' DD.) MM YYYY')

    WHERE ADRID = 11;

    COMMIT;

    Connection with SQL * Plus 12.1.0.1.0

    SQL > SELECT * FROM adressen2 from the PERIOD OF valid SYSDATE WHERE adrid = 11;

    ADRID PERSID STRASSE ORT BUNDESLAND PLZ ADRTYP

    ---------- ---------- -------------------- ---------- ---------- -------- ----------

    11 100073 Scharnhorststrasse 15 07950 11 Triebes

    SQL > SELECT * FROM adressen2 ad from the PERIOD OF valid SYSDATE WHERE adrid = 11;

    SELECT * FROM adressen2 ad from the PERIOD OF valid SYSDATE WHERE adrid = 11

    *

    ERROR on line 1:

    ORA-00933: SQL not correctly completed command.

    So if I omit the table alias everything works fine, but for a real application, this is not enough.

    Well, it helps to have the right syntax - check the syntax diagram in the docs:

    The alias goes after the flashback query clause.

  • ORA-00933 with an update

    Hello world

    I get an error ORA-00933 when running this code:
    UPDATE type_composant 
    set  nom='RE', 
    libelle='Réglementaire', 
    process_export='YIYZD', 
    lien='0', 
    lien_technique='0', 
    lien_reglementaire='1', 
    lien_squelette='0', 
    lien_demande='0', 
    lien_pj='0', 
    id_type_comp_rattach=null, 
    id_type_comp_grp=null, 
    imp_comp=0, 
    imp_lien=0, 
    is_spec=1, 
    imp_sque=0, 
    spec_table='reglementaire', 
    spec_req='SELECT A.CDREGL AS CDREGL, 
    A.CDSTCO AS REPERTOIRE, 
    C.LILONG AS LIB_REP, 
    A.CDCODE AS CODE, 
    B.LIBLON AS LIB_CODE 
    FROM HR.ZD00 A, 
    HR.ZD01 B, 
    HR.DI31 C 
    WHERE A.NUDOSS = B.NUDOSS 
    AND A.CDSTCO = C.VACDST 
    AND C.CDLANG = 'F' 
    AND B.CDLANG = 'F' 
    AND CDSTCO  IN ('DS9','UPA','WS0','UGQ','UHU','DSJ','WF0','DRX','G01','DS3',
    'GCP','UAA','G02','G00','DRH','DRB','WAA','DRE','WR2','DRC','DRJ','GPR','DRM',
    'WA0','GCO','UIG','UIQ','DRF','WG2','XXX','UCB')', 
    comp_web='0' 
    where id_type_comp='36';
    And here is the error I got:
    AND C.CDLANG = 'F'
                    *
    ERROR at line 28:
    ORA-00933: SQL command not properly ended
    I don't know if it's from the SELECTION, and I think that the syntax is good.

    Any help would be nice!

    Andalusians

    Published by: Guich may 11, 2011 11:04

    Published by: Guich may 11, 2011 11:04

    And with tabs, it would be more readable:

    UPDATE type_composant
    set  nom='RE',
         libelle='Réglementaire',
         process_export='YIYZD',
         lien='0',
         lien_technique='0',
         lien_reglementaire='1',
         lien_squelette='0',
         lien_demande='0',
         lien_pj='0',
         id_type_comp_rattach=null,
         id_type_comp_grp=null,
         imp_comp=0,
         imp_lien=0,
         is_spec=1,
         imp_sque=0,
         spec_table='reglementaire',
         spec_req='SELECT A.CDREGL AS CDREGL,
                          A.CDSTCO AS REPERTOIRE,
                          C.LILONG AS LIB_REP,
                          A.CDCODE AS CODE,
                          B.LIBLON AS LIB_CODE
                   FROM HR.ZD00 A,
                          HR.ZD01 B,
                          HR.DI31 C
                   WHERE A.NUDOSS = B.NUDOSS
                   AND A.CDSTCO = C.VACDST
                   AND C.CDLANG = 'F'
                   AND B.CDLANG = 'F'
                   AND CDSTCO  IN ('DS9','UPA','WS0','UGQ','UHU','DSJ','WF0','DRX','G01','DS3',
                                   'GCP','UAA','G02','G00','DRH','DRB','WAA','DRE','WR2','DRC','DRJ','GPR','DRM',
                                   'WA0','GCO','UIG','UIQ','DRF','WG2','XXX','UCB')',
         comp_web='0'
    where id_type_comp='36';
    

    According to this, you use (') quotes by quotation marks, you must use two to make it work:

    UPDATE type_composant
    set  nom='RE',
         libelle='Réglementaire',
         process_export='YIYZD',
         lien='0',
         lien_technique='0',
         lien_reglementaire='1',
         lien_squelette='0',
         lien_demande='0',
         lien_pj='0',
         id_type_comp_rattach=null,
         id_type_comp_grp=null,
         imp_comp=0,
         imp_lien=0,
         is_spec=1,
         imp_sque=0,
         spec_table='reglementaire',
         spec_req='SELECT A.CDREGL AS CDREGL,
                          A.CDSTCO AS REPERTOIRE,
                          C.LILONG AS LIB_REP,
                          A.CDCODE AS CODE,
                          B.LIBLON AS LIB_CODE
                   FROM HR.ZD00 A,
                          HR.ZD01 B,
                          HR.DI31 C
                   WHERE A.NUDOSS = B.NUDOSS
                   AND A.CDSTCO = C.VACDST
                   AND C.CDLANG = ''F''
                   AND B.CDLANG = ''F''
                   AND CDSTCO  IN (''DS9'',''UPA'',''WS0'',''UGQ'',''UHU'',''DSJ'',''WF0'',''DRX'',''G01'',''DS3'',
                                   ''GCP'',''UAA'',''G02'',''G00'',''DRH'',''DRB'',''WAA'',''DRE'',''WR2'',''DRC'',''DRJ'',''GPR'',''DRM'',
                                   ''WA0'',''GCO'',''UIG'',''UIQ'',''DRF'',''WG2'',''XXX'',''UCB'')',
         comp_web='0'
    where id_type_comp='36';
    

    Nicolas.

  • Any movement on the expired with JDBC thin, passwords reset?

    Most of the links for this is quite old and say you need an oracle client to be able to reset the expired passwords, due to the limitations of the JDBC driver.

    Were there no movement on this (or any prospect of any movement?)

    Not that I know well, although it would be a great add to our users.

  • ORA 12505: JDBC Thin Client

    Hi all

    We face at the below of issues connecting to the server 11 g Oracle RAC using IP SCAN of JDK 1.7 application using JDBC Thin client

    [16/may / 2014:22:33:58] warning (6975): CORE3283: stderr: java.sql.SQLException: IO exception: connection refused (DESCRIPTION = (TMP =)(VSNNUM=186647552) (ERR = 12505) (ERROR_STACK = (ERROR = (CODE = 12505) (EMFI = 4)))

    [16/may / 2014:22:33:58] warning (6975): CORE3283: stderr: to oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)

    [16/may / 2014:22:33:58] warning (6975): CORE3283: stderr: to oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)

    [16/may / 2014:22:33:58] warning (6975): CORE3283: stderr: to oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:333)

    [16/may / 2014:22:33:58] warning (6975): CORE3283: stderr: to oracle.jdbc.driver.OracleConnection. < init > (OracleConnection.java:404)

    [16/may / 2014:22:33:58] warning (6975): CORE3283: stderr: to oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:468)

    [16/may / 2014:22:33:58] warning (6975): CORE3283: stderr: to oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:314)

    [16/may / 2014:22:33:58] warning (6975): CORE3283: stderr: to java.sql.DriverManager.getConnection(DriverManager.java:571)

    [16/may / 2014:22:33:58] warning (6975): CORE3283: stderr: to java.sql.DriverManager.getConnection(DriverManager.java:215)

    Entrance to the TNSNAMES file ORA has good 'service_name', compared to the entries in the DB server Listener.ora file.

    I only "tnsnames.ora' file in my client ' / opt/app/oracle/product/11.2.0/client_1/network/admin ' and my GUI application that uses as a reference.

    HELLO =

    (DESCRIPTION =

    (ADDRESS = (PROTOCOL = TCP) (HOST = < name > - orasvip.rr. < xyz >)(PORT = 1522))

    (LOAD_BALANCE = yes)

    (CONNECT_DATA =

    (SERVER = DEDICATED)

    (SERVICE_NAME = HELLO)

    )

    )

    = I checked all the blogs and confirmed with all the settings, please let me know if I should add any other libraries/configuration on the client side?

    All,

    JDBC connection string must be changed to connect to the DB CARS with names of SCAN VIP, Oracle RAC features using

    JDBC: thin: @(DESCRIPTION = (ADDRESS_LIST = (LOAD_BALANCE = yes) (ADDRESS = (PROTOCOL = TCP) (HOST =)(PORT=1522))) (CONNECT_DATA = (SERVER = DEDICATED)(SERVICE_NAME=)))

  • TLSv1.2 with the JDBC Thin driver

    I set up a secure connection, and the handshake connects using TLSv1.

    Is it possible to have him negotiate TLSv1.2?

    I use 12.1.0.2 ojdbc7.jar

    The connection is made via a javax.sql.DataSource with org.apache.commons.dbcp.BasicDataSourceFactory reference

    The secure connection works, and he negotiates a connection TLSv1. However, I was prompted to use TLSv1.2. The client initiates a handshake with:

    '* ClientHello, TLSv1 '.

    Which means that the server will negotiate with TLSv1.

    How can I get the client starts the negotiation with a Hello TLSv1.2?

    I tried to set the following options:

    -Djdk.tls.client.protocols = TLSv1.2

    -Dhttps.protocols = TLSv1.2

    but neither had an effect.

    For all those who come across of this question, here is the answer:

    When you use the version 12.1.0.2 of ojdbc7 of the Java JDBC Thin client, there is a known bug (19030178) where the JDBC client acknowledges not TLS 1.1 and 1.2 ciphers.

    There is a patch available if you have an Oracle support account.

    When connecting to an Oracle 12 server that has the support of TLS 1.2, with the patch I get now:

    ClientHello, TLSv1.2

    ServerHello, TLSv1.2

    and with a server Oracle 11 don't supports TLS 1, I get:

    ClientHello, TLSv1.2

    ServerHello, TLSv1

    and the communication continues in TLSv1

    It now works as expected.

  • Create_entailment fails with ORA-00933

    Hi all

    When I try to launch the creation of a new commitment,

    EXECUTE sem_apis.create_entailment('my_entailment', sem_models('my_model'), sem_rulebases('owlprime'));
    

    the procedure fails with the following error:

    ORA-00933: comando SQL terminato erroneamente
    ORA-06512: a "MDSYS.SDO_SEM_INF_INTERNAL", line 13518
    ORA-06512: a "MDSYS.SDO_SEM_INFERENCE", line 142
    ORA-06512: a "MDSYS.SDO_SEM_INFERENCE", line 184
    ORA-06512: a "MDSYS.RDF_APIS", line 108
    ORA-06512: a line 1
    00933. 00000 -  "SQL command not properly ended"
    *Cause:    
    *Action:
    

    I've never experienced this problem when I was working on my 11.2.0.1 instance of my machine to Windows Server 2008 R2, but it happens now that I've migrated to 11.2.0.3. The same command that worked no longer; This happens on the migrated database, as well as on a new database. Also, I checked MDSYS. RDF_PARAMETER and SEM_VERSION 11203 is valid.

    I did some research, but I have not found anything on this topic... and the error message is not to help me trying to understand what goes wrong.

    Any suggestion?

    Hello

    Are there changes to the character set, the setting of the nls, etc. with the new database?

    Before running the entailment create command, that help to run the first next?

    SQL > ALTER SESSION SET NLS_NUMERIC_CHARACTERS ='.,';

    Thank you

    Zhe Wu

  • JDBC: thin gives error mystery

    Hi all

    I'm using Oracle 11 G and I have a java clause that is used to connect the other DB and extract the data. Here is my Echappementjdbc

    Public Shared Sub query (string usr, String pssw, String hostname, String, String DB, String InitialDate port) survey of exceptions
    {
    Class.forName ("oracle.jdbc.OracleDriver");
    String url = "jdbc:oracle:thin:@//" + name + ":" + port + "/" + DB;
    Jacot connection = DriverManager.getConnection (url, usr, pssw);
    try {}
    Statement stmt = connIW.createStatement ();

    Now I get

    ORA-29532:
    Appeal of Java completed by eception Java exception: java.sql.SQLException:
    ORA-01017: name of user and password invalid. connection refused

    But I can't able to connetc with Sql developer, using the same user name, password, HOST, port, and DB Service name .

    Could help me solve the problem.

    Kind regards

    San.

    We have fixed the problem. This
    is an Oracle Bug, please see the Oracle note for reference below.

    Connection to the external database
    Oracle Jvm using the Jdbc thin driver server-side throws Ora-01017 (Doc ID
    1303712.1)

    Applies to:

    Version - JDBC: 11.2.0.1 and later [Release: 11.2 and later]

    Information in this document applies to any platform.

    Symptoms

    A Java stored procedure using the JDBC/thin driver side server to connect to
    another database.

    When Java code is deployed on a pre - 11 g of the side database server
    JDBC/thin connection works very well.

    Once the Java code is deployed on a 11.2 the database-side JDBC/thin server
    failed to connect with ORA-01017: name of user and password invalid. connection refused

    If the Java code is executed on an external JAVA virtual machine connection works fine.

    Despite the error ORA-01017 it was determined that the user name and
    password are correct, and that it is not a matter of case sensitivity.

    Cause

    Corruption with the JIT
    compiled version of Java code.

    Oraclei¿½
    The database Java Developer's Guide

    11g Release 1 (11.1)

    Part number B31225-05

    "Overview of the JITStarting JVM Oracle with Oracle 11 g release 1 (11.1),
    There's a just-in-time (JIT) compiler for Oracle JVM environment. A JIT
    for Oracle JVM compiler allows much faster execution, because it manages the
    invalidation, recompilation and code without an external storage
    mechanism. Based on profiling data collected dynamically, this compiler
    seamlessly selects the Java methods to compile to native machine code and
    dynamically make them available for Java sessions running. In addition, the
    compiler can take advantage of the Oracle JAVA virtual machine class model to
    possibly persist methods Java compiled in the database of calls, sessions, or
    instances. This persistence avoids unnecessary recompilations overload
    through sessions or instances, when we know that semantically the Java
    code has not changed. "

    Solution

    Workaround solution:

    change the system
    java_jit_enabled = FALSE;

    This allows the JIT code to be bypassed, by simply interpreting the Java
    the code that is generated by bytecode, rather than using the JIT.

    There is no need to re - compile Java code. Just run the command above


    and repeat the Java stored procedure.

    To restore the functionality of JIT just do:

    change the system
    java_jit_enabled = TRUE;

    Solution:

    Delete all the lines in the java table $ mc$ and restart the database

    The java$ mc$ table stores the persistent version of the JIT code generated
    for performance reasons. remove this code apparently requires the JIT to
    regenerate the code.

  • Bug ORA-00933

    Hello

    You can see my PL/SQL:

    SET VERIFY OFF;
    SET TIMING ON;
    WHENEVER SQLERROR EXIT BYEBYE;
    
    
    prompt >>> Début mise à jour F0005D
    
    
    DECLARE
    
    
    CURSOR ORIGIN IS
      SELECT * FROM F0005;     
    
    TYPE ARRAY_T IS VARRAY(8) OF VARCHAR2(2);
    ARRAY ARRAY_T := ARRAY_T('P', 'G', 'RU', 'I', 'S', 'E', 'DU', 'F');
    
    
    BEGIN
    FOR ORI IN ORIGIN LOOP
       FOR I IN 1..ARRAY.COUNT LOOP
         BEGIN
           INSERT INTO F0005D (DRSY,DRRT,DRKY,DRLNGP,DRDL01,DRDL02) VALUES (ORI.DRSY,ORI.DRRT,ORI.DRKY,ARRAY(I),ORI.DRDL01,ORI.DRDL02);
         EXCEPTION -- Traduction déjà existante
           WHEN DUP_VAL_ON_INDEX THEN
             UPDATE F0005D SET DRDL01=ORI.DRDL01,DRDL02=ORI.DRDL02 WHERE ORI.DRSY=DRSY,ORI.DRRT=DRRT,ORI.DRKY=DRKY,ARRAY(I)=DRLNGP;
         END;
       END LOOP;
    END LOOP;
    commit;
    END;
    /
    prompt ============= FIN MISE À JOUR F0005D =============
    EXIT;
    

    And I have this error message:

    >>> Début mise à jour F0005D
    Commit
    
    
    Erreur commençant à la ligne 7 de la commande :
    DECLARE
    
    
    CURSOR ORIGIN IS
      SELECT * FROM F0005;     
    
    TYPE ARRAY_T IS VARRAY(8) OF VARCHAR2(2);
    ARRAY ARRAY_T := ARRAY_T('P', 'G', 'RU', 'I', 'S', 'E', 'DU', 'F');
    
    
    BEGIN
    FOR ORI IN ORIGIN LOOP
       FOR I IN 1..ARRAY.COUNT LOOP
         BEGIN
           INSERT INTO F0005D (DRSY,DRRT,DRKY,DRLNGP,DRDL01,DRDL02) VALUES (ORI.DRSY,ORI.DRRT,ORI.DRKY,ARRAY(I),ORI.DRDL01,ORI.DRDL02);
         EXCEPTION -- Traduction déjà existante
           WHEN DUP_VAL_ON_INDEX THEN
             UPDATE F0005D SET DRDL01=ORI.DRDL01,DRDL02=ORI.DRDL02 WHERE ORI.DRSY=DRSY,ORI.DRRT=DRRT,ORI.DRKY=DRKY,ARRAY(I)=DRLNGP;
         END;
       END LOOP;
    END LOOP;
    --commit;
    END;
    Rapport d'erreur :
    ORA-06550: Ligne 16, colonne 83 :
    PL/SQL: ORA-00933: la commande SQL ne se termine pas correctement
    ORA-06550: Ligne 16, colonne 10 :
    PL/SQL: SQL Statement ignored
    06550. 00000 -  "line %s, column %s:\n%s"
    *Cause:    Usually a PL/SQL compilation error.
    *Action:
    Elapsed: 00:00:00.017
    

    What is the problem please?

    Thank you.

    Take a look at the where clause in your update statement. You bind the predicates of equality with commas: you and probably average.

    More importantly if: you are using online = slow-by-slow cursors.

    Why you don't do this as a MERGE statement? It will be much faster.

  • TAF with JDBC

    Hi All-

    I know this is old dead topic and has been discussed several times on the forums. For some reason, I always found myself in a State of doubt so thought ask the experts here. I saw on multiple threads that TAF does not work with JDBC and we can take advantage of features such as CWF & FAN events for HA features.

    However, the link to the documentation below

    http://docs.Oracle.com/CD/B19306_01/Java.102/b14355/instclnt.htm#CIHHHDCH

    indicates that the failover Transparent to the JDBC OCI driver enforcement feature allows to automatically reconnect to a database if the database instance to which is made the connection goes down. The new database connection, well that created by another node, is identical to the original.


    should I assume that the jdbc connections works with TAF? I did a quick test and try to connect to my server from ebiz R12 with TAF service forms and I could get with failover. I'm not expert ebiz but I believe that Ebiz forms servers also uses JDBC connectivity.

    Could you please help me understand how JDBC OCI as JDBC thin client? or in simple words, TAF does work with JDBC.

    Thank you.

    Published by: 858634 on January 23, 2013 12:30 AM

    Yes.

  • ORA-00933 sql is not properly completed.

    Dear members,

    I have the following query in Report Builder 10g,

    Select a, b, c
    FROM table1
    where a = 12

    & p_whr_fy & p_whr_supp & p_whr_bt & p_whr_mat_spec & p_whr_lc_num & p_whr_cotton & P_WHR_LOC_ID

    Union of all the

    Select a, b, c
    from table2
    where a = 12

    & p_whr_fy & p_whr_supp & p_whr_bt & p_whr_mat_spec & p_whr_lc_num & p_whr_cotton & P_WHR_LOC_ID

    Here I used the lexical settings, and with spaces in the lines its ok but when trying to change the query / remove spaces in the lines, it gives the error.

    ORA-00933 sql not successfully completed

    With regard to:

    Hello
    Check your default values for substitution variables, at least one of them is not empty and causes an error.
    kikolus

  • Error ORA-00933

    Hi all, when I try to perform under query I get PL/SQL: ORA-00933: not correctly completed SQL command can someone tell where I'm wrong?
    DECLARE
    
    V_HEADER_ID NUMBER;
    
    V_GROUP_ID NUMBER;
    
    
    BEGIN
    
    
    select regal.regal_inv_landed_cost_seq.nextval.NEXTVAL into V_GROUP_ID from dual ;
    
    select regal.regal_inv_landed_cost_seq.nextval.currval into V_HEADER_ID from dual ;
    
    INSERT INTO rcv_transactions_interface 
    (
                 INTERFACE_TRANSACTION_ID,
                 HEADER_INTERFACE_ID,
                 GROUP_ID,
                 TRANSACTION_TYPE,
                 TRANSACTION_DATE,
                 PROCESSING_STATUS_CODE,
                 PROCESSING_MODE_CODE,
                 TRANSACTION_STATUS_CODE,
                 QUANTITY,
                 LAST_UPDATE_DATE,
                 LAST_UPDATED_BY,
                 CREATION_DATE,
                 CREATED_BY,
                 RECEIPT_SOURCE_CODE,
                 DESTINATION_TYPE_CODE,
                 AUTO_TRANSACT_CODE,
                 SOURCE_DOCUMENT_CODE,
                 UNIT_OF_MEASURE,
                 ITEM_ID,
                 UOM_CODE,
                 EMPLOYEE_ID,
                 SHIPMENT_HEADER_ID,
                 SHIPMENT_LINE_ID,
                 TO_ORGANIZATION_ID,
                 SUBINVENTORY_ID,
                 FROM_ORGANIZATION_ID,
                 FROM_SUBINVENTORY
    )
    SELECT 
         regal.regal_inv_landed_cost_seq.nextval,      --Interface_transaction_id
         V_HEADER_ID,                                  --Header Interface ID
         V_GROUP_ID,                                    --Group ID
         'Ship',                                       --Transaction Type
         sysdate,                                      --Transaction Date
         'PENDING',                                    --Processing Status Code
         'BATCH',                                      --Processing Mode Code
         'PENDING',                                    --Transaction Status Code
         lc.quantity_received,                          --Quantity
         lc.last_update_date,                          --last update date
         lc.last_updated_by,                           --last updated by
         sysdate,                                      --creation date
         lc.created_by,                                --created by
         'INVENTORY',                                  --Receipt source Code
         'INVENTORY',                                  --Destination Type Code
         'DELIVER' ,                                    --AUT Transact Code
         'INVENTORY',                                  --Source Document Code
          msi.primary_uom_code ,                       --Unit Of Measure
          msi.inventory_item_id,                        --Item ID
          msi.primary_unit_of_measure,                  --UOM COde
          regal.regal_inv_landed_cost_seq.curval,       --Shipment Header ID
          regal.regal_inv_landed_cost_seq.curval,       --SHipment Line ID
          82,                                           --To Organization ID
          'Brooklyn',                                     --Sub Inventory ID
          81,                                            --From Organization
          'Vessel'                                       --From Subinventory
      
      FROM
         regal.regal_inv_landed_cost_tab lc,
         mtl_system_items msi
    
      WHERE
         lc.organization_id = msi.organization_id
         AND  lc.inventory_item_id = msi.inventory_item_id
    END;
    
    ERROR at line 70:
    ORA-06550: line 69, column 56:
    PL/SQL: ORA-00933: SQL command not properly ended
    ORA-06550: line 7, column 1:
    PL/SQL: SQL Statement ignored
    ORA-06550: line 70, column 4:
    PLS-00103: Encountered the symbol "end-of-file" when expecting one of the
    following:
    ( begin case declare end exception exit for goto if loop mod
    null pragma raise return select update while with
    <an identifier> <a double-quoted
    Thanks in advance!

    These lines:

    Sandy wrote:

    select regal.regal_inv_landed_cost_seq.nextval.NEXTVAL into V_GROUP_ID from dual ;
    
    select regal.regal_inv_landed_cost_seq.nextval.currval into V_HEADER_ID from dual ;
    

    Probably should be this instead:

    select regal.regal_inv_landed_cost_seq.NEXTVAL into V_GROUP_ID from dual;
    select regal.regal_inv_landed_cost_seq.currval into V_HEADER_ID from dual;
    
  • How to recognize an exception with JDBC user-defined?

    declare
    x exception;
    begin 
     raise x;
    end;
    When you call this (or a similar procedure) with JDBC *, I get just a general java.sql.SQLException: ORA-06510: PL/SQL: not supported by the user-defined exception

    Is there a way to get more information about the exception?
    Then the client code can tell one from the other.


    * Spring JDBC actually

    Given this pl/sql block, he has nothing else to report, you raise just a generic exception. Try something more like:

    begin
       raise_application_error(-20001, 'Something bad happened');
    end;
    

    or, if you really want the e

    declare
       x exception;
    begin
       raise e;
    exception
       when e then
       raise_application_error(-20001, 'E happened');
    end;
    

    John

  • Group ADF opening too many sessions of database JDBC Thin Client.

    Hi all

    I have several panels of the ADF, which allows the user to run some simple queries against a database of Oracle is using the view objects ADF and ADF view links and ADF application module.
    Each ADF Panel as I mentioned contains several queries view link and links in the form of Jbuttons to other ADF signs other ADF links running.
    Run Control Panel of the ADF as described here opens up to 21 sessions of data showing as "JDBC Thin Client" when I look at their place of session$ v.
    Why I find myself with a lot of databases of sessions.
    Why didn't he just uses one or two sessions of database to run all of these links to view? It seems that it opens a session of data base for each of these links to view.

    How can I change this destructive behavior? I have that one to see one or two sessions of database for the whole ADF matter how ADF display the links it contains.
    Your suggestions are most appreciated.

    Thank you.
    Bobby has.

    Why so many AMs? Can not put all the your under a single AM?
    Each AM you will use will open a connection to the DB.

  • CN460A: ADF print copy with a thin line from top to bottom?

    ADF print copy with a thin line from top to bottom of page.  fine prints from the PC to the printer...

    This was probably caused by a specification on the thin glass used for scanning form the ADF.  See here for more information on cleaning this area to solve printing line when using the ADF.

Maybe you are looking for