Hi!
Sorry for the delay, I was doing some consultation with my team mates. After making a few tests I found a few discrepancies between the working decoder test log and the one that doesn't match.
Fist of all, adjusting de decoder like this will prematch both cases:
<decoder name="oracle_audit">
<prematch>journal: Oracle Audit[\d+]:</prematch>
</decoder>
<decoder name="oracle_audit">
<parent>oracle_audit</parent>
<regex type="pcre2">^(\w+)\s+(\d+)\s+(\d+:\d+:\d+)\s+\w+\s+journal:\s+Oracle\s+Audit\[\d+\]:</regex>
<order>oracle.mes,oracle.dia,oracle.hora</order>
</decoder>
Also, the following test log has a standard timestamp format which will be predigested in the
timestamp field, but won't be matched with the custom fields as it is already pre-digested:

In the 2nd case the day of the timestamp has only 1 digit and it is not recognized as a standard format, so all the log line is analyzed to extract the custom fields:
So, if the day has 1 digit
(like 7) it will be processed in one way, but if it has 2 digits
(like 17) it will processed as a standard timestamp.
If the log cannot be configured to have standard format, there's a workaround to capture both possible formats in the same field, which would be
timestamp. To do so the decoder would look like this:
<decoder name="oracle_auditEkip">
<prematch type="pcre2">^\w{3}\s+\d{1,2}\s+\d+:\d+:\d+\s+\w+\s+journal:\s+Oracle\s+Audit\[\d+\]:</prematch>
</decoder>
<decoder name="oracle_auditEkip_child">
<parent>oracle_auditEkip</parent>
<regex type="pcre2">^(\w+\x20\d+\x20\d+:\d+:\d+)\x20\x20</regex>
<order>timestamp</order>
</decoder>
<decoder name="oracle_audit">
<prematch>journal: Oracle Audit[\d+]:</prematch>
</decoder>
<decoder name="oracle_audit">
<parent>oracle_audit</parent>
<regex type="pcre2">^(\w+)\s+(\d+)\s+(\d+:\d+:\d+)\s+\w+\s+journal:\s+Oracle\s+Audit\[\d+\]:</regex>
<order>oracle.mes,oracle.dia,oracle.hora</order>
</decoder>
