Error connecting SAP BW System using EP 6.0

Hi All
I am trying to connect EP6.0 with SAP BW 3.1, using ITS.
I have created a 'system' in portal and my ITS test connection is successful. I chose 'SAP BW' as sytem instead of SAP R/3.
When I try to preview/access an iView which internally execute BW workbook, I am getting following error. Can anyone please guide me the possible solutions. As this is urgent, please provide help.
Sapgui 640 error window with the following message:
connection to partner broken
Time Wed Dec 12 16:15:03 2005
Component NI(Network interface)
Release 640
Version 37
Module ninti.c
Line 756
Method NiPRead(192.168.64.103/3320, hdl 1)
Return Code -6
System Call recv
Counter 1

Hi,
Any reason why want to connect to BW from EP through ITS.
I think you can directlty connect to BW from EP.
These links should be of some help
http://help.sap.com/saphelp_nw04/helpdata/en/a9/76bd3b57743b09e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/33/39fa40ee14f26fe10000000a1550b0/frameset.htm
Thanks
Senthil
P.S: Rewards Points for useful/helpful answers

Similar Messages

Error connecting SAP BW System using EP6.0

Hi All
I am trying to connect EP6.0 with SAP BW 3.1, using ITS.
I have created a 'system' in portal and my ITS test connection is successful. I chose 'SAP BW' as sytem instead of SAP R/3.
When I try to preview/access an iView which internally execute BW workbook, I am getting following error. Can anyone please guide me the possible solutions. As this is urgent, please provide help.
Sapgui 640 error window with the following message:
connection to partner broken
Time Wed Dec 12 16:15:03 2005
Component NI(Network interface)
Release 640
Version 37
Module ninti.c
Line 756
Method NiPRead(192.168.64.103/3320, hdl 1)
Return Code -6
System Call recv
Counter 1

Hi,
let me try to sort this out.
You want to use an ITS against a BW system using a SAP GUI for HTML. If you use the system type SAP R/3 everything is OK but if you use the system type SAP BW it doesn't work and you get a error message from your SAP GUI for Windows.
I'm not much aware of this but for me it looks like the portals iview is trying to use your SAP GUI for Windows to connect to your BW System (which is, as far as I understood, not what you intended).
If all my assumtions above are correct you should create a ITS iview (SAP IAC iView) against your BW system and everything should be OK then.
Regards Ralph

Error connecting SAP BW system from EP6.0

Hi All
I am trying to connect EP6.0 with SAP BW 3.1, using ITS.
I have created a 'system' in portal and my ITS test connection is successful. I chose 'SAP BW' as sytem instead of SAP R/3.
When I try to preview/access an iView which internally execute BW workbook, I am getting following error. Can anyone please guide me the possible solutions. As this is urgent, please provide help.
Sapgui 640 error window with the following message:
connection to partner broken
Time Wed Dec 12 16:15:03 2005
Component NI(Network interface)
Release 640
Version 37
Module ninti.c
Line 756
Method NiPRead(192.168.64.103/3320, hdl 1)
Return Code -6
System Call recv
Counter 1

Hi Srinivasa,
Please refer to the following link for Integration of BW with EP .
<a href="http://help.sap.com/saphelp_bw31/helpdata/en/f1/0a5a2ee09411d2acb90000e829fbfe/frameset.htm">http://help.sap.com/saphelp_bw31/helpdata/en/f1/0a5a2ee09411d2acb90000e829fbfe/frameset.htm</a>
hope it helps..
cheers
Anand

Connecting SAP PLM system to iview portal.

Hi experts i want one clarification on process of connecting SAP PLM system to iview portal.
here my scenario is SAP PLM->>>XI--->>>WEBSERVICES
RFC-->>XI--->>>>SOAP
1---->>here i have to get the list of all materials from SAP PLM using iview as
front end tool.
2---->>and the next thing is if the material is camera means it should require the
lengs software for the camera.In the iview we can select the material
for upgrated software.
3--->>after that the input parameters wil be sent to webservices
(some website) using XI part(mapping and all) and the response should come back then it has
to be stored in the SAP PLM system.
please clear me all the above questions.
thanks & regards
babu

HI,
See
1) Request is sent from the Portal.
2) Web Dynpro application is called through the URL.
3) Web Dynpro app makes use of Web Service based Model in sending SOAP request to XI.
4) SOAP adapter converts the incoming SOAP message into XI Message.
5) Synchronous call is made from XI to R3 backend using RFC adapter.
6) Response is mapped and routed back as SOAP message.
Necessary design steps in interface objects, mapping objects and Business process are created according to the functional requirements.
Sender Soap Communication channel is setup in Configuration along with other essential configuration steps.
WSDL is generated for the message interface in Integration Directory using Tools-->Define Web service.
Override the default URL with following while generating WSDL.
See the below link
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1334 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
Regards
Chilla

How to connect SAP R3 system to BW system

please give me step by step guidance how to connect SAP R3 system to BW system with example.

Hi,
Check the docs below.
Connection between Source Systems and BW
http://help.sap.com/saphelp_nw70/helpdata/en/00/dc54384ac9a81be10000009b38f8cf/frameset.htm
Creating SAP Source Systems
http://help.sap.com/saphelp_nw70/helpdata/en/ac/4a4e38493e4774e10000009b38f889/frameset.htm
BW connectivity(.doc)
http://help.sap.com/bp_biv335/BI_EN/BBLibrary/documentation/B84_BB_ConfigGuide_EN_DE.doc
hope this helps
Regards.

Error connecting to portal database using alias

i am using Connector framework api to connect to portal database.
in visual administrator -> JDBC connector. I click on runtime tab
Under Resources i find Data Sources and Drivers.
Under Data sources I see SAPSR3DB. In Main tab on right hand pane I find many other aliases called SAP/BC_UME and SAP/BC_WDDR etc. Which one do I use in creating a connection.
IConnectorGatewayService cgService = (IConnectorGatewayService) PortalRuntime.getRuntimeResources().getService("com.sap.portal.ivs.connectorservice.connector");
ConnectionProperties cp = new ConnectionProperties(request.getLocale(),request.getUser());
IConnection connection = cgService.getConnection("SAPSR3DB",cp);
No system found for alias SAPSR3DB.

Hi,
If you want to use the PortalService IConnectorGatewayService you will have to create a JDBC System in the System Landscape of the Portal and create a System Alias with usermapping.
You can then create a c connection to this JDBC System with the IConnectorGatewayServcie using the specified System alias.
But if you want to directly connect to the System Database you can also use OpenSQL in your Portalapplication and lookup the Connection using JNDI:
 InitialContext ctx= new InitialContext();
 ds= (DataSource) ctx.lookup("jdbc/SAPSR3DB");
 java.sql.Connection conn= ds.getConnection();
// user your connection here and close all jdbc objects finally!
Best regards,
Stefan Brauneis

Error Connecting SAP Business One and Crystal Report

Hi All,
I installed Crystal Report 2008 on my system for creating a report in Crystals.
I clicked on "New Report" and it opened a window called "Database Exert." However, when I look in the Database Expert, I cannot see "SAP Business One" in it. How can I connect SAP Business One 8.8 with Crystal Report?
Regards,
Bharath S

Hi
On your computer, locate the Crystal folder according to the following directory path: C:\Program Files\SAP\SAP Business One\Crystal. Then double-click the file: SAP Business One Crystal Report Integration Package.exe. and follow the step of the setup status screen.
Regards
Christian Carrasco

Error: The sap bw system must not be operated in client 000

Hi
I login as a client "200" and create new user "imran" and then login as a client 200 and user imran successfully but when I goto T.code RSOR it shows "the sap bw system must not be operated in client 000" when I check the status it shows client 200 and user imran.
so what is the solution??
Regards
Imran

hi
Yes I create new client "200" in a sap* then I login as a client "200" user "sap*" and password "pass" then create new user "imran" using copy DDIC then login as client 200 and user imran but result is same.
Edited by: iskhan on Nov 5, 2009 7:24 AM
Edited by: iskhan on Nov 5, 2009 11:36 AM

Error connecting ECC source system to BI

Hi Guru,
I'm trying to connect with ecc system to my bi.
My 100 client is ECC & 110 client is BI(already connected). I want to replicate ecc meta data(data sources) to bi..
But I'm connecting getting this error..
Kindly give your valuable feedbacks.
Thanks & Regards,
JTS

Issue Solved.
Problem with RFC connection.
Regards,
JTS

Error connecting to PTG repo using service designer.

I am trying to login into my ptg repousing service designer but have problems.i have install 9ias on a different server and my db on server. this is the message i get back.
oracle.panama.pasm.PASMException: Exception creating connection to: ERIC; nested exception is:
java.net.SocketException: connect (code=10061)
at oracle.panama.pasm.ConnectAction.connect(ConnectAction.java:148)
at oracle.panama.pasm.PASM$1.windowOpened(PASM.java:439)
at java.awt.AWTEventMulticaster.windowOpened(Unknown Source)
at java.awt.Window.processWindowEvent(Unknown Source)
at javax.swing.JFrame.processWindowEvent(Unknown Source)
at java.awt.Window.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForComponent(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForComponent(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
oracle.panama.PanamaException: Exception creating connection to: ERIC; nested exception is:
java.net.SocketException: connect (code=10061)
oracle.panama.PanamaException: Exception creating connection to: ERIC; nested exception is:
java.net.SocketException: connect (code=10061)
at oracle.panama.core.rmi.client.RMIServer.createModelConnection(RMIServer.java:54)
at oracle.panama.pasm.ConnectAction.connect(ConnectAction.java:184)
at oracle.panama.pasm.ConnectAction.rmiConnect(ConnectAction.java:178)
at oracle.panama.pasm.ConnectAction.connect(ConnectAction.java:142)
at oracle.panama.pasm.PASM$1.windowOpened(PASM.java:439)
at java.awt.AWTEventMulticaster.windowOpened(Unknown Source)
at java.awt.Window.processWindowEvent(Unknown Source)
at javax.swing.JFrame.processWindowEvent(Unknown Source)
at java.awt.Window.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForComponent(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForComponent(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
java.rmi.ConnectIOException: Exception creating connection to: ERIC; nested exception is:
java.net.SocketException: connect (code=10061)
java.rmi.ConnectIOException: Exception creating connection to: ERIC; nested exception is:
java.net.SocketException: connect (code=10061)
java.net.SocketException: connect (code=10061)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(Unknown Source)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(Unknown Source)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
at sun.rmi.server.UnicastRef.newCall(Unknown Source)
at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
at java.rmi.Naming.lookup(Unknown Source)
at oracle.panama.core.rmi.client.RMIServer.createModelConnection(RMIServer.java:50)
at oracle.panama.pasm.ConnectAction.connect(ConnectAction.java:184)
at oracle.panama.pasm.C onnectAction.rmiConnect(ConnectAction.java:178)
at oracle.panama.pasm.ConnectAction.connect(ConnectAction.java:142)
at oracle.panama.pasm.PASM$1.windowOpened(PASM.java:439)
at java.awt.AWTEventMulticaster.windowOpened(Unknown Source)
at java.awt.Window.processWindowEvent(Unknown Source)
at javax.swing.JFrame.processWindowEvent(Unknown Source)
at java.awt.Window.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForComponent(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForComponent(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
some body help
thanks.

What is the connect string you are using to connect Service Designer, e.g. "Localhost"? See my reply to an earlier question in this forum.

HELP with this error: "Connect to iTunes to use push notifications"

"connect to iTunes to use push notifications" myspace or facebook notifications may include alerts, sounds an icon badges"
I have an 3.1.2 iPhone 3G and everytime that I conected to my Mac and iTunes this message came up...
How Can I resolve this?
I'll appreciate any help.

That message generally means you've jailbroken your phone. So, have you jailbroken your phone? My guess is the answer is yes since you're still on 3.1.2.

Question about Note 886102 - Empty the delta queue of the connected SAP source systems

Dear expert
I'm doing the system refresh from ECC PRD to QAS using the hot backup of PRD
Before i start the database restore i was told to do the following step since this ECC has connection with one BW system
-----------------------Step -----------------------------
2.17 SAP note 886102 scenario C3
Empty the delta queue for all of the connected BW systems.
Execute all delta info packages two times on BW side, to clean up the delta queue in the source system. This is needed, because BDLS cannot rename the still available LUW-s in the qRFC queue.
----------------------Step-----------------------
But unfortunately i missed to execute this step
And the Q11 is now retoreing the backup of the database
My quesion
1. what will be bad consequence due to not execute this step? any way to makeup this error?
Best regards,

Hi Kate,
The probably issue which I could forsee is data getting wrongly updated into production if RFC connection from ECC to BW is not stopped.
Solution here could be to disable or deletethe RFC connections between ECC and BW before starting the SAP system at database level.
delete from sapr3.rfcdes where rfcdest = '<name>';
Once the system is up and running you can recreate them if required.
Also before starting SAP set the number of batch processes to 0 on the profile at OS level so that any released jobs don't start as soon as SAP is up.
Once the SAP system is up execute BDLS and change the logical system name.
Hope this helps.
Regards,
Deepak Kori

Error connecting SAP BW7.00/BI7.03 to R/3 4/7/6.20

We recently installed SAPNW2004s from ERP2005 package with BI7.03 addon. Right now we are configuring the system to connect to R/3 system which is a 4.7 appl with 6.20 basis. I am getting below error on RFC connection setting via RSA1 t-code.
"RFC user logon failed. Check the connection.
    Message no. R3077
Diagnosis
    You tried to logon to BW using the RFC user. This action failed.
System Response
    service 'sapgw01' unknown / CPI-C error CM_PRODUCT
Procedure
    On the following screen, check the destination from the source system into BW. Make sure you entered the correct password."
But I was able to reach R/3 system from bw system via ping test and viceversa. I know its not a password or user-id issue.
We were successfully able to do the same setup in SAPBW 3.5/BI 3.3
Was there any compatibility issue here between SAPBW7.0 WITH R/3 4.7/6.20 ? OR AM I missing some thing. Pls help.
Thanks
Srini

Hello,
Please check an entry in the /etc/services file for sapgw01.
                                                         sapgw01    3302/tcp
Best regards,
Daiva

Error connecting to oracle DB using SAS 8.1

Hi,
I am using SAS 8.1(2005 Q1) and the oracle server is 9.2.0.1. I am trying to run a sample application given in the app server (jdbc-simple) and it's not connecting to the database.
I am using oracle thin driver.
I have created the jdbc connection pool named jdbc-pool too. Is there anything else I shud do? I am able to ping to the database using this connection pool but not able to run the application and getting http status 500 error with the following message:
java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key exception
This is the server.log file:
[#|2005-08-22T13:04:45.356+0530|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=11;|WEB0783: Error commiting response
java.io.IOException: An existing connection was forcibly closed by the remote host
 at sun.nio.ch.SocketDispatcher.write0(Native Method)
 at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:33)
 at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)
 at sun.nio.ch.IOUtil.write(IOUtil.java:75)
 at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:302)
 at java.nio.channels.Channels.write(Channels.java:60)
 at java.nio.channels.Channels.access$000(Channels.java:47)
 at java.nio.channels.Channels$1.write(Channels.java:134)
 at org.apache.coyote.http11.InternalOutputBuffer.commit(InternalOutputBuffer.java:602)
 at com.sun.enterprise.web.connector.grizzly.ProcessorTask.action(ProcessorTask.java:749)
 at org.apache.coyote.Response.action(Response.java:188)
 at org.apache.coyote.Response.sendHeaders(Response.java:380)
 at org.apache.coyote.tomcat5.OutputBuffer.doFlush(OutputBuffer.java:357)
 at org.apache.coyote.tomcat5.OutputBuffer.close(OutputBuffer.java:318)
 at org.apache.coyote.tomcat5.CoyoteResponse.finishResponse(CoyoteResponse.java:496)
 at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:188)
 at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:653)
 at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:534)
 at com.sun.enterprise.web.connector.grizzly.ProcessorTask.doTask(ProcessorTask.java:403)
 at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:55)
