Dbms_xmldom package results in ORA-31020

Hi,
I have the following procedure which compiles correct:
CREATE OR REPLACE procedure vbk_selproc_doc is
queryctx dbms_xmlquery.ctxtype;
result varchar2(30000);
header varchar2(1000);
footer varchar2(1000);
body varchar2(20000);
line VARCHAR2(2000);
var XMLtype;
doc dbms_xmldom.domdocument;
docelem dbms_xmldom.domelement;
node dbms_xmldom.domnode;
childnode dbms_xmldom.domnode;
nodelist dbms_xmldom.domnodelist;
buf varchar2(30000);
begin
queryctx := dbms_xmlquery.newcontext('select * from jobs');
dbms_xmlquery.setrowsettag(queryctx, 'opdracht-aanbieding');
dbms_xmlquery.setrowtag(queryctx, 'opdracht');
dbms_xmlquery.settagcase(queryctx, 1);
dbms_xmlquery.setrowidattrName(queryctx, null);
header := '<?xml version="1.0" encoding="utf-8"?>
<SOAP-ENV:Envelope
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>';
body := dbms_xmlquery.getxml(queryctx);
var := XMLTYPE(body);
doc := dbms_xmldom.newdomdocument(var);
docelem := dbms_xmldom.getdocumentelement(doc);
nodelist := dbms_xmldom.getelementsbytagname(docelem, 'NAME');
node := dbms_xmldom.item(nodelist, 0);
childnode := dbms_xmldom.getfirstchild(node);
dbms_xmldom.writetobuffer(childnode, buf);
dbms_output.put_line('First Child = ' || buf);
footer := '</SOAP-ENV:Body>
</SOAP-ENV:Envelope>' || chr(10);
result := header || ' ' || body || ' ' || footer;
loop
exit when result is null;
line := substr(result, 1, instr(result, chr(10))-1);
dbms_output.put_line(line);
result := substr(result, instr(result, chr(10)) +1 );
end loop;
dbms_xmlquery.closecontext(queryctx);
end;
When executing i get the following error:
SQL> exec vbk_selproc_doc;
BEGIN vbk_selproc_doc; END;
FOUT in regel 1:
.ORA-31020: The operation is not allowed, Reason: Invalid pl/sql DOM Node hdl
ORA-06512: at "XDB.DBMS_XMLDOM", line 715
ORA-06512: at "XDB.DBMS_XMLDOM", line 735
ORA-06512: at "FWADMIN.VBK_SELPROC_DOC", line 48
ORA-06512: at line 1
What is wrong?
Regards,
Joshua

I get the error on:
dbms_xmldom.writetobuffer(childnode, buf);
or when i use dbms_xmldom.removechild(nodelist, childnode)

Similar Messages

Debug of package results in ORA-30683

I'm having a problem trying to debug any package with SQL Developer.
Environment : Windows SQLDeveloper 1.1 to Unix database with SID "eai"
It's returning the following error messages :-
Connecting to the database eai.
Executing PL/SQL: ALTER SESSION SET PLSQL_DEBUG=TRUE
Executing PL/SQL: ALTER SESSION SET PLSQL_COMPILER_FLAGS=INTERPRETED Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( '127.0.0.1', '3717' )
ORA-30683: failure establishing connection to debugger
ORA-12541: TNS:no listener
ORA-06512: at "SYS.DBMS_DEBUG_JDWP", line 68
ORA-06512: at line 1
Process exited.
Disconnecting from the database eai.
Listener is OK.
tnsnames.ora file works and the list of databases comes up in the "new connection".
I'd be grateful for any assistance you could provide.

The database needs to connect back to your PC for debugging. Sometimes sqldeveloper can't determine the address to pass to the database.
Go to Tools -> Preference -> Debugger and select Prompt for Debugger Host for Database Debugger.
You may still have problems if there is a firewall between you and the server.

Error when using DBMS_XMLDOM package

Hello,
I have created a set of triggers that use the DBMS_XMLDOM packages. These triggers were created on a Win 2k install of 9.2.0.2.1. A brand new user was created and a specific set of permissions granted. The permissions were:
GRANT CONNECT, RESOURCE, AQ_ADMINISTRATOR_ROLE, AQ_USER_ROLE
GRANT EXECUTE ON DBMS_AQADM
GRANT EXECUTE ON DBMS_AQ
grant execute on dbms_aqin
execute dbms_java.grant_permission('<USER>', 'java.net.SocketPermission', 'localhost:1024-', 'accept, listen, resolve');
execute dbms_java.grant_permission( '<USER>', 'SYS:java.lang.RuntimePermission', ' getClassLoader', '' )
execute dbms_java.grant_permission( '<USER>', 'SYS:java.lang.RuntimePermission' , 'setContextClassLoader', '' )
I then went to install these triggers on our application database server. This is a Solaris installation that started out as 9.2.0.1.0 and was then upgraded to 9.2.0.2.0. I created the user and granted the exact same permissions on this database. However, everytime I attempt to execute the triggers, or anything else that uses DBMS_XMLDOM packages, I get the following error:
doc dbms_xmldom.DOMDocument;
ERROR at line 3:
ORA-06550: line 3, column 11:
PLS-00201: identifier 'DBMS_XMLDOM.DOMDOCUMENT' must be declared
I did not create the application database instance on the Solaris machine, but from what I've talked with the DBA, it was created as a general database, which is how I created my test databases. I also verified that the users in both databases have Execute on SYS.XMLDOM granted.
Any ideas on why I might be getting this error?
Thanks,
Andrew

When I try the describe, it says object not found. If I go into OEM, I don't see that package either. Again, I didn't create that database, but I thought the XML DB stuff was installed by default with the database. Is there a way to add that package after the database is created?
Thanks,
Andrew

Receiving an ORA-31020: The operation is not allowed...

I'm trying to use a stylesheet that has several included stylesheets.
It looks something like this...
<?xml version='1.0'?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:include href="http://fhamiwsdt01/AMIWeb/namespaces/AmerisureClient.xsl"/>
<xsl:include href="http://fhamiwsdt01/AMIWeb/namespaces/AmerisurePolicy.xsl"/>
<xsl:include href="http://fhamiwsdt01/AMIWeb/namespaces/AmerisureRetailAgent.xsl"/>
<xsl:include href="http://fhamiwsdt01/AMIWeb/namespaces/TransactionUtilities.xsl"/>
My procedure is to grab an xml an bump it up against the stylesheet as follows.
CREATE OR REPLACE FUNCTION transformPolicyXml RETURN CLOB IS
-- Define the local variables
xmldata XMLType;
xsldata XMLType;
newxml XMLType;
xml clob;
xsl clob;
error varchar2(200);
BEGIN
-- Get the XML document using the getXML() function defined in the database.
-- Since XMLType.transform() method takes XML data as XMLType instance,
-- use the XMLType.createXML method to convert the XML content received
-- as CLOB into an XMLType instance.
xml := getxml('Policy.xml');
xmldata := XMLType.createXML(xml);
-- Get the XSL Stylesheet using the getXSL() function defined in the database.
-- Since XMLType.transform() method takes an XSL stylesheet as XMLType instance,
-- use the XMLType.createXML method to convert the XSL content received as CLOB
-- into an XMLType instance.
xsl := getxml('Amerisure EAI XSLT.xsl');
xsldata := XMLType.createXML(xsl);
-- Use the XMLtype.transform() function to get the transformed XML instance.
-- This function applies the stylesheet to the XML document and returns a transformed
-- XML instance.
newxml := xmldata.transform(xsldata);
-- Return the transformed XML instance as a CLOB value.
RETURN newxml.getClobVal();
EXCEPTION WHEN OTHERS THEN
error := sqlerrm;
raise_application_error (-20102, 'Exception occurred in transformPolicyXml :'||SQLERRM);
END transformPolicyXml;
The following statement is what causes an error:
newxml := xmldata.transform(xsldata);
the error i'm receiving is ORA-31020: The operation is not allowed, Reason: For security reasons, ftp and http access over XDB repository is not allowed on server side.
Is there anyway to get around this error?

As the error says, the XML DB does not allow ftp or http access to remote objects.
You will need to make all your includes local to the DB server.

TABLE, PACKAGE, USER가 DROP되지 않을 때의 조치 방법(ORA-1000)

제품 : ORACLE SERVER
작성날짜 : 2004-11-09
TABLE, PACKAGE, USER가 DROP되지 않을 때의 조치 방법(ORA-1000)
============================================================
다음 자료는 dropping an object (table, package, users) 시에
ora-1000 또는 internal error 가 발생하며 drop 되지 않을 때의 조치
방법입니다.
internal 자료로서 엔지니어가 직접 알려주는 것이 좋다고 remark 되어 있는
자료입니다.
요약>
drop package 시에 ora-1000 은 다음 자료 처럼 drop 하려는 object 와
dependency 는 남아있지만 invalid object(no interdependant objects
즉, children which are also parents) 가 존재할 때 발생합니다.
따라서, drop 하려는 object 의 dependency 를 조회하여 invalid object
와의 dependency 를 dependency$ 에서 지워줍니다.
주의!>
다음 작업을 수행 도중 dependency$ 의 row 를 삭제하기 전에는 반드시 cold
backup 을 해 주십시오.
<table, package, user 를 drop 할 때 Ora-1000(ORA-604) 이 발생하는 문제 조치
방법 >
Object 를 drop 할 때 ORA-1000 과 같은 에러가 발생하여, open_cursors
를 1000 이상으로 늘여도 계속 에러가 발생할 때는 다음과 같이 원인을
찾아 제거 합니다.
1. drop 하려는 object 의 parent dependency 를 찾는다.
svrmgr> connect internal;
select lpad(' ',2*(level-1))||p_obj#,d_obj#
from sys.dependency$
where p_obj#=(select a.obj# from sys.obj$ a, sys.user$ b
where a.owner#=b.user#
and a.name='PROCEDURE1' and b.name='SCOTT')
connect by prior d_obj#=p_obj#;
2. drop 하려는 object 의 child dependency 를 찾는다.
select lpad(' ',2*(level-1))||p_obj#,d_obj#
from dependency$
where d_obj#=(select a.obj# from obj$ a, user$ b
where a.owner#=b.user#
and a.name='PROCEDURE1' and b.name='SCOTT')
connect by prior p_obj#=d_obj#;
3. 위에서 조회된 모든 object 가 dba_objects 에 존재하지 않거나 status 가
invalid 인 것을 찾는다.
select * from dba_objects where object_id=xxx;
4. 1 의 조회 결과와 2 의 조회 결과에 의해 동시에 발견된 object id 가
있는지 확인한다.
5. 위의 3 의 조회 결과 object 가 존재하지 않거나 invalid 인 것 ,
4 의 결과 동시에 발견된 object id 가 있다면 cold backup 을 먼저 받아둔다
6. valid 한 backup 이 있다면, sys user 로 접속하여 이들 row 를 다음과 같이
delete 한다.
다음을 먼저 select 한 다음, valid 한 backup 이 있는지 확인한 다음
delete 해야 한다.
즉, 두개의 object 가 서로를 의존하고 있는 것이므로, 두개의 row 를 삭제한다.
다른 row 가 delete 되지 않도록 먼저 query 해 본다.
예) procedure (contact) -> package (dbwww) 그리고 package (dbwww) ->
procedure (contact) 인 경우
1)select * from dependency$
where d_obj#=(select object_id from dba_objects
where owner='....'
and object_type='PROCEDURE'
and object_name='CONTACT')
and p_obj#=(select object_id from dba_objects
where owner='....'
and object_type='PACKAGE;
and object_name='DBWWW')
and d_owner#=(select user_id from dba_users
where username='...');
2)select * from dependency$
where d_obj#=(select object_id from dba_objects
where owner='....'
and object_type='PACKAGE'
and object_name='DBWWW')
and p_obj#=(select object_id from dba_objects
where owner='....'
and object_type='PROCEDURE';
and object_name='CONTACT')
and d_owner#=(select user_id from dba_users
where username='...');
3) alter system flush shared_pool;
4) delete from dependency$
where 위의 1),2) 같음;

