My Oracle Support Banner

"JNPE at oracle.odi.domain.mapping.generator.GeneratorContext.getAPNodeSourceViewAccessName" Executing Mapping Using "LKM Oracle to Oracle Pull (DB Link)" (Doc ID 2649205.1)

Last updated on MAY 15, 2020

Applies to:

Oracle Data Integrator - Version 12.2.1.4.0 to 12.2.1.4.200304 [Release 12c]
Information in this document applies to any platform.

Symptoms

Oracle Data Integrator (ODI) mappings that are loading data between two Oracle Database servers using the "LKM Oracle to Oracle Pull (DB Link)" knowledge modules are failing at execution time (or in simulation mode) with the following error in ODI Studio: 

JNPE at oracle.odi.domain.mapping.generator.GeneratorContext.getAPNodeSourceViewAccessName(GeneratorContext.java:322)
Please check the Validation Results window for more information

At the same time, following error is seen in studio.log:

[2020-02-03T08:19:50.040+00:00] [odi] [NOTIFICATION] [] [oracle.odi.mapping] Start generation of map physical design: MapPhysicalDesign <MAPPING_NAME>.Physical
[2020-02-03T08:19:51.710+00:00] [odi] [NOTIFICATION] [] [oracle.odi.util.serialization.SerializationLibrary] serializationLibrary initialized
[2020-02-03T08:19:53.786+00:00] [odi] [WARNING] [] [oracle.odi.mapping] java.lang.NullPointerException[[
    at oracle.odi.domain.mapping.generator.GeneratorContext.getAPNodeSourceViewAccessName(GeneratorContext.java:322)
    at oracle.odi.domain.mapping.generator.GeneratorContext$getAPNodeSourceViewAccessName$0.call(Unknown Source)
    at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
    at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:128)
    at LKM_Oracle_to_Oracle_DB_Link.setBinding(LKM_Oracle_to_Oracle_DB_Link_create_class.groovy:33)
    at oracle.odi.domain.mapping.generator.GroovyComponentGeneratorDelegateBase.generateComponent(GroovyComponentGeneratorDelegateBase.java:50)
    at oracle.odi.domain.mapping.generator.MapComponentGenerator.generateComponent(MapComponentGenerator.java:259)
    at oracle.odi.domain.mapping.generator.MapComponentGenerator.generateComponent(MapComponentGenerator.java:146)
    at oracle.odi.domain.mapping.generator.MappingGenerator.generateTarget(MappingGenerator.java:2593)
    at oracle.odi.domain.mapping.generator.MappingGenerator.getEKMUsageList(MappingGenerator.java:2142)
    at oracle.odi.domain.mapping.generator.MappingGenerator.generateExecutableDetails(MappingGenerator.java:734)
    at oracle.odi.domain.mapping.generator.MappingGenerator.generateSession(MappingGenerator.java:372)
    at oracle.odi.domain.mapping.generator.MappingGenerator.generateSession(MappingGenerator.java:331)
    at oracle.odi.ui.mapping.MappingExecutionDialog$1.doInTransaction(MappingExecutionDialog.java:336)
    at oracle.odi.core.persistence.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:100)
    at oracle.odi.ui.mapping.MappingExecutionDialog.doExecution(MappingExecutionDialog.java:331)
    ...
]]

The mapping shows as successful through the mapping validator.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.