Destination R/3 System not mapped error

Hi,
I am getting the error "Destination R/3 System not mapped". I am getting this error when tried to extract data from a data source in transaction RSA3. I resaved the data source (RSA6) and activated the extract structure (RSA2), but still getting the same error. Any help will be much appreciated.
-Ravi.

Hi Dennis,
Thanks for your response. No, I was not specifying a target system. Per your suggestion, I picked one of the systems from the list, and still got the same message. I was thinking in the same lines on an RFC may be missing, but I have this problem with only one of the data sources. I am able to extract data from other data sources w/o issues. I would think all the data sources will fail if an RFC is missing.
Also, this system is backcopied from another system recently. I am thinking some thing went wrong with this data source during the backcopy, but unable to pinpoint what that could be. Your help is much appreciated.
Thanks,
Ravi.

Similar Messages

Source system not available error

If the error message is teling as source system not available
so what can be the reasons for that and tell me the solution also.
data cllection is incorrect
so what can i do i have checked trfc connections every thing but every thing is fine
so any body help me out in this.
your suggstions will be rewarded.
Regards.
Vikram.

Hi Vikram,
Try the below mentioned steps:
1. Check the connections on BW sysetem and R/3 system.
Use the tcodes: sm58 and sm59. On the context menu of the source system created, check the option for conections. If connections are not fine, contact the basis team
2. Go to 'source systems' select you source system and right click and select 'Repicate Data Sources' , then try replicating the the infosource for that
appilication at the top node level as a whole, the try replicating the Data source
with in your infoarea..
Hope it would help ..if yes..assign points.
Regards,
Manu.

Source system not Active error while installing BI content cube

Hi.,
When I try to install the BI content cube, In logs it is showing the error message as "Source client not Active". I activated the source system in modelling tab. Still the problem continues. In source system assignment of BI content the source client is also checked. Please give me a solution.

Hi Selva,
If you want to select only infocube, select "Only necessary objects" in grouping. If you want everything related to Info cube, then system will collect data source also and for that it will check if you are authorized in source system. Please check if the source system is connected to BI or you can do one thing activate the data source in source system and replicate it in BI.
Regards,
Kams

System not authorized error

I am using ITunes on Window 7. Some of the Apps on my Iphone 4(iOS 6) are associated with account A and some are associated with account B. Now, if I use ITunes on my desktop and try syncing/installing/updating the Apps using account B, it shows me an error that you need to authorize this computer and when I authorize my system, it shows that this computer is already authorized

Perhaps a dumb question on my part, but have you tried just restaring the problem systems? If you can't restart them, try restarting the ARD agent via the kickstart command:
http://support.apple.com/kb/HT2370
To restart the agent (at least in most versions of OS X):
/System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/ki ckstart -restart -agent
Hope this helps.

Operation System not found

I've been following the beginners' guide and I keep running into this "Operation System not found" error.
I'm using a dell xps l502x, and trying to install x86_64 arch. I've tried using syslinux and grub both with the same error on reboot
During a syslinux install I use fdisk to partition the drive. The tutorial says this is to create an mbr, but it gives me a gpt from some reason:
Disk /dev/sda: 120.0 GB, 120034123776 bytes, 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: gpt **this I don't understand, as I'm following the guide for the mbr**
# start end size type name
1 2048 31459327 15G Linux filesystem
2 31459328 234441614 96.8G Linux filesystem
and my fstab is:
# <file system> <dir> <type> <options> <dump> <pass>
#/dev/sda1
UUID=0ec7dc20-1ea3-4f1c-810b-4fded8550744 / ext4 rw,relatime,data=ordered 0 1
#/dev/sda2
UUID=9d6efd2f-8a18-4968-b251-7e09983ef539 /home ext4 rw,relatime,data=ordered 0 2
So I have no errors at this point other then fdisk creating gpt instead of mbr.
I install syslinux, no errors:
Syslinux install successful
attribute legacy bios bootable set - /dev/sda1
installed MBR (usr/lib/syslinux/gptmbr.bin) to /dev/sda
I edit the syslinux config to point to /dev/sda1.
exit, umount /mnt/home, reboot, operation system not found!. The strange thing is when i go to the install disk and click Boot existing OS, I am able to find my install through syslinux and select Arch Linux, and it is functional.
I'm not really sure where to go from here as I've tried both syslinux and grub with the same result. When using grub I make sure to create the 1007kb boot partition marking it as EF02, and i still get operation system not found.
Last edited by soote (2013-08-31 20:36:12)

