JOIN syntax for Oracle 8i

I have a SQL statement which looks like this:
SELECT * FROM user.table table LEFT OUTER JOIN user.table2 table2 ON table.column = table2.column;
Which seems to be the right syntax according to the Oracle SQL reference, but when I try and execute it I get the error:
ERROR at line 1:
ORA-00933: SQL command not properly ended
Is there a difference between 9i and 8i syntax?

Using LEFT OUTER JOIN was introduced in 9i
I have a SQL statement which looks like this:
SELECT * FROM user.table table LEFT OUTER JOIN user.table2 table2 ON table.column = table2.column;
Which seems to be the right syntax according to the Oracle SQL reference, but when I try and execute it I get the error:
ERROR at line 1:
ORA-00933: SQL command not properly ended
Is there a difference between 9i and 8i syntax?

Similar Messages

Bug in JOIN syntax? (oracle 9i)

Hi,
take these three tables:
MASTER (id NUMBER, name VARCHAR2(10))
DETAIL (id NUMBER, master_id NUMBER)
SUBDETAIL (id NUMBER, detail_id NUMBER, name VARCHAR(10)
When I perform this query:
SELECT SUBDETAIL.id as did, MASTER.id as mid
FROM SUBDETAIL
JOIN DETAIL ON (SUBDETAIL.detail_id = DETAIL.id)
JOIN MASTER ON (DETAIL.master_id = MASTER.id)
WHERE
name = 'joe';
I would expect the parser to give me 'column ambiguously defined' (because the 'name' field from the whereclause is defined in both subdetail and master).
However, it does not say that. Instead, it assumes that it should use the name field from master. This is confusing, as this could easily lead to mistakes (as it did in my application)
Greetings,
Ivo

There seems to be a difference between the way Oracle resolves column names using the ANSI join syntax and Oracle's syntax. It appears that Oracle does not know about the columns, until it processes each join, and further, the last table joined seems to be sued to resolve nameing conflicts. Consider:
SQL> SELECT * FROM master;
        ID NAME
         1 joe
SQL> SELECT * FROM subdetail;
        ID DETAIL_ID NAME
         1          2 fred
SQL> SELECT * FROM detail;
        ID MASTER_ID
         2          1
SQL> SELECT subdetail.id AS did, master.id AS mid
2 FROM subdetail
3       JOIN detail ON (subdetail.detail_id = detail.id)
4       JOIN master ON (detail.master_id = master.id)
5 WHERE name = 'joe';
       DID        MID
         1          1
SQL> SELECT subdetail.id AS did, master.id AS mid
2 FROM subdetail
3       JOIN detail ON (subdetail.detail_id = detail.id)
4       JOIN master ON (detail.master_id = master.id)
5 WHERE name = 'fred';
no rows selected
So, it is clearly going after master.name. However,
SQL> SELECT subdetail.id AS did, master.id AS mid
2 FROM detail
3       JOIN master ON (master.id = master_id)
4       JOIN subdetail ON (subdetail.detail_id = detail.id)
5 WHERE name = 'joe'
no rows selected
But,
SQL> SELECT subdetail.id AS did, master.id AS mid
2 FROM detail
3       JOIN subdetail ON (subdetail.detail_id = detail.id)
4       JOIN master ON (master.id = master_id)
5 WHERE name = 'joe'
       DID        MID
         1          1
Old style syntax gives:
SQL> SELECT subdetail.id AS did, master.id AS mid
2 FROM subdetail, detail, master
3 WHERE subdetail.detail_id = detail.id and
4        detail.master_id = master.id and
5        name = 'joe';
      name = 'joe'
ERROR at line 5:
ORA-00918: column ambiguously defined
and note that
SQL> SELECT subdetail.id AS did, master.id AS mid
2 FROM subdetail
3      JOIN master ON (detail.master_id = master.id)
4      JOIN detail ON (subdetail.detail_id = detail.id)
5 WHERE name = 'joe'
    JOIN master ON (detail.master_id = master.id)
ERROR at line 3:
ORA-00904: invalid column nameSo, in ANSI syntax, order matters, and whatever the syntax good testing matters.
TTFN
John

Urgent: Regarding Join Syntax in Oracle 9i and 10g

Dear Members
Please help me by providing me the synatx of following Join statements for Oracle 9i and 10g:
1.Inner Join
2.Left Outer Join
3.Right Outer Join
4.Self Join
5.Cross Join
6.Full Outer Join
N.B. I NEED THIS HELP URGENTLY
Regards
Praveen Kumar Pandey

Inner join
SELECT *
FROM a,
       b
WHERE a.<<column>> = b.<<column>>Left Outer Join
SELECT *
FROM a LEFT OUTER JOIN b
         ON a.<<column>> = b.<<column>>Right Outer Join
SELECT *
FROM a RIGHT OUTER JOIN b
         ON a.<<column>> = b.<<column>>Full Outer Join
SELECT *
FROM a FULL OUTER JOIN b
         ON a.<<column>> = b.<<column>>Self Join
SELECT *
FROM a a1,
       a a2
WHERE a1.<<column>> = a2.<<column>>Cartesian Join
SELECT *
FROM a,
       bJustin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

Is this syntax for oracle database?

Does the syntax below indicates that the developer is using oracle database?
PreparedStatement updt = db.prepareStatement("insert into tablename values (?, ?, ?, ?, ?)");
updt.setInt(1, number);
updt.setInt(2, 1);
updt.setString(3, staffName);
updt.setString(4, description);
updt.setDate(5, today);

Oh...
but when I use microsoft access, it didn't seems to work
error is:
SQL data type out of array
the PreparedStatement and it's associate syntax don't work with ODBC?

ASP syntax for Oracle update with parameters

I am trying to do update on aspx page (not with code behind). I can perform update without parameters but I get ORA-0136 illegal variable name/number when I try to use a parameter in where clause. I added the parameter with tag - <asp:Parameter>

ASPX page is below.
The issue is the UPDATE for last Gridview (Gridview3). If I put a literal in the WHERE clause (i.e., "...WHERE ITEMNUM = '0001'"", then the update works. So, it appears the issue is how I code the parameter.
Thanks...
==============================================
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="WebForm4.aspx.cs" Inherits="OraWeb1.WebForm4" %>
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
    <title></title>
</head>
<body>
    <form id="form1" runat="server">
    <div>
    vendor quote status
        <br />
        <asp:Label ID="Label1" runat="server"></asp:Label>
        <br />
        <br />
        <asp:Label ID="Label2" runat="server"></asp:Label>
        <br />
        <br />
    </div>
    <div>
        rfqvendordetail
        <asp:GridView ID="GridView1" runat="server" Width="681px" DataSourceID="RFQVendorDetail" BackColor="White" BorderColor="#999999" BorderStyle="None" BorderWidth="1px" CellPadding="3" GridLines="Vertical">
            <AlternatingRowStyle BackColor="#DCDCDC" />
            <FooterStyle BackColor="#CCCCCC" ForeColor="Black" />
            <HeaderStyle BackColor="#000084" Font-Bold="True" ForeColor="White" />
            <PagerStyle BackColor="#999999" ForeColor="Black" HorizontalAlign="Center" />
            <RowStyle BackColor="#EEEEEE" ForeColor="Black" />
            <SelectedRowStyle BackColor="#008A8C" Font-Bold="True" ForeColor="White" />
            <SortedAscendingCellStyle BackColor="#F1F1F1" />
            <SortedAscendingHeaderStyle BackColor="#0000A9" />
            <SortedDescendingCellStyle BackColor="#CAC9C9" />
            <SortedDescendingHeaderStyle BackColor="#000065" />
        </asp:GridView>
        <asp:SqlDataSource ID="RFQVendorDetail" runat="server" ConnectionString="<%$ ConnectionStrings:OraContracts %>" ProviderName="<%$ ConnectionStrings:OraContracts.ProviderName %>" SelectCommand="SELECT "ITEMNUM", "MFRNUM", "DESCRIPTION", "UOM", "QTY", "UNITPRICE", "TOTALPRICE" FROM "RFQVENDORDETAILS" WHERE (("VENDORID" = :VENDORID) AND ("RFQID" = :RFQID))">
            <SelectParameters>
                <asp:SessionParameter Name="VENDORID" SessionField="vendorid" Type="String" />
                <asp:SessionParameter Name="RFQID" SessionField="RFQID" Type="String" />
            </SelectParameters>
        </asp:SqlDataSource>
        <br />
        <br />
        <asp:GridView ID="GridView2" runat="server" AutoGenerateColumns="False" DataSourceID="testrows" Width="526px">
            <AlternatingRowStyle BackColor="#DCDCDC" />
            <FooterStyle BackColor="#CCCCCC" ForeColor="Black" />
            <HeaderStyle BackColor="#000084" Font-Bold="True" ForeColor="White" />
            <PagerStyle BackColor="#999999" ForeColor="Black" HorizontalAlign="Center" />
            <RowStyle BackColor="#EEEEEE" ForeColor="Black" />
            <SelectedRowStyle BackColor="#008A8C" Font-Bold="True" ForeColor="White" />
            <SortedAscendingCellStyle BackColor="#F1F1F1" />
            <SortedAscendingHeaderStyle BackColor="#0000A9" />
            <SortedDescendingCellStyle BackColor="#CAC9C9" />
            <SortedDescendingHeaderStyle BackColor="#000065" />
            <Columns>
                <asp:BoundField DataField="RFQID" HeaderText="RFQID" SortExpression="RFQID" />
                <asp:BoundField DataField="ITEMNUM" HeaderText="ITEMNUM" SortExpression="ITEMNUM" />
                <asp:BoundField DataField="QTY" HeaderText="QTY" SortExpression="QTY" />
                <asp:BoundField DataField="UOM" HeaderText="UOM" SortExpression="UOM" />
                <asp:TemplateField HeaderText="UNITPRICE" SortExpression="UNITPRICE">
                    <EditItemTemplate>
                        <asp:TextBox ID="TextBox1" runat="server" Text='<%# Bind("UNITPRICE") %>'></asp:TextBox>
                    </EditItemTemplate>
                    <ItemTemplate>
                        <asp:Label ID="Label1" runat="server" Text='<%# Bind("UNITPRICE") %>'></asp:Label>
                    </ItemTemplate>
                </asp:TemplateField>
            </Columns>
        </asp:GridView>
        <asp:SqlDataSource ID="testrows" runat="server" ConnectionString="<%$ ConnectionStrings:OraContracts %>" ProviderName="<%$ ConnectionStrings:OraContracts.ProviderName %>" SelectCommand="select rfqid,itemnum,qty,uom,unitprice from rfqvendordetails WHERE (("VENDORID" = :VENDORID) AND ("RFQID" = :RFQID))">
            <SelectParameters>
                <asp:SessionParameter Name="VENDORID" SessionField="vendorid" Type="String" />
                <asp:SessionParameter Name="RFQID" SessionField="RFQID" Type="String" />
            </SelectParameters>
        </asp:SqlDataSource>
        <br />
        <br />
        <asp:GridView ID="GridView3" runat="server" DataSourceID="testupd" Width="425px" AutoGenerateColumns="False">
            <Columns>
                <asp:CommandField ShowEditButton="True" />
                <asp:BoundField DataField="RFQDETAILID" HeaderText="RFQDETAILID" SortExpression="RFQDETAILID" />
                <asp:BoundField DataField="ITEMNUM" HeaderText="ITEMNUM" SortExpression="ITEMNUM" />
                <asp:BoundField DataField="DESCRIPTION" HeaderText="DESCRIPTION" SortExpression="DESCRIPTION" />
                <asp:BoundField DataField="QTY" HeaderText="QTY" SortExpression="QTY" />
                <asp:BoundField DataField="UOM" HeaderText="UOM" SortExpression="UOM" />
                <asp:BoundField DataField="UNITPRICE" HeaderText="UNITPRICE" SortExpression="UNITPRICE" />
                <asp:BoundField DataField="TOTALPRICE" HeaderText="TOTALPRICE" SortExpression="TOTALPRICE" />
            </Columns>
        </asp:GridView>
        <asp:SqlDataSource ID="testupd" runat="server" ConnectionString="<%$ ConnectionStrings:OraContracts %>" ProviderName="<%$ ConnectionStrings:OraContracts.ProviderName %>" SelectCommand="SELECT "RFQDETAILID", "ITEMNUM", "DESCRIPTION", "QTY", "UOM", "UNITPRICE", "TOTALPRICE" FROM "RFQVENDORDETAILS" WHERE (("VENDORID" = :VENDORID) AND ("RFQID" = :RFQID))" UpdateCommand="UPDATE CONTRACTS.RFQVENDORDETAILS SET DESCRIPTION = 'Test Desc2' WHERE ITEMNUM = :ITEMNUM">
            <SelectParameters>
                <asp:SessionParameter Name="VENDORID" SessionField="vendorid" Type="String" />
                <asp:SessionParameter Name="RFQID" SessionField="RFQID" Type="String" />
            </SelectParameters>
            <UpdateParameters>
                <asp:Parameter Name="ITEMNUM" Type="String" />
            </UpdateParameters>
        </asp:SqlDataSource>
        <br />
        <br />
    </div>
        <div>
            vendor comments</div>
    </form>
</body>
</html>
==============================================

ANSI inner join syntax

Hi,
Is there a way to configure BI Server 11g to generate ANSI join sytax ("INNER JOIN" clause) for Oracle, as it does when using OUTER JOINs?
Thank you.

OBIEE will not generate ANSI syntax for Inner Joins and as you said it only generates for Outer joins. Hope this clears your doubt.

OBIEE not applying outer join syntax to filters

(Note: I've already thoroughly searched the forums before posting this. Thanks)
My problem is the following:
I'm trying to build a report that is a count from my fact table, grouped by month from my date dimension for a given year, resulting in 12 data points. The problem is that not all months have actual data, but I still need those months to show on the report with a count of zero. Typical simple reporting requirement.
I have already done the obvious and within my business layer made the join between my fact table and my date dimension an outer join on the fact side, just like you'd do if writing the query by hand. And when tested by hand this includes all dates for the year anyway, and when coupled with the appropriate null test on the count measure I'd get my 12 data points with zeros were appropriate.
The problem is that there are additional filters I need to apply on the fact data (there are a couple text-based code values that didn't warrant full tables themselves so are just degenerate dimensions directly on the fact table.)
When these filters are applied at the Answer level, I'm only getting back the months that actually have data, and lose the months where the count should be zero. A check of the session log for the query that was generated shows the problem. While OBI properly generates the outer-join syntax for the join itself between the two tables (my date dim and fact table) it does NOT apply the outer-syntax to the constant-based filter against the fact, effectively negating the outer join.
Actual query from the log (I simply changed the table aliases from the ugly T##### stuff OBI generates to something more readable for posting here):
select D.DT_MONTH_NAME as c1,
D.DT_MONTH_NUM as c2,
I.INC_TYPE as c3,
I.INC_EMP_GROUP as c4,
sum(case when I.INC_KEY is null then 0 else 1 end ) as c5
from DATE_DIM D, INCIDENT_F I
where ( D.DATE_KEY = I.DATE_KEY (+) ) and ( D.DT_YEAR = 2010 and I.INC_EMP_GROUP = 'CONTRACTOR' )
group by D.DT_MONTH_NUM, D.DT_MONTH_NAME, I.INC_TYPE, I.INC_EMP_GROUP
order by c2
You can see that the outer syntax (+) is applied to the join, but not to the filter on I.INC_EMP_GROUP. If I take this query and drop it in something like SQL Developer, it only returns the months with data. If I throw the (+) after I.INC_EMP_GROUP like I'd do if writing this by hand, the desired zero-months results pop back in.
I have already searched the forums and while lots of people seem to have asked this question, the only solutions involve things like trickery in the business layer using dummy fact tables followed by manipulations at the report level etc. Unfortunately I can't rely on these as the system is eventually to be turned over to users who can't be expected to apply various hacks to write reports.
Anyone ever get to the bottom of getting OBI to apply outer join logic in filters as well, when the filtered table is meant to be outer-joined to?
Any comments are appreciated.
John

I know that this thread is a bit old thought it might be helpful to some one...
The Issue is, when using Degener@teDimen$ion ( this is !nner joned to FACT tables in BMM) and if any of the dimensions {other than theDegener@teDimen$ion (Let us say Dim X) } have an ()uter join to any of the fact tables, and you were doing your analysis using Degener@teDimen$ion, Dim X, Measure value you will face the following issues.
when filtering the analysis on the ()uter join dimension ( Dim X), the IN filter will not work. Reason is that the filter is getting applied to both the Dimension and FACT tables and the values that exist in Dimension Dim X but not in FACT table wont show up.
The above issue can be fixed by changing the join between the fact and Degener@teDimen$ion from inner to outer. I think this is a bug.. because it is supposed to filter the fact table after the entire outer joined result is obtained but not filter the fact table for the Dim X values and do a outer join. I think the BI should be intelligent enough.

OJ syntax for multi-table left outer join with MS Oracle Driver

I have a multi-table left outer join that works fine in SQL Server ODBC Driver, Oracle ODBC driver 8.01.07.00, but not with Microsoft ODBC Driver for Oracle 2.573.7326.0
SELECT * from { oj A LEFT OUTER JOIN B ON A.col1 = B.col1 LEFT OUTER JOIN C ON A.col1 = C.col1 }
I noticed someone had a similar problem (the proposed solution doesn't work):
http://www.justpbinfo.com/listarchive/msg02874.html
Does anyone know how to get this working with the Microsoft ODBC Driver for Oracle? Or does it just not work?

The Microsoft ODBC Driver for Oracle 2.573.7326.0 does perform the same 'fix up' with {oj} in Oracle 8i. The problem is that it doesn't work when joining more than two tables:
This works:
SELECT * from { oj A LEFT OUTER JOIN B ON A.col1 = B.col1}
This doesn't work:
SELECT * from { oj A LEFT OUTER JOIN B ON A.col1 = B.col1 LEFT OUTER JOIN C ON B.col1 = C.col1 }
(The second query will work with the Oracle Oracle ODBC driver, with a bit of tweaking. But I haven't found a way to get it to work with the Microsoft ODBC Driver for Oracle 2.573.7326.0. My suspicion is that it just doesn't work.)
Gavin

Difference between oracle join syntaxes and ANSI join syntaxes

What is difference between oracle join syntaxes and ANSI join syntaxes ?
why oracle is having different syntaxes for joins than ANSI syntaxes ?
Also Join syntaxes are different in some oracle vesrions ?

BluShadow wrote:
3360 wrote:
Yes it is. The Oracle database wasn't initially designed to be ANSI compliant. As you correctly state the ANSI standards weren't around when it was initially designed, so the statement is perfectly correct. ;)Ok, in one sense it may be correct but it is a completely misleading statement. Not sure why you think it's misleading.Because there was no ANSI standard, so making it sound like a design choice The Oracle database wasn't initially designed to be ANSI compliant. would suggest to most readers that there was a standard to be compliant to.
Like saying Ford originally did not design their cars to incorporate safety features such as ABS, seat belts and air bags.
The OP asked "why oracle is having different syntaxes for joins than ANSI syntaxes ?" and the answer is that Oracle wasn't initially designed with ANSI compliance, so it has it's old non-ANSI syntax,As shown above, the old syntax was ANSI compliant at the time and to call it non-ANSI is either incorrect or misleading dependent on your point of view.
and since ANSI syntax became the standard it now supports that. And since ANSI switched to a new standard, Oracle had to implement the new standard as well as the previous ANSI standard would be more accurate in my opinion.
Nothing misleading as far as I'm aware in that.I find the whole discussion about ANSI and Oracle's supposed non-compliance, reads like it was Oracle's choice to deviate from the standards, when it was ANSI's bullheaded decisions to pointlessly change standards that left Oracle and other vendors out of compliance, and that was a decision made solely by ANSI.
This is probably the reason ANSI no longer produces SQL standards, the endless syntax fiddling would eventually have made forward left under outer joins a reality.
{message:id=1785128}

Database Connection Error 42000:[Microsoft][ODBC driver for oracle] Syntax

Hi,
This is Sathish, I am trying to create a report and retrieve data through stored procedure using ODBC Connection. When connecting to the Stored Procedure it is showing Database Connection Error 42000:[Microsoft][ODBC driver for oracle] Syntax error or access violation' Error.
CRXI R2, Oracle 9i.
What do i do to solve this issue.
Regards,
Sathish

Hi Satish
It could be an issue with the driver.
You can try with the OLEDB n Oracle native connection to test if the issue persists.
Also you can refer to the [Troubleshooting Database Connectivity for Crystal Reports|http://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/d05b3bb7-0f28-2c10-4ea3-84dbdc4e414e&overridelayout=true]
Hope this helps!!
Regards
Sourashree

[Microsoft][ODBC driver for Oracle]Syntax error or access violation

Hi,
When I am trying to connect to Oracle 8.1.6 database using Microsoft ODBC driver for Oracle. The connection is established.
But while creating CallableStatement, I am getting error "[Microsoft][ODBC driver for Oracle]Syntax error or access violation".
What I need to do to resolve this problem.
Raj

Hi Satish
It could be an issue with the driver.
You can try with the OLEDB n Oracle native connection to test if the issue persists.
Also you can refer to the [Troubleshooting Database Connectivity for Crystal Reports|http://www.sdn.sap.com/irj/boc/index?rid=/library/uuid/d05b3bb7-0f28-2c10-4ea3-84dbdc4e414e&overridelayout=true]
Hope this helps!!
Regards
Sourashree

Outer Join Syntax in sql2k to Oracle Migration

All of my existing SQL Server 2000 code is using the (INNER, LEFT OUTER, RIGHT OUTER) JOIN syntax which according to Oracle SQL Reference (A90125-01) is supported. The migration workbench seems to want to convert this to the old style syntax of putting (+) in the where clause conditions. I am therefore getting lots of warnings telling me that "complex outer joins are not reliably supported". Is there a setting somewhere that will tell the migration workbench to maintain (subject to required conversion) the original syntax format.

Hi Doug,
The issue you report has been tackled in a recent internal build released by the OMWB team. OMWB version 9.2.0.1.6 which is freely downloadable on the http:\\mtg.ie.oracle.com site. As I've mentioned, this is an internal release and is therefore not supported - although it is very stable and has already been used by several internal customers. We expect to have a fully supported release of OMWB available on OTN in December.
In version 9.2.0.1.6, there is an option in the "Parse Options" tab on the Stored Procedures property sheet called "Generate Oracle 8i Outer Joins" - this setting is switched off by default in this build and would therefore preserve your ANSI compliant joins by default. Switching the setting on causes the OMWB parser to generate the joins in the old (+) Oracle syntax standard.
I hope this helps,
Tom.

Syntax for Data Pump in Oracle Database 11g

Hi, thanks to all. i myself clarifying many doubts by refering the POSTS in this Forum.
I need the syntax for the Data Pump in Oracle 11g.
Could you post the syntax plese.
Thanks & Regards..

Hello,
You may have all the options in Datapump by typing the statements belows:
expdp help=y
impdp help=yElse, you'll have much more details and examples in the Utilities book from Oracle 11g documentation on the link below:
http://www.comp.dit.ie/btierney/Oracle11gDoc/server.111/b28319/part_dp.htm#i436481
Hope this help.
Best regards,
Jean-Valentin
Edited by: Lubiez Jean-Valentin on Apr 19, 2010 11:07 PM

Oj syntax for outer join

Is there a way to make Crystal Reports XI not generate the {oj ..... syntax for outer joins?
In Crystal Reports 8, you could do a registry change to keep CR from using oj, but that doesn't seem to work on CR XI (or I don't know where to make the registry change)

A: oj syntax for outer join

Outer Join Escape Sequence builds the syntax for ODBC drivers using the outer join syntax in its SQL syntax.
Use Regedit on the problem client machine add following keys:
STEP 1........For Crystal Reports 9: HKEY_CURRENT_USER\Software\Crystal Decisions\9.0\Crystal Reports\Database\QueryBuilder\OuterJoinEscSeq
<<<OR>>>
...................For Crystal Reports 10:HKEY_CURRENT_USER\Software\Crystal Decisions\10.0\Crystal Reports\Database\QueryBuilder\OuterJoinEscSeq
STEP 2........"MSOuterJoinEscSeq"= "insert your ODBC driver name here": List of the drivers that support Microsoft ODBC {oj ..} join escape sequence.
"NoOuterJoinEscSeq"= "insert your ODBC driver name here": List of the drivers that do not support any join escape sequence.
For example...
MSOuterJoinEscSeq = "UVODBC"

Where can I find the syntax guide for Oracle 11g?

Sooooo frustrating...I've perused the Oracle site, have done Google searches, and cannot seem to find the syntax guide for Oracle 11g. Can someone provide me the URL or clue me in as to where it might be buried? Am I just being stupid???
Thanks in advance for your review and am hopeful for a reply.
PSULionRP

the syntax guide for Oracle 11gWhat does that mean exactly ? Maybe the Reference guide ?

JOIN syntax for Oracle 8i

Similar Messages

Maybe you are looking for