Copy/Pasting here - You should be able to access it.
EIC Migration - Considerations and Guidelines for Custom queries
Overview:
Custom Query Job v2 is the new and improved framework to create and manage Custom queries in EIC. v2 includes many updates and features, such as faster execution time, less susceptible to deadlocks etc.
What's New with Custom Query Job v2:
- Faster execution time, less susceptible to deadlock.
- Option to have Rollback turned OFF on execution failure
- Preview mode
- UI validations to ensure correctness of the query
With the introduction of Custom Query Job v2 we have also introduced certain restrictions in the Custom Query v1 to encourage the usage of v2 and avoid the known issues with v1. So when migrating the application from previous versions to EIC, keep in mind the following considerations and limitations for existing custom queries as described in below section. Remediation may need to be performed on existing queries as applicable to make them compatible with EIC.
EIC - Custom Query v1 restrictions
-
Managing Existing Queries
- Existing queries will be migrated as part of the migration and will continue to work as is. But some Custom queries may not function post migration because of restrictions imposed such as DDL statements, Calling functions/procedures etc.
- Only schedule can be modified for existing queries post migration.
- No other modifications will be allowed (Existing query logic/syntax cannot be changed)
- Existing triggers containing operations like ALTER, DELETE, TRUNCATE, etc. will not be allowed (only INSERT and UPDATE allowed)
-
New Job Triggers
Creation of new job triggers will not be supported for custom query v1 in EIC. Any new trigger need to use Custom Query v2.
Usage of stored procedures are not allowed in EIC. Hence calling stored procedures within the custom query is also not supported anymore. Any existing query performing this operation need to be remediated.
Usage of DB functions are not allowed in EIC. Hence calling DB function within the custom query is also not supported anymore. Any existing query performing this operation need to be remediated.
EIC - Guidelines for Custom query v2
The following statements are not supported:
- DDL statements: Create, alter, and drop are not supported
- Changes to USERS table are restricted, INLINE PREPROCESSOR to be used instead. Select is allowed.
- Changes (Insert / delete/ Update) are also not supported on following tables:
- p_history
- userlogin_access
- qrtz tables
- Updates not allowed for tables having composite primary keys eg. user_accounts, role_owners, etc.
- Multiple Queries per trigger (Only Single query per trigger are allowed)
- Calling DB functions and Stored procedures from custom query not allowed
The following statements are supported:
- Select / Insert / delete/ Update are supported on Tables (Except for the tables mentioned under Unsupported Statements)
- Select is supported on Users Table
