EBCDIC to ASCII conversion

[d_dimas75]

Hello experts,

i'm performing EBCDIC to ASCII conversion in our system and the export (command R3SETUP dbextr.r3s) terminates with the error :

...

...

...

EXP) TABLE: "MCDYNTYPEN"

(EXP) TABLE: "MCDYNUM"

DbSl Trace: Error -904 in function exec_cached_fetch

(EXP) ERROR: DbSlExeRead: rc = 99, table "MCHA"

(SQL error -904)

error message returned by DbSl:

DbSl Trace: SQL error -904 with reason code 13

Resource limit exceeded. Job=323987/DEVCPC/R3LOAD

#STOP: 20100416175601

Thank you,

[d_dimas75]

Hello the above issue has been solved, the problem was that the table MCHA has destroyed indexes.

The export has finished but i'm facing an other issue now at the import phase.I have replay from "R3SETUP dbcptr.r3s" that "command file could not be opened", any idea?

[Former Member]

Hi Dimitri,

typically this happens to me, when I'm in the root directory instead of /tmp/reload/SID

Otherwise, it might be an authorization issue - but I think the recommendation for reload is QSECOFR anyway, isn't it ?

Are you doing InPlace or Export/Import ?

Do you have this file located in /tmp/reload/SID ?

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

[d_dimas75]

Hi Volker,

we are using Export/Import procedure.The import run with QSECOFR but i'm not sure what file is trying to find.

Dimitrios

[d_dimas75]

the issue seems to be solved,running the "R3SETUP -f dbcptr.r3s" instead of "R3SETUP dbcptr.r3s" has started the import

Edited by: DimitrisDimas on Jul 7, 2010 4:30 PM

[d_dimas75]

Once more the installation stopped with error...

ERROR 2010-07-07 17:33:50 DBR3LOADEXEC_IND_DB4ASCII R3loadPrepare:0

Child exited with error: rc = 2

child_pid = 3

See logfile SAPAPPL0.log for further information

.

.

.

ERROR 2010-07-07 17:34:33 DBR3LOADEXEC_IND_DB4ASCII R3loadPrepare:0

Child exited with error: rc = 2

child_pid = 3

See logfile SAPAPPL1_10.log for further information

.

.

.ERROR 2010-07-07 17:36:01 DBR3LOADEXEC_IND_DB4ASCII R3loadPrepare:0

Processes started: 46

Ended with error: 2

load tool ended with error.

See above SAP*.log errors.

Error: Can not unlock the LogWriter.

Possible reasons:

No permissions to set the lock

Error: Can not lock the LogWriter.

Possible reasons:

No permissions to set the lock

Error: Can not unlock the LogWriter.

ERROR 2010-07-07 17:36:04 DBR3LOADEXEC_IND_DB4ASCII InstallationDo:0

Phase failed.

The message in "SAPAPPL0.log" is that

"(IMP) ERROR: SQL statement failed: DROP TABLE "MCHA"

MCHA in *LIBL not table, view, or physical file.

" and in "SAPAPPL1_10.log" is

"#Trying to create primary key "S602+0"

(IMP) ERROR: CREATE statement failed for object "S602"

(ALTER TABLE R3DEVDATA/"S602" ADD CONSTRAINT "S602+0" PRIMARY KEY ( "MANDT", "SSOUR", "VRSIO", "SPMON", "SPTAG", "SPWOC", "SPBUP", "VKORG", "VTWEG", "ZZIDIWTIS", "PRODH", "MATNR", "WERKS" ))

DbSlExecute: rc = 99

(SQL error -603)

error message returned by DbSl:

Unique index cannot be created because of duplicate keys. "

[Former Member]

Hi Dimitri,

... then you should have a look at the trouble shooting section how to prevent duplicate keys ...

I do hope, that you were using the environment variable for the greece codepage ...

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de

[d_dimas75]

Hi Volker,

the problem with S602 is solved but the one with MCHA remains. It seems that this table has not been exported. Checking the export log, the table has been exported successfully ....

Also the MCHA is solved, the R3SETUP found a *savf of this table in QGPL and we had to rename this in order to proceed.

The system is up and running and all the post steps are done except the report DB4_APQD that stops with memory problem(TSV....). Increasing the memory parameters had no result as it has more than 1.000.000 entries.

Reports RSBDCREO, RSBDC_REORG and transaction SM35 did not reduced the table as much we need. Is it save to clear this table?Is there any way for the report DB4_APQD to finish? i have already open a OSS message to SAP but a have no answer till now.

The solution was the report : DB4_APQD_LARGE

Edited by: DimitrisDimas on Jul 15, 2010 3:09 PM

Edited by: DimitrisDimas on Jul 15, 2010 4:40 PM

[Former Member]

Hi Dimitri,

did you already try to delete the SQL Packs and repeat ?

Normally, this creates reason code 7, I think, I never had 13, but at least a try ...

Otherwise, you should have a look at your PTFs. If they are current, you should then open a ticket with bc-db-db4.

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de