I submit that a dump on my system, when running a job SAP_COLLECTOR_FOR_PERFMONITOR,

===========================================================================

JOb Error:

===========================================================================

Job started                                                                               

Step 001 started (program RSCOLL00, variant , user ID MGBAUTE)                               

Clean_Plan:Cleanup of DB13 Plannings                                                         

Clean_Plan:started by RSDBPREV                                                               

Clean_Plan:Jobs in System R3D      werden bereinigt                                          

You are not authorized for DB access (S_DBCON: <LOCAL SYSTEM> R3D <Windows authentication> 03)

Function DB6_PLAN_STOP_BATCH_JOB failed with return code = Job error                         

Clean_Plan:terminated with error                                                             

REASON=Job error                                                                             

ABAP/4 processor: COMPUTE_INT_TIMES_OVERFLOW                                                 

Job cancelled                                                                               

===========================================================================

ST22 "Abap Dump"

===========================================================================

Runtime Errors         COMPUTE_INT_TIMES_OVERFLOW                                  

Exception              CX_SY_ARITHMETIC_OVERFLOW                                   

Date and Time          03.06.2009 08:43:12                                                                               

Short text                                                                        

     Whole number overflow on multiplication.                                                                               

What happened?                                                                    

     Error in the ABAP Application Program                                                                               

The current ABAP program "RSMSQSNP" had to be terminated because it has       

     come across a statement that unfortunately cannot be executed.                                                                               

What can you do?                                                                  

     Note down which actions and inputs caused the error.                                                                               

To process the problem further, contact you SAP system                        

     administrator.                                                                               

Using Transaction ST22 for ABAP Dump Analysis, you can look                   

     at and manage termination messages, and you can also                          

     keep them for a long time.                                                                               

Error analysis                                                                    

     An exception occurred that is explained in detail below.                      

     The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not

      caught in                                                                    

     procedure "GET_ELAPSEDSECS" "(FORM)", nor was it propagated by a RAISING      

      clause.                                                                      

     Since the caller of the procedure could not have anticipated that the         

exception would occur, the current program is terminated.                        

The reason for the exception is:                                                 

In the current program "RSMSQSNP", multiplying the numbers 733562 and            

86400 (using the operation '*' or 'MULTIPLY') resulted in a value                

greater than 2147483647 or smaller than -2147483648. This                        

results in a whole number overflow.                                                                               

to correct the error                                                             

It may be possible to break the current process down into subprocesses           

so that only smaller values occur.                                                                               

If the error occurred in your own ABAP program or in an SAP                      

program you modified, try to remove the error.                                                                               

If the error occures in a non-modified SAP program, you may be able to           

find an interim solution in an SAP Note.                                         

If you have access to SAP Notes, carry out a search with the following           

keywords:                                                                               

"COMPUTE_INT_TIMES_OVERFLOW" "CX_SY_ARITHMETIC_OVERFLOW"                         

"RSMSQSNP" or "RSMSQSNP"                                                         

"GET_ELAPSEDSECS"                                                                

System environment                                                               

    SAP-Release 700                                                                               

Application server... "srvctrsapd01"                                         

    Network address...... "200.200.1.2"                                          

    Operating system..... "Windows NT"                                           

    Release.............. "5.2"                                                  

    Hardware type........ "4x Intel 80686"                                       

    Character length.... 8 Bits                                                  

    Pointer length....... 32 Bits                                                

    Work process number.. 15                                                     

    Shortdump setting.... "full"                                                                               

Database server... "SRVCTRSAPD01"                                            

    Database type..... "MSSQL"                                                   

    Database name..... "R3D"                                                     

    Database user ID.. "r3d"                                                                               

Char.set.... "Spanish_Spain.1252"                                                                               

SAP kernel....... 700                                                        

    created (date)... "Aug 25 2008 01:11:49"                                     

    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"             

    Database version. "SQL_Server_8.00 "                                                                               

Patch level. 175                                                             

    Patch text.. " "                                                                               

Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"             

    SAP database version. 700                                                    

    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

     NT 6.0"                                                                     

Termination occurred in the ABAP program "RSMSQSNP" - in "GET_ELAPSEDSECS". 

The main program was "RSMSQSNP ".                                                                               

In the source code you have the termination point in line 205               

of the (Include) program "RSMSQSNP".                                        

