Datasource Postgresql problem

Dear colleagues,
We want to create a new Datasource in order to connect our Portal Application with a Postgresql DB.
We had been creating Datasources with Oracle before and everything was ok , but with Postgresql we are
experiencing some problems.
Firstly, we created a new jdbc driver in visual administrator console.
Secondly, we were trying to create a new datasource using the Postgresql driver but finished with error.
I would appreciate if someone have a clue to solve our problem.
Thanks in advance.
Oscar
This is a piece of error dump.
java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: Error during start of application "sap.com/JDBCConnector_DS_POST.xml". [id = StartupError]
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:608)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
     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:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: java.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 6280550:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "DS_POST".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4712)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
     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:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance ManagedConnectionFactoryImpl.
     at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:83)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1779)
     ... 42 more
Caused by: java.lang.ClassNotFoundException: postgresql.jdbc.driver.PostgresqlDriver
Loader Info -
ClassLoader name: [library:postgresql.jdbc.driver.PostgresqlDriver]
Parent loader name: [Frame ClassLoader]
No references !
Resources:
   /usr/sap/EPD/JC00/j2ee/cluster/server0/bin/core_lib/opensqlport.jar
   /usr/sap/EPD/JC00/j2ee/cluster/server0/bin/ext/postgresql.jdbc.driver.PostgresqlDriver/postgresql-8.4-701.jdbc3.jar
Loading model: {parent,local,references}
     at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:382)
     at com.sap.engine.services.dbpool.spi.ManagedConnectionFactoryImpl.<init>(ManagedConnectionFactoryImpl.java:74)
     ... 43 more
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:663)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
     ... 31 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 6280550:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "DS_POST".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)

