Dear all,

             I am facing on problem while doing th  Backup volume initialization from DB13 on the error log is mentioned below:

BR0051I BRBACKUP 7.00 (24)

BR0055I Start of database backup: bdywwgym.tib 2008-09-25 17.49.48

BR0484I BRBACKUP log file: /oracle/RD1/DEV/sapbackup/bdywwgym.tib

BR0101I Parameters

Name                           Value

oracle_sid                     DEV

oracle_home                    /oracle/RD1/DEV/102_64

oracle_profile                 /oracle/RD1/DEV/102_64/dbs/initDEV.ora

sapdata_home                   /oracle/RD1/DEV

sap_profile                    /oracle/RD1/DEV/102_64/dbs/initDEV.sap

backup_dev_type                tape

tape_copy_cmd                  cpio

cpio_flags                     -ovB

cpio_in_flags                  -iuvB

dd_flags                       obs=64k bs=64k

dd_in_flags                    ibs=64k bs=64k

rewind                         mt -f $ rew

rewind_offline                 mt -f $ offl

tape_address                   /dev/rmt/0mn

tape_address_rew               /dev/rmt/0m

volume_backup                  SCRATCH

expir_period                   30

tape_use_count                 100

exec_parallel                  0

system_info                    devadm/oradev rlsdev HP-UX B.11.31 U ia64

make_info                      hpia64 OCI_102 Apr 21 2007

command_line                   brbackup -u / -jid TAPIN20080925174944 -i force -c force -n 1 -v SCRATCH

BR0477I Oracle pfile /oracle/RD1/DEV/102_64/dbs/initDEV.ora created from spfile /oracle/RD1/DEV/102_64/

BR0205I Backup volume initialization

BR0058I BRBACKUP action ID: bdywwgym

BR0059I BRBACKUP function ID: tib

BR0102I Following backup device will be used: /dev/rmt/0mn

BR0131I All volumes get the name SCRATCH

BR0129I Force option set - no label checking during initialization

BR0134I Unattended mode with 'force' active - no operator confirmation allowed

BR0207I Volume in device: /dev/rmt/0mn will be initialized with name: SCRATCH

BR0280I BRBACKUP time stamp: 2008-09-25 17.49.49

BR0226I Rewinding tape volume in device /dev/rmt/0m ...

BR0278E Command output of 'LANG=C mt -f /dev/rmt/0m rew':

/dev/rmt/0m: No such device or address

BR0280I BRBACKUP time stamp: 2008-09-25 17.49.49

BR0279E Return code from 'LANG=C mt -f /dev/rmt/0m rew': 1

BR0213E Winding tape volume in device /dev/rmt/0mn failed

BR0219E Initialization of volume SCRATCH in device /dev/rmt/0mn failed

BR0206I End of backup volume initialization

BR0280I BRBACKUP time stamp: 2008-09-25 17.49.49

BR0054I BRBACKUP terminated with errors

Kindly help.

I am installing ECC 6.0 SR1 EHP4 Ready in AIX 6.1 db2 9.1.7.

Got following error in step 27 (IMPORT ABAP)

ARNING    2011-03-03 16:42:02.173

           CJSlibModule::writeWarning_impl()

Execution of the command "/usr/sap/WD1/SYS/exe/run/R3load -testconnect" finished with return code 2. Output:

sapparam: sapargv( argc, argv) has not been called.

sapparam(1c): No Profile used.

sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

/usr/sap/WD1/SYS/exe/run/R3load: START OF LOG: 20110303164202

/usr/sap/WD1/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#5 $ SAP

/usr/sap/WD1/SYS/exe/run/R3load: version R7.01/V1.4 [UNICODE]

Compiled Feb 24 2009 21:54:08

/usr/sap/WD1/SYS/exe/run/R3load -testconnect

DbSl Trace: DbSlConnect to 'WD1' as 'sapwd1' failed

(DB) ERROR: db_connect rc = 256

DbSl Trace: DbSlConnect to 'WD1' as 'sapwd1' failed

(DB) ERROR: DbSlErrorMsg rc = 29

/usr/sap/WD1/SYS/exe/run/R3load: job finished with 1 error(s)

/usr/sap/WD1/SYS/exe/run/R3load: END OF LOG: 20110303164202

WARNING[E] 2011-03-03 16:42:02.176

           CJSlibModule::writeError_impl()

Thanks

Amit Barnawal

Hi,

We had our Production System went down suddenly. When I analyzed the log details. I found the following. I went manually using SIDADM and started the SAP. Now it is working. But i would like to know what had caused the sudden interruption. Can someone help us?

Mon Mar  1 04:01:17 2010

***LOG Q0E=> SigIGenAction, signal ( 33) [sigux.c      1067]

DpHalt: shutdown server >DBSERVER_UP1_00                         < (normal)

DpModState: change server state from ACTIVE to SHUTDOWN

Stop work processes

Mon Mar  1 04:01:20 2010

Stop gateway

• ERROR => DpProcKill: kill failed (3: No such process) [dpuxdisp.c   404]

Stop icman

Terminate gui connections

wait for end of work processes

waiting for termination of work processes ...

Mon Mar  1 04:01:23 2010

waiting for termination of work processes ...

Mon Mar  1 04:01:24 2010

Mon Mar  1 04:01:27 2010

waiting for termination of work processes ...

Mon Mar  1 04:01:28 2010

waiting for termination of work processes ...

DpStartStopMsg: send stop message (myname is >DBSERVER_UP1_00

      <)

***LOG Q0I=> NiIWrite: writev (32: Broken pipe) [nixxi.cpp 3948]

• ERROR => NiIWrite: SiSendV failed for hdl 3 / sock 12

    (SI_ECONN_BROKEN/32; UD; ST; 192.168.102.244:3900) [nixxi.cpp    3948]

• ERROR => MsINiWrite: NiBufSend (rc=NIECONN_BROKEN) [msxxi.c      2480]

• ERROR => MsISnd2: MsINiWrite (rc=NIECONN_BROKEN) [msxxi.c      1438]

MBUF state OFF

MBUF component DOWN

• ERROR => DpStartStopMsg: MsSnd2Type failed (rc=-100) [dpxxdisp.c   14285]

• ERROR => MsIReceive: not_attached [msxxi.c      1201]

• ERROR => MsISnd2: not_attached [msxxi.c      1321]

• ERROR => DpHalt: MsSendKeepalive failed (-3) [dpxxdisp.c   10943]

detach from message server

cleanup EM

cleanup event management

cleanup shared memory/semaphores

Mon Mar  1 04:01:59 2010

removing request queue

***LOG Q05=> DpHalt, DPStop ( 618560) [dpxxdisp.c   11257]

• shutdown completed - server stopped ***

=> Stack Trace:

        DpHalt() at 0x101300f34

        SigIGenAction() at 0x1000c1f04

        Unknown at 0x44a4

!!! Invalid stack address encountered: 0x0

!!! Stack corrupted.

Hi,

I am below dump. Kindly do the needful.

Runtime Errors         CONVT_NO_NUMBER

Exception              CX_SY_CONVERSION_NO_NUMBER

Date and Time          28.09.2009 18:15:50

Short text                                                                               

Unable to interpret 0 as a number.                                                           

What happened?                                                                               

Error in the ABAP Application Program                                                                               

The current ABAP program "RSDSPROC" 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_CONVERSION_NO_NUMBER', was not              

     caught in                                                                               

procedure "AL_PRC_REPORT_VALUES" "(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:                                                             

    The program attempted to interpret the value 0 as a number, but                              

    since the value contravenes the rules for correct number formats,                            

    this was not possible.                                                                       

How to correct the error                                                                         

    Whole numbers are represented in ABAP as a sequence of numbers, possibly                     

     with an algebraic sign.                                                                     

    The following are the possibilities for the representation of floating                       

    point numbers:                                                                               

[algebraic sign][mantissa]E[algebraic sign][exponent]                                      

      [algebraic sign][whole number part].[fraction part]                                        

    For example, 12E+34, +12E34, 12E34, 12.34                                                  

    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 nonmodified 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:                                                                               

"CONVT_NO_NUMBER" "CX_SY_CONVERSION_NO_NUMBER"                                               

    "RSDSPROC" or "RSDSPROC"                                                                     

    "AL_PRC_REPORT_VALUES"                                                                               

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                          

    program: The source code of the program                                                      

       In the editor, choose "Utilities>More                                                    

    Utilities>Upload/Download>Download".                                                                               

4. Details about the conditions under which the error occurred or which                      

    actions and input led to the error.                                                                               

The exception must either be prevented, caught within proedure                               

    "AL_PRC_REPORT_VALUES" "(FORM)", or its possible occurrence must be declared in              

     the                                                                               

RAISING clause of the procedure.                                                             

    To prevent the exception, note the following:                                                

System environment                                                                               

SAPRelease 700                                                                               

Application server... "sapbwpapp"                                                            

    Network address...... "10.10.88.40"                                                          

    Operating system..... "AIX"                                                                  

    Release.............. "5.3"                                                                  

    Hardware type........ "00CF4CEC4C00"                                                         

    Character length.... 16 Bits                                                                 

    Pointer length....... 64 Bits                                                                

    Work process number.. 0                                                                      

    Shortdump setting.... "full"                                                                               

Database server... "sapbwpdb"                                                                

    Database type..... "ORACLE"                                                                  

    Database name..... "KBP"                                                                     

    Database user ID.. "SAPSR3"                                                                               

Terminal................. " "                                                                               

Char.set.... "C"                                                                               

SAP kernel....... 700                                                                        

    created (date)... "Jan 23 2008 21:25:00"                                                     

    create on........ "AIX 2 5 005DD9CD4C00"                                                     

    Database version. "OCI_102 (10.2.0.2.0) "                                                                               

Patch level. 144                                                                               

Patch text.. " "                                                                               

Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."               

    SAP database version. 700                                                                    

    Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"                                                                               

Memory consumption                                                                               

Roll.... 16192                                                                               

EM...... 12569544                                                                               

Heap.... 0                                                                               

Page.... 16384                                                                               

MM Used. 1287792                                                                               

MM Free. 2899456                                                                               

User and Transaction                                                                               

Client.............. 000                                                                     

    User................ "SAPSYS"                                                                

    Language key........ "E"                                                                     

    Transaction......... " "                                                                     

    Transactions ID..... "4AC099D78D84004BE10080000A0A5828"                                                                               

Program............. "RSDSPROC"                                                              

    Screen.............. "SAPMSSY0 1000"                                                         

    Screen line......... 6

Hallow, Please help me to solve the below issue in my BI server.

SM21 Log file.

Error 22 for write/read access to a file. File = \\SABIP\sapmnt\BIP\SYS\global\600JOBLG\0001X19003106X46756

Failed to create log for job BI_PROCESS_TRIGGER 19003106/

There is no change happen in OS level. Also I check permission on the server for that particular user.

This error continues appier. I try to check the job. BI_WRITE_PROT_TO_APPLLOG.

I am very new in Basis site.

Abdul Majeed.

Hi all,

I am using standard Export / Import method for client copy from PRD to QAS after long time it got terminated & showed the following error lines.

Start import R3TRTABUBSEG ...

twrtab reached memory limit; memory usage 2000000000

6837413 entries from BSEG (240%) deleted.

324400 39606713814

324400 39607038214

324400 39607362614

324400 39607687014

324400 39608011414

324400 39608335814

324400 39608660214

324400 39608984614

324400 39609309014

324400 39609633414

324400 39609957814

324400 39610282214

324400 39610606614

324400 39610931014

324400 39611255414

324400 39611579814

Unexpected EOF after 2378415224 bytes

Please contact the SAP support.

Main import

End date and time : 20090407061610

Ended with return code:  ===> 16 <===

######################################

I have got the following note  Note 103562 - R3trans: 'twrtab memory limit reached' then term.

any clues what needs to be done to overcome this issue.

Regards,

Rahul

I'm currently locked out of the system due to 6 failed logins. Does the system unlocks itself after certain time? Is there a way to reset the account? I'll like to keep the same password if possible. Thanks

Hi,

We have SAP ECC 6.0 on Solaris Sparc server. Our database is Oracle 10.2.0.2. We will buy 2 new solaris server and we want to use these server as cluster. We want to make homogeneous system copy from current server to new cluster server. How can we make homogeneous copy from current server to new cluster server? Firts of all do we have to install new ECC 6.0 on cluster server and then will we make homogeneous system copy?

Also how can we install ECC 6.0 on Solaris Cluster server? Will we have install ECC 6.0 seperatly for each server of cluster unit? I have SAP installation document but it is not clear. Do you have another document for SAP installation on cluster server? Please help us about these issues.

Best regards.

Hie Experts,

when we type tcode sost, all the mails are showing in waiting, we select that mails and try to resend it through, it shows this message

"A send process is already running for INT/prio

High"

Please do help us, to reslove this issue...

Regards,

Jayesh

Dear Team,

When we change Internal Table in XML file ,Then all space are reduce with one Space.

Whats the reason.I want same as it is.

Regards

Dear Expert Team,

We want to implement Support Pack via SUM ,I have never implement via SUM.

I always done via  SPAM only .We are using HP Ux 11.31 with Oracle 11g and SAP ECC6.0 with Ehp7

So please help me . How I can implement via SUM ,

Currently our Support pack Level as give below and  Kernel release  742.

Thanks & Regards

Dear all :

after the SAP Applicaton was reboot on Aug-12th , my backup is not working since then .

Env: TSM： Version 5, Release 4, Level 1.6 ; AIX:  5300-08-04-0844

.

at first the backup errorlog as following:

BR0051I BRBACKUP 7.00 (32)

BR0055I Start of database backup: betwigxw.fnf 2016-08-19 20.00.04

BR0484I BRBACKUP log file: /oracle/BP1/sapbackup/betwigxw.fnf

BR0477I Oracle pfile /oracle/BP1/102_64/dbs/initBP1.ora created from spfile /oracle/BP1/102_64/dbs/spfileBP1.ora

BR0328E Database file /oracle/BP1/sapdata1/system_1/system.data1 of tablespace SYSTEM is already in backup status

BR0328E Database file /oracle/BP1/sapdata1/undo_1/undo.data1 of tablespace PSAPUNDO is already in backup status

....

so the sap admin "alter the database backup end " then we re-try the backup :

but this time , the error log as following :

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

BKI2017I: Blocksize is set to 131072 bytes

BKI5016I: Time: 08/20/16 11:19:12 New TSM session created: MGMNT-CLASS: SAP, TSM-Server: 10.18.8.19:SERVER_SAP, type: SIMPLE

BKI0027I: Time: 08/20/16 11:19:12 Object: 1 of 5000 in process: /oracle/BP1/oraarch/BP1arch1_1056727_673668081.dbf Size: 44.452 MB,

MGMNT-CLASS: SAP, TSM-Server: 10.18.8.19:SERVER_SAP .

BKI5008E: Tivoli Storage Manager Error:

ANS1235E (RC-72)  An unknown system error has occurred from which TSM cannot recover.

--

BKI1208W: The object '/oracle/BP1/oraarch/BP1arch1_1056727_673668081.dbf' will be retried [2].

BKI0027I: Time: 08/21/16 02:20:12 Object: 1 of 5000 in process: /oracle/BP1/oraarch/BP1arch1_1056727_673668081.dbf Size: 44.452 MB,

MGMNT-CLASS: SAP, TSM-Server: 10.18.8.19:SERVER_SAP .

BKI5008E: Tivoli Storage Manager Error:

ANS1235E (RC-72)  An unknown system error has occurred from which TSM cannot recover.

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

on the tsm server:

q actlog begindate=08/20/2016 begintime=11:00

q actlog begindate=08/20/2016 begintime=11:00 

There is nothing actlog for my session .

......

There is another SAP applicatoin use the same TSM-Server whose backup is running normal , so I'm not sure what is the "Tivoli Storage Manager Error"

kindly help .