Ottmar’s Notes - Script

Generate APEX plug-ins on the command line

2021-10-13T00:00:00+00:00

Introduction</h2>
Everyone who develops plug-ins for APEX knows the problem: Once a plug-in is finished, future maintenance is usually just a matter of uploading updated JavaScript files to the plug-in and finally downloading the plug-in to make it available to others. This can be a very time consuming process when troubleshooting or implementing a new feature.</p>
So for my latest open source project, I thought about how to shorten the whole process. I already had a file watcher and a build script running anyway, which, when source files are changed, merges the entire project into a single SQL install script. The plug-in was just about updating a JavaScript file (normal and minified). The PL/SQL code for the plug-in is in a package and only referenced - this is also a good approach for performance reasons (Blog post by Daniel Hochleitner on the topic</a>).</p>

Creating a template from the existing plug-in</h2>

So I downloaded the finished plug-in once and stored it as a template in the project directory. Then I looked at how the files are stored in the SQL script of the plug-in:</p>

begin</span></span>
    wwv_flow_api.g_varchar2_table :</span>=</span> wwv_flow_api.empty_varchar2_table;</span></span>
    wwv_flow_api.g_varchar2_table(</span>1</span>) :</span>=</span> '766172206f69633d7b6f633a7b7d2c6f613a7b7d2c6c6e3a7b7d7d3b6f69632e6c6e2e6572726f723d312c6f69632e6c6e2e7761726e696e673d322c6f69632e6c6e2e696e666f3d332c6f69632e6c6e2e64656275673d342c6f69632e6c6e2e74726163'</span>;</span></span>
    wwv_flow_api.g_varchar2_table(</span>2</span>) :</span>=</span> '653d352c6f69632e746f537472696e673d66756e6374696f6e2872297b666f7228766172206f3d22222c653d303b653c722e6c656e6774683b652b2b296f2b3d30213d3d653f2220223a22222c226f626a656374223d3d747970656f6620725b655d3f6f'</span>;</span></span>
    wwv_flow_api.g_varchar2_table(</span>3</span>) :</span>=</span> '2b3d225c6e222b4a534f4e2e737472696e6769667928725b655d2c6e756c6c2c32293a6f2b3d725b655d3b72657475726e206f7d2c6f69632e696e69743d66756e6374696f6e28297b6f69632e6d6573736167653d66756e6374696f6e28722c6f2c652c'</span>;</span></span>
    /* snip */</span></span>
    wwv_flow_api.g_varchar2_table(</span>14</span>) :</span>=</span> '2e6c6e2e6572726f722c722c6e2c692e737461636b292c21317d7d3b'</span>;</span></span>
end</span>;</span></span>
/</span></span>
</span>
begin</span></span>
    wwv_flow_api.create_plugin_file (</span></span>
        p_id           </span>=></span> wwv_flow_api.id(</span>37195131994077352</span>),</span></span>
        p_plugin_id    </span>=></span> wwv_flow_api.id(</span>36295154520053378</span>),</span></span>
        p_file_name    </span>=></span> 'console.min.js'</span>,</span></span>
        p_mime_type    </span>=></span> 'application/javascript'</span>,</span></span>
        p_file_charset </span>=></span> 'utf-8'</span>,</span></span>
        p_file_content </span>=></span> wwv_flow_api.varchar2_to_blob(wwv_flow_api.g_varchar2_table) );</span></span>
end</span>;</span></span>
/</span></span></code></pre>
    Example of a file in the SQL installation script of a plug-in</figcaption>
</figure>
It looks like we have to encode the files somehow - but how? If you take a closer look at the characters, you will notice at some point that only the digits 0 to 9 and the letters a to f are used. So it seems to be a hexadecimal encoding - with 200 characters in each block.</p>
Ok, then in the template we replace the first anonymous PL/SQL block with a placeholder:</p>

    #CONSOLE_JS_FILE_MIN#</span></span>
</span>
begin</span></span>
    wwv_flow_api.create_plugin_file (</span></span>
        p_id           </span>=></span> wwv_flow_api.id(</span>37195131994077352</span>),</span></span>
        p_plugin_id    </span>=></span> wwv_flow_api.id(</span>36295154520053378</span>),</span></span>
        p_file_name    </span>=></span> 'console.min.js'</span>,</span></span>
        p_mime_type    </span>=></span> 'application/javascript'</span>,</span></span>
        p_file_charset </span>=></span> 'utf-8'</span>,</span></span>
        p_file_content </span>=></span> wwv_flow_api.varchar2_to_blob(wwv_flow_api.g_varchar2_table) );</span></span>
end</span>;</span></span>
/</span></span></code></pre>
    Example of a file in the plug-in template with placeholder</figcaption>
</figure>
Now we need some code to replace the placeholder with the converted source file.</p>
JavaScript helper functions for conversion</h2>
Since I implemented the file watcher and other scripts with Node.js/npm, it was obvious to solve this in JavaScript as well. First the needed modules and a md5 hash function:</p>
const</span> fs</span> =</span> require</span>(</span>'fs'</span>)</span>;</span></span>
const</span> UglifyJS</span> =</span> require</span>(</span>'uglify-js'</span>)</span>;</span></span>
const</span> crypto</span> =</span> require</span>(</span>'crypto'</span>)</span>;</span></span>
const</span> toMd5Hash</span> =</span> function</span> (</span>string</span>) {</span> return</span> crypto</span>.</span>createHash</span>(</span>'md5'</span>)</span>.</span>update</span>(string)</span>.</span>digest</span>(</span>'hex'</span>)</span> };</span></span>
let</span> consoleJsCode</span>,</span> minified</span>,</span> version</span>,</span> md5Hash</span>,</span> conf</span>;</span></span></code></pre>
Then we need a helper function that breaks a string into blocks of 200 characters and returns it as an array:</p>
const</span> toChunks</span> =</span> function</span> (</span>text</span>,</span> size</span>) {</span></span>
    const</span> numChunks</span> =</span> Math</span>.</span>ceil</span>(text</span>.</span>length</span> /</span> size)</span>;</span></span>
    const</span> chunks</span> =</span> new</span> Array</span>(numChunks)</span>;</span></span>
    for</span> (</span>let</span> i</span> =</span> 0</span>,</span> start</span> =</span> 0</span>;</span> i</span> <</span> numChunks</span>;</span> ++</span>i</span>,</span> start</span> +=</span> size)</span> {</span></span>
        chunks[i]</span> =</span> text</span>.</span>substr</span>(start</span>,</span> size)</span>;</span></span>
    }</span></span>
    return</span> chunks</span>;</span></span>
};</span></span></code></pre>
Finally, our actual function, which hexadecimally encodes a string (read file) and puts it into the required SQL script form:</p>
const</span> toApexPluginFile</span> =</span> function</span> (</span>text</span>) {</span></span>
    const</span> hexString</span> =</span> new</span> Buffer</span>.</span>from</span>(text)</span>.</span>toString</span>(</span>'hex'</span>)</span>;</span></span>
    const</span> chunks</span> =</span> toChunks</span>(hexString</span>,</span> 200</span>)</span>;</span></span>
    let</span> apexLoadFile</span> =</span> 'begin</span>\n</span>'</span> +</span></span>
        '  wwv_flow_api.g_varchar2_table := wwv_flow_api.empty_varchar2_table;</span>\n</span>'</span>;</span></span>
    for</span> (</span>let</span> i</span> =</span> 0</span>;</span> i</span> <</span> chunks</span>.</span>length</span>;</span> ++</span>i)</span> {</span></span>
        apexLoadFile</span> +=</span> `  wwv_flow_api.g_varchar2_table(</span>${</span>(</span>i</span> +</span> 1</span>)</span>}</span>) := '</span>${</span>chunks</span>[</span>i</span>]</span>}</span>';</span>\n</span>`</span>;</span></span>
    }</span></span>
    apexLoadFile</span> +=</span> 'end;</span>\n</span>/'</span>;</span></span>
    return</span> apexLoadFile</span>;</span></span>
};</span></span></code></pre>Build script to build the plug-in when changes are made in the source code</h2>
Everything is assembled by the build script - here is the relevant snippet:</p>

    console</span>.</span>log</span>(</span>'- build file install/apex_plugin.sql'</span>)</span>;</span></span>
consoleJsCode</span> =</span> fs</span>.</span>readFileSync</span>(</span>'sources/apex_plugin_console.js'</span>,</span> 'utf8'</span>)</span>;</span></span>
version</span> =</span> fs</span>.</span>readFileSync</span>(</span>'sources/CONSOLE.pks'</span>,</span> 'utf8'</span>)</span>.</span>match</span>(</span>/</span>c_version</span>\s</span>+</span>constant</span>.</span>*?</span>'(</span>.</span>*?</span>)'</span>/</span>)[</span>1</span>]</span>;</span></span>
md5Hash</span> =</span> toMd5Hash</span>(consoleJsCode)</span>;</span></span>
// reading the last saved version and md5Hash values as a reference for the comparison</span></span>
conf</span> =</span> JSON</span>.</span>parse</span>(fs</span>.</span>readFileSync</span>(</span>'apexplugin.json'</span>,</span> 'utf8'</span>))</span>;</span></span>
if</span> (conf</span>.</span>version</span> !==</span> version</span> ||</span> conf</span>.</span>jsFile</span>.</span>md5Hash</span> !==</span> md5Hash)</span> {</span></span>
    minified</span> =</span> UglifyJS</span>.</span>minify</span>(</span>{</span> "console.js"</span>:</span> consoleJsCode</span> }, {</span> sourceMap</span>:</span> true</span> }</span>)</span>;</span></span>
    if</span> (minified</span>.</span>error)</span> throw</span> minified</span>.</span>error</span>;</span></span>
    conf</span>.</span>version</span> =</span> version</span>;</span></span>
    conf</span>.</span>jsFile</span>.</span>md5Hash</span> =</span> md5Hash</span>;</span></span>
    conf</span>.</span>jsFile</span>.</span>version</span> +=</span> 1</span>;</span></span>
    fs</span>.</span>writeFileSync</span>(</span>'install/apex_plugin.sql'</span>,</span></span>
        '--DO NOT CHANGE THIS FILE - IT IS GENERATED WITH THE BUILD SCRIPT sources/build.js</span>\n\n</span>'</span> +</span></span>
        fs</span>.</span>readFileSync</span>(</span>'sources/apex_plugin_template.sql'</span>,</span> 'utf8'</span>)</span></span>
            .</span>replace</span>(</span>'#CONSOLE_VERSION#'</span>,</span> conf</span>.</span>version)</span></span>
            .</span>replace</span>(</span>'#FILE_VERSION#'</span>,</span> conf</span>.</span>jsFile</span>.</span>version)</span></span>
            .</span>replace</span>(</span>'#CONSOLE_JS_FILE#'</span>,</span> toApexPluginFile</span>(fs</span>.</span>readFileSync</span>(</span>'sources/apex_plugin_console.js'</span>,</span> 'utf8'</span>)))</span></span>
            .</span>replace</span>(</span>'#CONSOLE_JS_FILE_MIN#'</span>,</span> toApexPluginFile</span>(minified</span>.</span>code))</span></span>
            .</span>replace</span>(</span>'#CONSOLE_JS_FILE_MIN_MAP#'</span>,</span> toApexPluginFile</span>(minified</span>.</span>map))</span></span>
    )</span>;</span></span>
    fs</span>.</span>writeFileSync</span>(</span>'apexplugin.json'</span>,</span> JSON</span>.</span>stringify</span>(conf</span>,</span> null</span>,</span> 2</span>))</span>;</span></span>
}</span></span></code></pre>
    Example of a build script (excerpt, here the complete script</a>)</figcaption>
