Hi,
BC_BPEM_BL_ENTRY table contains business logs information.
Refer: 1894457 - Table BC_BPEM_BL_ENTRY is growing rapidly
You can archive logs once you have followed the above note.
Divyanshu
Hi,
BC_BPEM_BL_ENTRY table contains business logs information.
Refer: 1894457 - Table BC_BPEM_BL_ENTRY is growing rapidly
You can archive logs once you have followed the above note.
Divyanshu
here the local SLD means the portal system SLD ..?
Please clarify
Thanks in advance
BPEM_MAIL_BL_AT - I was not able to find any solid info on this table. However, it seems that this is a attachment table for emails related to business logs.
Hope, both information were helpful.
Divyanshu
Hi All,
I'm also facing same problem in Import ABAP Phase,
Error Message: " The migration key for a heterogeneous system copy is wrong. SOLUTION: Enter a valid migration key."
Source System: OS/400
DB: DB2 UDB for Iseries, 7.1
SAP: Solman 7.1
Target System: Linux 6
DB: DB2 LUM 10.1
SAP: Solman 7.1
Also I tried with “1G5fdEM50DwIrBzjt6TE5Pae ” (valid until 31/DEC/14) Key which is available in 1768158 (1768158 - System Copy of Systems Based on SAP NW 7.0 / 7.0 EHP 1-3) SAP note, but no luck.
Regards,
Vino
Yes, you are all right, just analyze the question from diffirent point.
Thanks for all your guys.
B.R
Michael
Thanks very much for your great reply.
Just ensure enough storage space is available. During restoration no need to extend any tablespace.
----Do I need create a new file system '/oracle/SID/sapdata<NO.> and assign the storage space to it first ?
Best Regards,
Michael
Hi everyone
I just applied SPS 12 + Kernel 721 to SAP 7.31 instance. Since then, DB13 jobs are failing with the following error:
SXPG_COMMAND_EXECUTE failed for BRCONNECT - Reason: program_start_error: For More Information, See SYS
Job cancelled after system exception ERROR_MESSAGE
The same issue happened on 2 other instances afeter the upgrade. Did anoyone had a similar issue before?
Here's our architecture:
* SAP running on AIX with DB + app server
* No gateway installed, but I configured SAPXPG_DBDEST_HOSTNAME. This RFC used to work fine before the kernel upgrade (not sure if related or not)
* RFC test give the following error:
Logon Connection Error
Error Details Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=27 thRc=2
Error Details ERROR: timeout during allocate
Error Details LOCATION: SAP-Gateway on host app_hostname / sapgwxx
Error Details DETAIL: no connect of TP sapxpg from host db_hostname after 20 sec
Error Details COMPONENT: SAP-Gateway
Error Details COUNTER: 1960
Error Details MODULE: gwr3cpic.c
Error Details LINE: 2164
Error Details RETURN CODE: 242
Error Details SUBRC: 0
Error Details RELEASE: 721
Error Details TIME: Tue Aug 5 11:54:16 2014
Error Details VERSION: 2
dev_rfc
=========
**** Trace file opened at 20140805 115416 EDT, by disp+work
**** Versions SAP-REL 721,0,300 RFC-VER U 3 1498751 MT-SL
======> CPIC-CALL: 'ThSAPOCMINIT' : cmRc=27 thRc=242
Timeout during connection setup. Please check partner availability
ABAP Programm: RSRFCPIN (Transaction: SM59)
User: USER (Client: NNN)
Destination: SAPXPG_DBDEST_DBHOST (Handle: 2, DtConId: 53DD532F2B422090E10080000A441E26, DtConCnt: 0, ConvId: ,)
EPP RootContextId: 53DFCD839FB72120E10080000A441E26, ConnectionId: 00000000000000000000000000000000, ConnectionCnt: 0
EPP TransactionId: 53DD532C2B422090E10080000A441E26
Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1730
CPIC-CALL: 'ThSAPOCMINIT' : cmRc=27 thRc=242
Timeout during connection setup. Please check partner availability
DEST =SAPXPG_DBDEST_DBHOST
HOST =xxx.xxx.xxx.xxx
PROG =sapxpg
dev_wxx
========
M Tue Aug 5 11:54:16 2014
M
M *****************************************************************************
M *
M * LOCATION SAP-Gateway on host app_hostname / sapgwxx
M * ERROR timeout during allocate
M *
M * TIME Tue Aug 5 11:54:16 2014
M * RELEASE 721
M * COMPONENT SAP-Gateway
M * VERSION 2
M * RC 242
M * MODULE gwr3cpic.c
M * LINE 2164
M * DETAIL no connect of TP sapxpg from host db_hostname after 20 sec
M * COUNTER 1960
M *
M *****************************************************************************
M
A RFC 1714 CONVID 89470994
A * CMRC=27 DATA=0 STATUS=0 SAPRC=242 ThSAPOCMINIT
A RFC> ABAP Programm: RSRFCPIN (Transaction: SM59)
A RFC> User: USER (Client: NNN)
A RFC> Destination: SAPXPG_DBDEST_DBHOST (handle: 2, DtConId: 53DD532F2B422090E10080000A441E26, DtConCnt: 0, ConvId: ,)
A *** ERROR => RFC ======> CPIC-CALL: 'ThSAPOCMINIT' : cmRc=27 thRc=242
Timeout during connection setup. Please check partner availability
[abrfcio.c 9199]
A {root-id=53DFCD839FB72120E10080000A441E26}_{conn-id=00000000000000000000000000000000}_0
A *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1730
CPIC-CALL: 'ThSAPOCMINIT' : cmRc=27 thRc=242
Timeout during connection setup. Please check partner availability
DEST =SAPXPG_DBDEST_DBHOST
HOST =xxx.xxx.xxx.xxx
PROG =sapxpg
[abrfcio.c 9199]
A {root-id=53DFCD839FB72120E10080000A441E26}_{conn-id=00000000000000000000000000000000}_0
A TH VERBOSE LEVEL FULL
A ** RABAX: end RX_GET_MESSAGE
Divyanshu
Thank for your reply. I went through these messages before and non of them helped. I am ussing ssh in our environment and it is configured properly for <sdi>adm to login without password. Also, as I mentioned, it was working fine just before the upgrade. In fact, the instances that are not upgraded yet are also working fine.
As per .rhosts, I cannot use that in our environment.
Can you go to your kernel directory and search for this file sapxpg.
Compare this with your old kernel. And if not working, replace this in new kernel with old one.
Also set, gw/acl_mode = 0 in instance profile.
Share dev_cp and dev_rfc logs.
BTW.... Refer: 980266 - RFC destination SAPXPG_DBDEST_<DB-HOST> does not work and troubleshoot
Yep, gateway ACL is set to 0.
I also went through the following oss notes, but still did not help:
980266
446172
583759
1914589
Thanks
Hi Nader,
Please share job failure logs.
Also, did you check the kernel as asked and permissions for the new files ?
Replace old sapxpg for the meanwhile from old kernel so that we can find the actual cause of this issue.
Divyanshu
Here's the log
Job started
Step 001 started (program RSDBAJOB, variant &0000000000090, user ID BASIS)
Execute logical command BRCONNECT On host axddasappia
Parameters: -jid CHECK20140805105434 -u / -c -f check
SXPG_STEP_XPG_START: is_local_host: rc = 403
SXPG_STEP_XPG_START: host = axddasappia
SXPG_STEP_XPG_START: is_local_r3_host: rc = 802
SXPG_STEP_XPG_START: RFC_TCPIP_CONNECTION_OPEN: rc = 1003
SXPG_STEP_COMMAND_START: SXPG_STEP_XPG_START returned: 1.003
SXPG_COMMAND_EXECUTE(LONG)
<timestamp> = 20140805105503
COMMANDNAME = BRCONNECT
ADDITIONAL_PARAMETERS = -jid CHECK20140805105434 -u / -c -f check
LONG_PARAMS
OPERATINGSYSTEM = ANYOS
TARGETSYSTEM = axddasappia
DESTINATION
SY-SUBRC = 1003
SXPG_COMMAND_EXECUTE failed for BRCONNECT - Reason: program_start_error: For More Information, See SYS
Job cancelled after system exception ERROR_MESSAGE
I checked the permission and they are fine.
I replaced sapxpg with the old one and it works now. Thanks for the assistance.
Good that is working with old.
Please upload dev_rd, cp and rfc logs for new sapxpg.
If you'd be more clear on how to "refresh from the SLD", I'd appreciate it.
Because simply pushing some button in RZ70 doesn't seem to do *anything*.
The SolMan recognizes all else about the system, the rigtht number of clients, MaxDB version and so on.
So why all these problems about the installed Software Components?
In LMDB, under technical system you selected, there is an option to resync from SLD in one of the tabs on the right part of screen.
Or checl this - https://help.sap.com/saphelp_sm71_sp05/helpdata/en/f6/a41e0402664451b9c4640ff4513527/content.htm
Sorru, but that note doesn't tell me *anything* at all.
As usual with SAP, it talks a lot of gibberish w/o mentioning any clear cut instructions at all.
I need something like transaction code this, entry field that, value input so and that's that.
All else just gets me back to guess works.
I used to know this shey1t, but by now its just too late.
I don't even see any such thing like "Product Instance" (and I forgot why SAP just won't use "normal language" in these things anyway, lest they want you to have to go to one of their costly seminars to understand what-the-heck a "Product Instance" is anyway, compare to a "Product System", compared to a "Technical System").
So I forgot this late at night, and I can't find any tab labeled "Product Instance" or any tree node with that name anyway.
Lost in this @#$! and getting very frustrated here.
This used to work just fine in the old SM with SMSY, now with the LMDB everyone is supposed to start from scratch again?!!