Error during export of xi-objects

Hi,
I get an strange error when trying to export objects from the repository and directory using "Transport Using File System". The error says "Error during export".
First we got the error "Internal error during pvc call: No space left on device" but this error disappeared without any actions from us and there is space left on the server.
Please help
Regards
Claes

Hi VJ,
It only says "Error during export".
/C

Similar Messages

Error during export of J2EE_CONFIGENTRY

Hi,
While doing homogeneous system copy for CRM 2007 System it gives Error during export of J2EE_CONFIGENTRY.
below is the detail error report.
15.04.09 14:01:29 com.sap.inst.jload.Jload dbExport
SEVERE: Error during export of J2EE_CONFIGENTRY
15.04.09 14:01:29 com.sap.inst.jload.Jload logStackTrace
SEVERE: java.lang.NullPointerException
     at com.sap.sql.jdbc.mss.MssSQLExceptionAnalyzer.getCategory(MssSQLExceptionAnalyzer.java:112)
     at com.sap.sql.services.core.CoreServices.isDuplicateKeyException(CoreServices.java:133)
     at com.sap.sql.jdbc.direct.DirectPreparedStatement.processSQLException(DirectPreparedStatement.java:1189)
     at com.sap.sql.jdbc.direct.DirectPreparedStatement.executeQuery(DirectPreparedStatement.java:285)
     at com.sap.sql.jdbc.common.CommonPreparedStatement.executeQuery(CommonPreparedStatement.java:185)
     at com.sap.inst.jload.db.DBTable.unload(DBTable.java:192)
     at com.sap.inst.jload.Jload.dbExport(Jload.java:179)
     at com.sap.inst.jload.Jload.executeJob(Jload.java:395)
     at com.sap.inst.jload.Jload.main(Jload.java:621)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
15.04.09 14:01:29 com.sap.inst.jload.db.DBConnection disconnect
INFO: disconnected
Thanks & Regards
Raj Kiran

Hi,
Search for sap notes on "J2EE_CONFIGENTRY"
service.sap.com/notes
You can get a better solution there.
Thanks and Regards
Jaianandh V

ERPI Error during Export data to GL for period 2012

