Source Extractor - SQL PLSQL - Extraction step on Documentation - V2

Source Extractor - SQL PLSQL - Error - IO exception Socket read timed out

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page provides solution to the PL/SQL extraction error :

Extracting: Oracle system check constraints on tables.. Extraction error: Io exception: Socket read timed out
on Query
——
Extraction error: Closed Connection

Observed in CAST AIP

Release	Yes/No
8.2.x	❌
8.1.x	❌
8.0.x	❌
7.3.x	❌
7.2.x	❌
7.0.x	✅

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	✅
CSS2	❌
CSS1	✅

Step by Step Scenario

Source Extractor - SQL PLSQL - Non Fatal Error - Extraction error - ORA-01427 single-row subquery returns more than one row

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page will help you to solve issues related to the below Extraction error message that occurs during PL/SQL extraction :

2017-12-11 07:50:40.036 - Extraction error: ORA-01427: single-row subquery returns more than one row

2017-12-11 07:50:50.411 - Extraction error: ORA-01427: single-row subquery returns more than one row

2017-12-11 07:51:00.785 - Extraction error: ORA-01427: single-row subquery returns more than one row

2017-12-11 07:51:11.190 - Extraction error: ORA-01427: single-row subquery returns more than one row

Source Extractor - SQL PLSQL - Error - No more data to read from socket

Mon, 01 Jan 0001 00:00:00 +0000

Problem Description

Following error encountered while extracting schema.

Extraction error: No more data to read from socket
Extraction error: OALL8 is in an inconsistent state
Extraction error: Io exception: Software caused connection abort: socket write error
Initialization error: Closed Connection
Extracting: Oracle public synonyms on views…
Error executing: Extraction -driver oracle.jdbc.OracleDriver -url jdbc:oracle:thin:@XXXX:1521:XXXX -user XXXX -password ************ -parameters schema=XXX -target C:\Users\exportResults => java.lang.NullPointerException
Execution failed!

Info

This issue has been observed in CAST version 7.1.0

Source Extractor - SQL PLSQL - Error - Resolution error type in CAST_AST_XXX for identification group

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page explains the impact of the below Resolution error message you can see in the PL/SQL Extraction

Resolution error type in: XXXXX for identification group: DT on value: ***.PLS_INTEGER

Resolution error type in: XXXXX for identification group: DT on value: ***.ODCIINDEXCTX

Resolution error type in: XXXXX for identification group: DT on value: ***.STRING

Resolution error type in: XXXXX for identification group: DT on value: ***.XMLFORMAT

Source Extractor - SQL PLSQL - Extraction step - Performance issue

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page troubleshoots performance issues you may face during a PL/SQL extraction.

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
CSS	✅

Step by Step Scenario

Run the DB extractor

Action Plan

Open the extractor log file
Check globally if the extraction rate is low : If they are lower than 1000 rows/s, this is a bad performance. You can focus on the Extracting: Oracle Tables… as below screenshot :

Source Extractor - SQL PLSQL - Fatal Error - Error in options Extraction - driver oracle jdbc OracleDriver - url

Mon, 01 Jan 0001 00:00:00 +0000

Problem Description

Upgrade CAST 7.0.18 to CAST 7.0.20.
Load the saved profile (XXX.properties) all data is loaded correctly.
Enter the password and run database extraction
Following error is encountered.

Error in options: Extraction -driver oracle.jdbc.OracleDriver -url jdbc:oracle:thin:@XXX:1521:XXX -user XYZ_user -password ********** -parameters schema=XX,YZ -target XXXX -l Z:\LOG\XXX

Info

This issue has been encountered in CAST version 7.0.20

Applicable in CAST Version

Release	Yes/No
8.2.x	❌
8.1.x	❌
8.0.x	❌
7.3.x	❌
7.2.x	❌
7.0.x	✅

Action Plan

Source Extractor - SQL PLSQL - Fatal Error - java.lang.ArrayIndexOutOfBoundsException

Mon, 01 Jan 0001 00:00:00 +0000

Description