ORA-31020 when using XML with external DTD or entities

I'd like to parse XML documents against a modular DTD that references other DTDs. This works fine with Oracle 9i. But after upgrading to 11g, the parsing of XML-instances fails and DBMS_XMLPARSER.parseClob produces ORA-31020.
The same error occurs even if I simply try to store XML with a reference to an external DTD as xmltype:
SQL> select xmltype('<?xml version="1.0" encoding="iso-8859-1"?><!DOCTYPE ewl-artikel SYSTEM "http://www.foo.com/example.dtd"><test>123</test>') from dual;
ERROR:
ORA-31020: Der Vorgang ist nicht zulässig, Ursache: For security reasons, ftp
and http access over XDB repository is not allowed on server side
ORA-06512: in "SYS.XMLTYPE", Zeile 310
ORA-06512: in Zeile 1
How can I use external DTDs on remote servers in order to parse XML in an 11g database??? Any ideas for a workaround? Thanks in advance!

This is my PL/SQL validation procedure:
procedure validatexml (v_id in number default 0) is
PARSER DBMS_XMLPARSER.parser;
DTD_SOURCE clob;
DTD_DOCUMENT xmldom.DOMDocumentType;
XML_INSTANCE xmltype;
BEGIN
-- load DTD from XDB repository
SELECT httpuritype('http://example.foo.de/app1/DTD1.dtd').getclob() into DTD_SOURCE from dual;
-- load XML instance
select co_xml into XML_INSTANCE from tb_xmltab where co_id=v_id;
-- parse XML instance
PARSER := DBMS_XMLPARSER.newParser;
xmlparser.setValidationMode( PARSER , false);
xmlparser.parseDTDClob( PARSER , DTD_SOURCE , 'myfirstnode' );
DTD_DOCUMENT := xmlparser.getDoctype( PARSER );
xmlparser.setValidationMode( PARSER , true );
xmlparser.setDoctype( PARSER , DTD_DOCUMENT );
DBMS_XMLPARSER.parseClob( PARSER , v_xml );
DBMS_XMLPARSER.freeParser(PARSER);
htp.print('<P>XML instance succesfully validated!<P>');
end validatexml;

Trying to connect as sysdba results in ORA-01031

Database server runs in shared server mode,
so in tnsnames I have entry for network service
name with (SERVER = DEDICATED) option to be
able to connect as sysdba, initialization
parameter REMOTE_LOGIN_PASSWORDFILE is set to EXCLUSIVE,
in password file there is one entry for user sys.
I'm trying to connect with user sys as sysdba,
but the result is ORA-01031 error.
Can anybody tell me how can I make it to work?
Thanks for advise a lot,
P.

I have recreated password file,
but it behaves like before, connecting
to database from local machine with
user not in OSDBA or OSOPER group works,
but from other machine it ends with error.
I have one more question: When I connect
from local machine using tnsnames.ora file
in network service name defined in that file
I have (SERVER = SHARED)
and I'm able to connect as sysdba, I thought that
connect as sysdba is possible only with
(SERVER = DEDICATED) when database works in
shared server mode.

Differences between XMLDOM and DBMS_XMLDOM packages

Hi all,
Anybody could tell me if exists any differences between XMLDOM and DBMS_XMLDOM packages. Which are these?
I have Oracle9i Enterprise Edition Release 9.2.0.3.0
Thanks.

hi,
Can you check this
Document TitleORA-1031 when setting Attribute via DBMS_SESSION SET_CONTEXT (Doc ID 100130.1)
thanks,
baskar.l

10.2: loading DBMS_XMLDOM package

I'm getting errors of the form identifier 'DBMS_XMLDOM.DOMNAMEDNODEMAP' must be declared when I run my stored procedure.
What script needs to be run in Oracle 10g to create this package?

I ran that, and that gives this error - do we need to create an xdb user? Is there a stock script for creating this user?
SQL> start dbmsxmld.sql;
CREATE OR REPLACE PACKAGE xdb.dbms_xmldom AUTHID CURRENT_USER IS
ERROR at line 1:
ORA-01435: user does not exist
No errors.
Synonym created.
Synonym created.
Synonym created.
GRANT EXECUTE ON xdb.dbms_xmldom TO PUBLIC
ERROR at line 1:
ORA-04042: procedure, function, package, or package body does not exist
GRANT EXECUTE ON sys.xmldom TO PUBLIC
ERROR at line 1:
ORA-04045: errors during recompilation/revalidation of SYS.XMLDOM
ORA-00980: synonym translation is no longer valid
ORA-00980: synonym translation is no longer valid
No errors.
SQL>

Abap insert into info cube results in ORA 14400