WonderWoofy wrote:This sounds not like a problem with Arch or your bootloader installation at all. Rather it sounds as though you need to make an adjustment to your bios to tell it to correctly try to boot the disk with syslinux on it.
Thank you for the advice. I followed the steps listed here, and ran everything except for the last command (# syslinux-install_update -i -m). On reboot I was still faced with the Operation system not found error. I then ran # syslinux-install_update -i -m and got the following:
Syslinux install successful
ABORT! MBR installation to partition (/dev/mapper/arch_root-image)!
I'm unsure of what this error means, but it lead me to this blog entry.
This blog looks promising.
roentgen wrote:
Same Dell here. It seems to be a compatibility problem between BIOS and GPT.
I couldn't find any other way than to use MBR.
How do you create the partition table? In fdisk 'o' is used to create a DOS (MBR) partition table.
I followed the beginners' guide to create it. I will try creating the partitions with o instead of p, i didn't know about that option. I really don't need a GPT partition.
Last edited by soote (2013-08-31 21:07:22)

Help~open hub destination file is not open error!

Hi all,
I met a problem, i tried several times and all got error messages.
It is about open hub destination, i want to use it to send some files to sever, but when i execute the DTP, i got system dump:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Runtime Errors         DATASET_NOT_OPEN
Except.                CX_SY_FILE_OPEN_MODE
Date and Time          26.10.2011 01:18:09
Short text
    File "I:\usr\sap\Q26\DVEBMGS11\work\ZSS_O0021.CSV" is not open.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_RSB_FILE_APPLSRV===========CP" had to
     terminated because it has
    come across a statement that unfortunately cannot be executed.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I have two open hub, one is fine ,but the rest one always get this error. Help..........

Thanks! I checked my ID and found that i have the role to access this folder.
Then i found that our Q system have two servers, A and B, for open hub i should run my process chain in system B, but i forgot that, so i got error. After i changed to sever B, i re-active my open hub and DTP, then re-fresh the process chain and re-executed it again, the error disappeared.

Error: System not configured as Integration Engine

Hi ,
I was trying to simulate the following scenario in SAP XI:
HTTP--> SAP XI --> (RFC/BAPI)SAP R/3
Let me clear what i did.
I have to call a BAPI using RFC adapter in XI to display some information on a request of some Http app.
1. I have Imported the RFC BAPI into IR.
2. I have created the XSD files for http Re and res messages.
3. I have created the XSLT mapping programs and put them in a zip file and imported into IR.
4. I have created a Interface mapping and assign the created messages and mapping programs.
5. In ID i have created a Business service for my web application.
6. Receiver determination created in Id and Interface determination and receiver agreement in ID and activated the changes.
7. I have tested the same by sending the request from my web application to xi plain http adapter as follows:
http://grserver:8000/sap/xi/adapter_plain?bs=XIWS_web&namespace=urn%3Axi%3Asap%3Awebapp&interface=HTTP_out&qos=BE
and in the result i have got the following error:
"System not configured as Integration Engine"
but i have tried it many times and some times it gives me correct results but after that the same error ios coming.
so can you tell me what could be wrong in the configuration of XI of what is the solution for this problem.
Reagrds
Gopesh Kumar Agarwal

Hi,
What is the version of XI you are using? If u are usign XI2.0, ur URL is correct. But if you are using XI3.0 then use service=<SENDERSERVICE>instead of
bs=<SENDERSERVICE> parameter in your URL.
bs is replaced by service in XI3.0
Your URL will be http://grserver:8000/sap/xi/adapter_plain?service=XIWS_web&namespace=urn%3Axi%3Asap%3Awebapp&interface=HTTP_out&qos=BE
Hope this helps you.
Cheers,
Siva Maranani.
Message was edited by: siva maranani
Message was edited by: siva maranani

RFC destination R/3 Source does not exist., error key: RFC_ERROR_SYSTEM_FAI

Hi All,
I am getting the error "RFC destination R/3 Source does not exist., error key: RFC_ERROR_SYSTEM_FAILURE" when planning sequence (IP) is executed. Can some one help me please asap.
Regards
Kiran

Hi,
Please go to sm59 and check if the RFC connection exists for this source system. If its there, please double click on it and on next screen, go to Menu bar and click on Test-> Connection and then test -> authorisation.
If you get any error, thats the reason. If you dont find the RFC at all, thats the reason why you got error.
You may also check WE20 for partner profile, whether it exists or not.

Message-driven bean destination name not found error

Hi,
I am getting this error when I attempt to deploy the Warehouse message-driven bean example/tutorial. I followed the steps in the JMS Queue Simple Sample Application included with the server to set up the queue and queue factory, but I don't think the app. is even getting that far. I can not figure out why I'm get this error. I have looked at everything I can think of, but I'm obviously missing something. Here is the error from the server log.
INFO ( 2252): JMS5015: Install JMS resources ...
INFO ( 2252): JMS5002: Binding [< JMS Destination: jms/WarehouseQueue, javax.jms.Queue, [ imqDestinationName=WarehouseQueue ] >]
INFO ( 2252): JMS5002: Binding [< JMS Connection Factory: jms/WarehouseQueueConnectionFactory, javax.jms.QueueConnectionFactory, [ imqBrokerHostName=localhost , imqBrokerHostPort=7676 ] >]
INFO ( 2252): HTTP3072: HTTP listener http-listener-1 [http://ibankdev2:80] ready to accept requests
INFO ( 2252): CORE3274: successful server startup
INFO ( 2252): CORE5053: Application onReady complete.
INFO ( 2252): MDB00044: Deploying message-driven bean [MDBApp:Warehouse], consuming from [jms/Warehouse]
SEVERE ( 2252): MDB00015: [MDBApp:Warehouse]: Message-driven bean destination name [jms/Warehouse] not found
SEVERE ( 2252): javax.naming.NameNotFoundException
javax.naming.NameNotFoundException: Warehouse not found
at com.sun.enterprise.naming.TransientContext.doLookup(TransientContext.java:185)
at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:157)
at com.sun.enterprise.naming.TransientContext.lookup(TransientContext.java:161)
at com.sun.enterprise.naming.SerialContextProviderImpl.lookup(SerialContextProviderImpl.java:78)
at org.omg.stub.com.sun.enterprise.naming._SerialContextProviderImpl_Tie._invoke(Unknown Source)
at com.sun.corba.ee.internal.corba.ServerDelegate.dispatch(ServerDelegate.java:375)
at com.sun.corba.ee.internal.iiop.ORB.process(ORB.java:275)
at com.sun.corba.ee.internal.iiop.LocalClientRequestImpl.invoke(LocalClientRequestImpl.java:96)
at com.sun.corba.ee.internal.corba.ClientDelegate.invoke(ClientDelegate.java:237)
at com.sun.corba.ee.internal.corba.ClientDelegate.invoke(ClientDelegate.java:279)
at org.omg.CORBA.portable.ObjectImpl._invoke(ObjectImpl.java:457)
at org.omg.stub.com.sun.enterprise.naming._SerialContextProvider_Stub.lookup(Unknown Source)
at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:138)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.sun.ejb.containers.MessageBeanHelperBase.setup(MessageBeanHelperBase.java:317)
at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:206)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:173)
at com.iplanet.ias.server.AbstractLoader.loadEjbs(AbstractLoader.java:345)
at com.iplanet.ias.server.ApplicationLoader.load(ApplicationLoader.java:81)
at com.iplanet.ias.server.ApplicationManager.applicationDeployed(ApplicationManager.java:134)
at com.iplanet.ias.server.ApplicationManager.applicationDeployed(ApplicationManager.java:110)
at com.iplanet.ias.server.ApplicationManager.applicationDeployed(ApplicationManager.java:294)
at com.iplanet.ias.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:424)
at com.iplanet.ias.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:408)
at com.iplanet.ias.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:291)
at com.iplanet.ias.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:99)
at com.iplanet.ias.admin.server.core.channel.AdminChannelServer.sendNotification(AdminChannelServer.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
SEVERE ( 2252): MDB00030: [MDBApp:Warehouse]: Exception in setting up message-driven bean container: [MDBApp:Warehouse: Message-driven bean destination jms/Warehouse not found]
SEVERE ( 2252): MDB00017: [Warehouse]: Exception in creating message-driven bean container: [javax.jms.JMSException: MDBApp:Warehouse: Message-driven bean destination jms/Warehouse not found]
SEVERE ( 2252): javax.jms.JMSException
javax.jms.JMSException: MDBApp:Warehouse: Message-driven bean destination jms/Warehouse not found
at com.sun.ejb.containers.MessageBeanHelperBase.setup(MessageBeanHelperBase.java:340)
at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:206)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:173)
at com.iplanet.ias.server.AbstractLoader.loadEjbs(AbstractLoader.java:345)
at com.iplanet.ias.server.ApplicationLoader.load(ApplicationLoader.java:81)
at com.iplanet.ias.server.ApplicationManager.applicationDeployed(ApplicationManager.java:134)
at com.iplanet.ias.server.ApplicationManager.applicationDeployed(ApplicationManager.java:110)
at com.iplanet.ias.server.ApplicationManager.applicationDeployed(ApplicationManager.java:294)
at com.iplanet.ias.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:424)
at com.iplanet.ias.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:408)
at com.iplanet.ias.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:291)
at com.iplanet.ias.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:99)
at com.iplanet.ias.admin.server.core.channel.AdminChannelServer.sendNotification(AdminChannelServer.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
SEVERE ( 2252): EJB5090: Exception in creating EJB container [javax.jms.JMSException: MDBApp:Warehouse: Message-driven bean destination jms/Warehouse not found]
SEVERE ( 2252): appId=MDBApp moduleName=EJBModule_Warehouse_jar ejbName=Warehouse
SEVERE ( 2252): LDR5004: UnExpected error occured while creating ejb container
javax.jms.JMSException: MDBApp:Warehouse: Message-driven bean destination jms/Warehouse not found
at com.sun.ejb.containers.MessageBeanHelperBase.setup(MessageBeanHelperBase.java:340)
at com.sun.ejb.containers.MessageBeanContainer.<init>(MessageBeanContainer.java:206)
at com.sun.ejb.containers.ContainerFactoryImpl.createContainer(ContainerFactoryImpl.java:173)
at com.iplanet.ias.server.AbstractLoader.loadEjbs(AbstractLoader.java:345)
at com.iplanet.ias.server.ApplicationLoader.load(ApplicationLoader.java:81)
at com.iplanet.ias.server.ApplicationManager.applicationDeployed(ApplicationManager.java:134)
at com.iplanet.ias.server.ApplicationManager.applicationDeployed(ApplicationManager.java:110)
at com.iplanet.ias.server.ApplicationManager.applicationDeployed(ApplicationManager.java:294)
at com.iplanet.ias.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:424)
at com.iplanet.ias.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:408)
at com.iplanet.ias.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:291)
at com.iplanet.ias.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:99)
at com.iplanet.ias.admin.server.core.channel.AdminChannelServer.sendNotification(AdminChannelServer.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
WARNING ( 2252): CORE5021: Application NOT loaded: [MDBApp]
WARNING ( 2252): ADM5603:Event listener error [Error while deploying application [MDBApp]. Please refer to the server log for more details. ]
My bean name is Warehouse, jms/Warehouse is the JNDI and is mapped to MDBPack.WarehouseBean.class. MDBPack is in the classpath on the server. I guessed that the physical destination name was WarehouseQueue, but using Warehouse produced the same result. Please let me know if there is anything I could be missing. TIA
--Michelle

Hi,
You have not created the jms destination queue object
jms/Warehouse
Your server logs says it cannot find the destination queue object.It has got nothing to do with jndi name of your bean
Create jms destination queue object using
asadmin>create-jms-resource instance <instance_name> resourcetype javax.jms.Queue --property imqDestinationName=<NAme> jms/Warehouse
Then use list-jms-resources <instance_name> to
find if jms/Warehouse destionation queue object has been created.
Get back in case of any issues

DG Observer triggering SIGSEGV Address not mapped to object errors in alert log

Hi,
I've got a Data Guard configuration using two 11.2.0.3 single instance databases. The configuration has been configured for automatic failover and I have an observer running on a separate box.
This fast-start failover configuration has been in place for about a month and in the last week, numerous SEGSEGV (address not mapped to object) errors are reported in the alert log. This is happening quite frequently (every 4/5 minutes or so).
The corresponding trace files show the process triggering the error coming from the observer.
Has anyone experienced this problem? I'm at my wits end trying to figure out how to fix the configuration to eliminate this error.
I must also note that even though this error is occurring a lot, it doesn't seem to be affecting any of the database functionality.
Help?
Thanks in advance.
Beth

Hi.. The following is the alert log message, the traced file generated, and the current values of the data guard configuration. In addition, as part of my research, I attempted to apply patch 12615660 which did not take care of the issue. I also set the inbound_connection_timeout parameter to 0 and that didn't help either. I'm still researching but any pointer in the right direction is very much appreciated.
Error in Alert Log
Thu Apr 09 10:28:59 2015
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x9] [PC:0x85CE503, nstimexp()+71] [flags: 0x0, count: 1]
Errors in file /u01/app/oracle/diag/rdbms/<db_unq_name>/<SID>/trace/<SID>_ora_29902.trc (incident=69298):
ORA-07445: exception encountered: core dump [nstimexp()+71] [SIGSEGV] [ADDR:0x9] [PC:0x85CE503] [Address not mapped to object] []
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Thu Apr 09 10:29:02 2015
Sweep [inc][69298]: completed
Trace file:
Trace file /u01/app/oracle/diag/rdbms/<db_unq_name>/<SID>/trace/<SID>_ora_29902.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning and Oracle Label Security options
ORACLE_HOME = /u01/app/oracle/product/11.2.0.3/dbhome_1
System name: Linux
Node name: <host name>
Release: 2.6.32-431.17.1.el6.x86_64
Version: #1 SMP Wed May 7 14:14:17 CDT 2014
Machine: x86_64
Instance name: <SID>
Redo thread mounted by this instance: 1
Oracle process number: 19
Unix process pid: 29902, image: oracle@<host name>
*** 2015-04-09 10:28:59.966
*** SESSION ID:(416.127) 2015-04-09 10:28:59.966
*** CLIENT ID:() 2015-04-09 10:28:59.966
*** SERVICE NAME:(<db_unq_name>) 2015-04-09 10:28:59.966
*** MODULE NAME:(dgmgrl@<observer host> (TNS V1-V3)) 2015-04-09 10:28:59.966
*** ACTION NAME:() 2015-04-09 10:28:59.966
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x9] [PC:0x85CE503, nstimexp()+71] [flags: 0x0, count: 1]
DDE: Problem Key 'ORA 7445 [nstimexp()+71]' was flood controlled (0x6) (incident: 69298)
ORA-07445: exception encountered: core dump [nstimexp()+71] [SIGSEGV] [ADDR:0x9] [PC:0x85CE503] [Address not mapped to object] []
ssexhd: crashing the process...
Shadow_Core_Dump = PARTIAL
ksdbgcra: writing core file to directory '/u01/app/oracle/diag/rdbms/<db_unq_name>/<SID>/cdump'
Data Guard Configuration
DGMGRL> show configuration verbose;
Configuration - dg_config
Protection Mode: MaxPerformance
Databases:
 dbprim - Primary database
 dbstby - (*) Physical standby database