|#]
[#|2005-08-22T13:05:34.432+0530|WARNING|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=12;|RAR6017 : Failed to get connection pool object via JNDI lookup : jdbc-pool|#]
[#|2005-08-22T13:07:39.704+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.tools.deployment|_ThreadID=13;|DPL5109: EJBC - START of EJBC for [jdbc-simple]|#]
[#|2005-08-22T13:07:39.724+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.tools.deployment|_ThreadID=13;|Processing beans ...|#]
[#|2005-08-22T13:07:39.814+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.tools.deployment|_ThreadID=13;|DPL5110: EJBC - END of EJBC for [jdbc-simple]|#]
[#|2005-08-22T13:07:41.707+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.tools.deployment|_ThreadID=13;|Total Deployment Time: 10042 msec, Total EJB Compiler Module Time: 110 msec, Portion spent EJB Compiling: 1%
Breakdown of EJBC Module Time: Total Time for EJBC: 110 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 50 msec (45%),
|#]
[#|2005-08-22T13:07:42.568+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.tools.deployment|_ThreadID=13;|deployed with moduleid = jdbc-simple|#]
[#|2005-08-22T13:07:43.459+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.tools.admin|_ThreadID=14;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added jdbc-simple]|#]
[#|2005-08-22T13:07:43.669+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.tools.admin|_ThreadID=14;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-08-22T13:07:43.759+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.tools.admin|_ThreadID=14;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy jdbc-simple]|#]
[#|2005-08-22T13:07:44.159+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.ejb|_ThreadID=14;|Instantiated container for: ejbName: jdbc-simpleEJB; containerId: 73708094084546560|#]
[#|2005-08-22T13:07:44.430+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.core.classloading|_ThreadID=14;|LDR5010: All ejb(s) of [jdbc-simple] loaded successfully!|#]
[#|2005-08-22T13:07:44.440+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=14;|WEB0100: Loading web module [jdbc-simple:jdbc-simple.war] in virtual server [server] at [/jdbc-simple]|#]
[#|2005-08-22T13:07:45.982+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.tools.admin|_ThreadID=14;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-08-22T13:10:48.029+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
GreeterDBServlet is executing ...|#]
[#|2005-08-22T13:10:48.029+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
Retrieving JNDI initial context...|#]
[#|2005-08-22T13:10:48.049+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
- Retrieved initial context successfully|#]
[#|2005-08-22T13:10:48.049+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
Looking up dbGreeter bean home interface...|#]
[#|2005-08-22T13:10:48.049+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
- Looking up: java:comp/env/ejb/jdbc-simple|#]
[#|2005-08-22T13:10:48.169+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
- Looked up the EJB successfully|#]
[#|2005-08-22T13:10:48.179+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
Creating the dbGreeter bean...|#]
[#|2005-08-22T13:10:48.189+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
- Created EJB successfully |#]
[#|2005-08-22T13:10:48.189+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
Getting the message from the dbGreeter bean ...|#]
[#|2005-08-22T13:10:48.229+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=16;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@1cce278|#]
[#|2005-08-22T13:10:48.239+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=16;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@2848b1|#]
[#|2005-08-22T13:10:48.239+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=16;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@bc9c25|#]
[#|2005-08-22T13:10:48.239+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=16;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@af5e3c|#]
[#|2005-08-22T13:10:48.239+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=16;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@153e9cf|#]
[#|2005-08-22T13:10:48.239+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=16;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@1b16bd|#]
[#|2005-08-22T13:10:48.239+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=16;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@7210ec|#]
[#|2005-08-22T13:10:48.239+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=16;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@b4fa48|#]
[#|2005-08-22T13:10:48.239+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=16;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@19bcae1|#]
[#|2005-08-22T13:10:48.239+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=16;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@1249338|#]
[#|2005-08-22T13:10:48.239+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=16;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@3d787c|#]
[#|2005-08-22T13:10:48.239+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=16;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@1b12c9b|#]
[#|2005-08-22T13:10:48.239+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=16;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@e797db|#]
[#|2005-08-22T13:10:48.239+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=16;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@a2e5cc|#]
[#|2005-08-22T13:10:48.239+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=16;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@1a7a525|#]
[#|2005-08-22T13:10:48.249+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=16;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@52732d|#]
[#|2005-08-22T13:10:48.249+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=16;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@107939f|#]
[#|2005-08-22T13:10:48.249+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=16;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@6cdb70|#]
[#|2005-08-22T13:10:48.249+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=16;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@baa4a4|#]
[#|2005-08-22T13:10:48.249+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=16;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@18f22f3|#]
[#|2005-08-22T13:10:48.259+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
ejbCreate() on obj samples.jdbc.simple.ejb.GreeterDBBean@15ec870|#]
[#|2005-08-22T13:10:48.269+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
GreeterDB EJB is determining message...|#]
[#|2005-08-22T13:10:48.269+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
- Message determined successfully|#]
[#|2005-08-22T13:10:48.269+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
- Got this message from greeter bean: afternoon|#]
[#|2005-08-22T13:10:48.269+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
Getting the name input to this servlet...|#]
[#|2005-08-22T13:10:48.269+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
- Got name: gmfgmf|#]
[#|2005-08-22T13:10:48.269+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
Recording the greeting in the database...|#]
[#|2005-08-22T13:10:48.279+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
Getting datasource...|#]
[#|2005-08-22T13:10:48.279+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
- Got datasource successfully|#]
[#|2005-08-22T13:10:48.279+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
Getting connection...|#]
[#|2005-08-22T13:10:48.870+0530|WARNING|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=15;|RAR5038:Unexpected exception while creating resource|#]
[#|2005-08-22T13:10:48.870+0530|WARNING|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=15;|RAR5117 : Failed to obtain/create connection. Reason : Connection could not be allocated because: ORA-01017: invalid username/password; logon denied
|#]
[#|2005-08-22T13:10:48.870+0530|WARNING|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=15;|RAR5114 : Error allocating connection : [Error in allocating a connection. Cause: Connection could not be allocated because: ORA-01017: invalid username/password; logon denied
]|#]
[#|2005-08-22T13:10:48.870+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
- Could not interact with the database|#]
[#|2005-08-22T13:10:48.880+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
Exception: java.sql.SQLException: Error in allocating a connection. Cause: Connection could not be allocated because: ORA-01017: invalid username/password; logon denied
|#]
[#|2005-08-22T13:10:48.880+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
Storing the message in request object for the JSP...|#]
[#|2005-08-22T13:10:48.880+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
- Stored message successfully|#]
[#|2005-08-22T13:10:48.880+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
Dispatching JSP for output...|#]
[#|2005-08-22T13:11:48.408+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
GreeterDBView JSP is executing...|#]
[#|2005-08-22T13:11:48.408+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
GreeterDBView JSP is all done|#]
[#|2005-08-22T13:11:48.418+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
- Dispatched JSP successfully|#]
[#|2005-08-22T13:11:48.418+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
GreeterDBServlet is all done
|#]
[#|2005-08-22T13:11:53.283+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
GreeterDBServlet is executing ...|#]
[#|2005-08-22T13:11:53.283+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
Retrieving JNDI initial context|#]
[#|2005-08-22T13:11:53.293+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
- Retrieved initial context successfully|#]
[#|2005-08-22T13:11:53.293+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
Getting datasource...|#]
[#|2005-08-22T13:11:53.293+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
- Got datasource successfully|#]
[#|2005-08-22T13:11:53.293+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
Getting connection|#]
[#|2005-08-22T13:11:53.644+0530|WARNING|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=15;|RAR5038:Unexpected exception while creating resource|#]
[#|2005-08-22T13:11:53.644+0530|WARNING|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=15;|RAR5117 : Failed to obtain/create connection. Reason : Connection could not be allocated because: ORA-01017: invalid username/password; logon denied
|#]
[#|2005-08-22T13:11:53.664+0530|WARNING|sun-appserver-pe8.1_02|javax.enterprise.resource.resourceadapter|_ThreadID=15;|RAR5114 : Error allocating connection : [Error in allocating a connection. Cause: Connection could not be allocated because: ORA-01017: invalid username/password; logon denied
]|#]
[#|2005-08-22T13:11:53.664+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.system.stream.out|_ThreadID=15;|
- Could not interact with the database|#]
[#|2005-08-22T13:11:53.674+0530|SEVERE|sun-appserver-pe8.1_02|javax.enterprise.system.container.web|_ThreadID=15;|StandardWrapperValve[GreeterDBLogDisplayServlet]: Servlet.service() for servlet GreeterDBLogDisplayServlet threw exception
java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key exception
 at java.util.ResourceBundle.getObject(ResourceBundle.java:326)
 at java.util.ResourceBundle.getString(ResourceBundle.java:286)
 at samples.jdbc.simple.servlet.GreeterDBLogDisplayServlet.doGet(Unknown Source)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:747)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:860)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:249)
 at java.security.AccessController.doPrivileged(Native Method)
 at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
 at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:282)
 at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:165)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:257)
 at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
 at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:161)
 at java.security.AccessController.doPrivileged(Native Method)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:263)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
 at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:225)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:173)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:132)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:551)
 at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:933)
 at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:185)
 at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:653)
 at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:534)
 at com.sun.enterprise.web.connector.grizzly.ProcessorTask.doTask(ProcessorTask.java:403)
 at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:55)
|#]
[#|2005-08-22T13:14:00.758+0530|WARNING|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. |#]
[#|2005-08-22T13:14:00.948+0530|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
D:/j2eesdk-1_4_02/jdk\bin\java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=D:/j2eesdk-1_4_02/domains/domain1/logs/server.log
-Dcom.sun.aas.verboseMode=true
-Djava.endorsed.dirs=D:/j2eesdk-1_4_02/lib/endorsed
-Djava.security.policy=D:/j2eesdk-1_4_02/domains/domain1/config/server.policy
-Djava.security.auth.login.config=D:/j2eesdk-1_4_02/domains/domain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=D:/j2eesdk-1_4_02/domains/domain1/config/keystore.jks
-Djavax.net.ssl.trustStore=D:/j2eesdk-1_4_02/domains/domain1/config/cacerts.jks
-Djava.ext.dirs=D:/j2eesdk-1_4_02/jdk/jre/lib/ext;D:/j2eesdk-1_4_02/domains/domain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=D:/j2eesdk-1_4_02/domains/domain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=D:/j2eesdk-1_4_02/config
-Djava.library.path=D:\j2eesdk-1_4_02\lib;D:\j2eesdk-1_4_02\lib;D:\j2eesdk-1_4_02\jdk\bin;.;C:\WINNT\system32;C:\WINNT;D:\j2eesdk-1_4_02\lib;D:\j2eesdk-1_4_02\bin;D:\j2eesdk-1_4_02\bin;D:\j2eesdk-1_4_02\bin;D:\oracle\ora81\lib;C:\j2sdk1.4.2_08\bin;D:\oracle\ora81\bin;C:\Program Files\Oracle\jre\1.1.7\bin;C:\Program Files\Oracle\jre\bin;c:\winnt;c:\winnt\system32;D:/j2eesdk-1_4_02/jdk/bin;D:/j2eesdk-1_4_02/lib;D:/j2eesdk-1_4_02/lib/locale;D:/JBuilder7/lib/bes;D:/j2eesdk-1_4_02/imq/lib/imqxm.jar;D:\j2eesdk-1_4_02\bin;D:/j2eesdk-1_4_02/bin
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
D:/j2eesdk-1_4_02/jdk/lib/tools.jar;D:/j2eesdk-1_4_02/lib/appserv-rt.jar;D:/j2eesdk-1_4_02/lib\activation.jar;D:/j2eesdk-1_4_02/lib\admin-cli.jar;D:/j2eesdk-1_4_02/lib\appserv-admin.jar;D:/j2eesdk-1_4_02/lib\appserv-cmp.jar;D:/j2eesdk-1_4_02/lib\appserv-ext.jar;D:/j2eesdk-1_4_02/lib\appserv-jstl.jar;D:/j2eesdk-1_4_02/lib\appserv-upgrade.jar;D:/j2eesdk-1_4_02/lib\commons-launcher.jar;D:/j2eesdk-1_4_02/lib\commons-logging.jar;D:/j2eesdk-1_4_02/lib\dom.jar;D:/j2eesdk-1_4_02/lib\j2ee-svc.jar;D:/j2eesdk-1_4_02/lib\j2ee.jar;D:/j2eesdk-1_4_02/lib\jax-qname.jar;D:/j2eesdk-1_4_02/lib\jaxr-api.jar;D:/j2eesdk-1_4_02/lib\jaxr-impl.jar;D:/j2eesdk-1_4_02/lib\jaxrpc-api.jar;D:/j2eesdk-1_4_02/lib\jaxrpc-impl.jar;D:/j2eesdk-1_4_02/lib\jmxremote.jar;D:/j2eesdk-1_4_02/lib\jmxremote_optional.jar;D:/j2eesdk-1_4_02/lib\jsf-api.jar;D:/j2eesdk-1_4_02/lib\jsf-impl.jar;D:/j2eesdk-1_4_02/lib\mail.jar;D:/j2eesdk-1_4_02/lib\relaxngDatatype.jar;D:/j2eesdk-1_4_02/lib\rmissl.jar;D:/j2eesdk-1_4_02/lib\saaj-api.jar;D:/j2eesdk-1_4_02/lib\saaj-impl.jar;D:/j2eesdk-1_4_02/lib\xalan.jar;D:/j2eesdk-1_4_02/lib\xercesImpl.jar;D:/j2eesdk-1_4_02/lib\xsdlib.jar;D:/j2eesdk-1_4_02/lib/install/applications/jmsra/imqjmsra.jar;D:/j2eesdk-1_4_02/imq/lib/jaxm-api.jar;D:/j2eesdk-1_4_02/imq/lib/fscontext.jar;D:/j2eesdk-1_4_02/lib/ant/lib/ant.jar;D:/j2eesdk-1_4_02/pointbase/lib/pbclient.jar;D:/j2eesdk-1_4_02/pointbase/lib/pbembedded.jar;${oracle.jdbc.lib.class.path}/ojdbc14.jar;${oracle.jdbc.lib.class.path}/ojdbc14_g.jar;${oracle.jdbc.lib.class.path}/ocrs12.zip
com.sun.enterprise.server.PEMain
stop
verbose|#]Cud someone tell me why am I getting this error?
Regards,
shipf1

Other solution:
on refresh period, default value is 1 minute, force this value at 0 and your connection
is ok.
Eric
Joseph Weinstein <[email protected]> wrote:
Redo the pool definition, and set 'test connection on reserve'. Don't
set 'test connections on release', and leave refresh minutes alone.
add a test table. DUAL is perfect for that. Everything else seems
fine.
Joe
Rafid wrote:
I am getting this error when I try to make a connection to an Oracle817DB.
I am using Oracles drviers (classes12.zip)
<Nov 2, 2001 2:05:18 PM EST> <Error> <JDBC> <Cannot startup connectionpool
"genPool" Test table must be specifed for genPool with 'test connectionon
reserve' or 'test connection on release' or 'refresh minutes' set higher
than 0.>
<Nov 2, 2001 2:05:18 PM EST> <Info> <JDBC> <Creating TX Data Sourcenamed
weblogic.jdbc.jts.genPool for pool genPool>
<Nov 2, 2001 2:05:18 PM EST> <Info> <JDBC> <Checking existence of connection
pool genPool requested by user system>
<Nov 2, 2001 2:05:18 PM EST> <Error> <JDBC> <Error during Data Source
creation: weblogic.common.ResourceException:
DataSource(weblogic.jdbc.jts.genPool) can't be created with non-existent
Pool (connection or multi) (genPool)>
I have created a connction pool called genPool,
set the URL :jdbc:oracle:thin:@genoracle:1521:GENORANY
driver class name = oracle.jdbc.driver.OracleDriver
Properties:
user=name ** where name is user
password=xx **where xx is password
dll=ocijdbc8
protocol=thin
I created the Tx Data Sources with
name = weblogic.jdbc.jts.genPool
jndi = weblogic.jdbc.jts.genPool
poolname = genPool
Can anyone help me through this, it would be a great help
Rafid Wahab

Error connecting multiple BW systems to one OLTP system

Hi BW Gurus,
As part of a major project we had to create a copy of our production BW system and thus have two BW systems connected to one production R/3 system. Before we proceed with the production systems, we decided to try it out with our staging systems.
1) Created a copy of STG BW (already connected to STG R/3) and renamed it to TST BW.
2) Transaction BDLS, renamed the logical system ID
3) Made sure all partner profiles were available and active
4) Since there was no connection between TST BW and R/3 STG, tried to activate the source system in TST BW. As per OSS note 886102, tried the restore functionality but we are running into a strange error.
Table RSBASIDOC in the source system already has an entry for STG R/3 and STG BW with IDOC TYP ZSSA015 and Prefix "SA" and now it complains that since this prefix alrady exists, it cannot create another entry with the same prefix for TST BW and STG R/3. It gives us the option to delete the existing entry and create a new one for TST BW. This in turn de-activates the delta between STG BW and STG R/3 and we can successfully initialize with the new system.
This process turned the queue entry in RSA7 red for STG BW and created a new one for TST BW (green). Delta stopped working for STG BW.
How can I have both the systems connected and run delta process simulataneously? I have read OSS note 775568 but this is after the fact that the two systems are already connected.
If I have to start from scratch, can someone please outline the steps involved?
Do I have to restore the source system or is there an alternate way? I cannot see how the delta would work if there is no connection betweeen the two systems.
Do I even need to worry about initializing with the TST BW System or can I just run the delta process and it would automatically add another entry in RSA7.
Any help would be truly appreciated and rewarded!!
Thank You.
Sreedhar

Looks like a much bigger issue than that. We did create the partner profile in WE20 but that didn't help either. It still complains about the prefix. This 2 Character prefix value is actually derived as the concatenation of the first letter of the BW system name and starting alphabet in a sequence. In our example STG BW has prefix of SA and the basic idoc type is ZSSA015. Based on this, TST BW system should have prefix of TA and basic idoc type might be ZSTA016. The program initially looks at RSBASIDOC table for source system and finds value SA and complains that this cannot be used again.
I have seen messages in this forum where people have actually done this and hopefully someone would reply back as to how to resolve this issue.
My main question though is, do we have to restore or activate or do not have to do anything to the source system after the copy of BW systems? None of the above three options seem to work for us right now.
Any ideas?
Thank You
Sreedhar

Error connecting SAP BW System using EP 6.0

Similar Messages

Maybe you are looking for