Hi friends,
in principle the situation is as following:
we have 2 cubes which are identically in design, in the number of info objects etc.
now we have the following code here:
* Dann aus Quelltabellen kopieren
* (Fakten zuletzt wegen Fremdschlüsselbez. zu Dim.)
CHECK P_KOP IS NOT INITIAL.
COMMIT WORK.
SELECT * FROM /BIC/DZHW_CUBE1P.
    CHECK /BIC/DZHW_CUBE1P-DIMID <> 0.
    MOVE-CORRESPONDING /BIC/DZHW_CUBE1P TO /BIC/DZHW_CUBE2P.
    INSERT /BIC/DZHW_CUBE2P.
ENDSELECT.
SELECT * FROM /BIC/DZHW_CUBE1T.
    CHECK /BIC/DZHW_CUBE1T-DIMID <> 0.
    MOVE-CORRESPONDING /BIC/DZHW_CUBE1T TO /BIC/DZHW_CUBE2T.
    INSERT /BIC/DZHW_CUBE2T.
ENDSELECT.
SELECT * FROM /BIC/DZHW_CUBE1U.
    CHECK /BIC/DZHW_CUBE1U-DIMID <> 0.
    MOVE-CORRESPONDING /BIC/DZHW_CUBE1U TO /BIC/DZHW_CUBE2U.
    INSERT /BIC/DZHW_CUBE2U.
ENDSELECT.
SELECT * FROM /BIC/DZHW_CUBE11.
    CHECK /BIC/DZHW_CUBE11-DIMID <> 0.
    MOVE-CORRESPONDING /BIC/DZHW_CUBE11 TO /BIC/DZHW_CUBE21.
    INSERT /BIC/DZHW_CUBE21.
ENDSELECT.
COMMIT WORK.
SELECT * FROM /BIC/FZHW_CUBE1.
    /BIC/FZHW_CUBE2-KEY_ZHW_CUBE2P = /BIC/FZHW_CUBE1-KEY_ZHW_CUBE1P.
    /BIC/FZHW_CUBE2-KEY_ZHW_CUBE2T = /BIC/FZHW_CUBE1-KEY_ZHW_CUBE1T.
    /BIC/FZHW_CUBE2-KEY_ZHW_CUBE2U = /BIC/FZHW_CUBE1-KEY_ZHW_CUBE1U.
    /BIC/FZHW_CUBE2-KEY_ZHW_CUBE21 = /BIC/FZHW_CUBE1-KEY_ZHW_CUBE11.
    /BIC/FZHW_CUBE2-/BIC/ZGEHALT   = /BIC/FZHW_CUBE1-/BIC/ZGEHALT.
    INSERT /BIC/FZHW_CUBE2.
ENDSELECT.
the problem is the insert statement. if the interpreter reaches this step in the code, we get a dump with the following message:
" Database error text........: "ORA-14400: inserted partition key does not map to
any partition"
now i assume - since this cube can be loaded with data normally - that it is not possible to store data in an info cube directly using a simple insert statement. are there any appropriate function modules to condense data in a request and load it into an info cube?
Kind Regards.
Gideon.
Message was edited by: Gideon Lenz

hi,
we had a similar error and solved with oss note 339896,
though 2.0b mentioned, it's applicable for our 3.0, please take a look beside the note Vinod mentioned ....(there also mentioned 509660 if f-fact table)
339896
Symptom
During the parallel upload into InfoCubes, ORACLE error ORA14400 might occur in BW 2.0B.
BW2.0B and BW2.1C both originate from the same BW technology basis. Thus 2.0B is a synonym for both releases.
Other terms
Partitioning, ODS, PSA, parallel loading, ORA14400
Reason and Prerequisites
The error can either occur during the insert into the "PSA table" ( /BIC/B00....) or during the insert into the "F-fact table" ( "/BI*/F<INFOCUBE>" ).
If the error occurs when writing to the F-fact table, please refer to Note 509660.
If the error occurs when writing to partitioned PSA tables, an inconsistency exists between administration table "RSTSODS" and the partitions in the database.
Solution
1.) As of Patch 22, CHECK Transaction "RSRV" allows to check the consistency of PSA tables and repair them, if required. (If no name is specified, the CHECK is carried out for all PSA tables.)
2.) Patch < 22: Please check whether function module "RSDDCVER_PSA_PARTITION" exists in your system.
- If yes: Start it for the corresponding PSA table using i_repair = 'X'. Then, the inconsistencies should be eliminated.
- If not: The inconsistencies have to be repaired manually!
Among all partitions of the PSA table, determine the partition with the highest "HIGH VALUE". Compare this partition to the entry in the Partno field of the "RSTSODS" table.
==> Transaction SE16 ---> 'RSTSODS' ---> filter on ODSNAME_TECH with the PSA table name. Error ORA14400 occurs if the entry in the RSTSODS table is higher than the highest partition. To solve the problem, release table RSTSODS in the SAP-DD so that you can change it via Transaction SE16. Then change the entry in the PARTNO field to the value of the highest 'HIGH VALUES'. If the PSA table is empty, enter value '2' in the PARTNO field of the "RSTSODS" table!!!!! The inconsistency may exist in the SAP buffer only. Table RSTSODS is "buffered completely". Before you change the table manually, do submit the command "/$tab rstsods" in the OK-code which invalidates the table in the buffer. If the problem continues to exist, change the entry and invalidate the buffer again by submitting "/$tab rstsods".
509660
Symptom
BW2.0B and BW2.1C are based on the same BW technology.2.0B is therefore a synonym for both releases.
The ORACLE error ORA14400 can occur in BW 2.0B//2.1C during writing to InfoCubes.
Other terms
Partitioning, parallel loading, F fact table, ORA00054, ORA14400, ORA14074, ORA02149
Reason and Prerequisites
The error can also occur during writing to PSA tables or when ODS objects are activated. Refer to note 339896 in this case.As of 2.0B, the F fact table in an BW/ORACLE environment is "range-partitioned" according to the package dimension.A new partition is created when a request is written to requests in the F fact table.If creation of the partition is not successful, ORACLE error 14400 ( "inserted partition key is beyond highest legally partition key" ). There are several causes for this:
1. During loading, there are jobs running (such as ANALYZE TABLE ... CREATE INDEX... ) which lock the table in the ORACLE catalog and take a very long time.Creating the partition on the database takes a very long time;In this case, the ORA00054 error (resource busy) is issued.
2. during parallel loading, an error occurs because an optimistic blocking concept is implemented in the update.
Adding a partition is linked to writing the package dimension entry. If the loading process terminates in such a way that the dimension entry was written, but the partition was not created, the second loading process terminates with ORACLE error ORA14400.
Solution
As of patch BW 2.0B 15 / BW 2.1C 7, creation of a new partition by a SAP lock is saved.If a lock is already present, the program tries to get the lock 100 more times and then continues.In the case of parallel loading processes, this optimistic lock approach always resulted in the ERROR.For this reason, the parameter _wait is set to True in the "RSTMPLWI" template for BW 2.0B patch 21 / BW 2.1C 13 when the enqueue function is called and the loop counter is set to 500, so that the loaders wait longer before continuing.
First select the test "Unused entries in the dimensions of a InfoCube" for the corresponding CUBE via transaction "rsrv" ==> InfocubeData and press "Eliminate error". The entry is then deleted in the dimension and during the next loading process, a new entry is generated and the partition is created.
The correction instructions for BW 2.9B patch 15 - 20 / BW 2.1C patch 7 - 12 is attached.In this way, the programs from the corrected TEMPLATE are regenerated.
If the error persists in spite of this change, check whether the F fact table is analyzing or whether indexes are being generated on the F fact table at the same time as the load process.
The program RSTMPLWI is an ABAP template where the update programs are generated. ==> For this reason, automatic installation is not possible and you can not run a syntax check!