Hi Oscar,
Your problem seems to be:
> Caused by: java.lang.ClassNotFoundException: postgresql.jdbc.driver.PostgresqlDriver
There might be different JDBC drivers for PostgreSQL, but for the one I know (http://jdbc.postgresql.org/) the driver class is: org.postgresql.Driver
Hope it helps
Detlev

Similar Messages

Datasource Configuration problem with Tomcat-4.0.3

Hi All !
When I trying to open connection to my DB2 database in tomcat -4.0.3,
I have put db2java.jar in /usr/local/jakartha-tomcat-4.03/common/lib directory
when I am trying to connect Database through my servlet getting expections
java.lang.NullPointerException: at DataSource ds = (DataSource)envContext.lookup("jdbc/SmsDBDS");
here is my dbconnection class
package com.ebizon.util.jdbc;
import java.sql.*;
import java.util.*;
import javax.naming.*;
import javax.sql.*;
public class DBUtil {
/* Ebizon DB Connection for Tomcat */
public static Connection getEbizDBConnection() throws NamingException, SQLException {
Connection conn = null;
try {
InitialContext initCtx = new InitialContext();
Context envContext = (Context)initContext.lookup("java:/comp/env");
DataSource ds = (DataSource)envContext.lookup("jdbc/SmsDBDS");
conn = ds.getConnection();
} catch (NamingException ne) {
throw ne;
} catch (SQLException se) {
throw se;
return conn;
And my resource definition in server.xml (/usr/local/jakartha-tomcat-4.0.3/conf/server.xml)
<Context path="/DBTest" docBase="DBTest"
debug="5" reloadable="true" crossContext="true">
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="localhost_DBTest_log." suffix=".txt"
timestamp="true"/>
<Resource name="jdbc/SmsDBDS"
auth="Container"
type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/SmsDBDS">
<parameter>
<name>factory</name>
<value>org.apache.commons.dbcp.BasicDataSourceFactory</value>
</parameter>
<parameter>
<name>maxActive</name>
<value>100</value>
</parameter>
<parameter>
<name>maxIdle</name>
<value>30</value>
</parameter>
<parameter>
<name>maxWait</name>
<value>10000</value>
</parameter>

<parameter>
<name>username</name>
<value>smsdb</value>
</parameter>
<parameter>
<name>password</name>
<value>smsdb</value>
</parameter>

<parameter>
<name>driverClassName</name>
<value>COM.ibm.db2.jdbc.app.DB2Driver</value>
</parameter>
<parameter>
<name>url</name>
<value>jdbc:db2:smsdb</value>
</parameter>
</ResourceParams>
</Context>
this is my Web Application descriptor /WEB-INF/web.xml
<resource-ref>
<description>
Resource reference to a factory for java.sql.Connection
instances that may be used for talking to a particular
database that is configured in the server.xml file.
</description>
<res-ref-name>
jdbc/EmployeDB
</res-ref-name>
<res-type>
javax.sql.DataSource
</res-type>
<res-auth>
Container
</res-auth>
</resource-ref>
Please look at once above , Do i missing any thing?
Anyhelp is greatly appreciate
Many thanks in advance
With Regards
Madhu Reddy

I don't see any problem with your files, so unfortunately I can't help. Since this forum is about the J2EE SDK, people may not have that much experience with standalone Tomcat. You may want to try the Tomcat user mailing list for a question about Tomcat: http://jakarta.apache.org/site/mail2.html

Post Refresh datasource Activation problems

Hello all,
After refreshing my sandbox from my dev system, the datasources are all inactive. I've run the BDLS, recreated the source system connection, run the 'replicate/activate', run the program for activating all transfer rules, etc.
When I go through the datasources one by one, I can 'change' and then activate through RSA1. This sets the M version to match the A version.
Is there a report that will set the M version to match the A version, and successfully activate all my datasources? I would really not like to do them one by one.

Yes, but I'm having some trouble with it. When I run it, it throws a 'Problem Class Important" - 'No transfer structure selected'
I don't see where to populate that.
edit:
I managed to get the program to run by leaving the source system out of the variables. Now, it runs, and activates a portion of my datasources, but not all.
Message was edited by:
Kenneth P

Multi datasource faliover problem - JDeveloper integrated Weblogic 10.3.5

Hi all,
I have a problem with JDeveloper integrated weblogic (version 10.3.5) fail over to second datasource in multi data source (2 generic datasources) configuration environment.
My test goes like this:
1. I have two databases running on separate servers.
2. both data sources are up & running OK.
3. JDeveloper integrated weblogic configured with multi datasource, using algorithm failover, and failover callback class.
4. weblogic started and adf application running using first datasource in list.
5. if I unplug network cable or shut down first database, weblogic won't fail over to second datasource and still trying to use the first one.
Failover callback class:
package failover;
public class ConnectionPoolFailoverCallback implements weblogic.jdbc.extensions.ConnectionPoolFailoverCallback {
     static {
          System.out.println("------------------------------------------------------------");
          System.out.println("\n\n\tConnectionPoolFailoverCallback class initiated...\n\n\t");
          System.out.println("------------------------------------------------------------");
     public int allowPoolFailover(String currPool, String nextPool, int opcode) {
          System.out.println("Current Pool - " + currPool);
          System.out.println("Next Pool - " + nextPool);
          System.out.println("Operation Code - " + opcode);
          System.out.println("------------------------------------------------------------");
          if (opcode == OPCODE_CURR_POOL_DEAD) {
               System.out.println("\n\n\tConnectionPoolFailoverCallback     return OK.");
               return OK;
          } else {
               System.out.println("\n\n\tConnectionPoolFailoverCallback     return DONOT_FAILOVER.");
               return DONOT_FAILOVER;
}{code}
*Problem:* When I unplug network cable or shutdown first database, method allowPoolFailover returns OK, but weblogic won't switch to second datasource entering allowPoolFailover method again and again.
+Note:+ weblogic integrated in JDeveloper is running u development mode.
Did I miss something in configuration or something else?
Any help is appreciated.
Thanks in advance,
Alexandar

Hi Alexandar,
Have you made any progress with this? We seem to have bumped into this issue as well. Connection requests are consistently routed to the disabled pool (it appears as disabled in the WLS console, but we can see the counters increasing steadily), the callback handler is called and returns OK, and the connection request is ultimately serviced by the active pool. So while the application still successfully handles requests, there's obviously an underlying problem in obtaining the connection.
Thanks,
Sebastien

[SOLVED] postgreSQL problems

Hi!
I have some problems with postgreSQL. When I run /etc/rc.d/postgresql start it says server starting [DONE]. There is no postgresql process and when I run /etc/postgresql stop it says pg_ctl: PID file "var/lib/postgres/data/postmaster.pid" does not exist
Is server running? [FAIL]. I tried to run the postmaster, but it couldn't find data files.
How can I fix this?
Thanks in advance,
-skazhy
Last edited by skazhy (2010-04-21 05:27:46)

postgres cannot access the server configuration file "/var/lib/postgres/data/postgresql.conf": No such file or directory
postgres cannot access the server configuration file "/var/lib/postgres/data/postgresql.conf": No such file or directory
postgres cannot access the server configuration file "/var/lib/postgres/data/postgresql.conf": No such file or directory
postgres cannot access the server configuration file "/var/lib/postgres/data/postgresql.conf": No such file or directory
postgres cannot access the server configuration file "/var/lib/postgres/data/postgresql.conf": No such file or directory
postgres cannot access the server configuration file "/var/lib/postgres/data/postgresql.conf": No such file or directory
postgres cannot access the server configuration file "/var/lib/postgres/data/postgresql.conf": No such file or directory
postgres cannot access the server configuration file "/var/lib/postgres/data/postgresql.conf": No such file or directory
postgres cannot access the server configuration file "/var/lib/postgres/data/postgresql.conf": No such file or directory
FATAL: data directory "/var/lib/postgres/data" has group or world access
DETAIL: Permissions should be u=rwx (0700).
I copied .conf files to /var/lib/postgres/data but still, it cant found it. I changed permissions to 700 too, but it still doesnt work :(
FATAL: data directory "/var/lib/postgres/data" has group or world access
DETAIL: Permissions should be u=rwx (0700).
FATAL: data directory "/var/lib/postgres/data" has group or world access
DETAIL: Permissions should be u=rwx (0700).

Generic Datasource creation problem..Please Help

There is a problem in creating a generic datasource.It doesnt permit us to create a DS on table EKBE
.(error states that solution is create a view or DDIC).
We created a view on four tables ( including all tables EKBE is referencing).EKBE has only 842 records.But the view created has 23400 recs.
The table names are
EKPO
EKKO
EKBE(references the other tables mentioned)
T001
.How do we solve this problem?Help needed .
Edited by: Prathibha Pillai on Apr 11, 2008 6:17 AM

Greetings,
hi
I am getting an javax.naming.InvalidNaming exception
I am using the expression java:comp/env/jdbc/myAtmDBThe 'lookup name' "jdbc/myAtmDB" is not set in your bean's environment. This should be set as the res-ref-name in your deployment descriptor...
i have set jdbc/Cloudscape as the jndi name in the
propertyThis, presumably, is the JNDI binding name by which your application server knows to find the resource. This, however, must be linked to your bean's "resource reference lookup name" (above). How to make the "link" is vendor specific so read your vendor docs.
please can anyone tell me how to go about it.
thanks
swaroopRegards,
Tony "Vee Schade" Cook

0hr_py_1 datasource extraction problem

Friends,
I am trying to extract data for 0hr_py_1 datasource and having issues.
After activation, when i go in R3 to check in rsa3, it says 0 records.
What i know is that HR extraction is simple and you just have to activate the datasource and replicate Metdata. I am not sure of any other steps...can anybody help. Are their any additional steps on R3 to be performed ????????

Hi,
Check if you are extracting in full mode in RSA3 and if you still don't get data, try to debug the extractor and see at which step it is not getting data.
From this you will get to know which are the tables / FM involved in data selection.
Regards,
Durgesh.

FLAT FILE Datasource SERIOUS Problem

Hi
I want to read a header information in csv file to fill the FLAT FILE DATASOURCE structure.
I cannot read it by default as I have to IGNORE THE HEADER ROW otherwise it wont come up correctly along with otherdetail data that is below header row during extraction of CSV file.
How can i do that or How can I CALL A Function module or any other to fetch that header row ?
PLEASE HELP URGENTLY.
Thanks

you cannot read the header row only. But you can do a start routine within the transfer rules. There you can do whatever you like.
Perhaps you might have some troubles getting your data that far. Your header row must comply to the rules defined in your datasource like size or data type. So you might need to change some definitions of your datasource.

JNDI DataSource Configuration Problem

I configured the Tomcat so that I can use a Datasource to access a database according to the JNDI HOW TO instructions.
I installed JDBC driver in %catalina_home%/common/lib, modified the web.xml in /WEB-INF and server.xml in /conf and coded the JSP page according to the instruction.
But I get the following error when I run the app.
Why this happens?
org.apache.jasper.JasperException: Unable to compile class for JSP
An error occurred between lines: 14 and 33 in the jsp file: /jsp/track/ds-test.jsp
Generated servlet error:
C:\jakarta-tomcat-4.0.3\work\localhost\examples\jsp\track\ds_0002dtest$jsp.java:64: Class org.apache.jsp.Context not found.
Context initCtx = new InitialContext();
^
An error occurred between lines: 14 and 33 in the jsp file: /jsp/track/ds-test.jsp
Generated servlet error:
C:\jakarta-tomcat-4.0.3\work\localhost\examples\jsp\track\ds_0002dtest$jsp.java:64: Class org.apache.jsp.InitialContext not found.
Context initCtx = new InitialContext();
^
An error occurred between lines: 14 and 33 in the jsp file: /jsp/track/ds-test.jsp
Generated servlet error:
C:\jakarta-tomcat-4.0.3\work\localhost\examples\jsp\track\ds_0002dtest$jsp.java:66: Class org.apache.jsp.Context not found.
Context envCtx = (Context) initCtx.lookup("java:comp/env");
^
An error occurred between lines: 14 and 33 in the jsp file: /jsp/track/ds-test.jsp
Generated servlet error:
C:\jakarta-tomcat-4.0.3\work\localhost\examples\jsp\track\ds_0002dtest$jsp.java:66: Class org.apache.jsp.Context not found.
Context envCtx = (Context) initCtx.lookup("java:comp/env");
^
4 errors

I imported the JNDI classes but I get a new error.
java.lang.NullPointerException
     at org.apache.jsp.ds_0002dtest$jsp._jspService(ds_0002dtest$jsp.java, Compiled Code)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:202)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java, Compiled Code)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java, Compiled Code)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:475)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.StandardContext.invoke(StandardContext.java, Compiled Code)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java, Compiled Code)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java, Compiled Code)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
     at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java, Compiled Code)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java, Compiled Code)
     at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java, Compiled Code)
     at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java, Compiled Code)
     at java.lang.Thread.run(Thread.java:472)

