ODI 10.1.3.5 - Text file to Hyperion Essbase - Metadata

Question

Hello folks,
I tried to insert new member on my outline in Essbase 9.3.1 using the following text file content:
Member;Parent;Alias;Consolidation;Data Storage
A;Account;A-Test;+;Never Share
Follow the error description below, but I could not understand the issue´s cause.
When I use the same text file to load Hyperion Planning, it works fine.
org.apache.bsf.BSFException: exception from Jython:
Traceback (innermost last):
File "<string>", line 20, in ?
java.sql.SQLException: Unexpected token: PARENTNAME in statement [select   C3_PARENT    ""ParentName]
Does somebody know what happened?
Best Regards,
Wallace Galvão
Sao Paulo - Brazil

Answer 1

Hello John,
I don´t have quotes on the column separator or table alias separator field. But I found the quotes on the language tab in object delimiter field, I removed and I have new error, follow below.
File "<string>", line 23, in ?
com.hyperion.odi.essbase.ODIEssbaseException: Cannot build dimension. Analytic Server Error(1030011): Invalid character in name (<Default>) in ESSAPI function adBuildDim
SQL Generated:
from com.hyperion.odi.common import ODIConstants
from com.hyperion.odi.connection import HypAppConnectionFactory
from java.lang import Class
from java.lang import Boolean
from java.sql import *
from java.util import HashMap
# Get the select statement on the staging area:
sql= """select C2_PARENT "ParentName",C3_MEMBER "MemberName",C1_ALIAS "Alias",C4_DATA_STORAGE "DataStorage",C5_CONSOLIDATION "Consolidation" from "C$_0Account" where      (1=1) """
srcCx = odiRef.getJDBCConnection("SRC")
stmt = srcCx.createStatement()
srcFetchSize=30
stmt.setFetchSize(srcFetchSize)
rs = stmt.executeQuery(sql)
#load the data
stats = pWriter.loadData(rs)
#close the database result set, connection
rs.close()
stmt.close()
Besides, for me it was strange found two languages defined on Essbase technology: Jython and SQL. And the definition tab, Tecnology type was: database or file (JDBC/ODBC), I changed to "bean script framework" (similar to Hyperion Planning technology) and removed the SQL keeping only Jython, but the issues continues.
Also, I changed my odihapp_essbase.jar (date created 9/9/2009) and readded the essbase technology, but without success.
Do you have any idea to solve this issue?
Regards,
Wallace Galvão
Sao Paulo - Brazil