Step 1.2: Create custom b-tree (default) indexes for the above described (large tables) tables with columns described. The following shows few large size tables with logsys field details. Run SLG1 and enter object ∼ALE and you will see this in the following screen shot – For Table EBKPF the logical system field is referred as AWSYS. Example: It is very easy to find out LOGSYS fields for large tables, if you have any old BDLS run logs you can see the fields as follows. Step 1.1: Find out what are the largest tables in your production system which are taking long time for BDLS conversions and list them out with LOGSYS (Logical system) fields. Step 1 – Create BDLS Indexes for bigger tables for columns LOGSYS: The final execution times differ a lot, following these steps we are able to run BDLS conversion in 6hrs which used to run for 18hrs for single logical system conversion run for the size of 12TB. This Weblog steps will help you in completing BDLS in less time. This conversion usually takes long time for large size database tables. Execute conversion of logical system names (BDLS) in short time and in parallel – Intermediateĭuring Homogeneous system copy from PROD to QAS environment, the most important step is to convert logical system (LOGSYS) names using transaction code BDLS.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |