XSD-2028: (error) Invalid Reference

I'm getting a number of these being generated when I attempt to load a schema via the build(0 method of XMLSchema.
The schema validates ok in other products.
What is the explanation of this error? Are there any known problems related to it?
Thanks

This error only happen if any kind of reference in your XML Schema can't be resolved by Schema processor.
Please check your schema file. If you think your schema is OK. Please send the Schema file and we will have a test on it.

Similar Messages

Error:Invalid reference to variable 'PARTS1.PNUM%TYPE' - how to resolve

error:
ERROR at line 29:
ORA-06550: line 29, column 39:
PLS-00487: Invalid reference to variable 'PARTS1.PNUM%TYPE'
ORA-06550: line 29, column 4:
PL/SQL: SQL Statement ignored
DECLARE
cursor c1 is select pnum from parts1;
TYPE NumTab IS TABLE OF parts1.pnum%TYPE INDEX BY PLS_INTEGER;
TYPE NumTab1 IS TABLE OF parts1.pnum%TYPE INDEX BY PLS_INTEGER;
--TYPE NameTab IS TABLE OF parts1.pname%TYPE INDEX BY PLS_INTEGER;
pnums NumTab;
pnums1 NumTab1;
-- pnames NameTab;
--iterations CONSTANT PLS_INTEGER := 500;
t1 INTEGER;
t2 INTEGER;
t3 INTEGER;
l_num_index integer := 0;
BEGIN
FOR j IN 1..50000 LOOP -- load index-by tables
insert into parts1 values(j);
END LOOP;
commit;
t1 := DBMS_UTILITY.get_time;
/* FOR i IN 1..iterations LOOP -- use FOR loop
INSERT INTO parts1 VALUES (pnums(i));
END LOOP;
select pnum bulk collect into pnums from parts1;
t2 := DBMS_UTILITY.get_time;
open c1;
loop
l_num_index := l_num_index + 1;
fetch c1 into pnums1(l_num_index).pnum;
EXIT WHEN c1%notfound;
end loop;
close c1;
t3 := DBMS_UTILITY.get_time;
DBMS_OUTPUT.PUT_LINE('Execution Time (secs)');
DBMS_OUTPUT.PUT_LINE('---------------------');
DBMS_OUTPUT.PUT_LINE('FOR loop: ' || TO_CHAR((t2 - t1)/100));
DBMS_OUTPUT.PUT_LINE('FORALL: ' || TO_CHAR((t3 - t2)/100));
COMMIT;
END;
thanks,
vinodh

The line number in the error message is nearly always a good clue.
fetch c1 into pnums1(l_num_index).pnum;should be
fetch c1 into pnums1(l_num_index);

Had Lion 10.7.3 and spctl enabled, after upgrading to 10.7.4 i got this error message: 'error: invalid API object reference'

I had Lion 10.7.3 with spctl enabled, few days ago i had thru Software Updates > Upgrade to 10.7.4; i upgraded but this time when im trying to install an program i have the message that producer is not signed or software was from AppleStore so i tried to disable on Terminal, but i got this message:
'error: invalid API object reference'
i guess now i cant install anything because either i want to enable or disable the result is the same.

I have this same trouble with an IMac, was also 10.7.3 with spctl enabled, and after upgraded to 10.7.4, i cant install anything.

Error 1026 invalid reference at runVI invoke method in main exe- subVI- subpanel

Hello,
I have a main VI which have subVI's inside case structures set up to show FP when called and be modal.
These subVIs have a subpanel that will pull up a dynamicVI using RunVI invoke method.The dymaicVIs path is built using application directory constant+the VI name to the invoke method.
now the main VI is built into exe with the dynamicVIs in always included list.
when i run the main exe i am getting 1026 error VI reference invalid.
Plz help
Thanks
Solved!
Go to Solution.

Hi Freemason,
The problem could be coming from the use of relative paths, because the path can sometimes change when building an application. Double check to make sure they are calling the right path. You can also try changing the AutoDispose Refnum in your run VI invoke node to false. It is one of the methods you can select in your run VI invoke node. If neither of these solutions work, run your code using the highlight execution function. If you implemented error handling in your program, you should be able to see the source of the error.
If you’re still having issues, could you post some screenshots or your actual VI? I may be able to get a better idea of the issue that way. I’ve also attached an example VI that uses multiple subVIs and a subpanel for reference. Hope this helps.
Paul C
Applications Engineer
National Instruments
Attachments:
Multiple VIs in a Subpanel.vi ‏19 KB

Can SOA 11g fault policy handle XSD Validation errors from the Mediator?

I would like all errors in my SOA process to go through the fault-policies.xml. But I don't seem to be able to catch any mediator error caused by an XSD validation failure. A sample of the sort of error I am trying to 'catch' is:
Nonrecoverable System Fault          oracle.tip.mediator.infra.exception.MediatorException: ORAMED-01303:[Payload default schema validation error]XSD schema validation fails with error Invalid text 'A' in element: 'TermCode'Possible Fix:Fix payload and resubmit.
My fault-policies.xml file is as follows:
<?xml version="1.0" encoding="UTF-8" ?>
<faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy">
<faultPolicy version="2.0.1"
     id="NewStudentRegistrationFaults"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Conditions>
<faultName xmlns:medns="http://schemas.oracle.com/mediator/faults" name="medns:1303">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
<faultName xmlns:rjm="http://schemas.oracle.com/sca/rejectedmessages" name="rjm:GetNewStudentRegistrationFile">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
<faultName xmlns:medns="http://schemas.oracle.com/mediator/faults" name="medns:TYPE_ALL">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:mediatorException">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:bindingFault">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:remoteFault">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
</Conditions>
<Actions>
<Action id="java-fault-handler">
<javaAction className="edu.villanova.soa.handlers.FaultNotificationHandler"
defaultAction="ora-human-intervention" propertySet="faultNotificationProps">
<returnValue value="OK" ref="ora-human-intervention"/>
</javaAction>
</Action>

<Action id="ora-human-intervention">
<humanIntervention/>
</Action>

<Action id="ora-terminate">
<abort/>
</Action>
</Actions>

<Properties>

<propertySet name="faultNotificationProps">
<property name="from">[email protected]</property>
<property name="to">[email protected]</property>
<property name="subject">Reporting a SOA fault</property>
</propertySet>
</Properties>
</faultPolicy>
<faultPolicy version="2.0.1"
     id="MediatorFaults"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Conditions>
<faultName xmlns:medns="http://schemas.oracle.com/mediator/faults" name="medns:1303">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
</Conditions>
<Actions>
<Action id="java-fault-handler">
<javaAction className="edu.villanova.soa.handlers.FaultNotificationHandler"
defaultAction="ora-human-intervention" propertySet="faultNotificationProps">
<returnValue value="OK" ref="ora-human-intervention"/>
</javaAction>
</Action>

<Action id="ora-human-intervention">
<humanIntervention/>
</Action>

<Action id="ora-terminate">
<abort/>
</Action>
</Actions>

<Properties>

<propertySet name="faultNotificationProps">
<property name="from">[email protected]</property>
<property name="to">[email protected]</property>
<property name="subject">Reporting a SOA rejected msg. fault</property>
</propertySet>
</Properties>
</faultPolicy>
</faultPolicies>
My fault-bindings.xml file is as follows:
<?xml version="1.0" encoding="UTF-8" ?>
<faultPolicyBindings version="2.0.1"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<composite faultPolicy="NewStudentRegistrationFaults"/>
<component faultPolicy="MediatorFaults">
<name>NewStudentRegistrationMediator</name>
</component>
<service faultPolicy="NewStudentRegistrationFaults">
<name>GetNewStudentRegistrationFile</name>
</service>
</faultPolicyBindings>
You'll notice that I've tried a number of ways (and various other combinations) to try to steer the error above into my Java fault handler but nothing has meet with success. The mplan is as follows:
<?xml version = '1.0' encoding = 'UTF-8'?>

<Mediator name="NewStudentRegistationMediator" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://xmlns.oracle.com/sca/1.0/mediator"
wsdlTargetNamespace="http://xmlns.oracle.com/pcbpel/adapter/ftp/Experiments/NewStudentRegistration/GetNewStudentRegistrationFile%2F">
<operation name="Get" deliveryPolicy="AllOrNothing" priority="4"
validateSchema="true">
<switch>
<case executionType="queued" name="RegToBanner.insert_2">
<action>
<transform>
<part name="$out.NewstudentregistrationCollection"
function="xslt(xsl/NewStudentRegistration_To_NewstudentregistrationCollection.xsl, $in.body)"/>
</transform>
<invoke reference="RegToBanner" operation="insert"/>
</action>
</case>
</switch>
</operation>
</Mediator>
I'm a newbie to Oracle SOA. So perhaps I am missing the obvious. But I haven't read much in the documentation specifically about using the XSD validation option on the mediator and have seen nothing specifically about catching this sort of exception in the fault policy (apart from the faults I already have in my policy). Can anyone suggest what I am doing incorrectly here or perhaps whether what I am attempting to do is not possible? Thanks.
- Cris

Has anyone got it working yet?
In my case, I have the following sequence:
FileAdapter -> Mediator1 -> Mediator2->DB Adapter
I am deliberately introducing validation error in File. Isn't it correct to assume Fault framework would get triggered at Mediator1 level since we are invoking FileAdapter service?
I am getting a strange behaviour. If I enable XSD validation at Mediator1 level, process is Faulted with no re-try option. However, if I enable XSD validation ONLY at Mediator2 level, I get Recoverable fault. There seems to be some disconnect between documentation and reality. I am using JDeveloper 11.1.1.3.0 version and SOA Suite 11g.
Thanks,
Amjad.

XMLTRANSORM - LPX-00607: Invalid reference - xsl:variable

Hi,
I'm working on Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit.
I have a problem using XMLTRANSFORM method with variable (ie. SenderDN).
There is a table "ma_table" with three columns : "id", "data_xml" and "data_xsl".
Here is the query used :
SELECT XMLTRANSFORM (data_xml, data_xsl) FROM ma_table WHERE id = 64;Here is the data to transform :
<?xml version="1.0" encoding="ISO-8859-1"?>
<SOSTA xmlns="http://www.xxxxxx.com/yyyy/pipo">
     <infos>
          <generated>2009-08-19T16:23:56</generated>
          <reference_tech>ABCD123456789</reference_tech>
     </infos>
     <RECEDEP>AAAAAAAA</RECEDEP>
     <SENDERM>BBB</SENDERM>
     <REFSEND>5100161753</REFSEND>
     <QUALIFI>N</QUALIFI>
     <REFINTE>0010000934487</REFINTE>
     <TYPSTAT>IPRC</TYPSTAT>
     <STAREMT>REJT</STAREMT>
     <RAISON>DSEC</RAISON>
     <NARRA>blablabla</NARRA>
     <NARRA1>blablabla</NARRA1>
     <NARRA2/>
     <CENTRDT>20090819</CENTRDT>
     <STTLMDT>00000000</STTLMDT>
     <TYPSORA>SOU</TYPSORA>
     <INDMONT>O</INDMONT>
     <QUANTFI/>
     <SEAMMNT>10941,19</SEAMMNT>
     <CLIEDEV>EUR</CLIEDEV>
     <IFICODI>EEEEEEEEEE</IFICODI>
     <IFILIBE/>
     <IDCPTIT>123456789456132</IDCPTIT>
     <routage>
          <feuille name="tagada">
               <Destinataire>dest</Destinataire>
               <Priority>Normal</Priority>
               <IsNotificationRequested>false</IsNotificationRequested>
               <Service>dervice</Service>
          </feuille>
     </routage>
</SOSTA>And here is the stylesheet :
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"
     xmlns:yyyy="http://www.xxxxxx.com/yyyy/pipo">
     <xsl:output method="xml" encoding="UTF-8" indent="yes"/>
     <xsl:variable name="SenderDN">sender dn</xsl:variable>
     <xsl:variable name="SenderBIC8">bic height</xsl:variable>
     <xsl:template match="/*">
          <DataPDU xmlns="urn:swift:saa:xsd:saa.2.0">
               <Header>
                    <Message>
                         <SenderReference>
                              <xsl:value-of select="./yyyy:infos/yyyy:reference_tech"/>
                         </SenderReference>
                         <MessageIdentifier>
                              <xsl:value-of select="./yyyy:routage/yyyy:feuille/yyyy:MessageIdentifier"/>
                         </MessageIdentifier>
                         <Format>MX</Format>
                         <Sender>
                              <DN>
                                   <xsl:value-of select="$SenderDN"/>
                              </DN>
                              <FullName>
                                   <X1>
                                        <xsl:value-of select="$SenderBIC8"/>
                                        <xsl:value-of select="./yyyy:routage/yyyy:feuille/yyyy:SenderBranchCode"/>
                                   </X1>
                              </FullName>
                         </Sender>
                         <Receiver>
                              <DN>
                                   <xsl:value-of select="./yyyy:routage/yyyy:feuille/yyyy:ReceiverDN"/>
                              </DN>
                              <FullName>
                                   <X1>
                                        <xsl:value-of select="./yyyy:routage/yyyy:feuille/yyyy:ReceiverBIC11"/>
                                   </X1>
                              </FullName>
                         </Receiver>
                         <InterfaceInfo>
                              <UserReference>
                                   <xsl:value-of select="./yyyy:infos/yyyy:reference_tech"/>
                              </UserReference>
                         </InterfaceInfo>
                         <NetworkInfo>
                              <Service>
                                   <xsl:value-of select="./yyyy:routage/yyyy:feuille/yyyy:Service"/>
                              </Service>
                         </NetworkInfo>
                    </Message>
               </Header>
               <Body>
                    <AppHdr>
                         <MsgRef>
                              <xsl:value-of select="./yyyy:infos/yyyy:reference_tech"/>
                         </MsgRef>
                         <CrDate>
                              <xsl:value-of select="./yyyy:infos/yyyy:generated"/>
                         </CrDate>
                    </AppHdr>
                    <Document> </Document>
               </Body>
          </DataPDU>
     </xsl:template>
</xsl:stylesheet>And I get this error message :
ORA-31011: XML parsing failed
ORA-19202: Erroroccured in XML processing
LPX-00607: Invalid reference: 'SenderDN'Why this error?
How to use this variable?
Thanks,
-Dominique

Hi,
I'va found the solution by modifying the <xsl:stylesheet> like this :
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"
     xmlns:yyyy="http://www.xxxxxx.com/yyyy/pipo"
     xmlns="urn:swift:saa:xsd:saa.2.0">(adding xmlns="urn:swift:saa:xsd:saa.2.0")
But I don't understand why it work fine now ???
If anyone have an explanation?
Thanks,
-Dominique

0,801: Invalid reference document import namespace

I have a Sensor Edge Server in which I've configured a Edge Simulator Driver. I'm dispatching my events to a BPEL Process thro' a WebService call.
My eflow.xml looks like this.
===============================================================================

===============================================================================
<eflow>
     <components>
          <component name="callBpel" class="oracle.edge.tools.eflow.impl.BpelState" />
          <component name="matchEvent" class="oracle.edge.tools.eflow.impl.MatchEventState" />
          <component name="sendEvent" class="oracle.edge.tools.eflow.impl.SendEventState" />
          <component name="callWs" class="oracle.edge.tools.eflow.impl.WsState" />
     </components>
     <entry>
          <onEvent state='A.check'/>
     </entry>
     <states>
          <matchEvent name="A.check" control="matchEvent" type="200" x="100" y="200" >
               <case result="ok" next="good.event"/>
          </matchEvent>
          <callWs name="good.event" wsdl="http://localhost:7777/orabpel/default/BPELProcess/1.0/BPELProcess?wsdl" method="initiate" namespace="http://xmlns.oracle.com/BPELProcess" docRoot="MyRoot">
               <param name="id" type="integer">$event.id$</param>
               <param name="subType" type="integer">$event.subType$</param>
          </callWs>
     </states>
</eflow>
===============================================================================
My BPEL process refers an xsd file 'BPELProcess.xsd'.
===============================================================================

===============================================================================
<types>
     <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/" xmlns:client="http://xmlns.oracle.com/BPELProcess">
     <xsd:import namespace="http://xmlns.oracle.com/BPELProcess" schemaLocation="BPELProcess.xsd"/>
</xsd:schema>
</types>
===============================================================================
I get the following error in Sensor Edge
Tue Jun 26 17:20:07 IST 2007(2):WsState: Failed init:>>
oracle.j2ee.ws.client.WebServiceProxyException: WSDL parsing failed
     0,801: Invalid reference document import namespace: http://xmlns.oracle.com/BPELProcess.
     at oracle.j2ee.ws.client.impl.DefaultWebServiceProxy.newInstanceFromService(DefaultWebServiceProxy.java:106)
I assume that I'm getting this error because Event Flow Dispatcher does not understand the schema as it's defined in an xsd file and Sensor Edge cannot find the xsd.
Can anybody help me with this. Where can I put my xsd file so that Sensor Edge can access it.
One solution is to define the schema inline in the BPELProcess.wsdl, but I do not want to do that for some particular reasons.
Please help!

Nimish, I don't have an answer to your question, but have a question for you. You talk about having the schema inline. Is there a way to have the wsdl document generated so that the schema is produced inline, instead of using a reference as in your case? If so, how do you do it?
Thanks,
Bob N

XSL-1047: (Error) Invalid instantiation of 'xsl:output' in 'INSERT' context

Following is my development environment:
JDeveloper 9i Release Candidate
JDeveloper JVM 1.3.1
Oracle XML Parser v2 9.2.0.0.0
I'm using the Oracle XML Parser V2 9.2.0.0.0 library to apply a stylesheet to an XML document. However when I invoke the call to processor.processXSL() an XSLException is thrown with the following details:
oracle.xml.parser.v2.XSLException: <Line 1, Column 116>: XSL-1047: (Error) Invalid instantiation of 'xsl:output' in 'INSERT' context.
exception
Below is the sequence of events:
// Create an instance of XSLProcessor to perform the transformation
XSLProcessor processor = new XSLProcessor();
// create a Reader from a String object that contains the stylesheet text
StringReader r = new StringReader( stylesheet );
// create a new XSL stylesheet, passing it the Reader object reference
XSLStylesheet sheet = processor.newXSLStylesheet(r);
// apply the stylesheet
// the variable sheet represents the XSLStylesheet object
// the variable source represents the XMLDocument object
// this call throws the exception
DocumentFragment df =
processor.processXSL(sheet,source);
I've included the Stylesheet and source XML file I'm processing below.
Note: My application works fine when I use the Oracle XML Parser v2 9.0.1 library. (although I have to use new XSLStylesheet() in place of XSLProcessor.newXSLStylesheet())
Any ideas on what has changed between the two releases? I do have a reproducible test case that I can send on if required?
thanks in advance
private String stylesheet =
"<INSERT xsl:version=\"1.0\" xmlns:xsl=\"http://www.w3.org/1999/XSL/Transform\"> "+
"<xsl:output method=\"xml\" indent=\"yes\"/> "+
"<ROWSET table_name=\"acc_database\"> "+
" <xsl:for-each select=\"DATABASES/DATABASE\"> "+
" <ROW> "+
" <DBID><xsl:value-of select=\"DBID\"/></DBID> "+
" <DBNAME><xsl:value-of select=\"DBNAME\"/></DBNAME> "+
" <DBSIZE><xsl:value-of select=\"DBSIZE\"/></DBSIZE> "+
" <DBPATHNAME><xsl:value-of select=\"DBPATHNAME\"/></DBPATHNAME> "+
" <DBUSER><xsl:value-of select=\"DBUSER\"/></DBUSER> "+
" <DBPASSWORD><xsl:value-of select=\"DBPASSWORD\"/></DBPASSWORD> "+
" <ISAPPDB><xsl:value-of select=\"ISAPPDB\"/></ISAPPDB> "+
" <ISATTACHEDDB><xsl:value-of select=\"ISATTACHEDDB\"/></ISATTACHEDDB> "+
" <CONVERTDB><xsl:value-of select=\"CONVERTDB\"/></CONVERTDB> "+
" <VERSION><xsl:value-of select=\"VERSION\"/></VERSION> "+
" </ROW> "+
" </xsl:for-each> "+
"</ROWSET> "+
"</INSERT>";
<?xml version="1.0" encoding="ISO-8859-1"?>


<DATABASES>
<DATABASE>
<DBID>1</DBID>
<DBNAME>xmltest</DBNAME>
<DBSIZE>1</DBSIZE>
<DBPATHNAME>E:\xmltest.mdb</DBPATHNAME>
<DBUSER>xmltest</DBUSER>
<DBPASSWORD>oracle</DBPASSWORD>
<ISAPPDB>1</ISAPPDB>
<ISATTACHEDDB>0</ISATTACHEDDB>
<CONVERTDB>1</CONVERTDB>
<VERSION>4.0</VERSION>
<TABLES>
<TABLE PRIMARY_KEY="1">
<TBLID>1</TBLID>
<DBID>1</DBID>
<TBLNAME>xsu_test</TBLNAME>
<CNVTABLESTRUCT>1</CNVTABLESTRUCT>
<CNVMOVEDATA>1</CNVMOVEDATA>
<CNVRI>1</CNVRI>
<CNVVALIDATION>1</CNVVALIDATION>
<CNVDEFAULT>1</CNVDEFAULT>
<CNVADDTIMESTAMP>1</CNVADDTIMESTAMP>
<ATTACHTABLEBACKTOACCESS>1</ATTACHTABLEBACKTOACCESS>
<SAVEPASSWORD>0</SAVEPASSWORD>
<CNVMAKEUPDATEABLE>1</CNVMAKEUPDATEABLE>
<RETAINLOCALCOPY>0</RETAINLOCALCOPY>
<SYNCWITHSERVER>1</SYNCWITHSERVER>
<OWNERID>1</OWNERID>
<VALIDATIONTEXT></VALIDATIONTEXT>
<VALIDATIONRULE></VALIDATIONRULE>
<NUMBEROFROWS>1</NUMBEROFROWS>
<CACHINGTABLE>0</CACHINGTABLE>
<DESCRIPTION></DESCRIPTION>
<COLUMNS>
<COLUMN>
<COLID>1</COLID>
<TBLID>1</TBLID>
<COLNAME>id</COLNAME>
<COLTYPE>4</COLTYPE>
<COLTYPEDESC>Long</COLTYPEDESC>
<COLAUTOINCR>1</COLAUTOINCR>
<NEXTCOUNTERVALUE>0</NEXTCOUNTERVALUE>
<MAXLENGTHSOURCE>0</MAXLENGTHSOURCE>
<AVGLENGTHSOURCE>0</AVGLENGTHSOURCE>
<COLTEXTSIZE>4</COLTEXTSIZE>
<ALLOWZEROLENGTH>0</ALLOWZEROLENGTH>
<DEFAULTVALUE></DEFAULTVALUE>
<COLREQUIRED>1</COLREQUIRED>
<COLCOLLATINGORDER>1033</COLCOLLATINGORDER>
<COLORDPOSITION>1</COLORDPOSITION>
<VALIDATIONRULE></VALIDATIONRULE>
<VALIDATIONTEXT></VALIDATIONTEXT>
<COLUMNDESCRIPTION></COLUMNDESCRIPTION>
</COLUMN>
<COLUMN>
<COLID>2</COLID>
<TBLID>1</TBLID>
<COLNAME>name</COLNAME>
<COLTYPE>10</COLTYPE>
<COLTYPEDESC>Text</COLTYPEDESC>
<COLAUTOINCR>0</COLAUTOINCR>
<NEXTCOUNTERVALUE>0</NEXTCOUNTERVALUE>
<MAXLENGTHSOURCE>0</MAXLENGTHSOURCE>
<AVGLENGTHSOURCE>0</AVGLENGTHSOURCE>
<COLTEXTSIZE>50</COLTEXTSIZE>
<ALLOWZEROLENGTH>0</ALLOWZEROLENGTH>
<DEFAULTVALUE></DEFAULTVALUE>
<COLREQUIRED>1</COLREQUIRED>
<COLCOLLATINGORDER>1033</COLCOLLATINGORDER>
<COLORDPOSITION>2</COLORDPOSITION>
<VALIDATIONRULE></VALIDATIONRULE>
<VALIDATIONTEXT></VALIDATIONTEXT>
<COLUMNDESCRIPTION></COLUMNDESCRIPTION>
</COLUMN>
</COLUMNS>
<INDEXES>
<INDEX>
<INDID>1</INDID>
<TBLID>1</TBLID>
<DBID>1</DBID>
<INDNAME>id</INDNAME>
<CNVINDEX>1</CNVINDEX>
<ISPRIMARY>0</ISPRIMARY>
<ISUNIQUE>0</ISUNIQUE>
<ISFOREIGN>0</ISFOREIGN>
<IGNORENULLS>0</IGNORENULLS>
<ISREQUIRED>0</ISREQUIRED>
<INDEX_COLUMNS>
<INDEX_COLUMN>
<INDCOLID>1</INDCOLID>
<INDID>1</INDID>
<COLID>1</COLID>
<COLORDER>1</COLORDER>
</INDEX_COLUMN>
</INDEX_COLUMNS>
</INDEX>
<INDEX>
<INDID>2</INDID>
<TBLID>1</TBLID>
<DBID>1</DBID>
<INDNAME>PK_xsu_test</INDNAME>
<CNVINDEX>1</CNVINDEX>
<ISPRIMARY>1</ISPRIMARY>
<ISUNIQUE>1</ISUNIQUE>
<ISFOREIGN>0</ISFOREIGN>
<IGNORENULLS>0</IGNORENULLS>
<ISREQUIRED>1</ISREQUIRED>
<INDEX_COLUMNS>
<INDEX_COLUMN>
<INDCOLID>2</INDCOLID>
<INDID>2</INDID>
<COLID>1</COLID>
<COLORDER>1</COLORDER>
</INDEX_COLUMN>
</INDEX_COLUMNS>
</INDEX>
</INDEXES>
</TABLE>
</TABLES>
<RELATIONS>
</RELATIONS>
</DATABASE>
<ATTACHED_TABLES>
</ATTACHED_TABLES>
</DATABASES>

Your problem is that your stylesheet is illegal.
You're using the "simple form" of the stylesheet which
is equivalent to having a single root template.
If you use the simple form, you cannot use: <xsl:include>,
<xsl:import>, <xsl:output>, <xsl:param>
or any other <xsl:XXX> element which must be at the "top-level"
of the stylesheet.
The solution is to change from:
<INPUT xsl:version="1.0" xmlns:xsl="...">
   <xsl:output>
</INPUT>.
which is illegal to:
<xsl:stylesheet version="1.0" xmlns:xsl="...">
    <xsl:output>
    <xsl:template match="/">
      <INPUT>
      </INPUT>
    </xsl:template>
</xsl:stylesheet>

PLS-S-00487, Invalid reference to variable while compiling PRO*C program

Hi,
I am writing a PRO*C code and get an error in compilation.
Code is as below:
+#include <stdio.h>+
+#include <string.h>+
EXEC SQL INCLUDE sqlca.h;
int main(int argc , char **argv)
+{+
int i;
EXEC SQL BEGIN DECLARE SECTION;
VARCHAR connString[100];
struct emp_record
+{+
char name[25];
char dept[10];
int id;
int salary;
int comm;
int tot_sal;
+}e1;+
EXEC SQL END DECLARE SECTION;
strcpy (connString.arr, "abcd/efgh@ijkl");
connString.len = strlen ( connString.arr);
+printf("\n Connection is [%d][%s]",connString.len,connString.arr);+
+EXEC SQL CONNECT :connString;+
+if(sqlca.sqlcode!=0)+
+{+
+printf("\nFailed to Connect, sqlcode is %d\n",sqlca.sqlcode);+
+printf("\nOracle Message = %s", sqlca.sqlerrm.sqlerrmc);+
+exit(-1);+
+}+
+else+
+{+
+printf("\nConnected\n");+
+}+
+EXEC SQL EXECUTE+
+BEGIN+
+emp_calc ( :e1.name,+
+:e1.id,+
+:e1.salary,+
+:e1.tot_sal+
+);+
+END;+
+END-EXEC;+
+if(sqlca.sqlcode!=0)+
+{+
+printf("Oracle Error:[%d][%s]",sqlca.sqlcode,sqlca.sqlerrm.sqlerrmc);+
+}+
+}+
Procedure code is:
+CREATE OR REPLACE PROCEDURE "EMP_CALC" (+
+pi_empname in emp.ename%type,+
+pi_empno in emp.empno%type,+
+pi_sal in emp.sal%type,+
+po_totsal out NUMBER)+
+is+
+begin+
+po_totsal := 1.1 * pi_sal;+
+dbms_output.put_line('Total Salary is:' || po_totsal);+
+end;+
*My main aim is to use elements of a structure in procedure call as parameters*
*But when I compile I get error on such usage as follows:*
Pro*C/C++: Release 11.2.0.3.0 - Production on Tue Apr 30 16:59:22 2013
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
System default option values taken from: /mtsapp1/ora11g/product/11.2.0.3/dbhome_1/precomp/admin/pcscfg.cfg
Error at line 52, column 20 in file singleStructOra.pc
emp_calc ( :e1.name,
...................1
PLS-S-00487, Invalid reference to variable 'E1'
Error at line 52, column 1 in file singleStructOra.pc
emp_calc ( :e1.name,
1
PLS-S-00000, Statement ignored
Semantic error at line 50, column 1, file singleStructOra.pc:
BEGIN
1
PCC-S-02346, PL/SQL found semantic errors
*I would like to know how to resolve this compilation error and how do I use members of structures in such a procedure call.*
Thanks....

Sadly PL/SQL blocks do not understand structs (or arrays). DML statements do understand them.
This is not very clearly stated in the manual, but it does say:
http://docs.oracle.com/cd/E11882_01/appdev.112/e10825/pc_08arr.htm#autoId33
Restrictions on Arrays of Structs
The following restrictions apply to the use of arrays of structs in Pro*C/C++:
Arrays of structs (just as with ordinary structs) are not permitted inside an embedded PL/SQL block.
http://docs.oracle.com/cd/E11882_01/appdev.112/e10825/pc_07pls.htm#autoId13
Do not use C pointer or array syntax in PL/SQL blocks. The PL/SQL compiler does not understand C host-variable expressions and is, therefore, unable to parse them.
Although the example uses an array of structs, simple structs also fail. I have always had to copy the fields to and from simple variables when calling stored procedures.
regards,
David

AIP-51505: 5084: XEngine error - Invalid data.

Hi All,
I am getting invalid data error when posting a EDI 855 from BPEL to iB2B.
I have done the following already: set validation to false and verified the XML against the xsd using XMLSpy.
Any idea what can be wrong?
Thanks in advance,
Suresh
2007.09.25 at 14:08:14:877: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:getControlNumberFromEDIRepository CtlNum (TP): Interchange = 1101, Functional Group = 1101, Transaction Set = 1097
2007.09.25 at 14:08:14:877: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Enter
2007.09.25 at 14:08:14:877: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl fullOutboundBatching = false
2007.09.25 at 14:08:14:878: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl validateEnvelope = false
2007.09.25 at 14:08:14:878: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Leave
2007.09.25 at 14:08:17:023: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:reset Enter
2007.09.25 at 14:08:17:023: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:reset Leave
2007.09.25 at 14:08:17:023: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument XML = 1
2007.09.25 at 14:08:17:024: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument no result from XDataToNative
2007.09.25 at 14:08:17:024: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sErrorGuid = {F35AFE03-C479-4F96-B4F1-2EF36DABC5FE}
2007.09.25 at 14:08:17:024: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sDescription = Invalid data.
2007.09.25 at 14:08:17:024: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sBrDescription = 5084: XEngine error - Invalid data.
2007.09.25 at 14:08:17:024: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ErrorLevel sParameterValue = 0
2007.09.25 at 14:08:17:025: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = Name sParameterValue = XData2Native
2007.09.25 at 14:08:17:025: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ecdn_guid_ sParameterValue = {4A4CF358-6B92-11DC-82C1-00142223EF95}
2007.09.25 at 14:08:17:025: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ecindex sParameterValue = 0
2007.09.25 at 14:08:17:025: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ec_error_scope sParameterValue = Document
2007.09.25 at 14:08:17:025: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument added Hash Key = {4A4CF358-6B92-11DC-82C1-00142223EF95}
2007.09.25 at 14:08:17:025: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument batch Position = 0
2007.09.25 at 14:08:17:026: Thread-22: B2B - (ERROR) Error -: AIP-51505: General Validation Error
     at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2021)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1219)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:725)
     at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:906)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:655)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:353)
     at java.lang.Thread.run(Thread.java:534)
2007.09.25 at 14:08:17:026: Thread-22: B2B - (ERROR) Error -: AIP-51505: General Validation Error
     at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2021)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1219)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:725)
     at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:906)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:655)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:353)
     at java.lang.Thread.run(Thread.java:534)
2007.09.25 at 14:08:17:027: Thread-22: B2B - (ERROR) Error -: AIP-51505: General Validation Error
     at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2062)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1219)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:725)
     at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:906)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:655)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:353)
     at java.lang.Thread.run(Thread.java:534)
2007.09.25 at 14:08:17:027: Thread-22: B2B - (ERROR) Error -: AIP-51505: General Validation Error: Error -: AIP-51505: General Validation Error
     at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2062)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1219)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:725)
     at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:906)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:655)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:353)
     at java.lang.Thread.run(Thread.java:534)
Caused by: Error -: AIP-51505: General Validation Error
     at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2021)
     ... 6 more
2007.09.25 at 14:08:17:027: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage B2BDomainException
2007.09.25 at 14:08:17:027: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updating Error Message: Error -: AIP-51505: General Validation Error
2007.09.25 at 14:08:17:028: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2007.09.25 at 14:08:17:029: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message not found.
2007.09.25 at 14:08:17:029: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
2007.09.25 at 14:08:17:032: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
2007.09.25 at 14:08:17:032: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updating Native Event Tbl Row
2007.09.25 at 14:08:17:032: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
2007.09.25 at 14:08:17:033: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
** DbAccess:updateNativeEvtTblRow:tip_wireMsg wiremsg not found
2007.09.25 at 14:08:17:034: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException notifying App
2007.09.25 at 14:08:17:034: Thread-22: B2B - (DEBUG) Engine:notifyApp Enter
2007.09.25 at 14:08:17:036: Thread-22: B2B - (DEBUG) Enqueue Engine AQJMSCorrelationID = 3AE6A497D52861F3E0400302290324BA
2007.09.25 at 14:08:17:036: Thread-22: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
<Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<correlationId>4de21f37c68d8a74:-3030dba5:11538f2ec0d:-7cfc</correlationId>
<b2bMessageId>4de21f37c68d8a74:-3030dba5:11538f2ec0d:-7cfc</b2bMessageId>
<errorCode>AIP-51505</errorCode>
<errorText>5084: XEngine error - Invalid data.</errorText>
<errorDescription>
<![CDATA[Machine Info: (phantom.ciena.com)
Invalid data. ]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
2007.09.25 at 14:08:17:036: Thread-22: B2B - (DEBUG) AQJMSCorrelationID = 3AE6A497D52861F3E0400302290324BA
2007.09.25 at 14:08:17:041: Thread-22: B2B - (DEBUG) Engine:notifyApp Exit
2007.09.25 at 14:08:17:041: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updated the Error Message Successfully: Error -: AIP-51505: General Validation Error
2007.09.25 at 14:08:17:042: Thread-22: B2B - (DEBUG) DBContext commit: Enter
2007.09.25 at 14:08:17:046: Thread-22: B2B - (DEBUG) DBContext commit: Transaction.commit()
2007.09.25 at 14:08:17:046: Thread-22: B2B - (DEBUG) DBContext commit: Leave
2007.09.25 at 14:08:17:046: Thread-22: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Exit
xml 855:
<Transaction-855 xmlns:ns1="urn:oracle:integration:b2b:ED4636190E8D48CB88002EE2393BAFD6" xmlns="urn:oracle:integration:b2b:ED4636190E8D48CB88002EE2393BAFD6">
<ns1:Segment-ST>
<ns1:Element-143>855</ns1:Element-143>
<ns1:Element-329>36770001</ns1:Element-329>
</ns1:Segment-ST>
<ns1:Segment-BAK>
<ns1:Element-353>00</ns1:Element-353>
<ns1:Element-587>AT</ns1:Element-587>
<ns1:Element-324>QW-09122007-T2</ns1:Element-324>
<ns1:Element-373>20070924</ns1:Element-373>
<ns1:Element-373_1>20070924</ns1:Element-373_1>
</ns1:Segment-BAK>
<ns1:Segment-CUR>
<ns1:Element-98>PE</ns1:Element-98>
<ns1:Element-100>USD</ns1:Element-100>
</ns1:Segment-CUR>
<ns1:Loop-PO1>
<ns1:Segment-PO1>
<ns1:Element-350>004.000</ns1:Element-350>
<ns1:Element-330>2</ns1:Element-330>
<ns1:Element-355>EA</ns1:Element-355>
<ns1:Element-212>1.1</ns1:Element-212>
<ns1:Element-235>IN</ns1:Element-235>
<ns1:Element-234>009-2002-734</ns1:Element-234>
<ns1:Element-235_1>VN</ns1:Element-235_1>
<ns1:Element-234_1>76814</ns1:Element-234_1>
</ns1:Segment-PO1>
<ns1:Loop-ACK>
<ns1:Segment-ACK>
<ns1:Element-668>IA</ns1:Element-668>
</ns1:Segment-ACK>
</ns1:Loop-ACK>
<ns1:Loop-SCH>
<ns1:Segment-SCH>
<ns1:Element-380>2</ns1:Element-380>
<ns1:Element-355_1>EA</ns1:Element-355_1>
<ns1:Element-374_5>079</ns1:Element-374_5>
<ns1:Element-373>20070924</ns1:Element-373>
</ns1:Segment-SCH>
</ns1:Loop-SCH>
</ns1:Loop-PO1>
<ns1:Loop-PO1>
<ns1:Segment-PO1>
<ns1:Element-350>002.000</ns1:Element-350>
<ns1:Element-330>2</ns1:Element-330>
<ns1:Element-355>EA</ns1:Element-355>
<ns1:Element-212>1.1</ns1:Element-212>
<ns1:Element-235>IN</ns1:Element-235>
<ns1:Element-234>009-2002-375</ns1:Element-234>
<ns1:Element-235_1>VN</ns1:Element-235_1>
<ns1:Element-234_1>76752</ns1:Element-234_1>
</ns1:Segment-PO1>
<ns1:Loop-ACK>
<ns1:Segment-ACK>
<ns1:Element-668>IA</ns1:Element-668>
</ns1:Segment-ACK>
</ns1:Loop-ACK>
<ns1:Loop-SCH>
<ns1:Segment-SCH>
<ns1:Element-380>2</ns1:Element-380>
<ns1:Element-355_1>EA</ns1:Element-355_1>
<ns1:Element-374_5>079</ns1:Element-374_5>
<ns1:Element-373>20070924</ns1:Element-373>
</ns1:Segment-SCH>
</ns1:Loop-SCH>
</ns1:Loop-PO1>
<ns1:Loop-PO1>
<ns1:Segment-PO1>
<ns1:Element-350>003.000</ns1:Element-350>
<ns1:Element-330>2</ns1:Element-330>
<ns1:Element-355>EA</ns1:Element-355>
<ns1:Element-212>1.1</ns1:Element-212>
<ns1:Element-235>IN</ns1:Element-235>
<ns1:Element-234>009-2002-710</ns1:Element-234>
<ns1:Element-235_1>VN</ns1:Element-235_1>
<ns1:Element-234_1>76744</ns1:Element-234_1>
</ns1:Segment-PO1>
<ns1:Loop-ACK>
<ns1:Segment-ACK>
<ns1:Element-668>IA</ns1:Element-668>
</ns1:Segment-ACK>
</ns1:Loop-ACK>
<ns1:Loop-SCH>
<ns1:Segment-SCH>
<ns1:Element-380>2</ns1:Element-380>
<ns1:Element-355_1>EA</ns1:Element-355_1>
<ns1:Element-374_5>079</ns1:Element-374_5>
<ns1:Element-373>20070924</ns1:Element-373>
</ns1:Segment-SCH>
</ns1:Loop-SCH>
</ns1:Loop-PO1>
<ns1:Loop-CTT>
<ns1:Segment-CTT>
<ns1:Element-354>3</ns1:Element-354>
</ns1:Segment-CTT>
</ns1:Loop-CTT>
<ns1:Segment-SE>
<ns1:Element-96>14</ns1:Element-96>
<ns1:Element-329>36770001</ns1:Element-329>
</ns1:Segment-SE>
</Transaction-855>

Hello,
Can you please restart the b2b server and apply the latest patch. If the problem still persist send us the export.
Rgds,Ramesh

Data error (invalid data type 17) in a Remote Function Call

Hi,
I am passing 2 select-option tables to RFC.
Tables have structures -
   Table1 SIGN(C1)
               OPTION(C2)
               HIGH(C6)
               LOW(C6)
   Table2 SIGN(C1)
               OPTION(C2)
               HIGH(C20)
               LOW(C20)
At the destination side, I have created two table types which have same structure.
But when I call the RFC , program terminates with error - "Data error (invalid data type 17) in a Remote Function Call"
Not able to understand the reason for this error. Please help.
Thanks,
Sujeet

Hi,
check out this example
[LINK|http://abap.googlar.eu/viewtopic.php?f=5&t=28]
You have several ranges that you can use like RANGE_AUF.
Function example:
FUNCTION zexemple.
*"*"Interface local:
*" IMPORTING
*"     REFERENCE(R_HORA) TYPE FLAG
*"     REFERENCE(R_DIA_1) TYPE FLAG
*"     REFERENCE(P_IDOC) TYPE FLAG
*" EXPORTING
*"     REFERENCE(MSG) TYPE CHAR255
*" TABLES
*"      T_OIFSPBL STRUCTURE OIFSPBL
*"      SL_PBLNR STRUCTURE RANGE_PBLNR
*"      SL_MATNR STRUCTURE RANGE_MATNR
*"      SL_HORA STRUCTURE RANGE_UZEIT
*"      T_ERROS STRUCTURE ZARSTRING
ENDFUNCTION.
Report:
SELECT-OPTIONS: sl_pblnr FOR oirbpblb-pblnr,
                              sl_matnr FOR a361-matnr.
~
Final question:
You are passing the values using TABLES and not IMPORTING right?

PLS-00487: Invalid reference to variable 'RC_PARAMSGET'

Oracle 9.2 client ORA 8.1.7 Server:
Trying to run an SP in SQL navigator ( or PL/SQL)
I get the following error(s)
ORA-06550: line 6, column 16:
PLS-00487: Invalid reference to variable 'RC_PARAMSGET'
ORA-06550: line 6, column 3:
++++++++++++++++++++++++++++++++++++++++++++
Here's the Package and Proc Code with the errors at the end.
It seems not to like a Ref Cursor, but I'm not experienced enough to know the reason.
ANy Help would be very appreciated: AJACODE
++++++++++++++++++++++++++++++++++++++++++++
--Package Spec
Package RPT_NB_GUI_Param_Get_PKG
IS
TYPE rc_Params_gettbl IS RECORD (
     o_QueryID          Number,
     o_ParameterID          Number,
     o_Param               VARCHAR2 (20),
     o_Param_Type          VARCHAR2 (50),
     o_Param_QueryID          Number
TYPE rc_params IS REF CURSOR RETURN rc_Params_gettbl;
END; -- Package Specification RPT_NB_GUI_Param_Get_PKG
--+++++++++++++++++++++++++++++++++++++++++
-- Proc
Procedure RPT_NB_GUI_Param_Get_PROC
p_QueryID in Number ,
rc_ParamsGet IN OUT RPT_NB_GUI_Param_Get_PKG.rc_Params)
IS
-- Purpose: To generate Parameters for GUI
-- MODIFICATION HISTORY
-- Person           Date      Comments
-- AJ Grasso           04/11/2003      Created
BEGIN
OPEN rc_ParamsGet For
SELECT
QP.QueryID
,P.ParameterID
,P.Parameter
,PT.Parameter_Type
,PQ.Parameter_QueryID
FROM
rpt_Query_Parameter QP, rpt_Parameter P, rpt_Parameter_Type PT, rpt_parameter_query PQ
WHERE --inner join rpt_Parameter P ON
(QP.ParameterID = P.ParameterID)
AND --inner join rpt_Parameter_Type PT ON
(QP.Parameter_TypeID = PT.Parameter_TypeID)
AND --left outer join rpt_parameter_query PQ ON
(QP.Parameter_queryID = PQ.parameter_queryID)
AND (QP.QueryID = p_QueryID) ;
END; -- RPT_NB_GUI_Param_Get_PROC
-- ERRORS
-- +++++++++++++++++
ORA-06550: line 6, column 16:
PLS-00487: Invalid reference to variable 'RC_PARAMSGET'
ORA-06550: line 6, column 3:
PL/SQL: Statement ignored
ORA-06550: line 7, column 16:
PLS-00487: Invalid reference to variable 'RC_PARAMSGET'
ORA-06550: line 7, column 3:
PL/SQL: Statement ignored
ORA-06550: line 8, column 16:
PLS-00487: Invalid reference to variable 'RC_PARAMSGET'
ORA-06550: line 8, column 3:
PL/SQL: Statement ignored
ORA-06550: line 9, column 16:
PLS-00487: Invalid reference to variable 'RC_PARAMSGET'
ORA-06550: line 9, column 3:
PL/SQL: Statement ignored
ORA-06550: line 10, column 16:
PLS-00487: Invalid reference to variable 'RC_PARAMSGET'
ORA-06550: line 10, column 3:
PL/SQL: Statement ignored
ORA-06550: line 16, column 74:
PLS-00487: Invalid reference to variable 'RC_PARAMSGET'
ORA-06550: line 16, column 3:
PL/SQL: Statement ignored
ORA-06550: line 17, column 78:
PLS-00487: Invalid reference to variable 'RC_PARAMSGET'
ORA-06550: line 17, column 3:
PL/SQL: Statement ignored
ORA-06550: line 18, column 71:

Oracle 9.2 client ORA 8.1.7 Server:
Trying to run an SP in SQL navigator ( or PL/SQL)
I get the following error(s)
ORA-06550: line 6, column 16:
PLS-00487: Invalid reference to variable 'RC_PARAMSGET'
ORA-06550: line 6, column 3:
++++++++++++++++++++++++++++++++++++++++++++
Here's the Package and Proc Code with the errors at the end.
It seems not to like a Ref Cursor, but I'm not experienced enough to know the reason.
ANy Help would be very appreciated: AJACODE
++++++++++++++++++++++++++++++++++++++++++++
--Package Spec
Package RPT_NB_GUI_Param_Get_PKG
IS
TYPE rc_Params_gettbl IS RECORD (
     o_QueryID          Number,
     o_ParameterID          Number,
     o_Param               VARCHAR2 (20),
     o_Param_Type          VARCHAR2 (50),
     o_Param_QueryID          Number
TYPE rc_params IS REF CURSOR RETURN rc_Params_gettbl;
END; -- Package Specification RPT_NB_GUI_Param_Get_PKG
--+++++++++++++++++++++++++++++++++++++++++
-- Proc
Procedure RPT_NB_GUI_Param_Get_PROC
p_QueryID in Number ,
rc_ParamsGet IN OUT RPT_NB_GUI_Param_Get_PKG.rc_Params)
IS
-- Purpose: To generate Parameters for GUI
-- MODIFICATION HISTORY
-- Person           Date      Comments
-- AJ Grasso           04/11/2003      Created
BEGIN
OPEN rc_ParamsGet For
SELECT
QP.QueryID
,P.ParameterID
,P.Parameter
,PT.Parameter_Type
,PQ.Parameter_QueryID
FROM
rpt_Query_Parameter QP, rpt_Parameter P, rpt_Parameter_Type PT, rpt_parameter_query PQ
WHERE --inner join rpt_Parameter P ON
(QP.ParameterID = P.ParameterID)
AND --inner join rpt_Parameter_Type PT ON
(QP.Parameter_TypeID = PT.Parameter_TypeID)
AND --left outer join rpt_parameter_query PQ ON
(QP.Parameter_queryID = PQ.parameter_queryID)
AND (QP.QueryID = p_QueryID) ;
END; -- RPT_NB_GUI_Param_Get_PROC
-- ERRORS
-- +++++++++++++++++
ORA-06550: line 6, column 16:
PLS-00487: Invalid reference to variable 'RC_PARAMSGET'
ORA-06550: line 6, column 3:
PL/SQL: Statement ignored
ORA-06550: line 7, column 16:
PLS-00487: Invalid reference to variable 'RC_PARAMSGET'
ORA-06550: line 7, column 3:
PL/SQL: Statement ignored
ORA-06550: line 8, column 16:
PLS-00487: Invalid reference to variable 'RC_PARAMSGET'
ORA-06550: line 8, column 3:
PL/SQL: Statement ignored
ORA-06550: line 9, column 16:
PLS-00487: Invalid reference to variable 'RC_PARAMSGET'
ORA-06550: line 9, column 3:
PL/SQL: Statement ignored
ORA-06550: line 10, column 16:
PLS-00487: Invalid reference to variable 'RC_PARAMSGET'
ORA-06550: line 10, column 3:
PL/SQL: Statement ignored
ORA-06550: line 16, column 74:
PLS-00487: Invalid reference to variable 'RC_PARAMSGET'
ORA-06550: line 16, column 3:
PL/SQL: Statement ignored
ORA-06550: line 17, column 78:
PLS-00487: Invalid reference to variable 'RC_PARAMSGET'
ORA-06550: line 17, column 3:
PL/SQL: Statement ignored
ORA-06550: line 18, column 71:

FR error: *Error: invalid report object*

Hi All,
When we run the report we are getting error "*Error: invalid report object*. It is for one specific entity at the base level for some user's. Other user's can able to view the data at that leve. All the user's have same level of access. can someone help......
Thanks in advance.
Moh

You are most likely getting this error because you have a report object trying to reference a value out of a datagrid or a POV that doesn't have any data for the given entity.
When you run it for an entity with data in the grid, everything works great. When you run it for an entity with no data, the datagrid essentially doesn't exist and references to it will fail with the error you have shown.
A good example of this is when you have a header and you pull parts of the header from a grid such as showing the scenario, etc. To do this you reference a row (or column) from the datagrid, etc.....
Charles

'Error: Invalid Staging Area' while installing Developer Studio 10g

Dear All,
I am trying to install Oracle Developer Studio 10g on Windows 2000 SP4 machine having 512 MB RAM.
All the installer requirements are met.
After that Oracle Universal Installer displays the error:
Invalid Staging Area. There are no top level components for Windows NT, Windows 2000 available for installation in this staging area.
Please explain me this error. I am not getting any references about the same on Internet.
Do i able to install Oracle Developer Suite on my machine?
-Sameer

"Invalid Staging Area. There are no top level components for Windows NT available for install from this staging area."
This is Oracle's way of saying nothing on this CD can be installed on Windows NT (or Windows 2000)
Also see
http://www.orafaq.com/forum/?t=msg&th=46751/0/
Google on "There are no top level components"

PLS-00487: Invalid reference to variable ' expression '

oracle database 10G
OS unix
One of procedure is giving error PLS-00487: Invalid reference to variable '<expression>' while compilation in above database while it is compiling
successfully in other database.
Is there any database error?

PLS-00487: Invalid reference to variable "string"
Cause: A variable was referenced in a way that is inconsistent with its datatype. For example, a scalar variable might have been mistakenly referenced as a record, as follows: DECLARE CURSOR emp_cur IS SELECT empno, ename, sal FROM emp; emp_rec emp_cur%ROWTYPE; my_sal NUMBER(7,2); BEGIN ... total_sal := total_sal + my_sal.sal; -- invalid ...
Action: Check the spelling of the variable name. Make sure the variable was declared properly and that the declaration and reference are consistent regarding datatype.
Most probably the compiler "sees" some other type variable with the same name first which in the other database doesn't exist or is out of scope.
Regards
Etbin

XSD-2028: (error) Invalid Reference

Similar Messages

Maybe you are looking for