2 Sybase Gateway Features and Restrictions

2.2.2.1 OCI Program Fetching from Result Sets in Sequential Mode

The following example shows OCI program fetching from result sets in sequential mode:

OCIEnv *ENVH;OCISvcCtx *SVCH;OCIStmt *STMH;OCIError *ERRH;OCIBind *BNDH[3];OraText arg1[20];
OraText arg2[255];OCIResult *rset;OCIStmt *rstmt;ub2 rcode[3];ub2 rlens[3];sb2 inds[3];OraText *stmt = (OraText *) "begin refcurproc@SYBS(:1,:2,:3); end;";OraText *n_rs_stm = (OraText *)  "begin :ret := DBMS_HS_RESULT_SET.GET_NEXT_RESULT_SET@SYBS; end;";/* Prepare procedure call statement *//* Handle Initialization code skipped */OCIStmtPrepare(STMH, ERRH, stmt, strlen(stmt), OCI_NTV_SYNTAX, OCI_DEFAULT);/* Bind procedure arguments */inds[0] = 0;strcpy((char *) arg1, "Hello World");rlens[0] = strlen(arg1);OCIBindByPos(STMH, &BNDH[0], ERRH, 1, (dvoid *) arg1, 20, SQLT_CHR,             (dvoid *) &(inds[0]), &(rlens[0]), &(rcode[0]), 0, (ub4 *) 0,              OCI_DEFAULT);
inds[1] = -1;OCIBindByPos(STMH, &BNDH[1], ERRH, 1, (dvoid *) arg2, 20, SQLT_CHR,             (dvoid *) &(inds[1]), &(rlens[1]), &(rcode[1]), 0, (ub4 *) 0,              OCI_DEFAULT);inds[2] = 0;rlens[2] = 0;OCIDescriptorAlloc(ENVH, (dvoid **) &rset, OCI_DTYPE_RSET, 0, (dvoid **) 0);OCIBindByPos(STMH, &BNDH[2], ERRH, 2, (dvoid *) rset, 0, SQLT_RSET,             (dvoid *) &(inds[2]), &(rlens[2]), &(rcode[2]),             0, (ub4 *) 0, OCI_DEFAULT);/* Execute procedure */OCIStmtExecute(SVCH, STMH, ERRH, 1, 0, (CONST OCISnapshot *) 0,               (OCISnapshot *) 0, OCI_DEFAULT);/* Convert result set to statement handle */OCIResultSetToStmt(rset, ERRH);rstmt = (OCIStmt *) rset;/* After this the user can fetch from rstmt *//* Issue get_next_result_set call to get handle to next_result set *//* Prepare Get next result set procedure call */OCIStmtPrepare(STMH, ERRH, n_rs_stm, strlen(n_rs_stm), OCI_NTV_SYNTAX,               OCI_DEFAULT);/* Bind return value */OCIBindByPos(STMH, &BNDH[1], ERRH, 1, (dvoid *) rset, 0, SQLT_RSET,             (dvoid *) &(inds[1]), &(rlens[1]), &(rcode[1]),             0, (ub4 *) 0, OCI_DEFAULT);/* Execute statement to get next result set*/OCIStmtExecute(SVCH, STMH, ERRH, 1, 0, (CONST OCISnapshot *) 0,               (OCISnapshot *) 0, OCI_DEFAULT);/* Convert next result set to statement handle */OCIResultSetToStmt(rset, ERRH);rstmt = (OCIStmt *) rset;/* Now rstmt will point to the second result set returned by theremote stored procedure *//* Repeat execution of get_next_result_set to get the output arguments */

2.2.2.2 PL/SQL Program Fetching from Result Sets in Sequential Mode

Assume that the table loc_emp is a local table exactly like the Sybase emp table. The same assumption applies for loc_dept. outargs is a table with columns corresponding to the out arguments of the Sybase stored procedure.

create or replace package rcpackage is  type RCTYPE is ref cursor;end rcpackage;/

