ORDER SIBLINGS not working in Forms

Question

This code run fine in Toad BUT giving me error in forms.
SELECT
       LEVEL                           LOC_NAME,
       LOCATION_NAME                   LOC_ID,
       LOCATION_ID                     HLOC_ID,
       HEAD_LOC_ID MUDRA
  FROM AS_LOCATION_HDR
CONNECT BY PRIOR LOCATION_ID = HEAD_LOC_ID
START WITH HEAD_LOC_ID is null
ORDER SIBLINGS BY LOC_IDThe error is:
"Encountered sysbol "SIBLINGS" when expecting one of the following:
by
The symbol "by inserted before the "SIBLINGS" to continue.Is the SIBLINGS keyword not acepted in forms? What would be the alternative?
I am using oracle forms 10G (10.1.2.0.2)

Answer 1

hi
Oracle's START WITH and CONNECT BY clauses in the
SELECT statement automatically traverse a hierarchy.
Without this feature, a complex self-join would be required to identify
which rows are logically related to others.
The START WITH clause identifies the row or rows to be considered
the starting points, or "roots," of the hierarchy.
The CONNECT BY PRIOR clause
then indicates how to identify which rows are related to each other.
example, the query in Listing A produces a "Reports To" listing from the EMPLOYEES table in the HR sample schema provided by Oracle.
The LEVEL pseudocolumn indicates how deeply the report is currently nested; here,
I use it to LPAD the employee names to indent them.
The START WITH condition states that only employees 101 and 102 are to be considered as starting points.
The CONNECT BY PRIOR clause then links the employee_id
column in one row to the manager_id column in the next, to indicate who reports to whom.
If you run this query in the HR schema,
you'll notice that the last names are not sorted within the listing for a specific manager;
they are listed in the order Oracle encountered them in processing the hierarchy.
If you want the subordinates in alphabetical order,
you might try to ORDER BY the original last_name column.
However, this would break up the hierarchy, and turn it back into a flat list of names.
You might also try to ORDER BY the pseudocolumn LEVEL first,
which tells how deep a specific row is in the hierarchy. This, too,
breaks up the hierarchy—all the managers will be listed first, followed by people who report to any of them.
In Oracle 10g (both releases),
it's now easy to do this: You can use the new SIBLINGS keyword to create the correct ordering. The syntax is:
ORDER SIBLINGS BY <expression>So adding the clause:
ORDER SIBLINGS BY last_nameto the end of the query will preserve
the hierarchy and also alphabetize the last names within each level.
Note that the original last_name was used not the alias "Reports To."
The extra space padding in "Reports To" would affect the sort, so the original must be used.
Listing B shows the output, both before and after adding ORDER SIBLINGS BY.
The ORDER SIBLINGS BY clause is valid only in a hierarchical query. The optional SIBLINGS keyword specifies an order that first sorts the parent rows, and then sorts the child rows of each parent for every level within the hierarchy.
Rows that have duplicate lists of values in the columns specified after the SIBLINGS BY keywords are arbitrarily ordered among the rows with the same list of values and the same parent. If a hierarchical query includes the ORDER BY clause without the SIBLINGS keyword, rows are ordered according to the sort specifications that follow the ORDER BY keywords. Neither the ORDER BY clause nor the ORDER SIBLINGS BY option to the ORDER BY clause is required in hierarchical queries.
The hierarchical query in the following example returns the subset of rows in the hierarchical data set whose root is Goyal, as listed in the topic Hierarchical Clause. This query includes the ORDER SIBLINGS BY clause to sort by name the employees who report to the same manager:
SELECT empid, name, mgrid, LEVEL
   FROM employee
      START WITH name = 'Goyal'
      CONNECT BY PRIOR empid = mgrid
   ORDER SIBLINGS BY name;The rows returned by this query are sorted in the following order:
         empid name             mgrid       level
         16 Goyal               17           1
         12 Henry               16           2
          7 O'Neil              12           3
          9 Shoeman             12           3
          8 Smith               12           3
         14 Scott               16           2
         11 Zander              16           2
          6 Barnes              11           3
          5 McKeough            11           3
9 row(s) retrieved.Here the START WITH clause returned the Goyal row at the root of this hierarchy. Two subsequent CONNECT BY steps (marked as 2 and 3 in the level pseudocolumn) returned three sets of sibling rows:
Henry, Scott, and Zander are siblings whose parent is Goyal;
O'Neil, Shoeman, and Smith are siblings whose parent is Henry;
Barnes and McKeough are siblings whose parent is Zander.
The next CONNECT BY step returned no rows, because the rows for which level = 3 are leaf nodes within this hierarchy. At this point in the execution of the query, the ORDER SIBLINGS BY clause was applied to the result set, sorting the rows in the order shown above.
Because the sort key, name, is a VARCHAR column, the returned rows within each set of siblings are in the ASCII order of their employee.name values. Only the sets of siblings that are leaf nodes in the hierarchy of returned rows appear consecutively in the sorted result set, because the managers are immediately followed by the employees who report to them, rather than by their siblings. An exception in this example is Scott, whose child nodes form an empty set.
The SIBLINGS keyword in the ORDER BY clause is an extension to the ISO standard syntax for the SQL language. The SELECT statement fails with an error if you include the SIBLINGS keyword in the ORDER BY clause of a query or subquery that does not include a valid CONNECT BY clause. hope this helps u.
sarah