SAP Ides ECC 6.0 Install: Import ABAP - Package SAPDODS Error - ORA-00903

Experts,
Good Morning!
I'm trying to install SAP IDES ECC 6.0 version on a Windows 2008 R2 Server with Oracle 11g DB (11.2).
System Info: 16GM RAM & 600GB Hdd. Prereqs passed.
I'm getting the following error during the Import ABAP phase (16 of 29) in the sapinst log:
"An error occurred while processing option Enhancement Package 6 for SAP ERP 6.0 > SAP Application Server ABAP > Oracle > Central System > Central System( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. "
Here's the dump of import_monitor.java.log
java version "1.4.2_32"
Java(TM) 2 Runtime Environment, Standard Edition (build 4.1.012)
SAP Java Server VM (build 4.1.012 1.6-b03, Oct 21 2011 14:18:45 - 41_REL - optU - windows amd64 - 6 - bas2:161688 (mixed mode))
Import Monitor jobs: running 1, waiting 1, completed 141, failed 0, total 143.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 141, failed 1, total 143.
Here's the dump of import_monitor.log:
INFO: 2014-07-05 13:42:53
Data codepage 4103 is determined using TOC file 'C:\Target\Export1\DATA\D010TAB.TOC' for package 'D010TAB'.
TRACE: 2014-07-05 13:42:53 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is started.
TRACE: 2014-07-05 13:42:53 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDODS' import package into database:
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
ERROR: 2014-07-05 13:42:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is interrupted with R3load error.
Process 'C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error' exited with return code 2.
For mode details see 'SAPDODS.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2014-07-05 13:43:21
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2014-07-05 13:43:21
1 error(s) during processing of packages.
INFO: 2014-07-05 13:43:21
Import Monitor is stopped.
Here's the log of SAPDODS...
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140705134253
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Aug 16 2011 02:26:36
patchinfo (patches.h): (0.098) DB6: correction for R3load PL 91 on HP-UX and SOLARIS (note 1609719)
process id 1488
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF16
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file C:\Target\Export1\DB/SQLFiles.LST
(SQL) INFO: C:\Target\Export1\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file DODS.SQL
(SQL) INFO: DODS.SQL not found
(SQL) INFO: Searching for SQL file C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: found C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: Trying to open C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: C:\Target\Export1\DB/ORA/DODS.SQL opened
(DB) ERROR: DDL statement failed
(DROP TABLE "/BI0/APERS_BOD00")
DbSlExecute: rc = 103
(SQL error 942)
error message returned by DbSl:
ORA-00942: table or view does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: Error 903 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-00903 occurred at SQL stmt (parse error offset=15)
(DB) ERROR: DDL statement failed
( CREATE TABLE [/BI0/APERS_BOD00] ( [TCTUSERNM] nvarchar(000012) NOT NULL , [TCTOBJVERS] nvarchar(000001) NOT NULL , [TCTSYSID] nvarchar(000010) NOT NULL , [TCTQUACT] nvarchar(000001) NOT NULL , [TCTOBJNM] nvarchar(000040) NOT NULL , [TCTTLOGO] nvarchar(000004) NOT NULL , [RECORDMODE] nvarchar(000001) NOT NULL , [TCTTIMSTMP] nvarchar(000014) NOT NULL ) WITH ( DATA_COMPRESSION = PAGE ) )
DbSlExecute: rc = 99
(SQL error 903)
error message returned by DbSl:
ORA-00903: invalid table name
(DB) INFO: disconnected from DB
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140705134254
FYI - A retry does not help. Also tried to search for the error on scn, google but haven't been able to find the right solution.
Can you help?
Regards,
Cobain.

