Error 1723 oracle database

What a timely question and answer! I was stuck with the same problem, posted to the forum site and was directed here (thanks Eunsil_YOON). The new version of the Achilles R package worked to a point, but after completing the Achilles results, it moved on to the Concept Hierarchy creation, producing the familiar zero-length error:

Executing SQL took 0.563 secs
Done. Achilles results can now be found in schema mark
Executing Concept Hierarchy creation. This could take a while
Connecting using Oracle driver

• using THIN to connect
  | | 0%Error: Error executing SQL:
  java.sql.SQLSyntaxErrorException: ORA-01723: zero-length columns are not allowed

Below is the output of the error report showing the familiar uncasted null column

«null as concept_hierarchy_type,»

👍
DBMS:
oracle

Error:
java.sql.SQLSyntaxErrorException: ORA-01723: zero-length columns are not allowed

SQL:
—HINT DISTRIBUTE_ON_KEY(concept_id)
CREATE TABLE suj9wqrzs_tmpach_ch_condition
AS
SELECT
snomed.concept_id,
snomed.concept_name AS concept_name,
‘Condition’ AS treemap,
null as concept_hierarchy_type,
pt_to_hlt.pt_concept_name as level1_concept_name,
hlt_to_hlgt.hlt_concept_name as level2_concept_name,
hlgt_to_soc.hlgt_concept_name as level3_concept_name,
soc.concept_name AS level4_concept_name

FROM
(SELECT concept_id,
concept_name
FROM mark.concept
WHERE domain_id = ‘Condition’
) snomed
LEFT JOIN
(SELECT c1.concept_id AS snomed_concept_id,
max(c2.concept_id) AS pt_concept_id
FROM mark.concept c1
INNER JOIN
mark.concept_ancestor ca1
ON c1.concept_id = ca1.descendant_concept_id
AND c1.domain_id = ‘Condition’
AND ca1.min_levels_of_separation = 1
INNER JOIN
mark.concept c2
ON ca1.ancestor_concept_id = c2.concept_id
AND c2.vocabulary_id = ‘MedDRA’
GROUP BY c1.concept_id
) snomed_to_pt
ON snomed.concept_id = snomed_to_pt.snomed_concept_id

LEFT JOIN
(SELECT c1.concept_id      AS pt_concept_id,
   c1.concept_name    AS pt_concept_name,
   max(c2.concept_id) AS hlt_concept_id
 FROM mark.concept c1
   INNER JOIN
   mark.concept_ancestor ca1
     ON c1.concept_id = ca1.descendant_concept_id
        AND c1.vocabulary_id = 'MedDRA'
        AND ca1.min_levels_of_separation = 1
   INNER JOIN
   mark.concept c2
     ON ca1.ancestor_concept_id = c2.concept_id
        AND c2.vocabulary_id = 'MedDRA'
 GROUP BY c1.concept_id, c1.concept_name
 ) pt_to_hlt
  ON snomed_to_pt.pt_concept_id = pt_to_hlt.pt_concept_id

LEFT JOIN
(SELECT c1.concept_id      AS hlt_concept_id,
   c1.concept_name    AS hlt_concept_name,
   max(c2.concept_id) AS hlgt_concept_id
 FROM mark.concept c1
   INNER JOIN
   mark.concept_ancestor ca1
     ON c1.concept_id = ca1.descendant_concept_id
        AND c1.vocabulary_id = 'MedDRA'
        AND ca1.min_levels_of_separation = 1
   INNER JOIN
   mark.concept c2
     ON ca1.ancestor_concept_id = c2.concept_id
        AND c2.vocabulary_id = 'MedDRA'
 GROUP BY c1.concept_id, c1.concept_name
 ) hlt_to_hlgt
  ON pt_to_hlt.hlt_concept_id = hlt_to_hlgt.hlt_concept_id

LEFT JOIN
(SELECT c1.concept_id      AS hlgt_concept_id,
   c1.concept_name    AS hlgt_concept_name,
   max(c2.concept_id) AS soc_concept_id
 FROM mark.concept c1
   INNER JOIN
   mark.concept_ancestor ca1
     ON c1.concept_id = ca1.descendant_concept_id
        AND c1.vocabulary_id = 'MedDRA'
        AND ca1.min_levels_of_separation = 1
   INNER JOIN
   mark.concept c2
     ON ca1.ancestor_concept_id = c2.concept_id
        AND c2.vocabulary_id = 'MedDRA'
 GROUP BY c1.concept_id, c1.concept_name
 ) hlgt_to_soc
  ON hlt_to_hlgt.hlgt_concept_id = hlgt_to_soc.hlgt_concept_id

LEFT JOIN mark.concept soc
  ON hlgt_to_soc.soc_concept_id = soc.concept_id 

R version:
R version 3.5.1 (2018-07-02)

Platform:
x86_64-w64-mingw32

Attached base packages:

• stats
• graphics
• grDevices
• utils
• datasets
• methods
• base

Other attached packages:

• Achilles (1.6)
• OhdsiRTools (1.5.5)
• httr (1.3.1)
• openxlsx (4.1.0)
• rjson (0.2.20)
• DatabaseConnector (2.2.0)
• SqlRender (1.5.2)
• devtools (1.13.6)

	Error Number:	Error 1723
Error Name:	Java Error 1723
Error Description:	Error 1723: Java has encountered a problem and needs to close. We are sorry for the inconvenience.
Developer:	Oracle Corporation
Software:	Java
Applies to:	Windows XP, Vista, 7, 8, 10, 11

