E possível configurar 2 conexões do persistence.xml?

E possível configurar 2 conexões do persistence.xml ?

se caso for possível ai necessito de configurar os datasources e drive no diterorio no meu caso Jboss ?

se alguém pode dar um exemplo de como pode ficar essa configuração no Persistence.xml

Sim.

Sim.

É só você ter 2 tags persistence-unit

Aqui mostra: JPA: Mini Livro - Primeiros passos e conceitos detalhados.

No exemplo mostra duas conexões locais, mas c você estiver utilizando JBoss, será necessário criar os datasources e apontar de dentro do EM igualmente como se fosse feito com um EM apenas.

“E possível configurar 2 conexões do persistence.xml ?”

Siim, você tem que criar dois PU no persistence.xml

“se caso for possível ai necessito de configurar os datasources e drive no diterorio no meu caso Jboss ?”

Sim, você precisa ter os dois datasources no JBoss.

Esses dias precisei pegar dados do MySQL e SQL Server e fiz esse tipo de configuração.

Abs

Estou fazendo a configuração e esta dando essa Msg quando inicio o Jboss

JBAS014775:    New missing/unsatisfied dependencies:
      service jboss.jdbc-driver.oracle (missing) dependents: [service jboss.data-source.java:/DSTESTE] 

Como eu corrigir isso ?

Crie o datasource.

service jboss.data-source.java:/DSTESTE

Já criei o DataSource conforme abaixo no arquivo standalone.xml

                <datasource jta="false" jndi-name="java:/DSTESTE" pool-name="DSTESTE-RAC" enabled="true" use-ccm="false">
                    <connection-url>jdbc:oracle:thin:@server:1521:Data base</connection-url>
                    <driver>oracle</driver>
                    <security>
                        <user-name>user</user-name>
                        <password>senha</password>
                    </security>
                    <statement>
                        <prepared-statement-cache-size>100</prepared-statement-cache-size>
                        <share-prepared-statements>true</share-prepared-statements>
                    </statement>
                </datasource>
				
				     <driver name="oracle" module="com.oracle.ojdbc6">
                        <xa-datasource-class>oracle.jdbc.OracleDriver</xa-datasource-class>
                    </driver>

e criei o arquivo module.xml e no mesmo diretório deste arquivo adicionei o jar de conexão do Oracle

<?xml version="1.0" encoding="UTF-8"?>  
 <module xmlns="urn:jboss:module:1.0" name="com.oracle.ojdbc14">
  <resources>
    <resource-root path="ojdbc14.jar"/>
  </resources>
  <dependencies>
    <module name="javax.api"/>
  </dependencies>
</module>

Em relação ao driver você pode simplesmente realizar o deploy se for JDBC 4 compliant. Não é necessário criar um módulo para isso.

Qualquer JDBC 4 compliant driver será automaticamente reconhecido e instalado no sistema pelo nome e pela versão do Java service provider.
Um JDBC 4 compliant driver possui um arquivo no META-INF/services/java.sql.Driver contendo o fully qualified class name do driver JDBC em questão.

Nao sei no oracle mas a versão do connector j do MySQL5.1.22 já é JDBC 4 compliant.

Mas é isso ai…

Abs

E outra coisa… no module.xml vc declara assim:

name="com.oracle.ojdbc14">

e no standalone.xml ou domain.xml nao sei qual vc está utilizando vc chama assim:

module="com.oracle.ojdbc6">

Isso está correto?

Abs

Feras fiz a alteração na declaração dos nomes nos xml standalone.xml e module.xml conforme abaixo e nao surtiu efeito

standalone.xml

                <datasource jndi-name="java:/DSTESTE" pool-name="OracletDS_pool" enabled="true" use-java-context="true">
                    <connection-url>jdbc:oracle:thin:@server:1521:DSTESTE</connection-url>
                    <driver>oracle</driver>
                    <security>
                        <user-name>user</user-name>
                        <password>senha</password>
                    </security>
                </datasource>
                <drivers>
                    <driver name="oracle" module="com.oracle.jdbc">
                        <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
                        <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
                    </driver>
                </drivers>

module.xml

<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="com.oracle.jdbc">
  <resources>
    <resource-root path="ojdbc14.jar"/>
  </resources>
  <dependencies>
    <module name="javax.api"/>
    <module name="javax.transaction.api"/>
  </dependencies>
</module>

Quantos ao JDBC 4 compliant qual seria a diferença dele e o modulo que eu criei para o deploy ?

pois tirei o modulo que eu criei mais continuo com o aviso quando inicio o Jboss

JBAS014775:    New missing/unsatisfied dependencies:
      service jboss.jdbc-driver.oracle (missing) dependents:

Se fosse JDBC 4 compliant você poderia simplesmente pegar o driver e deployar no diretório deployments… JBOSS_HOME/standalone/deployments/

Eu nao trabalho com Oracle mas acredito que o driver ojdbc6 seja compativel.

Dá uma olhada no post desse cara… acho que pode ajudar :slight_smile:

http://www.thiagovespa.com.br/blog/2011/10/06/data-souce-oracle-no-jboss-as-7/

Abs

Se você nao estiver utilizando Two-Phase Commit o driver nao precisa ser XA entao pode remover a conf abaixo:

 <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>  

E se for XA você precisa modificar todo o data source por exemplo:

<xa-datasource jndi-name ... <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class> ... </xa-datasource>

Abs

Feras,

eu já tinha achado esse link http://www.thiagovespa.com.br/blog/2011/10/06/data-souce-oracle-no-jboss-as-7/ e parei no problema abaixo

JBAS014775:    New missing/unsatisfied dependencies:
      service jboss.jdbc-driver.oracle (missing) dependents: [service jboss.data-source.java:/DSTESTE] 

eu tentei tb tirar a linha <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class> mas tb não deu certo

alguém tem mais alguma sugestão ?

Olá,

Tem como vc postar o seu datasource, o seu persistence e qual a versão do driver está utilizando?

Obrigado.

A versão do drive e ojdbc14.jar

segue meu stadalone.xml

<?xml version='1.0' encoding='UTF-8'?>

