MS-SQL 2005/ECC6/W3K

[Former Member]

Dear All,

I am not able to schedule the backup jobs through Tcode -DB13, anybody can advise the best practice to do backup jobs in SAP/MS-SQL 2005/W3K environment !! i.e. tools to use, steps & prcedures, guides etc..

Thanks in advance.

[Former Member]

Hi,

When you say "I am not able to schedule the backup jobs through Tcode -DB13", can you please mention the error that you are getting?

Regards

[Former Member]

Hello Shehryar,

When I do DB13 backup scheduling system throws the following error whenever you logon to system.

DB CHECK Jobs are created with wrong backup parameters. Please see note 126973.

DB CHECK DB CHECK DB CHECK DB CHECK DB CHECK DB CHECK DB CHECK

Server problems were detected during initial system check.

Please, do not use that system before fixing these problems.

Thanks & Regards

[Former Member]

Dear Rayees,

Can you please run the transaction SICK and paste the output in this message.

Can you confirm which SAP_BASIS support pack you are on in SPAM.

Please also run the following two queries on your SAP database and past into this message:

select @@version

go

select serverproperty('collation')

go

Thanks

N.P.C

[Former Member]

Dear N.P.C.

SICK - Output

SAP System Check

DB CHECK Jobs are created with wrong backup parameters. Please see note 126973

DB CHECK DB CHECK DB CHECK DB CHECK DB CHECK DB CHECK DB CHECK DB CHECK DB

Severe problems were detected during initial system check.

Please, do not use that system before fixing these problems.

Support Pack Level

SAP_BASIS 700 0009 SAPKB70009

Query Result

Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

SQL_Latin1_General_CP850_BIN2

Thanks & Regards

[clas_hortien]

Hi,

please follow note 142731 and perform a complete database check by means of SQL Server DBCC command.

Please check at least the SAP database, master, model and msdb database.

Do you see any obvious messages in the SQL errorlog ?

Best regards

Clas

[Former Member]

Dear Clas,

Please find below the DBCC CHECKDB results.

CHECKDB found 0 allocation errors and 0 consistency errors in database 'mssqlsystemresource'.

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Thanks & Regards

[clas_hortien]

Hello,

this is only a part of the master DB check output, do you checked all the other databases as well ?

Regards

Clas

[Former Member]

Dear Clas,

Yes I did for all and did not find any errors or warning !!

Thanks & Regards

[clas_hortien]

Hi,

did you follow note 935968, especially the steps in the solution section ?

Please run the transaction SE38, enter MSSPROCS, and execute it. In the database release field check the version (8 = SQL 2000, 9 = SQL 2005) and press 'start all'. When the transaction is finished, run the transaction SICK again.

Regards

Clas

[Former Member]

Hello Rayees,

If you follow the instructions from Clas it should fix this problem.

When you have resolved this problem, I recommend you apply SP1 for SQL 2005. Your version is the RTM at the moment Microsoft SQL Server 2005 - 9.00.1399.06.

9.00.2047 is SP1 from memory.

Thanks

N.P.C