Errors when executing DDL statements against MaxDB

Hi guys,
We are experiencing problems with DDL execution against MaxDB. I have installed version 7.8.00.17 on my 32-bit Windows XP XP3 machine. I got the following errors:
1. MaxDB complained that the "VARCHAR(8008)" data type has invalid length.
2. When fixing this, I got the problem, that a unique constraint has too long name.
3. After shortening this name, now I get the following:
u2190[4;35;1mSQL (0.0ms)u2190[0m u2190[0mActiveRecord::JDBCError: SAP DBTech JDBC: [-4006] (at 25): Unknown domain name:PRIMARY_KEY: CREATE TABLE photos (id primary_key, title varchar(8008), created_at timestamp, updated_at timestamp) u2190[0m
rake aborted!
All these DDL statements, are generated as part of a rake task execution (we are testing a simple Rails application, that uses persistence), and they execute fine on MySQL for instance. But on MaxDB it seems that there are more severe limitations about name lengths, data types, etc.
Could you please advice about this problem ?
Thanks and Kindest Regards,
Krum.

Hmm... what's wrong with the internet on your side, that you don't have access to the MaxDB documentation?
ad 1. You are using a UNICODE varchar, aren't you? check [here|http://maxdb.sap.com/doc/7_7/45/33337d9faf2b34e10000000a1553f7/frameset.htm] why it fails.
ad 2. Unique constraints don't get names in MaxDB [see here|http://maxdb.sap.com/doc/7_7/45/50fa4272c31796e10000000a1553f6/frameset.htm]
ad 3. You're simply using the wrong DDL format. "PRIMARY_KEY" is not even a MaxDB keyword.
I'm pretty sure you'll find the correct syntax for primary key definition yourself, by simply browsing the documentation, so I leave this to you now.
regards,
Lars

Similar Messages

Error when executing sql-statement

I get the following error:
select commodity_id from book where CONTAINS(review,'%a%')>0;
ORA-29902: error in executing ODCIIndexStart() routine
ORA-20000: interMedia Text error:
DRG-50937: query too complex
DRG-51030: wildcard query expansion resulted in too many terms
Does anywhone know what to do?
null

Originally posted by Sergey:
I get the following error:
select commodity_id from book where review like '%a%';
use it like this
Suresh
null

Error when executing statement for table/stored proc

Hi All,
 I am getting this error when executing IDOC to JDBC (Stored Procedure) Scenario.
 In my stored procedure I have three insert statements to insert rows in to 3 tables.
 This stored procedure is working fine for two insert statements i.e,
 For this I have created data type for stored procedure with 10 elements and executed the scenario and was successfully running.
 when I added 3rd insert statement to stored procedure ie., when i added 5 more elements to the datatype (totally 15 elements) it starts giving the bellow error in Message Monitoring.
Exception caught by adapter framework: Error processing request in sax parser: Error when executing statement for table/stored proc. 'COGRP_TMP_PROC_1' (structure 'Statements'): java.sql.SQLException: General error
Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'COGRP_TMP_PROC_1' (structure 'Statements'): java.sql.SQLException: General error
 Note:- I have run the stored procedure with three insert statements in Sql Server, and also by calling an external program also, and was working fine.
 Note : Is there any structure needs to be follow when working with IDOC to Stored procedure.
I am struck up with the error, can any body resolve this issue.
Thanks in Advance,
Murthy

Hi narasimha,
 This seems to be any error due to incorrect query formation.In your receiver jdbc channel set the parameter logSQLstatement = true.you can find this parameter in the advanced mode. Using this parameter you will be able to see the sql query which is generated at runtime in the audit log in RWB.
Regards,
Pragati

Error processing request in sax parser: Error when executing statement...

Hello,
I want to INSERT data from R/3 System to AS400 via JDBC adapter into a DB2 database. The interfaces from R/3 are Ok. but i have some problems to use the JDBC in DB2 Systems. The message in comunitation channel is:
" Error processing request in sax parser: Error when executing statement for table/stored proc. 'SPE106TST' (structure 'STATEMENT'): java.sql.SQLException: SPE106TST de SADMT1 no válido para la operación."
in the SXMB_MONI -> Request Message Mapping payloads this:
The connection to the database is fine, Sender adapter with a SELECT * works perfect.
Please Can anyone help me solve this problem? I'm lost.
Best regards,
Edited by: Nicola Occhipinti on May 22, 2008 7:40 PM

Hi Nicola,
This error occurs when the receiver side structure is incorrect.
Your structure seems to be correct.
Please use lower case for action, access and table.
Please check whether the field names are exactly the same as in the actual Database table sadmt1.SPE106TST.
Check if the table has permissions to write.
You can try an alternate structure without using table tag.
<ns0:MT_XMLSQL_SPEC xmlns:ns0="urn:damm.com/pi/EmployeeMasterData">
<STATEMENT>
<sadmt1.SPE106TST action="INSERT">
<access>
<CODEMP>D</CODEMP>
<CODPRO>00202339</CODPRO>
<NOMPRO>ROSIQUE PERALSGENIS</NOMPRO>
<DIRPRO>GIRONA</DIRPRO>
<POBPRO>S. VICENS HORTS</POBPRO>
<RUTA>0</RUTA>
<ORDEN>0</ORDEN>
<NOMINA>S</NOMINA>
</access>
</sadmt1.SPE106TST>
</STATEMENT>
</ns0:MT_XMLSQL_SPEC>
Hope your problem gets solved.
-Shamly

File to JDBC :Error when executing statement for table/stored proc.

Hi,
I am getting following error when i am trying to insert data into z-table using JDBC recr adapter.
Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'ZTEST' (structure 'STATEMENT'): java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Invalid object name 'ZTEST'.
But the database table name 'ZTEST' exists in the system.
XML structure:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_RECR xmlns:ns0="http://urn:srini/FileToJDBC">
 <STATEMENT>
 <TEST action="INSERT">
 <table>ZTEST</table>
 <access>
 <ROLLNO>123</ROLLNO>
 <FIRSTNAME>ABC</FIRSTNAME>
 <LASTNAME>XYZ</LASTNAME>
 </access>
 </TEST>
 </STATEMENT>
</ns0:MT_RECR>
Regards,
Srinivas

Hi,
I have changed my MT str but still getting the same error.Is it possible to insert/ update a z-table using JDBC adapter.
XML str:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_RECR xmlns:ns0="http://urn:srini/FileToJDBC">
 <STATEMENT>
 <ZTEST action="INSERT">
 <access>
 <ROLLNO>123</ROLLNO>
 <FIRSTNAME>abc</FIRSTNAME>
 <LASTNAME>XYZ</LASTNAME>
 </access>
 </ZTEST>
 </STATEMENT>
</ns0:MT_RECR>
Regards,
Srinivas

Error when executing statement for table/stored proc DB2 - Data Truncation

Hi,
I have one call sp in XI with n parameters int and two parameters out.
well, to implement the interface gives the following error
com.sap.aii.af.ra.ms.api.DeliveryException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'SPSAPAR9' (structure 'Statement'): java.sql.SQLException: The number of parameter values set or registered does not match the number of parameters
Thanks for your help
Ximena
Edited by: Ximena Gonzalez on Feb 19, 2008 11:50 AM
Edited by: Ximena Gonzalez on Feb 20, 2008 12:17 PM

My Error is change
Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'SAPPRG.SPSAPAR9' (structure 'Statement'): java.sql.DataTruncation: Data truncation
but de change DT SP
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:AlistReqDet2_MT xmlns:ns1="urn:proxl:tmuc:proxl01:AlistReqItems">
<Statement>
<SPSAPAR9 action="EXECUTE">
<table>SAPPRG.SPSAPAR9</table>
<ISAPNU1 isInput="TRUE" type="STRING">0080000353</ISAPNU1>
<ISAPEM1 isInput="TRUE" type="STRING">'LU'</ISAPEM1>
<ISAPC05 isInput="TRUE" type="STRING">15353</ISAPC05>
<ISAPSEC isInput="TRUE" type="STRING">10</ISAPSEC>
<ISAPLOT isInput="TRUE" type="STRING">'lats'</ISAPLOT>
<ISAPCA1 isInput="TRUE" type="STRING">10</ISAPCA1>
<ISAPCA2 isInput="TRUE" type="STRING">10</ISAPCA2>
<ISAPKIL isInput="TRUE" type="STRING">10</ISAPKIL>
<ISAPES1 isInput="TRUE" type="STRING">'T'</ISAPES1>
<ISAPSW isOutput="TRUE" type="STRING" />
</SPSAPAR9>
</Statement>
</ns1:AlistReqDet2_MT>

Error when executing statement for table/stored proc. : ORA-00911

Hi All,
I am posting IDOC->XI->JDBC, approx 5000 Idocs.
But few messages are giving following error in XI-_SXMB_MONI
Can any one guide me what is the cause of error? I check whole Idoc data I am not able to see bad character? can any once guide me what are the bad character in XML to post data in oracle? so that i can search in XML and how to avoide this error.
"com.sap.aii.af.ra.ms.api.MessagingException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'HRP1001' (structure 'INSERT_PAD34'): java.sql.SQLException: ORA-00911: invalid character"

> I am talking about following IDOC.<ZRMD_A06> ->
> <E1PLOGI SEGMENT="1">-> <E1PITYP SEGMENT="1"> ->
> <E1PAD34 SEGMENT="1"> -><PROZT>0.00 #</PROZT>.
> Can we remove this # during message mapping in XI??
sure you can remove it using Replace function or by writing UDF.
as I am seing # is last character..so remove # with " " (single space) and then use the TRIM fucntion.
Thanks
Farooq.
*Rewards points if you find it useful*

Why there is implicit commit before and after executing DDL Statements

Hi Guys,
Please let me know why there is implicit commit before and after executing DDL Statements ?
Regards,
sushmita

Helyos wrote:
This is because Oracle has design it like this.Come on Helyos, that's a bit of a weak answer. :)
The reason is that it makes no sense to update the structure of the database whilst there is outstanding data updates that have not been committed.
Imagine having a column that is VARCHAR2(50) that currently only has data that is up to 20 characters in size.
Someone (person A) decides that it would make sense to alter the table and reduce the size of the column to varchar2(20) instead.
Before they do that, someone else (person B) has inserted data that is 30 characters in size, but not yet committed it.
As far as person B is concerned that insert statement has been successful as they received no error, and they are continuing on with their process until they reach a suitable point to commit.
Person A then attempts to alter the database to make it varchar2(20).
If the database allowed that to happen then the column would be varchar2(20) and the uncommitted data would no longer fit, even though the insert was successful. When is Person B going to find out about this? It would be wrong to tell them when they try and commit, because all their transactions were successful, so why should a commit fail.
In this case, because it's two different people, then the database will recognise there is uncommitted transactions on that table and not let person B alter it.
If it was just one person doing both things in the same session, then the data would be automatically committed, the alter statement executed and the person informed that they can't alter the database because there is (now) data exceeding the size they want to set it to.
It makes perfect sense to have the database in a data consistent state before any alterations are made to it, hence why a commit is issued beforehand.
Here's something I wrote the other day on the subject...
DDL's issue a commit before carrying out the actual action
As long as the DDL is syntactically ok (i.e. the parser is happy with it) then the commit is issued, even if the actual DDL cannot be executed for another reason.
Example...
We have a table with some data in it...
SQL> create table xtest as select rownum rn from dual;
Table created.
SQL> select * from xtest;
        RN
         1We then delete the data but don't commit (demonstrated by the fact we can roll it back)
SQL> delete from xtest;
1 row deleted.
SQL> select * from xtest;
no rows selected
SQL> rollback;
Rollback complete.
SQL> select * from xtest;
        RN
         1
SQL> delete from xtest;
1 row deleted.
SQL> select * from xtest;
no rows selectedSo now our data is deleted, but not committed, what if we issue a DDL that is syntactically incorrect...
SQL> alter tab xtest blah;
alter tab xtest blah
ERROR at line 1:
ORA-00940: invalid ALTER command
SQL> rollback;
Rollback complete.
SQL> select * from xtest;
        RN
         1... the data can still be rolled back. This is because the parser was not happy with the syntax of the DDL statement.
So let's delete the data again, without committing it, and issue a DDL that is syntactically correct, but cannot execute for another reason (i.e. the database object it refers to doesn't exist)...
SQL> delete from xtest;
1 row deleted.
SQL> select * from xtest;
no rows selected
SQL> truncate table bob;
truncate table bob
ERROR at line 1:
ORA-00942: table or view does not exist
SQL> rollback;
Rollback complete.
SQL> select * from xtest;
no rows selectedSo, there we have it. Just because the statement was syntactically correct, the deletion of the data was committed, even though the DDL couldn't be performed.
This makes sense really, because if we are planning on altering the definition of the database where the data is stored, it can only really take place if the database is in a state where the data is where it should be rather than being in limbo. For example, imagine the confusion if you updated some data on a column and then altered that columns datatype to be a different size e.g. reducing a varchar2 column from 50 character down to 20 characters. If you had data that you'd just updated to larger than 20 characters whereas previously there wasn't, then the alter table command would not know about it, would alter the column size and then the data wouldn't be valid to fit whereas the update statement at the time didn't fail.
Example...
We have a table that only allows 20 characters in a column. If we try and insert more into that column we get an error for our insert statement as expected...
SQL> create table xtest (x varchar2(20));
Table created.
SQL> insert into xtest values ('012345678901234567890123456789');
insert into xtest values ('012345678901234567890123456789')
ERROR at line 1:
ORA-12899: value too large for column "SCOTT"."XTEST"."X" (actual: 30, maximum: 20)Now if our table allowed more characters our insert statement is successful. As far as our "application" goes we believe, nay, we have been told by the database, we have successfully inserted our data...
SQL> alter table xtest modify (x varchar2(50));
Table altered.
SQL> insert into xtest values ('012345678901234567890123456789');
1 row created.Now if we tried to alter our database column back to 20 characters and it didn't automatically commit the data beforehand then it would be happy to alter the column, but then when the data was committed it wouldn't fit. However the database has already told us that the data was inserted, so it can't go back on that now.
Instead we can see that the data is committed first because the alter command returns an error telling us that the data in the table is too big, and also we cannot rollback the insert after the attempted alter statement...
SQL> alter table xtest modify (x varchar2(20));
alter table xtest modify (x varchar2(20))
ERROR at line 1:
ORA-01441: cannot decrease column length because some value is too big
SQL> rollback;
Rollback complete.
SQL> select * from xtest;
X
012345678901234567890123456789
SQL>Obviously, because a commit statement is for the existing session, if we had tried to alter the table column from another session we would have got
SQL> alter table xtest modify (x varchar2(20));
alter table xtest modify (x varchar2(20))
ERROR at line 1:
ORA-00054: resource busy and acquire with NOWAIT specified
SQL>... which is basically saying that we can't alter the table because someone else is using it and they haven't committed their data yet.
Once the other session has committed the data we get the expected error...
ORA-01441: cannot decrease column length because some value is too bigHope that explains it

Error when executing interface which load data from csv file which has 320

Hi,
Can some one provide a resolution for below error:
I have created an interface which load data from csv file which has 320 columns, to a Synonym which has 320 columns in it
using LKM File to SQL, IKM Sql Control Append.
I am getting below error when executing the interface :
com.sunopsis.tools.core.exception.SnpsSimpleMessageException: ODI-17517: Error during task interpretation. Task: 6 java.lang.Exception: BeanShell script error: Sourced file: inline evaluation of: ``out.print("The application script threw an exception: java.lang.StringIndexOutOf . . . '' Token Parsing Error: Lexical error at line 2, column 42. Encountered: "\\" (92), after : "": <at unknown location> BSF info: Create external table at line: 0 column: columnNo
at com.sunopsis.dwg.codeinterpretor.SnpCodeInterpretor.transform(SnpCodeInterpretor.java:485)
 at com.sunopsis.dwg.dbobj.SnpSessStep.createTaskLogs(SnpSessStep.java:711)
 at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:461)
 at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2093)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:366)
 at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:300)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:292)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:855)
 at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:126)
 at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
 at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.bsf.BSFException: BeanShell script error: Sourced file: inline evaluation of: ``out.print("The application script threw an exception: java.lang.StringIndexOutOf . . . '' Token Parsing Error: Lexical error at line 2, column 42. Encountered: "\\" (92), after : "": <at unknown location>
BSF info: Create external table at line: 0 column: columnNo
 at bsh.util.BeanShellBSFEngine.eval(Unknown Source)
 at bsh.util.BeanShellBSFEngine.exec(Unknown Source)
 at com.sunopsis.dwg.codeinterpretor.SnpCodeInterpretor.transform(SnpCodeInterpretor.java:471)
 ... 11 more
Text: The application script threw an exception: java.lang.StringIndexOutOfBoundsException: String index out of range: 2 BSF info: Create external table at line: 0 column: columnNo
out.print("createTblCmd = r\"\"\"\ncreate table ") ;
out.print(odiRef.getTable("L", "COLL_NAME", "W")) ;
out.print("<?=(extTabColFormat.getUseView())?\"_ET\":\"\"?>\n(\n\t") ;
out.print(odiRef.getColList("", "[CX_COL_NAME]\\t"+
 "<?=extTabColFormat.getExtTabDataType(\\u0022[CX_COL_NAME]\\u0022,\\u0022[SOURCE_DT]\\u0022, \\u0022[DEST_WRI_DT]\\u0022, \\u0022[COL_FORMAT]\\u0022, \\u0022[BYTES]\\u0022, \\u0022[LONGC]\\u0022, \\u0022[SCALE]\\u0022)?>"
 , ",\\n\\t", "","")) ;
out.print("\n)\nORGANIZATION EXTERNAL\n(\n\tTYPE ORACLE_LOADER\n\tDEFAULT DIRECTORY dat_dir\n\tACCESS PARAMETERS\n\t(\n\t\tRECORDS DELIMITED BY 0x'") ;
out.print(odiRef.getSrcTablesList("[XFILE_SEP_ROW]","")) ;
out.print("'\n\t\t") ;
out.print(odiRef.getUserExit("EXT_CHARACTERSET")) ;
out.print("\n\t\t") ;
out.print(odiRef.getUserExit("EXT_STRING_SIZE")) ;
out.print("\n\t\tBADFILE\t\t'") ;
out.print(odiRef.getSrcTablesList("", "[RES_NAME]", "", "")) ;
out.print("_%a.bad'\n\t\tLOGFILE\t\t'") ;
out.print(odiRef.getSrcTablesList("", "[RES_NAME]", "", "")) ;
out.print("_%a.log'\n\t\tDISCARDFILE\t'") ;
out.print(odiRef.getSrcTablesList("", "[RES_NAME]", "", "")) ;
out.print("_%a.dsc'\n\t\tSKIP \t\t") ;
out.print(odiRef.getSrcTablesList("", "[FILE_FIRST_ROW]", "", "")) ;
out.print("\n") ;
if (odiRef.getSrcTablesList("", "[FILE_FORMAT]", "", "").equals("F")) {out.print("\n\t\tFIELDS\n\t\t") ;
out.print(odiRef.getUserExit("EXT_MISSING_FIELD")) ;
out.print("\n\t\t(\n\t\t\t") ;
out.print(odiRef.getColList("", "[CX_COL_NAME]\\tPOSITION([FILE_POS]:[FILE_END_POS])\\t"+
 "<?=extTabColFormat.getExtTabFormat(\\u0022[CX_COL_NAME]\\u0022,\\u0022[SOURCE_DT]\\u0022, \\u0022DEST_WRI_DT\\u0022, \\u0022[COL_FORMAT]\\u0022, \\u0022[BYTES]\\u0022, \\u0022[LONGC]\\u0022, \\u0022[SCALE]\\u0022)?>"
 , ",\\n\\t\\t\\t", "","")) ;
out.print("\t\t\n\t\t)\n\t)\n") ;
} else {out.print("\n\t\tFIELDS TERMINATED BY x'") ;
out.print(odiRef.getSrcTablesList("", "[XFILE_SEP_FIELD]", "", "")) ;
out.print("'\n\t\t") ;
if(odiRef.getSrcTablesList("", "[FILE_ENC_FIELD]", "", "").equals("")){out.print("\n\t\t") ;
} else {out.print("OPTIONALLY ENCLOSED BY '") ;
out.print(odiRef.getSrcTablesList("", "[FILE_ENC_FIELD]", "", "").substring(0,1)) ;
out.print("' AND '") ;
out.print(odiRef.getSrcTablesList("", "[FILE_ENC_FIELD]", "", "").substring(1,2)) ;
out.print("' ") ;
}out.print("\n\t\t") ;
out.print(odiRef.getUserExit("EXT_MISSING_FIELD")) ;
out.print("\n\t\t(\n\t\t\t") ;
out.print(odiRef.getColList("", "[CX_COL_NAME]\\t"+
 "<?=extTabColFormat.getExtTabFormat(\\u0022[CX_COL_NAME]\\u0022,\\u0022[SOURCE_DT]\\u0022, \\u0022DEST_WRI_DT\\u0022, \\u0022[COL_FORMAT]\\u0022, \\u0022[BYTES]\\u0022, \\u0022[LONGC]\\u0022, \\u0022[SCALE]\\u0022)?>"
 , ",\\n\\t\\t\\t", "","")) ;
out.print("\t\t\n\t\t)\n\t)\n") ;
}out.print("\tLOCATION (") ;
out.print(odiRef.getSrcTablesList("", "'[RES_NAME]'", "", "")) ;
out.print(")\n)\n") ;
out.print(odiRef.getUserExit("EXT_PARALLEL")) ;
out.print("\nREJECT LIMIT ") ;
out.print(odiRef.getUserExit("EXT_REJECT_LIMIT")) ;
out.print("\n\"\"\"\n \n# Create the statement\nmyStmt = myCon.createStatement()\n \n# Execute the trigger creation\nmyStmt.execute(createTblCmd)\n \nmyStmt.close()\nmyStmt = None\n \n# Commit, just in case\nmyCon.commit()") ;
****** ORIGINAL TEXT ******
createTblCmd = r"""
create table <%=odiRef.getTable("L", "COLL_NAME", "W")%><?=(extTabColFormat.getUseView())?"_ET":""?>
 <%=odiRef.getColList("", "[CX_COL_NAME]\t"+
 "<?=extTabColFormat.getExtTabDataType(\u0022[CX_COL_NAME]\u0022,\u0022[SOURCE_DT]\u0022, \u0022[DEST_WRI_DT]\u0022, \u0022[COL_FORMAT]\u0022, \u0022[BYTES]\u0022, \u0022[LONGC]\u0022, \u0022[SCALE]\u0022)?>"
 , ",\n\t", "","")%>
ORGANIZATION EXTERNAL
 TYPE ORACLE_LOADER
 DEFAULT DIRECTORY dat_dir
 ACCESS PARAMETERS
 RECORDS DELIMITED BY 0x'<%=odiRef.getSrcTablesList("[XFILE_SEP_ROW]","")%>'
 <%=odiRef.getUserExit("EXT_CHARACTERSET")%>
 <%=odiRef.getUserExit("EXT_STRING_SIZE")%>
 BADFILE '<%=odiRef.getSrcTablesList("", "[RES_NAME]", "", "")%>_%a.bad'
 LOGFILE '<%=odiRef.getSrcTablesList("", "[RES_NAME]", "", "")%>_%a.log'
 DISCARDFILE '<%=odiRef.getSrcTablesList("", "[RES_NAME]", "", "")%>_%a.dsc'
 SKIP <%=odiRef.getSrcTablesList("", "[FILE_FIRST_ROW]", "", "")%>
<% if (odiRef.getSrcTablesList("", "[FILE_FORMAT]", "", "").equals("F")) {%>
 FIELDS
 <%=odiRef.getUserExit("EXT_MISSING_FIELD")%>
 <%=odiRef.getColList("", "[CX_COL_NAME]\tPOSITION([FILE_POS]:[FILE_END_POS])\t"+
 "<?=extTabColFormat.getExtTabFormat(\u0022[CX_COL_NAME]\u0022,\u0022[SOURCE_DT]\u0022, \u0022DEST_WRI_DT\u0022, \u0022[COL_FORMAT]\u0022, \u0022[BYTES]\u0022, \u0022[LONGC]\u0022, \u0022[SCALE]\u0022)?>"
 , ",\n\t\t\t", "","")%>
<%} else {%>
 FIELDS TERMINATED BY x'<%=odiRef.getSrcTablesList("", "[XFILE_SEP_FIELD]", "", "")%>'
 <% if(odiRef.getSrcTablesList("", "[FILE_ENC_FIELD]", "", "").equals("")){%>
 <%} else {%>OPTIONALLY ENCLOSED BY '<%=odiRef.getSrcTablesList("", "[FILE_ENC_FIELD]", "", "").substring(0,1)%>' AND '<%=odiRef.getSrcTablesList("", "[FILE_ENC_FIELD]", "", "").substring(1,2)%>' <%}%>
 <%=odiRef.getUserExit("EXT_MISSING_FIELD")%>
 <%=odiRef.getColList("", "[CX_COL_NAME]\t"+
 "<?=extTabColFormat.getExtTabFormat(\u0022[CX_COL_NAME]\u0022,\u0022[SOURCE_DT]\u0022, \u0022DEST_WRI_DT\u0022, \u0022[COL_FORMAT]\u0022, \u0022[BYTES]\u0022, \u0022[LONGC]\u0022, \u0022[SCALE]\u0022)?>"
 , ",\n\t\t\t", "","")%>
<%}%> LOCATION (<%=odiRef.getSrcTablesList("", "'[RES_NAME]'", "", "")%>)
<%=odiRef.getUserExit("EXT_PARALLEL")%>
REJECT LIMIT <%=odiRef.getUserExit("EXT_REJECT_LIMIT")%>
# Create the statement
myStmt = myCon.createStatement()
# Execute the trigger creation
myStmt.execute(createTblCmd)
myStmt.close()
myStmt = None
# Commit, just in case
myCon.commit().
 at com.sunopsis.dwg.dbobj.SnpSessStep.createTaskLogs(SnpSessStep.java:738)
 at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:461)
 at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2093)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:366)
 at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:300)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:292)
 at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:855)
 at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:126)
 at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82)
 at java.lang.Thread.run(Thread.java:662)

The issue is encountered because the text delimiter used in the source file did not consist of a pair of delimiters.
Please see support Note [ID 1469977.1] for details.

ORA-20000 error when executing background jobs in BI System

Hello Experts,
We newly installed NW2004s System. Few BI related background jobs are showing Error no: 4 or Error no: 3 in SM50. Also few BI related background jobs are giving error "ORA-20000 occurred when executing SQL statement (parse error offset=0)". Please let me know what does Error 4 or 3 mean in SM50 and how to resolve Ora-20000 error?
Thanks

This may be to do with insufficient authorization for the user (for creating statistics for example). Check OSS note 963760.

Error when executing query without passing variable selection

Hi Gurus
I am getting an error while executing a query with out passing values for variables
When executing the query by passing the filter values report returns the data
When executing the query with out passing variable selections the error message is
Unknown error in SQL interface
Error reading the data of Info Provider ZCRM_O08
Error while reading data; navigation possible
System error in program SSAPLRS_EXCEPTION and form
RS_EXCEPTION_TO_MESSAGE
No Data Available
can any one please help me in resolving this
Thank you

Hi Srini
Thanks for your quick response
When i am executing the query with selection it is returning the data
giving error when executing with out passing the selection
is there any other cause for this problem
like any particular info object causes this sort of problem
Thank you

Webi report throwing error when executed

HI Experts,
While executing a Webi Report we are gettign following error when executing with more than one characteristics -
A Database error occured. The database eror text is : The MDX Query select { [Measures].[4225B1TBMEMOYKZGDKLVINMAW] } ON COLUMNS FROM [ZMEPSC01/ZMEPSC01_QRY_0001]
failed to execute with the error Unknown error.(WIS 10901).
We tried changing the Universe -> Parameter -> Control -> Limit size of result set to -> unchecked it.
But still the error remains. Can u put some light over it.
Thanks.

Hello ,
Just Check with the BI the people they might change the the column name or some thing else in the bex Query that s way It is showing error.
Refresh the universe and generate the report then check it.
Thanks
Santhosh V

Error when executing a .irpt page

Hi,
I am getting the below error when executing a .irpt from the workbench. I am on MII 12.2.2 Build (235).
404 Not Found
SAP NetWeaver Application Server 7.20 / AS Java 7.30
Error: S:usrsapALXJ10j2eeclusterappssap.comxappsxmiiearservlet_jspXMII
oot/XMII/CM/<Project>/<File.irpt>
Troubleshooting Guide https://sdn.sap.com/irj/sdn/wiki?path=/display/jstsg/home
Details: No details available.
Please share your thoughts on this.
Regards,
Chanti.

Hi Chanti,
This sounds obvious, but check to make sure your irpt page has the extension .irpt in the workbench. Depending on how you saved it, it might have been dropped.
Also make sure the page is published by either saving it to web:// (not db://) or by right clicking and selecting Publish.
Regards,
Mike

Runtime error when executing ME2B/ME3B if condition recs 160

Dear all,
I have created a vendor rebate agreement and entered condition records for a vendor/material combination.
Since for this vendor there are 170 materials for which he provides rebate I have created 170 condition records.
When I am trying to change or display the rebate agreement by executing transaction codes ME2B and ME3B respectively the following run time error occurs (Runtime error when executing transaction codes ME2B/ME3B for condition recrds >160):
Runtime Errors: DBIF_RSQL_INVALID_RSQL
Except. CX_SY_OPEN_SQL_DB
The error is in function module SELECT_TEXT at line 120 "select * from stxh client specified into table stxh_buffer".
When I debug or test/execute the function module SELECT_TEXT, I find that there are no relevant entries in table STXH for the vendor rebate agreements.
Please note that if the condition records of the rebate agreement are 160 and less then there is no problem.
I would appreciate if I could have your expert oppinion on what is causing this runtime error and if it is possible on how to resolve it.
Thanks in advance.
Regards,
Mimis
Edited by: Mimis1973 on Jan 26, 2011 11:18 AM
Edited by: Mimis1973 on Jan 26, 2011 11:20 AM
Edited by: Mimis1973 on Jan 26, 2011 11:23 AM

There's something similar in OSS note 1002788. Is it relevant to your system?

Error when executing DBMS_ERRLOG through Stored Procedures...

Hi,
We have TWO schemas like IDWH_ODS and IDWH_ERR running on Oracle 10g Rel.2.
The schema IDWH_ERR has direct SELECT privilege on all the base tables in IDWH_ODS schema. (As Pl/sql doesn't support ROLE, we have granted direct SELECT on each of the tables)
IDWH_ODS schema has tables like ACCOUNT & CUSTOMER, for which I need to create DML Error logging tables in IDWH_ERR schema.
I have one procedure 'Cr_Errlog_Tabs' in IDWH_ERR schema which gets all tables in IDWH_ODS and creates Error logging table in IDWH_ERR schema using DBMS_ERRLOG package. My problem starts here,
When I execute the DBMS_ERRLOG package in IDWH_ERR through SQL*Plus LIKE,
> exec DBMS_ERRLOG.CREATE_ERROR_LOG('idwh_ods.ACCOUNT','ERR$_ACCOUNT','idwh_err');
it's creating the error log table 'ERR$_ACCOUNT' in IDWH_ERR schema.
(...the same will be working when execute through Anonymous plsql block)
BUT, when i execute the DBMS_ERRLOG package with same parameters through the stored Procedure 'Cr_Errlog_Tabs', it throws the following error...
ORA-01031: insufficient privileges
Please let me know how the solution at the earliest.

WHY DO YOU FEEL YOU HAVE TO START A NEW THREAD FOR YOUR PROBLEM!?
Insufficient priv error when executing DBMS_ERRLOG through PLSQL

Errors when executing DDL statements against MaxDB

Similar Messages

Maybe you are looking for