cancel
Showing results for 
Search instead for 
Did you mean: 

Systemcopy problem by installing the central instance

Former Member
0 Kudos

Hello,

i am trying to make a Systemcopy from the PRD System to QAS System (Release R/3 4.7 X200) ,

and got a error message duringsapinst.exe at Input section:

Error by Dbo objects check Database QAS contains user objects belonging to

system user dbo;

correct reported errors before continuing with the installation.

Step´s to reproduce the problem.

1. Install Windows 2K3 server and Service packs

2. Install the SQL 2000 and patches

3. Create the database and restore the database from the production backup

4. run Sapinst.exe---->nonunicode installation--->Install a Central

Instance--->Local Installation--->Install Additional SAP system into an

existing database------>enter the database name -

-


then got the error

above

I can´t execute the Script user_Change.sql because the sidadm user can not be find.

any help ?

Regards

Steven

Accepted Solutions (0)

Answers (9)

Answers (9)

Former Member
0 Kudos

Hi,

by starting sapinst.

greets

steven

Former Member
0 Kudos

Hi,

clearing the temp directory -> same error

I test it on serveral 2003 maschines ervery time the same problem.

Thanks

Steven

Former Member
0 Kudos

Where do you get the error, extraction of ZIP file or starting sapinst from STM/<Your Server type>?

Former Member
0 Kudos

Hello Gaurav,

yes we do attach/ detach method.

Tahnks for the tip with the sap tools but the software saptools won´t be start we have a selfextractor error,

we test ist on serveral server alway the same.

Error:

Selfextractor error

ianxsysex.c:473............. Reinstalling the application may fix the Problem.

i habe no idea how to fix this.

regards

Steven

Former Member
0 Kudos

Steven,

Can you try extracting the tool on your local machine.

Also try it on the server by cleaning your temp directory.

Regards

Gaurav Desai

-


markus_doehr2
Active Contributor
0 Kudos

> Error:

> Selfextractor error

> ianxsysex.c:473............. Reinstalling the application may fix the Problem.

I'd say that this error is caused by a missing security patch; check the eventlog for the error provided in

Note 1402510 - Resolving SideBySide Assembly Errors

and if yes, install the patch mentioned in

Note 1375494 - SAP system does not start after applying SAP kernel patch

Markus

Former Member
0 Kudos

Hi Steve,

Did you try using Attach/Detach method of MSSQL?

Once you do that you can perform the post processing using SAP tool for MSSQL, it will take care of managing logins in the database and changing ownerships, as well it will delete temporary procedures created in MS SQL.

Refer Note, 683447

Regards

Gaurav Desai

-


Former Member
0 Kudos

Hi Markus,

sorry but we use a MSSQL Server 2000 and when i try to use the new sapinst, where the option

"system copy by "backup/restore" a CI (and DI) will be installed, sapinst stops and requests you to import the backup." is placed,

we must use a SQL Server 2005 because the new sapinst doesn´t support the old MSSQL Database.

Thank

Steven

markus_doehr2
Active Contributor
0 Kudos

sorry but we use a MSSQL Server 2000 and when i try to use the new sapinst, where the option

"system copy by "backup/restore" a CI (and DI) will be installed, sapinst stops and requests you to import the backup." is placed,

we must use a SQL Server 2005 because the new sapinst doesn´t support the old MSSQL Database.

I see.

You know

Note 151603 - Copying an SQL Server database

And just for curiousity: Any reason why you don't use SQL Server 2005?

Markus

Former Member
0 Kudos

Hallo Markus,

i can´t follow the systemcopy guide because i can´t do a r3load from the system, i only habe a dump of the mssql 2000 database.

regards

steven

markus_doehr2
Active Contributor
0 Kudos

Stephen,

there are two method of doing a system copy: The R3load method and the method of importing a database backup. Both are supported by sapinst.

If you choose system copy by "backup/restore" a CI (and DI) will be installed, sapinst stops and requests you to import the backup. Just read the system copy guides, it's all in there.

Markus

markus_doehr2
Active Contributor
0 Kudos

> 1. Install Windows 2K3 server and Service packs

> 2. Install the SQL 2000 and patches

> 3. Create the database and restore the database from the production backup

Why don't you follow the way given in the system copy guides like choosing system copy?

Markus

Former Member
0 Kudos

Hi Sven,

no my system isn´t a schema installation, an all objects are belong to user dbo in sysobjects.

regards

Steven

Former Member
0 Kudos

Hi Steven,

concerning the sidadm login please check Note 1294762 (and then please retry).

If you want to find out which objects belong to user dbo you can try this:

use <SID>

go

select * from sysobjects

where sysobjects.uid = (select uid from sysusers where name = 'dbo')

go

Is your SAP system a schema installation?

Sven