(*) Fast-Start Failover target
Properties:
 FastStartFailoverThreshold = '30'
 OperationTimeout = '30'
 FastStartFailoverLagLimit = '180'
 CommunicationTimeout = '180'
 FastStartFailoverAutoReinstate = 'TRUE'
 FastStartFailoverPmyShutdown = 'TRUE'
 BystandersFollowRoleChange = 'ALL'
Fast-Start Failover: ENABLED
Threshold: 30 seconds
Target: dbstby
Observer: observer_host
Lag Limit: 180 seconds
Shutdown Primary: TRUE
Auto-reinstate: TRUE
Configuration Status:
SUCCESS
DGMGRL> show database verbose dbprim
Database - dbprim
Role: PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
 DG_CONFIG
Properties:
 DGConnectIdentifier = 'dbprim'
 ObserverConnectIdentifier = ''
 LogXptMode = 'ASYNC'
 DelayMins = '0'
 Binding = 'optional'
 MaxFailure = '0'
 MaxConnections = '1'
 ReopenSecs = '300'
 NetTimeout = '30'
 RedoCompression = 'DISABLE'
 LogShipping = 'ON'
 PreferredApplyInstance = ''
 ApplyInstanceTimeout = '0'
 ApplyParallel = 'AUTO'
 StandbyFileManagement = 'MANUAL'
 ArchiveLagTarget = '0'
 LogArchiveMaxProcesses = '4'
 LogArchiveMinSucceedDest = '1'
 DbFileNameConvert = ''
 LogFileNameConvert = ''
 FastStartFailoverTarget = 'dbstby'
 InconsistentProperties = '(monitor)'
 InconsistentLogXptProps = '(monitor)'
 SendQEntries = '(monitor)'
 LogXptStatus = '(monitor)'
 RecvQEntries = '(monitor)'
 SidName = ‘<sid>’
 StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<db host name>)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=<service_name>)(INSTANCE_NAME=<sid>)(SERVER=DEDICATED)))'
 StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
 AlternateLocation = ''
 LogArchiveTrace = '0'
 LogArchiveFormat = '%t_%s_%r.dbf'
 TopWaitEvents = '(monitor)'
Database Status:
SUCCESS
DGMGRL> show database verbose dbstby
Database - dbstby
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: 0 seconds
Apply Lag: 0 seconds
Real Time Query: ON
Instance(s):
 DG_CONFIG
Properties:
 DGConnectIdentifier = 'dbstby'
 ObserverConnectIdentifier = ''
 LogXptMode = 'ASYNC'
 DelayMins = '0'
 Binding = 'optional'
 MaxFailure = '0'
 MaxConnections = '1'
 ReopenSecs = '300'
 NetTimeout = '30'
 RedoCompression = 'DISABLE'
 LogShipping = 'ON'
 PreferredApplyInstance = ''
 ApplyInstanceTimeout = '0'
 ApplyParallel = 'AUTO'
 StandbyFileManagement = 'AUTO'
 ArchiveLagTarget = '0'
 LogArchiveMaxProcesses = '4'
 LogArchiveMinSucceedDest = '1'
 DbFileNameConvert = ''
 LogFileNameConvert = ''
 FastStartFailoverTarget = 'dbprim'
 InconsistentProperties = '(monitor)'
 InconsistentLogXptProps = '(monitor)'
 SendQEntries = '(monitor)'
 LogXptStatus = '(monitor)'
 RecvQEntries = '(monitor)'
 SidName = ‘<sid>’
 StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<db host name>)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=<service_name>)(INSTANCE_NAME=<sid>)(SERVER=DEDICATED)))'
 StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
 AlternateLocation = ''
 LogArchiveTrace = '0'
 LogArchiveFormat = '%t_%s_%r.dbf'
 TopWaitEvents = '(monitor)'
