SAP system copy error

[#1]

Hi Experts,

I am currently facing an issue/error while doing a homogeneous system copy with SAP NW 7.4 (SAP ERP 6.0 Ehp7) servers. Both source and target systems are test/demo servers and system copy procedure needs to be established as a part of implementation.

      An error occurred while processing option SAP Business Suite 7i 2013 Support Release 1 > EHP7 for SAP ERP 6.0 ABAP Support Release 1 > SAP ASE > System Copy > Target System > Standard System > Based on AS ABAP > Database Refresh or Move( Last error reported by the step: Assertion failed: Unable to load database RD3. Refer to trace file sapinst_dev.log for further information.)

Sybase ASE version = 15.7_122

sapinst_dev log file description -

Error description (sapinst_dev log file) –

Execution of the command "isql64 -e -w999 -Usa -SSAP-PROD-TEST:4901 -X" finished with return code 0. Output:

Password:

1> use master

1> load database RD3

2>  from 'F:/Backup_RD1_04042015/rd1_s1.dmp' stripe on 'F:/Backup_RD1_04042015/rd1_s2.dmp' stripe on 'F:/Backup_RD1_04042015/rd1_s3.dmp'

Backup Server session id is: 33. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.

Backup Server: 6.28.1.1: Dumpfile name 'RD11509409BE6    ' section number 1 mounted on disk file 'F:/Backup_RD1_04042015/rd1_s3.dmp'

Backup Server: 6.28.1.1: Dumpfile name 'RD11509409BE6    ' section number 1 mounted on disk file 'F:/Backup_RD1_04042015/rd1_s1.dmp'

Backup Server: 6.28.1.1: Dumpfile name 'RD11509409BE6    ' section number 1 mounted on disk file 'F:/Backup_RD1_04042015/rd1_s2.dmp'

Msg 3105, Level 16, State 4:

Server 'RD3', Line 1:

Data on dump will not fit into current database. Need 101376 Mbyte database.

1> online database RD3

Msg 930, Level 14, State 1:

Server 'RD3', Line 1:

Database 'RD3' cannot be opened because either an earlier system termination left LOAD DATABASE incomplete or the database is created with 'for load' option. Load the database or contact a user with System Administrator (SA) role.

No matter how much I try to execute the commands for loading database (LOAD DATABASE & ALTER DATABASE commands), i's not working. I have already added the size mentioned above. Although it still didnt work the size of the DB grew by 99GB (displayed in the incresed size of F: drive in Windows.server 2012 r2 OS level.

Any help leading to closure of this error is highly appreciated. I have attached all necessary screenshots for your kind reference.

Thanks and regards,

M. Nizam

[srinivasan_vinayagam]

Hi Nizamuddin,

Message text

Data on dump will not fit into current database. Need %d Mbyte database. 

Explanation

This error occurs when an attempt is made to load a database dump into a database smaller than the dumped database. You cannot use dump database or load database to shrink a database, regardless of the amount of actual data in the database.

Action

If your goal is to load the database from the dump, you must increase the size of the database being loaded into to at least the configured size of the dumped database. You can do this with either the alter database command or by dropping and re-creating a larger database.

If your goal is to shrink the total size of a database, you cannot use dump and load. You must copy all the data out of the database using bcp, drop the database and re-create a smaller database, then re-create the database structure with scripts, and reload the data with bcp.

extend your current master *database* on the master *device* to a total size of 101376MB(or more) (use  'alter database' command)

alter database master on master = <size in MB>

If there isn't enough room on the master device AND the master device is either a file system device in a file system that has free space or was created on a raw partition that is actually larger than the master device was defined, then you can use the DISK RESIZE command to enlarge the master device

disk resize name = "master", size = <additional space in MB>

Regards,

V Srinivasan

[Former Member]

Hi Srinivasan,

Thanks for your reply. I did try this method before I raised this message but it's not working. I also increased the requested size but it's not responding in the command prompt that size has increased.However the space in F drive increased by 99 GB (101376 MB) after doing so. I tried to proceed with the system copy but unable to do so as the same error keeps coming back.

I had also unlocked user 'sa' and it is still unlocked. Is it OK for me to lock user 'sa' now? In logs it was asking me to unlock it as the import was unable to proceed further. In case my commands for the target system 'SID" has anything missing please update me on this.

My intention is to load/dump database of source onto the target server. I have tried both methods but it's not working. I appreciate your response.

I HAVE ATTACHED THE LOG FILE FOR YOUR REFERENCE.

Thanks and regards,

M. Nizam

SAP system copy error.txt.zip

[Johan_sapbasis]

Hi Mohammed,

For the existing database where you want to upload the existing dump into the size is insufficient still. From the below text I have seen try this

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.dc36272_1251/html/commands/X61977.htm

alter database database_name on database_device = size for load;

alter database RD3 on R3D_data_001 = ''101376M'' for load;

If the aformentioned does not work you may want to try and include alter size in the command.

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc31644.1570/html/sag2/X275...

database is created with 'for load' option so you must add at the end of the command according to my understanding.

If you created the database using the "for load" option only the following commands will work.

If you create a database using for load, you can run only the following commands in the new database before loading a database dump:

alter database...for load

drop database

load database

When you load a database dump, the new database device allocations for the database must match the usage allocations in the dumped database. See Chapter 13,

“Backing Up and Restoring User Databases,” for a discussion of duplicating space allocation.

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc31644.1570/html/sag2/X328...

Hope you succeed,

Johan

[Former Member]

Hi Nicholas and Srinivasan,

You have been a great help to me. I have executed the disk resize command in order to make the DB more bigger for system copy to take place but unfortunately its not reflected in the command prompt, although the disk size has increased considerably.

I also have already executed the command alter database but there is the same error. However, I will try with the load option and update you all here.

Thanks and regards,

M. Nizam

[Johan_sapbasis]

Hi,

Yes please use the for load option at the end as the it only allows the 3 commands and the alter command only with the for load option as per link.

http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.infocenter.dc31644.1570/html/sag2/X275...

Kind Regards,

JOhan

[Former Member]

Hi Nicholas,

I have just tried this command after a few syntax alterations.

The space is also increased in RD3 (sp_dbhelp)

Now it's showing a different error "unable to verify database dump files.

Kind regards,

M. Nizam

[Johan_sapbasis]

Hi,

In which utility are you receiving the error? Also please attach the log file.

At least this is progress. Sorry for the late reply Im a but sick so resting.

Johan

[Former Member]

Hi Nicholas,

Its showing the error in the same phase of system copy (create database error). I need to extend the log segment of the SID database. Currently there is no space in the logical drive. My IT admin will add more space (100 GB) and I will resume the system copy with "continue with old option" while running the SWPM tool again with options for system copy I chose before.

I hope that you get well soon. Hope to start the system copy soon once the system drive is ready. I am attaching the screenshot of the error. I will first increase/extend the log segment (10240 MB) and run the system copy (Usapsa db owner/user). I will update all workarounds for everyone else's reference.

Thanks and regards,

M. Nizam

[Johan_sapbasis]

Hi,

That would be good especially disk space and if you resolve the error. Hope they add the space for you quickly rather intrigued to have the copy running smoothly

Good luck there and thanks for keeping us up to date.

Kind Regards,

Johan Van Zyl

[Former Member]

Hi Nicholas,

Sure, I will keep you all updated here on this regards. Once the space constraint is finished and log segment incresed, I hope that the system copy runs smoothly in an error-free manner.

I shall be awarding points to all relevant answers by you and Srinivasan once this task is concluded with and "answered" status to this thread.

Thanks and regards,

M. Nizam

[Johan_sapbasis]

Hi,

I know your pain with errors in system copies I would just like to get it running knowing we are on the right track on corrective actions.

J

[Former Member]

Hi,

I am getting the same error again

Server 'RD3', Line 1:

The log segment in the target database 'RD3' is too small (2048 MB) to accommodate the log segment from the dumped database (10240 MB).

1> online database RD3

Msg 930, Level 14, State 1:

Server 'RD3', Line 1:

Database 'RD3' cannot be opened because either an earlier system termination left LOAD DATABASE incomplete or the database is created with 'for load' option. Load the database or contact a user with System Administrator (SA) role.

On SWPM screen - Unable to load database RD3.

I have already increased the size of the sybase log segment device.

Instead of 10240 MB (10GB), I increased it to 11264 MB (11GB) as shown in yellowed section. Even in the Drive it shows the space extended by this amount. Kindly advice. Need to close this soon. Appreciate your kind help here.

Thanks and regards,

M. Nizam

[Former Member]

Hi,

The log segment is not extending properly. These are the steps I used but it wont work

1> alter database master

2> log on master = 11264

3> with override

4> go

Still it shows that its not extended. Any help for resolution will be highly appreciated and points rewarded.

Thanks and regards,

M. Nizam

[Johan_sapbasis]

Hi Mohammad,

You will see there you have increased the device but you need to increase the log segment itself which lies on the device.

alter database RD3 log on RD3_log_001 = "10G"

Just check for the correct name of your logsegment not sure if the name is RD3_log_001.

Kind Regards,

Johan

[Former Member]

Hi Nicolaas,

Thanks for your supportive reply. But this command is not working. I am referring to the SAP Note 1591387 now (SYB homogeneous system copy Sybase ASE).

Hope to find a solution in that. FYI - As shown in the above figure (CMD prompt), the name of the logsegment is RD3_log_001 (size currently 1028 MB, needs to be extended by 10240 MB as suggested in the sapinst_dev.log.

Error description -

The log segment in the target database 'RD3' is too small (2048 MB) to accommodate the log segment from the dumped database (10240 MB).

1> online database RD3

Msg 930, Level 14, State 1:

Server 'RD3', Line 1:

Database 'RD3' cannot be opened because either an earlier system termination left LOAD DATABASE incomplete or the database is created with 'for load' option. Load the database or contact a user with System Administrator (SA) role.

On SWPM screen - Unable to load database RD3

Thanks and regards,

M. Nizam

[Johan_sapbasis]

HI,

Sorry I forgot to for load option.

alter database RD3 log on RD3_log_001 = "10G" for load

Just play around with syntax again if necessary.

J

[Former Member]

Hi Nicolaas,

Thanks a lot for your help. The system copy is running now. I will update you the results once the system copy is finished and award point to you and all

Thanks and regards,

M. Nizam

[Johan_sapbasis]

Hi Mohammed,

How many steps are left in the system copy? If you are past your errors and the system copy is running this is what your problem was initially I think you can probably close this thread.

Kind Regards,

Johan

[Former Member]

Hi Nicolaas and Srinivasan.

The error is past the troubleshooting level and resolved. Thanks you your time and valuable inputs which helped me go ahead with the SAP system copy process. As requested, I am closing this thread.

Thanks and regards,

M. Nizam

[AtulKumarJain]

Hi NM,

Please follow the below link

You will get solution .

BR

AKJ