The program "RSMSQSNP" was started as a background job.                     

Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"                             

Job Initiator.. "MGBAUTE"                                                   

Job Number..... 07431004                                                    

The termination is caused because exception "CX_SY_ARITHMETIC_OVERFLOW"     

occurred in                                                                

procedure "GET_ELAPSEDSECS" "(FORM)", but it was neither handled locally nor

declared                                                                   

in the RAISING clause of its signature.                                                                               

The procedure is in program "RSMSQSNP "; its source code begins in line     

172 of the (Include program "RSMSQSNP ".                                    

Thank and regards for your help.

Gustavo Gonzalez.

Hi experts,

  I install a non shared disk cluster on SQL 2012 AlwaysOn like the procedure below. It runs on first node without any problems.

However, when I fail over ASCS to second node, I always get an error: login not possible(error in license check). I check every item in the KBA: 1512766 and I find it can't connect to MS on second node. I try to restart SAP servers but the problem persists, please help.

----------------------------------------------------------------------------------------------

Thu Aug 22 17:58:59 2013

***LOG Q0I=> NiPConnect2: 10.243.23.60:3901: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3286]

*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 1232

    (SI_ECONN_REFUSE/10061; I4; ST; 10.243.23.60:3901) [nixxi.cpp    3286]

*** ERROR => MsIAttachEx: NiBufConnect to sapgrptcd/3901 failed (rc=NIECONN_REFUSED) [msxxi.c 718]

***LOG Q0L=> DpLoopInit, nomscon () [dpxxdisp.c   1801]

CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.

CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.

CCMS: start to initalize 3.X shared alert area (first segment).

DpAppcBlksLow: max appc blocks in queue is 1000 (50 %)

DpWpBlksLow: max wp blocks in queue is 1600 (80 %)

Thu Aug 22 17:59:40 2013

***LOG Q0I=> NiPConnect2: 10.243.23.60:3901: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3286]

*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 49/sock 1544

    (SI_ECONN_REFUSE/10061; I4; ST; 10.243.23.60:3901) [nixxi.cpp    3286]

*** ERROR => MsIAttachEx: NiBufConnect to sapgrptcd/3901 failed (rc=NIECONN_REFUSED) [msxxi.c 718]

----------------------------------------------------------------------------------------------

First node downtime:

1. 1.     1. 70SWPM -> System copy -> First node
2. 2.     2. Change dbs/mss/server & SAPDBHOST to node 1
3. 3.     3. 70SWPM -> System copy -> Database instance

Second node downtime:

1. 1.     4. 70SWPM -> System copy -> Additional node
2. 2.     5. Change SAPDBHost and dbs/mss/server to AG Listener

  6.     Sp_help_revlogin + add sysadmin role for SAPserivce<SID> + SWPM(7.3) -> Database copy completion

HI EXPERTS I TRY TO IMPORT A SUPPORT PACKAGE IN SOLMAN WINDOWS SERVER 2008 R2 WITH SQL SERVER 2008 R2 BUT A I CANu00B4T BECAUSE THE USER <SID>ADM DONT HAVE PERMISION TO LOGON DB. I APLIED R3trans.exe -d WITH THE USER <SID>ADM AND AS A RESULT IS THAT:

4 ETW000 E:\usr\sap\slm\sys\exe\uc\NTAMD64\R3trans.exe version 6.14 (release 701 - 23.07.10 - 09:23:00).

4 ETW000 unicode enabled version

4 ETW000 ===============================================

4 ETW000

4 ETW000 date&time   : 18.08.2011 - 14:44:43

4 ETW000 control file: <no ctrlfile>

4 ETW000 R3trans was called as follows: E:\usr\sap\slm\sys\exe\uc\NTAMD64\R3trans.exe -d

4 ETW000  trace at level 2 opened for a given file pointer

4 ETW000  [dev trc     ,00000]  Thu Aug 18 14:44:46 2011                                               11769  0.011769

4 ETW000  [dev trc     ,00000]  db_con_init called                                                        25  0.011794

4 ETW000  [dev trc     ,00000]  create_con (con_name=R/3)                                                633  0.012427

4 ETW000  [dev trc     ,00000]  Loading DB library 'dbmssslib.dll' ...                                    52  0.012479

4 ETW000  [dev trc     ,00000]  DlLoadLib success: LoadLibrary("dbmssslib.dll"), hdl 0, addr 0000000186BB0000

4 ETW000                                                                                139786  0.152265

4 ETW000  [dev trc     ,00000]      using "E:\usr\sap\slm\sys\exe\uc\NTAMD64\dbmssslib.dll"               16  0.152281

4 ETW000  [dev trc     ,00000]  Library 'dbmssslib.dll' loaded                                            18  0.152299

4 ETW000  [dev trc     ,00000]  function DbSlExpFuns loaded from library dbmssslib.dll                    19  0.152318

4 ETW000  [dev trc     ,00000]  Version of 'dbmssslib.dll' is "700.08", patchlevel (0.117)              3239  0.155557

4 ETW000  [dev trc     ,00000]  function dsql_db_init loaded from library dbmssslib.dll                   29  0.155586

4 ETW000  [dev trc     ,00000]  function dbdd_exp_funs loaded from library dbmssslib.dll                  21  0.155607

4 ETW000  [dev trc     ,00000]  New connection 0 created                                                  31  0.155638

4 ETW000  [dev trc     ,00000]  000: name = R/3, con_id = -000000001, state = DISCONNECTED, tx = NO , hc = NO , perm = YES,

4 ETW000                             reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO

4 ETW000                                                                                49  0.155687

4 ETW000  [dev trc     ,00000]  db_con_connect (con_name=R/3)                                             24  0.155711

4 ETW000  [dev trc     ,00000]  find_con_by_name found the following connection for reuse:                16  0.155727

4 ETW000  [dev trc     ,00000]  000: name = R/3, con_id = 000000000, state = DISCONNECTED, tx = NO , hc = NO , perm = YES,

4 ETW000                             reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO

4 ETW000                                                                                44  0.155771

4 ETW000  [dev trc     ,00000]  Thread ID:7748                                                         16461  0.172232

4 ETW000  [dev trc     ,00000]  Thank You for using the SLODBC-interface                                  24  0.172256

4 ETW000  [dev trc     ,00000]  Using dynamic link library 'E:\usr\sap\slm\sys\exe\uc\NTAMD64\dbmssslib.dll'

4 ETW000                                                                                32  0.172288

4 ETW000  [dev trc     ,00000]  dbmssslib.dll patch info                                                  27  0.172315

4 ETW000  [dev trc     ,00000]    SAP patchlevel  0                                                       16  0.172331

4 ETW000  [dev trc     ,00000]    SAP patchno  117                                                        15  0.172346

4 ETW000  [dev trc     ,00000]    Last MSSQL DBSL patchlevel 0                                            19  0.172365

4 ETW000  [dev trc     ,00000]    Last MSSQL DBSL patchno         117                                     29  0.172394

4 ETW000  [dev trc     ,00000]    Last MSSQL DBSL patchcomment Tables ########## in SM50 or SM66 (1523684)

4 ETW000                                                                                77  0.172471

4 ETW000  [dev trc     ,00000]  lpc:(local) connection used on SMAPORTA                                 3990  0.176461

4 ETW000  [dev trc     ,00000]  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2285]

4 ETW000                                                                                42813  0.219274

4 ETW000  [dev trc     ,00000]  (18456) [28000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'SMAPORTA\slmadm'.

4 ETW000                                                                                31  0.219305

4 ETW000  [dev trc     ,00000]  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2285]

4 ETW000                                                                                2399  0.221704

4 ETW000  [dev trc     ,00000]  (18456) [28000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'SMAPORTA\slmadm'.

4 ETW000                                                                                31  0.221735

4 ETW000  [dev trc     ,00000]  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2285]

4 ETW000                                                                                2398  0.224133

4 ETW000  [dev trc     ,00000]  (18456) [28000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'SMAPORTA\slmadm'.

4 ETW000                                                                                31  0.224164

4 ETW000  [dev trc     ,00000]  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2285]

4 ETW000                                                                                3724  0.227888

4 ETW000  [dev trc     ,00000]  (18456) [28000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'SMAPORTA\slmadm'.

4 ETW000                                                                                32  0.227920

4 ETW000  [dev trc     ,00000]  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2285]

4 ETW000                                                                                2440  0.230360