declare  rc1 rcpackage.rctype;  rec1 loc_emp%rowtype;  rc2 rcpackage.rctype;  rec2 loc_dept%rowtype;  rc3 rcpackage.rctype;  rec3 outargs%rowtype;
  out_arg varchar2(255);begin  -- Execute procedure
  out_arg := null;  refcurproc@SYBS('Hello World', out_arg, rc1);  -- Fetch 20 rows from the remote emp table and insert them into loc_emp  for i in 1 .. 20 loop    fetch rc1 into rec1;    insert into loc_emp (rec1.empno, rec1.ename, rec1.job,    rec1.mgr, rec1.hiredate, rec1.sal, rec1.comm, rec1.deptno);  end loop;  -- Close ref cursor  close rc1;  -- Get the next result set returned by the stored procedure  rc2 := dbms_hs_result_set.get_next_result_set@SYBS;  -- Fetch 5 rows from the remote dept table and insert them into loc_dept  for i in 1 .. 5 loop    fetch rc2 into rec2;    insert into loc_dept values (rec2.deptno, rec2.dname, rec2.loc);  end loop;  --Close ref cursor  close rc2;  -- Get the output arguments from the remote stored procedure  -- Since we are in sequential mode, they will be returned in the  -- form of a result set  rc3 := dbms_hs_result_set.get_next_result_set@SYBS;  -- Fetch them and insert them into the outarguments table  fetch rc3 into rec3;  insert into outargs (rec3.outarg, rec3.retval);  -- Close ref cursor  close rc3;end;
/

2.3.3.1 Rules for Naming Objects

Oracle and Sybase use different database object naming rules. For example, the maximum number of characters allowed for each object name can be different. Also, the use of single and double quotation marks, case sensitivity, and the use of alphanumeric characters can all be different.

2.3.3.2 Case Sensitivity

The Oracle database defaults to uppercase unless you surround identifiers with double quote characters. For example, to refer to the Sybase table called emp, enter the name with double quote characters, as follows:

SQL> SELECT * FROM "emp"@SYBS;

However, to refer to the Sybase table called emp owned by SCOTT from an Oracle application, enter the following:

SQL> SELECT * FROM "Scott"."emp"@SYBS;

If the Sybase table called emp is owned by SCOTT, a table owner name in uppercase letters, you can enter the owner name without double quote characters, as follows:

SQL> SELECT * FROM SCOTT."emp"@SYBS;

Or

SQL> SELECT * FROM scott."emp"@SYBS;

Oracle recommends that you surround all Sybase object names with double quote characters and use the exact letter case for the object names as they appear in the Sybase data dictionary. This convention is not required when referring to the supported Oracle data dictionary tables or views listed in Appendix C, "Data Dictionary".

If existing applications cannot be changed according to these conventions, create views in Oracle to associate Sybase names to the correct letter case. For example, to refer to the Sybase table emp from an existing Oracle application by using only uppercase names, define the following view:

SQL> CREATE VIEW EMP (EMPNO, ENAME, SAL, HIREDATE)      AS SELECT "empno", "ename", "sal", "hiredate"      FROM "emp"@SYBS;

With this view, the application can issue statements such as the following:

SQL> SELECT EMPNO, ENAME FROM EMP;

Using views is a workaround solution that duplicates data dictionary information originating in the Sybase data dictionary. You must be prepared to update the Oracle view definitions whenever the data definitions for the corresponding tables are changed in the Sybase database.

2.3.4.1 Binary Literal Notation

Oracle SQL uses hexadecimal digits surrounded by single quotes to express literal values being compared or inserted into columns defined as data type RAW.

This notation is not converted to syntax compatible with the Sybase VARBINARY and BINARY data types (a 0x followed by hexadecimal digits, surrounded by single quotes).

For example, the following statement is not supported:

SQL> INSERT INTO BINARY_TAB@SYBS VALUES ('0xff')

