BPE Issue?

Hi,
gurus,
I have gone through BTE Basics while doing scenario i have created Z FM for BTE- '00001120' and assigned to a customer while creating a document in FB01 i am getting error: 'Posting is only possible with a zero balance; correct document' i don't know how to over come it please suggest me on that.
Or else Please forward me any BTE scenarios link or documents or sceanrios.
Thank u,
shabeer ahmed.

thank u

Similar Messages

CcBPM - BPE_ADAPTER : SYSTEM_FAILURE_INTERNAL

Hi gurus,
I am facing below errorn in ccBPM
<SAP:Code area="BPE_ADAPTER">SYSTEM_FAILURE_INTERNAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>An internal error has occurred</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I checke din sxi_cache and it shows return code - 0 , what could be the reason!!!

Try this :
The BPE Adapter error may be also because of Inactive version of BPM runtime
So as suggested check the SXI_CACHE again and make sure that Return value is 0.
Also do this: Go to Transaction SWWL and delete all the errored entries which belongs to your integration scenario
Then you can re-import the Integration Process into Directory so that it will be re-active.
Solution:
Step maintain prefix numbers allows you assign number ranges to your custom workflows on the ABAP side (BPMs)
This is a post install step - pretty easy... You can ask your basis person, or do it yourself --> click on the execute icon and enter a number range e.g. 99* will work.
As for your BPM - first step is check if the BPM was succesfully replicated to the ABAP side. SXI_CACHE, select the BPM and ensure RC is '0'.
If all this works, then thats a good start.
After that, check your queues, check SWI1 and check SWPR - for the possible errors with that BPM...
Of course check RWB for the initial message that should have kickstarted this scenario and look at the status.
check this links who has same error,their problem got rectified:
BPE Issue
BPM activation problem

ASR9001 module A9K-MPA-20X1GE issue

Hi all!
Who knows, what does these messages mean?
LC/0/0/CPU0:Oct 22 10:53:32.120 : envmon_lc[160]: %PLATFORM-ENVMON-4-OPERATION_WARN : Unable to get plug sensor data, error code 'Subsystem(2890)' detected the 'fatal' condition 'Code(0)'
RP/0/RSP0/CPU0:Oct 22 10:53:32.860 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:ADMIN DOWN
LC/0/0/CPU0:Oct 22 10:53:32.862 : lda_server[65]: %PLATFORM-LDA-3-MPA_BAY_SW_ERROR : Unable to initialize MPA in bay: 0, Module has been shutdown due to identify test failure (0x00000000 - No error) : pkg/bin/lda_server : (PID=40990) : -Traceback= 4ed5159c 4bf1eed0 4bf1efdc 4d02c28c 4d02a1f4 4ba73a44 4ba71554 4d029ddc 4bada400
RP/0/RSP0/CPU0:Oct 22 10:53:33.860 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/0, state: UNPOWERED
Is this hardware or software issue? What do you think?
I think we have faced with hardware issue of module A9K-MPA-20X1GE.
More outputs:
RP/0/RSP0/CPU0:asr9001#sh ver
Tue Oct 22 10:53:46.186 UTC
Cisco IOS XR Software, Version 4.3.2[Default]
Copyright (c) 2013 by Cisco Systems, Inc.
ROM: System Bootstrap, Version 2.01(20130627:172232) [ASR9K ROMMON],
asr9001 uptime is 6 minutes
System image file is "bootflash:disk0/asr9k-os-mbi-4.3.2/0x100000/mbiasr9k-rp.vm"
cisco ASR9K Series (P4040) processor with 8388608K bytes of memory.
P4040 processor at 1500MHz, Revision 2.0
ASR-9001 Chassis
2 Management Ethernet
4 TenGigE
4 DWDM controller(s)
4 WANPHY controller(s)
219k bytes of non-volatile configuration memory.
2880M bytes of hard disk.
3932144k bytes of disk0: (Sector size 512 bytes).
Configuration register on node 0/RSP0/CPU0 is 0x102
Boot device on node 0/RSP0/CPU0 is disk0:
Package active on node 0/RSP0/CPU0:
iosxr-infra, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-infra-4.3.2
    Built on Sun Sep 1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-fwding, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-fwding-4.3.2
    Built on Sun Sep 1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-routing, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-routing-4.3.2
    Built on Sun Sep 1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-diags, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-diags-4.3.2
    Built on Sun Sep 1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-ce, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-ce-4.3.2
    Built on Sun Sep 1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-os-mbi, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-os-mbi-4.3.2
    Built on Sun Sep 1 19:23:39 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-base, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-base-4.3.2
    Built on Sun Sep 1 19:21:14 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-fwding, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-fwding-4.3.2
    Built on Sun Sep 1 19:21:14 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-diags-supp, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-diags-supp-4.3.2
    Built on Sun Sep 1 19:21:19 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-scfclient, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-scfclient-4.3.2
    Built on Sun Sep 1 19:21:22 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-cpp, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-cpp-4.3.2
    Built on Sun Sep 1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-ce, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-ce-4.3.2
    Built on Sun Sep 1 19:21:16 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-mini-px, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-mini-px-4.3.2
    Built on Sun Sep 1 19:27:30 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-mgbl, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-mgbl-4.3.2
    Built on Sun Sep 1 19:28:25 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-mgbl-supp, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-mgbl-supp-4.3.2
    Built on Sun Sep 1 19:28:25 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-mgbl-px, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-mgbl-px-4.3.2
    Built on Sun Sep 1 19:28:37 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-fpd, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-fpd-4.3.2
    Built on Sun Sep 1 19:29:15 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-fpd-px, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-fpd-px-4.3.2
    Built on Sun Sep 1 19:29:40 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9K-doc-supp, V 4.3.2[Default], Cisco Systems, at disk0:asr9K-doc-supp-4.3.2
    Built on Sun Sep 1 19:29:07 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-doc-px, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-doc-px-4.3.2
    Built on Sun Sep 1 19:29:14 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
Boot device on node 0/0/CPU0 is mem:
Package active on node 0/0/CPU0:
iosxr-infra, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-infra-4.3.2
    Built on Sun Sep 1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-fwding, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-fwding-4.3.2
    Built on Sun Sep 1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-routing, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-routing-4.3.2
    Built on Sun Sep 1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-diags, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-diags-4.3.2
    Built on Sun Sep 1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
iosxr-ce, V 4.3.2[Default], Cisco Systems, at disk0:iosxr-ce-4.3.2
    Built on Sun Sep 1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-os-mbi, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-os-mbi-4.3.2
    Built on Sun Sep 1 19:23:39 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-base, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-base-4.3.2
    Built on Sun Sep 1 19:21:14 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-fwding, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-fwding-4.3.2
    Built on Sun Sep 1 19:21:14 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-diags-supp, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-diags-supp-4.3.2
    Built on Sun Sep 1 19:21:19 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-scfclient, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-scfclient-4.3.2
    Built on Sun Sep 1 19:21:22 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-cpp, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-cpp-4.3.2
    Built on Sun Sep 1 19:21:10 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-ce, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-ce-4.3.2
    Built on Sun Sep 1 19:21:16 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
asr9k-mini-px, V 4.3.2[Default], Cisco Systems, at disk0:asr9k-mini-px-4.3.2
    Built on Sun Sep 1 19:27:30 UTC 2013
    By iox-bld2 in /auto/srcarchive7/production/4.3.2/all/workspace for pie
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#sh log
Tue Oct 22 10:54:22.823 UTC
Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
    Console logging: level warnings, 44 messages logged
    Monitor logging: level debugging, 0 messages logged
    Trap logging: level informational, 0 messages logged
    Buffer logging: level debugging, 148 messages logged
Log Buffer (307200 bytes):
RP/0/RSP0/CPU0:Oct 22 10:47:29.090 : init[65540]: %OS-INIT-7-MBI_STARTED : total time 8.814 seconds
RP/0/RSP0/CPU0:Oct 22 10:47:29.113 : imio[64]: %PLATFORM-IMIO-3-OPERATION_NOTIFY : imio_main: cold start
RP/0/RSP0/CPU0:Oct 22 10:48:42.672 : sysmgr[96]: %OS-SYSMGR-5-NOTICE : Card is COLD started
RP/0/RSP0/CPU0:Oct 22 10:48:50.075 : init[65540]: %OS-INIT-7-INSTALL_READY : total time 89.801 seconds
RP/0/RSP0/CPU0:Oct 22 10:48:51.803 : sysmgr[407]: %OS-SYSMGR-6-INFO : Backup system manager is ready
RP/0/RSP0/CPU0:Oct 22 10:48:52.088 : sc_reddrv[376]: imio_lance2_init_interrupts:
RP/0/RSP0/CPU0:Oct 22 10:48:58.262 : sysmgr[96]: %OS-SYSMGR-7-DEBUG : node set to DSC
RP/0/RSP0/CPU0:Oct 22 10:49:04.763 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-SYSTEM_COLD_START : System cold start detected. Resetting Line Cards.
RP/0/RSP0/CPU0:Oct 22 10:49:06.487 : pwr_mgmt[360]: %PLATFORM-PWR_MGMT-2-MODULE_FAILURE : Power-module 0/PM1/SP failure condition raised : Module input voltage out of range
RP/0/RSP0/CPU0:Oct 22 10:49:07.565 : online_diag_rsp[427]: %DIAG-DIAG-6-RUN_MINIMUM : ASR9001-RP 0/RSP0/CPU0: Running Minimum Diagnostics...
RP/0/RSP0/CPU0:Oct 22 10:49:09.369 : envmon[204]: %PLATFORM-ENVMON-4-FANTRAY_RPM : Fan tray RPM warning on slot 0/FT0/SP
RP/0/RSP0/CPU0:Oct 22 10:49:12.761 : bpe[144]: %PLATFORM-BPE-5-INFO : successfully retrieved i2c eeprom
RP/0/RSP0/CPU0:Oct 22 10:49:12.969 : shelfmgr[381]: %PLATFORM-SHELFMGR_HAL-7-CAN_INFO : Can API: slot 0 online event.
RP/0/RSP0/CPU0:Oct 22 10:49:12.991 : shelfmgr[381]: %PLATFORM-SHELFMGR_HAL-3-POWER_SUPPLY_REDUNDANCY : Power Supply Failures are not protected.
RP/0/RSP0/CPU0:Oct 22 10:49:13.624 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/FT0/SP inserted
RP/0/RSP0/CPU0:Oct 22 10:49:13.780 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/PM0/SP inserted
RP/0/RSP0/CPU0:Oct 22 10:49:13.788 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/PM1/SP, state: FAILED
RP/0/RSP0/CPU0:Oct 22 10:49:13.789 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/PM1/SP inserted
RP/0/RSP0/CPU0:Oct 22 10:49:13.800 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/RSP0/CPU0, state: IOS XR RUN
RP/0/RSP0/CPU0:Oct 22 10:49:18.393 : envmon[204]: %PLATFORM-ENVMON-3-OPERATION_ERROR : Failed in envmon lwmconnect.message channel connection failed!,-1 error code 'Subsystem(8191)' detected the 'unknown' condition 'Code(63)': Unknown Error(511)
RP/0/RSP0/CPU0:Oct 22 10:49:19.395 : envmon[204]: %PLATFORM-ENVMON-3-OPERATION_FAIL : Failed in envmon_fantray_alarms.7076, error code 'Subsystem(8191)' detected the 'unknown' condition 'Code(63)': Unknown Error(511)
RP/0/RSP0/CPU0:Oct 22 10:49:19.395 : envmon[204]: %PLATFORM-ENVMON-2-ENV_CONDITION : Outstanding environmental condition exists in the chassis
RP/0/RSP0/CPU0:Oct 22 10:49:19.815 : invmgr[250]: lance_client_init: Client already connected
RP/0/RSP0/CPU0:Oct 22 10:49:20.816 : invmgr[250]: lance_client_init: Client already connected
RP/0/RSP0/CPU0:Oct 22 10:49:21.817 : invmgr[250]: lance_client_init: Client already connected
RP/0/RSP0/CPU0:Oct 22 10:49:22.843 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/RSP0/CPU0 inserted
RP/0/RSP0/CPU0:Oct 22 10:49:27.313 : sysmgr[96]: %OS-SYSMGR-7-DEBUG : sysmgr_admin_plane_check:SYSMGR_PLANE_ADMIN Notification sent.
RP/0/RSP0/CPU0:Oct 22 10:49:32.838 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_DISCOVERY : Node State Discovery complete
RP/0/RSP0/CPU0:Oct 22 10:49:32.854 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/CPU0 ASR9001-LC state:PRESENT
RP/0/RSP0/CPU0:Oct 22 10:49:32.905 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/FT0/SP FAN TRAY state:PRESENT
RP/0/RSP0/CPU0:Oct 22 10:49:32.957 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/0/CPU0 inserted
RP/0/RSP0/CPU0:Oct 22 10:49:35.224 : syslog_dev[94]: hsbi_fpd_agent[240]: FPD ltrace_file_name => fpd-agent/hsbi_fpd_agent
RP/0/RSP0/CPU0:Oct 22 10:49:37.310 : alphadisplay[115]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : Alpha display on node 0/RSP0/CPU0 changed to IOXR in state default
RP/0/RSP0/CPU0:Oct 22 10:49:48.759 : syslog_dev[94]: netio[327]: > WARNING (BM) [/ws/akgoswam-bgl/hellhound/nto6.4-XR/cisco/lib/3rdparty/netcomm/NetCommSw/Peripherals/BM/bm.h:352 BmBpidGet]: No Ipc - can't validate bpid.^M
RP/0/RSP0/CPU0:Oct 22 10:50:02.721 : ipodwdm[275]: %L2-G709-6-INFO : /harddisk:/ipodwdm_log Already present
RP/0/RSP0/CPU0:Oct 22 10:50:03.698 : shelfmgr[381]: %PLATFORM-SHELFMGR_HAL-6-BOOT_REQ_RECEIVED : Boot Request from 0/0/CPU0, RomMon Version: 2.1
RP/0/RSP0/CPU0:Oct 22 10:50:04.481 : shelfmgr[381]: %PLATFORM-MBIMGR-7-IMAGE_VALIDATED : Remote location 0/0/CPU0: : MBI tftp:/disk0/asr9k-os-mbi-4.3.2/lc/mbiasr9k-lc.vm validated
RP/0/RSP0/CPU0:Oct 22 10:50:04.499 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/CPU0 ASR9001-LC state:MBI-BOOTING
RP/0/RSP0/CPU0:Oct 22 10:50:07.632 : alphadisplay[115]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : Alpha display on node 0/RSP0/CPU0 changed to ACTV in state default
RP/0/RSP0/CPU0:Oct 22 10:50:14.758 : canb-server[149]: %PLATFORM-CANB_SERVER-3-ALARM_CLEARED : Clear alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED
RP/0/RSP0/CPU0:Oct 22 10:50:14.764 : canb-server[149]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_GREEN_FAILED
RP/0/RSP0/CPU0:Oct 22 10:50:29.223 : placed[346]: LR-PLANE-READY DECLARATION
RP/0/RSP0/CPU0:Oct 22 10:50:31.360 : envmon[204]: %PLATFORM-ENVMON-4-FANTRAY_RPM_CLEAR : Fan tray RPM warning cleared on slot 0/FT0/SP
RP/0/RSP0/CPU0:Oct 22 10:50:33.247 : ifmgr[242]: %PKT_INFRA-LINK-5-CHANGED : Interface MgmtEth0/RSP0/CPU0/1, changed state to Administratively Down
RP/0/RSP0/CPU0:Oct 22 10:50:33.251 : ifmgr[242]: %PKT_INFRA-LINK-3-UPDOWN : Interface MgmtEth0/RSP0/CPU0/0, changed state to Down
RP/0/RSP0/CPU0:Oct 22 10:50:33.251 : ifmgr[242]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface MgmtEth0/RSP0/CPU0/0, changed state to Down
RP/0/RSP0/CPU0:Oct 22 10:50:33.257 : cfgmgr-rp[158]: %MGBL-CONFIG-6-OIR_RESTORE : Configuration for node '0/RSP0/0' has been restored.
RP/0/RSP0/CPU0:Oct 22 10:50:35.006 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/PM1/SP A9K-750W-AC state:PRESENT
RP/0/RSP0/CPU0:Oct 22 10:50:35.012 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/PM0/SP A9K-750W-AC state:PRESENT
RP/0/RSP0/CPU0:Oct 22 10:50:35.588 : ifmgr[242]: %PKT_INFRA-LINK-3-UPDOWN : Interface MgmtEth0/RSP0/CPU0/0, changed state to Up
RP/0/RSP0/CPU0:Oct 22 10:50:35.589 : ifmgr[242]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface MgmtEth0/RSP0/CPU0/0, changed state to Up
RP/0/RSP0/CPU0:Oct 22 10:51:15.756 : canb-server[149]: %PLATFORM-CANB_SERVER-3-ALARM_INDICATION : Raise alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_RED_FAILED
RP/0/RSP0/CPU0:Oct 22 10:51:15.756 : canb-server[149]: %PLATFORM-CANB_SERVER-3-ALARM_CLEARED : Clear alarm from CBC in slot 0/FT0/SP, alarm code CBC_ALRM_FT_LED_GREEN_FAILED
RP/0/RSP0/CPU0:Oct 22 10:51:23.316 : dsc[181]: %PLATFORM-DSC_CTRL-6-RACK_STATE : Rack 1 is now Down
RP/0/RSP0/CPU0:Oct 22 10:51:23.321 : gsp[239]: gsp_rack_down_handler: for node:0x1
RP/0/RSP0/CPU0:Oct 22 10:51:25.396 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/CPU0 ASR9001-LC state:MBI-RUNNING
LC/0/0/CPU0:10: init[65540]: %OS-INIT-7-MBI_STARTED : total time 5.152 seconds
LC/0/0/CPU0:Oct 22 10:51:57.119 : sysmgr[91]: %OS-SYSMGR-5-NOTICE : Card is COLD started
LC/0/0/CPU0:Oct 22 10:51:57.524 : init[65540]: %OS-INIT-7-INSTALL_READY : total time 38.219 seconds
LC/0/0/CPU0:Oct 22 10:51:58.119 : sysmgr[341]: %OS-SYSMGR-6-INFO : Backup system manager is ready
RP/0/RSP0/CPU0:Oct 22 10:52:11.473 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 UNKNOWN state:UNPOWERED
RP/0/RSP0/CPU0:Oct 22 10:52:11.896 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:POWER UP
LC/0/0/CPU0:Oct 22 10:52:12.716 : lda_server[65]: %L2-SPA-5-STATE_CHANGE : SPA in bay 0 type A9K-MPA-20X1GE Initing
RP/0/RSP0/CPU0:Oct 22 10:52:13.786 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:INITIALIZED
LC/0/0/CPU0:Oct 22 10:52:25.265 : prm_server_ty[295]: %PLATFORM-QOSHAL-6-QOS_MODE_CHANGE : Line-card QoS mode set to child-shaping-enabled.
LC/0/0/CPU0:Oct 22 10:52:25.273 : prm_server_ty[295]: %PLATFORM-QOSHAL-6-QOS_MODE_CHANGE : Line-card QoS mode set to lowburst-disabled.
LC/0/0/CPU0:Oct 22 10:52:25.402 : lda_server[65]: %PLATFORM-UPGRADE_FPD-4-DOWN_REV : fpga3 instance 0 is down-rev (V0.07), upgrade to (V0.08). Use the "upgrade hw-module fpd" CLI in admin mode.
LC/0/0/CPU0:Oct 22 10:52:25.632 : sysmgr[91]: %OS-SYSMGR-7-DEBUG : sysmgr_admin_plane_check:SYSMGR_PLANE_ADMIN Notification sent.
LC/0/0/CPU0:Oct 22 10:52:27.651 : syslog_dev[89]: hsbi_fpd_agent[198]: FPD ltrace_file_name => fpd-agent/hsbi_fpd_agent
RP/0/RSP0/CPU0:Oct 22 10:52:37.663 : exec[65727]: %MGBL-exec-3-LOGIN_AUTHEN : Login Authentication failed. Exiting...
RP/0/RSP0/CPU0:Oct 22 10:52:43.079 : exec[65727]: %SECURITY-login-6-AUTHEN_SUCCESS : Successfully authenticated user 'shopik' from 'console' on 'con0_RSP0_CPU0'
RP/0/RSP0/CPU0:Oct 22 10:52:46.558 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:OK
RP/0/RSP0/CPU0:Oct 22 10:52:46.578 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/0, state: OK
RP/0/RSP0/CPU0:Oct 22 10:52:46.583 : invmgr[250]: %PLATFORM-INV-6-OIRIN : OIR: Node 0/0/0 inserted
LC/0/0/CPU0:Oct 22 10:52:58.858 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/3, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:58.863 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/2, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:58.863 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/1, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:58.863 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/0/2/0, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.133 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/19, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.133 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/18, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.133 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/17, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.133 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/16, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.133 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/15, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/14, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/13, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/12, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/11, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/10, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/9, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/8, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/7, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.134 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/6, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/5, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/4, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/3, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/2, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/1, changed state to Administratively Down
LC/0/0/CPU0:Oct 22 10:52:59.135 : ifmgr[200]: %PKT_INFRA-LINK-5-CHANGED : Interface GigabitEthernet0/0/0/0, changed state to Administratively Down
RP/0/RSP0/CPU0:Oct 22 10:53:00.041 : upgrade_fpd_cli[65763]: %PLATFORM-UPGRADE_FPD-6-STATUS : FPD upgrade started.
LC/0/0/CPU0:Oct 22 10:53:01.800 : lda_server[65]: %PLATFORM-SCC-2-BAD_ID_HW : Failed Identification Test in 0/130/0 [5/0] The module in 0/130/0 in this router may not be a genuineCisco product. Cisco warranties and support programs onlyapply to genuine Cisco products. If Cisco determines thatyour insertion of non-Cisco SPA cards or other modules into aCisco product is the cause of a support issue, Cisco maydeny support under your warranty or under a Cisco supportprogram such as SmartNet.
RP/0/RSP0/CPU0:Oct 22 10:53:09.746 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/CPU0 ASR9001-LC state:IOS XR RUN
RP/0/RSP0/CPU0:Oct 22 10:53:09.755 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/CPU0, state: IOS XR RUN
LC/0/0/CPU0:Oct 22 10:53:31.822 : lda_server[65]: %PLATFORM-LDA-4-MPA_OIR_QUICK_BACK_TO_BACK_ERROR : OIR operation was performed on MPA in bay:0 while the system is initializing. Recommend waiting for two minutes after EP initialized.
LC/0/0/CPU0:Oct 22 10:53:31.988 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/19, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.988 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/19, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/18, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/18, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/17, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/17, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/16, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/16, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/15, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/15, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/14, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/14, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/13, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/13, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/12, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/11, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.989 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/12, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/11, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/10, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/10, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/9, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.990 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/9, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/8, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/8, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/7, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/7, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/6, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/5, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/5, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/4, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/4, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/6, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/3, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/3, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/2, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.991 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/2, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.992 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/1, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.992 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/1, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.992 : ifmgr[200]: %PKT_INFRA-LINK-3-UPDOWN : Interface GigabitEthernet0/0/0/0, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:31.992 : ifmgr[200]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line protocol on Interface GigabitEthernet0/0/0/0, changed state to Down
LC/0/0/CPU0:Oct 22 10:53:32.120 : envmon_lc[160]: %PLATFORM-ENVMON-4-OPERATION_WARN : Unable to get plug sensor data, error code 'Subsystem(2890)' detected the 'fatal' condition 'Code(0)'
RP/0/RSP0/CPU0:Oct 22 10:53:32.860 : shelfmgr[381]: %PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/0/0 A9K-MPA-20X1GE state:ADMIN DOWN
LC/0/0/CPU0:Oct 22 10:53:32.862 : lda_server[65]: %PLATFORM-LDA-3-MPA_BAY_SW_ERROR : Unable to initialize MPA in bay: 0, Module has been shutdown due to identify test failure (0x00000000 - No error) : pkg/bin/lda_server : (PID=40990) : -Traceback= 4ed5159c 4bf1eed0 4bf1efdc 4d02c28c 4d02a1f4 4ba73a44 4ba71554 4d029ddc 4bada400
RP/0/RSP0/CPU0:Oct 22 10:53:33.860 : invmgr[250]: %PLATFORM-INV-6-NODE_STATE_CHANGE : Node: 0/0/0, state: UNPOWERED
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#
RP/0/RSP0/CPU0:asr9001#show inventory
Tue Oct 22 11:01:32.251 UTC
NAME: "module 0/RSP0/CPU0", DESCR: "ASR 9001, Route Switch Processor with 8GB memory"
PID: ASR9001-RP, VID: V01 , SN: FOC1728XXXX
NAME: "module 0/0/CPU0", DESCR: "ASR 9001, Modular Line Card"
PID: ASR9001-LC, VID: V01 , SN: FOC1728XXXX
NAME: "module 0/0/0", DESCR: "ASR 9000 20-port 1GE Modular Port Adapter"
PID: A9K-MPA-20X1GE, VID: V00, SN: FOC1522XXXX
NAME: "module 0/0/2", DESCR: "ASR 9000 Virtual Module"
PID: A9K-MODULEv, VID: N/A, SN: N/A

Bryan,
We checked the "show hw-module fpd location all" and there is no "yes" in the last column.
http://pastebin.com/W1wuqYks
RP/0/RSP0/CPU0:asr9001#sh hw-module fpd location all
Thu Oct 24 13:40:19.487 UTC
===================================== ==========================================
                                      Existing Field Programmable Devices
                                      ==========================================
                                        HW                       Current SW Upg/
Location     Card Type                Version Type Subtype Inst   Version   Dng?
============ ======================== ======= ==== ======= ==== =========== ====
0/RSP0/CPU0 ASR9001-RP                 1.0   lc   fpga2   0       1.14     No
                                              lc   cbc     0      22.114    No
                                              lc   rommon 0       2.01     No
0/FT0/SP     ASR-9001-FAN               1.0   ft   cbc     7      24.114    No
0/0/CPU0     ASR9001-LC                 1.0   lc   cbc     0      23.114    No
                                              lc   fpga2   0       1.18     No
                                              lc   fpga4   0       2.07     No
                                              lc   rommon 0       2.01     No

Issues with loadjava utility on oracle database 10.2.0.4.0

Hi all
Hoping if this is a known issue, am approaching you here .. We have an oracle database in 10.2.0.4.0 version. This database functionality of Websphere Process Server, a product from IBM. In the course we are expected to load a JAR file for a one schema and it fails for some reason with ORA - 07445 errors. I happen to set out SGA_MAX_SIZE and SGA_TARGET at 1024 MB and JAVA_POOL_SIZE at 768MB to allow this loadjava command to run successfully. I also happen to set the LD_LIBRARY_PATH as $ORACLE_HOME/lib on this solaris 10 machine. Below is the command and the error message we are receiving. Please do advice us if this is a known issue or guide us to any information which might help us resolve this issue while we continue searching for a solution.. Many thanks in advance.
Regards!
Sarat
loadjava -user BPCDB/[email protected]:1521:WPSDB -resolve /opt/IBMProc/WebSphere/ProcServer/lib/bpcodbutil.jar -thin -schema BPCDB
Error while testing for existence of dbms_java.handleMd5
No more data to read from socket
Error while testing for existence of "BPCDB".JAVA$CLASS$MD5$TABLE
OALL8 is in an inconsistent state
Error while testing for existence of "BPCDB".JAVA$CLASS$MD5$TABLE
OALL8 is in an inconsistent state
Error while creating "BPCDB".JAVA$CLASS$MD5$TABLE
No more data to read from socket
Error while getting old MD5 of META-INF/MANIFEST.MF
Io exception: Broken pipe
Error while testing for existence of "BPCDB".CREATE$JAVA$LOB$TABLE
Closed Connection
Error while testing for existence of "BPCDB".CREATE$JAVA$LOB$TABLE
Closed Connection
Error while creating "BPCDB".CREATE$JAVA$LOB$TABLE
Closed Connection
Error while getLoadLOB BPCDB
Closed Connection
Error while deleting MD5 of META-INF/MANIFEST.MF
Closed Connection
Error while getting old MD5 of com/ibm/bpe/observer/dbutil/TimestampUtil
Closed Connection
Error while processing com/ibm/bpe/observer/dbutil/TimestampUtil
Exception java.lang.NullPointerException
Error while deleting MD5 of META-INF/MANIFEST.MF
Closed Connection
Error while getShortFromLongnameStmt
Closed Connection
Error while processing class BPCDB.com/ibm/bpe/observer/dbutil/TimestampUtil
Exception java.lang.NullPointerException
Error while getShortFromLongnameStmt
Closed Connection
Exception in thread "main" java.lang.NullPointerException
at oracle.aurora.server.tools.loadjava.ClientSchemaObject.getShortname(C
lientSchemaObject.java:65)
at oracle.aurora.server.tools.loadjava.ClientSchemaObject.status(ClientS
chemaObject.java:91)
at oracle.aurora.server.tools.loadjava.SchemaObject.failure(SchemaObject
.java:799)
at oracle.aurora.server.tools.loadjava.LoadJava.process(LoadJava.java:85
1)
at oracle.aurora.server.tools.loadjava.LoadJava.command(LoadJava.java:25
1)
at oracle.aurora.server.tools.loadjava.LoadJavaMain.run(LoadJavaMain.jav
a:103)
at oracle.aurora.server.tools.loadjava.LoadJavaMain.main(LoadJavaMain.ja
va:28)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

ORA-07445 is an untrapped exception, an error, in Oracle's own code.
Open an SR at metalink and update an RDA along with your description of what happened.

BPM Error Permanent Error in BPE inbound processing

Hi
I require some urgent help on this BPM issue.
We are trying to integrate SRM PO being directly sent to Vendors using HTTP. We are getting an error saying Permanent Error in BPE inbound processing. The scenario works like this.
SRM system would sent PO using the SRM Standard interface PurchaseOrderRequest_Out. We need to transform the message into cXML format and send it to the vendors using HTTP adapter. Using the HTTP response we need to trigger an email to the business process team.
The SRM interface is under the software component SAP SRM Server 5.5 and our mapping is being done in a common software component and for the vendor interface we have another software component. We have created a relationship in the SLD by making the common SWC as dependent software component to SAP SRM Server and Vendor Software Component. So in the integration repository we are able to get the interfaces for the SAP SRM Server and Vendor Software Component under the common software component. The receive step for this BPM is a copy of the standard SRM interface PurchaseOrderRequest_Out(as the standard interface is an asynchronous interface) and we would require an abstract interface for the BPM. We have checked the semantics for the BPM and its fine. The related ID development is in place. When the message is being triggered, it gives us this above mentioned error. When we go to the QRFC monitor we are able to check the details.
Regards,
Indranil

Hi Indranil,
     You don't see you BPM....
First go to SXI_CACHE and check that your BPM is listed there and that the compilation has been completed succesfully.
Is this the first time the BPM is being used? If so check if has been configured. For example, go to RWB->Component Monitoring->BPE in <SYSID>
and check if any error is listed there.
In order to check what is going on in your BPM you can trace it:
                  SXMB_MONI_BPE->Diagnosis Processes with Errors
                  SXMB_MONI->Process, get your msg and click on 'PE'. You should see the workitems and see if there is any error.
         Hope this helps you....
         Regards,
            Encinas.

Error in BPE Adapter Processing

Hi Experts,
I have a scenario in which data flow from JDBC => BPE => ECC.
while sending data from JDBC to BPE adapter, faced below error in SXMB_MONI.
"Error in BPE Adapter Processing"
In SXMB_MONI, Overall status displays as "Manual Restart Possible" error as attached below.
I completed the all configuration related to SWF_XI_CUSTOMIZING and SXI_CACHE.
also my Integration process has return code 0 in SXI_CACHE.
I also want to know what are the software's required in PI related to BPM for both JAVA and ABAP Stack. i have a SAP PI System with version 7.31.
Please guide me to solve this error and also inform me if any configuration related to BPE adapter is missing or not.

hi dear,
Tried the reports which are mentioned in the notes and followed the link
but we couldn't resolve the same. can u please help us to move ahead to resolve our issue.
any corrections / suggestion regarding the same.
Permanent error in BPE inbound processing

Newbie: Where do you find the Resource Adapter XML in BPE

Hi,
I am trying to follow the documentation for adding a "Delete After Action" to a resource. Step 6 mentions editing the XML for the resource adapter. I know how to run the BPE, but I cannot find what object to open in the repository. How do I perform this step?
6. Edit the XML for the NT resource and add information to the �delete after action� schema mapping. Here is an example of a complete schema mapping for this resource with the new additions. (You will be adding the views-related information.)
<AccountAttributeType id='12' name='delete after action' syntax='string' mapName='IGNORE_ATTR' mapType='string'>
   <Views>
      <String>Delete</String>
   </Views>
</AccountAttributeType>
Thx,
Jim

Are there any known issues with the instructions
here:
http://docs.sun.com/source/819-4520/Adding_Actions_to_
Resources.htmlI have the same problems with IDM 7.0. Followed the instructions and many tips in this forum but nothing worked. My delete-method is not executed.
Does anyone know how to fix this?

BPM Issue with Queue

HI All,
I created a BPM in our upgraded PI 7.0 SP10 server. However every message is getting the scheduled in Outbound queue(Green Flag) while trying to go to the BPE. I checked SMQ1 and found that the messages are failing with the following error "Password logon no longer possible - too many failed attempts" using user XIISUSER. Now is is confusing to me, because this user is NOT LOCKED. Also, I tried various other users to the same error. Is this some type of new issue with 7.0 compared to 6.40? How can I solve this? I even changed the password of XIISUSER and still no avail. Can this error be turned off in the instance profile?
Thanks for the help!
Chris

Hi Richard,
maybe it's not the user who is locked but his wrong password
somewhere?
check places where do you use this user and change the passwords there too
like RFC dest : INTEGRATION_DIRECTORY_HMI
and other
do you understand the idea ?
Regards,
michal

TimeOut Exceeded in Inbound BPE queue

Hi All,
We have been facing an issue in our PI production box which stops the whole BPE inbound queue for one particular BPM.
We have a simple BPM pattern to spilitt messages
Receive Message>Transformation which includes Java mapping>Send step Inside Block with multiline elemnet ( To send n number of messages to target application using HTTP adapter).
We received 5 MB file for this interface and it got failed in BPE inbound queue with error message "Time Limt Exceeded". The IP is using One queue and Buffering possible options. Ideally what happens is message is getting blocked in the BPE inbound queue which stops other messages.
There is always active receive step is available to receive messages from Q.
The corresponding Integration process was not able to pick the message which 5-7MB file size. The BPM is running fine without any issue when file size is smaller.
I have gone through the following documents already.
How To Configure Inbound Processing in ccBPM Part I: DeliveryMode
How to Configure Inbound Processing in ccBPM Part II Queue Assignment
How ToConfigure ccBPM Runtime Part III: Transactional Behavior of an Integration Process.
Could anyone suggest me if i hcan change any default settings which mentioned in above documents? Rightnow i am using "One Queue" and "Buffering possible" options.
Where exactly time limt settings are maintained for BPE inbound queue?
Edited by: Rajesh on Oct 27, 2009 11:47 PM

First thing that I would do is to remove the queue specification in the BPM. This way, it will not block any other messages of the BPM. Then check for any Runtime paramters in SXMB_ADM for increasing the wait time.
VJ

Permanent error in BPE inbound processing for BPM Mesg Split

Hi Friends,
i have done the below scenario. i had done everything what theys mentioned in the blog but i am getting the error in smq2 as "Permanent error in BPE inbound processing" sysfail please helpme on this issue.
Illustration of Multi-Mapping and Message Split using BPM in SAP Exchange Infrastructure

Hi Uday,
Please check this blog for your error, This is really interesting. Permanent solution for your question.
Delivery Modes in BPM.
Thanks!

BPM - two FORKS and a Transformation issue

my scenario is File - BPM - Proxy
input file has multiple records and each record has 1 field that we put a validation logic in. There will be one message created for each record, so this is a 1:N Integration Process
I used two Forks:
Fork #2 has two branches: Branch 1 --> Transformation Step 3;     Branch 2 ---> Fork #1.
Validation#1 = if the validation field has null value then it will go to Transformation Step3 along Fork#2 (end receiver is Proxy-C)
validation#2 = if the field has value then it will go inside Fork#1 which has 2 branches: Transformation Step 1 (goes to Proxy-A) and Transformation Step 2 (goes to Proxy-B)
I am testing a file with only the null value, so I am doing validation#1 only.
I can see the message in BPE engine (Outbound status = Processed successfully) but the message is stucked in the BPE
I checked on the workflow log and here is what i see:
1) Transformation Step 3 is executed (all mapping steps 1-4 completed so this is successful)
2) Transformation Step 2 is executed (but mapping encounters an exception so this is not successful)
3) Transformation Step 1 is not executed already because of the exception, and therefore Send Alert is triggered.
It seems that all records of the file passes through all the branches, which is not intended.
My intention is that when the validation field has null value that record will only pass thru Transformation Step 3,   if it is not null then record will pass thru Transformation Step 2 & 1.
I already created a mapping for this validation, and when I test the Interface Mapping for Transformation Step 3 (consisting of 4 mapping steps) using an actual payload it is successfuly generating the message. - so no problem in this Interface Mapping.
But on Runtime, BPM triggers exception due to validation#2 failing which again is because all records of file seem to pass on both Forks. I want that when Validation#1 is true that specific record only passes in Fork#2   and not in Fork#1 also.
I am using ParForEach.
Can you kindly advise how to correct this issue?

that was a very detailed explanation!
But on Runtime, BPM triggers exception due to validation#2 failing which again is because all records of file seem to
pass on both Forks. I want that when Validation#1 is true that specific record only passes in Fork#2 and not in Fork#1 also
problem with your design...Fork seems to be working fine....you need to have a Switch block which will perform the validation and then route the message accordingly.
I already created a mapping for this validation, and when I test the Interface Mapping for Transformation Step 3
(consisting of 4 mapping steps) using an actual payload it is successfuly generating the message. - so no problem in this
Interface Mapping.
Mapping success does not mean that the BPM processing will be success.

BPM workflow "In Process"-Queue "Permanent error in BPE inbound processing"

Hi All,
I am trying to collect messages from 2 different interfaces into BPM( Integration Process).
when I checked in sxmb_moni , i found the error on outbound status & BPM workflow has stuck with status "In Process".
it is not showing any error in Workflow, how to solve the issue.
due to the above error, other messages are stuck in Queue stating "Permanent error in BPE inbound processing".
Please help.
-Jyoti

Hi Jyoti,
Goto T.Code swwl, in that clear all fields and choose from date as 1 month ago and try to execute. Then, delete all entries there. And re-execute your scenario.
In this case, please see SAP Note 1126656.
Please see the below blog, it might be helpful to you.
/people/henrike.kaiser/blog/2009/02/03/how-to-analyze-stopped-queues-in-xi-ccbpm
Regards,
Rajesh

Correlation issue due to async receive with sync/async bridge

Hi,
I have an Integration process (PI 7.0), which consists of sync/async bridge.
One of the step in the process is async receive.
To avoid any issue with correlation, i placed the whole process (except start and end) into a block and assigned a local correlation to it.
The Sync receive in sync/async bridge will activate the correlation and one of the async receive step in the process will use that correlation.
Normally it worked fine. But during one execution (just for testing), the async receive step did not take input to the process, and so the process execution replied "Timeout in Pipeline". But thereafter i cannot execute the process successfully, even when async takes the input.
And in the BPE monitoring, in workflow log, the process Instances are still "In Progress".
Do we have any way to stop these processes and unlink any possible correlation related to them?

Hi,
A local correlation is only valid for the block for which it is defined. Once the block has been processed, the correlation is no longer active.
If the validity of a correlation is not restricted correctly, the following problems can occur:
¡ Messages that satisfy an active correlation are continued to be assigned to a running integration process. The integration process no longer processes the messages because no processing steps are waiting for the messages.
¡ Messages that satisfy an active correlation are continued to be assigned to a running integration process, instead of starting a new integration process.
You can avoid these problems and make it easier to follow how messages are processed by restricting correlations correctly to the required block.
Please check the local correlations for it
With SXMB_MONI_BPE you can monitor these instances.
But to kill it you need to use tcode SWWL. You can go to SXMB_ADM_BPE to check the BPM related settings.
Thanks
swarup
Edited by: Swarup Sawant on May 31, 2008 1:40 AM

System Error in BPE after upgrading to SPS 20

Hi,
on Monday we have updated our XI from SPS 19 to SPS 20.
Since that day we get errors in our BPE.
Following the scenario:
We receive a SOAP request from our partner, which is delivered to a ccBPM Process via an abstract synchronous interface. First step in the process is starting a sync/async bridge, followed by 2 mapping steps. The the bridge is closed by sending the response to our partner.
Looking at the workflow protocol I see the error in step "<i>S/A Bridge - Response to synchronous Request</i>". Looking at the transaction SWF_XI_SWI2_DIAG the error:
<i>Error on access to table SXMS_AS_STATUS Methode: SELECT. 00000000000000000000000000000000
Workitem 000000271155: Object CL_SWF_XI_MSG_BROKER Method SEND_SYNCHRON_REPLY could not be executed</i>
Has anyone an idea why we are getting this error?
Before upgrading to SPS 20 this error did not occur...
Thanks for your help!
Greetings
Habib Sarbas

Hello Habib,
I'm having the same error in our BPM scenario.
Can you share what you had to do to fix this issue?
Thanks,
Jay

IDoc to Soap, with BPM - Permanent error in BPE inbound processing

Hi Experts,
IDoc to Soap, with BPM - > Permanent error in BPE inbound processing
How to rectify this any issue???
Thanks-
sk

Hi,
The inbound processing encountered a permanent error and the queue therefore stopped.
The error message "Permanent error in BPE inbound processing" may be caused by the following:
- At the start or when you process a process instance, the inbound processing encounters an exception that was not handled. This exception is triggered, for example, by a transformation step, a synchronous send step or a control step but it was not caught in an exception handler branch. If the exception that was not handled occurs in the first transaction of the started process instance, the system does not write the process instance to the database but it sets the queue that has this error message to the error status.
Refer to the help in Note 1082099
- The inbound processing triggers this error if the correlation evaluation shows that a message should be delivered to a process instance that has the status "error". Since delivery to process instances that contain errors is not permitted, the queue is stopped.
Use the simulation of the message delivery in the detail view of the relevant queue LUW to determine the relevant process instance for the affected message and use transaction SXMB_MONI_BPE "Continue Process Following Error" (or transaction SWF_XI_SWPR) to continue. If you cannot continue the process instance, check whether you can logically delete the instance. In this case, use the method that is described in Note 807906 to logically delete a process instance.
Check whether your system contains other process instances that have errors in order to detect similar problems. Use transaction SXMB_MONI_BPE "Continue Process Following Error" or transaction SWF_XI_SWPR.
Use the report RSWF_CRL_MAINTAIN to check all of the correlation instances in question or the relevant process instances that you can reach using "Display Work Item".
- Messages that cannot be delivered because no correlation instance can be found may lead to the error that is mentioned here. Check whether the causes that are outlined in Note 1094028 affect your case.
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful.

BPE Issue?

Similar Messages

Maybe you are looking for