SnowConvert AI - Object References Report¶

What is an “Object Reference”?¶

An object reference is the term used to refer to DDL definitions in the source code, that are being referenced by code units. The table below shows which elements could be referenced in each supported language.

Where can I find it?¶

The object references report can be found in a folder named “reports”, in the output folder of your conversion. The name of the file itself starts with “ObjectReferences” so it can easily be located.

The format of the file is .CSV.

What information does it contain?¶

The object references report contains the following information about all the references found while converting:

Oracle Database Links as object references¶

To get the information such as database name, schema name, or object name of database link references, we need to know how the database link was defined. Database links contain the most relevant information in the connection string used in its definition. E.g.

Database Link with database name¶

 CREATE DATABASE LINK remote_hr_db
CONNECT TO hr_user
IDENTIFIED BY hr_password
USING 'RemoteDB';

SELECT * FROM hr.employees@remote_hr_db;

Using the example above, the object reference information should look like this:

Database Link with database and schema names¶

 CREATE DATABASE LINK remote_hr_db1
CONNECT TO hr_user
IDENTIFIED BY hr_password
USING 'RemoteDB.MySchema';

SELECT * FROM employees@remote_hr_db1;

Using the example above, the object reference information should look like this:

Database Link with a connection string¶

 CREATE DATABASE LINK remote_hr_db2
CONNECT TO hr_user
IDENTIFIED BY hr_password
USING '(DESCRIPTION=(
          ADDRESS=
          (PROTOCOL=TCP)
          (HOST=10.48.195.17)
          (PORT=1521))
      (CONNECT_DATA=(SID=MyDB)))';

SELECT * FROM employees@remote_hr_db2;

Using the example above, the object reference information should look like this:

Relation Type¶

The relation type represents how a caller code unit is related to an object reference. SnowConvert AI is able to identify the following kinds of relations:

• FOREIGN KEY
• INSERT
• DELETE
• UPDATE
• CALL
• EXECUTE
• SYNONYM
• ALTER
• DROP
• MERGE
• TRUNCATE
• LOCK
• INDEX
• TABLE COLUMN
• GRANT
• REVOKE
• SELECT
  • COLUMN
  • FROM
  • WHERE
  • HAVING
  • GROUP BY
  • JOIN
  • ORDER BY

Examples¶

1. A stored procedure referencing a table through an UPDATE statement:

 CREATE TABLE TABLE2
(
  COL1 VARCHAR(50) NOT NULL,
  COL2 INT NOT NULL
);

CREATE OR REPLACE PROCEDURE Procedure01 (param1 NUMBER)
IS
BEGIN
    UPDATE TABLE2
    SET COL1 = 'Anderson'
    WHERE COL2 = param1;
END;

The report will show something like the following table:

2. A table referencing another table through a FOREIGN KEY:

 CREATE TABLE TABLE1
(
  COL1 INT
);

CREATE TABLE TABLE2
(
  COL1 INT,
  CONSTRAINT FK_COL1 FOREIGN KEY (COL1)
    REFERENCES TABLE1(COL1)
);

The report will show something like the following table:

3. A table referenced by a view in the FROM clause of the SELECT statement:

 CREATE TABLE TABLE1
(
  COL1 INT
);

CREATE VIEW VIEW1
AS
SELECT * FROM TABLE1;

The report will show something like the following table:

4. A user-defined function (UDF) referenced by a view as a result set column.

 CREATE FUNCTION FUNCTION1(PARAM1 INT)
RETURN NUMBER
IS
BEGIN
  RETURN(PARAM1 + 1);
END;

CREATE VIEW VIEW1
AS
SELECT FUNCTION1(*) FROM TABLE1;

The report will show something like the following table: