Error during System Copy Export Preperations

[Former Member]

Hello Experts,

I am supposed to perform a heterogeneous system copy from windows/Ms-SQL environment to Linux/MAX-DB. I am performing the DB export on the source system where I get this error during Export Preperation.

ERROR: Select for get_rowcnt failed (table "SOTR_TEXT")

Could not continue scan with NOLOCK due to data movement.

ERROR: init_table: get_rowcnt failed

Its coming during R3szchk job.

Has anyone faced this kind of error before? How do you think we should resolve this?

Any pointers to any other threads would be appreciated.

Thanks!

Rahul.

[markus_doehr2 · Accepted solution]

> I am supposed to perform a heterogeneous system copy from windows/Ms-SQL environment to Linux/MAX-DB. I am performing the DB export on the source system where I get this error during Export Preperation.

Just as additional info: Heterogeneous copies require a certified migration consultant on-site, otherwise you'll loose support for the migration itself and for the target system (see http://service.sap.com/osdbmigration --> FAQ).

> ERROR: Select for get_rowcnt failed (table "SOTR_TEXT")

> Could not continue scan with NOLOCK due to data movement.

This can mean that you have a physical corruption on the database. I suggest you run a database verify and check if it finds any errors.

Markus

[Former Member · Accepted solution]

Hi all,

I have done system copy from DEV to QAS, While Export the database ur SAP should OFFLINE.

for more detail Please check below links.

http://www.sdn.sap.com/irj/sdn/systemcopy.

Santosh Kumar Shakya

+919810333190

[Former Member · Accepted solution]

Santosh,

Did you really mean the reply? SAP system was obviously offline. Please refrain from such opaque replies and read the rules of postings before answering.

Thanks!

Rahul.

[former_member189546]

Hello,

The phase R3SZCHK has to traverse each table and

calculate the table size using a very time consuming SQL statement

(select count (*) from tab).

Make sure you have most up to date R3SZCHK

Also make sure the statistics are up to date for the tables.

For the Maxdb side check note 129352

regards,

John Feely