<server xmlns="urn:jboss:domain:1.2">

    <extensions>
        <extension module="org.jboss.as.clustering.infinispan"/>
        <extension module="org.jboss.as.configadmin"/>
        <extension module="org.jboss.as.connector"/>
        <extension module="org.jboss.as.deployment-scanner"/>
        <extension module="org.jboss.as.ee"/>
        <extension module="org.jboss.as.ejb3"/>
        <extension module="org.jboss.as.jaxrs"/>
        <extension module="org.jboss.as.jdr"/>
        <extension module="org.jboss.as.jmx"/>
        <extension module="org.jboss.as.jpa"/>
        <extension module="org.jboss.as.logging"/>
        <extension module="org.jboss.as.mail"/>
        <extension module="org.jboss.as.naming"/>
        <extension module="org.jboss.as.osgi"/>
        <extension module="org.jboss.as.pojo"/>
        <extension module="org.jboss.as.remoting"/>
        <extension module="org.jboss.as.sar"/>
        <extension module="org.jboss.as.security"/>
        <extension module="org.jboss.as.threads"/>
        <extension module="org.jboss.as.transactions"/>
        <extension module="org.jboss.as.web"/>
        <extension module="org.jboss.as.webservices"/>
        <extension module="org.jboss.as.weld"/>
    </extensions>

    <management>
        <security-realms>
            <security-realm name="ManagementRealm">
                <authentication>
                    <properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/>
                </authentication>
            </security-realm>
            <security-realm name="ApplicationRealm">
                <authentication>
                    <properties path="application-users.properties" relative-to="jboss.server.config.dir"/>
                </authentication>
            </security-realm>
        </security-realms>
        <management-interfaces>
            <native-interface security-realm="ManagementRealm">
                <socket-binding native="management-native"/>
            </native-interface>
            <http-interface security-realm="ManagementRealm">
                <socket-binding http="management-http"/>
            </http-interface>
        </management-interfaces>
    </management>

    <profile>
        <subsystem xmlns="urn:jboss:domain:logging:1.1">
            <console-handler name="CONSOLE">
                <level name="INFO"/>
                <formatter>
                    <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
                </formatter>
            </console-handler>
            <periodic-rotating-file-handler name="FILE">
                <formatter>
                    <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
                </formatter>
                <file relative-to="jboss.server.log.dir" path="server.log"/>
                <suffix value=".yyyy-MM-dd"/>
                <append value="true"/>
            </periodic-rotating-file-handler>
            <logger category="com.arjuna">
                <level name="WARN"/>
            </logger>
            <logger category="org.apache.tomcat.util.modeler">
                <level name="WARN"/>
            </logger>
            <logger category="sun.rmi">
                <level name="WARN"/>
            </logger>
            <logger category="jacorb">
                <level name="WARN"/>
            </logger>
            <logger category="jacorb.config">
                <level name="ERROR"/>
            </logger>
            <root-logger>
                <level name="INFO"/>
                <handlers>
                    <handler name="CONSOLE"/>
                    <handler name="FILE"/>
                </handlers>
            </root-logger>
        </subsystem>
        <subsystem xmlns="urn:jboss:domain:configadmin:1.0"/>
        <subsystem xmlns="urn:jboss:domain:datasources:1.0">
            <datasources>
                <datasource jta="true" jndi-name="java:/catalina" pool-name="my_pool" enabled="true" use-java-context="true" use-ccm="true">
                    <connection-url>jdbc:mysql://localhost:3306/catalina</connection-url>
                    <driver>mysql</driver>
                    <security>
                        <user-name>root</user-name>
                        <password>admin</password>
                    </security>
                    <statement>
                        <prepared-statement-cache-size>100</prepared-statement-cache-size>
                        <share-prepared-statements>true</share-prepared-statements>
                    </statement>
                </datasource>
                <datasource jndi-name="java:/DSTESTE" pool-name="OracletDS_pool" enabled="true" use-java-context="true" use-ccm="true">
                    <connection-url>jdbc:oracle:thin:@servidor:1521:HOMOLOG</connection-url>
                    <driver>oracle</driver>
                    <security>
                        <user-name>user</user-name>
                        <password>senha</password>
                    </security>
                </datasource>
                <drivers>
                    <driver name="mysql" module="com.mysql">
                        <xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>
                    </driver>
                    <driver name="oracle" module="com.oracle.jdbc">
                        <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
                    </driver>
                </drivers>
            </datasources>
        </subsystem>
        <subsystem xmlns="urn:jboss:domain:ee:1.0"/>
        <subsystem xmlns="urn:jboss:domain:ejb3:1.2">
            <session-bean>
                <stateless>
                    <bean-instance-pool-ref pool-name="slsb-strict-max-pool"/>
                </stateless>
                <stateful default-access-timeout="20000" cache-ref="simple"/>
                <singleton default-access-timeout="20000"/>
            </session-bean>
            <pools>
                <bean-instance-pools>
                    <strict-max-pool name="slsb-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="20" instance-acquisition-timeout-unit="MINUTES"/>
                    <strict-max-pool name="mdb-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="20" instance-acquisition-timeout-unit="MINUTES"/>
                </bean-instance-pools>
            </pools>
            <caches>
                <cache name="simple" aliases="NoPassivationCache"/>
                <cache name="passivating" passivation-store-ref="file" aliases="SimpleStatefulCache"/>
            </caches>
            <passivation-stores>
                <file-passivation-store name="file"/>
            </passivation-stores>
            <async thread-pool-name="default"/>
            <timer-service thread-pool-name="default">
                <data-store path="timer-service-data" relative-to="jboss.server.data.dir"/>
            </timer-service>
            <remote connector-ref="remoting-connector" thread-pool-name="default"/>
            <thread-pools>
                <thread-pool name="default">
                    <max-threads count="10"/>
                    <keepalive-time time="100" unit="milliseconds"/>
                </thread-pool>
            </thread-pools>
        </subsystem>
        <subsystem xmlns="urn:jboss:domain:infinispan:1.2" default-cache-container="hibernate">
            <cache-container name="hibernate" default-cache="local-query">
                <local-cache name="entity">
                    <transaction mode="NON_XA"/>
                    <eviction strategy="LRU" max-entries="10000"/>
                    <expiration max-idle="100000"/>
                </local-cache>
                <local-cache name="local-query">
                    <transaction mode="NONE"/>
                    <eviction strategy="LRU" max-entries="10000"/>
                    <expiration max-idle="100000"/>
                </local-cache>
                <local-cache name="timestamps">
                    <transaction mode="NONE"/>
                    <eviction strategy="NONE"/>
                </local-cache>
            </cache-container>
        </subsystem>
        <subsystem xmlns="urn:jboss:domain:jaxrs:1.0"/>
        <subsystem xmlns="urn:jboss:domain:jca:1.1">
            <archive-validation enabled="true" fail-on-error="true" fail-on-warn="false"/>
            <bean-validation enabled="true"/>
            <default-workmanager>
                <short-running-threads>
                    <core-threads count="50"/>
                    <queue-length count="50"/>
                    <max-threads count="50"/>
                    <keepalive-time time="10" unit="seconds"/>
                </short-running-threads>
                <long-running-threads>
                    <core-threads count="50"/>
                    <queue-length count="50"/>
                    <max-threads count="50"/>
                    <keepalive-time time="10" unit="seconds"/>
                </long-running-threads>
            </default-workmanager>
            <cached-connection-manager/>
        </subsystem>
        <subsystem xmlns="urn:jboss:domain:jdr:1.0"/>
        <subsystem xmlns="urn:jboss:domain:jmx:1.1">
            <show-model value="true"/>
            <remoting-connector/>
        </subsystem>
        <subsystem xmlns="urn:jboss:domain:jpa:1.0">
            <jpa default-datasource=""/>
        </subsystem>
        <subsystem xmlns="urn:jboss:domain:mail:1.0">
            <mail-session jndi-name="java:jboss/mail/Default">
                <smtp-server outbound-socket-binding-ref="mail-smtp"/>
            </mail-session>
        </subsystem>
        <subsystem xmlns="urn:jboss:domain:naming:1.1"/>
        <subsystem xmlns="urn:jboss:domain:osgi:1.2" activation="lazy">
            <properties>
                <property name="org.osgi.framework.startlevel.beginning">
                    1
                </property>
            </properties>
            <capabilities>
                <capability name="javax.servlet.api:v25"/>
                <capability name="javax.transaction.api"/>
                <capability name="org.apache.felix.log" startlevel="1"/>
                <capability name="org.jboss.osgi.logging" startlevel="1"/>
                <capability name="org.apache.felix.configadmin" startlevel="1"/>
                <capability name="org.jboss.as.osgi.configadmin" startlevel="1"/>
            </capabilities>
        </subsystem>
        <subsystem xmlns="urn:jboss:domain:pojo:1.0"/>
        <subsystem xmlns="urn:jboss:domain:remoting:1.1">
            <connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/>
        </subsystem>
        <subsystem xmlns="urn:jboss:domain:resource-adapters:1.0"/>
        <subsystem xmlns="urn:jboss:domain:sar:1.0"/>
        <subsystem xmlns="urn:jboss:domain:security:1.1">
            <security-domains>
                <security-domain name="other" cache-type="default">
                    <authentication>
                        <login-module code="Remoting" flag="optional">
                            <module-option name="password-stacking" value="useFirstPass"/>
                        </login-module>
                        <login-module code="RealmUsersRoles" flag="required">
                            <module-option name="usersProperties" value="${jboss.server.config.dir}/application-users.properties"/>
                            <module-option name="rolesProperties" value="${jboss.server.config.dir}/application-roles.properties"/>
                            <module-option name="realm" value="ApplicationRealm"/>
                            <module-option name="password-stacking" value="useFirstPass"/>
                        </login-module>
                    </authentication>
                </security-domain>
                <security-domain name="jboss-web-policy" cache-type="default">
                    <authorization>
                        <policy-module code="Delegating" flag="required"/>
                    </authorization>
                </security-domain>
                <security-domain name="jboss-ejb-policy" cache-type="default">
                    <authorization>
                        <policy-module code="Delegating" flag="required"/>
                    </authorization>
                </security-domain>
            </security-domains>
        </subsystem>
        <subsystem xmlns="urn:jboss:domain:threads:1.1"/>
        <subsystem xmlns="urn:jboss:domain:transactions:1.1">
            <core-environment>
                <process-id>
                    <uuid/>
                </process-id>
            </core-environment>
            <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/>
            <coordinator-environment default-timeout="1200"/>
        </subsystem>
        <subsystem xmlns="urn:jboss:domain:web:1.1" default-virtual-server="default-host" native="false">
            <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/>
            <virtual-server name="default-host" enable-welcome-root="true">
                <alias name="localhost"/>
                <alias name="example.com"/>
            </virtual-server>
        </subsystem>
        <subsystem xmlns="urn:jboss:domain:webservices:1.1">
            <modify-wsdl-address>true</modify-wsdl-address>
            <wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host>
            <endpoint-config name="Standard-Endpoint-Config"/>
            <endpoint-config name="Recording-Endpoint-Config">
                <pre-handler-chain name="recording-handlers" protocol-bindings="##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM">
                    <handler name="RecordingHandler" class="org.jboss.ws.common.invocation.RecordingServerHandler"/>
                </pre-handler-chain>
            </endpoint-config>
        </subsystem>
        <subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
            <deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" deployment-timeout="4800"/>
        </subsystem>
    </profile>

    <interfaces>
        <interface name="management">
            <inet-address value="${jboss.bind.address.management:127.0.0.1}"/>
        </interface>
        <interface name="public">
            <inet-address value="${jboss.bind.address:127.0.0.1}"/>
        </interface>
        <interface name="unsecure">
            <inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>
        </interface>
    </interfaces>

    <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
        <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>
        <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
        <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/>
        <socket-binding name="ajp" port="8009"/>
        <socket-binding name="http" port="8080"/>
        <socket-binding name="https" port="8443"/>
        <socket-binding name="osgi-http" interface="management" port="8090"/>
        <socket-binding name="remoting" port="4447"/>
        <socket-binding name="txn-recovery-environment" port="4712"/>
        <socket-binding name="txn-status-manager" port="4713"/>
        <outbound-socket-binding name="mail-smtp">
            <remote-destination host="localhost" port="25"/>
        </outbound-socket-binding>
    </socket-binding-group>

</server>

Persistence.xml

<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.0"
	xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://java.sun.com/xml/ns/persistence  
             http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">

			<!-- ########################################## -->
			<!-- Configuração Acessar Banco de Dados Mysql -->
			<!-- ########################################## -->
	<persistence-unit name="portalEmail" transaction-type="RESOURCE_LOCAL">
		<provider>org.hibernate.ejb.HibernatePersistence</provider>
		<jta-data-source>java:/catalina</jta-data-source>
		
		<class>br.com.getnet.portalsistemaretaguarda.produtoTO.ProdutoTO</class>
		<properties>
			<property name="hibernate.dialect" value="org.hibernate.dialect.MySQL5InnoDBDialect" />
			<property name="javax.persistence.jdbc.url" value="jdbc:mysql://localhost:3306/catalina" />
			<property name="javax.persistence.jdbc.driver" value="com.mysql.jdbc.Driver" />
			<property name="javax.persistence.jdbc.password" value="123" />
			<property name="javax.persistence.jdbc.user" value="root" />
			<property name="hibernate.hbm2ddl.auto" value="update" />
			<property name="hibernate.show_sql" value="true" />
			<property name="hibernate.format_sql" value="true" />
		</properties>
	</persistence-unit>
	
			<!-- ########################################## -->
			<!-- Configuração Acessar Banco de Dados Oracle -->
			<!-- ########################################## -->
	<persistence-unit name="portalEmail" transaction-type="RESOURCE_LOCAL">
		<provider>org.hibernate.ejb.HibernatePersistence</provider>
		<jta-data-source>java:/DSTESTE</jta-data-source>
		
		<class>br.com.getnet.portalsistemaretaguarda.produtoTO.ProdutoTO</class>
		<properties>
			<property name="hibernate.dialect" value="org.hibernate.dialect.OracleDialect" />
			<property name="javax.persistence.jdbc.url" value="jdbc:oracle:thin:@servidor:1521:HOMOLOG" />
			<property name="javax.persistence.jdbc.driver" value="oracle.jdbc.OracleDriver" />
			<property name="javax.persistence.jdbc.password" value="senha" />
			<property name="javax.persistence.jdbc.user" value="usuario" />
			<property name="hibernate.hbm2ddl.auto" value="update" />
			<property name="hibernate.show_sql" value="true" />
			<property name="hibernate.format_sql" value="true" />
		</properties>
	</persistence-unit>