Divyanshu - sorry to ask but can you explain why i need to update r3load and r3trans to resolve this error? Just want to understand why I'm doing a correction so I can learn from the same.
Also, can you clarify the file update process:
For R3load:
a) the r3load used by the command is dated 8/16/2011 (location:C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\...)
b) the r3load i have in my db folder is dated 10/23/2011 (location:C:\Final\Installer\BS7i2011_Installation_Master_\DATA_UNITS\BS2011_IM_WINDOWS_X86_64\ORA\UC\...)
Do i replace (a) with (b)?
For R3trans:
How do I update this file?
- Cobain.

How can I fix a xquery resulting error ORA-19279: XPTY0004 - XQuery dynamic type mismatch: expected singleton sequence - got multi-item sequence

Hello,
How can I improve the XQuery below in order to obtain a minimised return to escape from both errors ORA-19279 and ORA-01706?
XQUERY for $book in fn:collection("oradb:/HR/TB_XML")//article let $cont := $book/bdy where $cont   [ora:contains(text(), "(near((The,power,Love),10, TRUE))") > 0] return $book
ERROR:
ORA-19279: XPTY0004 - XQuery dynamic type mismatch: expected singleton sequence
- got multi-item sequence
XQUERY for $book in fn:collection("oradb:/HR/TB_XML")//article let $cont := $book/bdy where $cont   [ora:contains(., "(near((The,power,Love),10, TRUE))") > 0] return $book//bdy
/*ERROR:
ORA-01706: user function result value was too large
Regards,
Daiane

below query works for 1 iteration . but for multiple sets i am getting following error .
When you want to present repeating groups in relational format, you have to extract the sequence of items in the main XQuery expression.
Each item is then passed to the COLUMNS clause to be further shredded into columns.
This should work as expected :
select x.*
from abc t
   , xmltable(
       xmlnamespaces(
         default 'urn:swift:xsd:fin.970.2011'
       , 'urn:swift:xsd:mtmsg.2011' as "ns0"
     , '/ns0:FinMessage/ns0:Block4/Document/MT970/F61a/F61'
       passing t.col1
       columns F61ValueDate                Varchar(40) Path 'ValueDate'
             , DebitCreditMark             Varchar(40) Path 'DebitCreditMark'
             , Amount                      Varchar(40) Path 'Amount'
             , TransactionType             Varchar(40) Path 'TransactionType'
             , IdentificationCode          Varchar(40) Path 'IdentificationCode'
             , ReferenceForTheAccountOwner Varchar(40) Path 'ReferenceForTheAccountOwner'
             , SupplementaryDetails        Varchar(40) Path 'SupplementaryDetails'
     ) x ;

Package Returning Error ORA-06502: PL/SQL: numeric or value error

Hi,
I create a package to export to spread sheet .xls, The package work for simple query if i pass the query to package.
There is no error in package please create the package and do the following as mentioned below
create or replace
PACKAGE export_pkg_spread_sheet
AS
procedure download_excel(vsql in clob );
PROCEDURE excel_header(p_header in out nocopy clob);
procedure excel_content(p_content in out nocopy clob,
vsql in clob );
procedure excel_footer(p_footer in out nocopy clob);
procedure get_usable_sql (p_sql_in IN clob,
p_sql_out OUT clob);
END export_pkg_spread_sheet;
create or replace
PACKAGE body export_pkg_spread_sheet
AS
PROCEDURE excel_header (p_header IN OUT nocopy CLOB)
AS
BEGIN
p_header := '<html><body>';
END;
procedure download_excel( vsql in clob )
as
p_header clob;
p_footer clob;
p_content clob;
begin
owa_util.mime_header( 'application/octet', FALSE );
htp.p('Content-Disposition: attachment; filename="report.xls"');
owa_util.http_header_close;
excel_header( p_header);
excel_content(p_content,vsql);
excel_footer(p_footer);
dbms_output.put_line(p_header ||p_content|| p_footer);
HTP.PRN( p_header ||p_content|| p_footer);
htmldb_application.g_unrecoverable_error := true;
end;
procedure excel_content(p_content in out nocopy clob,
vsql in clob)
as
p_sql_stmt clob;
cur PLS_INTEGER := DBMS_SQL.OPEN_CURSOR;
cols DBMS_SQL.DESC_TAB;
ncols PLS_INTEGER;
TYPE varColumn     IS TABLE OF varchar2(32000);
vtab varColumn;
v_column_count     NUMBER     DEFAULT 0;
v_status      INTEGER;
BEGIN
htp.prn('am here');
/* SELECT region_source into p_sql_stmt
FROM apex_application_page_regions
WHERE region_id = p_region_id AND
page_id = p_page_id AND
application_id = p_app_id; */
get_usable_sql (vsql,p_sql_stmt);
p_content := p_sql_stmt;
-- Parse the query.
DBMS_SQL.PARSE(cur, p_sql_stmt , DBMS_SQL.NATIVE);
-- Retrieve column information
DBMS_SQL.DESCRIBE_COLUMNS (cur, ncols, cols);
-- Display each of the column names
p_content := '<table> <tr>';
FOR colind IN 1 .. ncols
LOOP
p_content := p_content || '<td>' || cols(colind).col_name || '</td>';
END LOOP;
p_content := p_content || '</tr>';
vtab := varColumn(null);
for i in 1..ncols
loop
vtab.extend;
DBMS_SQL.DEFINE_COLUMN (cur, i, vtab(i), 2000);
--dbms_output.put_line(vtab(i));
end loop;
v_status := DBMS_SQL.EXECUTE (cur);
LOOP
p_content := p_content || '<tr>';
EXIT WHEN (DBMS_SQL.FETCH_ROWS (cur) <= 0);
FOR i IN 1 ..ncols
loop
DBMS_SQL.COLUMN_VALUE (cur, i, vtab(i));
-- p_content := p_content || '<td>' || 'xyz' || '</td>';
p_content := p_content || '<td>' || vtab(i) || '</td>';
END LOOP;
p_content := p_content || '</tr>' ;
END LOOP;
p_content := p_content || '<table>' ;
DBMS_SQL.CLOSE_CURSOR (cur);
exception
when others then
     p_content := '<td>Exception Error in printing data</td><table>' ;