Datasource creation problem in 7.0 with demo version?

hi friends,
i installed netweaver demo version.
i created infoare and info objects
In the left panel select data sources
Create application component(AC)
Right click AC and create datasource
in left panel i selected datasources , i went in right panil, i am unable to find create application component, its shoing options replicate metadata. how can i create application component, please help me.
regards
suneel.

if the datasource is pointing to a R/3 source system, you cant create a application component - rather you need to replicate it. So make sure you are seeing the datasources in flat file source system - Icon with X mark (choose source system - in the top panel of icons)- click on it and select file system - then clcik on it and it will give you a option to create a AC

FISL Datasource Screen Problem........Please Help me

Hi All,
I have generated Extract structure for FISL Tables like GLFUNCT.....after generating this, i got the message that, "2 Extract Structures for table GLFUNCT was generated"
Now, "<b>i am trying to Assign FISL Datasource to a Leadger using BW03.....
After giving t-code.... Screen is showing empty, there is no any list of information</b>"
Please anybody help me this is very urgent....
Your help will be appriciated....
Regards,
Kiran Telkar

Hi
You should make a mapping for the service sapmsPRD in your /etc/services file (On Windows: C:WINDOWSSYSTEM32DRIVERSETCservices). If your instance number is 00 you will have to add the following entry:
sapmsPRD 3600/tcp
Good luck!
René van Es

Sun App Sever 8.1 / JNDI - datasource lookup problems

I get an error when calling the ctx.lookup function. I have the datasource and the resource set up in the server OK. I can ping successfully and view the table data. I am using NetBeans 4.1 / Sun 8.1
I have been up all night (11pm - 4:30am) trying to figure this out.
    <%
        java.sql.Connection conn = null;
        java.util.Hashtable env = new java.util.Hashtable();
        javax.naming.Context ctx ;
        javax.sql.DataSource cachedDataSource;
        try {
        env.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.cosnaming.CNCtxFactory");
        ctx = new javax.naming.InitialContext();
        cachedDataSource = (javax.sql.DataSource)ctx.lookup("jdbc/mysql");
        if (cachedDataSource == null)
            {out.println("<h2>The datasource is not getting set properly</h2>");
            conn = cachedDataSource.getConnection();}
        else
        { out.println("<h2>the datasource is not null and seems like it gets initialized.<h2>"); }
        } catch (javax.naming.NamingException ne) {}
          catch (java.sql.SQLException se) {}
        env = null;
        ctx = null;
        conn.close();
        conn = null;
        cachedDataSource = null;
    %>

RTFM
http://docs.sun.com/app/docs/doc/819-0079
The resource lookup in the application code looks like this:
InitialContext ic = new InitialContext();
String dsName = "java:comp/env/jdbc/HelloDbDs";
DataSource ds = (javax.sql.DataSource)ic.lookup(dsName);
Connection connection = ds.getConnection();
The resource being queried is listed in the res-ref-name element of the web.xml file as follows:
<resource-ref>
<description>DataSource Reference</description>
<res-ref-name>jdbc/HelloDbDs</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
The resource-ref section in a Sun Java System specific deployment descriptor, for example sun-web.xml, maps the res-ref-name (the name being queried in the application code) to the JNDI name of the JDBC resource. The JNDI name is the same as the name of the JDBC resource as defined in the resource file when the resource is created.
<resource-ref>
<res-ref-name>jdbc/HelloDbDs</res-ref-name>
<jndi-name>jdbc/HelloDbDataSource</jndi-name>

