Autor: Tom Lieber (Page 2 of 4)

Die Migration von Oracle Forms zu APEX: 5 Vorteile und 5 Risiken


In der sich ständig weiterentwickelnden Welt der Technologie ist es für Unternehmen unerlässlich, ihre Anwendungen auf dem neuesten Stand zu halten. Eine Technologie, die in den letzten Jahren in den Fokus gerückt ist, ist Oracle Application Express (APEX), eine Plattform, die als vielversprechende Option für die Modernisierung von Oracle Forms Anwendungen gilt. In diesem Beitrag werden wir die fünf Hauptvorteile und Risiken der Migration von Oracle Forms zu APEX untersuchen.

Vorteile der Migration zu APEX:

  1. Leichtgewichtige Architektur: APEX ist eine Plattform, die in der Cloud oder On-Premises betrieben werden kann. Dies bietet Flexibilität und erleichtert die Integration in bestehende Infrastrukturen.
  2. Einfache Bedienung: APEX bietet eine benutzerfreundliche Oberfläche und eine einfache Programmierung, die sowohl Entwicklern als auch Endbenutzern zugänglich ist.
  3. Skalierbarkeit: APEX ist auf Skalierbarkeit ausgelegt und kann problemlos für kleine oder große Unternehmen verwendet werden. Es kann auf eine Vielzahl von Datenquellen zugreifen und ermöglicht die Integration von Drittanbieter-Tools.
  4. Sicherheit: APEX bietet robuste Sicherheitsfunktionen, darunter eine rollenbasierte Zugriffskontrolle, Schutz vor SQL-Injektion Angriffen und SSL-Unterstützung.
  5. Kosteneffizienz: Im Vergleich zu Oracle Forms ist APEX in den meisten Fällen kostengünstiger, insbesondere wenn eine bestehende Oracle-DB-Infrastruktur vorhanden ist.

Risiken der Migration zu APEX:

  1. Komplexe Architektur: Oracle-Forms-Anwendungen haben oft eine komplexe Architektur, die sich über Jahre hinweg entwickelt hat. Die Modernisierung erfordert ein tiefes Verständnis der Architektur und der verwendeten Technologien.
  2. Fehlende Dokumentation: Oft fehlt es an ausreichender Dokumentation, um das Verständnis der Architektur und der Funktionalität der Anwendung zu erleichtern. Dies kann die Modernisierung erschweren und den Prozess verlangsamen.
  3. Inkompatible Technologien: Oracle Forms wurde entwickelt, bevor moderne Web- und Mobiltechnologien aufkamen. Die Anwendung ist daher in der Regel nicht mit diesen Technologien kompatibel. Die Modernisierung erfordert oft eine umfassende Überarbeitung der Benutzeroberfläche und der Backend-Architektur.
  4. Komplexität der Datenmigration: Bei der Modernisierung von Oracle-Forms-Anwendungen kann die Datenmigration eine Herausforderung darstellen. Die Daten müssen oft in ein neues Datenbankschema migriert werden, was Zeit und Ressourcen erfordert.
  5. Schulung der Mitarbeiter: Die Migration von Oracle Forms nach APEX erfordert eine Umschulung der Entwickler, um sicherzustellen, dass sie die neuen Technologien verstehen und effektiv nutzen können.


Die Migration von Oracle Forms zu APEX bietet eine Reihe von Vorteilen, darunter eine leichtgewichtige Architektur, einfache Bedienung, Skalierbarkeit, verbesserte Sicherheit und Kosteneffizienz. Gleichzeitig gibt es jedoch auch Risiken, wie die Komplexität der vorhandenen Architektur, fehlende Dokumentation, Inkompatibilität mit modernen Technologien, die Herausforderung der Datenmigration und die Notwendigkeit der Umschulung von Entwicklern. Daher ist es wichtig, dass Unternehmen eine sorgfältige Planung und Vorbereitung durchführen, um sicherzustellen, dass die Migration erfolgreich ist. Mit der richtigen Strategie und den richtigen Ressourcen können Unternehmen jedoch die Vorteile von APEX voll ausschöpfen und ihre Anwendungen erfolgreich modernisieren.

Oracle Apex 23.1


Beste Apex Release ever is here..

