Skip to Main Content

DevOps, CI/CD and Automation

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Validate XML: LSX-00333: literal "..." is not valid with respect to the pattern

MarwimFeb 4 2025 — edited Feb 5 2025

Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.21.0.0.0

→ code for the current problem and the working example at the end of the post

A long time ago I had a problem validating a XML containing a timestamp.

https://forums.oracle.com/ords/apexds/post/validate-xml-datetime-ora-01830-01858-7109

My current problems seems to be very similar but I just can't get it to work

The element to validate is a timestamp with three digits

 <puegRequest:DatumAnfrage>2025-01-31T13:09:16.739</puegRequest:DatumAnfrage>

it is defined as

<xs:element name="DatumAnfrage" type="common:DatumZeitMilliSecType"/>
    <xs:simpleType name="DatumZeitMilliSecType" xdb:SQLType="TIMESTAMP">
        <xs:annotation>
            <xs:documentation>Zeitstempel ohne Angabe der Zeitzone im XML Datumsformat</xs:documentation>
        </xs:annotation>
        <xs:restriction base="xs:dateTime">
            <xs:pattern value="20[0-9]{2}-(12|11|10|0[1-9])-((3)(0|1)|(1|2)[0-9]|(0)[1-9])T([0-1][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9].[0-9]{3}"/>
        </xs:restriction>
    </xs:simpleType>

As you can see I annotated it as SQLType TIMESTAMP

I validate it with

ALTER SESSION SET NLS_TIMESTAMP_FORMAT='yyyy-mm-dd"T"hh24:mi:ss.ff3';
ALTER SESSION SET NLS_NUMERIC_CHARACTERS = '.,';
…
XMLTYPE.schemaValidate(xmldoc)

And get

ORA-31154: Ungültiges XML-Dokument → invalid XML-Document
ORA-19202: Fehler bei XML-Verarbeitung → Error occurred in XML processing
LSX-00333: Literal "2025-01-31T13:09:16.739000" ist bezogen auf Muster nicht gültig
→literal "…" is not valid with respect to the pattern

Any idea why it compares 6 digits. What is the difference to the working example in the other thread (see code below)?

The complete xsd can be found at Schemata PUEG für Arbeitgeber und Zahlstellen - Datenstelle der Rentenversicherung

My current example

BEGIN
   dbms_xmlschema.registerSchema(
        schemaURL => 'timestamp.xsd'
       ,schemaDoc =>   q'[<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb">
 <xs:element name="DatumAnfrage" type="DatumZeitMilliSecType"/>
    <xs:simpleType name="DatumZeitMilliSecType" xdb:SQLType="TIMESTAMP">
        <xs:annotation>
            <xs:documentation>Zeitstempel ohne Angabe der Zeitzone im XML Datumsformat</xs:documentation>
        </xs:annotation>
        <xs:restriction base="xs:dateTime">
            <xs:pattern value="20[0-9]{2}-(12|11|10|0[1-9])-((3)(0|1)|(1|2)[0-9]|(0)[1-9])T([0-1][0-9]|2[0-3]):[0-5][0-9]:[0-5][0-9].[0-9]{3}"/>
        </xs:restriction>
    </xs:simpleType>
</xs:schema>]'
       ,local => TRUE
       ,genTypes => FALSE
       ,genTables => FALSE
       ,enableHierarchy => dbms_xmlschema.ENABLE_HIERARCHY_NONE
   );
END;
/

ALTER SESSION SET NLS_TIMESTAMP_FORMAT='yyyy-mm-dd"T"hh24:mi:ss.ff3';
ALTER SESSION SET NLS_NUMERIC_CHARACTERS = '.,';
DECLARE
doc xmltype := xmltype('<DatumAnfrage>2012-06-02T09:30:47.123</DatumAnfrage>', 'timestamp.xsd');
BEGIN
 doc.schemaValidate();
EXCEPTION
   WHEN OTHERS THEN RAISE;
END;
/

The working example from the other thread

