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.

Similar Messages

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)

Debugger on Windows Vista - ORA-30683: Failure establishing connection to d

We can't get the debugger to work on our Vista machines... On our XP machines we don't have this problem, so I suspect it's a "Vista" issue.
The vista machine is a desktop running sql developer, connection to another machines (server's) database. XP machines connect and debug on that same database fine.
We get this error when debugging:
Executing PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP('0.0.0.0', '4000')
ORA-30683: Failure establishing connection to debugger
ORA-12541: TNS: no listener
ORA-06512: at "SYS"."DBMS_DEBUG_JDWP", line 68
we've tried:
1) controlling the port on the SQL Developer preferences to be 4000, then making an exception on the firewall (on the vista machien) for that port
2) making an exception for sql developerj.exe files
3) Running it as an administrator
no luck.
I do notice that on teh first line, it puts: CONNECT_TCP('0.0.0.0', '4000')
The zero's... on an xp machine, the IP: 127.0.0.0 would be there instead. Not sure if that's related to the problem.
Please help, we can't debug on our Vista machines until this is resolved.

Definitely. The database needs to be able to contact your PC, so '0.0.0.0' won't work.
Check Preferences - Debugger - Prompt for Debugger Host, initiate another debug session, and when prompted, give your IP instead. Once you had a successful debug session, I'm pretty sure you can uncheck the preference again.
Have fun,
K.

Can we trace the values in a cursor if we debug the package?

Can we trace the values in a cursor if we debug the package having a cursor?
Does it shows cursor attributes like %rowcount,%notfound,%found etc?
Because i am debugging a pachage , and I am getting the exception.
And its after the fetching of a cursor I am hitting on the exception.
If I click the profilier after I debug, its showing the error ora 1775::looping chain of synonyms.
The scenario is after the fetching of cursor, i am hitting the exception and after debug If i see the profilier I am getting the error 1775::looping chain of synonyms.

Firslty, thanks for your time.
I am using the PLSQL developer.
The select command in the cursor picks tha value but when it fetches, it is showing the error.
Any idea what could be the reason.?
FETCH get_notices ----would show ( rowcount =0,%open,first iteration), does that mean cursor is not picking any value?
Because i have checked the select statement and it picks the value.

Cannot Debug SSIS packages in 64 bit mode.

Hi,
To anyone who may be able to help. We are using SQL server 2014 Enterprise addition. Visual studio 2013, SSDT latest version installed, all 64 bit tools installed. I have tried to run my packages with the "Run64bitRuntime"
set to true ( project properties-->Debugging-->Run64BitRuntime = True). Initially I thought it an issues with my package (we migrated them from SSIS 2008R2, they run fine with no issues within the 32 bit memory constraints) so I created
a super simple package with VS 2013 in the SSIS 2014 environment from scratch, a lookup and an OLEDB Data source that's it. Same problem. No matter what I do when I debug in SSIS the 32 bit process (DtsDebugHost.exe (32 bit)) fires up,
even though I have selected debug in 64 bit runtime I cannot get the 64 bit version of DtsDebugHost to run. This is an issue because I am debugging projects that will utilise more than 4GB of memory for say a particular set of lookups. Curiously
when I schedule the projects to run in the scheduler, it fires up a 64 bit process, and the package executes successfully, however if I can't debug in 64 bit mode and leverage the extra memory at the design stage,
this is useless. I have checked obvious things like the path environment variable, thinking perhaps SSIS debug doesn't know where the 64 bit exe is, but it is all fine paths are as they should be. All 64 bit tools/dll's are installed. I
have tested this directly on the server, and on the client machine that I use and the issue is the same. If no one can help me here I guess I can log a support ticket.
thanks in advance.

Hi des_77,
According to your description, you can only debug your SSIS package in 32 bit mode.
Based on my research, I think the issue is caused by 64bit SSIS runtime is not installed on your machine. We can verify the issue by seeing if DtsDebugHost.exe under <Installation Drive>\Program Files\Microsoft SQL Server\120\DTS\Binn or not.
To fix this issue, please install SQL Server and select Integration Services for installation, Setup installs all available 64-bit Integration Services features and tools. Then we can set the Debug Options property Run64BitRuntime to “True”, view the processes
in Windows Task Manager to verify the version of DTDebugHost.exe when debugging the package.
Besides, if the issue still existed, it is my pleasure to help you to reflect your recommendation to the proper department for their consideration. Please feel free to submit your situation on our product to the following link
https://connect.microsoft.com/SQLServer/. Your feedback is valuable for us to improve our products and increase the level of service provided.
References:
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2014/05/22/ssis-packages-executed-from-visual-studio-business-intelligence-development-studio-bids-design-time-on-a-64bit-development-server-goes-to-unresponsive-state-during-package-execution.aspx
http://dougbert.com/blog/post/64-bit-considerations-for-sql-server-integration-services-final.aspx
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

How to debug a Package / function in PL SQL developer ??

How can we debug a Package / function in PL SQL developer ??
i want to debug a code line by line

Karthick_Arp wrote:
This question does not belong to this fourm. We have a {forum:id=260} forum for such question.Not even there Karthick. PL/SQL Developer is a 3rd party tool, not Oracle's SQL Developer, so it doesn't even belong on the Oracle forums.

Compile for Debug Proc/Package Size

Was attempting to debug a package on a DB but when compiling for debug got a message along the lines of 'Pacakge to large' and the compilation finished with warnings.
Is there a max size the compile for debug can handle and if so what is it.
Thanks
Paul

Google gave me this from the Oracle 11.1 PL/SQL Langauge Reference:
>
In the shared memory pool, a package spec, object type spec, standalone subprogram, or anonymous block is limited to 67108864 (2**26) DIANA nodes which correspond to tokens such as identifiers, keywords, operators, and so on. This allows for <b>~6,000,000 lines of code</b>...
>
http://download-west.oracle.com/docs/cd/B28359_01/appdev.111/b28370/limits.htm

Can we debug the package pa_project_pvt.add_class_categories which is called in Pa_project_pub.create_project?

We are trying to create a project using the api code pa_project_pub.create_project. But we are unable to create due to some unexpected error status flag when pa_project_pvt.add_class_categories is executed. We tried by going through the code but it was in vain.
So couple of questions from our side.
1) Can we debug the package procedure pa_project_pvt.add_class_categories by any chance?
2) If yes, then what is the debugging process?
Any help in this regard would be helpful.
Thanks in advance.

Hi,
you may try to enable debugging via Sysadmin responsibility by setting following profile options, either for a certain user (preferred) or a certain responsibility:
- "FND: Debug Log Enabled" set it to yes
- "FND: Debug Log Level" set it to 1 (but only temporarily, as it generates lots of loggings)
- "FND: Debug Log Module" set it to "pa" or "PA"
You'll have to log off and login to apps again for the profile options to come into effect.
Before you start your process, have a look at fnd_log_messages table (write down last value LOG_SEQUENCE,
so you can identify the loggings for your process easier) by filtering column log_sequence, module and user_id
(which is the user_id coming from fnd_user table).
Make sure that you set apps context (fnd_global.apps_initialize) correctly before the logic of your api call starts.
Regards.

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) 같음;

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.

Debug a package

Hello,
I am trying to debug a package.
The package is invooked through a table function like
select * from table(hrs_vu_hrs_vu_xx_fn.get_hrs_vu_xx_fn_lst(2009,8))
where sub_section_id = 33
How can I debug this package, please advise,
Thanks

IQ wrote:
select * from table(hrs_vu_hrs_vu_xx_fn.get_hrs_vu_xx_fn_lst(2009,8))
where sub_section_id = 33 You are aware that having the where clause there like that, will cause the pipelined table function to have to return all rows, right?
Whenever I select from a table function, there's never a where-clause. I supply all necessary context to it, so that it only returns (pipes) the rows that are required.
So in this case, I would:
select *
from table(hrs_vu_hrs_vu_xx_fn.get_hrs_vu_xx_fn_lst(2009,8,33)) -- added third parameter hereAnd change the code of GET_HRS_VU_XX_FN_LST to only pipe the rows that are needed.
Not a answer to your question, just a comment on your code.
Toon

Output Error When Debugging the Package

Hi,
I just created my first SSIS Package, with OLE DB Connection pointing to our Oracle server and using SQL SERVER Destination. When I Debug, I get the following error:
SSIS package "C:\Users\Documents\SQL Server Management Studio\Packageload.dtsx" starting.
Information: 0x4004300A at Load Season, SSIS.Pipeline: Validation phase is beginning.
Error: 0xC0209303 at Packageload, Connection manager "ABCDEF": The requested OLE DB provider MSDAORA.1 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode. Error code: 0x00000000.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".
Error: 0xC020801C at Load Season, OLE DB Source [46]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "ABCDEF" failed with error code 0xC0209303. There may
be error messages posted before this with more information on why the AcquireConnection method call failed.
Error: 0xC0047017 at Load Season, SSIS.Pipeline: OLE DB Source failed validation and returned error code 0xC020801C.
Error: 0xC004700C at Load Season, SSIS.Pipeline: One or more component failed validation.
Error: 0xC0024107 at Load Season: There were errors during task validation.
Warning: 0x80019002 at Packageload: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (5) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches
the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "C:\Users\Documents\SQL Server Management Studio\Packageload.dtsx" finished: Failure.
I tried setting the DelayValidation property to True, but still getting same error.
Thanks
Parul

Hi Parul,
Regarding the error “Unable to bulk copy data. You may need to run this package as an administrator”, it is described in the KB article
http://support.microsoft.com/kb/2009672:
On systems where UAC is enabled, when an application (like SSIS) is launched by an account that is a member of the Administrators group, it gets two security tokens, one a low privileged token and another an elevated token. The elevated token is only
used when the application is explicitly run under an Administrator account by choosing “Run as Administrator” option. By default SSIS always uses the low privileged token resulting in a failure when connecting to a SQL Destination.
The solution is launch the tool (SQL Server Management Studio or Business Intelligence Development Studio or DTExecUI.exe or Command Prompt) as administrator.
Regarding the original error “The requested OLE DB provider MSDAORA.1 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode”, it is because Microsoft OLE DB Provider for Oracle has only 32-bit version. To avoid this issue,
you can either run the package in 32-bit runtime mode as you have done or install the 64-bit Oracle Provider for OLE DB.
If you use Enterprise edition of SSIS 2008 or higher, you can also install the Microsoft Connector for Oracle by Attunity:
http://www.microsoft.com/en-in/download/details.aspx?id=29283
Regards,
Mike Yin
TechNet Community Support

Compile debug causes package to become invalid

We're running 10.2.0.4.0 and I have a large package (7730 lines) which compiles fine on it's own. However, if I try to enable debug mode, I get an error:
SQL> alter package mypkg compile debug package;
Warning: Package altered with compilation errors.
SQL> show errors;
No errors.
If I perform another alter command without the debug parameter, then it compiles fine:
SQL> alter package mypkg compile package;
Package altered.
Also, if I compile this package using the "Compile for Debug" button in SQL Developer then I actually get an error message:
Error(1): PLS-00707: unsupported construct or internal error [2603]
Does anyone have any idea what's going on here? I've spent the past couple days searching for a solution and while I've seen many cases of people having the PLS-00707 error, I wasn't able to find anyone who only receives it when compiling for debug.

SQL> CONN SCOTT
Connected.
SQL> SELECT * fROM V$VERSION;
BANNER
Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
PL/SQL Release 9.2.0.1.0 - Production
CORE 9.2.0.1.0 Production
TNS for 32-bit Windows: Version 9.2.0.1.0 - Production
NLSRTL Version 9.2.0.1.0 - Production
SQL> ALTER PACKAGE P1 COMPILE DEBUG;
Package altered.
SQL> alter session set events='10938 trace name context level 14';
Session altered.
SQL> SELECT P1.ADD_NUM(5,6) FROM DUAL;
SELECT P1.ADD_NUM(5,6) FROM DUAL
ERROR at line 1:
ORA-03113: end-of-file on communication channel
SQL> SELECT NAME FROM V$DATABASE;
SELECT NAME FROM V$DATABASE
ERROR at line 1:
ORA-03114: not connected to ORACLE
SQL> SELECT SYSDATE FROM DUAL;
SELECT SYSDATE FROM DUAL
ERROR at line 1:
ORA-03114: not connected to ORACLE
can one tell me how to solve this problem? thanks in advance.

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.

Debug of package results in ORA-30683

Similar Messages

Maybe you are looking for