Oracle APEX 23.1 has introduced a number of new features and improvements that enhance and expand the development experience. Here are some of the highlighted features:

  1. Template Components Unleashed: With APEX 23.1’s Template Components, building UI components is made easy and reusable. They can be rendered as standalone regions or within reports, and they support actions, menus, and custom attributes.
  2. PWA Push Notifications: The push notifications keep users updated whether they’re on desktop or mobile. They allow for easy subscription management and a manageable queue of notifications. The setup is very quick and straightforward.
  3. Developer Experience: The improvements to the Object Browser in APEX 23.1 offer a modernized design and enhanced editing experience. It also has improved performance and accessibility.
  4. Page Processing Improvements: With the new Page Process Type – Execution Chains, you can keep your page processes organized and under control. You can now monitor and report on running background executions, making your life as an APEX developer more efficient and enjoyable.
  5. REST Data Source Enhancements: With the REST Data Source Enhancements, you can invoke API for REST Sources, discover them with Swagger/OpenAPI, and enjoy the added flexibility of Raw Selectors.
  6. General Builder Improvements: With the General Builder Improvements, you can now copy pages from Create App, save and run pages from Code Editor, and access context-sensitive help. There is also native support for Property Graphs in Database 23c.
  7. APEX Approvals: With the Approvals component in APEX 23.1, you can keep your approval tasks on track by specifying due dates when creating them.
  8. Universal Theme and UX Improvements: The Universal Theme in APEX 23.1 has been updated and improved. It offers improved Template Components, improved icon fidelity, and an enhanced Region Display Selector.

These improvements and features contribute to making APEX an even more powerful platform for developing enterprise applications.

Exasol Virtual Schema Performancetest

In today’s world, where companies have to deal with huge amounts of data, the issue of data management efficiency becomes more and more important. One of the solutions to optimize data management and improve performance is to use Virtual Schemas in Exasol, a high-performance in-memory database.

In the following, we present a performance test of Exasol Virtual Schema to reduce the amount of data in an Exasol cluster environment. The idea behind this technique is to use a smaller Exasol cluster with a storage (memory) license and offload data to it.

Offloading data to a smaller cluster can lead to better performance by reducing the amount of active data that needs to be stored on the main Exasol instance. It also allows for greater flexibility by not having to keep the data on the main cluster all the time, resulting in better use of resources.

To perform this test, we use the Virtual Schema Adapter, which is written in Java. This adapter allows us to interact with Exasol via JDBC.

First we create the schema and the adapter:

    %scriptclass com.exasol.adapter.RequestDispatcher;
    %jar /buckets/bfsdefault/vschema/virtual-schema-dist-10.5.0-exasol-7.1.1.jar;

We then define two connections to our Exasol instance, one JDBC and one native Exasol connection:

TO 'jdbc:exa:'
TO ''

After that we create the Virtual Schema with the JDBC connection we created earlier:

    IMPORT_FROM_EXA = 'true'
    MAX_TABLE_COUNT = '10000';

After that, the data will be merged with the data from the other source:

Since we do not want that another query is necessary than before. It should remain transparent for our customer!

create or replace view FULL_DATA
as select * from ACTUAL_DATA 
where datadate > sysdate-interval '1' MONTH
union all 
where datadate < sysdate- interval '1' MONTH;

When we do a performance test we see that there is a clear difference if we do a query on a large database or on 2 databases when they are linked via Union All and Virtual Schema.

DEV1 is really slow – but cheap!

The optimizer of course passes the Where Clause, but still fetches all the necessary data over the network. And that takes time. Note: Runtime in seconds.

Conclusion: Depending on the query, the query performance has an effect. If you only need a few data for a calculation, it is of course not so dramatic, but we achieved a slowness factor between 11 upto 157 in our tests. Since we only tested with simple queries, this is still an important knowhow for us.



Oracle Security Patches

Stay safe and patch

We would like to inform you that it’s patching day again, even though many of our customers have their databases located behind a secure network firewall. We understand that some customers may be reluctant to regularly engage in patching due to the effort and risks involved, especially when the system is actively in use. Therefore, we recommend that Oracle patches be initially installed on development and test systems before being applied to the production system after 2-3 weeks. We would be happy to support you in managing the patching process of your Oracle environment. Our Managed Services team is available to assist you promptly, and we also recommend this approach to our customers.


Introduction: Patching is an essential aspect of maintaining an Oracle environment. Keeping up with the latest patches can help ensure the security, stability, and performance of your database system. However, the patching process can be overwhelming, especially for beginners. In this blog post, we’ll provide a step-by-step guide to Oracle patching and offer some tips to help simplify the process.

Step 1: Identify the Appropriate Patches Before starting the patching process, you need to identify the appropriate patches for your environment. Oracle releases patches on a regular basis, so it’s essential to keep track of the latest patches and determine which ones are relevant to your database system. You can use Oracle’s My Oracle Support (MOS) to identify and download patches.

Step 2: Plan the Patching Process Once you have identified the appropriate patches, it’s time to plan the patching process. This involves creating a patching plan that outlines the sequence of patch installations, the estimated downtime, and the rollback strategy. It’s important to involve stakeholders in the planning process to ensure that the patching process aligns with their requirements.