Java Error 1723 Background

Java Error 1723 is often called as runtime error (bug). Programmers work through different levels of debugging in attempt to make sure that Java is as close to error-free as possible. Sadly, many errors can be missed, resulting in problems like those with error 1723.

Error 1723 might be faced by Java users if they are using the program regularly, also seen as «Java Error 1723». After error 1723 is encountered, the software user has the ability to inform the developer of this issue. The developer will then be able to rectify its source code and release an update in the market. Consequently, the developer will use a Java update package to resolve error 1723 and any other reported error messages.

Why Does Runtime Error 1723 Happen?

Java Error 1723 can most often occur when Java is being loaded up. The following three most significant causes of error 1723 runtime errors include:

Error 1723 Crash — Error 1723 will stop the machine from performing a regular program operation. This occurs a lot when the product (Java) or computer is unable to handle the unique input data.

Java Error 1723 Memory Leak — The consequences of a Java memory leak involve a malfunctioning operating system. Potential triggers may be «infinite loop», or when the program performs a «loop» or repetition over and over again.

Error 1723 Logic Error — The computer system creates incorrect information or produces a different result even though the data that is input is accurate. The culprit in this case is usually a flaw in Oracle Corporation source code that handles the input incorrectly.

Oracle Corporation problems with Java Error 1723 most often stem from a corrupt or missing Java file. As a first troubleshootiong step, most PC professionals will attempt to replace the applicable version of the Oracle Corporation file. Additionally, some Java Error 1723 errors can be due to incorrect registry references, so we recommend conducting a registry scan to clean up any invalid entries.

Common Java Error 1723 Issues

Partial List of Java Error 1723 Java Errors:

• «Java Error 1723 Error.»
• «Win32 Software Error: Java Error 1723»
• «Sorry, Java Error 1723 encountered a problem.»
• «Cannot find Java Error 1723.»
• «Java Error 1723 can’t be found.»
• «Problem starting application: Java Error 1723.»
• «Java Error 1723 not executing.»
• «Java Error 1723 quit.»
• «Software Path Fault: Java Error 1723.»

Java Java Error 1723 issues occur with installation, while Java Error 1723-related software runs, during shutdown or startup, or less-likely during operating system updates. Documenting Java Error 1723 problem occasions in Java is key to determine cause of the Windows problems, and reporting them to Oracle Corporation.

Causes of Java Error 1723 Errors

Malware infestation, invalid Java registry entries, or missing / corrupt Java Error 1723 files can create these Java Error 1723 errors.

More precisely, Java Error 1723 errors created from:

• Corrupt Windows registry keys associated with Java Error 1723 / Java.
• Malware infestation corrupted Java Error 1723 file.
• Java Error 1723 mistakenly deleted or maliciously by software unrelated to the Java application.
• Another software application in conflict with Java Error 1723.
• Incomplete or corrupt Java (Java Error 1723) from download or installation.

Product by Solvusoft

Download Now
WinThruster 2022 — Scan your PC for computer errors.

Compatible with Windows 11, 10, 8, 7, Vista, XP and 2000

Optional Offer for WinThruster by Solvusoft | EULA | Privacy Policy | Terms | Uninstall

How to fix the Runtime Code 1723 Java Error 1723

Symptoms of Code 1723 — Java Error 1723

Runtime errors happen without warning. The error message can come up the screen anytime Java is run. In fact, the error message or some other dialogue box can come up again and again if not addressed early on.

There may be instances of files deletion or new files appearing. Though this symptom is largely due to virus infection, it can be attributed as a symptom for runtime error, as virus infection is one of the causes for runtime error. User may also experience a sudden drop in internet connection speed, yet again, this is not always the case.

(For illustrative purposes only)

Causes of Java Error 1723 — Code 1723

During software design, programmers code anticipating the occurrence of errors. However, there are no perfect designs, as errors can be expected even with the best program design. Glitches can happen during runtime if a certain error is not experienced and addressed during design and testing.

Runtime errors are generally caused by incompatible programs running at the same time. It may also occur because of memory problem, a bad graphics driver or virus infection. Whatever the case may be, the problem must be resolved immediately to avoid further problems. Here are ways to remedy the error.

Repair Methods

Runtime errors may be annoying and persistent, but it is not totally hopeless, repairs are available. Here are ways to do it.

If a repair method works for you, please click the upvote button to the left of the answer, this will let other users know which repair method is currently working the best.

Please note: Neither ErrorVault.com nor it’s writers claim responsibility for the results of the actions taken from employing any of the repair methods listed on this page — you complete these steps at your own risk.

ORA-01723: zero-length columns are not allowed
Cause: Columns with zero length were not allowed.
Action: Correct the use of the column.

Example to reproduce ORA-01723 —

SQL> Create table mytable as
select
        ename,
        null age,
    null doj,
    null mgrname
from
        scott.emp ;

        null age
        *
ERROR at line 4:
ORA-01723: zero-length columns are not allowed

Solution to avoid ORA-01723 exception use cast:

SQL> Create table mytable as
select
        ename,
        cast(null as number) age,
        cast(null as date) doj,
        cast(null as varchar2(10)) mgrname
from
        scott.emp ;

Table created.


SQL> desc mytable
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 ENAME                                              VARCHAR2(10)
 AGE                                                NUMBER
 DOJ                                                DATE
 MGRNAME                                            VARCHAR2(10)

_____________________________________________________________________________________________________________________

_____________________________________________________________________________________________________________________

Website Stats