Database Status:
SUCCESS

ALE error : Maintenance systems not identical

Hi All,
I just configured the ALE settings to send material from client 250 to 214 on the same ECC. When I try to distribute the model I get the error "Maintenance systems are not identical."
What could be the fix for this?

Hi Sakthi,
Refer these links:
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/sapR3%2528Idocs%2529ToXI--Steps+Summarized
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
Steps to be followed are:
1. Create a Logical system for the sender SAP system and the receiving XI system using Transaction - u2018SALEu2019:
2. Assign Client to the Sender Logical System
3. Create RFC destination of type u20183u2019 for SAP XI system using transaction u2013 SM59 note: Make sure that the name of the RFC destination and Logical system for SAP XI is the same.
4. Create a Distribution Model through u2018SALEu2019 transaction. Create a Distribution Model by selecting u2018Create Model Viewu2019.
5. For the model view created above, add the message type of the idoc that you wish to send using this model view. Select u2018Add Message Typeu2019 option and then specify the sender logical system and the receiver logical system.
6. Generate the partner profiles by selecting the navigation path from the main menu, Environment --> Generate Partner profiles
7. From the main screen navigate through the menu option, EDIT --> MODEL VIEW --> DISTRIBUTE. Upon receiving the message, it means the distribution is successful.
8. Go to transaction BD10 to send a material out of IDES
9. Go to transaction WE02/WE05 to check the status of the IDOC in the sendign system.
Hope this helps
Regards,
Nithiyanandam

Logical target not mapped to physical system

Hi Experts,
We are getting issue when we are aceesing webservices.Trace are mentioned below.I am not able to figure out why is this prob as i already test in netweaver administrator-configuration-destination and under this we test all the webservices destination that we created and test is succesfull.Kindly put some lights on this matter.
com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WS metadata destination 'WS_METADATA_DEST_CONF' and WS interface 'PRConfig_1Vi_Document'. One possible reason is that the metadata destination 'WS_METADATA_DEST_CONF' has not been properly configured; check configuration.
* at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:440)*
* at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372)*
* at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342)*
* at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:326)*
* at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo$Cache.getModelInfo(WSModelInfo.java:199)*
* at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:1035)*
* at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:248)*
* at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:41)*
* at com.sap.srm.mdm.admin.pr.PRConfiguration.<init>(PRConfiguration.java:53)*
* at com.sap.srm.mdm.pr.PRConfiguration.wdDoInit(PRConfiguration.java:121)*
* at com.sap.srm.mdm.pr.wdp.InternalPRConfiguration.wdDoInit(InternalPRConfiguration.java:313)*
* at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)*
* at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)*
* at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)*
* at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)*
* at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)*
* at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)*
* at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)*
* at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)*
* at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)*
* at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)*
* at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)*
* at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)*
* at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)*
* at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)*
* at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)*
* at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)*
* at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)*
* at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)*
* at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)*
* at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)*
* at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)*
* at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)*
* at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)*
* at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)*
* at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)*
* at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)*
* at java.security.AccessController.doPrivileged(AccessController.java:219)*
* at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)*
* at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)*
Caused by: com.sap.engine.services.webservices.espbase.discovery.TargetConfigurationException: Logical Target sap.com/DynamicWSProxies/WS_METADATA_DEST_CONF not mapped to a physical system.
* at com.sap.engine.services.webservices.server.management.discovery.ServiceDiscoveryImpl.getWSDLUrl(ServiceDiscoveryImpl.java:73)*
* at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:128)*
* at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:429)*
* ... 39 more*
Caused by: com.sap.engine.services.webservices.espbase.query.exceptions.TechnicalException: Logical Target sap.com/DynamicWSProxies/WS_METADATA_DEST_CONF not mapped to a physical system.
* at com.sap.engine.services.webservices.espbase.query.EngineWSFactoryImpl.getWSQuery(EngineWSFactoryImpl.java:115)*
* at com.sap.engine.services.webservices.server.management.discovery.ServiceDiscoveryImpl.getWSDLUrl(ServiceDiscoveryImpl.java:64)*
* ... 41 more*
Caused by: com.sap.engine.services.webservices.espbase.discovery.TargetNotMappedException: Logical Target sap.com/DynamicWSProxies/WS_METADATA_DEST_CONF not mapped to a physical system.
* at com.sap.engine.services.webservices.server.management.discovery.DestinationsResolver.<init>(DestinationsResolver.java:100)*
* at com.sap.engine.services.webservices.server.management.discovery.ServiceDiscoveryImpl.getEntityResolverForTarget(ServiceDiscoveryImpl.java:99)*
* at com.sap.engine.services.webservices.espbase.query.EngineWSFactoryImpl.getWSQuery(EngineWSFactoryImpl.java:113)*
* ... 42 more*
Thanks,
sudhanshu

For your reference:
This is the only code so far in the implementation:
public void wdDoInit()
 //@@begin wdDoInit()
 //$$begin Service Controller(-608326537)
 Bp03 model = new Bp03();
// wdContext.nodeRequest_BusinessPartnerBasicDataByIDQueryResponse_In().bind(new Request_BusinessPartnerBasicDataByIDQueryResponse_In(model));
 Request_BusinessPartnerBasicDataByIDQueryResponse_In req = new Request_BusinessPartnerBasicDataByIDQueryResponse_In(model);
 wdContext.currentIDElement().setBP_ID("0000000009");
 //$$end
 //@@end
Am i implementing the correct code?
Thanks.

FILE not found error: j2ee/home/applib/applications-mapping.xml (No such fi

Hi EveryBody
i have my applications-mapping.xml file already in the applib directory, but when i try to conect to a remote ejb i had this error[b]
FILE not found error: j2ee/home/applib/applications-mapping.xml (No such file or directory)
can anyone help??

gday
Is the error on the client or server?
What role in the application does applications-mapping.xml fulfill?
How are you loading the file in?
-steve-

PS CS5 The operation could not be completed. A file system I/O error has occurred

Howdy...
I'm using Photoshop CS5 and when I go to use a handful of filters such as Liquify or Lens Correction I am suddenly getting an error message saying:
"The operation could not be completed. A file system I/O error has occurred"
Doesn't matter if it's a massive file or a small one. Sometimes the Liquify box will actually come up, but after I make one or two strokes, the beachball comes up and moments later I get the error message again. It doesn't actually crash PS, it just prevents me from using those filters. Each time I click, the error message comes up again. I've also tried it with my PS CS3 on the same Mac and it does the same thing. However on my 4 year old MacBook Pro, it's absolutely fine. Grrrrr!
I have my PS set as default on 64 bit. I have a scratch disk with nearly 500gb free (which is not my start-up disk) I am running a Mac Pro 2.8 GHz 8 Core Intel with 16gb of ram, so it's not a memory problem. Running Mac OS 10.6.7 but did the same on 10.6.6 too.
I have repaired the disk permissions on the start-up disk. I have reloaded a fresh copy of PS (a few times). Even did a hard Un-install with maccs3clean after trying a regular Un-install with no success.
I had an 1.5hr conversation with an Adobe Tech guy earlier today and he's scratching his head, so I'd thought I'd throw it open to you guys hoping someone has had the same problem and can save the rest of my hair from being pulled out.
HELP!

Hi Guys,
I know this is an old post but I need to bump it.
I work for a image processing company and we all sit on top spec mac pro's with 16-32 GB of RAM, top graphic cards and SSD drives.
All of my collegaues' computers are working fine when it comes to using liquify and all of the filters that come with CS5, but it sure doesn't work on my mac at all.
We have a tech guy who has re-installed the OSX on a new SSD drive now two times and we have started from scratch with installing CS5 but it still will not work. I keep getting "the operation could not be completed..." every time i try
to liquify or do any other filter work.
I am 100% sure it doesn't have to do with any disk permissions or broken drives in my case.
Could there be an issue with the graphic card or any other hardware component since it's clearly not a software related issue?
Any help would be much appreciated because we are very much in the dark here.
Best regards,
Anders

ERROR: SAP-System not installed properly. (TADIR HEAD SYST missing.)

Hi Experts I´m facing this issue.
This is tp version 340.16.41 (release 640)
HALT 20091029110915
ERROR: SAP-System not installed properly. (TADIR HEAD SYST missing.)
ERROR: EXIT(16) -> process ID is: 9660
tp returncode summary:
TOOLS: Highest return code of single steps was: 16
ERRORS: Highest tp internal error was: 0233
standard output from tp and from tools called by tp:
Any Clue?

Hi,
Was the system copied from another system? Or is this a new installation?
If yes, did you run SE06 after the installation?
What is the results of trans.log (generated from R3trans -d)?
Also paste the contents of table TADIR in SE16.
Best regards,
Warren

Destination R/3 System not mapped error

Similar Messages

Maybe you are looking for