Step 3: Test the Patches Before installing patches on the production environment, it’s essential to test them on a development or test environment. This can help identify any potential issues that may arise during the patching process. It’s crucial to ensure that the testing environment replicates the production environment as closely as possible.

Step 4: Install the Patches After testing the patches, it’s time to install them on the production environment. The installation process can vary depending on the type of patch, but Oracle provides detailed instructions on how to install each patch.

Step 5: Validate the Patch Installation Once the patches have been installed, it’s important to validate the patch installation to ensure that the patches have been successfully applied. You can use Oracle’s opatch utility to validate the patch installation.

Step 6: Monitor and Maintain the Patched Environment After successfully patching the environment, it’s essential to monitor and maintain the patched environment. This includes regularly checking for new patches, applying patches as needed, and testing the patches before applying them to the production environment.

Conclusion: Oracle patching can be a complex and time-consuming process, but it’s an essential aspect of maintaining a stable and secure database environment. By following these steps, you can simplify the patching process and ensure that your Oracle environment remains up-to-date and secure.

About our chart series

The topics covered in this chart series explore the types of charts used in data visualization and how they can help you better understand data patterns. The articles cover the pros and cons of various charts such as area charts, pie charts, heat maps, bubble charts, Sankey charts, boxplots, Gantt charts, line charts, and bar charts. Each article explains the purpose of the chart, how to interpret it, and when to use it. These articles provide valuable information for data analysts, project managers, and anyone who wants to visualize data in a more meaningful way.

We are happy to share our experience, feel free to ask us about dashboards and charts!


Understanding Data Patterns with Area Charts


Area charts are a type of data visualization that display quantitative data over time or across categories. They are similar to line charts, but with the area beneath the line filled in with color or shading to create a solid shape.

Area charts are useful for showing trends in data, especially when comparing multiple data sets. They can also be used to emphasize the magnitude of changes in data over time or across categories. However, they can be less precise than other types of charts, especially when the data sets overlap.

When creating an area chart, it’s important to choose appropriate colors and shading to ensure that the chart is easy to read and interpret. It’s also important to label the axes clearly and provide a legend to help viewers understand the data being presented.

The main difference between area charts and line charts is that in area charts, the area beneath the line is filled in with color or shading to create a solid shape, while in line charts, only the line representing the data is displayed.

Here are some key differences between area charts and line charts:

  1. Emphasis: Area charts place more emphasis on the magnitude of changes in data over time or across categories, while line charts focus more on the trends and patterns in the data.
  2. Precision: Line charts tend to be more precise than area charts because they only display the line representing the data without the added shading or color that may obscure or overlap data points.
  3. Data density: Line charts are better suited for displaying large data sets or data with many categories, while area charts may become difficult to interpret when multiple data sets overlap or when there are too many categories.
  4. Interpretation: Line charts are easier to interpret for comparisons and relationships between multiple data sets, while area charts are better for showing how a single data set changes over time or across categories.

Ultimately, the choice between an area chart and a line chart depends on the specific data being presented and the intended message or insights to be conveyed.

Use-Cases for area-charts:

  1. Stock Market Performance: An area chart can be used to show the performance of a stock market index, such as the S&P 500, over time. The chart would display the index value on the vertical axis and time on the horizontal axis. The area beneath the line would be filled in with color or shading to show the magnitude of changes in the index value.
  2. Website Traffic: An area chart can be used to show the traffic to a website over time. The chart would display the number of page views on the vertical axis and time on the horizontal axis. The area beneath the line would be filled in with color or shading to show the level of traffic.
  3. Sales by Product Category: An area chart can be used to show sales by product category over time. The chart would display the sales amount on the vertical axis and time on the horizontal axis. The area beneath each line, representing each product category, would be filled in with a different color or shading to differentiate between the categories.
  4. Climate Data: An area chart can be used to show changes in climate data, such as temperature or precipitation, over time. The chart would display the data on the vertical axis and time on the horizontal axis. The area beneath the line would be filled in with color or shading to show the magnitude of changes in the data.