After delivering an existing Oracle Extractor Output package in the DMT and setting it as Current Version on CMS ,the process stopped and the following error is found in extractionDB_log

2015-02-18 12:51:43.218 - Incomplete export: 244 extraction error(s)!
2015-02-18 12:52:52.860 - Read line feed error!
Error executing: Delivery -target C:.….\log.txt => java.lang.ArrayIndexOutOfBoundsException: 65533

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
CSS	✅

Step by Step Scenario

Source Extractor - SQL PLSQL - Fatal Error - java.lang.NegativeArraySizeException

Mon, 01 Jan 0001 00:00:00 +0000

Description

When running the CAST DB extractor on an Oracle 10g database, we come across the below error from the extraction log

com.castsoftware.util.logger.exceptions.LogException  cast.utilities.logger.subExecuteException:
com.castsoftware.util.logger.exceptions.LogException  cast.utilities.logger.subExecuteException
                at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
                at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
                at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
                at java.lang.reflect.Constructor.newInstance(Unknown Source)
                at java.lang.Class.newInstance(Unknown Source)
                at com.castsoftware.util.logger.exceptions.LogException.newInstance(LogException.java:79)
                at com.castsoftware.util.logger.exceptions.LogException.newInstance(LogException.java:118)
                at com.castsoftware.util.logger.Logging.execute(Logging.java:547)
                at com.castsoftware.util.logger.Logging.runInNewContext(Logging.java:415)
                at com.castsoftware.cli.GUIApplication$ApplicationRunner.run(GUIApplication.java:2642)
                at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NegativeArraySizeException
                at oracle.net.ano.CryptoNIONSDataChannel.readDataFromSocketChannel(Unknown Source)
                at oracle.jdbc.driver.T4CMAREngineNIO.prepareForReading(T4CMAREngineNIO.java:98)
                at oracle.jdbc.driver.T4CMAREngineNIO.unmarshalUB1(T4CMAREngineNIO.java:534)
                at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:485)
                at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:252)
                at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:612)
                at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:213)
                at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:37)
                at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:733)
                at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:904)
                at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1082)
                at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1276)
                at oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:366)
                at com.castsoftware.extractor.exporter.DatabaseIdentificationGroupExporter.executeQuery(DatabaseIdentificationGroupExporter.java:91)
                at com.castsoftware.extractor.exporter.IdentificationGroupExporter.executeQuery(IdentificationGroupExporter.java:370)
                at com.castsoftware.extractor.exporter.IdentificationGroupExporter.exportType(IdentificationGroupExporter.java:156)
                at com.castsoftware.extractor.exporter.IdentificationGroupExporter.run(IdentificationGroupExporter.java:71)
                at com.castsoftware.extractor.exporter.Exporter.exportSlice(Exporter.java:552)
                at com.castsoftware.extractor.exporter.Exporter.export(Exporter.java:375)
                at com.castsoftware.extractor.exporter.DatabaseExporter.exportServer(DatabaseExporter.java:517)
                at com.castsoftware.extractor.cli.DatabaseExtractor.process(DatabaseExtractor.java:510)
                at com.castsoftware.cli.GUIApplication$ApplicationRunner$2.call(GUIApplication.java:2648)
                at com.castsoftware.cli.GUIApplication$ApplicationRunner$2.call(GUIApplication.java:2643)
                at com.castsoftware.util.logger.Logging.execute(Logging.java:527)

Observed in CAST AIP

Source Extractor - SQL PLSQL - Fatal Error - Validation error -1 Schema your database to extract is missing

Mon, 01 Jan 0001 00:00:00 +0000

Description

This page will help you to solve issues related to the below error message that occurs during PL/SQL extraction :

2017-12-11 16:23:24.711 - Validation error #-1: Schema your_database_to_extract is missing

Observed in CAST AIP

Release	Yes/No
8.3.x	✅

Step by Step Scenario

Configure the PL/SQL source Extractor
Run the extraction

Action Plan

Check that the schemas that are configured exist
If the schema exist, check that the case is correct. The schema used should be in upper case.
If the above point do not help you, contact CAST Technical Support with Relevant Input.

Related Pages