4 ETW000  [dev trc     ,00000]  (18456) [28000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'SMAPORTA\slmadm'.

4 ETW000                                                                                31  0.230391

4 ETW000  [dev trc     ,00000]  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2285]

4 ETW000                                                                                2433  0.232824

4 ETW000  [dev trc     ,00000]  (18456) [28000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'SMAPORTA\slmadm'.

4 ETW000                                                                                31  0.232855

4 ETW000  [dev trc     ,00000]  Connection 0 failed using Driver={SQL Server Native Client 10.0};Server=SMAPORTA;AutoTranslate=no;Trusted_Connection=yes;WSID=SMAPORTA;APP=R3 00 comm rd ODBC;Database=SLM;

4 ETW000                                                                                41  0.232896

4 ETW000  [dblink      ,00433]  ***LOG BY2=>sql error 18456  performing CON [dblink#4 @ 433]            8207  0.241103

4 ETW000  [dblink      ,00433]  ***LOG BY0=>[Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'SMAPORTA\slmadm'. [dblink#4 @ 433]

4 ETW000                                                                                42  0.241145

2EETW169 no connect possible: "DBMS = MSSQL                            ---  SERVER = 'SMAPORTA' DBNAME = 'SLM'"

PLEASE HELP ME EXPERTS!!!

Hi experts,

we get the following error messages each monday morning:

Database error 4860 at OPC

> [Microsoft][SQL Server Native Client 10.0][SQL Server]Cann

> bulk load. The file "C:\Program Files\Microsoft SQL

> Server\MSSQL10.MSSQLSERVER\MSSQL\CCMS_CHECK_DB_HIST_2011.txt

> does not exist.

Database error 4860

Database error 911 at OPC

> [Microsoft][SQL Server Native Client 10.0][SQL

> Server]Database 'mssqlsystemresource' does not exist. Make

> sure that the name is entered correctly.

Database error 911

We found this error messages on two independent ECC 6.0 systems which both run MS SQL Server since activating early watch reports. At this time data for the early watch report is collected, maybe this is the trigger for this error. But I think that the real cause for this error is located somewhere in the database configuration.

By the way there is no shortdump or any additional information in the EWA report.

Any ideas or hints? Thank you in advance.

Hi All

During installing MS SQL server 2005 ,i am getting the error like

Could not start SQL server Service.

When trying to start the service manually ,getting error like service could nto start in a timely fashion.

We are using Windows 2003 SP2 with 12 CPUs .

This is a domaininstallation ,the accounts are present ,but when tried with local installation also ,got the same error.

Is this article is of any use

http://support.microsoft.com/kb/954835

Does there any issue with Win 2003 SP2 and SQL Server domain installationwiht named instance.

Pls let me know if you have any suggestions.

Regards

Ajay

Respected Guru's,

we are unable to access user SAP* as the password is not available.

I need to delete user SAP* from database table and restart the server using MSSQL 2005 server.

Please help me to do so, as i am a novice in MSSQL 2005 server.

Regards,

Daya

Hi All,

I got a couple of dumps DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC in BW production.

Below is the screen shot.

How to correct the error                                                          

    Database error text........: "ORA-00060: deadlock detected while waiting for  

     resource"                                                                    

    Internal call code.........: "[RSQL/INSR//BIC/FZSDGL ]"                       

    Please check the entries in the system log (Transaction SM21).                                                                               

You may able to find an interim solution to the problem                       

    in the SAP note system. If you have access to the note system yourself,       

    use the following search criteria:                                                                               

-

    "DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC                                      

    "GP3WBSX71P2XVNPZ488HSACPEL5" or "GP3WBSX71P2XVNPZ488HSACPEL5"                

    "WRITE_ICFACT"                                                                

Pls help to resolve the issue.

Regards,

Kris

Edited by: raama krishna on Apr 1, 2008 10:55 PM

I have recently restored a newly built Test server (stand alone Target) with a copy of a system (source) from a different network (meaning the 2 networks are totally seperate and can not connect to each other).

But when the standard background jobs "SAP_CCMS_MONI_BATCH_DP - RSAL_BATCH_TOOL_DISPATCHING" and "SAP_COLLECTOR_FOR_NONE_R3_STAT - RSN3_STAT_COLLECTOR" run, they do finish succesfully, but have system error messages "Operating system call gethostbyname failed (error no. 11004)" for each.

I've reviewed the trace record for that work process and find:

Wed Feb 17 16:09:26 2010                                                                               

***LOG Q0I=> NiPGetHostByName: hostname 'XXXXXX-906' not found: gethostbyname (11004: WSANO_DATA: Valid name, no data record of

• ERROR => ThCPIC: NiHostToAddr failed [thxxcpic.c   1866]                                                                    

RFC 1485  CONVID                                                                               

• CMRC=19 DATA=0 STATUS=0 SAPRC=497 ThSAPOCMINIT                                                                               

RFC> ABAP Programm: CL_SLD_ACCESSOR===============CP (Transaction: )                                                            

RFC> User: DDIC (Client: 100)                                                                               

RFC> Destination: SAPSLDAPI (handle: 1, , )                                                                               

TH VERBOSE LEVEL FULL                                                                               

• RABAX: end RX_GET_MESSAGE                                                                               

• ERROR => ThCPIC: NiHostToAddr failed [thxxcpic.c   1866]                                                                    

RFC 1485  CONVID                                                                               

• CMRC=19 DATA=0 STATUS=0 SAPRC=497 ThSAPOCMINIT                                                                               

RFC> ABAP Programm: CL_SLD_ACCESSOR===============CP (Transaction: )                                                            

RFC> User: DDIC (Client: 100)                                                                               

RFC> Destination: SAPSLDAPI (handle: 2, , )                                                                               

TH VERBOSE LEVEL FULL                                                                               

• RABAX: end RX_GET_MESSAGE                                                                               

It should be noted that the hostname 'xxxxxx-906' is a server in the source system that was used for CUA.

I've run "rsdelcua" to take the target server out of CUA.

I've deleted all of the Source system RFC entries.

I've deleted all of the source system entries out of tables RSWTTR02, ALCONSEG, SWNCMONI, SMNCMONIINDEX, SAPLSERV and the like.

I've made sure an empty line is the last line in the host file.

The system profiles are new and do not have references to any other (source system) servers.

I did copy the source system background jobs making changes to reference the Target system \ client, although the above mentioned jobs do not have variants that required it.

I'm stumped on this one. Does anyone out there have any suggestions?

Hi

      I am getting following error .     Process terminated by signal 0

     The current ABAP "SAPLSD41" program had to be terminated because the  

     ABAP processor detected an internal system error.          

        An R/3 System process was terminated by an operating system signal.                     

        -                                                                               

Possible reasons for this are:                                                          

        1. Internal system error.                                                               

        2. Process was terminated externally (by the system administrator).                     

           -                                                                               

Last error logged in SAP kernel                                                                               

Component............ "Taskhandler"                                                     

        Place................ "SAP-Server sugarland_DE1_11 on host sugarland (wp 1)"            

        Version.............. 1                                                                 

        Error code........... 11                                                                

        Error text........... "ThSigHandler: signal"                                            

        Description.......... " "                                                               

        System call.......... " "                                                               

        Module............... "thxxhead.c"                                                      

        Line................. 10852                                                                               

The error reported by the operating system is:        

How to correct the Error

The R/3 System work directory (e.g. /usr/sap/c11/D00/work ) often        

contains a file called 'core'.                                                                               

Save this file under another name.                                                                               

If you cannot solve the problem yourself and want to send an error       

notification to SAP, include the following information:                                                                               

1. The description of the current problem (short dump)                                                                               

To save the description, choose "System->List->Save->Local File       

(Unconverted)".                                                                               

2. Corresponding system log                                                                               

Display the system log by calling transaction SM21.                   

   Restrict the time interval to 10 minutes before and five minutes      

after the short dump. Then choose "System->List->Save->Local File        

(Unconverted)".                                                                               

3. If the problem occurs in a problem of your own or a modified SAP                                        

        Error number..... " "                                                                   

Information on where terminated                                               

         Termination occurred in the ABAP program "SAPLSD41" - in "SYSTEM-EXIT".   

         The main program was "SAPMSRD0 ".                                                                               

In the source code you have the termination point in line 0               

         of the (Include) program " ".                                             

Need your advice on this?

Thanks

Srikanth

Hi community,

We are running SAP EHP 1 for SAP Solution Manager 7.0 on MS SQL Server 2005 Release 9.00.3042  DB.

From this morning without install/update/change nothing, we have got on systemlog and trace data, lot of entries with this detail:

Database error 7719 at EXE

ExecuteAndFlush return code: 0x80040e14 Stmt: [ALTER PARTITION FUNCTION [/BI0/F0SMD_PE2H_PFUN0]() SPLIT RANGE (0000001009) ]

sloledb.cpp [ExecuteAndFlush,line 6678]: Error/Message: (err 7719, sev 0), CREATE/ALTER partition function failed as only a maxim

Procname: [ExecuteAndFlush - no proc]

DbSlExecute - Error 99 (dbcode 7719) on DDLExecute

DbSlExecute - <ALTER PARTITION FUNCTION [/BI0/F0SMD_PE2H_PFUN0]() SPLIT RANGE (0000001009) >

dbdsmss: DBSL99 SQL7719

CREATE/ALTER partition function failed as only a maximum of 1000 partitions can be created.

***LOG BY2=> sql error 7719       performing EXE        [dbds#2 @ 699] [dbds    0699 ]

***LOG BY0=> CREATE/ALTER partition function failed as only a maximum of 1000 partitions can be created. [dbds#2 @ 699] [dbds

***LOG BY2=> sql error 7719       performing EXE        [dbacds#2 @ 893] [dbacds  0893 ]

On SE14 I found anything whit the name /BI0/F0SMD_PE2H table and function /BI0/F0SMD_PE2H_PFUN0. Check option was succesfully but indicates number of partitions =1000.

After look for any similar situation, I didn't found nothing except this SDN Thread: BI : msg " Database error 7719 at EXE " during loading Here the solution applied is not valid to our system because the OSS Note 1494789 - Enabling 1000+ partitions support on SQL Server is by SQL Server 2008 SP2 (not our version).

On OSS Note 1010854 - Table with too many partitions on SQL Server 2005/2008 I am not really sure about if the solution(symptom2)  fits to our problem.

And on OSS Note Note 869407 - Partitioning on Microsoft SQL Server i didn't correct with tool RSDD_MSSQL_CUBEANALYZE because we don't have enabled the (vardecimal) compression.

Do you know how can I achive this error???

Thanks in advance!

Scottie

Hi experts,

we get the following error messages each monday morning:

Database error 4860 at OPC

> [Microsoft][SQL Server Native Client 10.0][SQL Server]Cann

> bulk load. The file "C:\Program Files\Microsoft SQL

> Server\MSSQL10.MSSQLSERVER\MSSQL\CCMS_CHECK_DB_HIST_2011.txt

> does not exist.

Database error 4860

Database error 911 at OPC

> [Microsoft][SQL Server Native Client 10.0][SQL

> Server]Database 'mssqlsystemresource' does not exist. Make

> sure that the name is entered correctly.

Database error 911

We found this error messages on two independent ECC 6.0 systems which both run MS SQL Server since activating early watch reports. At this time data for the early watch report is collected, maybe this is the trigger for this error. But I think that the real cause for this error is located somewhere in the database configuration.

By the way there is no shortdump or any additional information in the EWA report.

Any ideas or hints? Thank you in advance.

Hey all,

Which versions, if any, of SAP Business One support MS SQL Server 2012?

Hi Guys,

I am trying to connect to one of the SQL Server in my Domain. I have made entries as mentioned by SAP note in DBCO Transaction. When I am testing connection through program 'ADBC_TEST_CONNECTION' it is showing me following error:

Testing a Database Connection Defined in DBCON

Could not open connection SQLCONNECTION

sql error          1- occured:

I have already installed DBMSSSLIB.DLL in executable directory also.

Please advice.

Thanks,

Usman Malik

I have recently restored a newly built Test server (stand alone Target) with a copy of a system (source) from a different network (meaning the 2 networks are totally seperate and can not connect to each other).

But when the standard background jobs "SAP_CCMS_MONI_BATCH_DP - RSAL_BATCH_TOOL_DISPATCHING" and "SAP_COLLECTOR_FOR_NONE_R3_STAT - RSN3_STAT_COLLECTOR" run, they do finish succesfully, but have system error messages "Operating system call gethostbyname failed (error no. 11004)" for each.

I've reviewed the trace record for that work process and find:

Wed Feb 17 16:09:26 2010                                                                               

***LOG Q0I=> NiPGetHostByName: hostname 'XXXXXX-906' not found: gethostbyname (11004: WSANO_DATA: Valid name, no data record of

• ERROR => ThCPIC: NiHostToAddr failed [thxxcpic.c   1866]                                                                    

RFC 1485  CONVID                                                                               

• CMRC=19 DATA=0 STATUS=0 SAPRC=497 ThSAPOCMINIT                                                                               

RFC> ABAP Programm: CL_SLD_ACCESSOR===============CP (Transaction: )                                                            

RFC> User: DDIC (Client: 100)                                                                               

RFC> Destination: SAPSLDAPI (handle: 1, , )                                                                               

TH VERBOSE LEVEL FULL                                                                               

• RABAX: end RX_GET_MESSAGE                                                                               

• ERROR => ThCPIC: NiHostToAddr failed [thxxcpic.c   1866]                                                                    

RFC 1485  CONVID                                                                               

• CMRC=19 DATA=0 STATUS=0 SAPRC=497 ThSAPOCMINIT                                                                               

RFC> ABAP Programm: CL_SLD_ACCESSOR===============CP (Transaction: )                                                            

RFC> User: DDIC (Client: 100)                                                                               

RFC> Destination: SAPSLDAPI (handle: 2, , )                                                                               

TH VERBOSE LEVEL FULL                                                                               

• RABAX: end RX_GET_MESSAGE                                                                               

It should be noted that the hostname 'xxxxxx-906' is a server in the source system that was used for CUA.

I've run "rsdelcua" to take the target server out of CUA.

I've deleted all of the Source system RFC entries.

I've deleted all of the source system entries out of tables RSWTTR02, ALCONSEG, SWNCMONI, SMNCMONIINDEX, SAPLSERV and the like.

I've made sure an empty line is the last line in the host file.

The system profiles are new and do not have references to any other (source system) servers.

I did copy the source system background jobs making changes to reference the Target system \ client, although the above mentioned jobs do not have variants that required it.

I'm stumped on this one. Does anyone out there have any suggestions?

Dears,

I need to do performance tuning of my demo system as its response time is very slow.In performance tuning I am little bit aware of its basic concept like how to find that which response time is low and how to recover that but issue is that we daily stop our this server in the evening and start it in the morning so due to it I can not follow that concept of finding which response time is slow as due to buffer refresh daily obviously its database time will be high.

Now I want to check that whether all parameters like buffer are set correctly to provide us a good response time.

One more thing I want to confirm My RAM is 4 GB initially I was using 12 GB paging memory now i am thinking it to change it to 16 GB,Will it effect my system performance and how can i make it effective in my SAP system.

Please suggest.

Shivam

Hi

      I am getting following error .     Process terminated by signal 0

     The current ABAP "SAPLSD41" program had to be terminated because the  

     ABAP processor detected an internal system error.          

        An R/3 System process was terminated by an operating system signal.                     

        -                                                                               

Possible reasons for this are:                                                          

        1. Internal system error.                                                               

        2. Process was terminated externally (by the system administrator).                     

           -                                                                               

Last error logged in SAP kernel                                                                               

Component............ "Taskhandler"                                                     

        Place................ "SAP-Server sugarland_DE1_11 on host sugarland (wp 1)"            

        Version.............. 1                                                                 

        Error code........... 11                                                                

        Error text........... "ThSigHandler: signal"                                            

        Description.......... " "                                                               

        System call.......... " "                                                               

        Module............... "thxxhead.c"                                                      

        Line................. 10852                                                                               

The error reported by the operating system is:        

How to correct the Error

The R/3 System work directory (e.g. /usr/sap/c11/D00/work ) often        

contains a file called 'core'.                                                                               

Save this file under another name.                                                                               

If you cannot solve the problem yourself and want to send an error       

notification to SAP, include the following information:                                                                               

1. The description of the current problem (short dump)                                                                               

To save the description, choose "System->List->Save->Local File       

(Unconverted)".                                                                               

2. Corresponding system log                                                                               

Display the system log by calling transaction SM21.                   

   Restrict the time interval to 10 minutes before and five minutes      

after the short dump. Then choose "System->List->Save->Local File        

(Unconverted)".                                                                               

3. If the problem occurs in a problem of your own or a modified SAP                                        

        Error number..... " "                                                                   

Information on where terminated                                               

         Termination occurred in the ABAP program "SAPLSD41" - in "SYSTEM-EXIT".   

         The main program was "SAPMSRD0 ".                                                                               

In the source code you have the termination point in line 0               

         of the (Include) program " ".                                             

Need your advice on this?

Thanks

Srikanth

Hi,

we are getting below dump while the user executing the IW32 transaction, please advice me

Short text
    The current application triggered a termination with a short dump.

What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).

What can you do?
    Note down which actions and inputs caused the error.

    To process the problem further, contact you SAP system
    administrator.

    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.

Error analysis
    Short text of error message:
    Program error (contact your system administrator)

    Long text of error message:
     Diagnosis
         An internal error has occurred.
     System Response
         Processing stopped.
     Procedure
         Contact your system administrator.
         If possible, send all relevant documents to SAP for analysis.

    Technical information about the message:
    Message class....... "CO"
    Number.............. 901
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "

Hello.

I have a SAP system running in SQL Server 2003.

I need to connect to external MySQL DB., to operate with this information in ABAP program.

I have done the step necesary... I mean I go to DBCO transaction and configure the connection like this:

DB CONNECTION --> AFIS

DBMS --> MSS

user name --> xxxxxx

DBpass -->xxxxxx / xxxxxx

Conn Info -->MSSQL_SERVER=192.168.1.233 MSSQL_DBNAME=alliance OBJECT_SOURCE=alliance

I do a test program, when I do the statement CONNECT TO, sy-subrc 0 and connection = DEFAULT... I mean, with this form I cannot connect to MySQL Database...

Can you help me to do this?? I think the problem it's the connection string in DBCO... but I'm not sure...,

Would be possible to connect by MySQL ODBC??? I mean , installing the ODBC driver in my SAP server, and using this in ABAP Program??

Thks.

DATA: BEGIN OF wa,

cod_modelo(20),

END OF wa.

DATA: dbs TYPE dbcon-con_name.

DATA: con(20) TYPE c.

DATA : ls_wa LIKE wa.

con = 'AFIS'. "DB Connection in DBCO above

EXEC SQL.

CONNECT TO :con

ENDEXEC.

WRITE sy-subrc. ---> The result it's 4

EXEC SQL.

GET CONNECTION :con

ENDEXEC.

WRITE : con. --> The result it's DEFAULT

EXEC SQL.

SET CONNECTION DEFAULT

ENDEXEC.

write : con. --> The result it's DEFAULT

Hi All,

I got a couple of dumps DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC in BW production.

Below is the screen shot.

How to correct the error                                                          

    Database error text........: "ORA-00060: deadlock detected while waiting for  

     resource"                                                                    

    Internal call code.........: "[RSQL/INSR//BIC/FZSDGL ]"                       

    Please check the entries in the system log (Transaction SM21).                                                                               

You may able to find an interim solution to the problem                       

    in the SAP note system. If you have access to the note system yourself,       

    use the following search criteria:                                                                               

-

    "DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC                                      

    "GP3WBSX71P2XVNPZ488HSACPEL5" or "GP3WBSX71P2XVNPZ488HSACPEL5"                

    "WRITE_ICFACT"                                                                

Pls help to resolve the issue.

Regards,

Kris

Edited by: raama krishna on Apr 1, 2008 10:55 PM

Hi experts,

we get the following error messages each monday morning:

Database error 4860 at OPC

> [Microsoft][SQL Server Native Client 10.0][SQL Server]Cann

> bulk load. The file "C:\Program Files\Microsoft SQL

> Server\MSSQL10.MSSQLSERVER\MSSQL\CCMS_CHECK_DB_HIST_2011.txt

> does not exist.

Database error 4860

Database error 911 at OPC

> [Microsoft][SQL Server Native Client 10.0][SQL

> Server]Database 'mssqlsystemresource' does not exist. Make

> sure that the name is entered correctly.

Database error 911

We found this error messages on two independent ECC 6.0 systems which both run MS SQL Server since activating early watch reports. At this time data for the early watch report is collected, maybe this is the trigger for this error. But I think that the real cause for this error is located somewhere in the database configuration.

By the way there is no shortdump or any additional information in the EWA report.

Any ideas or hints? Thank you in advance.