Hi, experts
When I write back data from Planning to EBS, I encounter the following error during Export data to GL for period 2012. I have confirmed that Planning data has been upload to ERPI.
Do you have any hints on this error for me? Thanks a lot.
Log:
,COALESCE(ppa.YEARTARGET, pp.YEARTARGET) YEARTARGET
,CASE
WHEN (INSTR(UPPER(wld.TEMP_COLUMN_NAME),'AMOUNT',1) = 1) THEN
CAST(SUBSTR(wld.TEMP_COLUMN_NAME,7,LENGTH(wld.TEMP_COLUMN_NAME)) AS NUMERIC(15,0))
ELSE 0
END ENTITY_NAME_ORDER
FROM (
AIF_WRITEBACK_LOAD_DTLS wld
LEFT OUTER JOIN TPOVPERIODADAPTOR_FLAT_V ppa
ON ppa.INTSYSTEMKEY = 'JC2PLN'
AND ppa.PERIODTARGET = wld.DIMENSION_NAME
AND ppa.YEARTARGET = 'FY12'
) LEFT OUTER JOIN TPOVPERIOD_FLAT_V pp
ON pp.PERIODTARGET = wld.DIMENSION_NAME
AND pp.YEARTARGET = 'FY12'
WHERE wld.LOADID = 176
AND wld.COLUMN_TYPE = 'DATA'
) query
GROUP BY PERIODTARGET
,YEARTARGET
,ENTITY_NAME_ORDER
) q
,TPOVPERIOD p
,AIF_GL_PERIODS_STG prd
WHERE p.PERIODKEY = q.PERIODKEY
AND NOT EXISTS (
SELECT 1
FROM AIF_PROCESS_DETAILS pd
WHERE pd.PROCESS_ID = 176
AND pd.ENTITY_TYPE = 'PROCESS_WB_EXP'
AND pd.ENTITY_ID = prd.YEAR
AND prd.SOURCE_SYSTEM_ID = 3
AND prd.SETID = '0'
AND prd.CALENDAR_ID = '10000'
AND prd.PERIOD_TYPE = 'Month'
AND prd.START_DATE > p.PRIORPERIODKEY
AND prd.START_DATE <= p.PERIODKEY
AND prd.ADJUSTMENT_PERIOD_FLAG = 'N'
ORDER BY prd.YEAR
2012-10-12 11:05:10,078 INFO [AIF]: COMM Writeback Period Processing - Insert Periods into Process Details - END
2012-10-12 11:05:10,516 INFO [AIF]: COMM End Process Detail - Update Process Detail - START
2012-10-12 11:05:10,594 DEBUG [AIF]:
UPDATE AIF_PROCESS_DETAILS
SET STATUS = 'FAILED'
,RECORDS_PROCESSED = CASE
WHEN RECORDS_PROCESSED IS NULL THEN 0
ELSE RECORDS_PROCESSED
END + 0
,EXECUTION_END_TIME = CURRENT_TIMESTAMP
,LAST_UPDATED_BY = CASE
WHEN ('native://DN=cn=911,ou=People,dc=css,dc=hyperion,dc=com?USER' IS NULL) THEN LAST_UPDATED_BY
ELSE 'native://DN=cn=911,ou=People,dc=css,dc=hyperion,dc=com?USER'
END
,LAST_UPDATE_DATE = CURRENT_TIMESTAMP
WHERE PROCESS_ID = 176
AND ENTITY_TYPE = 'PROCESS_WB_EXP'
AND ENTITY_NAME = '2012'
2012-10-12 11:05:10,594 INFO [AIF]: COMM End Process Detail - Update Process Detail - END
2012-10-12 11:05:10,719 INFO [AIF]: ERPI Process End, Process ID: 176

I do not have any hints on this.
Would need to see the ODI Operator when the process is ran.

DRM Batch Client error during export

Hello,
I am experiencing an error when using the DRM Batch Client to execute export books. The same export process fails sometimes and runs to completion successfully at other times. When it fails, it does not always fail in the same place within the export process, and the error is as follows:
2/2/2011 8:31:40 PM - ERemotableException with message: "Server was unable to process request. ---> Error during Export. Export was unable to run. Error: Timeout expired" while running Export Book
2/2/2011 8:31:40 PM - => ERROR: Data Relationship Management Server returned error: "Server was unable to process request. ---> Error during Export. Export was unable to run. Error: Timeout expired."
2/2/2011 8:31:40 PM - *** MDMConnect stopping ***
Because this issue is sporadic, it seems like there could be a few possible causes:
1. Network issues
2. SQL connection/time-out issues -- These particular exports are writing to SQL tables versus flat files
3. Am wondering if there are any known issues with the MDMConnect? Or are there time-out settings we can adjust?
We currently have our in-house IT chasing down any possible network or SQL issues. Does anyone know of any issues with the batch client, or have ideas on any other possible causes? Any help is greatly appreciated. Thanks!
EJ

There is a timeout setting in DRM system preferences and there are mulitlple session timeout settings in IIS that you may need to configure. Try the system preference first. For very large jobs, ie. hundreds of thousands of nodes with hundreds of properties per node, you'll need to update settings in IIS as well.

[Error during Export] R3load exited with return code 11

Hi guys,
While performing and Unicode Migration, during Export Phase, Migration Monitor returned the following error while exporting a package
ERROR: 2014-06-01 10:57:44 com.sap.inst.migmon.LoadTask run
Unloading of 'REGUC' export package is interrupted with R3load error.
Process '/usr/sap/ECP/DVEBMGS00/exe/R3load -e REGUC.cmd -datacodepage 4102 -l REGUC.log -stop_on_error' exited with return code 11.
For mode details see 'REGUC.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
REGUC.log details:
(As you see, it does not provide reasons of this error, all messages are informative and alike all other Packages logs)
/usr/sap/ECP/DVEBMGS00/exe/R3load: START OF LOG: 20140601105052
/usr/sap/ECP/DVEBMGS00/exe/R3load: sccsid @(#) $Id: //bas/740_REL/src/R3ld/R3load/R3ldmain.c#4 $ SAP
/usr/sap/ECP/DVEBMGS00/exe/R3load: version R7.40/V1.8
Compiled Jul 23 2013 21:30:53
/usr/sap/ECP/DVEBMGS00/exe/R3load -e REGUC.cmd -datacodepage 4102 -l REGUC.log -stop_on_error
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): US7ASCII
(EXP) INFO: check NameTab widths: Ok.
(DB) INFO: Export without hintfile
(RSCP) INFO: UMGCOMCHAR read check, OK.
(RSCP) INFO: environment variable "I18N_POOL_WIDTH" is not set. Checks are active.
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
(RSCP) INFO: UMGSETTINGS nametab creation: ok.
(RSCP) INFO: Global fallback code page = 1160
(RSCP) INFO: Common character set is not 7-bit-ASCII
(RSCP) INFO: Collision resolution method is 'fine'
(RSCP) INFO: R3trans code pages = Normal
(RSCP) INFO: EXPORT TO ... code pages = Normal
(RSCP) INFO: Check for invalid language keys: activated
(RSCP) INFO: I18N_NAMETAB_NORM_ALLOW = 999999999
(RSCP) INFO: I18N_NAMETAB_NORM_LOG   = 1000000002
(RSCP) INFO: I18N_NAMETAB_ALT_ALLOW = 10000
(RSCP) INFO: I18N_NAMETAB_ALT_LOG    = 10003
(RSCP) INFO: I18N_NAMETAB_OLD_ALLOW = 0
(RSCP) INFO: I18N_NAMETAB_OLD_LOG    = 500
(RSCP) INFO: init SUMG interface (3#$Revision: #1 $); package name: "REGUC".
(RSCP) INFO: "REGUC001.xml" created.
(GSI) INFO: dbname   = "ECP20030615080638
(GSI) INFO: vname    = "ORACLE "
(GSI) INFO: hostname = "ecp "
(GSI) INFO: sysname = "SunOS"
(GSI) INFO: nodename = "ecp"
(GSI) INFO: release = "5.10"
(GSI) INFO: version = "Generic_142900-13"
(GSI) INFO: machine = "sun4u"
Tried to find what does R3load Return Code 11 means, but I couldnt find further information on this.
Any hint of what is causing this error?
(Please disregard any Filesystem issues since all of them have available space)
Best!

After using latest R3load patch, it provides furher information on the log file.
-------------------- Start of patch information ------------------------
patchinfo (patches.h): (0.070) R3ldctl: fix CDS views creation in upgrade export mode (note 2
017805)
DBSL patchinfo (patches.h): (0.022) Smaller corrections in release 7.40 (th, dp, vmc, dpmon)
(note 1821404)
--------------------- End of patch information -------------------------
process id 27326
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): US7ASCII
(EXP) INFO: check NameTab widths: Ok.
(DB) INFO: Export without hintfile
(RSCP) INFO: UMGCOMCHAR read check, OK.
(RSCP) INFO: environment variable "I18N_POOL_WIDTH" is not set. Checks are active.
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
(RSCP) INFO: UMGSETTINGS nametab creation: ok.
(RSCP) INFO: Global fallback code page = 1160
(RSCP) INFO: Common character set is not 7-bit-ASCII
(RSCP) INFO: Collision resolution method is 'fine'
(RSCP) INFO: R3trans code pages = Normal
(RSCP) INFO: EXPORT TO ... code pages = Normal
(RSCP) INFO: Check for invalid language keys: activated
(RSCP) INFO: I18N_NAMETAB_NORM_ALLOW = 999999999
(RSCP) INFO: I18N_NAMETAB_NORM_LOG   = 1000000002
(RSCP) INFO: I18N_NAMETAB_ALT_ALLOW = 10000
(RSCP) INFO: I18N_NAMETAB_ALT_LOG    = 10003
(RSCP) INFO: I18N_NAMETAB_OLD_ALLOW = 0
(RSCP) INFO: I18N_NAMETAB_OLD_LOG    = 500
(RSCP) INFO: init SUMG interface (3#$Revision: #1 $); package name: "REGUC".
(RSCP) INFO: "REGUC003.xml" created.
(GSI) INFO: dbname   = "ECP20030615080638
(GSI) INFO: vname    = "ORACLE                          "
(GSI) INFO: hostname = "ecp                                                             "
(GSI) INFO: sysname = "SunOS"
(GSI) INFO: nodename = "ecp"
(GSI) INFO: release = "5.10"
(GSI) INFO: version = "Generic_142900-13"
(GSI) INFO: machine = "sun4u"
(GSI) INFO: instno   = "6120023288"
(RTF) ########## WARNING ###########
        Without ORDER BY PRIMARY KEY the exported data may be unusable for some databases
(RDI) WARNING: /respaldo/ECP_Export/ABAP/DATA/REGUC.STR: cannot find version token "ver:" at line 1
(RDI) WARNING: /respaldo/ECP_Export/ABAP/DATA/REGUC.STR: unknown file format, assuming version 2
(EXP) INFO: table REGUC will be exported with sorting (task modifier)
------------------ C-STACK ----------------------
[0] t_splay ( 0x1020df850, 0xb3, 0x4386, 0x100a02078, 0x0, 0x1020df870 ), at 0xffffffff7b9629
94
[1] t_delete ( 0x1020df850, 0x4348, 0x1d9870, 0x1000d0408, 0xffffffff7bb3c000, 0x0 ), at 0xff
ffffff7b9627e4
[2] realfree ( 0x101ee7590, 0x1f82b1, 0x1d9cd0, 0x1f82b0, 0xffffffff7bb3c000, 0x101ee7590 ),
at 0xffffffff7b9623b0
[3] _malloc_unlocked ( 0x7d40, 0x200000, 0x101edf840, 0x0, 0x101ee7580, 0x0 ), at 0xffffffff7
b961eb4
[4] malloc ( 0x7d39, 0x2388, 0x1da428, 0x10038fe84, 0xffffffff7bb3c000, 0x2000 ), at 0xffffff
ff7b961c28
[5] rstg_get ( 0x2, 0x0, 0x2, 0x7d10, 0x0, 0x10077d8c0 ), at 0x10038ff4c
[6] c3_uc_new_cache ( 0x100a02078, 0x284db0, 0x284c00, 0x10077d8c0, 0x100a02108, 0xb3 ), at 0
x1000d1ce8
[7] c3_uc_seek_cache ( 0xb3, 0xff79, 0xffffffff7ffcae3e, 0x100a02078, 0x10189fa48, 0x10077d8c
0 ), at 0x1000d188c
[8] c3_uc_new_tabcache ( 0x0, 0xb3, 0x4386, 0x100a02078, 0xb3, 0x10077d8c0 ), at 0x1000d13fc
[9] c3_uc_insert_record_in_cache ( 0xffffffff7ffcb04e, 0x10189fa48, 0x100a02078, 0x100a024c8,
0xb3, 0x1058c8f84 ), at 0x1000d0408
[10] c3_uc_insert ( 0x0, 0x100a02078, 0x0, 0x0, 0x10077d8c0, 0xffffffff7ffcb04e ), at 0x1000c
f944
[11] c3_uc_convert_table_entry ( 0x1015c61f8, 0x0, 0x100a02078, 0x0, 0x10189f408, 0x31a000 ),
at 0x1000ce314
[12] c3_uc_convert_logic_table ( 0x1015c61f8, 0x100a02078, 0x0, 0x4a, 0x100638dc0, 0x10077d8c
0 ), at 0x1000cdb18
[13] c3_uc_convert_cluster_data ( 0x100a02078, 0xffffffff7ffcbc50, 0x1015c6428, 0x1015c61f8,
0x10077d8c0, 0x0 ), at 0x1000cd10c
[14] c3_uc_convert_cluster_item ( 0xffffffff7ffcbc78, 0xffffffff7ffcbc50, 0x100954770, 0x1038
6f6e0, 0xffffffff7ffcbb8c, 0x100a02812 ), at 0x1000be1d4
[15] process_task ( 0xffffffff7ffcbc78, 0xffffffff7ffcbc50, 0x100954770, 0x100a02810, 0x10063
32e0, 0x10077d8c0 ), at 0x1000b2f58
[16] CnvCluster ( 0x1014642d0, 0x100954670, 0x100aa9610, 0x2849b8, 0x284800, 0x6cb978 ), at 0
x1000b1f8c
[17] cnv_clust2 ( 0x100aa9580, 0xffffffff7ffcc258, 0x100954770, 0xfc0, 0x107d00, 0x100954670
), at 0x100062714
[18] cnv_cp ( 0x100aa9580, 0xffffffff7ffcc258, 0x100aa95e0, 0x0, 0x10077d8c0, 0x1d6c00 ), at
0x100064644
[19] process_buffer ( 0x100aa9580, 0xffffffff7ffcc258, 0xfff00, 0x100a97bd0, 0x10, 0x100aa95b
0 ), at 0x10007162c
[20] execute_table_unload ( 0xffffffff7ffed610, 0xffffffff7ffdc4b0, 0x0, 0x100aa9580, 0xfffff
fff7ffcc258, 0x10077d8c0 ), at 0x10006c488
[21] export_table_task ( 0xffffffff7ffed610, 0x0, 0xffffffff7ffdc368, 0xffffffff7ffcc330, 0xf
fffffff7ffeedb8, 0xffffffff7ffeec60 ), at 0x10006c934
[22] db_unload ( 0x100a97b0d, 0xffffffff7ffed610, 0x0, 0x10077d8c0, 0xffffffff7ffeec60, 0xfff
fffff7bb47540 ), at 0x10006d148
[23] main_r3ldmain ( 0x72ec00, 0xffffffff7ffff448, 0xffffffff7ffff228, 0xffffffff7bb47540, 0x
1005fc290, 0x0 ), at 0x1000514e0

Error during export & import of rules in RAR 5.2

Hi all,
We followed the steps mentioned in exporting & importing the rules as per the Config guide. But we
are receiving the below error during the import of rules. Can anybody please throw a limelight on why this error message is appearing?
"Error in Table Data ==> VIRSA_CC_CRPROF
SQL==>Insert into VIRSA_CC_CRPROF(VSYSKEY,PROFILE,RULESETID,RISKLEVEL,STATUS)Values(??????)
Record==>D VIRSA_CC_CRPROF null"
We also ensured that the downloaded file is not truncated and saved it in a separate folder. Does the file needs to saved in ANSI or Unicode text? We saved in ANSI
Also the background ground job is not getting scheduled automatically during the import of ruels. Is that due to the above error?
Thanks and Best Regards,
Srihari.K

Hello Sri,
background job for generating the rules won`t be scheduled before you upload the file successfully.
The most obvious reason for this error message is that you have line in your file - in table VIRSA_CC_CRPROF that is corrupted. Make sure all lines from table VIRSA_CC_CRPROF have all predefined fields - (VSYSKEY,PROFILE,RULESETID,RISKLEVEL,STATUS).
If you keep hiting this problem just delete this table, after the upload you`ll add the critical profiles manually - I bet you don`t have many of them.
Also from my experience I always choose to save the downloaded file in UNICODE UTF-8 format.
Once the file is saved in other format, there`s no use of it, download it again and save directly in Unicode.
Make sure you don`t have empty fields, even in the fields where you don`t have values, you must leave space, otherwise you`ll keep hitting the same issue.
Regards,
Iliya

Essbase Version 11 Error During Export

Hi,
I have just installed Hyperion Essbase version 11 on windows 2003 Server, It’s a fresh install on new machine. I am getting following error during nightly backup.
After "Calc All" we export data to the following location. Hyperion\APP\DB. Same Maxl script works fine on version 7 of Essbase. If i export data manually its works fine, only issue i have during nightly back (Automated). Data size is 1.4 GB; Please let me know if you need some more information.
Error.. *ERROR - 1005000 - Ascii Backup: Failed to open [\PLAN\TEST\TEST_Export_AllData_1.txt]..*
Maxl Script:
MAXL> export database "PLAN"."TEST" all data to data_file
2>      "'\\PLAN\\TEST\\TEST_Export_AllData_1.txt'",
3>      "'\\PLAN\\TEST\\TEST_Export_AllData_2.txt'";
Error:
OK/INFO - 1019020 - Writing Free Space Information For Database [TEST].
OK/INFO - 1005029 - Parallel export enabled: Number of export threads [2].
*ERROR - 1005000 - Ascii Backup: Failed to open [\PLAN\TEST\TEST_Export_AllData_1.txt]..*
MaxL Shell completed with error
Thank you,
T.Khan

I tried with other path and it works. I really appreciate all your help. I used following maxl
export database "Plan"."Test" all data to data_file
C:\Hyperion\products\Essbase\EssbaseServer\app\PLAN\TEST\Export_AllDtata_1.txt,
C:\Hyperion\products\Essbase\EssbaseServer\app\PLAN\TEST\Export_AllDtata_2.txt;
What changes I need to make on my maxl. Do I need to make any changes on Variables? Here is my current Maxl
/*      Export Database                              */
/* Environment Variables: (set by calling script)               */
/* $ess_UserName      - Essbase username                     */
/* $ess_Password     - Essbase password                    */
/* $ess_Server          - Essbase server                    */
/* Local variables: (set by MaxL script)                    */
/* $APP               - Essbase application ($1 positional parameter)     */
/* $DB               - Essbase database ($2 positional parameter)     */
/* Any error returned from a MaxL command causes the               */
/* logic to branch to an error exit at end of the script           */
/* set local variables to values of positional parameters */
set APP=$1;
set DB=$2;
/* Login to Essbase */
login $ess_UserName $ess_Password on $ess_Server;
/* Export database in parallel to the database directory - all data */
export database "$APP"."$DB" all data to data_file
     "'\\$APP\\$DB\\$(DB)_Export_AllData_1.txt'",
     "'\\$APP\\$DB\\$(DB)_Export_AllData_2.txt'";
iferror 'ERROREXIT';
/* Normal Exit */
Thank You
T.Khan

Error - During Export Grid Data to CSV

OS: Windows XP
Detail: Eror Message Pop-Up During Export Grid Data to CSV. Error Message:
ORA-00972: identifier is too long
Vendor code 972.

There is a bug with all export formats if you are exporting without using aliases and you export a long text string (see More export issues/bugs
This will fail:
select 'testing query execution on export' from dual
This will work:
select 'testing query execution on export' dummy from dual

Error during Export of MAXDB

Hi,
   I am trying to export MAXDB and getting the following error during the R3szchk phase where it is getting terminated at the following point SAPDDIM.STR exits with error code 1......

Hi,
Please find the details of the log file below.
INFO: processing SAPSDIC.STR
INFO: processing SAPUSER.STR
DbSl Trace:   execute() of C_0001, #rec=0, rc=1, rcSQL=-942 (POS(59) Unknown table name:__TABLE_SIZES__)
ERROR: dbdd_get_size() rc = 2
error message: POS(59) Unknown table name:__TABLE_SIZES__
INFO: processing SAPAPPL1.STR
INFO: processing SAPAPPL0.STR
INFO: processing SAPAPPL2.STR
INFO: processing SAPSDOCU.STR
DbSl Trace:   execute() of C_0001, #rec=0, rc=1, rcSQL=-942 (POS(59) Unknown table name:__TABLE_SIZES__)
ERROR: dbdd_get_size() rc = 2
error message: POS(59) Unknown table name:__TABLE_SIZES__
INFO: processing SAPSSEXC.STR
INFO: processing SAPSSRC.STR
DbSl Trace:   execute() of C_0001, #rec=0, rc=1, rcSQL=-942 (POS(59) Unknown table name:__TABLE_SIZES__)
ERROR: dbdd_get_size() rc = 2
error message: POS(59) Unknown table name:__TABLE_SIZES__
INFO: processing SAPSPROT.STR
INFO: processing SAPPOOL.STR
DbSl Trace:   execute() of C_0001, #rec=0, rc=1, rcSQL=-942 (POS(59) Unknown table name:__TABLE_SIZES__)
ERROR: dbdd_get_size() rc = 2
error message: POS(59) Unknown table name:__TABLE_SIZES__
INFO: processing SAPSLOAD.STR
DbSl Trace:   execute() of C_0001, #rec=0, rc=1, rcSQL=-942 (POS(59) Unknown table name:__TABLE_SIZES__)
ERROR: dbdd_get_size() rc = 2
error message: POS(59) Unknown table name:__TABLE_SIZES__
INFO: processing SAPCLUST.STR
DbSl Trace:   execute() of C_0001, #rec=0, rc=1, rcSQL=-942 (POS(59) Unknown table name:__TABLE_SIZES__)
ERROR: dbdd_get_size() rc = 2
error message: POS(59) Unknown table name:__TABLE_SIZES__
INFO: processing SAPSLEXC.STR
DbSl Trace:   execute() of C_0001, #rec=0, rc=1, rcSQL=-942 (POS(59) Unknown table name:__TABLE_SIZES__)
ERROR: dbdd_get_size() rc = 2
error message: POS(59) Unknown table name:__TABLE_SIZES__
INFO: processing SAP0000.STR
DbSl Trace:   execute() of C_0001, #rec=0, rc=1, rcSQL=-942 (POS(59) Unknown table name:__TABLE_SIZES__)
ERROR: dbdd_get_size() rc = 2
error message: POS(59) Unknown table name:__TABLE_SIZES__
INFO: processing SAPDODS.STR
DbSl Trace:   execute() of C_0001, #rec=0, rc=1, rcSQL=-942 (POS(59) Unknown table name:__TABLE_SIZES__)
ERROR: dbdd_get_size() rc = 2
error message: POS(59) Unknown table name:__TABLE_SIZES__
INFO: processing SAPDFACT.STR
DbSl Trace:   execute() of C_0001, #rec=0, rc=1, rcSQL=-942 (POS(59) Unknown table name:__TABLE_SIZES__)
ERROR: dbdd_get_size() rc = 2
error message: POS(59) Unknown table name:__TABLE_SIZES__
INFO: processing SAPDDIM.STR
DbSl Trace:   execute() of C_0001, #rec=0, rc=1, rcSQL=-942 (POS(59) Unknown table name:__TABLE_SIZES__)
ERROR: dbdd_get_size() rc = 2
error message: POS(59) Unknown table name:__TABLE_SIZES__
Regards
Balaji

Ora-00904 error during Export

Hi ,
I am facing a problem in export utility 8i database, this is occuring after i installed the packaes required for java stored procedure, any suggestion is appreciated
L:\>exp userid=ubs/ubs owner=scott file=test.dmp log=test.log
Export: Release 8.1.7.0.0 - Production on Tue Jul 9 13:37:31 2002
(c) Copyright 2000 Oracle Corporation. All rights reserved.
Connected to: Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
Export done in WE8ISO8859P1 character set and UTF8 NCHAR character set
server uses UTF8 character set (possible charset conversion)
About to export specified users ...
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user SCOTT
. exporting object type definitions for user SCOTT
About to export SCOTT's objects ...
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
. about to export SCOTT's tables via Conventional Path ...
. . exporting table TEMP 0 rows exported
. exporting synonyms
EXP-00008: ORACLE error 904 encountered
ORA-00904: invalid column name
EXP-00000: Export terminated unsuccessfully
thankyou in advance for a reply
Regards
bala

It might be that you have not ran the exp script to build the correct views.
Some applications build tables with double quotes around them to force the table or view names to lower case. exp doesn't play well with that. You may have to go through and rename all the objects that were creates case specific.

"unexpected error" during export to html

I absolutely love the new feature to export flash to javascript/html. However with a particularly complex animation I'm building I keep getting this error when I try to test or publish the file. Through process of elimination I know that this error is caused because there is too much going on in my project.
So my question is this: Is there a maximum capacity for flash's new html document feature?
I'm creating an animation where line art city gets built up, and the only way I know how to do this is put individual keyframes for each step of the way. I have only about 10 keyframes and it throughs this error, but I'm also wondering if there's a better approach I could be taking to making my project do what I want. I've built similar animations in this way, and they all have worked fine, but I assume they worked because there was less complexity going on in them. I suspect the error is cause because the animation has to draw each intricate detail for every keyframe, and this ends up being an extremely large javascript file.
Any and all help would be greatly appreciated. Thanks!
Here's an image of the error:

Hi,
Can you please share the fla file for which you are facing the error on export?
Thanks!
Mohan

Error during import of business object BOREPMA (crystal reports)

Dear Colleagues,
we have a problem with importing of crystal reports into productive system,
export works fine - I get .car files, but import finished with error : "Error occurred in data conversion".
We could not find any reason for this error..... may be someone had same issue in the past?
How can I check what happens in background during import?
Thank you very much for response

Hi Nick,
our problem is following: we changed *existing crystal report* on development workstation, and trying to import to q-workstation, as it was not possible, we made changes on q-workstation and trying to import to productive-workstation. We don't have crystal report designer on productive workstation and it is a reason why we can not create new report with same name as you suggested (on productive workstation).
In general, how should crystal reports be transferred between different systems (development, test,, productive) if you have crystal report designer only on development system? We think the export-import function can do this, but there is a data conversion error.... OSS message is created since 9 month, we don't get really solution from SAP...
Did you had the same problem or you have crystal report designer on productive workstation and can change coding there?
Thank you very much
Best rehgards
Natalia Barannikov

Decimal Conversion Error During Export

Hi All
We are migrating our production system from HP-UX to SOLARIS and Informix to Oracle.
During the export phase for the process SAPAPPL1 terminates with error :
DbSl Trace: Error in decimal conversion. Length: 5, Decimals: 0
(EXP) ERROR: DbSlExeRead: rc = 2, table "S011"
(SQL error 0)
error message returned by DbSl:
I am not able to get hold of it.
Kindly help, if someone has experience on the same.
Regards
Rahul

Hi Rahul,
What is your kernel release? Please confirm that you are in latest kernel and using the latest version of R3load.
Regards,
Satyabrat

Error during transport of info object

Dear all,
We are using BI7.0 During transport of the infoobject "0MAINTPOS" the following error is appearing.
Start of the after-import method RS_IOBJ_AFTER_IMPORT for object type(s) IOBJ (Activation Mode)
Characteristic 0CM_CTAR: Unit 0UNIT_DIM no allowed in compounding
Characteristic 0CM_SHAR: Unit 0AREA_UNIT no allowed in compounding
Can anyone tell what has to be done to get this error solved.
Regards,
M.Magesh

MM,
Please refer
Re: inactive info objects in BI Content
Re: Unit no allowed in compounding
Hope it helps.

Error during export of ECC 6.0 system for unicode conversion

We have upgraded a 4.7 system to ECC 6.0 running on MSSQL 2000. We have the latest r3load, and are using the Netweaver 7.0 sapinst to perform the system copy (export) to convert to unicode. Our goal is an exported system which we can use on a clean install once we have de-installed SAP and SQL 2000 and installed MSSQL 2005.
When running the export, the r3szchk finishes and then the next phase runs. But it gets almost all errors (so we are stopping the export).
The export_monitor.log is shown below, and also an example of one of the table logs shown here as well. but its almost as if every table hits the same problem, BSIS, MSEG, EDIDS etc.....
If you look at the ACCTIT.log, it looks like the SQL/stored preocedure error is as follows, but not sure what this means:
check NameTab width SQL DbSlRead on DDNTT_CONV_UC failed for table T002 with rc 24
Export_Monitor.log
==============
NFO: 2008-08-25 17:30:11
Export Monitor is started.
CONFIG: 2008-08-25 17:30:11
Application options:
dataCodepage=4103
dbType=MSS
exportDirs=S:\ABAP
installDir=C:\Program Files\sapinst_instdir\NW04S\LM\COPY\MSS\EXP\CENTRAL\AS\EXP
jobNum=3
loadArgs=-stop_on_error
monitorTimeout=30
orderBy=
r3loadExe=D:\usr\sap\ED0\SYS\exe\run\R3load.exe
sapinst=
server=
trace=all
tskFiles=yes
CONFIG: 2008-08-25 17:30:11
List of packages with table structure: 'SAP0000'.
CONFIG: 2008-08-25 17:30:11
List of packages with views: 'SAPVIEW'.
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask run
Unloading of 'ACCTIT' export package is started.
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask run
Unloading of 'BSIS' export package is started.
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'ACCTIT' export package:
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -ctf E S:\ABAP\DATA\ACCTIT.STR S:\ABAP\DB\DDLMSS.TPL ACCTIT.TSK MSS -l ACCTIT.log
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask run
Unloading of 'CMFP' export package is started.
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'BSIS' export package:
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -ctf E S:\ABAP\DATA\BSIS.STR S:\ABAP\DB\DDLMSS.TPL BSIS.TSK MSS -l BSIS.log
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'CMFP' export package:
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -ctf E S:\ABAP\DATA\CMFP.STR S:\ABAP\DB\DDLMSS.TPL CMFP.TSK MSS -l CMFP.log
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask processPackage
Unloading of 'ACCTIT' export package from database:
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e ACCTIT.cmd -datacodepage 4103 -l ACCTIT.log -stop_on_error
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask processPackage
Unloading of 'CMFP' export package from database:
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e CMFP.cmd -datacodepage 4103 -l CMFP.log -stop_on_error
TRACE: 2008-08-25 17:30:11 com.sap.inst.migmon.LoadTask processPackage
Unloading of 'BSIS' export package from database:
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e BSIS.cmd -datacodepage 4103 -l BSIS.log -stop_on_error
ERROR: 2008-08-25 17:30:12 com.sap.inst.migmon.LoadTask run
Unloading of 'ACCTIT' export package is interrupted with R3load error.
Process 'D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e ACCTIT.cmd -datacodepage 4103 -l ACCTIT.log -stop_on_error' exited with return code 2.
For mode details see 'ACCTIT.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
ERROR: 2008-08-25 17:30:12 com.sap.inst.migmon.LoadTask run
Unloading of 'CMFP' export package is interrupted with R3load error.
Process 'D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e CMFP.cmd -datacodepage 4103 -l CMFP.log -stop_on_error' exited with return code 2.
For mode details see 'CMFP.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
ERROR: 2008-08-25 17:30:12 com.sap.inst.migmon.LoadTask run
Unloading of 'BSIS' export package is interrupted with R3load error.
Process 'D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e BSIS.cmd -datacodepage 4103 -l BSIS.log -stop_on_error' exited with return code 2.
For mode details see 'BSIS.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
etc.....
ACCTIT.log
=========
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: START OF LOG: 20080825191346
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#18 $ SAP
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: version R7.00/V1.4
Compiled Aug 18 2008 23:55:23
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -ctf E S:\ABAP\DATA\ACCTIT.STR S:\ABAP\DB\DDLMSS.TPL ACCTIT.TSK MSS -l ACCTIT.log
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: job completed
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: END OF LOG: 20080825191346
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: START OF LOG: 20080825191347
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#18 $ SAP
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: version R7.00/V1.4
Compiled Aug 18 2008 23:55:23
D:\usr\sap\ED0\SYS\exe\run\R3load.exe -e ACCTIT.cmd -datacodepage 4103 -l ACCTIT.log -stop_on_error
(DB) INFO: connected to DB
(EXP) WARN: check NameTab width SQL DbSlRead on DDNTT_CONV_UC failed for table T002 with rc 24.
(DB) ERROR: DbSlErrorMsg rc = 99
(EXP) WARN: check NameTab width SQL DbSlRead on DDNTT_CONV_UC failed for table CDPOS with rc 24.
(DB) ERROR: DbSlErrorMsg rc = 99
(EXP) WARN: check NameTab width SQL DbSlRead on DDNTT_CONV_UC failed for table TACOB with rc 24.
(DB) ERROR: DbSlErrorMsg rc = 99
(EXP) INFO: check NameTab widths: Ok.
(DB) INFO: Export without hintfile
(RSCP) INFO: UMGCOMCHAR read check, skip: no data found; probably old SPUMG.
(RSCP) INFO: environment variable "I18N_POOL_WIDTH" is not set. Checks are active.
(RSCP) WARN: UMGCONTAINER has 9 more problems.
(RSCP) WARN: UMGSETTINGS nametab creation: status not available, no table entry.
(RSCP) INFO: Global fallback code page = 0000
(RSCP) INFO: Common character set is 7-bit-ASCII
(RSCP) INFO: Collision resolution method is unexpected !
(RSCP) INFO: R3trans code pages = AskSPUMG
(RSCP) INFO: EXPORT TO ... code pages = AskSPUMG
(RSCP) INFO: Check for invalid language keys: active, by default
(RSCP) INFO: I18N_NAMETAB_NORM_ALLOW = 0
(RSCP) INFO: I18N_NAMETAB_NORM_LOG   = 0
(RSCP) INFO: I18N_NAMETAB_ALT_ALLOW = 0
(RSCP) INFO: I18N_NAMETAB_ALT_LOG    = 0
(RSCP) INFO: I18N_NAMETAB_OLD_ALLOW = 0
(RSCP) INFO: I18N_NAMETAB_OLD_LOG    = 0
(GSI) INFO: dbname   = "ED0ecc6dev                                                                                "
(GSI) INFO: vname    = "MSSQL                           "
(GSI) INFO: hostname = "ECC6DEV                                                         "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "ECC6DEV"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 2"
(GSI) INFO: machine = "8x AMD64 Level 6 (Mod 23 Step 6)"
(BEK) ERROR: SAPSYSTEMNAME not in environment
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: job finished with 1 error(s)
D:\usr\sap\ED0\SYS\exe\run\R3load.exe: END OF LOG: 20080825191348

> We will quickly implement the UC as a separate project, not put it off forever.
VERY good decision!
> But as we have single code page, no JAVA integration, no web integration (SOA) etc... the added complexity on our already short timeframe is more than we care to take on at this point.
Happy upgrading!
Our upgrade from 4.7 to ERP 6.0 was one of the smoothest I've made.
Markus

Error during export of xi-objects

Similar Messages

Maybe you are looking for