DBMS_SQL.CLOSE_CURSOR (cur);
end;
procedure excel_footer( p_footer in out nocopy clob)
as
begin
p_footer := '</body></html>';
end;
PROCEDURE get_usable_sql (p_sql_in IN clob, p_sql_out OUT clob)
IS
v_sql clob;
v_names DBMS_SQL.varchar2_table;
v_pos NUMBER;
v_length NUMBER;
v_exit NUMBER;
BEGIN
v_sql := p_sql_in;
v_names := wwv_flow_utilities.get_binds (v_sql);
FOR i IN 1 .. v_names.COUNT
LOOP
<<do_it_again>>
v_pos := INSTR (LOWER (v_sql), LOWER (v_names (i)));
v_length := LENGTH (LOWER (v_names (i)));
v_sql :=
SUBSTR (v_sql, 1, v_pos - 1)
|| v_names (i)
|| SUBSTR (v_sql, v_pos + v_length);
v_sql :=
REPLACE (v_sql,
UPPER (v_names (i)),
'(SELECT v('''
|| LTRIM (v_names (i), ':')
|| ''') FROM DUAL)'
IF INSTR (LOWER (v_sql), LOWER (v_names (i))) > 0
THEN
GOTO do_it_again;
END IF;
END LOOP;
p_sql_out := v_sql;
END;
END export_pkg_spread_sheet;
After creating the package pass the parameter to package like this
begin
export_pkg_spread_sheet.download_excel('select * from emp');
end;
Package will allow to download the spread shreet. If i try to pass the a complex query to package it is returning error as mentioned below
ORA-06502: PL/SQL: numeric or value error
In the above package there is a procedure called procedure excel_content which actuall prints the data in the spread sheet this is where the error is coming from there is a variable called vsql have declared it as clob to hold large string but still i am getting the same error when trying to pass a big string.
Please check the error and let me know.
Thanks
Sudhir

Hi Praveen,
This is the query i am using to pass
Declare
qry clob;
Begin
qry := ' 'SELECT
AR.REGION_CODE,
AR.DISTRICT_CODE,
AR.TERRITORY_CODE,
CASE
WHEN AR.REGION_NAME IS NOT NULL AND AR.DISTRICT_NAME IS NULL AND AR.TERRITORY_NAME IS NULL THEN
AR.REGION_NAME
WHEN AR.REGION_NAME IS NOT NULL AND AR.DISTRICT_NAME IS NOT NULL AND AR.TERRITORY_NAME IS NULL THEN
AR.DISTRICT_NAME
WHEN AR.REGION_NAME IS NOT NULL AND AR.DISTRICT_NAME IS NOT NULL AND AR.TERRITORY_NAME IS NOT NULL THEN
AR.TERRITORY_NAME
END TERR_NAME,
AR.EMPLOYEE_ID,
AR.LAST_NAME,
AR.FIRST_NAME,
AR.GENDER,
AR.DATE_OF_HIRE,
AR.PROJECT_EMPLOYEE_TITLE_ID,
AR.COMPANY_ID,
AR.CUSTOMER_EMAIL,
AR.BUSINESS_EMAIL,
AR.CUSTOMER_VOICEMAIL,
AR.CUSTOMER_VOICEMAIL_EXT,
AR.QUINTILES_VOICEMAIL,
AR.QUINTILES_VOICEMAIL_EXT , complete_roster_pkg_report.AR_F_ADDRESS_GET_LINE_1(AR.PROJECT_ID,AR.EMPLOYEE_ID,1 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Shipping_ADDRESS_TYPE_1" , complete_roster_pkg_report.AR_F_ADDRESS_GET_LINE_2(AR.PROJECT_ID,AR.EMPLOYEE_ID,1 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Shipping_ADDRESS_TYPE_2" , complete_roster_pkg_report.AR_F_ADDRESS_GET_PHONE(AR.PROJECT_ID,AR.EMPLOYEE_ID,1 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Shipping_Phone" , complete_roster_pkg_report.AR_F_ADDRESS_GET_CITY_TOWN(AR.PROJECT_ID,AR.EMPLOYEE_ID,1 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Shipping_City_Town" , complete_roster_pkg_report.AR_F_ADDRESS_GET_COUNTRY_NAME(AR.PROJECT_ID,AR.EMPLOYEE_ID,1 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Shipping_Country_Name" , complete_roster_pkg_report.AR_F_ADDRESS_GET_STATE_NAME(AR.PROJECT_ID,AR.EMPLOYEE_ID,1 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Shipping_State_Name" , complete_roster_pkg_report.AR_F_ADDRESS_GET_ZIP_POSTAL(AR.PROJECT_ID,AR.EMPLOYEE_ID,1 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Shipping_ZipCode" , complete_roster_pkg_report.AR_F_ADDRESS_GET_LINE_1(AR.PROJECT_ID,AR.EMPLOYEE_ID,3 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Storage_ADDRESS_TYPE_1" , complete_roster_pkg_report.AR_F_ADDRESS_GET_LINE_2(AR.PROJECT_ID,AR.EMPLOYEE_ID,3 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Storage_ADDRESS_TYPE_2" , complete_roster_pkg_report.AR_F_ADDRESS_GET_PHONE(AR.PROJECT_ID,AR.EMPLOYEE_ID,3 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Storage_Phone" , complete_roster_pkg_report.AR_F_ADDRESS_GET_CITY_TOWN(AR.PROJECT_ID,AR.EMPLOYEE_ID,3 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Storage_City_Town" , complete_roster_pkg_report.AR_F_ADDRESS_GET_COUNTRY_NAME(AR.PROJECT_ID,AR.EMPLOYEE_ID,3 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Storage_Country_Name" , complete_roster_pkg_report.AR_F_ADDRESS_GET_STATE_NAME(AR.PROJECT_ID,AR.EMPLOYEE_ID,3 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Storage_State_Name" , complete_roster_pkg_report.AR_F_ADDRESS_GET_ZIP_POSTAL(AR.PROJECT_ID,AR.EMPLOYEE_ID,3 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Storage_ZipCode" , complete_roster_pkg_report.AR_F_ADDRESS_GET_LINE_1(AR.PROJECT_ID,AR.EMPLOYEE_ID,4 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Home_ADDRESS_TYPE_1" , complete_roster_pkg_report.AR_F_ADDRESS_GET_LINE_2(AR.PROJECT_ID,AR.EMPLOYEE_ID,4 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Home_ADDRESS_TYPE_2" , complete_roster_pkg_report.AR_F_ADDRESS_GET_PHONE(AR.PROJECT_ID,AR.EMPLOYEE_ID,4 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Home_Phone" , complete_roster_pkg_report.AR_F_ADDRESS_GET_CITY_TOWN(AR.PROJECT_ID,AR.EMPLOYEE_ID,4 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Home_City_Town" , complete_roster_pkg_report.AR_F_ADDRESS_GET_COUNTRY_NAME(AR.PROJECT_ID,AR.EMPLOYEE_ID,4 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Home_Country_Name" , complete_roster_pkg_report.AR_F_ADDRESS_GET_STATE_NAME(AR.PROJECT_ID,AR.EMPLOYEE_ID,4 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Home_State_Name" , complete_roster_pkg_report.AR_F_ADDRESS_GET_ZIP_POSTAL(AR.PROJECT_ID,AR.EMPLOYEE_ID,4 ,TO_DATE(AAH.EFFECTIVE_DATE)) "Home_ZipCode" FROM AR_V_ROSTER AR
LEFT JOIN AR_V_ADDRESS_HISTORY AAH
ON
(AR.PROJECT_ID = AAH.PROJECT_ID AND
AR.EMPLOYEE_ID = AAH.EMPLOYEE_ID)
WHERE
UPPER(AR.USER_EMPLOYEE_ID) = ''Q766730'' AND
AR.PROJECT_ID = 81 ';
export_pkg_spread_sheet.download_excel(qry);
End;
Praveen you can pass your DB table query to check the error. I am trying to pass as mentioned above.
Please let me know if my question is not clear.
Thanks
Sudhir

DBMS_XMLDOM Package Sample

Hello everyone
I need to generate XML output through PL/SQL. Though I had been successful in using DBMS_XMLGEN package, I need to us DBMS_XMLDOM, as I need create hierarchical xml document (ie., Department .....Department Attributes; Employee ....employee attributes....Employee and its attributes within Department node). I was searching for any samples but could not find any. Any help would be appreciated. Also, if I need to approach it in a different way, please let me know about it.
Thank you in advance
VV.

There are some examples of using DBMS_XMLDOM in the online documentation ...
http://download-west.oracle.com/docs/cd/B14117_01/appdev.101/b10790/xdb10pls.htm#sthref1069
Some other options would be to use XMLType Views, the XMLType functions or schema object types and the object based XMLType constructor ...
http://download-west.oracle.com/docs/cd/B14117_01/appdev.101/b10790/xdb14vie.htm#CJIDAFJI
http://download-west.oracle.com/docs/cd/B14117_01/appdev.101/b10790/xdb14vie.htm#i1025417
http://download-west.oracle.com/docs/cd/B14117_01/appdev.101/b10802/t_xml.htm#1009843
http://download-west.oracle.com/docs/cd/B14117_01/appdev.101/b10790/xdb13gen.htm#sthref1166

Save several result of ora xml in a folder

Hello,
I would like to save the result of the ora xml query in one folder. I know that if the result is only one register (one xml file) is:
1. Create a directory
create or replace directory test_dir as 'c:\oracle\test';
2. Run procedure
CREATE OR REPLACE PROCEDURE Getloc3
IS
xmldoc CLOB;
BEGIN
SELECT XMLSerialize(DOCUMENT
... all xmlelement, xmlagg,..)
INTO xmldoc
FROM table;
DBMS_XSLPROCESSOR.clob2file(xmlprolog||xmldoc,'TEST_DIR','index'||TO_CHAR(SYSDATE, 'YYYYMMDD-HH24MISS')||'.xml');
END;
That works if the result is only one register, how can I do if I have several xml file as the result query.
Thanks

That works if the result is only one register, how can I do if I have several xml file as the result query.Not sure what a register means to you.
Do you want to say that the query returns multiple "rows" (or "records")?
If so, just iterate over the result set with a FOR loop :
FOR r IN (
SELECT XMLSerialize(DOCUMENT
XMLElement(
) as xmldoc
FROM table_name
WHERE ...
LOOP
DBMS_XSLPROCESSOR.clob2file(xmlprolog||r.xmldoc, 'TEST_DIR', 'index'||TO_CHAR(SYSDATE, 'YYYYMMDD-HH24MISS')||'.xml');
END LOOP;

Dbms_xmldom package results in ORA-31020

Similar Messages

Maybe you are looking for