Struts-Hibernate Postgresql problem

Hi all!,
i have been developing a web application using struts-hibernate concept with postgresql as database., (Postgres- 7.3.2, Hibernate- 2.0, MyEclipse     - 3.1.2)
When i insert the value the following error occurs,
root cause
java.lang.ArrayIndexOutOfBoundsException: 1
     org.postgresql.core.QueryExecutor.sendQuery(QueryExecutor.java:143)
     org.postgresql.core.QueryExecutor.execute(QueryExecutor.java:65)
     org.postgresql.jdbc1.AbstractJdbc1Connection.ExecSQL(AbstractJdbc1Connection.java:451)
     org.postgresql.jdbc1.AbstractJdbc1Statement.execute(AbstractJdbc1Statement.java:281)
     org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:48)
     org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1Statement.java:179)
     org.postgresql.jdbc1.AbstractJdbc1Statement.executeUpdate(AbstractJdbc1Statement.java:165)
     org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:80)
     org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:57)
     org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:174)
     org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:226)
     org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:136)
     org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:274)
     org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
     org.hibernate.impl.SessionImpl.flush(SessionImpl.java:730)
     org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:324)
     org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:86)
     com.etm.manager.DistrictLoginUserManager.saveDistrictLoginUser(DistrictLoginUserManager.java:162)
     com.etm.struts.action.DistrictLoginEditAction.saveDistrictLogin(DistrictLoginEditAction.java:60)
     sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     java.lang.reflect.Method.invoke(Method.java:585)
     org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:280)
     org.apache.struts.actions.DispatchAction.execute(DispatchAction.java:216)
     org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
     org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
     org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
     org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
     javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
thanks in advance,