</figure>
It should be noted that we will also have to manage the file version itself - APEX will install it as we create it. For that purpose, we check by means of hash-function whether JavaScript source file has changed and only then we regenerate the plug-in (including minification). This way, we avoid unnecessarily regenerating the plug-in every time we change source code in the repository and thus incrementing the file version.In the build script snippet above, the current file version and hash value is stored in a JSON file (apexplugin.json</code>, last line of code) so that we can use this as a reference in the next build.</p>
Here is the relevant place in the plug-in template where the file version is entered by the build script (placeholder #FILE_VERSION#</code>, last parameter):</p>

    prompt </span>-</span> application</span>/</span>shared_components</span>/</span>plugins</span>/</span>dynamic_action</span>/</span>com_ogobrecht_console</span></span>
begin</span></span>
    wwv_flow_api.create_plugin (</span></span>
        p_id                        </span>=></span> wwv_flow_api.id(</span>36295154520053378</span>),</span></span>
        p_plugin_type               </span>=></span> 'DYNAMIC ACTION'</span>,</span></span>
        p_name                      </span>=></span> 'COM.OGOBRECHT.CONSOLE'</span>,</span></span>
        p_display_name              </span>=></span> 'Oracle Instrumentation Console'</span>,</span></span>
        p_supported_ui_types        </span>=></span> 'DESKTOP:JQM_SMARTPHONE'</span>,</span></span>
        p_api_version               </span>=></span> 2</span>,</span></span>
        p_render_function           </span>=></span> 'console.apex_plugin_render'</span>,</span></span>
        p_ajax_function             </span>=></span> 'console.apex_plugin_ajax'</span>,</span></span>
        p_substitute_attributes     </span>=></span> true,</span></span>
        p_subscribe_plugin_settings </span>=></span> true,</span></span>
        p_version_identifier        </span>=></span> '#CONSOLE_VERSION#'</span>,</span></span>
        p_about_url                 </span>=></span> 'https://github.com/ogobrecht/console'</span>,</span></span>
        p_files_version             </span>=></span> #FILE_VERSION# );</span></span>
end</span>;</span></span>
/</span></span></code></pre>
    Plug-in template with placeholders for file and plug-in version (snippet)</figcaption>
</figure>
In addition, the version number of the plug-in itself is also updated here (placeholder #CONSOLE_VERSION#</code>, third last parameter) - but this depends on the respective circumstances of the project. In my case I write the version number of the PL/SQL package CONSOLE also into the plug-in depending on it - so if the version number of the package changes, the plug-in will be rebuilt as well. But here everybody has to see what is needed in the project.</p>
When saving source code changes, the file watcher starts and triggers the build script. This then builds two installation SQL scripts together: That of the logging tool itself (not the focus of this article) and then that for the plug-in. Following this, both scripts are then installed in a dev environment. For this, of course, the default workspace stored in the plug-in and the default application number must be present in the dev environment.</p>
NPM scripts for orchestration</h2>
I now often manage build and install scripts with the node package manager npm. The reason for this is the good integration with Visual Studio Code, the operating system independence and the possibility to orchestrate the scripts a bit - ok, you have to install Node.js, but don’t you always? With one click you can either start the watch task, which does everything automatically with every save of a source file, or you can conveniently call the scripts individually. If someone else looks into the repository, it is also clearer with the npm scripts what works here and how.</p>

    
    npm script integration in VS Code</figcaption>
</figure>
It’s also clear that you don’t write usernames and passwords into the scripts here anymore - that’s already forbidden in principle when the code is checked into version control. On the screenshot you can (hopefully) see that here a wallet with the alias playground</code> is used. For those who only use the instant client and have problems setting up a wallet: How to use mkstore and orapki with Oracle Instant Client</a>.</p>
The scripts are managed in the file package.json</code> on the top level of the project directory. If you want to read more about npm scripts, you can start here:</p>

Introduction to NPM Scripts</a></li>
Why I Left Gulp and Grunt for npm Scripts</a></li>
Why npm Scripts?</a></li>
</ul>
A complete example</h2>
For those who want to see how everything can work together: I took the examples here in the article from my open source project Oracle Instrumentation Console</a>.</p>
Another way</h2>
My focus with this solution was to be able to supply a plug-in locally on the PC with new files. But there is another way: You can upload files or whole directories via script into an installed plug-in of an APEX application and then download the plug-in afterwards. For this purpose there is the Open Souce Project APEX Publish Static Files</a> by Vincent Morneau. This project is also integrated with APEX Nitro</a> which can speed up frontend development in APEX.</p>
Have fun generating plug-ins :-)</p>
Ottmar</p>



Create fast insert scripts
2021-01-31T00:00:00+00:00
A few weeks ago I released a new version of my PLEX project</a>. I improved the ability to export table data as insert scripts. Previously, PLEX was only able to export CSV data. The reason was that I originally developed PLEX to speed up the implementation of version control in Oracle DB projects, and the ability to export CSV data was intended to track changes in master data tables.</p>
It turned out that a colleague of mine wanted PLEX to export insert scripts for all data in all tables for the initial deployment of a new application. I implemented an initial version, but was not happy with the runtime of the insert scripts. I now hear some people arguing that there are better tools than insert scripts for importing larger amounts of data - but sometimes this is the only accepted way because only SQL*Plus is available to run the deployment scripts….</p>
Then I stumbled across an older post by Connor McDonald on creating fast insert scripts</a>. I have integrated his performance hacks into PLEX.</p>
You can use them as follows (see last parameter):</p>
declare</span></span>
  l_zip_file blob;</span></span>
begin</span></span>
  l_zip_file :</span>=</span> plex.to_zip(plex.backapp(</span></span>
    p_app_id                   </span>=></span> 100</span>,  </span>-- parameter only available when APEX is installed</span></span>
    p_include_ords_modules     </span>=></span> true, </span>-- parameter only available when ORDS is installed</span></span>
    p_include_object_ddl       </span>=></span> true,</span></span>
    p_include_data             </span>=></span> true,</span></span>
    p_data_as_of_minutes_ago   </span>=></span> 0</span>,     </span>-- Read consistent data with the resulting timestamp (SCN). Defaults to 0.</span></span>
    p_data_max_rows            </span>=></span> 10000</span>, </span>-- Maximum number of rows per table. Defaults to 1000.</span></span>
    p_data_table_name_like     </span>=></span> 'CAT\_%,USERS,ROLES,RIGHTS'</span>,</span></span>
    p_data_table_name_not_like </span>=></span> '%\_HIST,LOGGER%'</span>,</span></span>
    p_data_format              </span>=></span> 'insert:10'</span>));</span></span>
</span>
  -- Do something with the zip file.</span></span>
  -- Your code here...</span></span>
end</span>;</span></span>
/</span></span></code></pre>
The p_data_format</code> parameter is new and can contain a comma-separated list of formats - currently the CSV and INSERT formats are supported. An example: csv,insert</code> exports for each table a CSV file and a SQL file with insert statements. For insert you can also specify the number of rows per insert all</code> statement (default value is 20) - example: csv,insert:10</code> or insert:5</code>.</p>
As you can see from the p_data_table_name_not_like => '%\_HIST,LOGGER%'</code> parameter, PLEX also accepts lists with like filters. In our example %\_HIST,LOGGER%</code> is translated to:</p>
where</span> ...</span></span>
  and</span> (    table_name </span>not like</span> '%\_HIST'</span> escape </span>'\'</span></span>
       and</span> table_name </span>not like</span> 'LOGGER%'</span> escape </span>'\'</span></span>
       and</span> ...</span></span>
      )</span></span></code></pre>
For the parameter p_data_table_name_like => 'CAT\_%,USERS,ROLES,RIGHTS'</code> the tables are filtered as follows:</p>
where</span> ...</span></span>
  and</span> (   table_name </span>like</span> 'CAT\_%'</span> escape </span>'\'</span></span>
       or</span> table_name </span>like</span> 'USERS'</span>  escape </span>'\'</span></span>
       or</span> ...</span></span>
      )</span></span></code></pre>
There is a good reason why the default p_data_max_rows</code> parameter is set to 1000</code> - if you don’t specify table name filters, all tables will be exported…</p>
The resulting insert scripts look like this:</p>
-- Script generated by PLEX version 2.4.2 - more infos here: https://github.com/ogobrecht/plex</span></span>
-- Performance Hacks by Connor McDonald: https://connor-mcdonald.com/2019/05/17/hacking-together-faster-inserts/</span></span>
-- For strange line end replacements a big thank to SQL*Plus: https://support.oracle.com/epmos/faces/DocumentDisplay?id=2377701.1 (SQL Failed With ORA-1756 In Sqlplus But Works In SQL Developer)</span></span>
prompt </span>-</span> insert</span> 847</span> rows into</span> USERS (exported </span>2021</span>-</span>01</span>-</span>31 14</span>:</span>24</span>:</span>30</span>.</span>703234000</span> +</span>00</span>:</span>00</span>)</span></span>
set</span> define </span>off</span> feedback </span>off</span> sqlblanklines </span>on</span></span>
alter session set</span> cursor_sharing          </span>=</span> force</span>;</span></span>
alter session set</span> nls_numeric_characters  </span>=</span> '.,'</span>;</span></span>
alter session set</span> nls_date_format         </span>=</span> 'yyyy-mm-dd hh24:mi:ss'</span>;</span></span>
alter session set</span> nls_timestamp_format    </span>=</span> 'yyyy-mm-dd hh24:mi:ssxff'</span>;</span></span>
alter session set</span> nls_timestamp_tz_format </span>=</span> 'yyyy-mm-dd hh24:mi:ssxff tzr'</span>;</span></span>
begin</span></span>
insert</span> all</span></span>
into</span> USERS(U_ID,U_FIRST_NAME,U_LAST_NAME,U_EMAIL) </span>values</span> (</span>1</span>,</span>'Ylcmsajbil'</span>,</span>'Fojkjryntnixzfh'</span>,</span>'qvspjgvwmtbi@ghovilkddx.mly'</span>)</span></span>
into</span> USERS(U_ID,U_FIRST_NAME,U_LAST_NAME,U_EMAIL) </span>values</span> (</span>2</span>,</span>'Axify'</span>,</span>'Cofjlkwzxytdih'</span>,</span>'ajgttnqlds@minokpyfo.gu'</span>)</span></span>
into</span> USERS(U_ID,U_FIRST_NAME,U_LAST_NAME,U_EMAIL) </span>values</span> (</span>3</span>,</span>'Ckyqqvuqrkuktb'</span>,</span>'Igacqwp'</span>,</span>'qpygabuhbrs@nsjxpgjlle.ze'</span>)</span></span>
into</span> USERS(U_ID,U_FIRST_NAME,U_LAST_NAME,U_EMAIL) </span>values</span> (</span>4</span>,</span>'Noythhl'</span>,</span>'Gausfu'</span>,</span>'ngmgsbr@duyxqzn.hmyo'</span>)</span></span>
into</span> USERS(U_ID,U_FIRST_NAME,U_LAST_NAME,U_EMAIL) </span>values</span> (</span>5</span>,</span>'Kpewbrecnfzsi'</span>,</span>'Nwbsnjh'</span>,</span>'xwlhcfaxko@uhqsibdojjp.hsm'</span>)</span></span>
into</span> USERS(U_ID,U_FIRST_NAME,U_LAST_NAME,U_EMAIL) </span>values</span> (</span>6</span>,</span>'Qlzyizkl'</span>,</span>'Gwnaojlvyud'</span>,</span>'kzndqj@nsosenf.fm'</span>)</span></span>
into</span> USERS(U_ID,U_FIRST_NAME,U_LAST_NAME,U_EMAIL) </span>values</span> (</span>7</span>,</span>'Xpepttcemrd'</span>,</span>'Ktaqqdnqyfvc'</span>,</span>'uhbnzezvz@buiptt.lkrm'</span>)</span></span>
into</span> USERS(U_ID,U_FIRST_NAME,U_LAST_NAME,U_EMAIL) </span>values</span> (</span>8</span>,</span>'Ybyinr'</span>,</span>'Vngairocujhy'</span>,</span>'igvfzoegbh@hsepkqiwbst.evs'</span>)</span></span>
into</span> USERS(U_ID,U_FIRST_NAME,U_LAST_NAME,U_EMAIL) </span>values</span> (</span>9</span>,</span>'Ctjixltj'</span>,</span>'Yvsiei'</span>,</span>'ozpspssyw@vooiyfuf.xeh'</span>)</span></span>
into</span> USERS(U_ID,U_FIRST_NAME,U_LAST_NAME,U_EMAIL) </span>values</span> (</span>10</span>,</span>'Lttzwsavnozxu'</span>,</span>'Kcyjalvzrl'</span>,</span>'yvwowaqrpku@dyapdumb.fvi'</span>)</span></span>
select</span> *</span> from</span> dual;</span></span>
</span>
/* S N I P */</span></span>
</span>
insert</span> all</span></span>
into</span> USERS(U_ID,U_FIRST_NAME,U_LAST_NAME,U_EMAIL) </span>values</span> (</span>841</span>,</span>'Gpkabykoveq'</span>,</span>'Gljhlrijqop'</span>,</span>'imnhrheyr@ypccyiu.ah'</span>)</span></span>
into</span> USERS(U_ID,U_FIRST_NAME,U_LAST_NAME,U_EMAIL) </span>values</span> (</span>842</span>,</span>'Mwrfazphbvmekpw'</span>,</span>'Kxirzfth'</span>,</span>'fxoatt@frlbwbn.tf'</span>)</span></span>
into</span> USERS(U_ID,U_FIRST_NAME,U_LAST_NAME,U_EMAIL) </span>values</span> (</span>843</span>,</span>'Hzxomvkliaxl'</span>,</span>'Mstdrrmgfmsy'</span>,</span>'gpeidglzwfa@hwyumsansy.fet'</span>)</span></span>
into</span> USERS(U_ID,U_FIRST_NAME,U_LAST_NAME,U_EMAIL) </span>values</span> (</span>844</span>,</span>'Vwvwezfsd'</span>,</span>'Xtfouojiymtlu'</span>,</span>'zgsdtowsvt@ywfngnijgts.ozd'</span>)</span></span>
into</span> USERS(U_ID,U_FIRST_NAME,U_LAST_NAME,U_EMAIL) </span>values</span> (</span>845</span>,</span>'Eljntjfkxx'</span>,</span>'Sifgii'</span>,</span>'gksggat@ubfmmdopqy.ly'</span>)</span></span>
into</span> USERS(U_ID,U_FIRST_NAME,U_LAST_NAME,U_EMAIL) </span>values</span> (</span>846</span>,</span>'Ewvyjeudjb'</span>,</span>'Anihlpdgeg'</span>,</span>'gietuk@ezciwejuedy.nuf'</span>)</span></span>
into</span> USERS(U_ID,U_FIRST_NAME,U_LAST_NAME,U_EMAIL) </span>values</span> (</span>847</span>,</span>'Wscdamsgssmouf'</span>,</span>'Omtaofvlrjs'</span>,</span>'jrwyzftmbmo@gjylnuez.esq'</span>)</span></span>
select</span> *</span> from</span> dual;</span></span>
end</span>;</span></span>
/</span></span>
commit</span>;</span></span>
alter session set</span> cursor_sharing </span>=</span> exact;</span></span>
set</span> define </span>on</span></span></code></pre>
PLEX saves the NLS settings of the current session and makes sure that the insert scripts run with the same settings - this means that you should not get any number or date conversion errors. The performance hacks from Connor are alter session set cursor_sharing = force;</code> and insert all</code> - thanks for pointing that out Connor :-)</p>
PLEX has many parameters to configure the export - the focus of PLEX is to quickly introduce version control to existing projects (see also this article about PLEX in general</a>). If you want to use PLEX only for exporting table data, then you should create a wrapper function for it that suits your personal needs - here is an example:</p>
create or replace function</span> to_insert</span>(</span></span>
  p_table_name </span>varchar2</span>,</span></span>
  p_max_rows   </span>integer default</span> 1000</span>,</span></span>
  p_batch_size </span>integer default</span> 20</span>)</span></span>
  return</span> clob</span></span>
is</span></span>
  l_file_collection plex.tab_export_files;</span></span>
begin</span></span>
  l_file_collection :</span>=</span> plex.backapp(</span></span>
    p_include_data         </span>=></span> true,</span></span>
    p_data_max_rows        </span>=></span> p_max_rows,</span></span>
    p_data_table_name_like </span>=></span> p_table_name,</span></span>
    p_data_format          </span>=></span> 'insert:'</span> ||</span> to_char(p_batch_size),</span></span>
    --overwrite defaults to save work for plex:</span></span>
    p_include_templates    </span>=></span> false,</span></span>
    p_include_runtime_log  </span>=></span> false,</span></span>
    p_include_error_log    </span>=></span> false);</span></span>
  return</span> l_file_collection(</span>1</span>).contents;</span></span>
end</span>;</span></span>
/</span></span></code></pre>
Now you can always do a quick export like this: select to_insert('USERS', 10000) from dual;</code></p>
Happy exporting and scripting :-)</p>
Ottmar</p>


