Quantcast
Channel: SCN: Message List - SAP on SQL Server
Viewing all 2591 articles
Browse latest View live
↧

Re: System copy 'Homogeneous' from MSSQL2005 to SQL2012 on Windows

July 5, 2015, 4:59 am
$
0
0

Hi SS

 

I don't find path in Summary file as well.

 

Summary file is:

 

Dialog "Parameter Mode > Default Settings"

Typicalselected

Dialog "SAP System > General Parameters"

SAP System ID (SAPSID)S11
Installation DriveD:
Unicode System (recommended)deselected

Dialog "SAP System > DNS Domain Name"

Set FQDN for SAP Systemdeselected
DNS Domain Name for SAP System

Dialog "SAP System > Master Password"

Password for all users of this SAP system******

Dialog "SAP System > Windows Domain"

SAP System ID (SAPSID)S11
Local installationselected
Windows Domain

Dialog "SAP System > OS User Passwords"

Password of SAP System Administrator******
Password of SAP System Service User******

Dialog "SAP System > Database"

Homogeneous System Copy (MS SQL Server-specific: Detach/Attach or Backup/Restore)selected
Start Migration Monitor manuallydeselected

Dialog "MS SQL Server > Database Connection Information"

Local MS SQL Server InstancesSAP-DR

Dialog "MS SQL Server > Database Information"

Database ID (DBSID)S11

Dialog "Media Browser > Software Package Request"

Package LocationMedium
D:\SAPMigration\InstallationKernel\51049439_2\Krnl_7.21_EXT_WIN__IA64__x64__SP08_\DATA_UNITS\K_721_N_WINDOWS_X86_64Kernel NW 7.20 / 7.21

Dialog "MS SQL Server > Database Schema"

Password of ABAP Schema******

Dialog "SAP System > Central Instance and ASCS Instance"

Central Instance Number00
ASCS Instance Number01

Dialog "SAP System > Central Instance"

Host with Transport DirectorySAP-DR

Dialog "SAP System > Actions Before Starting System"

Interrupt before SAP System startsdeselected

Dialog "SAP System > DDIC Users"

Password of 'DDIC' in client 000 in the source system******

 

 

 

↧
Search

Re: System copy 'Homogeneous' from MSSQL2005 to SQL2012 on Windows

July 5, 2015, 6:20 am
$
0
0

Hi Sel

 

In target system you are performed detached / attach method, because of this it may not asked for source system export path.

 

 

Regards

SS

↧
↧

Re: System copy 'Homogeneous' from MSSQL2005 to SQL2012 on Windows

July 5, 2015, 10:17 am
$
0
0

Hi Sel,

 

It has been a long time that I don't perform a system copy. In the System Copy guide for SAP NetWeaver systems, there is topic for "Database Specific" topic for MSSQL Server.

 

It's a step before you run SWPM. You restore the database with SSMS and then run SWPM. It is not asked during the execution.

 

Check the system copy guide in the following link.

 

There is also a space for specific questions regarding SWPM in our community:

 

Software Logistics

 

If you could complete your copy, go and mark as answered/helpful answers that assisted you through this and create a new topic.

 

Best Regards,

Luis Darui

SAP Support.

↧

Re: Problem on Shrinking logfile

July 8, 2015, 7:11 am
$
0
0

Hello Nurujjaman,

 

I don't think there is any issue to shrink.As Sriram rightly said it should be done in non-peak business hours.

Below note explains the process in detail..

1224089 - How to shrink a MSSQL Server 2005 / 2008 Database?

 

More information can be found on below links..


https://msdn.microsoft.com/en-us/library/ms190925.aspx

Log truncation does not reduce the size of the physical log file. To reduce the physical size of a physical log file, you need to shrink the log file. For information about shrinking the size of the physical log file, see https://msdn.microsoft.com/en-us/library/ms365418.aspx

 

To reduce the physical size of a physical log file, you must shrink the log file. This is useful if you know that a transaction log file contains unused space that you will not be needing. Shrinking a log file can occur only while the database is online and, also, at least one virtual log file is free. In some cases, shrinking the log may not be possible until after the next log truncation.

 

 

Shrinking database and log files can be set to occur automatically. However, we recommend against automatic shrinking, and the autoshrink database property is set to FALSE by default. If autoshrink is set to TRUE, automatic shrinking reduces the size of a file only when more than 25 percent of its space is unused. The file is shrunk either to the size at which only 25 percent of the file is unused space or to the original size of the file, whichever is larger.

 

Thanks,

Mofizur

↧

