Hi Ravi,
First of all note 1591387 - SYB: Homogeneous Systemcopy Sybase ASE which aimed at
specific db version of 15.7.0.002 is discontinued and cannot be accessed.
Secondly have you decided on which method of data import you want to do using SWPM with reference to choosing Homogenous System Copy(SAP ASE specific: Detach/Attach or Backup/Restore)
If you choose copy method attach database devices using a database manifest file this manifest file will have to be one that you initially made on your source system before copying of the files.
This next part requires application downtime in source system as part of original exports.
In the source system you will have to quiesce the database to create the manifest file.
quiesce database SID_tag hold SID for external dump to 'D:\export\SID.manifest
go
Now view the contents of the manifest file to see which datafiles to copy.
mount database all from 'D:\export\SID.manifest' with listonly
go
Now you need to unquiesce the database for normal use again
quiesce database SID_tag release
go
!!! ps: note the blank space in the screenshot above represents SID and was added for privacy reasons.!!!
Here quiesce database used with the hold keyword suspends all updates to the specified database. Transactions cannot update data in suspended databases, and background tasks such as the checkpoint process and housekeeper process skip all databases that are in the suspended state. So we can safely copy the database devices to their new location,Now copy the datafiles from their original folders to other folder.
And yes file system structures and sizes have to be consistent for standardization reasons in your landscape hopefully especially the target sizes does matter. But you could probably if you wanted alter the target directory structure a bit but I would not recommend this.
Good references:
2162183 - SYB: Frequently Asked Questions for SAP ASE
http://wiki.scn.sap.com/wiki/display/SYBASE/Nov+2nd+2015+ASE+KBAs
547314 FAQ: System Copy procedure
Good luck.
Regards,
Johan