Where BINARY_TAB contains a column of data type VARBINARY or BINARY. Use bind variables when inserting into or updating VARBINARY and BINARY data types.

2.3.4.2 Data Type Conversion

Sybase does not support implicit date conversions. Such conversions must be explicit.

For example, the gateway issues an error for the following SELECT statement:

SELECT DATE_COL FROM TEST@SYBS WHERE DATE_COL = "1-JAN-2001";

To avoid problems with implicit conversions, add explicit conversions, as in the following:

SELECT DATE_COL FROM TEST@SYBS WHERE DATE_COL = TO_DATE("1-JAN-2001")

2.3.5.1 Row Selection

Sybase evaluates a query condition for all selected rows before returning any of the rows. If there is an error in the evaluation process for one or more rows, no rows are returned even though the remaining rows satisfy the condition.

Oracle evaluates the query condition row-by-row and returns a row when the evaluation is successful. Rows are returned until a row fails the evaluation.

2.3.5.2 Empty Strings

Oracle processes an empty string in a SQL statement as a null value. Sybase processes an empty string as an empty string.

When comparing an empty string, the gateway passes literal empty strings to the Sybase database without any conversion. If you intended an empty string to represent a null value, Sybase does not process the statement that way; it uses the empty string.

You can avoid this problem by using NULL or IS NULL in the SQL statement instead of the empty string syntax, as in the following example:

SELECT * from "emp"@SYBS where "ename" IS NULL;

Selecting an empty string

For VARCHAR columns, the gateway returns an empty string to the Oracle database as NULL value.

For CHAR columns, the gateway returns the full size of the column with each character as empty space (' ').

2.3.5.3 Empty Bind Variables

For VARCHAR bind variables, the gateway passes empty bind variables to the Sybase database as a NULL value.

2.4.7.1 WHERE CURRENT OF Clause

UPDATE and DELETE statements with the WHERE CURRENT OF clause are not supported by the gateway because they rely on the Oracle ROWID implementation. To update or delete a specific row through the gateway, a condition style WHERE clause must be used.

2.4.7.2 CONNECT BY Clause

The gateway does not support the CONNECT BY clause in a SELECT statement.

2.4.7.3 ROWID

The Oracle ROWID implementation is not supported.

2.4.7.4 Subqueries in INSERT Statement

Subqueries of INSERT statements cannot use multiple aliases for the same table. For example, the following statement is not supported:

SQL> INSERT INTO "emp_target"@SYBS
         SELECT a."empno" FROM "emp_source"@SYBS a,
            "emp_source"@SYBS b WHERE b."empno"=9999

2.4.7.5 EXPLAIN PLAN Statement

The EXPLAIN PLAN statement is not supported.

2.4.7.6 Callback Support

SQL statements that require the gateway to callback to Oracle database would not be supported.

The following categories of SQL statements will result in a callback:

• Any DML with a sub-select, which refers to a table in Oracle database. For example:

  INSERT INTO emp@non_oracle SELECT * FROM oracle_emp;
  

• Any DELETE, INSERT, UPDATE or "SELECT... FOR UPDATE..." SQL statement containing SQL functions or statements that need to be executed at the originating Oracle database.

  These SQL functions include USER, USERENV, and SYSDATE, and the SQL statements are in selects of data from the originating Oracle database. For example:

  DELETE FROM emp@non_oracle WHERE hiredate > SYSDATE;
  

  SELECT ename FROM tkhoemp@non_oracle
  WHERE hiredate IN (SELECT hiredate FROM tkhoemp)
  FOR UPDATE OF empno;
  

• Any SQL statement that involves a table in Oracle database, and a LONG or LOB column in a remote table. For example:

  SELECT a.long1, b.empno FROM scott.table@non_oracle a, emp b
  WHERE a.id=b.empno; 
  

  SELECT a.long1, b.dummy FROM table_non@non_oracle a, dual b;
  

where a.long1 is a LONG column.