Re: Post Installation Steps After Homogeneous Copy

July 8, 2015, 7:30 am
$
0
0

Hi Sel,

 

Regarding question 3.

 

You have to ensure that your jobs are activated in the DBACockpit, usually the installation does it already. The other post-activities regarding the database, SWPM does it already.

 

Another point is to ensure that you're backing up your database on regular basis (full backup > transaction log backup > differential backup > transaction log backup).

 

You can get more details about Backup and Restore strategy for SQL Server in note 1297986.

 

The other questions:

 

1 is more related with Software Logistics (Installation guides/Post-steps installation):

Software Logistics

2 is more related with CTS, not sure what is the space that you could get more help regarding specific question.

 

And I didn't get the 4th question. Are you asking whether you could pull the background jobs from source system to run in the target system? Aren't them already there?

 

All the post-steps required for the system copy are documented in the installation guides, perhaps you could be more specific in which post-step you're in doubt or having issues:

 

COPYING SAP SYSTEMS BASED ON SAP NETWEAVER 7.0 SUPPORT RELEASE 3 / 7.0 INCLUDING 1, 2, OR 3 - USING SOFTWARE PROVISIONING MANAGER 1.0

 

COPYING SAP SYSTEMS BASED ON SAP NETWEAVER 7.1 AND HIGHER - USING SOFTWARE PROVISIONING MANAGER 1.0

 

In order to access the guides you must be logged into Service Marketplace.

 

Best Regards,

Luis Darui

↧
↧

Re: Post Installation Steps After Homogeneous Copy

July 8, 2015, 8:11 am
$
0
0

Hi Sel,

 

The System Copy Guide, which Luis linked (use the first link, the one to systems based on NetWeaver 7.0x) has an entire chapter on "follow-up activities" (it is chapter 6 in the guide). It is practically a step-by-step checklist.

 

With regard to some of your questions, it depends on some of the choices you made for your copy. Was this a system move, in which the SID stayed the same? Or a true copy, where you created a new SID?

 

