...
Running out of available memory is the most common issue caused by large DML scripts in Datical for any supported database platform. Therefor Therefore it is recommended that you allocate at least 8 GB (8192 MB) of memory to the Datical run time environment. See Increase the amount of RAM used by Datical DB for more details on managing available memory settings.
...
To preserve the order of execution for the statements in the original file, add a numeric indicator to each filename. For example, a large file named myLargeDMLFile.sql would become myLargeDMLFile_1.sql, myLargeDMLFile_2.sql, myLargeDMLFile_3.sql, myLargeDMLFile_4.sql To ensure that the file set is appropriately ordered in the resulting change log:
...
If you are using SQL Parser for Oracle in your project, do not put large DML scripts in folders that will use the parser, such as:
the folders called “ddl_direct”, “sql_direct”, or “sql” in fixed folder name configurations
or folders with other flexible folder names that have packageMethod=”ddl_direct”, packageMethod=”direct”, or packageMethod=”sqlfile” set in the metadata.properties
or in folders that have disableSqlParser=”false” set in the metadata.properties
...
Set disableSqlParser=true in the metadata.properties file for any folders that you do not want SQL Parser to process.
|
Disabling SQL Parser at the Change Set level
...
Add disableSqlParser=true in the appdba:sqlplus section of the change set for a specific change set you do not want SQL Parser to process.
|