IS ABAP FINISHED
HI TO ALL SDNERS,
I HAVE HEARD IN THE NEAR FUTURE SAP IS GOING TO COMPLETLY REPLACE ABAP WITH JAVA.DUE SAP's NETWEAVER push and SOA (service-oriented architecture) strategy .
IS THAT TRUE
I HAVE SPEND ENDLESS HOURS FOR LEARNING ABAP AND
ABAP OBJECTS WILL THAT BE A WASTE?
Abhishek Sarkar wrote:>
> But frankly speaking learning only ABAP is not going to take you anywhere. You have to do technof-unctional/Functional work soon or latter as you have already spend 2 years in ABAP. Only the person who also have buisness knowledge get importance in ERP field instead than a teche person. And if you gather good buisness knowledge then you will not be dependent on language.
>
> In software engineering language learning is a very insignificant. Even and not engineer can also learn in a specific language and can do efficient coding using some language. So better learn SAP technology or Buisness.
If every ABAPer after two years of ABAP experience moved away from programming, it wouldn't take long before there were no decent programmers left. One client I've worked for already found this an issue with their off-shore team - anyone who was any good moved out of programming or into management - result; no one available who could handle the really complex developments. On the plus side, those of us who are competent are assured work for years to come.
I've been programming ABAP at various levels for over ten years, and have been hearing rumours of ABAP's demise in all that time. It hasn't happened yet, and though I've widened my skill-set to cover the many components of Netweaver, I've still no plans to move out of being the technical area. If you're really worried - learn Java. The skill of programming is largely language independent. If you've mastered one, you can readily master another.
matt
Similar Messages
-
Trigger a waiting ABAP program from a User Exit of CO01
Hi all,
We would like to launch a ABAP program from a User Exit (EXIT_SAPLCOZV_001) of CO01, this ABAP program has a special characteristic: using Function Module RFC_PING_AND_WAIT, so this program will be existing until terminating event coming.
Our purpose is terminate CO01 normally before finishing of ABAP program. We don't know if it's possible?
Actually:
1. when we use SUBMIT ..., the process will stop CO01 (stop not normally) and then launch ABAP program. => This is not suitable for our purpose.
2. when we use SUBMIT ... and RETURN, CO01 will wait for finishing of ABAP program => This is not suitable for our purpose too, because we wish CO01 terminated normally when ABAP program is still existing and waiting for its terminating event.
Do you have a solution that is suitable for our purpose, could you please help us?
(The context is below:
Time: Begin-->CO finished> ABAP finished-->
Launch CO01 --> Call User Exit --> Call ABAP program for waiting --> CO01 saved normally.
> ABAP program still waiting ---> waiting for terminating event
Thanks a lot,
Vinh VoHi,
Try with the function module BP_EVENT_RAISE, it takes eventid, and eventparm as import parameters in the User exit.
1) With Eventid, you create a background job of the ABAP program and schedule it. Eventparm can be the Production order number.
2) So when ever the Event is triggered the FM gets triggered and which in turn run the ABAP program, so the foreground the CO01 transaction runs without waiting for the ABAP program to complete.
Regards
Bala Krishna -
I am trying to deploy 2 missing components in java. I am using the SDM and get the following errors below.
All other components worked fine
==========================================================================
Deployment started Wed Feb 06 16:11:58 GMT 2008
===========================================================================
Starting Deployment of caf/eu/cc/ddic
Deployment of caf/eu/cc/ddic finished successfully (Duration 6498 ms)
Starting Deployment of caf/eu/er/ddic
Deployment of caf/eu/er/ddic finished successfully (Duration 5451 ms)
Starting Deployment of caf/eu/es/api
The SDM will now stop SAP Web AS Java cluster instance(s) processes in order to perform offline deployment. After that the deployment will proceed.
It could take some time, so please be patient.
Deployment of caf/eu/es/api finished successfully (Duration 33394 ms)
Starting Deployment of caf/eu/es/conn/abap
Deployment of caf/eu/es/conn/abap finished successfully (Duration 5544 ms)
Starting Deployment of caf/eu/es/conn/google
Deployment of caf/eu/es/conn/google finished successfully (Duration 5123 ms)
Starting Deployment of caf/eu/es/ddic
Deployment of caf/eu/es/ddic finished successfully (Duration 5966 ms)
Starting Deployment of caf/eu/es/portal/toolarea
Deployment of caf/eu/es/portal/toolarea finished successfully (Duration 5341 ms)
Starting Deployment of caf/eu/gp/base
Deployment of caf/eu/gp/base finished successfully (Duration 5030 ms)
Starting Deployment of caf/eu/es/mse/service
Deployment of caf/eu/es/mse/service finished successfully (Duration 5342 ms)
Starting Deployment of caf/eu/es/conn/km
Deployment of caf/eu/es/conn/km finished successfully (Duration 5123 ms)
Starting Deployment of caf/eu/gp/lib/msdocumentserver
Deployment of caf/eu/gp/lib/msdocumentserver finished successfully (Duration 5404 ms)
Starting Deployment of caf/eu/gp/model/api
Deployment of caf/eu/gp/model/api finished successfully (Duration 5608 ms)
Starting Deployment of caf/eu/cc/api
Deployment of caf/eu/cc/api finished successfully (Duration 5108 ms)
Starting Deployment of caf/eu/er/base
Deployment of caf/eu/er/base finished successfully (Duration 5248 ms)
Starting Deployment of caf/eu/er/service/api
Deployment of caf/eu/er/service/api finished successfully (Duration 4936 ms)
Starting Deployment of caf/eu/er/service
Deployment of caf/eu/er/service finished successfully (Duration 5358 ms)
Starting Deployment of caf/eu/gp/api
Deployment of caf/eu/gp/api finished successfully (Duration 5311 ms)
Starting Deployment of caf/eu/gp/actions
Deployment of caf/eu/gp/actions finished successfully (Duration 5138 ms)
Starting Deployment of caf/eu/gp/example/train/bg
Deployment of caf/eu/gp/example/train/bg finished successfully (Duration 5154 ms)
Starting Deployment of caf/eu/gp/model
Deployment of caf/eu/gp/model finished successfully (Duration 7748 ms)
Starting Deployment of caf/eu/gp/model/ddic
Deployment of caf/eu/gp/model/ddic finished successfully (Duration 14135 ms)
Starting Deployment of caf/eu/gp/schedule
Deployment of caf/eu/gp/schedule finished successfully (Duration 5342 ms)
Starting Deployment of caf/eu/gp/schedule/ddic
Deployment of caf/eu/gp/schedule/ddic finished successfully (Duration 5123 ms)
Starting Deployment of caf/eu/gp/ui/render
Deployment of caf/eu/gp/ui/render finished successfully (Duration 4905 ms)
Starting Deployment of caf/eu/odi/mnuacc/api
Deployment of caf/eu/odi/mnuacc/api finished successfully (Duration 5124 ms)
Starting Deployment of caf/eu/odi/mnuacc
Deployment of caf/eu/odi/mnuacc finished successfully (Duration 5359 ms)
Starting Deployment of tc/eu/jwf/ui/wizsvc
Deployment of tc/eu/jwf/ui/wizsvc finished successfully (Duration 5359 ms)
Starting Deployment of caf/eu/cc/content/eap
The SDM will now start SAP Web AS Java instance processes in order to perform online deployment. After that the deployment will proceed.
It could take some time, so please be patient.
Deployment of caf/eu/cc/content/eap finished successfully (Duration 392520 ms)
Starting Deployment of caf/eu/cc/ui
Deployment of caf/eu/cc/ui finished successfully (Duration 7156 ms)
Starting Deployment of caf/eu/er/ui/rt
Finished with warnings: development component 'caf/eu/er/ui/rt'/'sap.com'/'MAIN_APL70P04_C'/'145296', grouped by :
Caught exception during application startup from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Error occurred while starting application sap.com/caf/eu/er/ui/rt and wait. Reason: Clusterwide exception: server ID 2842450:com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/cafeueruirt cannot be started. Reason: it has hard reference to resource com.sap.portal.ivs.connectorservice with type application, which is not active on the server.
at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:596)
at com.sap.engine.services.deploy.server.ReferenceResolver.processMakeReference(ReferenceResolver.java:399)
at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:328)
at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:178)
at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:147)
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:327)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:111)
at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:230)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4700)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4605)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4578)
at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
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(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception while starting: sap.com/com.sap.portal.ivs.connectorservice', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception while starting: sap.com/com.sap.portal.ivs.connectorservice
at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.prepareStart(PortalRuntimeContainer.java:527)
at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationLocalAndWait(DeployServiceImpl.java:4354)
at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:588)
... 21 more
Caused by: com.sap.engine.services.deploy.container.DeploymentException: <Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception while starting: SAPJ2EE::sap.com/cafeueruirt', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception while starting: SAPJ2EE::sap.com/cafeueruirt
at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getAndStartSAPJ2EEApplicationItem(SAPJ2EEPortalRuntime.java:886)
at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.prepareStart(PortalRuntimeContainer.java:511)
... 23 more
Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: [ExternalApplicationItem.prepare]: SAPJ2EE::sap.com/cafeueruirt
at com.sapportals.portal.prt.core.broker.ExternalApplicationItem.prepare(ExternalApplicationItem.java:188)
at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:232)
at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.start(SAPJ2EEApplicationItem.java:192)
at com.sapportals.portal.prt.service.sapj2ee.Mediator.getAndStartExternalApplication(Mediator.java:132)
at com.sap.portal.prt.sapj2ee.StartPortalApplication.coreRun(StartPortalApplication.java:59)
at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime.getAndStartSAPJ2EEApplicationItem(SAPJ2EEPortalRuntime.java:882)
... 24 more
Caused by: com.sapportals.portal.prt.core.broker.PortalApplicationNotFoundException: Could not find portal application com.sap.portal.ivs.connectorservice
at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:415)
at com.sapportals.portal.prt.core.broker.ExternalApplicationItem.prepare(ExternalApplicationItem.java:180)
... 29 more
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of caf/eu/er/ui/rt finished with Warning (Duration 6953 ms)
Starting Deployment of caf/eu/es/cafumcontent
Deployment of caf/eu/es/cafumcontent finished successfully (Duration 7000 ms)
Starting Deployment of caf/eu/es/portalcontent
Aborted: development component 'caf/eu/es/portalcontent'/'sap.com'/'MAIN_APL70P04_C'/'145031', grouped by software component 'SAP-EU'/'sap.com'/'MAIN_APL70P04_C'/'1000.7.00.4.1.20051007083632':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/cafeues~portalcontent.. Reason: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception during deploy: Could not find a portal deployment access for file type: .epa either the file type is unknown or the deployment access was not registered successfully.
com.sap.portal.prt.sapj2ee.deployment.PortalDeploymentException: Could not find a portal deployment access for file type: .epa either the file type is unknown or the deployment access was not registered successfully.
at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.deploy(PortalRuntimeContainer.java:159)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:319)
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception during deploy: Could not find a portal deployment access for file type: .epa either the file type is unknown or the deployment access was not registered successfully.
com.sap.portal.prt.sapj2ee.deployment.PortalDeploymentException: Could not find a portal deployment access for file type: .epa either the file type is unknown or the deployment access was not registered successfully.
at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.deploy(PortalRuntimeContainer.java:159)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:319)
; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: <--Localization failed: ResourceBundle='com.sap.engine.services.deploy.DeployResourceBundle', ID='Exception during deploy: Could not find a portal deployment access for file type: .epa either the file type is unknown or the deployment access was not registered successfully.
com.sap.portal.prt.sapj2ee.deployment.PortalDeploymentException: Could not find a portal deployment access for file type: .epa either the file type is unknown or the deployment access was not registered successfully.
at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.deploy(PortalRuntimeContainer.java:159)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:319)
', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Exception during deploy: Could not find a portal deployment access for file type: .epa either the file type is unknown or the deployment access was not registered successfully.
com.sap.portal.prt.sapj2ee.deployment.PortalDeploymentException: Could not find a portal deployment access for file type: .epa either the file type is unknown or the deployment access was not registered successfully.
at com.sap.portal.prt.sapj2ee.PortalRuntimeContainer.deploy(PortalRuntimeContainer.java:159)
at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:319)
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of caf/eu/es/portalcontent finished with Error (Duration 6171 ms)
Starting Deployment of SAP-EU
Aborted: software component 'SAP-EU'/'sap.com'/'MAIN_APL70P04_C'/'1000.7.00.4.1.20051007083632':
No further description found.
Deployment of SAP-EU finished with Error (Duration 5468 ms)Hi,
as you send the whole trace, I suppose you don't know which part is important?
That is this one:
Application sap.com/cafeueruirt cannot be started. Reason: it has hard reference to resource com.sap.portal.ivs.connectorservice with type application, which is not active on the server.
First tip: Search in manuals for an explanation of hard reference.
Then either get the missing thing there or change the reference.
Regards,
Benny -
Home-grown ABAP report sometimes hangs & sometimes finishes successfully
Dear All,
I am re-posting the below thread, which was previously posted on the : SAP on DB2 UDB for i5/OS (DB4) forum, maybe I will get a reply :
We are implementing SAP ECC 6.0 (ABAP stack) on IBM System i (iSeries), i5/OS V5R4, Kernel patch level 173
We have a home-grown ABAP report that sometimes finishes successfully and sometimes just hangs; i.e. through the OS/400 job monitoring, no change happens in the database records I/O counts.
Below is the OS/400 job log, related to a case where the report did not complete successfully (actually the below is an excerpt from the beginning and the end of the OS/400 job log)
I would highly appreciate any advise about the cause of this problem :
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 1
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
CPC2196 Completion 00 05/11/08 11:44:32.099024 QLICUSRL QSYS 0113 QXDAEDRS QSYS *STMT
To module . . . . . . . . . : QXDAEDRS
To procedure . . . . . . . : QxdaProcessCommandEDRS
Statement . . . . . . . . . : 325
Message . . . . : Library QGY added to library list.
Cause . . . . . : If the ADDLIBLE command was used, QGY was added to the
user library list. If the CHGSYSLIBL command was used, QGY was added to the
system portion of the library list.
CPC2198 Completion 00 05/11/08 11:44:32.099232 QLICHLLE QSYS 01A3 QXDAEDRS QSYS *STMT
To module . . . . . . . . . : QXDAEDRS
To procedure . . . . . . . : QxdaProcessCommandEDRS
Statement . . . . . . . . . : 325
Message . . . . : Current library changed to R3PRODATA.
Cause . . . . . : The current library in the library list was changed to
R3PRODATA.
*NONE Information 05/11/08 11:44:32.214488 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3PRO400/R3INLPGM: File Version: 7000, 173, 0, 0
*NONE Information 05/11/08 11:44:32.214640 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3PRO400/R3INLPGM: Product Version: 700, patch 173,
changelist 0
*NONE Information 05/11/08 11:44:32.214808 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3PRO400/R3INLPGM: Platform: os400 for releases OS400 3 5,
OS400 4 5, OS400 1 6
*NONE Information 05/11/08 11:44:32.214904 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3PRO400/R3INLPGM: Special Build Description: OPT (Aug 11
2008, 08:14:03) (ASCII in PASE ASCII build)
*NONE Information 05/11/08 11:44:32.230728 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 2
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3INLPGM: Connect from Client Protocol: 610
*NONE Information 05/11/08 11:44:32.230840 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3INLPGM: Remote Link: /usr/sap/PRO/SYS/exe/run/DBSLDB4RMT
*NONE Information 05/11/08 11:44:32.268688 R3INLPGM R3PRO400 *STMT R3INLPGM R3PRO400 *STMT
From module . . . . . . . . : O4TMKLIBI
From procedure . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
To module . . . . . . . . . : O4TMKLIBI
To procedure . . . . . . . : prtjoblA
Statement . . . . . . . . . : 15
Message . . . . : R3INLPGM: Kernel Library: SAPPROUCN
CPF9897 Completion 40 05/11/08 11:44:32.286120 QDBENCWT QSYS 0066 DBSLENCWT SAPPROUCN *STMT
To module . . . . . . . . . : DBSLENCWT
To procedure . . . . . . . : main
Statement . . . . . . . . . : 14
Message . . . . : CONCURRENT WRITE IS ENABLED.
Cause . . . . . : No additional online help information is available.
CPF9897 Completion 40 05/11/08 11:44:32.286136 QDBENCWT QSYS 0066 DBSLENCWT SAPPROUCN *STMT
To module . . . . . . . . . : DBSLENCWT
To procedure . . . . . . . : main
Statement . . . . . . . . . : 14
Message . . . . : CONCURRENT WRITE WILL BE ENABLED NEXT IPL.
Cause . . . . . : No additional online help information is available.
CPC2197 Completion 00 05/11/08 11:44:32.323144 QLICHLBL QSYS 013C QXDAEDRS QSYS *STMT
To module . . . . . . . . . : QXDAEDRS
To procedure . . . . . . . : QxdaProcessCommandEDRS
Statement . . . . . . . . . : 325
Message . . . . : Library SAPPROUCN removed from library list.
Cause . . . . . : If the RMVLIBLE command was used, SAPPROUCN was removed
from the user library list. If the CHGSYSLIBL command was used, SAPPROUCN
was removed from the system portion of the library list.
CPC2196 Completion 00 05/11/08 11:44:32.323368 QLICUSRL QSYS 0113 QXDAEDRS QSYS *STMT
To module . . . . . . . . . : QXDAEDRS
To procedure . . . . . . . : QxdaProcessCommandEDRS
Statement . . . . . . . . . : 325
Message . . . . : Library SAPPROUCN added to library list.
Cause . . . . . : If the ADDLIBLE command was used, SAPPROUCN was added to
the user library list. If the CHGSYSLIBL command was used, SAPPROUCN was
added to the system portion of the library list.
SAP4000 Information 00 05/11/08 11:44:32.336544 DBSLDB4RMT SAPPROUCN *STMT DBSLDB4RMT SAPPROUCN *STMT
From module . . . . . . . . : O4SAPUCI_E
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 3
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
From procedure . . . . . . : O4_QMHSNDPM__FPCcN21iN21T4PUcR11O4_ERRC0100
Statement . . . . . . . . . : 4
To module . . . . . . . . . : DBSLDB4RMT
To procedure . . . . . . . : CXXPEP__Fv
Statement . . . . . . . . . : *N
Message . . . . : Connect from workprocess w2 on MASAPPRO_PRO_00
CPC2196 Completion 00 05/11/08 11:44:32.975448 QLICHLBL QSYS 013C CHGR3SYSLE SAPPROUCN *STMT
To module . . . . . . . . . : CHGR3SYSLE
To procedure . . . . . . . : CHGR3SYSLE
Statement . . . . . . . . . : 13600
Message . . . . : Library R3SYS added to library list.
Cause . . . . . : If the ADDLIBLE command was used, R3SYS was added to the
user library list. If the CHGSYSLIBL command was used, R3SYS was added to
the system portion of the library list.
SQL7917 Information 00 05/11/08 11:47:23.199272 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : OPQRYDBM
Statement . . . . . . . . . : 16590
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
CPF9898 Information 40 05/11/08 11:54:11.399680 QXDAUTIL QSYS *STMT QXDAEDRS QSYS *STMT
From module . . . . . . . . : QXDATRACE
From procedure . . . . . . : QxdaWriteJoblog__FPciT1R16QxdaTraceControl
Statement . . . . . . . . . : 13
To module . . . . . . . . . : QXDAEDRS
To procedure . . . . . . . : QxdaConnectEDRSInternal__FPvPcT1PiT2T1R16clean
upMutexes_tP19XDAGlobalDataStruct
Statement . . . . . . . . . : 3266
Message . . . . : Connection #2, Server Job: 303463/QUSER/QXDARECVR.
Cause . . . . . : This message is used by application programs as a general
escape message.
CPF5009 Diagnostic 10 05/11/08 11:54:32.741480 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 22987
Message . . . . : Duplicate record key in member RSEUINC.
Cause . . . . . : The output or update operation to member number 1 record
number 4942 format RSEUINC, for member RSEUINC file RSEUINC in library
R3PRODATA, failed. Member number 1 record number 4941 format RSEUINC has the
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 4
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
same record key as member number 1 record number 4942 format RSEUINC. If
the record number is zero, the duplicate record key occurred on an output
operation. Recovery . . . : Change either record key so that the keys are
unique. Then try your request again.
CPF5034 Sender copy 30 05/11/08 11:54:32.741536 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 4942 record
format FORMAT0001 member number 1 failed because of a duplicate key in a
unique keyed member that is based on member RSEUINC file RSEUINC in library
R3PRODATA, or in a based-on member of RSEUINC. The failure could also have
been caused by an output or update operation done to another file by a
trigger program associated with file RSEUINC in library R3PRODATA. Recovery
. . . : See previously listed message CPF5009 to identify the file and
record with the duplicate key and change the key value so that it is unique.
Note that the file could be a file operated on by a trigger program. Then
try your request again. Possible choices for replying to message . . . . . .
. . . . . . . . . : C -- The request is canceled. I -- The request is
ignored.
CPF5034 Notify 30 05/11/08 11:54:32.741552 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 22987
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 4942 record
format FORMAT0001 member number 1 failed because of a duplicate key in a
unique keyed member that is based on member RSEUINC file RSEUINC in library
R3PRODATA, or in a based-on member of RSEUINC. The failure could also have
been caused by an output or update operation done to another file by a
trigger program associated with file RSEUINC in library R3PRODATA. Recovery
. . . : See previously listed message CPF5009 to identify the file and
record with the duplicate key and change the key value so that it is unique.
Note that the file could be a file operated on by a trigger program. Then
try your request again. Possible choices for replying to message . . . . . .
. . . . . . . . . : C -- The request is canceled. I -- The request is
ignored.
SQL0803 Diagnostic 30 05/11/08 11:54:32.748064 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint RSEUINC in R3PRODATA exists over one or
more columns of table RSEUINC in R3PRODATA. The operation cannot be
performed because one or more values would have produced a duplicate key in
the unique index or constraint. Recovery . . . : Change the statement so
that duplicate keys are not produced. For information on what rows contain
the duplicate key values, look at the previously listed messages in the job
log (DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 5
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
SQL7917 Information 00 05/11/08 12:33:54.649416 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : STORE_ACCPLN
Statement . . . . . . . . . : 19339
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
SQL7917 Information 00 05/11/08 12:33:54.709808 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : STORE_ACCPLN
Statement . . . . . . . . . : 19339
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
SQL7917 Information 00 05/11/08 12:33:54.745288 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : STORE_ACCPLN
Statement . . . . . . . . . : 19339
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 6
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
SQL7917 Information 00 05/11/08 12:34:28.245160 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : OPQRYDBM
Statement . . . . . . . . . : 16643
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
SQL7917 Information 00 05/11/08 12:49:06.875752 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : STORE_ACCPLN
Statement . . . . . . . . . : 19339
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
SQL7917 Information 00 05/11/08 12:49:06.935840 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : STORE_ACCPLN
Statement . . . . . . . . . : 19339
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 7
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
SQL7917 Information 00 05/11/08 12:49:06.965560 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : STORE_ACCPLN
Statement . . . . . . . . . : 19339
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
CPF9898 Information 40 05/11/08 12:50:51.470216 QXDAUTIL QSYS *STMT QXDAEDRS QSYS *STMT
From module . . . . . . . . : QXDATRACE
From procedure . . . . . . : QxdaWriteJoblog__FPciT1R16QxdaTraceControl
Statement . . . . . . . . . : 13
To module . . . . . . . . . : QXDAEDRS
To procedure . . . . . . . : QxdaConnectEDRSInternal__FPvPcT1PiT2T1R16clean
upMutexes_tP19XDAGlobalDataStruct
Statement . . . . . . . . . : 3266
Message . . . . : Connection #2, Server Job: 303480/QUSER/QXDARECVR.
Cause . . . . . : This message is used by application programs as a general
escape message.
SQL7917 Information 00 05/11/08 12:59:55.956784 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQOPEN
From procedure . . . . . . : SNDINFOMSG
Statement . . . . . . . . . : 24269
To module . . . . . . . . . : QSQOPEN
To procedure . . . . . . . : OPQRYDBM
Statement . . . . . . . . . : 16590
Message . . . . : Access plan not updated.
Cause . . . . . : The query optimizer rebuilt the access plan for this
statement, but the program could not be updated. Another job may be running
the program. The program cannot be updated with the new access plan until a
job can obtain an exclusive lock on the program. The exclusive lock cannot
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 8
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
be obtained if another job is running the program, if the job does not have
proper authority to the program, or if the program is currently being saved.
The query will still run, but access plan rebuilds will continue to occur
until the program is updated. Recovery . . . : See previous messages from
the query optimizer to determine why the access plan has been rebuilt. To
ensure that the program gets updated with the new access plan, run the
program when no other active jobs are using it.
CPC2206 Completion 00 05/11/08 13:06:49.865608 QSYCHONR QSYS 0665 QLIINSRT QSYS 0453
Message . . . . : Ownership of object SAPFGUTRBL in R3PRO02070 type *SQLPKG
changed.
Cause . . . . . : The ownership of object SAPFGUTRBL in library R3PRO02070
type *SQLPKG has changed.
CPC2206 Completion 00 05/11/08 13:06:50.312272 QSYCHONR QSYS 0665 QSQXPGM QSYS 0469
Message . . . . : Ownership of object SAPFGUTRBL in R3PRO02070 type *SQLPKG
changed.
Cause . . . . . : The ownership of object SAPFGUTRBL in library R3PRO02070
type *SQLPKG has changed.
SQL0204 Diagnostic 30 05/11/08 13:06:51.011064 QSQPRCED QSYS *STMT QSQPRCED QSYS *STMT
From module . . . . . . . . : QSQPRCED
From procedure . . . . . . : SENDDIAG
Statement . . . . . . . . . : 19346
To module . . . . . . . . . : QSQPRCED
To procedure . . . . . . . : QSQPRCED
Statement . . . . . . . . . : 18435
Message . . . . : T801WEI in R3PRO32060 type *SQLPKG not found.
Cause . . . . . : T801WEI in R3PRO32060 type *SQLPKG was not found. If the
member name is *ALL, the table is not partitioned. If this is an ALTER TABLE
statement and the type is *N, a constraint or partition was not found. If
this is not an ALTER TABLE statement and the type is *N, a function,
procedure, trigger or sequence object was not found. If a function was not
found, T801WEI is the service program that contains the function. The
function will not be found unless the external name and usage name match
exactly. Examine the job log for a message that gives more details on which
function name is being searched for and the name that did not match.
Recovery . . . : Change the name and try the request again. If the
object is a node group, ensure that the DB2 Multisystem product is installed
on your system and create a nodegroup with the CRTNODGRP CL command. If an
external function was not found, be sure that the case of the EXTERNAL NAME
on the CREATE FUNCTION statement exactly matches the case of the name
exported by the service program.
CPC2206 Completion 00 05/11/08 13:06:51.378408 QSYCHONR QSYS 0665 QLIINSRT QSYS 0453
Message . . . . : Ownership of object T801WEI in R3PRO32060 type *SQLPKG
changed.
Cause . . . . . : The ownership of object T801WEI in library R3PRO32060 type
*SQLPKG has changed.
CPC2206 Completion 00 05/11/08 13:06:51.439824 QSYCHONR QSYS 0665 QSQXPGM QSYS 0469
Message . . . . : Ownership of object T801WEI in R3PRO32060 type *SQLPKG
changed.
Cause . . . . . : The ownership of object T801WEI in library R3PRO32060 type
*SQLPKG has changed.
CPF5009 Diagnostic 10 05/11/08 13:06:51.708688 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 9
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member T801W.
Cause . . . . . : The output or update operation to member number 1 record
number 0 format T801W, for member T801W file T801W in library R3PRODATA,
failed. Member number 1 record number 751 format T801W has the same record
key as member number 1 record number 0 format T801W. If the record number
is zero, the duplicate record key occurred on an output operation. Recovery
. . . : Change either record key so that the keys are unique. Then try
your request again.
CPF5034 Sender copy 30 05/11/08 13:06:51.708736 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 0 record
format FORMAT0001 member number 1 failed because of a duplicate key in a
unique keyed member that is based on member T801W file T801W in library
R3PRODATA, or in a based-on member of T801W. The failure could also have
been caused by an output or update operation done to another file by a
trigger program associated with file T801W in library R3PRODATA. Recovery .
. . : See previously listed message CPF5009 to identify the file and
record with the duplicate key and change the key value so that it is unique.
Note that the file could be a file operated on by a trigger program. Then
try your request again. Possible choices for replying to message . . . . . .
. . . . . . . . . : C -- The request is canceled. I -- The request is
ignored.
CPF5034 Notify 30 05/11/08 13:06:51.708776 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 0 record
format FORMAT0001 member number 1 failed because of a duplicate key in a
unique keyed member that is based on member T801W file T801W in library
R3PRODATA, or in a based-on member of T801W. The failure could also have
been caused by an output or update operation done to another file by a
trigger program associated with file T801W in library R3PRODATA. Recovery .
. . : See previously listed message CPF5009 to identify the file and
record with the duplicate key and change the key value so that it is unique.
Note that the file could be a file operated on by a trigger program. Then
try your request again. Possible choices for replying to message . . . . . .
. . . . . . . . . : C -- The request is canceled. I -- The request is
ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:51.710352 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint T801W in R3PRODATA exists over one or more
columns of table T801W in R3PRODATA. The operation cannot be performed
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 10
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
SQL0518 Diagnostic 30 05/11/08 13:06:51.732720 QSQROUTS QSYS *STMT QSQROUTS QSYS *STMT
From module . . . . . . . . : QSQCLNUP
From procedure . . . . . . : SQROUTE_CLEANUP
Statement . . . . . . . . . : 3814
To module . . . . . . . . . : QSQCLNUP
To procedure . . . . . . . : SQROUTE_CLEANUP
Statement . . . . . . . . . : 3814
Message . . . . : Prepared statement RD0IAAAABA not found.
Cause . . . . . : An EXECUTE statement referred to the statement RD0IAAAABA.
RD0IAAAABA is not a valid prepared statement. The statement has one of the
following conditions: -- The statement has never been prepared. -- The
statement identifies a prepared SELECT or DECLARE PROCEDURE statement. --
The statement was in error at prepare or bind time. -- The statement was
prepared in another program or another call of this program and the program
was created with CLOSQLCSR(*ENDPGM). -- The statement was prepared in
another module or another call of this module and the module was created
with CLOSQLCSR(*ENDMOD). -- The statement was prepared in another call of
this program and programs which have run SQL statements have ended and the
program was created with CLOSQLCSR(*ENDSQL). -- The statement was prepared
in another call of this module and the activation group ended between calls.
The module was created with CLOSQLCSR(*ENDACTGRP). -- The prepared statement
was destroyed by a COMMIT or ROLLBACK statement. This only occurs when
connected to a database other than DB2 UDB for iSeries. Recovery . . . :
Do one of the following: -- If RD0IAAAABA identifies a prepared SELECT or
DECLARE PROCEDURE statement, a different prepared statement must be named in
the EXECUTE statement. -- If the statement had errors, correct the errors
and either prepare the statement again or precompile the program again. --
Make certain that RD0IAAAABA has been prepared in the same program or module
call prior to using the EXECUTE statement or specify either
CLOSQLCSR(ENDSQL), CLOSQLCSR(ENDJOB), or CLOSQLCSR(*ENDACTGRP) when
precompiling the application. -- If the statement was deleted by a COMMIT or
ROLLBACK, either specify PREPARE WITH HOLD or bind the program with the
correct option to preserve prepared statements.
CPF5009 Diagnostic 10 05/11/08 13:06:56.094184 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member ATAB.
Cause . . . . . : The output or update operation to member number 1 record
number 644685 format ATAB, for member ATAB file ATAB in library R3PRODATA,
failed. Member number 1 record number 635738 format ATAB has the same record
key as member number 1 record number 644685 format ATAB. If the record
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 51
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
number is zero, the duplicate record key occurred on an output operation.
Recovery . . . : Change either record key so that the keys are unique.
Then try your request again.
CPF5034 Sender copy 30 05/11/08 13:06:56.094240 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF5034 Notify 30 05/11/08 13:06:56.094256 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:56.094376 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint ATAB in R3PRODATA exists over one or more
columns of table ATAB in R3PRODATA. The operation cannot be performed
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
CPF5009 Diagnostic 10 05/11/08 13:06:56.096008 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 52
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member ATAB.
Cause . . . . . : The output or update operation to member number 1 record
number 644685 format ATAB, for member ATAB file ATAB in library R3PRODATA,
failed. Member number 1 record number 635779 format ATAB has the same record
key as member number 1 record number 644685 format ATAB. If the record
number is zero, the duplicate record key occurred on an output operation.
Recovery . . . : Change either record key so that the keys are unique.
Then try your request again.
CPF5034 Sender copy 30 05/11/08 13:06:56.096048 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF5034 Notify 30 05/11/08 13:06:56.096080 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:56.096208 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint ATAB in R3PRODATA exists over one or more
columns of table ATAB in R3PRODATA. The operation cannot be performed
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 53
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
CPF5009 Diagnostic 10 05/11/08 13:06:56.098520 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member ATAB.
Cause . . . . . : The output or update operation to member number 1 record
number 644685 format ATAB, for member ATAB file ATAB in library R3PRODATA,
failed. Member number 1 record number 635819 format ATAB has the same record
key as member number 1 record number 644685 format ATAB. If the record
number is zero, the duplicate record key occurred on an output operation.
Recovery . . . : Change either record key so that the keys are unique.
Then try your request again.
CPF5034 Sender copy 30 05/11/08 13:06:56.098552 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF5034 Notify 30 05/11/08 13:06:56.098568 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:56.098720 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 54
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint ATAB in R3PRODATA exists over one or more
columns of table ATAB in R3PRODATA. The operation cannot be performed
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
CPF5009 Diagnostic 10 05/11/08 13:06:56.101560 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member ATAB.
Cause . . . . . : The output or update operation to member number 1 record
number 644685 format ATAB, for member ATAB file ATAB in library R3PRODATA,
failed. Member number 1 record number 635865 format ATAB has the same record
key as member number 1 record number 644685 format ATAB. If the record
number is zero, the duplicate record key occurred on an output operation.
Recovery . . . : Change either record key so that the keys are unique.
Then try your request again.
CPF5034 Sender copy 30 05/11/08 13:06:56.101592 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF5034 Notify 30 05/11/08 13:06:56.101608 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:56.101760 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 55
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint ATAB in R3PRODATA exists over one or more
columns of table ATAB in R3PRODATA. The operation cannot be performed
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
CPF5009 Diagnostic 10 05/11/08 13:06:56.105864 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member ATAB.
Cause . . . . . : The output or update operation to member number 1 record
number 644685 format ATAB, for member ATAB file ATAB in library R3PRODATA,
failed. Member number 1 record number 635906 format ATAB has the same record
key as member number 1 record number 644685 format ATAB. If the record
number is zero, the duplicate record key occurred on an output operation.
Recovery . . . : Change either record key so that the keys are unique.
Then try your request again.
CPF5034 Sender copy 30 05/11/08 13:06:56.105904 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF5034 Notify 30 05/11/08 13:06:56.105920 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 56
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:56.106056 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint ATAB in R3PRODATA exists over one or more
columns of table ATAB in R3PRODATA. The operation cannot be performed
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
CPF5009 Diagnostic 10 05/11/08 13:06:56.107696 QDBSIGEX QSYS 0D60 QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate record key in member ATAB.
Cause . . . . . : The output or update operation to member number 1 record
number 644685 format ATAB, for member ATAB file ATAB in library R3PRODATA,
failed. Member number 1 record number 635948 format ATAB has the same record
key as member number 1 record number 644685 format ATAB. If the record
number is zero, the duplicate record key occurred on an output operation.
Recovery . . . : Change either record key so that the keys are unique.
Then try your request again.
CPF5034 Sender copy 30 05/11/08 13:06:56.107736 QDBSIGEX QSYS 01EA QDBSIGEX QSYS 01EA
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
CPF5034 Notify 30 05/11/08 13:06:56.107752 QDBSIGEX QSYS 01EA QSQRUN3 QSYS *STMT
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : SQL_Insert
Statement . . . . . . . . . : 10309
Message . . . . : Duplicate key on access path.
Cause . . . . . : An output or update operation on record number 644685
5722SS1 V5R4M0 060210 Display Job Log MASAPPRO 05/11/08 14:49:22 Page 57
Job name . . . . . . . . . . : WP02 User . . . . . . : PRO00 Number . . . . . . . . . . . : 303461
Job description . . . . . . : R3_00 Library . . . . . : R3PRO400
MSGID TYPE SEV DATE TIME FROM PGM LIBRARY INST TO PGM LIBRARY INST
record format FORMAT0001 member number 1 failed because of a duplicate key
in a unique keyed member that is based on member ATAB file ATAB in library
R3PRODATA, or in a based-on member of ATAB. The failure could also have been
caused by an output or update operation done to another file by a trigger
program associated with file ATAB in library R3PRODATA. Recovery . . . :
See previously listed message CPF5009 to identify the file and record with
the duplicate key and change the key value so that it is unique. Note that
the file could be a file operated on by a trigger program. Then try your
request again. Possible choices for replying to message . . . . . . . . . .
. . . . . : C -- The request is canceled. I -- The request is ignored.
SQL0803 Diagnostic 30 05/11/08 13:06:56.107880 QSQRUN3 QSYS *STMT QSQRUN3 QSYS *STMT
From module . . . . . . . . : QSQINS
From procedure . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
To module . . . . . . . . . : QSQINS
To procedure . . . . . . . : CLEANUP
Statement . . . . . . . . . : 24031
Message . . . . : Duplicate key value specified.
Cause . . . . . : An INSERT, UPDATE or ALTER TABLE statement was issued.
Unique index or unique constraint ATAB in R3PRODATA exists over one or more
columns of table ATAB in R3PRODATA. The operation cannot be performed
because one or more values would have produced a duplicate key in the unique
index or constraint. Recovery . . . : Change the statement so that
duplicate keys are not produced. For information on what rows contain the
duplicate key values, look at the previously listed messages in the job log
(DSPJOBLOG command) or press F10 (Display messages in job log) on this
display.
SQL0204 Diagnostic 30 05/11/08 13:06:56.159320 QSQPRCED QSYS *STMT QSQPRCED QSYS *STMT
From module . . . . . . . . : QSQPRCED
From procedure . . . . . . : SENDDIAG
Statement . . . . . . . . . : 19346
To module . . . . . . . . . : QSQPRCED
To procedure . . . . . . . : QSQPRCED
Statement . . . . . . . . . : 18435
Message . . . . : T801LEI in R3PRO32060 type *SQLPKG not found.
Cause . . . . . : T801LEI in R3PRO32060 type *SQLPKG was not found. If the
member name is *ALL, the table is not partitioned. If this is an ALTER TABLE
statement and tI don't have FIOS but I do use Safari to access the discussion forums without encountering the issue you've described (knock on wood). It's always hard to diagnose and troubleshoot connection issues without actually sitting in front of the computer (even more so when the problem is intermittent). Let me ask some questions:
Is your computer connecting wirelessly?
Have you tried resetting Safari and/or emptying the cache?
Have you tried Private Browsing to note any differences?
How about going to Safari's->Preferences->Security and checking/unchecking Web Contents and/or enabling/disabling cookies?
Have you tried creating another user account on your machine and log in with that user account to access the discussion board to see if there's a difference?
Good luck,
TK -
How to finish ABAP program in the process chains
Hello All,
we have one ABAP program in the process chains which was created in the BW system only.
this program we are using in the synchronous mode. according to my understanding we can not capture the failure of the ABAP program when it is in the synchronous mode.
but i found a way through one this forum topic to capture the failure of the program through asynchrous mode by calling a function module RSPC_ABAP_FINISH but it was with the R/3 program in BW.
can we use the same function module for BW program also.
kindly let me know what steps we need to follow for the BW program in the process chains to capture the failure status.
Regards,
Ala.Hi Ala,
we created an own processtype, look at this HowTo: https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/45d8a990-0201-0010-a290-f22083728179
and than also an abap which can end red or green:
PARAMETERS: red RADIOBUTTON GROUP radi,
green RADIOBUTTON GROUP radi.
IF NOT green IS INITIAL.
MESSAGE i162(00) WITH 'Status' 'Green'.
ELSE.
MESSAGE e162(00) WITH 'Status' 'Red'.
ENDIF.
with i-message process ends green, with e-message process ends red.
/manfred -
Error while installing J2EE Add- In to the ABAP system
Error while installing J2EE Add-In to the ABAP system
We are installing J2EE Add-In to the ECC5 System in the new hardware.
When are getting Error while installing J2EE Add-In to the ABAP system.
Transaction Begin*****************************
ERROR 2005-08-10 14:58:28
CJSlibModule::writeLogEntry()
CJS-20011 J2EE engine configuration error. DIAGNOSIS: Error when
configuring J2EE Engine. See output of
logfile /usr/sap/QSS/install/batchconfig.log: 'My Library Path
is: /usr/j2se/jre/lib/sparcv9/server:/usr/j2se/jre/lib/sparcv9:/usr/j2se/jre/../lib/sparcv9:/tmp/sapinst_exe.13084.1123702275:/usr/lib::/usr/openwin/lib:/usr/sap/QSS/SYS/exe/run:/oracle/QSS/920_64/lib:/oracle/QSS/920_64/lib32:/usr/lib
ElementInfoTask has finished successfully on dispatcher
ConsoleLogsTask has finished successfully on dispatcher
ChangeManagerPropsTask has finished successfully. Manager:
LockingManager on dispatcher
ChangeManagerPropsTask has finished successfully. Manager:
ClusterManager on dispatcher
ElementInfoTask has finished successfully on server
ConsoleLogsTask has finished successfully on server
ChangeManagerPropsTask has finished successfully. Manager:
LockingManager on server
ChangeManagerPropsTask has finished successfully. Manager:
ClusterManager on server
ChangeServicePropsTask has finished successfully. Service: dbpool on
server
ChangePasswordsTask finished successfully.
Error occured while connecting to database (UploadFile). Msg: No such
algorithm: DESede
Transaction end***********************************
We tried twice clean installation, after removing j2ee dir, SCS and
resp profiles and droping PSAPQSSDB tablespace and SAPQSSDB user.
I have also confirmed the passwords in ABAP system/000 for SAPJSF, DDIC, J2EE_ADMIN, J2EE_GUEST.
We are getting the same error in both tries.
Kindly advice us to resolve the problem.
Thanks and Regards,
SrinivasAnanda,
you saved my day! I've been banging my head against the wall with this same problem during a J2EE add-in installation for SRM 4.0 on Windows, in preparation of an LAC 2.0 installation. I had tried deleting the schema first, but that didn't work. After I removed the sys\global\security folder as well, it worked perfectly.
Thank you. -
Consuming a webservice in ABAP ECC 6.0 without using XI/ PI
Hi Experts,
I wanted to consume an external webservice without using XI / PI.After doing my homework and search on sdn I came to know that we can consume webservices in ABAP using proxies using SE80(Enterprise Services).
I am trying to create a client proxy with the URL of webservice.It asks me the option to choose between URL or HTTP.
I am selecting URL and in the second screen it asks about the package details and after that it finishes.Later I get an error message stating "NO VENDOR SPECIFIED".Its not allowing me to create a proxy.
So, here are my questions.
Does anyone faced the same kind of problem?
Can we really consume a webservice without using XI / PI or any other middleware?
Is it possible to consume the webservice only with URL or WSDL file ?
Please let me know the exact process.
Thanks in Advance.
Shanker Pandey.Hi Martin,
Please check these following links. Though you have reported already, these may help
Proxy Object generation error using Wizard for Web Service Consumption
Also, please have a look @ /people/thomas.jung/blog/2006/03/13/develop-a-web-service-that-sends-an-email--in-abap-netweaver-04s
Hope this helps,
Karthik -
Hi SDN Team,
We are in the proceess of EHP4 upgrade,now we are at the road map configuration where we got stuck,I is looking for JAVA sca files in XML file but could not found the same and it throw an error,
Trouble Ticket Log
===============
Trouble Ticket Report
Installation of enhancement package 1 for SAP NetWeaver 7.0
SID................: SE1
Hostname...........: NA00SAPSAND02
Install directory..: g:/usr/sap/SE1
Upgrade directory..: G:\EHPI\EHPI\java
Database...........: Microsoft SQL Server
Operating System...: NT
JDK version........: 1.6.0_07 SAP AG
SAPJup version.....: 3.4.29
Source release.....: 700
Target release.....: 700
Start release SP...: $(/J2EE/StandardSystem/SPLevel)
Target release SP..: $(/J2EE/ShadowSystem/SPLevel)
Current usages.....:
ABAP stack present.: true
The execution of PREPARE/INIT/PREPARE_JSPM_QUEUE ended in error.
The stack T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml contains no components for this system.
More information can be found in the log file G:\EHPI\EHPI\java\log\PREPARE_JSPM_QUEUE_CSZ_02.LOG.
Use the information provided to trouble-shoot the problem. There might be an OSS note providing a solution to this problem. Search for OSS notes with the following search terms:
com.sap.sdt.j2ee.phases.PhaseTypePrepareJSPMQueue
com.sap.sdt.ucp.phases.PhaseException
The stack T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml contains no components for this system.
PREPARE_JSPM_QUEUE
INIT
NetWeaver Enhancement Package Installation
SAPJup
Java Enhancement Package Installation
We have added the system in SMSY and download the stack properly and I could see SCA files listed in XML file but still iam stuck the above error
PREPARE_JSPM_QUEUE_CSZ_02
===========================
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[2.0.7.1006]/>
<!NAME[G:\EHPI\EHPI\java\log\PREPARE_JSPM_QUEUE_CSZ_02.LOG]/>
<!PATTERN[PREPARE_JSPM_QUEUE_CSZ_02.LOG]/>
<!FORMATTER[com.sap.tc.logging.TraceFormatter(%d [%s]: %-100l [%t]: %m)]/>
<!ENCODING[UTF8]/>
<!LOGHEADER[END]/>
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:754) [Thread[main,5,main]]: Phase PREPARE/INIT/PREPARE_JSPM_QUEUE has been started.
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:755) [Thread[main,5,main]]: Phase type is com.sap.sdt.j2ee.phases.PhaseTypePrepareJSPMQueue.
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:409) [Thread[main,5,main]]: Parameter inputFile=EHPComponents.xml
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMQueuePreparatorFactory.createJSPMQueuePreparator(JSPMQueuePreparatorFactory.java:93) [Thread[main,5,main]]: Creating JSPM SP Stack queue preparator.
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.ucp.dialog.elim.DialogEliminatorContainer.canBeOmitted(DialogEliminatorContainer.java:96) [Thread[main,5,main]]: Dialog eliminator spStackDialogEliminator allows to omit dialog SPStackLocationDialog
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:97) [Thread[main,5,main]]: Validatable parameter SP/STACK/LOCATION has been validated by validator RequiredFields.
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.util.validate.ValidationProcessor.validate(ValidationProcessor.java:97) [Thread[main,5,main]]: Validatable parameter SP/STACK/LOCATION has been validated by validator SPStackLocationValidator.
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.createQueue(JSPMSpStackQueuePreparator.java:107) [Thread[main,5,main]]: Using SP Stack T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml.
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:488) [Thread[main,5,main]]: STACK-SHORT-NAME tag is missing. The CAPTION of the stack will be used as stack name.
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseStackTag(SPXmlParser.java:582) [Thread[main,5,main]]: PRODUCT-PPMS-NAME tag is missing. The CAPTION of the product will be used as product PPMS name.
Jul 27, 2010 3:48:22 AM [Warning]: com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:730) [Thread[main,5,main]]: Software feature EHP4 FOR SAP ERP 6.0 / NW7.01 : SAP Learning Sol-Frontend CP - 05 (11/2009) found in stack definition file T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml is applicable for system SID: ZSE and HOST: na00sapsand02, but the current system is SID: SE1 and HOST: NA00SAPSAND02. This software feature will be skipped.
Jul 27, 2010 3:48:22 AM [Warning]: com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:730) [Thread[main,5,main]]: Software feature EHP4 FOR SAP ERP 6.0 / NW7.01 : SAP NW - Applic. Server Java - 05 (11/2009) found in stack definition file T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml is applicable for system SID: ZSE and HOST: na00sapsand02, but the current system is SID: SE1 and HOST: NA00SAPSAND02. This software feature will be skipped.
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSPXml(SPXmlParser.java:424) [Thread[main,5,main]]: Parsing of stack definition file T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml has finished.
Jul 27, 2010 3:48:22 AM [Error]: com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception has occurred during the execution of the phase.
Jul 27, 2010 3:48:22 AM [Error]: com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.createQueue(JSPMSpStackQueuePreparator.java:136) [Thread[main,5,main]]: The stack T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml contains no components for this system.
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:906) [Thread[main,5,main]]: Phase PREPARE/INIT/PREPARE_JSPM_QUEUE has been completed.
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:907) [Thread[main,5,main]]: Start time: 2010/07/27 03:48:22.
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:909) [Thread[main,5,main]]: End time: 2010/07/27 03:48:22.
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:910) [Thread[main,5,main]]: Duration: 0:00:00.141.
Jul 27, 2010 3:48:22 AM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:911) [Thread[main,5,main]]: Phase status is error.
Not sure what to do now.please advise.
Regards
UdayHi Uday,
> Jul 27, 2010 3:48:22 AM [Warning]: >com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:730) >[Thread[main,5,main]]: Software feature EHP4 FOR SAP ERP 6.0 / NW7.01 : SAP Learning Sol-Frontend CP - 05 (11/2009) >found in stack definition file T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml is applicable for >system SID: ZSE and HOST: na00sapsand02, but the current system is SID: SE1 and HOST: NA00SAPSAND02. This >software feature will be skipped.
> Jul 27, 2010 3:48:22 AM [Warning]: >com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSoftwareFeatureStackTag(SPXmlParser.java:730) >[Thread[main,5,main]]: Software feature EHP4 FOR SAP ERP 6.0 / NW7.01 : SAP NW - Applic. Server Java - 05 (11/2009) >found in stack definition file T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml is applicable for >system SID: ZSE and HOST: na00sapsand02, but the current system is SID: SE1 and HOST: NA00SAPSAND02. This >software feature will be skipped.
> Jul 27, 2010 3:48:22 AM [Info]: >com.sap.sdt.j2ee.tools.spxmlparser.SPXmlParser.parseSPXml(SPXmlParser.java:424) [Thread[main,5,main]]: Parsing of >stack definition file T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml has finished.
> Jul 27, 2010 3:48:22 AM [Error]: >com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:863) [Thread[main,5,main]]: Exception >has occurred during the execution of the phase.
> Jul 27, 2010 3:48:22 AM [Error]: >com.sap.sdt.j2ee.phases.jspm.JSPMSpStackQueuePreparator.createQueue(JSPMSpStackQueuePreparator.java:136) >[Thread[main,5,main]]: The stack T:\EHP4_Downloads\SMSDXML_CROSSSYS_20100726091148.945.xml contains no >components for this system.
I can see in the log that stack xml you are using is not for the system to whom you are upgrading. That is the reason system is rejecting stack file. Please check above extract of logs.
I would suggest you to please generate stack xml file for this system from MOPZ after correctly configuring SMSY and use it. Then your problem will be resolved.
Thanks
Sunny -
SAP ERP 2005 SR 2 IDES installation error in step "Run ABAP Reports"
Hello,
I'm installing SAP ERP 2005 SR 2 IDES on Win2003 R2 SP2 and Oracle 10.2 to create a test-system for my diploma thesis.
During the step "Import ABAP" I got the following message:
object_checker.log
ERROR: 2008-05-21 20:50:38
1 objects have error/ignore/execute or unknown status in the task lines.
Invalid objects are saved in 'invalid_objects.txt' file.
invalid_objects.txt
package object type action status
SAPDFACT ?N pkey create
but the installation went on until "Run ABAP Reports".
Warnings and Errors in sapinst.log are:
WARNING 2008-05-27 15:09:36
Execution of the command "C:\usr\sap\IMP\SYS\exe\uc\NTI386\stopsap.exe name=IMP nr=00 SAPDIAHOST=imperia-sap" finished with return code -1. Output:
STOPSAP: execution of C:\usr\sap\IMP\SYS\exe\uc\NTI386\sapntwaitforhalt.exe name=IMP nr=00 SAPDIAHOST=imperia-sap 3600 failed
Details are written to C:\Programme\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\stopsap.log
WARNING 2008-05-27 15:09:36
Could not stop instance 'DVEBMGS00' of SAP system IMP.
WARNING 2008-05-27 15:09:38
Connect to message server (imperia-sap/3900) failed: NIECONN_REFUSED.
WARNING[E] 2008-05-27 15:12:05
FSL-06002 Error 1060 (Der angegebene Dienst ist kein installierter Dienst.) in execution of a 'OpenService' function, line (266), with parameter (sapccmsr.00).
WARNING[E] 2008-05-27 15:21:42
FRF-00007 Unable to open RFC connection.
ERROR 2008-05-27 16:30:15
FRF-00025 Unable to call function. Error message: connection closed without message (CM_NO_DATA_RECEIVED) .
INFO 2008-05-27 16:30:19
RFC connection closed.
ERROR 2008-05-27 16:30:45
MUT-03025 Caught ERfcExcept in Modulecall: connection closed without message (CM_NO_DATA_RECEIVED).
ERROR 2008-05-27 16:30:47
FCO-00011 The step runRADDBDIF with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_ABAP_Reports|ind|ind|ind|ind|2|0|runRADDBDIF was executed with status ERROR .
Full log of today is available at [http://pastebin.com/f43531f97]
Has anyone an idea how I can finish this installation?
Thx
DanieleIt seems that the system did not come up and thus the RFC call fails.
What´s the output of
dev_w0
dev_disp
(in the ...work directory)?
Markus -
Error in SAP installation in phase 19 of 34 - Import ABAP
Hi SAP Gurus,
Good day all, I'm facing problem when installing SAP ECC 6.0 EHP7 (IDES version). Its stucked in phase 19 of 34 Import ABAP.
Below are the error details:-
ECC Message Box
An error occurred while processing option SAP Business Suite 7i 2013 Support Release 1 > EHP7 for SAP ERP 6.0 ABAP Support Release 1 > Oracle > SAP Systems > Application Server ABAP > Standard System > Standard System( Last error reported by the step: Process call 'D:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log.). You can now:
Choose Retry
to repeat the current step.
Choose Log Files
to get more information about the error.
Stop the option and continue later.
Log files are written to C:\Program Files/sapinst_instdir/BS2013/BS2013SR1/ERP607SR1/ORA/INSTALL/STD/ABAP.
Below are the logs from R3load.exe:-
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
D:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20141006062234
D:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/741_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
D:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: version R7.40/V1.8 [UNICODE]
Compiled Nov 23 2013 13:31:32
-------------------- Start of patch information ------------------------
patchinfo (patches.h): (0.009) Support for SUM/ZDM and DMO (note 1778564)
DBSL patchinfo (patches.h): (0.011) DBSL error corrections in 7.41: (4) LOBs (note 1928526)
--------------------- End of patch information -------------------------
process id 4612
DbSl Trace: Connect via SAPUSER not supported for kernel >= 740.
(DB) ERROR: db_connect rc = 256
DbSl Trace: Connect via SAPUSER not supported for kernel >= 740.
(DB) ERROR: DbSlErrorMsg rc = 29
D:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
D:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20141006062234
Looking forward for your reply.
Regards,
Jay
-96-Hi
I'm afraid you forget selecting the SSFS option during installation and it is the only connection method supported for kernel 7.40
It should be possible to fix this manually and perform all the step to connect using SSFS... but restarting your installation might be faster & easier.
1622837 - Secure connection of AS ABAP to Oracle via SSFS
As of SAP Kernel Release 7.40 (irrespective of the Oracle version), only the secure connection (secure connect) is supported via SSFS.
Regards -
SAP Ides ECC 6.0 Install: Import ABAP - Package SAPDODS Error - ORA-00903
Experts,
Good Morning!
I'm trying to install SAP IDES ECC 6.0 version on a Windows 2008 R2 Server with Oracle 11g DB (11.2).
System Info: 16GM RAM & 600GB Hdd. Prereqs passed.
I'm getting the following error during the Import ABAP phase (16 of 29) in the sapinst log:
"An error occurred while processing option Enhancement Package 6 for SAP ERP 6.0 > SAP Application Server ABAP > Oracle > Central System > Central System( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. "
Here's the dump of import_monitor.java.log
java version "1.4.2_32"
Java(TM) 2 Runtime Environment, Standard Edition (build 4.1.012)
SAP Java Server VM (build 4.1.012 1.6-b03, Oct 21 2011 14:18:45 - 41_REL - optU - windows amd64 - 6 - bas2:161688 (mixed mode))
Import Monitor jobs: running 1, waiting 1, completed 141, failed 0, total 143.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 141, failed 1, total 143.
Here's the dump of import_monitor.log:
INFO: 2014-07-05 13:42:53
Data codepage 4103 is determined using TOC file 'C:\Target\Export1\DATA\D010TAB.TOC' for package 'D010TAB'.
TRACE: 2014-07-05 13:42:53 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is started.
TRACE: 2014-07-05 13:42:53 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDODS' import package into database:
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
ERROR: 2014-07-05 13:42:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is interrupted with R3load error.
Process 'C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error' exited with return code 2.
For mode details see 'SAPDODS.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2014-07-05 13:43:21
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2014-07-05 13:43:21
1 error(s) during processing of packages.
INFO: 2014-07-05 13:43:21
Import Monitor is stopped.
Here's the log of SAPDODS...
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140705134253
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Aug 16 2011 02:26:36
patchinfo (patches.h): (0.098) DB6: correction for R3load PL 91 on HP-UX and SOLARIS (note 1609719)
process id 1488
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF16
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file C:\Target\Export1\DB/SQLFiles.LST
(SQL) INFO: C:\Target\Export1\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file DODS.SQL
(SQL) INFO: DODS.SQL not found
(SQL) INFO: Searching for SQL file C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: found C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: Trying to open C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: C:\Target\Export1\DB/ORA/DODS.SQL opened
(DB) ERROR: DDL statement failed
(DROP TABLE "/BI0/APERS_BOD00")
DbSlExecute: rc = 103
(SQL error 942)
error message returned by DbSl:
ORA-00942: table or view does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: Error 903 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-00903 occurred at SQL stmt (parse error offset=15)
(DB) ERROR: DDL statement failed
( CREATE TABLE [/BI0/APERS_BOD00] ( [TCTUSERNM] nvarchar(000012) NOT NULL , [TCTOBJVERS] nvarchar(000001) NOT NULL , [TCTSYSID] nvarchar(000010) NOT NULL , [TCTQUACT] nvarchar(000001) NOT NULL , [TCTOBJNM] nvarchar(000040) NOT NULL , [TCTTLOGO] nvarchar(000004) NOT NULL , [RECORDMODE] nvarchar(000001) NOT NULL , [TCTTIMSTMP] nvarchar(000014) NOT NULL ) WITH ( DATA_COMPRESSION = PAGE ) )
DbSlExecute: rc = 99
(SQL error 903)
error message returned by DbSl:
ORA-00903: invalid table name
(DB) INFO: disconnected from DB
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140705134254
FYI - A retry does not help. Also tried to search for the error on scn, google but haven't been able to find the right solution.
Can you help?
Regards,
Cobain.Divyanshu - sorry to ask but can you explain why i need to update r3load and r3trans to resolve this error? Just want to understand why I'm doing a correction so I can learn from the same.
Also, can you clarify the file update process:
For R3load:
a) the r3load used by the command is dated 8/16/2011 (location:C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\...)
b) the r3load i have in my db folder is dated 10/23/2011 (location:C:\Final\Installer\BS7i2011_Installation_Master_\DATA_UNITS\BS2011_IM_WINDOWS_X86_64\ORA\UC\...)
Do i replace (a) with (b)?
For R3trans:
How do I update this file?
- Cobain. -
RFC Connection Error during Web AS ABAP Database Instance
I keep getting RFC Connection error installing the database instance. The following are the pertinent logs:
INFO 2007-05-09 20:10:04
Working directory changed to C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\MSS\UC\DB.
INFO 2007-05-09 20:10:04
Output of C:\usr\sap\X22\SYS\exe\run\r3trans.exe -u 1 -i "C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\MSS\UC\DB\mssprocs640.dat" is written to the logfile r3trans.exe.log.
INFO 2007-05-09 20:10:22
Execution of the command "C:\usr\sap\X22\SYS\exe\run\r3trans.exe -u 1 -i "C:\Program Files\sapinst_instdir\NW04\SYSTEM\ABAP\MSS\UC\DB\mssprocs640.dat"" finished with return code 0. Output: This is C:\usr\sap\X22\SYS\exe\run\r3trans.exe version 6.13 (release 640 - 03.06.05 - 17:04:00).unicode enabled versionC:\usr\sap\X22\SYS\exe\run\r3trans.exe finished (0000).
INFO 2007-05-09 20:12:23
RFC parameter CLIENT set to value 000.
INFO 2007-05-09 20:12:23
RFC parameter USER set to value DDIC.
INFO 2007-05-09 20:12:23
RFC parameter LCHECK set to value 1.
INFO 2007-05-09 20:12:23
RFC parameter PCS set to value 1.
INFO 2007-05-09 20:12:23
RFC parameter LANG set to value EN.
INFO 2007-05-09 20:12:23
RFC parameter ASHOST set to value cix22.
INFO 2007-05-09 20:12:23
RFC parameter SYSNR set to value 00.
INFO 2007-05-09 20:12:23
RFC connection information checked successfully.
ERROR 2007-05-09 20:12:24
FRF-00007 Unable to open RFC connection.
I tried the following fixes spread across different threads in this Expert Forums:
1. Someone said network problem. I rebooted, restarted the install and even redo it.
2. Another suggestion was to use caps on the password. Didnt work.
3. One suggestion was to update the keydb.xml file. However, I could find such property name:
search for the table t_SAPComponent_SAPSystemLogon_SHARED
then look for <fld name="pPW">, <properties>,
<property name ="GUIENG_USER_INPUT" and set the value
"GUINEG_TRUE" to "GUIENG_FALSE".
4. I even used the ddic password 19920706 which is supposed to be the default.
5. Restarted the instance and applied all the fixes above.
Does anyone know what is going on base on the logs above? Thanks.try moving all your install disk onto local file system then rerun the install. That might work....
-
Import ABAP error in ERP 2005 SR2 IDES installation
Hi Experts
I am trying to install the SAP ERP 2005 SR2 ( OS is 2003 and Database is Oracle 10g )IDES which i downloaded from the SAP market place and got
the following error at the IMPORT ABAP task
INFO 2008-02-20 14:19:37
Output of C:\Program Files\Java\j2re1.4.2_16\bin\java.exe -classpath migmon.jar -showversion
com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs "D:\ERP 2005 IDES\51032413_1\EXP1;
D:\ERP 2005 IDES\51032413_2\EXP2;D:\ERP 2005 IDES\51032413_3\EXP3;D:\ERP 2005 IDES\51032413_4\EXP4;
D:\ERP 2005 IDES\51032413_5\EXP5;D:\ERP 2005 IDES\51032413_6\EXP6;D:\ERP 2005 IDES\51032413_6\EXP7;
D:\ERP 2005 IDES\51032413_6\EXP8;D:\ERP 2005 IDES\51032413_6\EXP9;D:\ERP 2005 IDES\51032413_6\EXP10;
D:\ERP 2005 IDES\51032413_6\EXP11" -installDir C:\PROGRA1\SAPINS1\ERP\SYSTEM\ORA\CENTRAL\AS
-orderBy "" -r3loadExe D:\usr\sap\SRD\SYS\exe\nuc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 1100
-jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst is written to the logfile import_monitor.java.log.
WARNING 2008-02-20 14:31:07
Execution of the command "C:\Program Files\Java\j2re1.4.2_16\bin\java.exe -classpath migmon.jar -showversion
com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs "D:\ERP 2005 IDES\51032413_1\EXP1;
D:\ERP 2005 IDES\51032413_2\EXP2;D:\ERP 2005 IDES\51032413_3\EXP3;D:\ERP 2005 IDES\51032413_4\EXP4;
D:\ERP 2005 IDES\51032413_5\EXP5;D:\ERP 2005 IDES\51032413_6\EXP6;D:\ERP 2005 IDES\51032413_6\EXP7;
D:\ERP 2005 IDES\51032413_6\EXP8;D:\ERP 2005 IDES\51032413_6\EXP9;D:\ERP 2005 IDES\51032413_6\EXP10;
D:\ERP 2005 IDES\51032413_6\EXP11" -installDir C:\PROGRA1\SAPINS1\ERP\SYSTEM\ORA\CENTRAL\AS
-orderBy "" -r3loadExe D:\usr\sap\SRD\SYS\exe\nuc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 1100
-jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103.
Output: java version "1.4.2_16"Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_16-b05)Java HotSpot(TM)
Client VM (build 1.4.2_16-b05, mixed mode)Import Monitor jobs: running 1, waiting 18, completed 0, failed 0, total 19.
Loading of 'SAPSDIC' import package: ERRORImport Monitor jobs: running 0, waiting 18, completed 0, failed 1, total 19.
ERROR 2008-02-20 14:31:07
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2008-02-20 14:31:07
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW
CreateDBandLoad|ind|ind|ind|ind|10|0|NWABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor
was executed with status ERROR .
can anyone help me to fix this error. Installation of ECC 6.0 with SQL SERVER 2005 was done fine.
Thanking you
Regards
MrudulHi Mrudul,
Understood you have downloaded the completed IDES SAP 2005 SR2 package, i have also downloaded it several months ago, but i found the package not full good when i prepare to install it last week, 3 of 35 Exp unpackage CRC32 error(51032413_part15.rar & 51032413_part16.rar & 51032413_part17.rar) when unpackage them, can you do me a favor to share me the 3 rar files? As the original download address have been obsoleted away service.sap.com, i can tell you my FTP site to store them.
51032413_part15.rar & 51032413_part16.rar & 51032413_part17.rar
Or 51032413_3\EXP3\DATA\SAPAPPL1.009 & SAPAPPL1.010
12/17/2006 02:32 AM 1,048,576,000 SAPAPPL1.009
12/17/2006 02:42 AM 954,643,456 SAPAPPL1.010
Tks!
Best rds,
Jeff
msn: [email protected] -
Error while installing the java add-on on abap system
Dear All,
We are trying to install java add-on with EP on present ABAP system, but getting struck up with error as below at creating java users (sapjsf) in central instance installation phase.
ENVIRONMENT:
ECC6.0
WIN 2003
KERNEL 136
SUPPORT PACK LEVEL AT 13
NETWEAVER 2004S SR1.
DB- ORACLE
error: ( usercheck.log)
java.lang.NoClassDefFoundError: com/sun/tools/javac/Main
Exception in thread "main" Reserved 1610612736 (0x60000000) bytes before loading DLLs.
Critical Error
Launching program failed
-> Internal program error (rc = -1)
error: (sapinst.log)
WARNING 2008-08-11 15:00:00
Execution of the command "C:\usr\sap\B60\DVEBMGS00\exe\jlaunch.exe UserCheck.jlaunch com.sap.security.tools.UserCheck "C:\Program Files\sapinst_instdir\ERP\LM\AS-JAVA\ADDIN\ORA\CENTRAL\CI\install\lib;C:\Program Files\sapinst_instdir\ERP\LM\AS-JAVA\ADDIN\ORA\CENTRAL\CI\install\sharedlib;C:\Program Files\sapinst_instdir\ERP\LM\AS-JAVA\ADDIN\ORA\CENTRAL\CI\install" -c sysnr=00 -c ashost=sapserver -c client=001 -c user=DDIC -c XXXXXX -a checkCreate -u SAPJSF -p XXXXXX -r SAP_BC_JSF_COMMUNICATION_RO -message_file UserCheck.message" finished with return code -1. Output:
java.lang.NoClassDefFoundError: com/sun/tools/javac/Main
Exception in thread "main" Reserved 1610612736 (0x60000000) bytes before loading DLLs.
Critical Error
Launching program failed
-> Internal program error (rc = -1)
INFO 2008-08-11 15:00:00
Removing file C:\Program Files\sapinst_instdir\ERP\LM\AS-JAVA\ADDIN\ORA\CENTRAL\CI\dev_UserCheck.
ERROR 2008-08-11 15:00:00
CJS-30197 . For more details see output of logfile:
ERROR 2008-08-11 15:00:00
FCO-00011 The step createJSF with step key |NW_Addin_CI|ind|ind|ind|ind|0|0|NW_CI_Instance|ind|ind|ind|ind|8|0|NW_CI_Instance_Doublestack|ind|ind|ind|ind|2|0|createJSF was executed with status ERROR .
Please help us out at your earliest convenience.
Thanks and warm regards,Dear Samrat Dangeti ,
Thanks.
Inst version: 701.
JDK version: 1.4.2_13
Regards, -
Import ABAP error in ECC6 system copy targert
Hi Experts,
I am istalling SAP Ecc 6 in System copy targrt, ABAP import fail in 2/87. I got the error Loading of 'SAPDFACT' import package: ERRORImport Monitor jobs.
My OS Windows 2003 64 bit and Oracle 10.2. Please find the log files belo. Please help me to solve this issue
:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100325173244
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jul 17 2007 00:40:17
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe -ctf I H:\MVGK IDESBackup-march2010\ABAP\DATA\SAPDFACT.STR C:\Program Files\sapinst_instdir\ERP\LM\COPY\ORA\SYSTEM\CENTRAL\AS\DDLORA.TPL SAPDFACT.TSK ORA -l SAPDFACT.log
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: job completed
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100325173244
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100325173244
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jul 17 2007 00:40:17
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(GSI) INFO: dbname = "AT220100325020343 "
(GSI) INFO: vname = "ORACLE "
(GSI) INFO: hostname = "KENKI "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "KENKI"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 2"
(GSI) INFO: machine = "4x AMD64 Level 6 (Mod 15 Step 7)"
(DB) INFO: /BI0/E0RSTT_C01 created #20100325173245
(IMP) INFO: import of /BI0/E0RSTT_C01 completed (0 rows) #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~0 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~01 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~02 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~04 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~05 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~06 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~07 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~08 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~09 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~10 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~11 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~12 created #20100325173245
(DB) INFO: /BI0/E0RSTT_C01~13 created #20100325173245
DbSl Trace: Error 1408 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-1408 occurred when executing SQL stmt (parse error offset=57)
(DB) ERROR: DDL statement failed
(CREATE INDEX "/BI0/E0RSTT_C01~P" ON "/BI0/E0RSTT_C01" ( "KEY_0RSTT_C01P" , "KEY_0RSTT_C01T" , "KEY_0RSTT_C01U" , "KEY_0RSTT_C011" , "KEY_0RSTT_C012" , "KEY_0RSTT_C013" , "KEY_0RSTT_C014" , "KEY_0RSTT_C015" , "KEY_0RSTT_C016" , "KEY_0RSTT_C017" , "KEY_0RSTT_C018" , "KEY_0RSTT_C019" , "KEY_0RSTT_C01A" ) TABLESPACE PSAPSR3 STORAGE (INITIAL 65536 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )
DbSlExecute: rc = 99
(SQL error 1408)
error message returned by DbSl:
ORA-01408: such column list already indexed
(DB) INFO: disconnected from DB
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100325173245
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100325174158
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jul 17 2007 00:40:17
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(GSI) INFO: dbname = "AT220100325020343 "
(GSI) INFO: vname = "ORACLE "
(GSI) INFO: hostname = "KENKI "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "KENKI"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 2"
(GSI) INFO: machine = "4x AMD64 Level 6 (Mod 15 Step 7)"
(DB) ERROR: DDL statement failed
(DROP INDEX "/BI0/E0RSTT_C01~P")
DbSlExecute: rc = 103
(SQL error 1418)
error message returned by DbSl:
ORA-01418: specified index does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: Error 1408 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-1408 occurred when executing SQL stmt (parse error offset=57)
(DB) ERROR: DDL statement failed
(CREATE INDEX "/BI0/E0RSTT_C01~P" ON "/BI0/E0RSTT_C01" ( "KEY_0RSTT_C01P" , "KEY_0RSTT_C01T" , "KEY_0RSTT_C01U" , "KEY_0RSTT_C011" , "KEY_0RSTT_C012" , "KEY_0RSTT_C013" , "KEY_0RSTT_C014" , "KEY_0RSTT_C015" , "KEY_0RSTT_C016" , "KEY_0RSTT_C017" , "KEY_0RSTT_C018" , "KEY_0RSTT_C019" , "KEY_0RSTT_C01A" ) TABLESPACE PSAPSR3 STORAGE (INITIAL 65536 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )
DbSlExecute: rc = 99
(SQL error 1408)
error message returned by DbSl:
ORA-01408: such column list already indexed
(DB) INFO: disconnected from DB
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100325174158
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100325180802
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jul 17 2007 00:40:17
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: DbSlErrorMsg rc = 99
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100325180808
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100325182246
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jul 17 2007 00:40:17
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: DbSlErrorMsg rc = 99
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100325182251
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100325183259
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jul 17 2007 00:40:17
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: DbSlErrorMsg rc = 99
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100325183304
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100326100904
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jul 17 2007 00:40:17
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
DbSl Trace: OCI-call 'OCIServerAttach' failed with rc=12541
DbSl Trace: CONNECT failed with sql error '12541'
(DB) ERROR: DbSlErrorMsg rc = 99
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
G:\usr\sap\AT2\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100326100910
Thanks in Advance
Jose HHi,
You can check the defined enviornment variable using command prompt and System properties.
Open Command Prompt and give "set" command. It will show you active environment variable.
You can also set missing environment variables in system properties.
Start -->Control Panel --> System
On Advanced Tab --> Environment Variables.
After logging to the database if it shows message "Connected to idle instance", that means your database is not started.
Please start the database using below SQL command.
Open Command Prompt
C:\Sqlplus / as sysdba
SQL>startup
Once it says "Database opened", retry SAP installation.
You can also check the database status in SQL prompt using below command:
SQL> select instance_name,status from v$instance;
It must show output like:
INSTANCE_NAME STATUS
<SID> OPEN
Regards.
Rajesh Narkhede
Maybe you are looking for
-
Weblogic server deployment problem.
Dear All, I create a package as webservice. I deployed it into the weblogic server. When i start the webservice, it shows this error. java.lang.Exception: [DeploymentService:290049]Deploy failed for id '1,239,100,872,065' since no targets are reachab
-
ShowExceptionErrorMessage - what is it?
I see code examples with showExceptionErrorMessage in it and the error after it but I always get a symbol not resolved error when I try to use it in my code. i.e.: catch (FileNotFoundException fnfe) { System.err.println("FileNotFoundException: " + fn
-
HT5622 can i see what i have in the cloud? pictures files contacts?
ca i see what i have in the cloud?
-
I have a function that searches through an ArrayList and sees if one of the objects' variable has a certain value. What I want to do is return the index of all of the objects with a certain values. But because I don't know how many objects there are
-
Is it possible to request CD/DVD discs from Toshiba?
I would prefer manufacturers' disks to the recovery disks that I have already made.