R3load error on import with declustering

[MarcinOzdzinski]

Hi

We are installing CRM 7.0 EHP3 on Windows Sybase 16.00.2 and choosen declustering and depooling option.

During import Abap phase there are errors on DOKTL and EDI40 tables:

(DB) ERROR: DDL statement failed

(DROP INDEX "DOKTL"."DOKTL~0")

DbSlExecute: rc = 103

  (SQL error 3701)

  error message returned by DbSl:

[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server

Enterprise]Cannot drop the index 'DOKTL.DOKTL~0', because it doesn't

exist in the system catalogs.

(IMP) INFO: a failed DROP attempt is not necessarily a problem

(DB) ERROR: DDL statement failed

(CREATE UNIQUE INDEX "DOKTL~0" ON "DOKTL" ( "ID", "OBJECT", "LANGU",

"TYP", "DOKVERSION", "LINE" ) with sorted_data )

DbSlExecute: rc = 99

  (SQL error 1581)

  error message returned by DbSl:

[ASE Error SQL1581][SAP][ASE ODBC Driver][Adaptive Server

Enterprise]Create index was aborted because pages in the data only

locked

table are not linked.

(DB) INFO: disconnected from DB

There is a note for this problem:

http://service.sap.com/sap/support/notes/2039613

but our initial R3Load was 742 PL13 and we upgraded to PL23 without any progress.

However in note is statement about R3Load 742 PL10 without "and above" so maybe only this version is OK (don't have access to PL10 to try ) ?

Opened OSS ticket and waiting .....

Regards

MArcin

[MarcinOzdzinski · Accepted solution]

Good to know that there is no support for ASE specific  problems in OSS ......

If any customer will ask for db recommendation i'll have answer .....

[baptiste_vandaele · Accepted solution]

Dear Marcin,

Did you find a solution to your problem?
I'm facing exactly the same situation.

Thanks in advance for your help.
Best regards,

Baptiste

[MarcinOzdzinski · Accepted solution]

No, and no single word from OSS . Cool

[baptiste_vandaele · Accepted solution]

Dear Marcin,

The only solution we found to avoid this error is to choose option for *NOT* decluster/depool DB tables. We restarted the whole process and everything ran OK then. It seems that this process is a little buggy so we finally chose to avoid using it.

I hope it will help you...

Best regards,

Baptiste

[MarcinOzdzinski · Accepted solution]

Hi Baptiste

We did the same tired of  waiting  a week for support , hearing some child excuses from OSS and receiving no action plan in the end.

Another customer will be pissed of during installation , well ....

Thanks for feedback.

Regards

Marcin

[Former Member]

If you don't want to restart your installation note   2039613  ist he solution

Just import a at leaste SP10 of R3load into your kernel