</persistence>

Acredito que o driver que está no módulo não esteja sendo encontrado. Vamos utilizar outra abordagem. Faça o download do driver ojdbc6.jar e realize o deploy do mesmo no diretório JBOSS_HOME/standalone/deployments. Agore troque essa parte:

<datasource jndi-name="java:/DSTESTE" pool-name="OracletDS_pool" enabled="true" use-java-context="true" use-ccm="true"> <connection-url>jdbc:oracle:thin:@servidor:1521:HOMOLOG</connection-url> <driver>oracle</driver> <security> <user-name>user</user-name> <password>senha</password> </security> </datasource>

Por:

<datasource jndi-name="java:/DSTESTE" pool-name="OracletDS_pool" enabled="true" use-java-context="true" use-ccm="true"> <connection-url>jdbc:oracle:thin:@servidor:1521:HOMOLOG</connection-url> <driver>ojdbc6.jar</driver> <security> <user-name>user</user-name> <password>senha</password> </security> </datasource>

remova essa parte:

<driver name="oracle" module="com.oracle.jdbc"> <driver-class>oracle.jdbc.driver.OracleDriver</driver-class> </driver>

Reinicie o JBoss e nos diga se está a mesma coisa ou não.

Vlw

O resultado deu o mesmo

JBAS014775:    New missing/unsatisfied dependencies:
      service jboss.jdbc-driver.ojdbc6_jar (missing) dependents: [service jboss.data-source.java:/HOMOLOG] 

