Migration SAP SolMan 7.1 MSSQL 2008 R2 Enterprise Edition to MSSQL Standard Edition

Hello,
I try to migrate a SAP SolMan 7.1 on Windows MSSQL 2008 R2 ENTERPRISE EDITION to
MSSQL 2008 R2 STANDARD EDITION.
In the source system (MSSQL 2008 R2 ENTERPRISE EDITION) there is "table compression" and
"partitioning" active.
the MSSQL STANDARD EDITION doesn`t support these two features.
So a normal DB backup on the source system and restore in the destination system is not possible.
But the tables compression I can deactivte by the SQL script
SELECT DISTINCT ‘ALTER TABLE [' + SCHEMA_NAME(schema_id) + '].[' + NAME + '] REBUILD PARTITION = ALL WITH (DATA_COMPRESSION = NONE);’
FROM sys.partitions p
join sys.objects o
on p.object_id = o.object_id
WHERE o.TYPE = ‘u’
and data_compression_desc != ‘NONE’
UNION
SELECT ‘ALTER INDEX ALL ON [' + SCHEMA_NAME(schema_id) + '].[' + NAME + '] REBUILD PARTITION = ALL WITH (DATA_COMPRESSION = NONE);’
FROM sys.partitions p
join sys.objects o
on p.object_id = o.object_id
WHERE o.TYPE = ‘u’
and data_compression_desc != ‘NONE’
is there a way to undo or deactivate the the SQL table partitioning without any data lost ?
Or is there a other way to migrate a SAP SolMan 7.1 form MSSQL 2008 R2 ENTERPRISE EDITION to MSSQL 2008 R2 STANDARD EDITION ?
Best regards
A. Moore

Hi Moore
Could you refer the SAP Note for MS Sql Version supports
1076022 - Release planning for Microsoft SQL Server 2008 (R2)
and MS SQL table compression & decompression SAP Note
1488135 - Database compression for SQL Server
BR
SS

Similar Messages

  • Migration SAP SolMan 7 MSSQL 2008 R2 Enterprise Edition to MSSQL Standard Edition

    Hello,
    I try to migrate a databse on Windows MSSQL 2008 R2 ENTERPRISE EDITION to
    MSSQL 2008 R2 STANDARD EDITION.
    In the source system (MSSQL 2008 R2 ENTERPRISE EDITION) there is "table compression" and
    "partitioning" active.
    Unfortunately the MSSQL STANDARD EDITION doesn`t support these two features.
    So a normal DB backup on the source system and restore in the destination system is not possible.
    But the tables compression I can deactivte by the SQL script
    SELECT DISTINCT ‘ALTER TABLE [' + SCHEMA_NAME(schema_id) + '].[' + NAME + '] REBUILD PARTITION = ALL WITH (DATA_COMPRESSION = NONE);’
    FROM sys.partitions p
    join sys.objects o
    on p.object_id = o.object_id
    WHERE o.TYPE = ‘u’
    and data_compression_desc != ‘NONE’
    UNION
    SELECT ‘ALTER INDEX ALL ON [' + SCHEMA_NAME(schema_id) + '].[' + NAME + '] REBUILD PARTITION = ALL WITH (DATA_COMPRESSION = NONE);’
    FROM sys.partitions p
    join sys.objects o
    on p.object_id = o.object_id
    WHERE o.TYPE = ‘u’
    and data_compression_desc != ‘NONE’
    is there a way to undo or deactivate the the SQL table partitioning without data lost ?
    Best regards
    B.-D.

    Hello Lydia Zhang,
    thanks for your help.
    For a few tables this will work.
    Unfortunately I have an SAP system with thousands of tables and index`s .
    With the SQL script:
    SELECT
     SCHEMA_NAME(t.schema_id) AS SchemaName
    ,OBJECT_NAME(i.object_id) AS ObjectName
    ,p.partition_number AS PartitionNumber
    ,fg.name AS Filegroup_Name
    ,rows AS 'Rows'
    ,au.total_pages AS 'TotalDataPages'
    ,CASE boundary_value_on_right
        WHEN 1 THEN 'less than'
        ELSE 'less than or equal to'
     END AS 'Comparison'
    ,value AS 'ComparisonValue'
    ,p.data_compression_desc AS 'DataCompression'
    ,p.partition_id
    FROM sys.partitions p
    JOIN sys.indexes i ON p.object_id = i.object_id AND p.index_id = i.index_id
    JOIN sys.partition_schemes ps ON ps.data_space_id = i.data_space_id
    JOIN sys.partition_functions f ON f.function_id = ps.function_id
    LEFT JOIN sys.partition_range_values rv ON f.function_id = rv.function_id AND p.partition_number = rv.boundary_id
    JOIN sys.destination_data_spaces dds ON dds.partition_scheme_id = ps.data_space_id AND dds.destination_id = p.partition_number
    JOIN sys.filegroups fg ON dds.data_space_id = fg.data_space_id
    JOIN (SELECT container_id, sum(total_pages) as total_pages
            FROM sys.allocation_units
            GROUP BY container_id) AS au ON au.container_id = p.partition_id
    JOIN sys.tables t ON p.object_id = t.object_id
    WHERE i.index_id < 2
    ORDER BY ObjectName,p.partition_number;
    GO
    Output:
    SchemaName    ObjectName    PartitionNumber    Filegroup_Name    Rows    TotalDataPages    Comparison    ComparisonValue    DataCompression  
     partition_id
    swp    /BI0/F0CCMARSH    1    PRIMARY    0    0    less than    NULL    NONE    72057613126729728
    swp    /BI0/F0CCMAWDD1    1    PRIMARY    0    0    less than    NULL    NONE    72057613127516160
    swp    /BI0/F0CCMAWDD2    1    PRIMARY    0    0    less than    NULL    NONE    72057613128237056
    swp    /BI0/F0CCMAWDH1    1    PRIMARY    0    0    less than    NULL    NONE    72057613128957952
    and so on
    I got about 5000 tables .
    Is there a way to delete all index on the partioned table an create a new with one script ?
    Best regards
    B.-D.

  • Downgrade SQL Server 2008 Enterprise to SQL Server2008 Standard Edition

    I would like to know from fourm users, what are the necessary steps I would take care for above mentioned activity and also please let me know best suitable option for Production.
    SNS

    You can't do in-place downgrade. You need to go with backup -> uninstall ent -> install std -> bring it to same patch -> restore databases approach.
    You need to make sure that there is not enterprise only feature used else you can't restore database on standard.
    Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker
    This posting is provided "AS IS" with no warranties, and confers no rights.
    My Blog |
    Team Blog | @Twitter
    Balmukund's answer above is the Microsoft supported route for doing a downgrade of an instance of SQL Server.  However, before you do this, you need to query the sys.dm_db_persisted_sku_fearures DMV in each of your user databases to make certain that
    you don't have any Enterprise features in use that would block your ability to restore a database onto Standard Edition.
    No matter what you are going to have to do an uninstall and reinstall of the SQL Server instance to downgrade the SKU.  However, you can save yourself some time and the headache of trying to restore the system databases if you are careful about what
    you do.  I have done a couple of SKU downgrades in the past and the easiest way to do it, and I am not saying this is the Microsoft supported way but that it works if done correctly, is to:
    Take a good backup of all of your databases (system and user).  
    Run SELECT @@VERSION and note the specific build number of SQL Server that you are currently on.
    Shut down your existing instance of SQL Server.  
    Copy the master, model, and msdb database files (both mdf and ldf), don't move them copy them, from the current location to a new folder that you mark as readonly. 
    Uninstall SQL Server from the system.
    Reboot the server.
    Install SQL Server Standard Edition.
    Apply the necessary Service Pack and/or Cumulative Updates to bring the instance up to your previous build number.
    Shutdown SQL Server.
    Copy the master, model, and msdb database files (both mdf and ldf) from the folder you saved them in to the correct location for the new install and remove the readonly flag from the files, and change the file ACL's so that the SQL Service account has Full
    Control over the files.
    Startup SQL Server and if you did it correctly it will startup and be exactly where you were before you made any changes, with all of your user databaes online and you should be ready to let applications connect and resume operations.
    If you screw something up in the above, you still have your backups and you can run setup to rebuild the system databases and then go about following the Microsoft supported path for restoring the system databases and then user databases into the system
    to bring it online.  Essentially the file copy is no different that what would occur through attach/detach you are just doing it with system databases which is not supported, but it does work.  The key is to have your backups from before you do anything
    so you have the supported route available if you encounter an issue.  The only issue I have ever had doing this set of steps is that I didn't set the file ACL's correctly and the database engine threw Access Denied errors and failed to start until I fixed
    the ACL's correctly.  This can save you many hours of frustration and downtime trying to restore everything since the database files are already there and it is just some small copy operations to put them where you need them to be.
    Balmukund, feel free to beat me over the head for suggesting a non-supported path. :-)
    Jonathan Kehayias | Senior Consultant,
    SQLSkills.com
    SQL Server MVP | Microsoft Certified Master: SQL Server 2008
    Feel free to contact me through
    My Blog or
    Twitter. Become a
    SQLskills Insider!
    Please click the Mark as Answer button if a post solves your problem!

  • Confirm no support for MSSQL 2008 before reverting to older EM version

    Before I resort to installing EM Grid Control (11.1.0.1), I want to confirm that I have correctly read that EM12C does NOT support monitoring of MSSQL 2008. I understand that MSSQL 2008 R2 is certified with EM12C but, it appears that monitoring the original MSSQL 2008 is not.
    Also, I'm a bit nervous about using EM Grid Control since it appears to have been a one-and-only version. Would I be smarter to go back to one of the EM10 versions?
    This will be a new install, not an upgrade, so I hate to start out with an outdated EM tool but, I have to be able to monitor MSSQL 2008.
    TIA,
    Jeri

    I have received a response from MOS to my original SR which confirms that EM12C is not certified for monitoring MSSQL 2008. For those who may possibly be interested in clarification of other OS and/or MSSQL versions with various flavors of EM, I've included below the full SR response details:
    "The 12cR1 and 12cR2 Cloud Control are only certified to monitor two versions of Microsoft SQL Server : 2005 and 2008 R2
    The 12cR2 is certified with these 3 Windows OS versions : 7,2008 R2,2003 on 64-bit platform where as the 12cR2 is certified with 4 versions of Windows OS version: 7,2008 R2,2008,2003
    The 11g Grid Control is certified to monitor 7 versions of Microsoft SQL Server (including 2008) : 2008 R2 Cluster,2008 R2,2008 Cluster,2008,2005 Cluster,2005,2000
    Also 11g Grid Control certified with 4 versions of Windows platform : 7,2008,2003 R2,2003"
    The analyst who provided this information was also kind enough to open another SR on my behalf which will hopefully yield the answer to my other question- whether deploying 11g Grid Control is the best option for my environment or whether one of the EM10 versions might be a better choice. Unless someone else here is interested in that answer too, I won't update this post further with that information.
    Thanks, Jeri

  • SP3 cannot be installed on SQL Server 2008 standard edition 64 bit

    I am getting error during the running of setup of SP3 for SQL Server 2008 Standard edition on windows 2008 R2 enterprise ed.
    Description:
      SQL Server 2008 Setup has encountered an error.
    Problem signature:
      Problem Event Name: SQL100Exception
      Problem Signature 01: SQL2008@RTM@KB2546951
      Problem Signature 02: 0xFE9E43A7
      Problem Signature 03: 0xFE9E43A7
      Problem Signature 04: 0xDC80C325
      Problem Signature 05: 0xDC80C325
      Problem Signature 06: InitializeUIDataAction
      Problem Signature 07: Unknown
      Problem Signature 08: Unknown
      Problem Signature 09: Unknown
      Problem Signature 10: Unknown
      OS Version: 6.1.7601.2.1.0.274.10
      Locale ID: 1033
    Additional information about the problem:
      LCID: 1033
    Read our privacy statement online:
    http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt

    Hi,
    I found the log file but I am not able to find any upload file button. It is very big file how can I upload it here?
    Overall summary:
      Final result:                  The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
      Exit code (Decimal):           -74274373
      Exit facility code:            914
      Exit error code:               43451
      Exit message:                  The system cannot open the device or file specified. 
      Start time:                    2014-04-10 08:03:59
      End time:                      2014-04-10 08:05:15
      Requested action:              Patch
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140410_080359\Detail.txt
      Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.5500.0%26EvtType%3d0xFE9E43A7%400xDC80C325
    Machine Properties:
      Machine name:                  AD-ITD-SW-SQLDB
      Machine processor count:       16
      OS version:                    Windows Server 2008
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Database Engine Services                
    1033                 Standard Edition     10.0.1600.22    No       
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            SQL Server Replication                  
    1033                 Standard Edition     10.0.1600.22    No       
      Sql Server 2008      MSSQLSERVER          MSSQL10.MSSQLSERVER            Full-Text Search                        
    1033                 Standard Edition     10.0.1600.22    No       
      Sql Server 2008      MSSQLSERVER          MSAS10.MSSQLSERVER             Analysis Services                       
    1033                 Standard Edition     10.0.1600.22    No       
      Sql Server 2008      MSSQLSERVER          MSRS10.MSSQLSERVER             Reporting Services                      
    1033                 Standard Edition     10.0.1600.22    No       
      Sql Server 2008      SWMSSQLSERVER        MSSQL10.SWMSSQLSERVER          Database Engine Services                
    1033                                      10.0.1600.22   
    No       
      Sql Server 2008      SWMSSQLSERVER        MSSQL10.SWMSSQLSERVER          SQL Server Replication                  
    1033                                      10.0.1600.22   
    No       
      Sql Server 2008                                                         
    Management Tools - Basic                 1033                 Standard Edition    
    10.0.1600.22    No       
      Sql Server 2008                                                         
    Management Tools - Complete              1033                 Standard Edition     10.0.1600.22   
    No       
      Sql Server 2008                                                         
    Client Tools Connectivity                1033                 Standard Edition    
    10.0.1600.22    No       
      Sql Server 2008                                                         
    Client Tools Backwards Compatibility     1033                 Standard Edition     10.0.1600.22    No       
      Sql Server 2008                                                         
    Client Tools SDK                         1033                
    Standard Edition     10.0.1600.22    No       
      Sql Server 2008                                                         
    Integration Services                     1033                 Standard Edition    
    10.0.1600.22    No       
    Package properties:
      Description:                   SQL Server Database Services 2008
      SQLProductFamilyCode:          {628F8F38-600E-493D-9946-F4178F20A8A9}
      ProductName:                   SQL2008
      Type:                          RTM
      Version:                       10
      SPLevel:                       3
      KBArticle:                     KB2546951
      KBArticleHyperlink:           
      PatchType:                     SP
      AssociatedHotfixBuild:         0
      Platform:                      x64
      PatchLevel:                    10.3.5500.0
      ProductVersion:                10.0.1600.22
      GDRReservedRange:              10.0.1000.0:10.0.1099.0;10.0.3000.0:10.0.3099.0;10.0.4010.0:10.0.4250.0;10.0.5501.0:10.0.5750.0
      PackageName:                   SQLServer2008-KB2546951-x64.exe
      Installation location:         d:\c8811b7ec810308deb\x64\setup\
    User Input Settings:
      ACTION:                        Patch
      ALLINSTANCES:                  False
      CLUSTERPASSIVE:                False
      CONFIGURATIONFILE:            
      HELP:                          False
      INDICATEPROGRESS:              False
      INSTANCENAME:                  <empty>
      QUIET:                         False
      QUIETSIMPLE:                   False
      X86:                           False
    Rules with failures:
    Global rules:
    There are no scenario-specific rules.
    Rules report file:               The rule result report file is not available.
    Exception summary:
    The following is an exception stack listing the exceptions in outermost to innermost order
    Inner exceptions are being indented
    Exception type: System.ComponentModel.Win32Exception
        Message:
            The system cannot open the device or file specified.
        Data:
          DisableWatson = true
        Stack:
            at Microsoft.SqlServer.Chainer.Infrastructure.MsiNativeMethodHelpers.GetDBProperty(ServiceContainer context, String pathToMsi, String propertyName)
            at Microsoft.SqlServer.Configuration.MsiExtension.SetPatchInstallStateAction.GetMsiRtmVersion(PackageInstallProperty targetPackage)
            at Microsoft.SqlServer.Configuration.MsiExtension.SetPatchInstallStateAction.IsApplicablePatch(PatchProperty currentPatch, PackageInstallProperty targetPackage)
            at Microsoft.SqlServer.Configuration.MsiExtension.SetPatchInstallStateAction.ExecuteAction(String actionId)
            at Microsoft.SqlServer.Configuration.MsiExtension.ProductInstallProperty.GetInstalledPackages(String instanceName, List`1& installedInstancePackages, List`1& installedSharedPackages, String& returnedErrorMessage)
            at Microsoft.SqlServer.Configuration.MsiExtension.ProductInstallProperty.CollectProductData()
            at Microsoft.SqlServer.Configuration.FeatureTreeConfigurationBase.LoadFeatureTreeDefinitionAllInstances()
            at Microsoft.SqlServer.Configuration.PatchFeatureTree.InitializePatchFeatureTree(ServiceContainer context)
            at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
            at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
            at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)

  • SAP SOLMAN 7.1 error in ATM for DBACOCKPIT

    Hi Experts,
    My client's SAP Solution Manager 7.1 has been displaying the error message - "Error in RDI back-end setup occured!", since last one week. I am unable to analyze this to resolution, as there is nothing I couldn't find closely relative in the standard database SAP Sybase 15.7. ASE server configuration guides or in the SCN itself for that matter, which would help me resolve this bugging error.
    I have also checked in system logs but have always found different types/varieties of database errors everyday. I am attaching the error screenshots for your kind reference and consideration. Kindly note that I have worked on most databases previously in an efficient manner except for Sybase ASE, which is relatively new to me.
    When I click on repair, I am getting the following error, which my SAP Basis PM/lead has told me its a generic error.
    Upon clicking on yes, I am getting the unavoidable error shown below -
    The error is - "Error in RDI back-end setup occured!", as i have stated above.
    I have checked the ATM logs and history and they are fine. I am getting error only in the ATM queue as shown below -
    I am also getting the same database errors in event viewer as to those in the system logs for SAP SOLMAN 7.1 server.
    I would appreciate it very much if one of the Sybase experts would help me out here. Speaking of technical configuration for any database in conceptual terms, I perceive this error to be a space issue as mentioned in the ATM queue. I believe I have provided sufficient details. The OS here is the Windows server 2008 R2 version.
    Kindly mention if you need more details for a speedy and possible error analysis and resolution
    This is an emergency task for me as I need to resolve it on ASAP basis. Rest assured, points for all right answers will be awarded generously.
    Thanks and regards,
    M. Nizam

    Hi Nizam,
    Please share what is the database patch level for Sybase ASE 15.7
    Additionall please review below SAP notes
    1619967
    SYB: DBA Cockpit Correction Collection SAP Basis 7.31
    1558958
    SYB: DBA Cockpit Correction Collection SAP Basis 7.02 / 7.30
    1920025 DBACOCKPIT - Error 'Repair ATM' when started from different systems
    Hope this helps.
    Regards,
    Deepak Kori

  • Migration SAP-System from 32bit-server to 64bit- server

    We want to change our SAP SOLMAN EHP1-system , which running
    on LINUX SLES9 32bit ( with MAXDB 7.7 ) to a new target server with LINUX SLES10 64bit ( as well MAXDB 7.7 ).
    We have also the same OS Linux but differents releases.
    My question: Can I perform this change with the tool "homogene
    Systemcopy" or is there any other solution for this problem ??

    A Solution Manager is a combined ABAP + Java system. You can do a database copy approach but you must use sapinst to migrate the Java part (it's all included in sapinst).
    Keep in mind that your JDK changes, for 32bit Linux you must use the Sun JDK, for x86_64 you must use the IBM JDK. The migration may fail on initial attempt since the parameter for the Sun JDK are different to those for the IBM JDK. You'd then have to adapt the parameters using configtool before you can continue.
    Apart from that it should be smooth.
    Markus

  • Migrating windows 2003 standard edition  to windows 2008 enterprise edition

    Hi
    We are using ECC 5.0 and our PRD system is running on windows 2003 standard edition,and recently we have got some physical memory problem.as windows 2003 standard edition supports only 4 GB of RAM. and we want to extend our RAM for that we are planning to upgrade os to windows 2008 enterprise edition,is that possible.and after upgrading OS what are the activities that need to be performed for SAP to run succesfully,kindly suggest.
    Regards
    Pranav

    Hi Markus
    I read note SAP Note 690432 - Windows 2003 Support in it regarding upgradation of os  windows 2003 standard edition to windows 2003 enterprise edition.
    Upgrade of Your Operating System
    If you upgrade an existing SAP system to Windows Server 2003 perform the
    following actions:
    o Install the latest R3DLLINS
    You find the latest dynamic link libraries R3DLLINS for Windows
    Server 2003 on the EXT-Kernel CD in the NTPATCH directory.
    o Replace the R/3 kernel with the EXT-Kernel.
    If you do not replace it you will get error "SICK" after the first
    logon attempt after the start.
    In this case, download the disp+work package(s) from the SAP
    Service Marketplace at service.sap.com/patches and unpack the
    patch(es) to directory usr\sap\exe:
    dw*_<patch-level>
    Use at least patch level 186.
    o Use the latest saposcol version.
    This version supports the changed performance counter of Windows
    Server 2003 to determine values for ST06 and RZ20.
    You can find the latest version in file saposcol_<Patch Level>.CAR.
    in the SAP Service Marketplace.
    o SAP DB only: See SAP Note 315237.o Compatibility of the Hardware with Windows Server 2003
    You can perform the upgrade to Windows Server 2003 only if the
    hardware has been explicitly released for this purpose. To check,
    do one of the following:
    - If the Windows Server 2003 CD is available, check compatibility
    with WINNT32.EXE in the \I386 directory. The exact statement
    is: <DRIVE:>\I386\WINNT32 /CHECKUPGRADEONLY. The result is
    stored as text file WINNT32.LOC in the present Windows
    directory (e.g. C:\WINNT).
    - The hardware has successfully passed SAP hardware certification
    (http://www.addon.de).
    - The hardware is contained in the Microsoft Hardware
    Compatibility List (http://www.microsoft.com/hcl).
    - The hardware has been released for Windows Server 2003 by the
    manufacturer. This information is published on the
    corresponding website.
    o Kerberos Single Sign-On
    When the SAP system is installed on Windows Server 2003 you can
    setup the Kerberos Single Sign-On. If you use the kerberos protocol
    the information exchanged between the SAP frontend and the
    application server for authentication is encrypted.
    The procedure for setting up Single Sign-On is described in all
    recent installation guides which you can download from the SAP
    Service Marketplace at: service.sap.com/instguides.
    o SAP domain under Windows Server 2003
    Follow the instructions of the Windows documentation for the
    migration of a Windows NT 4 domain to Windows 2003. For the SAP
    environment some additional points need to be observed.
    For Windows NT 4 there are two models for the SAP system domain:
    - Single domain
    All users and the SAP system build one single domain. This
    domain can be migrated to Windows Server 2003 and exist there
    as single domain.
    - Additional domain
    There is one domain for the users and a second domain for the
    SAP system(s). For a migration to Windows Server 2003 the SAP
    system domain has to be created as child domain under the user
    domain. A "Top-down" procedure is to be used. The higher domain
    (the user domain) must be migrated prior to the SAP child
    domain. If the user and SAP domain is part of a larger domain
    structure the complete domain structure for Windows Server 2003
    needs to be planned in a preparing phase. Usually, the
    structure created under Windows NT 4 has to be re-arranged and
    consolidated.
    The name space of the root domain and all sub-ordinated domains
    has to be defined and the distribution of the DNS services
    needs to be determined.
    Note the following:
    The SAP domain has to be created as child domain.
    The SAP domain must not be converted into an organizational
    unit (OU). OUs are not supported by R3SETUP and R3up.
    in it nowhere it is mentioned about system copy so plz suggest.

  • How to Migrate SAP Scripts to Adobe form

    Hi,
    Can yo uplease tell me step by step how to convert/migrate SAP Script to Adobe forms.
    Thanks,
    Rajeev Gupta

    Hi
    Transforming SAP Scripts - > Smartform -> Adobe Forms is the right way.
    refer this thread...
    [Re: Convert SAP Scripts to Adobe PDF Forms|Re: Convert SAP Scripts to Adobe PDF Forms]
    Regards
    Raj
    Edited by: Rajasekhar Dinavahi on Dec 9, 2008 5:25 AM

  • Unable to delete Role from User ID in SAP SOLMAN production system but able to from DEV with the same authorization, pls suggest

    unable to delete Role from User ID in SAP SOLMAN production system but able to from DEV with the same authorization, pls suggest

    Hi,
    For SU01 role removal, you do not need S_USER_AGR with 02, and as you mentioned both authorizations available in production, if so trace should not show you the S_USER_AGR with 02 with RC=04.
    I would recommend to do role comparison for the user performing the activity. and then check if you have the S_USER_AGR with 02 in user buffer SU56.
    But ideally it should not ask you S_USER_AGR for 02 through SU01, so please take help of abaper to debug it.
    Also put trace in non-prd to see if S_USER_AGR is getting checked with 02 for removal through SU01.
    BR,
    Mangesh

  • SAP Authentication issue in Xcelsius 2008 SP4

    Ingo Can you help me?
    Xcelsius 2008 SP4 Failed to Open/Save from BusinessObjects Enterprise and throws an error Failed While Trying to Logon User "0000" RFC error: "LOGON_DATA_INCOMPLETE" when using SAP Authentication.
    It works perfect with Enterprise.
    Recently we have upgraded from Xcelsius 2008 SP3 FP 3.5 to Xcelsius 2008 SP4. It also displays the password without encrypting.
    BOE 3.1 Sp3
    Integration Kit SP3Fix Pack 3.2
    SAP GUI 720
    Xcelsius 2008 SP4
    It was working good with SAP Authentication when using Xcelsius 2008 SP3 FP3.5
    Thanks
    Dais

    Hi,
    As a starting point, i would strongly recommend you standardise all your component versions.
    from what i can see, you've just asserted that Server, Integration Kit, and Client  are all on different Fix levels..
    that's not a nice baseline on which to investigate!  
    Also, patching would also include importing the correct SAP Transports into your BW. (they change almost every FP)
    Regards,
    H
    Edited by: Henry Banks on Feb 10, 2012 4:00 PM

  • HT204350 Hey, migration from an old mac late 2008 aluminium to a brand new mac book air. Only the new one has firewire. Transmissiom via wifi estimates ~50h. Is there a faster Way to sync? Tanks in advance

    Hey, migration from an old mac late 2008 aluminium to a brand new mac book air. Only the new one has firewire. Transmissiom via wifi estimates ~50h. Is there a faster Way to sync? Tanks in advance

    I'll venture that your problem here is that you're using two very different versions of Mac OS X.  The USB adapter has been useful to me when making big downloads or while using other networks, but it might not be your case. 
    Here's what I would advise, though it may be less than stellar:  Copy the files you need into folders and move them through a USB flash drive or using that external hard drive of yours. (Could the format be the reason your MBA can't see it?). Some stuff like calendars and contacts can be exported too. At least in Lion, I haven't used Tiger in a while. 
    Good luck.

  • MSSQL 2008 - Database size getting smaller after EHP upgrade??

    Hi All,
    Did anyone observe the DB size of MSSQL 2008 after EHP upgrade?
    In my two system, after upgraded to EHP5 and EHP2 respectively, the database is getting smaller compare to before upgrade, estimated 5-10gb.
    EHP upgrade is unlike DBEXPORT, it shouldn't have any reorganization features and so do MSSQL.
    Any idea?
    Cheers,
    Nicholas Chang

    > Right after upgrade is smaller and after sgen, db size is bigger than source.
    So it's ok.
    > As system was upgrade from ECC6 to EHP5 with Central Application, HCM and Finance .... the after upgrade size should bigger than the source even before SGEN. Your kind input is mostly welcome.
    If the source system was compiled completely (using SGEN) then you need to compare the sizes of the target system also, otherwise you compare apple with pies.
    Another reason may be that index compression was activated:
    Note 1459005 - Enabling index compression for SQL Server
    You could now upgrade to SQL Server 2008 R2 and apply
    Note 1488135 - Database compression for SQL Server
    this will save additional space (30 - 50 %).
    Markus

  • Problem in SAP toolbar of Crytal report 2008!

    Hi Experts,
    As some Articles from Blogs, after the installation of the SAP Integration Kit there is a new toolbar in Crystal Reports.
    But I installed SAP Solution Integration Kit for Business Object Edge Series Standard Package on Server andI installed Crystal Report on Client. How can I see SAP toolbar on Crystal Report 2008 to integrate and connect with SAP BW?. Could you show the solution to solve that?
    Thanks
    Jack,

    Hi,
    you need to have the SAP GUI with BW 3.5 and BI 7 Add On installed and you need the client componets from the SAP Integration Kit installed.
    Ingo

  • MSSQL 2008 R2 - 32bit, TSQL backup with compression, error: There is insufficient system memory in resource pool 'internal' to run this query

    Hello,
    I would like to ask you about advice.
    We have MSSQL 2008 R2, 32 bit. Memory is 4GB, split into 2GB for Windows and 2GB for applications. Database has recovery model simple because we have replicated data into other servers ( 2 ). Contemporary we work with 2 servers. Max memory for MSSQL is 2048
    MB.
    We set the backup as follows:
    USE MSDB
    GO
    DECLARE @JMENO_ZALOHY VARCHAR(120)
    SELECT  @JMENO_ZALOHY = 'E:\backup\BackupSQL\1 Pondeli\DAVOSAM_'+ convert( varchar(2), datepart( hh, getdate() ) ) + '00_DEN_DIFF.bak'
    SELECT  @JMENO_ZALOHY
    BACKUP DATABASE [DAVOSAM]
    TO DISK = @JMENO_ZALOHY
    WITH INIT, DIFFERENTIAL, CHECKSUM, COMPRESSION
    GO
    Every second or third day in log there is error message: 'There is insufficient system memory in resource pool 'internal' to run this query' Accurate in time of backup. The error is still repeat, majority in working hours.
    Today I have found out, that problem is probably in compression of backup. Because if I removed word: compression, a backup normally runs without error.
    Question: Is my hypothesis correct that problem is in backup with compression?
    Thank you David

    Hello, today evening I have ran backup command bellow. All is OK. Probably MSSQL has cleaned memory. Next attempt I will try in peak next week.
    Since time I have removed word compression, in error log is not any error.
    I have checked memory as soon as memory gets on top, it is about 1.707 GB the MSSQL writes into log this messgages:
    2014-03-14 15:00:04.63 spid89      Memory constraints resulted reduced backup/restore buffer sizes. Proceding with 7 buffers of size 64KB.
    2014-03-14 15:00:08.74 Backup      Database differential changes were backed up. Database: DAVOSAM, creation date(time): 2014/01/12(22:03:10), pages dumped: 16142, first LSN: 1894063:1673:284,
    last LSN: 1894063:1792:1, full backup LSN: 1894053:15340:145, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'E:\backup\BackupSQL\5 Patek\DAVOSAM_1500_DEN_DIFF.bak'}). This is an informational message. No user action is required.
    2014-03-14 15:00:12.79 spid72      Memory constraints resulted reduced backup/restore buffer sizes. Proceding with 7 buffers of size 64KB.
    2014-03-14 15:00:12.88 Backup      Database differential changes were backed up. Database: WEBFORM, creation date(time): 2014/02/01(05:22:47), pages dumped: 209, first LSN: 125436:653:48, last
    LSN: 125436:674:1, full backup LSN: 125435:689:36, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'E:\backup\BackupSQL\5 Patek\WEBFORM_1500_DEN_DIFF.bak'}). This is an informational message. No user action is required.
    After that the MSSQL reduced memory on 1.692.
    USE MSDB
    GO
    DECLARE @JMENO_ZALOHY VARCHAR(120)
    SELECT  @JMENO_ZALOHY = 'E:\backup\BackupSQL\6 Sobota\DAVOSAM_'+ convert( varchar(2), datepart( hh, getdate() ) ) + '00_DEN_FULL.bak'
    SELECT  @JMENO_ZALOHY
    BACKUP DATABASE [DAVOSAM]
    TO DISK = @JMENO_ZALOHY
    WITH INIT, CHECKSUM, COMPRESSION, MAXTRANSFERSIZE=65536
    GO
    E:\backup\BackupSQL\6 Sobota\DAVOSAM_2100_DEN_FULL.bak
    (1 row(s) affected)
    Processed 467240 pages for database 'DAVOSAM', file 'DavosAM_Data' on file 1.
    Processed 2 pages for database 'DAVOSAM', file 'DavosAM_Log' on file 1.
    BACKUP DATABASE successfully processed 467242 pages in 24.596 seconds (148.411 MB/sec).
    select * from sys.dm_exec_connections
    where net_packet_size > 8192
    session_id  most_recent_session_id connect_time            net_transport                            protocol_type            
                   protocol_version endpoint_id encrypt_option                           auth_scheme                
                 node_affinity num_reads   num_writes  last_read               last_write              net_packet_size client_net_address  
                                client_tcp_port local_net_address                                local_tcp_port
    connection_id                        parent_connection_id                 most_recent_sql_handle
    (0 row(s) affected)
    SELECT SUM (pages_allocated_count * page_size_in_bytes)/1024 as 'KB Used', mo.type, mc.type
    FROM sys.dm_os_memory_objects mo
    join sys.dm_os_memory_clerks mc on mo.page_allocator_address=mc.page_allocator_address
    GROUP BY mo.type, mc.type, mc.type
    ORDER BY 1 DESC;
    KB Used     type                                                         type
    29392       MEMOBJ_SORTTABLE                                             MEMORYCLERK_SQLSTORENG
    9392        MEMOBJ_SOSNODE                                               MEMORYCLERK_SOSNODE
    8472        MEMOBJ_SQLTRACE                                              MEMORYCLERK_SQLGENERAL
    5480        MEMOBJ_SECOLMETACACHE                                        USERSTORE_SCHEMAMGR
    5280        MEMOBJ_RESOURCE                                              MEMORYCLERK_SQLGENERAL
    5008        MEMOBJ_CACHEOBJPERM                                          USERSTORE_OBJPERM
    4320        MEMOBJ_SOSSCHEDULER                                          MEMORYCLERK_SOSNODE
    2864        MEMOBJ_PERDATABASE                                           MEMORYCLERK_SQLSTORENG
    2328        MEMOBJ_SQLCLR_CLR_EE                                         MEMORYCLERK_SQLCLR
    2288        MEMOBJ_SESCHEMAMGR                                           USERSTORE_SCHEMAMGR
    2080        MEMOBJ_SOSDEADLOCKMONITORRINGBUFFER                          MEMORYCLERK_SQLSTORENG
    2008        MEMOBJ_LOCKBLOCKS                                            OBJECTSTORE_LOCK_MANAGER
    1584        MEMOBJ_CACHESTORETOKENPERM                                   USERSTORE_TOKENPERM
    1184        MEMOBJ_LOCKOWNERS                                            OBJECTSTORE_LOCK_MANAGER
    840         MEMOBJ_SNIPACKETOBJECTSTORE                                  OBJECTSTORE_SNI_PACKET
    760         MEMOBJ_SOSDEADLOCKMONITOR                                    MEMORYCLERK_SQLSTORENG
    752         MEMOBJ_SESCHEMAMGR_PARTITIONED                               USERSTORE_SCHEMAMGR
    688         MEMOBJ_RESOURCEXACT                                          MEMORYCLERK_SQLSTORENG
    616         MEMOBJ_SOSWORKER                                             MEMORYCLERK_SOSNODE
    552         MEMOBJ_METADATADB                                            MEMORYCLERK_SQLGENERAL
    480         MEMOBJ_SRVPROC                                               MEMORYCLERK_SQLCONNECTIONPOOL
    424         MEMOBJ_SQLMGR                                                CACHESTORE_SQLCP
    400         MEMOBJ_SBOBJECTPOOLS                                         OBJECTSTORE_SERVICE_BROKER
    384         MEMOBJ_SUPERLATCH_BLOCK                                      MEMORYCLERK_SQLSTORENG
    384         MEMOBJ_RESOURCEDATASESSION                                   MEMORYCLERK_SQLGENERAL
    352         MEMOBJ_SOSSCHEDULERMEMOBJPROXY                               MEMORYCLERK_SOSNODE
    328         MEMOBJ_SBMESSAGEDISPATCHER                                   MEMORYCLERK_SQLSERVICEBROKER
    320         MEMOBJ_METADATADB                                            USERSTORE_DBMETADATA
    296         MEMOBJ_INDEXSTATSMGR                                         MEMORYCLERK_SQLOPTIMIZER
    264         MEMOBJ_LBSSCACHE                                             OBJECTSTORE_LBSS
    224         MEMOBJ_XE_ENGINE                                             MEMORYCLERK_XE
    216         MEMOBJ_GLOBALPMO                                             MEMORYCLERK_SQLGENERAL
    208         MEMOBJ_PROCESSRPC                                            USERSTORE_SXC
    200         MEMOBJ_SYSTASKSESSION                                        MEMORYCLERK_SQLCONNECTIONPOOL
    200         MEMOBJ_REPLICATION                                           MEMORYCLERK_SQLGENERAL
    192         MEMOBJ_SOSSCHEDULERTASK                                      MEMORYCLERK_SOSNODE
    176         MEMOBJ_SQLCLRHOSTING                                         MEMORYCLERK_SQLCLR
    168         MEMOBJ_SYSTEMROWSET                                          CACHESTORE_SYSTEMROWSET
    128         MEMOBJ_RESOURCESUBPROCESSDESCRIPTOR                          MEMORYCLERK_SQLGENERAL
    128         MEMOBJ_CACHESTORESQLCP                                       CACHESTORE_SQLCP
    128         MEMOBJ_RESOURCESEINTERNALTLS                                 MEMORYCLERK_SQLSTORENG
    120         MEMOBJ_BLOBHANDLEFACTORYMAIN                                 MEMORYCLERK_BHF
    120         MEMOBJ_SNI                                                   MEMORYCLERK_SNI
    88          MEMOBJ_QUERYNOTIFICATON                                      MEMORYCLERK_SQLOPTIMIZER
    72          MEMOBJ_HOST                                                  MEMORYCLERK_HOST
    72          MEMOBJ_INDEXRECMGR                                           MEMORYCLERK_SQLOPTIMIZER
    64          MEMOBJ_RULETABLEGLOBAL                                       MEMORYCLERK_SQLGENERAL
    56          MEMOBJ_SERVICEBROKER                                         MEMORYCLERK_SQLSERVICEBROKER
    56          MEMOBJ_REMOTESESSIONCACHE                                    MEMORYCLERK_SQLGENERAL
    56          MEMOBJ_PARSE                                                 CACHESTORE_PHDR
    48          MEMOBJ_CACHESTOREBROKERTBLACS                                CACHESTORE_BROKERTBLACS
    48          MEMOBJ_APPENDONLYSTORAGEUNITMGR                              MEMORYCLERK_SQLSTORENG
    40          MEMOBJ_SBASBMANAGER                                          MEMORYCLERK_SQLSERVICEBROKER
    32          MEMOBJ_OPTINFOMGR                                            MEMORYCLERK_SQLOPTIMIZER
    32          MEMOBJ_SBTRANSPORT                                           MEMORYCLERK_SQLSERVICEBROKERTRANSPORT
    32          MEMOBJ_CACHESTOREBROKERREADONLY                              CACHESTORE_BROKERREADONLY
    32          MEMOBJ_DIAGNOSTIC                                            MEMORYCLERK_SQLGENERAL
    32          MEMOBJ_UCS                                                   MEMORYCLERK_SQLSERVICEBROKER
    24          MEMOBJ_STACKSTORE                                            CACHESTORE_STACKFRAMES
    24          MEMOBJ_CACHESTORESXC                                         USERSTORE_SXC
    24          MEMOBJ_FULLTEXTGLOBAL                                        MEMORYCLERK_FULLTEXT
    24          MEMOBJ_APPLOCKLVB                                            OBJECTSTORE_LOCK_MANAGER
    24          MEMOBJ_FULLTEXTSTOPLIST                                      CACHESTORE_FULLTEXTSTOPLIST
    24          MEMOBJ_CONVPRI                                               CACHESTORE_CONVPRI
    16          MEMOBJ_SQLCLR_VMSPY                                          MEMORYCLERK_SQLCLR
    16          MEMOBJ_VIEWDEFINITIONS                                       MEMORYCLERK_SQLOPTIMIZER
    16          MEMOBJ_SBACTIVATIONMANAGER                                   MEMORYCLERK_SQLSERVICEBROKER
    16          MEMOBJ_AUDIT_EVENT_BUFFER                                    OBJECTSTORE_SECAUDIT_EVENT_BUFFER
    16          MEMOBJ_HASHGENERAL                                           MEMORYCLERK_SQLQUERYEXEC
    16          MEMOBJ_SBTIMEREVENTCACHE                                     MEMORYCLERK_SQLSERVICEBROKER
    16          MEMOBJ_ASYNCHSTATS                                           MEMORYCLERK_SQLGENERAL
    16          MEMOBJ_BADPAGELIST                                           MEMORYCLERK_SQLUTILITIES
    16          MEMOBJ_QSCANSORTNEW                                          MEMORYCLERK_SQLQUERYEXEC
    16          MEMOBJ_SCTCLEANUP                                            MEMORYCLERK_SQLGENERAL
    16          MEMOBJ_XP                                                    MEMORYCLERK_SQLXP
    8           MEMOBJ_SECURITY                                              MEMORYCLERK_SQLGENERAL
    8           MEMOBJ_CACHESTOREBROKERRSB                                   CACHESTORE_BROKERRSB
    8           MEMOBJ_EXCHANGEXID                                           MEMORYCLERK_SQLGENERAL
    8           MEMOBJ_CACHESTOREVENT                                        CACHESTORE_EVENTS
    8           MEMOBJ_CACHESTOREXPROC                                       CACHESTORE_XPROC
    8           MEMOBJ_DBMIRRORING                                           MEMORYCLERK_SQLUTILITIES
    8           MEMOBJ_SERVICEBROKERTRANSOBJ                                 CACHESTORE_BROKERTO
    8           MEMOBJ_CACHESTOREOBJCP                                       CACHESTORE_OBJCP
    8           MEMOBJ_CACHESTOREXMLDBELEMENT                                CACHESTORE_XMLDBELEMENT
    8           MEMOBJ_ENTITYVERSIONINFO                                     MEMORYCLERK_SQLSTORENG
    8           MEMOBJ_AUDIT_MGR                                             MEMORYCLERK_SQLGENERAL
    8           MEMOBJ_EXCHANGEPORTS                                         MEMORYCLERK_SQLGENERAL
    8           MEMOBJ_DEADLOCKXML                                           MEMORYCLERK_SQLSTORENG
    8           MEMOBJ_CACHESTORETEMPTABLE                                   CACHESTORE_TEMPTABLES
    8           MEMOBJ_HTTPSNICONTROLLER                                     MEMORYCLERK_SQLHTTP
    8           MEMOBJ_CACHESTOREVIEWDEFINITIONS                             CACHESTORE_VIEWDEFINITIONS
    8           MEMOBJ_CACHESTOREPHDR                                        CACHESTORE_PHDR
    8           MEMOBJ_CACHESTOREXMLDBTYPE                                   CACHESTORE_XMLDBTYPE
    8           MEMOBJ_CACHESTORE_BROKERUSERCERTLOOKUP                       CACHESTORE_BROKERUSERCERTLOOKUP
    8           MEMOBJ_EVENTSUBSYSTEM                                        MEMORYCLERK_SQLGENERAL
    8           MEMOBJ_CACHESTOREBROKERDSH                                   CACHESTORE_BROKERDSH
    8           MEMOBJ_SOSDEADLOCKMONITORXMLREPORT                           MEMORYCLERK_SQLSTORENG
    8           MEMOBJ_CACHESTOREXMLDBATTRIBUTE                              CACHESTORE_XMLDBATTRIBUTE
    8           MEMOBJ_CACHESTOREBROKERKEK                                   CACHESTORE_BROKERKEK
    8           MEMOBJ_QPMEMGRANTINFO                                        MEMORYCLERK_SQLQUERYEXEC
    8           MEMOBJ_CACHESTOREQNOTIFMGR                                   CACHESTORE_NOTIF
    (101 row(s) affected)
    David

Maybe you are looking for