How to migrate Oracle Cloud wallet into existing auto_login_local wallet
2020-08-03T00:00:00+00:00
I started to store user credentials in wallet files for higher security in SQL scripts. If you do so you should also secure the access to your wallet files on the operating system level. This is especially true for auto-login wallets from the Oracle Cloud. To increase the security a bit further you can restrict the auto-login to the local user who created the wallet. To achieve this you need to create an own wallet with orapki</code> instead of mkstore</code>:</p>
orapki</span> wallet create</span> \</span></span>
  -wallet "path/to/my/wallet"</span> \</span></span>
  -pwd myPassword</span> \</span></span>
  -auto_login_local</span></span></code></pre>
You can then add new alias/user/password entries with mkstore (you need to add each alias to your tnsnames.ora):</p>
mkstore</span> \</span></span>
  -wrl "path/to/my/wallet"</span> \</span></span>
  -createCredential myAlias myUser myPassword</span></span></code></pre>
If you use only the instant client and cannot find mkstore and orapki, then have a look at my previous post</a> on how to simulate these tools.</p>
The Migration</h2>
I assume you have set an environment variable called TNS_ADMIN pointing to your TNS directory. In this directory, you have your wallet files and also your existing tnsnames.ora and sqlnet.ora to successfully connect to your local Oracle instances.</p>
Now you need to extract the downloaded cloud wallet - for security reasons it makes sense to create a temporary subdirectory in your TNS directory and extract the cloud wallet there. You need to migrate the entries from tnsnames.ora</code> and sqlnet.ora</code> into your own TNS files and align the path to your wallet directory. Additionally, you should also copy over the file ojdbc.properties</code> if you do not have it already and you plan to use SQLcl or SQL Developer with your wallet.</p>
My resulting sqlnet.ora:</p>
WALLET_LOCATION = (SOURCE = (METHOD = file) (METHOD_DATA = (DIRECTORY = "C:\\path\\to\\my\\wallet")))</span></span>
SSL_SERVER_DN_MATCH = yes</span></span>
sqlnet.wallet_override = true</span></span></code></pre>
My resulting tnsnames.ora:</p>
myCloudDbName_high, myAlias = (description = (...</span></span>
myCloudDbName_medium        = (description = (...</span></span>
myCloudDbName_low           = (description = (...</span></span>
myCloudDbName_tp            = (description = (...</span></span>
myCloudDbName_tpurgent      = (description = (...</span></span>
</span>
myLocalDbName, myOtherAlias = (description = (...</span></span>
...</span></span></code></pre>
That was the easy part, but how you migrate the needed private key and all certificates?</p>
It took me some time to figure this out because most people seem to use the cloud wallet as it is. This is understandable since SQL Developer can direct use the zipped version of the wallet. But my target is not to manage the passwords in multiple places - the databases, multiple wallets, SQL Developer and possibly other tools. I want to manage the passwords only in the databases and in one wallet and use this wallet with all the tools - in my case SQL*Plus, SQLcl and SQL Developer.</p>
First I tried to export the private key and all certificates from the cloud wallet and then import it into my wallet. I was not successful with this mostly because of the private key and unknown alias names - maybe I was too tired from all the try and error things on how to achieve this. I came finally up with the idea to use the cloud wallet Java KeyStore files and convert them into my wallet with the orapki method jks_to_pkcs12</code>.</p>
Migrate private key and certificate from cloud wallet:</p>
orapki</span> wallet jks_to_pkcs12</span> \</span></span>
  -wallet "path/to/my/wallet"</span> \</span></span>
  -pwd myPassword</span> \</span></span>
  -keystore "path/to/cloud/wallet/keystore.jks"</span> \</span></span>
  -jkspwd myCloudWalletPassword</span></span></code></pre>
Migrate trusted certificates from cloud wallet:</p>
orapki</span> wallet jks_to_pkcs12</span> \</span></span>
  -wallet "path/to/my/wallet"</span> \</span></span>
  -pwd myPassword</span> \</span></span>
  -keystore "path/to/cloud/wallet/truststore.jks"</span> \</span></span>
  -jkspwd myCloudWalletPassword</span></span></code></pre>
Finally, list the wallet content to see the migrated entries:</p>
orapki</span> wallet display -wallet . -pwd myPassword</span></span>
# or</span></span>
orapki</span> wallet display -wallet . -pwd myPassword -complete</span></span></code></pre>
The final file list in my TNS directory (without the Java KeyStore files from the cloud wallet):</p>
cwallet.sso</span></span>
cwallet.sso.lck</span></span>
ewallet.p12</span></span>
ewallet.p12.lck</span></span>
ojdbc.properties</span></span>
sqlnet.ora</span></span>
tnsnames.ora</span></span></code></pre>
I am now able to connect to my cloud database with the desired tools without providing user/password details (tested version):</p>

SQL*Plus (19.6): sqlplus /@myAlias</code></li>
SQLcl (20.2): sql /@myAlias</code></li>
SQL Developer (20.2): authentication type “OS”, connection type “Custom JDBC” with URL jdbc:oracle:thin:/@myAlias</code></li>
</ul>
If you forgot which aliases you have configured in your wallet:</p>
mkstore</span> -wrl "path/to/my/wallet" -listCredential</span></span></code></pre>
Hope this helps someone else.</p>
Happy developing and scripting :-)</p>
Ottmar</p>


How to use mkstore and orapki with Oracle Instant Client
2020-07-29T00:00:00+00:00
For some years I use only the Oracle Instant Client</a>. I had too often trouble with the full client installation on my corporate PCs under Windows, especially in the old Windows 32/64 bit times. The instant client can be used by download and extract one basic zip file and adding an entry to your path environment variable. If you want to use SQL*Plus and other tools you need to download two additional files - no drama, also without admin rights.</p>
When I started to store the user details in wallet files I was wondering why Oracle does not deliver the mkstore and orapki tools with the instant client. I searched for a workaround and found some posts about it - including installing the full client or other software to get the tools. But I do not want to install additional software only for two small command-line tools. I found the final hint in an old post from Andriy Dmytrenko</a>. Seems that the two utilities are only shell scripts that are calling some Java libraries. The question was from which location I should take the needed libraries. Since I also have SQLcl</a> on my PC I found the libs there. Below my final shell scripts for Windows - put them somewhere and have the path pointing to the directory where they are stored. If you need them for Linux you will find a way to do it by yourself:</p>
mkstore.bat:</p>
@</span>echo off</span></span>
rem</span> inspiration: https://andriydmytrenko.wordpress.com/2013/07/01/using-the-secure-external-password-store-with-instant-client/</span></span>
</span>
setlocal</span></span>
</span>
rem</span> get the command line arguments</span></span>
set</span> args</span>=</span></span>
:</span>loop</span></span>
  if</span> !%1==!</span> goto</span> :</span>done</span></span>
  set</span> args</span>=</span>%args% %</span>1</span></span>
  shift</span></span>
  goto</span> :</span>loop</span></span>
:</span>done</span></span>
</span>
rem</span> set classpath for mkstore - align this to your local SQLcl installation</span></span>
set</span> sqlcl</span>=</span>c:\path\to\sqlcl\lib</span></span>
set</span> classpath</span>=</span>%sqlcl%\oraclepki.jar</span></span>
set</span> classpath</span>=</span>%classpath%;%sqlcl%\osdt_core.jar</span></span>
set</span> classpath</span>=</span>%classpath%;%sqlcl%\osdt_cert.jar</span></span>
</span>
rem</span> simulate mkstore command</span></span>
java -classpath %classpath% oracle.security.pki.OracleSecretStoreTextUI %args%</span></span>
</span>
endlocal</span></span></code></pre>
orapki.bat:</p>
@</span>echo off</span></span>
rem</span> inspiration: https://andriydmytrenko.wordpress.com/2013/07/01/using-the-secure-external-password-store-with-instant-client/</span></span>
</span>
setlocal</span></span>
</span>
rem</span> get the command line arguments</span></span>
set</span> args</span>=</span></span>
:</span>loop</span></span>
  if</span> !%1==!</span> goto</span> :</span>done</span></span>
  set</span> args</span>=</span>%args% %</span>1</span></span>
  shift</span></span>
  goto</span> :</span>loop</span></span>
:</span>done</span></span>
</span>
rem</span> set classpath for orapki - align this to your local SQLcl installation</span></span>
set</span> sqlcl</span>=</span>c:\path\to\sqlcl\lib</span></span>
set</span> classpath</span>=</span>%sqlcl%\oraclepki.jar</span></span>
set</span> classpath</span>=</span>%classpath%;%sqlcl%\osdt_core.jar</span></span>
set</span> classpath</span>=</span>%classpath%;%sqlcl%\osdt_cert.jar</span></span>
</span>
rem</span> simulate orapki command</span></span>
java -classpath %classpath% oracle.security.pki.textui.OraclePKITextUI %args%</span></span>
</span>
endlocal</span></span></code></pre>
If you need a starter on using mkstore and orapki then Tim Hall from Oracle Base has covered you with an article about the secure external password store</a>.</p>
Happy password storing :-)</p>
Ottmar</p>


Sample Data Sets for Oracle
2020-05-25T00:00:00+00:00
Sometimes you need only some small tables and some rows of data to play around with, to test things out. I think most of you immediately would say EMP, DEPT…</p>
Sure, but a bit more data would be nice. Ok, OE and HR schema…</p>
Sure, but I have no SYS rights on the database in my current project to install the schemas, can I have it in my current dev schema?…</p>
Sure, but then I have to fiddle a bit with the scripts to make it run in my dev schema, I need it fast, no time at all…</p>
Mmhhh, sounds this familiar to you? Maybe I can help…</p>
The sample data sets from Oracle were normally created for a dedicated schema. I changed that and omitted all the schema creation parts of the scripts. Instead, all objects from a data set get a prefix - an example: All objects from the customer orders schema (one of the newer data sets from Oracle) are prefixed with CO_. This allows me to use all data sets in parallel in a single schema and easily identify the data set the object belongs to.</p>
All table scripts are created with identity columns and the simplest possible options for easy readability - no fancy constraint and index names. Constraints and indexes will be renamed with global helper scripts after the table creation. Only real indexes are coded - foreign key indexes are generated with a global helper script too.</p>
For each data set, you have always the same three scripts to handle the installation/data refresh/uninstallation.</p>
List of Data Sets, Copyrights</h2>

EMP & DEPT (2 tabs, 18 rows), source</a>, Copyright Oracle (MIT license</a>)</li>
Order Entry & Human Resources (15 tabs, 3.002 rows), source oe</a>, source hr</a>, Copyright Oracle (MIT license</a>)</li>
Customer Orders (5 tabs, 6.325 rows), source</a>, Copyright Oracle (MIT license</a>)</li>
Sakila DVD Rental Store (16 tabs, 46.273 rows), source</a>, original source</a>, Copyright MySQL AB documentation team, DB Software Laboratory, Lukas Eder (BSD-3-Clause license</a>)</li>
</ul>
For more info about the Oracle sample schemas see the docs</a>.</p>
List of Global Helper Scripts</h2>

Disable/enable all foreign key constraints</li>
Create missing foreign key indexes</li>
Unify constraint names</li>
Unify index names</li>
Sync sequence values to data</li>
</ul>
You can find the project on GitHub</a>.</p>
Hope this helps someone else…</p>
Happy data modeling and testing :-)</p>
Ottmar</p>
P.S. For those of you who are working with Oracle APEX: Have a look under SQL Workshop > Utilities > Sample Datasets</p>


Why I Like SQL*Plus for Deployment Scripts
2020-01-02T00:00:00+00:00
The following simplified example deployment master script is given:</p>
set</span> define </span>off</span> verify </span>off</span> feedback </span>off</span></span>
whenever sqlerror exit sql.sqlcode</span> rollback</span></span>
spool deployment.log</span></span>
</span>
prompt</span></span>
prompt Example Deployment </span>Master</span> Script</span></span>
prompt </span>========================================</span></span>
</span>
prompt Step </span>1</span>: Dummy </span>for</span> demonstration</span></span>
-- normally we call here some other scripts like</span></span>
-- @other-script.sql</span></span>
</span>
prompt Step </span>2</span>: Error test </span>in anonymous block</span></span>
begin</span></span>
  raise_application_error(</span></span>
    -</span>20000</span>,</span></span>
    'Error test for SQL*Plus <> SQLcl comparison'</span></span>
  );</span></span>
end</span>;</span></span>
/</span></span>
</span>
prompt </span>========================================</span></span>
prompt Deployment Done :</span>-</span>)</span></span>
prompt</span></span>
</span>
spool </span>off</span></span></code></pre>
When we call this in SQL*Plus (version 19.5), we get the following output (in
the console and also in deployment.log) with an indication of what went wrong
with our deployment:</p>
Example Deployment </span>Master</span> Script</span></span>
========================================</span></span>
Step </span>1</span>: Dummy </span>for</span> demonstration</span></span>
Step </span>2</span>: Error test </span>in anonymous block</span></span>
begin</span></span>
*</span></span>
ERROR </span>at line</span> 1</span>:</span></span>
ORA</span>-</span>20000</span>: Error test </span>for SQL</span>*</span>Plus </span><></span> SQLcl comparison</span></span>
ORA</span>-</span>06512</span>: </span>at line</span> 2</span></span></code></pre>
Ok, this error message is stupid, but usually, I get some useful information
here to fix my problem in the deployment script - especially when the
problematic script is a bit longer…</p>
When we call this in SQLcl (latest version 19.4 on Windows) we get the following
output (in the console and also the deployment.log):</p>
Example Deployment </span>Master</span> Script</span></span>
========================================</span></span>
Step </span>1</span>: Dummy </span>for</span> demonstration</span></span>
Step </span>2</span>: Error test </span>in anonymous block</span></span></code></pre>
Mhhh… What was going on here? Why was my script terminating in step 2?</p>
That’s one reason why I like SQL*Plus a bit more than SQLcl for deployment
scripts. The fast start time of SQL*Plus is another reason. Nevertheless, SQLcl
is a cool command-line tool.</p>
Happy scripting :-)</p>
Ottmar</p>
PS: There is a small Twitter
discussion</a> around
this…</p>
UPDATE January 3, 2020</h2>
Jeff Smith has confirmed that this bug was fixed in SQLcl version
19.4</a>. I was using
19.4 - but on Windows. It turns out that the bug is still there - only on
Windows, not Mac, not Linux…</p>
So, if you are facing this problem on Windows then you have to wait for a future
release or set as a workaround the feedback to on:</p>
set</span> define </span>off</span> verify </span>off</span> feedback </span>on</span></span>
<</span>snip</span>></span></span></code></pre>
Here the output on my Windows 10 laptop:</p>
Demo Deployment </span>Master</span> Script</span></span>
========================================</span></span>
Step </span>1</span>: Dummy </span>for</span> demonstration</span></span>
Step </span>2</span>: </span>Begin</span> error test </span>in anonymous block</span></span>
Rollback</span></span>
</span>
Error starting </span>at line</span> : </span>10</span> File</span> @ C:\temp\deployment.sql</span></span>
In</span> Command </span>-</span></span>
begin</span></span>
  raise_application_error(</span>-</span>20000</span>, </span>'error test for SQL*Plus <> SQLcl comparison'</span>);</span></span>
end</span>;</span></span>
Error report </span>-</span></span>
ORA</span>-</span>20000</span>: error test </span>for SQL</span>*</span>Plus </span><></span> SQLcl comparison</span></span>
ORA</span>-</span>06512</span>: </span>at line</span> 2</span></span>
20000</span>. </span>00000</span> -</span>  "%s"</span></span>
*</span>Cause:    The stored </span>procedure</span> 'raise_application_error'</span></span>
           was called which causes this error </span>to</span> be </span>generated</span>.</span></span>
*</span>Action</span>:   Correct the problem </span>as</span> described </span>in</span> the error </span>message or</span> contact</span></span>
           the </span>application</span> administrator </span>or</span> DBA </span>for</span> more information.</span></span></code></pre>
If you are on Mac OS or Linux then you have to update to the latest SQLcl
version 19.4 or use also the described workaround.</p>
UPDATE July 20, 2020</h2>
The bug still exists in SQLcl 20.2 and SQL Developer 20.2 under Windows - we
have to wait a bit longer…</p>
UPDATE January 31, 2021</h2>
For me it is working now with SQL Developer 20.4.0 under Windows and also with
SQLcl 20.4.1, when I have the environment variable path pointing to the JDK
delivered within SQL Developer (...\sqldeveloper\jdk\jre\bin\</code>). I had the path
before pointing to another standalone Java 11 distribution and it was not
working there…</p>
Again: happy scripting :-)</p>
Ottmar</p>


Download BLOBs with SQL*Plus
2020-01-01T00:00:00+00:00
Have you ever tried to spool/download BLOBS with SQL*Plus? Some months ago I tried to find a way to download a collection of CLOBs or even better a zipped version of the collection as BLOB. I learned that BLOBs are not a valid datatype in SQL*Plus when it comes to the spool command. I found a way by putting the CLOBs into a global temporary table, creating an intermediate SQL script with tons of select and spool commands, and finally spooling the CLOBs one by one by calling the intermediate SQL script. It was working, but far from elegant. Also, when I was in the home office with a less powerful connection, it was slowing down the whole export process significantly.</p>
If you are using PLEX (PL/SQL Export Utilities) and this sounds familiar to you - the described method was the default for exporting an APEX app or your schema DDL with the delivered export script templates.</p>
If you have no idea what I am talking about: PLEX is a PL/SQL package that is able to export an Oracle APEX app, ORDS modules, all schema objects and table data into a nice directory structure in one go ready to use for version control. Check out the project on GitHub</a> and this blog post on how to get started</a>.</p>
But there is a better way: Simply convert the BLOB into a base64 encoded CLOB. I have no idea why this was not my first solution for the PLEX export templates. In the new version 2.1.0 of PLEX the templates are using this approach. Here is a simplified example.</p>
File export.sql:</p>
set</span> verify </span>off</span> feedback </span>off</span> heading </span>off</span></span>
set</span> trimout </span>on</span> trimspool </span>on</span> pagesize </span>0</span> linesize </span>5000</span> long </span>100000000</span> longchunksize </span>32767</span></span>
whenever sqlerror exit sql.sqlcode</span> rollback</span></span>
variable contents clob</span></span>
begin</span></span>
  :contents :</span>=</span> plex.to_base64(plex.to_zip(plex.backapp(</span></span>
    p_app_id               </span>=></span> 100</span>,</span></span>
    p_include_ords_modules </span>=></span> true,</span></span>
    p_include_object_ddl   </span>=></span> false,</span></span>
    p_include_data         </span>=></span> false,</span></span>
    p_include_templates    </span>=></span> true)));</span></span>
end</span>;</span></span>
/</span></span>
set</span> termout </span>off</span></span>
spool </span>"app_100.zip.base64"</span></span>
print</span> contents</span></span>
spool </span>off</span></span>
set</span> termout </span>on</span></span></code></pre>
Congratulations - You are the owner of a base64 encoded CLOB on your client disk. And now? Before you can unzip the file you need to decode it - depending on your operating system you can do this with your OS tools:</p>

Windows: certutil -decode app_100.zip.base64 app_100.zip</code></li>
Mac: base64 -D -i app_100.zip.base64 -o app_100.zip</code></li>
Linux: base64 -d app_100.zip.base64 > app_100.zip</code></li>
</ul>
Here a simple Windows batch file, which calls the SQL script above, decodes the file and deletes the base64 version.</p>
File export.bat</p>
echo</span> exit </span>|</span> sqlplus -S demo/oracle</span>@</span>localhost:1521/xepdb1 </span>@</span>export.sql</span></span>
certutil</span> -decode app_100.zip.base64 app_100.zip</span></span>
del</span> app_100.zip.base64</span></span></code></pre>
The described method to download a BLOB is independent of the package PLEX - you only need a small helper function to encode the BLOB. I found an example provided by Tim Hall on his Oracle Base site</a>. Thanks for sharing Tim!</p>
CREATE OR REPLACE FUNCTION</span> base64encode</span>(p_blob </span>IN</span> BLOB)</span></span>
  RETURN</span> CLOB</span></span>
-- -----------------------------------------------------------------------------------</span></span>
-- File Name    : https://oracle-base.com/dba/miscellaneous/base64encode.sql</span></span>
-- Author       : Tim Hall</span></span>
-- Description  : Encodes a BLOB into a Base64 CLOB.</span></span>
-- Last Modified: 09/11/2011</span></span>
-- -----------------------------------------------------------------------------------</span></span>
IS</span></span>
  l_clob CLOB;</span></span>
  l_step PLS_INTEGER :</span>=</span> 12000</span>; </span>-- make sure you set a multiple of 3 not higher than 24573</span></span>
BEGIN</span></span>
  FOR</span> i </span>IN</span> 0</span> .. TRUNC((DBMS_LOB.getlength(p_blob) </span>-</span> 1</span> )</span>/</span>l_step) </span>LOOP</span></span>
    l_clob :</span>=</span> l_clob </span>||</span> UTL_RAW.cast_to_varchar2(UTL_ENCODE.base64_encode(DBMS_LOB.substr(p_blob, l_step, i </span>*</span> l_step </span>+</span> 1</span>)));</span></span>
  END LOOP</span>;</span></span>
  RETURN</span> l_clob;</span></span>
END</span>;</span></span>
/</span></span></code></pre>
This function is included in the newest version of PLEX (named to_base64) - you can download PLEX here</a>.</p>
Happy scripting, exporting and version controlling :-)</p>
Ottmar</p>

Ottmar’s Notes - Script

Generate APEX plug-ins on the command line

JavaScript helper functions for conversion</h2> Since I implemented the file watcher and other scripts with Node.js/npm, it was obvious to solve this in JavaScript as well. First the needed modules and a md5 hash function:</p>

A complete example</h2> For those who want to see how everything can work together: I took the examples here in the article from my open source project Oracle Instrumentation Console</a>.</p>

Create fast insert scripts

How to migrate Oracle Cloud wallet into existing auto_login_local wallet

How to use mkstore and orapki with Oracle Instant Client

Sample Data Sets for Oracle

List of Global Helper Scripts</h2> Disable/enable all foreign key constraints</li> Create missing foreign key indexes</li> Unify constraint names</li> Unify index names</li>

Why I Like SQL*Plus for Deployment Scripts

UPDATE July 20, 2020</h2> The bug still exists in SQLcl 20.2 and SQL Developer 20.2 under Windows - we have to wait a bit longer…</p>

Download BLOBs with SQL*Plus

A complete example</h2>
For those who want to see how everything can work together: I took the examples here in the article from my open source project Oracle Instrumentation Console</a>.</p>

UPDATE July 20, 2020</h2>
The bug still exists in SQLcl 20.2 and SQL Developer 20.2 under Windows - we have to wait a bit longer…</p>