Create an Area Chart (

Oracle 23c: A Necessary Upgrade for the Future

As a database developer, I’m sure you’re aware of the importance of staying up-to-date with the latest technology. Oracle 23c is the latest version of Oracle’s database software, and it’s a necessary upgrade for the future. With its improved scalability, enhanced security, and advanced analytics capabilities, Oracle 23c is a must-have for any business that wants to stay competitive in the digital age. It’s a powerful tool that can help you take your business to the next level.

Oracle 23c Free Developers Edition will bring the Release early to Developers


Things that we as Oracle Database Developers have been missing for a long time have now been implemented for the most part:

  • Data type BOOLEAN
  • The End from DUAL
  • Column alias in GROUP BY und HAVING
  • Better Error Messages
  • Annotiations for Table, Columns usw.. useful for LOVs ?
  • Javascript supportin the database
  • JSON Duality Views
  • GraphQL

Try it out:


Oracle 23c is a great upgrade for the future. It’s packed with new features that make it easier to use and more secure. I’m excited to see what this upgrade has to offer and how it can help us stay ahead of the competition. It’s a necessary upgrade for the future!

TIPP to get more Free Stuff from Oracle .. more coming soon ..

Databases (

Why I’ll Never Use Pie Charts Again


If you’re like me, you’ve probably used pie charts in the past to visualize data. But after a while, I started to realize that pie charts weren’t the best way to present information. They can be difficult to read, hard to compare, and just plain ugly. That’s why I’ll never use pie charts again. Instead, I’ll be using more modern, Human-friendly alternatives like bar graphs, line graphs, and scatter plots. These options are much easier to read, easier to compare, and can be customized to look more visually appealing. So if you’re looking for a better way to present data, ditch the pie charts and try something other.


I used to think pie charts were the best way to display data, but after trying them out I realized they can be misleading. They don’t always show the full picture, and it’s hard to compare values. So, I’m done with pie charts – I’m sticking to bar graphs from now on.

Create a Pie or Ring Chart (

How Heat Maps Can Help You Find the Big Fish in Your Data Pond

A heat map is a graphical representation of data in which different values are represented by different colors. In a BI dashboard, a heat map can be used to visualize patterns and trends in large datasets, making it easier for users to quickly identify areas of interest and focus their attention where it’s needed most.

Some use-cases for heat maps in BI dashboards include:

  1. Sales Analysis: A heat map can be used to show the distribution of sales across different regions or territories. This can help sales teams identify areas where they need to focus their efforts in order to improve performance.
  2. Customer Behavior Analysis: A heat map can be used to show the areas of a website or application where users are spending the most time. This can help designers and product managers identify areas of the user experience that need improvement.
  3. Risk Management: A heat map can be used to visualize potential risks and their likelihood of occurrence. This can help organizations identify and prioritize risks in order to develop effective risk management strategies.

Some good practices for using heat maps in BI dashboards include:

  1. Keep it Simple: Heat maps can quickly become overwhelming if there are too many data points or if the colors are too bright or contrasting. Stick to a simple color scheme and limit the number of data points in order to keep the visualization clear and easy to read.
  2. Use Color Effectively: Choose colors that are easy to differentiate and that have meaning. For example, green might represent positive values, while red might represent negative values. Make sure that the color scheme is intuitive and easy to understand.
  3. Provide Context: Heat maps are most useful when they are accompanied by other data or visualizations that provide context. For example, a heat map showing sales by region might be more useful if it’s also accompanied by a chart showing the overall sales trends over time.

Introduction to Heat Maps (

Exploring the Power of Bubble Charts with Hans Rosling


If you’re looking to explore the power of bubble charts, Hans Rosling is the man to turn to. A Swedish statistician and public health professor, Rosling is known for his groundbreaking work in data visualization. He was the first to use bubble charts to illustrate the relationship between health and wealth in the world. Through his work, Rosling has been able to make complex data more accessible and understandable. With his help, you can learn how to create your own bubble charts and use them to explore the power of data visualization.

Hans Rosling was a Swedish physician, statistician, and public speaker who was known for his creative use of data visualization to explain complex global issues. He was a pioneer in the use of bubble charts to illustrate data in a more visually appealing way. Bubble charts are a type of chart that uses circles to represent data points, with the size of the circle representing the magnitude of the data point.

Rosling used bubble charts to show the progress of countries over time, such as the change in life expectancy and the GDP of countries. He used this type of chart to demonstrate how the world has changed and to show the differences between countries. His work has been credited with helping to bring data visualization to the mainstream and to make it more accessible to the public. Rosling’s work has been an inspiration to many, and his use of bubble charts has been adopted by many other data visualizers. His work has helped to make data more accessible and easier to understand, and has been a great contribution to the field of data visualization. His legacy will continue to inspire and inform data visualizers for years to come.


I recently watched Hans Rosling’s TED Talk on the power of bubble charts. It was amazing to see how he used data to tell a story and how he used visuals to make it easier to understand. I’m inspired to use bubble charts to explore data in my own work.

« Older posts Newer posts »

© 2024 Sphinx Blog

Theme by Anders NorenUp ↑