BEGIN
   dbms_xmlschema.registerSchema(
        schemaURL => 'timestamp.xsd'
       ,schemaDoc =>   q'[<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xdb="http://xmlns.oracle.com/xdb">
 <xs:element name="CreDtTm" type="ISODateTime" />
 <xs:simpleType name="ISODateTime" xdb:SQLType="TIMESTAMP">
   <xs:restriction base="xs:dateTime"/>
 </xs:simpleType>
</xs:schema>]'
       ,local => TRUE
       ,genTypes => FALSE
       ,genTables => FALSE
       ,enableHierarchy => dbms_xmlschema.ENABLE_HIERARCHY_NONE
   );
END;
/

ALTER SESSION SET NLS_TIMESTAMP_FORMAT='yyyy-mm-dd"T"hh24:mi:ss.ff3';
ALTER SESSION SET NLS_NUMERIC_CHARACTERS = '.,';
DECLARE
doc xmltype := xmltype('<CreDtTm>2012-06-02T09:30:47.000</CreDtTm>', 'timestamp.xsd');
BEGIN
 doc.schemaValidate();
EXCEPTION
   WHEN OTHERS THEN RAISE;
END;
/

Comments

Sdhamoth-Oracle Oct 16 2024

Check the error reported in “Control panel→System and Securities→Administrative Tools→Event Viewer” under Windows Log→Application.

How did you set the Instant Client path in PATH? In command prompt?

If you have set it in a command prompt, then make sure you start that command prompt as administrator (i.e. opening it by right clicking on command prompt icon and select “run as administrator” from popped context menu). Also, you should start ODBC data source administrator by executing “odbcad32” from that command prompt. Have you?

pczurak-JavaNet Oct 16 2024

Yes I started the cmd as run as Administrator.

I am using ODBC 64 bit not 32 bit.

I set the path using Windows UI (System properties), and if I open a cmd window and type set I can see the correct path.

starting “odbcad32” from the command line did not help.

I tried the same process on a different computer and got the same results.

Sdhamoth-Oracle Oct 16 2024

odbcad32 is for ODBC 64 bit on Windows x64 versions. You need to start odbcad32 from syswow64 directory to configure ODBC 32 bit on Windows x64 versions.

Have you checked the Application error logs in Event viewer? Did you find any error related to your ODBC application?

pczurak-JavaNet Oct 16 2024

I am running the 64bit version, if I start odbcad32 from syswow64 it starts the 32bit version.

There are no errors in the Event Viewer.

pczurak-JavaNet Oct 17 2024

I have tried basic driver version 19.24, but when I click on the Test button, I get the following error:

---------------------------
Testing Connection
---------------------------
Unable to connect
SQLState=S1000
[Oracle][ODBC][Ora]ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA

---------------------------
OK
---------------------------

Sdhamoth-Oracle Oct 17 2024

Looks like the service name is missing in your connection string.

Here is a sample of connection string:

sales=
(DESCRIPTION=
(ADDRESS= (PROTOCOL=tcp)(HOST=sales-server)(PORT=1521))
(CONNECT_DATA=
(SERVICE_NAME=sales.us.acme.com)))
The part that is highlighted with bold characters seems to be missing in your connection string. Fix it.

pczurak-JavaNet Oct 17 2024

This is what I am using.

JDEPRD =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = testoda0)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = jdeprd.test.com)
)
)

Sdhamoth-Oracle Oct 17 2024

Are you able to connect to your database using SQL*Plus?

pczurak-JavaNet Oct 17 2024

No:

F:\instantclient_23_5>sqlplus

SQL*Plus: Release 19.0.0.0.0 - Production on Thu Oct 17 07:55:39 2024
Version 19.24.0.0.0

Copyright (c) 1982, 2024, Oracle. All rights reserved.

Enter user-name: testuser
Enter password:
ERROR:
ORA-12560: TNS:protocol adapter error

Enter user-name:

pczurak-JavaNet Oct 17 2024

The issue is fixed

In the ODBC Driver Configuration.

For the TNS Service Name you cannot type the name even if you type it exactly as it shows in the dropdown, you must select it from the dropdown, otherwise it won't work.

1 - 10

Post Details

Added on Feb 4 2025
1 comment
52 views