Here is my code:
public void saveDistrictLoginUser(DistrictLoginUser districtloginuserValue) {
          // a Hibernate session
          Session session = null;
          Transaction tx = null;
          try {
               // get session of the current thread
               session=ETMSessionFactory.currentSession();
               tx = session.beginTransaction();
               DistrictLoginUser districtloginuser;
               if (districtloginuserValue.getDistrictloginid() != null && districtloginuserValue.getDistrictloginid().intValue() != 0) {
                    districtloginuser = (DistrictLoginUser)session.get(DistrictLoginUser.class,districtloginuserValue.getDistrictloginid());
                    if (districtloginuser != null) {
                         districtloginuser.setDistrictid(districtloginuserValue.getDistrictid());
                         districtloginuser.setDistrictusername(districtloginuserValue.getDistrictusername());
                         districtloginuser.setDistrictpassword(districtloginuserValue.getDistrictpassword());
                         districtloginuser.setDistrictfirstname(districtloginuserValue.getDistrictfirstname());
                         districtloginuser.setDistrictemail(districtloginuserValue.getDistrictemail());
                         districtloginuser.setDistrictdesignation(districtloginuserValue.getDistrictdesignation());
                         session.update(districtloginuser);
               else
                    districtloginuser = new DistrictLoginUser();
                    districtloginuser.setDistrictid(districtloginuserValue.getDistrictid());
                    districtloginuser.setDistrictusername(districtloginuserValue.getDistrictusername());
                    districtloginuser.setDistrictpassword(districtloginuserValue.getDistrictpassword());
                    districtloginuser.setDistrictfirstname(districtloginuserValue.getDistrictfirstname());
                    districtloginuser.setDistrictemail(districtloginuserValue.getDistrictemail());
                    districtloginuser.setDistrictdesignation(districtloginuserValue.getDistrictdesignation());
                    session.save(districtloginuser);
               tx.commit();
          } catch (HibernateException e) {
               e.printStackTrace();
               // it is recommended to roll back the transaction after an error occured
               if (tx != null) try {
                    tx.rollback();
               } catch (HibernateException e1) {
                    e1.printStackTrace();
          } finally {
               try {
                    if (session != null) session.close();
               } catch (HibernateException e1) {
                    e1.printStackTrace();
here when i commit the tx it gives the error.,

Datasource activation problem in SCM APO 5.1

Dear friends,
I am working in APO5.1 and creating a cube with using datasource from BW side (8ODS_EPDTL).
1. Source system --> replicate Datasources (in BW 3.X) (My client requirement.)
While activate datasouce, it saying need to create Transfer rules..if i create it also data source is not activating..
if i don't wont to create TR then it now coming to change mode.
If i create TR rules at datasource it will be come infosource system na,,,, i can't assign to my APO Communication structure.
so want have to do..and how i can activate my Datasource(8ODS_EPDTL)
Please help me..
Regards
Srinivasarao

solved

Datasource Assignment Problem in BW 3.5 ( URGENT Please)

Hi Guys,
We have migrated some data sources to BI 7.0 which have been created in BW 3.5. After some point of time we have deleted source system(flat file) in BW 3.5 and we tried to again assign the same source system. Here we are getting a peccular error like
1.DataSource /ACN/PPROCESS_ATTR does not exist in source
system /ACN/PFFSS of version A
2.Field /ACN/S_PPROCESS will not be delivered from DataSource /ACN/PPROCESS_ATTR in source system /ACN/PFFSS
System Describes...
Field /ACN/S_PPROCESS will not be delivered from DataSource /ACN/PPROCESS_ATTR in source system /ACN/PFFSS
Message no. RSAOLTP007
Diagnosis
The DataSource replica /ACN/PPROCESS_ATTR does not contain the field /ACN/S_PPROCESS.
System Response
A transfer rule is not possible for this field.
Procedure
Check whether the DataSource /ACN/PPROCESS_ATTR contains this field in source system /ACN/PFFSS, or whether the field in the DataSource has been hidden, to exclude it from data transfer. If the field in the data source does not exist, or if it was excluded from data transfer, correct the DataSource manually. You do this by (re) transferring from the Content or by importing from a development system. In all cases, repliciate the DataSource into BW (even when it is correct in the source system).
Thanks in advance
peter

Peter,
I think because source system deletion, it got inconsistent. I would like you to go back to 3.X Datasource and assing source system. activate all the Transfer Rules etc. then Migrate your Datasource to BI 7.0 again. If it is still giving any issues, try creating in BI7.0 directly.
all the best.
Regards,
Nagesh Ganisetti.

Datasource Postgresql problem

Similar Messages

Maybe you are looking for