SQL File Format

Program blocks

Program blocks should be terminated by use of /. See examples below. For example, Package Specification, Package Body, Trigger etc. FlexDeploy will add / at the end of the file if last statement is program block.

BEGIN
   EXECUTE IMMEDIATE 'DROP TABLE XXHR.XXHR_WF1';
EXCEPTION
   WHEN OTHERS THEN
      NULL;
END;
/

BEGIN
   EXECUTE IMMEDIATE 'DROP SYNONYM XXHR_WF1';
EXCEPTION
   WHEN OTHERS THEN
      NULL;
END;
/

CREATE OR REPLACE PACKAGE xxhr_bipub_rep_pkg AS

   PROCEDURE generate_xml(p_errbuf  OUT VARCHAR2
                         ,p_retcode OUT NUMBER);

END xxhr_bipub_rep_pkg;
/

Non program blocks

Statements that are not program blocks should be terminated using ;. For example create or replace view, insert etc.

CREATE SYNONYM apps.XXHR_WF1 FOR xxhr.XXHR_WF1;

CREATE OR REPLACE FORCE VIEW "APPS"."DUMMY_V1" ("COUNT") AS
  (SELECT 1 from dual);

Comments

Comments in SQL file. See below for supported formats.

Good comment examples

--single line comment
/* 
 * Name : XXHR_WF1                                                        *
 */

Following comment is not supported as it will cause SP2-0103: Nothing in SQL buffer to run.

Bad Comments

/*Added comment by chandresh to test flexdeploy*/

Recompiling invalids

Consider adding compileInvalidSqls operation in Deploy workflow if SQL files are being deployed. This operation can take longer if there are many invalid objects in Schema.

Custom objects in non apps schema

Custom objects in non APPS schema with grants to APPS user. It is recommended by Oracle to create custom objects in custom schema. You need to provide Grants to APPS user to these custom objects. You can achieve this in two different ways in FlexDeploy.

Give necessary rights to APPS user, so it can select on any other schema objects. For example, SELECT ANY TABLE privilege can be given to APPS and similarly other ANY type Grants can be given to APPS user.
Use custom schema user in FlexDeploy to create objects and grant to APPS.
1. Create custom user and password properties on Deploy workflow to be at Target Scope. For example,
2. Defined values for these user and password in various Target pages in Topology.
3. Use custom properties on Project Files tab for specific Files.
If you want the file to populate with the correct schema user and password property attached, create the filename like "SCHEMASCHEMANAME_FILENAME.sql"
1. e.g. SCHEMAPOS_registertrans.tbl
2. This will automatically try to use the properties FDEBS_DB_SCHEMAPOS_USER and FDEBS_DB_SCHEMAPOS_PASSWORD, so if using the filenames to link the schema users, follow this naming standard of the property codes.

SQL File Considerations