e tem mais essa informação agora no Log

JBAS014776:    Newly corrected services:
      service jboss.jdbc-driver.ojdbc6_jar (no longer required)

Configurar um datasource no JBoss é uma tarefa bem trivial, mas nao estamos conseguindo ter sucesso por algum problema que realmente agora não sei. Normalmente trabalho com MySQL e esses procedimentos deveriam funcionar.

Hoje a noite vou instalar o oracle EX em um VM e configurar o JBoss para acessar esse banco.
Posso estar errado, mas a sua configuração inicial do JBoss parece estar correta.

Se resolver avisa… mas hoje vou testar e ver se consigo fazer isso funcionar e posto o resultado
a noite.

Abs

Fiz a configuração usando Mysql e esta funcionando perfeitamente, mas com o Oracle estou com esse impasse,

irei fazer mais algumas pesquisas e quando funcionar eu aviso e caso tenha alguma outra sugestão q possa me ajudar antes que eu ache uma solução

estarei aguardando

Obrigado pela prestatividade com suas sugestões

Entao rsrs o estranho que com o MySQL funciona perfeitamente… deve ser alguma coisa relacionada ao driver… mas vou testar pq ai já resolvemos um problema e ajudamos outras pessoas :slight_smile:

Estamos ai pra aprender e ajudar né…

Abraços