1. Profiles. No, you do not copy the profiles from your source system. They have too many parameters in them that are system-specific, and will probably break your new target system. Instead, you will go into RZ10 on the new system and choose Utilities -> Import Profiles -> Of Active Servers. This will import the new profiles that SWPM created for you automatically with default settings. Then go into each profile, one by one, make any required changes (you can refer to the original profiles for tuning parameters you'd like to keep), then save and activate them. After saving changed profiles, you will need to restart the system.

 

2. Transport routes and configuration. It depends. Probably not. Was this system the domain controller, or will be the new domain controller? Is it remaining in the same transport domain, or going off on its own somehow? Most likely you will not change anything about your transport routes, but you will need to "add" this system into the existing transport domain, then from the domain controller "accept" (or "approve") it. If it is replacing a system in a transport route, then yes, you'll need to rebuild the routes. If it's going to be a "single system" on the side, like a sandbox or extra test system, or if this copy overwrote an existing system in the route but kept its SID (of the overwritten system), then no, you won't rebuild the routes, you'll just update the configuration. This is all done partly in STMS on the new copied system, and partly in STMS on the transport domain controller.

 

3. Database-level tasks. I think Luis covered this already. SWPM will have automatically setup the basic housekeeping jobs for an SAP database, except for backups. You may need to setup your backup jobs.

 

4. Background jobs. Again, it depends. Did you deschedule all the jobs in the source system before you copied it? If not, you'll find that a bunch of them started trying to run as soon as you started the target system, unless you manually set rdisp/wp_no_btc to 0. Whether or not they succeeded will depend on whether they tried to print before the print devices were adjusted, or needed an RFC connection that needed adjustment, etc. So, you'll need to go into SM37 and look at the "scheduled" jobs and then, one by one, determine whether or not to release them. Many production jobs are probably inappropriate for a test system, but you'll certainly want all the housekeeping jobs. If you aren't sure, you can leave them all alone and then just run a couple processes to set up new default housekeeping jobs:

a. SM36 -> Standard Jobs -> Default Scheduling

b. RZ70 -> Activate Current Configuration -> Start Data Collection and Job Scheduling

c. SA38 -> RDDNEWPP (from client 000)

 

You are going to have to relicense the system (in SLICENSE), adjust the spool server for all print devices (in SPAD), possibly adjust batch server groups (in SM61), possibly adjust logon groups (in SMLG), recreate or recertify SSL certificates (in STRUST), etc. Also, you may need to adjust RFC connections in SM59 in this system and in other systems that talk to it.

 

All of this is covered in the guide at a high level, but experience helps a lot too.

 

Cheers,

Matt

↧

Re: Post Installation Steps After Homogeneous Copy

July 8, 2015, 9:28 am
$
0
0

Thank you so much.

 

Let me go through one by one and keep you update.

↧

Re: Post Installation Steps After Homogeneous Copy

July 8, 2015, 9:28 am
$
0
0

Thank you so much Mr.Matt.

 

Let me go through one by one and keep you update.

↧
Search

Re: Repair or Restore an **Incomplete** SQL 2005 .BAK file

July 3, 2015, 10:43 pm
↧
↧

Re: Post Installation Steps After Homogeneous Copy

July 8, 2015, 9:56 am
↧

Re: Post Installation Steps After Homogeneous Copy

July 8, 2015, 9:58 am
$
0
0

Hello Sel,

 

Please find post step after homogeneous system copy.

 

1. Cancel any production batch jobs:

 

    a. Transaction SM37, enter job name, user “*”, and date range including the next day, job status “released” and click “execute”

 

    b. Select the job, go to the Job menu and click “released->scheduled”

 

2. Delete Source System profiles and Import the correct SAP profiles

 

    a. Transaction RZ10

 

    b. Go to Utilities > Import Profiles > Of Active Servers

 

3. Delete Source System Licenses and install the new Licenses

 

    a. Transaction SLICENSE, click “New Licenses”

 

    b. Select Each license and go to Edit > Delete License

 

    c. Click Install and enter the path to the license key file provided by SAP in the browse field and click Open

 

    d. If you are unable to install the permanent license key, it may be necessary to truncate the SAPLIKEY table first, then repeat 12-c

 

4. Reinitialize in the transport domain

 

    a. Logon to client 000

 

    b. Transaction STMS

 

5. (Optional) Change the login screen to reflect the correct system information

 

    a. Transaction SE61

 

    b. Select general text, ZLOGIN_SCREEN_INFO, change

 

    c. Change the text and save

 

6. Change the Logical System

 

    a. Transaction SCC4

 

    b. Click the edit button

 

    c. Double-click client 100

 

    d. Change the Client Role to Test, and save

 

    e. Then change the Logical System to the appropriate name, and save

 

7. If you are using workflow, you will need to reinitialize it

 

    a. Transaction SWU3

 

    b. Execute the line items marked with a red ‘X’

 

8. If you are using BI, re-activate the system in RSA1 on the BI system

10. Verify the Adobe Document Services connection

 

    a. Transaction SM59

 

    b. Edit the HTTP connection ADS

 

    c. Go to the Logon & Security tab and enter the Administrative Password in the password field, and save

 

    d. Transaction SE38

 

    e. Execute program FP_TEST_00, print preview to test ADS connection

 

    f. A simple adobe form with lines and numbers will be rendered if successful

 

11. Apply any necessary transports

12. Change the logical spool server to point to correct system:

 

    a. Transaction SPAD

 

    b. Select Display for Spool Servers

 

    c. Double click SAP_PRINT SERVER

 

    d. Click the change button

 

    e. In the mapping field select the appropriate application server, and save

 

13. Lock/Unlock users as necessary, using Transaction SU01

14. Stop and restart the SAP system

15. Run SGEN to recompile programs and reports

16. Run BDLS to change logical system

 

For further information you can refer SAP note

For more information about the system copy procedure, see also SAP Notes 193816 and 151603

 

Regards

Anand

↧

Re: Post Installation Steps After Homogeneous Copy

July 8, 2015, 11:41 am
$
0
0

Thanks Sriram

 

The kernel 7.21 Ext has already been applied.

↧

Re: Post Installation Steps After Homogeneous Copy

July 8, 2015, 11:44 am
↧
↧

SMux Provider: Physical Connection is not usable [xFFFFFFFF]

July 9, 2015, 9:07 am
$
0
0

Hi All,

We have migrated our SAP Landscape 5 months back from HP-UX/Oracle to Windows 2012 R2 and SQL Server 2012 R2 SP2. The servers are VM (VMware 5.1) on HP ESX host. From past 3 months we have started getting below error which is very random. This is happening in SAP BI system.Jobs get cancelled with the message saying System Shutdown and on checking the SM21 logs it shows “operating system call receive failed (error no. 10054)”

 

The installation is distributed with DB on one host and CI & App on other hosts within same data center.

 

SM21.png

At the same time there is a dump in ST22

 

SM21.png

 

Things which we have already done:

  1. Checked the SNAC version which is same as the SQL version
  2. Increased the Keep Alive and Keep Alive interval for TCP/IP from 30000 and 1000 to 90000 ND 5000 respectivley.
  3. Increased the TCPMaxDataRetransmission to 10 on the DB server
  4. Checked the recommendation from VMware and HP regarding the network and power setting.
  5. Checked the resource utilization during the time of error and nothing abnormal is reported, which make me think that this can be specific to SQL server settings.
  6. The order of protocol enabled for SQL Server is Shared Memory (1), TCP/IP (2) and Names Pipes (3)

 

  Scheduled niping with the option long Lan stability test, but there doesn’t seems to any drop. It can be because there was no such incident where the error occurred and niping was running, as the error is very random. Happened twice in April and  then in Jul.


This issue is not happening in QA which is having same setting as Prod except for the fact that it is kept in different DC. Also we are not able to replicate the issue as an when desired as it is too random.


Any help or direction to troubleshoot will be a great help.


Thanks,

Manas

↧

Re: SMux Provider: Physical Connection is not usable [xFFFFFFFF]

July 9, 2015, 10:20 am
$
0
0

Hi Manas,

 

I think it is related with VMware. See that after the database disconnection you have also errors to access files in your \\.\sapmnt share.

 

Are you using VMware snapshot backups?

 

My colleague Eduardo has pointed in his blog here: Are you facing disconnections? some interesting points that can help you in case of disconnections when running on VMware:

 

 

Also I think this topic is more related with the following spaces:

 

SAP on Microsoft Windows

Virtualization on Windows

 

As the 10054 error comes from the OS and is, in most of cases, related with network disconnections.

 

Please make sure your system is set with the following recommendations in Note 1056052 - Windows: VMware vSphere configuration guidelines

 

 

Best Regards,

Luis Darui

SAP Support

↧
Search

Re: SMux Provider: Physical Connection is not usable [xFFFFFFFF]

July 9, 2015, 2:22 pm
$
0
0

Thanks for your reply Luis.

 

I have already checked Eduardo's bolg and have consulted with the VM/Infra team and as per them all settings are in place as recommended. Have also reffered to Dale's presentation and checked the pointers mentioned in there.

As I said this issue is very random and only coming in 2 of the production systems (ECC and BI). The QA landsapce is exact replica of Production except for the different data centre.

 

Another thing that I came across from the Note 1593183 - TCP/IP networking parameters for SQL Server is that it mentiones to increase the Keep Alive from 30000 to 90000 on the server side as well. Will that help as I have only increased it on the CI and APP servers.

 

Thanks,

Manas

↧

Re: SMux Provider: Physical Connection is not usable [xFFFFFFFF]

July 10, 2015, 2:45 am
$
0
0

Hi Manas

 

1.  Have you check the VM log any disconnection error during those times?

 

2. Could you share your kernel release & level? if it is low you may require to upgrade the DCK kernel.

 

Regards

SS

↧
↧

having a bit trouble in shrinking the transaction logs

July 10, 2015, 6:17 am
$
0
0

Hi all,


I am using Sql 2008 r2 database and I want to shrink the Transaction logs by giving the script.



DBCC SHRINKFILE(PEMDMPRD2_m000_Log, 1)


LOOOOOOOO1.jpg





But we are unable to achieve the desired result, kindly guide me how I can achieve my desired result.


LOOOOOOOO2.jpg



NOTE: I want to perform the shrink to at-least 50% but am able to achieve only 2% and I don’t want the database to be disturbed as it comprises of production data. Thanks and regards, Kaushik G

↧

Re: having a bit trouble in shrinking the transaction logs

July 10, 2015, 7:30 am
$
0
0

Hello Kaushik,

If your log is 98% used and there is any active transaction you will only be able to shrink 2%.

 

You can check how much of your log is used and the active transactions:

 

DBCC SQLPERF(LOGSPACE)

DBCC OPENTRAN

 

Ensure you don't have any active transaction and perform a log backup before before the log shrink.

 

One question from my side, why do you want to shrink your log file?

 

Regards,

Eduardo Rezende
SAP Support

↧

Re: having a bit trouble in shrinking the transaction logs

July 10, 2015, 9:48 am
$
0
0

Hi Kaushik,

 

Normally once the daily backup completed then you can start the transaction log truncate backup. and also you can enable the option at DB level "Auto Shrink - True " it will take care the  DB & Transaction log shrinking, Kindly refer the snapshot.

 

 

Capture.PNG

 

BR

SS

↧
Viewing all 2591 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>