No table name specified in ejb-jar.xml file
Hi, I have an entity bean defined as follows:
<enterprise-beans>
<entity>
<display-name>SponsorEJB</display-name>
<ejb-name>SponsorEJB</ejb-name>
<home>com.ultradns.j2ee.components.sponsor.ejb.SponsorHome</home>
<remote>com.ultradns.j2ee.components.sponsor.ejb.Sponsor</remote>
<ejb-class>com.ultradns.j2ee.components.sponsor.ejb.SponsorEJB</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.String</prim-key-class>
<reentrant>False</reentrant>
<resource-ref>
<res-ref-name>jdbc/jdbc/OracleDS</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>sponsor</abstract-schema-name>
<cmp-field>
<primkey-field>guid</primkey-field>
<query>
<query-method>
<method-name>findAll</method-name>
<method-params></method-params>
</query-method>
<ejb-ql>
<![CDATA[ SELECT OBJECT(a) FROM sponsor AS a]]>
</ejb-ql>
</query>
</entity>
</enterprise-beans>
In the database, I want this entity bean refers to a table named "sponsor", but I could not specify the relation in the ejb-jar.xml file. So when I deployed this bean, it auto created a table called "SponsorEJB". Where is this name come from, from display-name or ejb-name field?
Basically, how can I specify a bean "SponsorEJB" referes to a table "sponsor"?
Thanks,
First thing, to stop OC4J auto-creating tables, edit the file %J2EE_HOME%/config/application.xml. Change the first orion-application tag so that one attribute says autocreate-tables="false"
The ejb-jar.xml file describes your EJB's to the container. It is not supposed to describe which table each entity bean maps too, as this is an implementation specific property, so would not be portable between databases. Therefore you have to configure the container to point an entity to a table. Sun uses the sun-j2ee-ri.xml file to do this, and this has to be included in the deployment.
OC4J however uses the file 'orion-ejb-jar.xml', and will generate this for you. Since you have already deployed your application, this will have already been generated. Go to the directory %J2EE_HOME%/application-deployments. There will be a directory corresponding to your application name. In there is a directory corresponding to your ejb module name, and in there is the 'orion-ejb-jar.xml' file. If you open this file, you will see the entity deployment tags, an example of one is below. Edit the tag so that the table attribute points to the table in your database (note that there is a data-source attribute as well, so make sure that this points to the correct schema). The example below points the EJB Emp to the table EMP:
<entity-deployment name="Emp" max-instances="10" location="Emp" wrapper="EmpHome_EntityHomeWrapper3" table="EMP" data-source="jdbc/rob9iDS" locking-mode="optimistic" update-changed-fields-only="true" min-instances-per-pk="0" max-instances-per-pk="50" disable-wrapper-cache="true">
Hope this helps,
Rob
Similar Messages
-
Dynamic jndi-name in weblogic-ejb-jar.xml
Is there a way to create dynamic (i.e. runtime) jndi-names for EJBs instead of
(or in addition to) "hard coding" them in the weblogic-ejb-jar.xml file? What
I'm trying to do is have one WebLogic instance (JVM) host multiple environments
(our Beta and Training environments) and I simply want to deploy the same .ear
file twice but have each environment (application - .ear) reference a different
database schema (jdbc connection pool). I have everything working just fine for
this scenario except when I define jndi-names for our ejbs. The problem is that
I am really deploying the same ejbs (jndi-names and actually code base) in each
applicatoin instance and I get an exception when the WebLogic is trying to deploy
the second application (.ear) because the jndi-names in it have already been deployed
by the first application instance. I recieve a jndi error stating that the name
is already deployed.
Or is there a better path to go down for what I am trying to do to have one WebLogic
instance support our beta and training environments? Usually (but not always)
our code base is the for same for both of these environments, I simply need to
have each environment use a different database schema.
ThanksA little birdie tells me that BEA does this very thing. Looking at the
descriptors for WebLogic Portal I see:
<weblogic-enterprise-bean>
<ejb-name>LoaderEJB</ejb-name>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>${APPNAME}.BEA_content.LoaderHome</jndi-name>
</weblogic-enterprise-bean>
Yes, the ${APPNAME} token really is expanded into the J2EE application
name at deployment time!
Sincerely,
Daniel Selman
Bryan Dixon wrote:
Rewriting our build process isn't really much of an option for me. Our current
build process is too complex and time consuming right now to convert to Ant (we
eventually will do this but not for a while). So are there any other ideas that
aren't build related?
Thanks
"Eric Ma" <[email protected]> wrote:
You don't need run-time dynamism in JDNI names and it can't be done anyways.
You
need token substitution in XML configuration files when building the
app. If
you are using Ant for building, then it is a breeze. If not, first convert
your
build process to use Ant.
Also, a single WLS instance hosting multiple environments sounds really
INTRIGUING
to me.
Eric Ma
"Bryan Dixon" <[email protected]> wrote:
Is there a way to create dynamic (i.e. runtime) jndi-names for EJBsinstead
of
(or in addition to) "hard coding" them in the weblogic-ejb-jar.xml file?
What
I'm trying to do is have one WebLogic instance (JVM) host multiple environments
(our Beta and Training environments) and I simply want to deploy the
same .ear
file twice but have each environment (application - .ear) referencea
different
database schema (jdbc connection pool). I have everything working just
fine for
this scenario except when I define jndi-names for our ejbs. The problem
is that
I am really deploying the same ejbs (jndi-names and actually code base)
in each
applicatoin instance and I get an exception when the WebLogic is trying
to deploy
the second application (.ear) because the jndi-names in it have already
been deployed
by the first application instance. I recieve a jndi error stating that
the name
is already deployed.
Or is there a better path to go down for what I am trying to do to have
one WebLogic
instance support our beta and training environments? Usually (but not
always)
our code base is the for same for both of these environments, I simply
need to
have each environment use a different database schema.
Thanks -
Oc4j generated finders in orion-ejb-jar.xml file causing errors
Any information or assistance would be greatly appreciated.
I have encountered a problem with the generated orion-ejb-jar.xml file.
It looks like the additional finder methods that are generated when the application
is deployed are incorrect from the 9.0.3 version to the new 10.1.2.0.2 version.
The original content of orion-ejb-jar.xml before additional finder syntax is added:
<finder-method query=
"NO_SYS_USER_OBJECT_HISTORY.USER_ID=UPPER($1) and
NO_SYS_USER_OBJECT_HISTORY.AUTOID NOT IN(
SELECT H1.AUTOID
FROM NO_SYS_USER_OBJECT_HISTORY H1,
(SELECT AUTOID
FROM NO_SYS_USER_OBJECT_HISTORY
WHERE USER_ID=UPPER($1)
ORDER BY DATE_TIME DESC) H2
WHERE ROWNUM <= $2
AND H1.AUTOID = H2.AUTOID)">
<method>
<ejb-name>NoUserHistoryEntry</ejb-name>
<method-name>findOldest</method-name>
<method-params>
<method-param>java.lang.String</method-param>
<method-param>java.lang.Integer</method-param>
</method-params>
</method>
</finder-method>
After deploying in 9.0.3 the following information is added to the orion-ejb-jar.xml file:
<finder-method query=
"NO_SYS_USER_OBJECT_HISTORY.USER_ID=UPPER($1) and
NO_SYS_USER_OBJECT_HISTORY.AUTOID NOT IN(
SELECT H1.AUTOID
FROM NO_SYS_USER_OBJECT_HISTORY H1,
(SELECT AUTOID
FROM NO_SYS_USER_OBJECT_HISTORY
WHERE USER_ID=$1
ORDER BY DATE_TIME DESC) H2
WHERE ROWNUM <= $2
AND H1.AUTOID = H2.AUTOID)">
<!-- Generated SQL:
"select NO_SYS_USER_OBJECT_HISTORY.autoid
from NO_SYS_USER_OBJECT_HISTORY
where NO_SYS_USER_OBJECT_HISTORY.USER_ID=UPPER(?)
and NO_SYS_USER_OBJECT_HISTORY.AUTOID NOT IN(
SELECT H1.AUTOID
FROM NO_SYS_USER_OBJECT_HISTORY H1,
(SELECT AUTOID
FROM NO_SYS_USER_OBJECT_HISTORY
WHERE USER_ID=?
ORDER BY DATE_TIME DESC) H2
WHERE ROWNUM <= ?
AND H1.AUTOID = H2.AUTOID) -->
<method>
<ejb-name>NoUserHistoryEntry</ejb-name>
<method-name>findOldest</method-name>
<method-params>
<method-param>java.lang.String</method-param>
<method-param>java.lang.Integer</method-param>
</method-params>
</method>
</finder-method>
After deploying in 10.1.2.0.2 the following information is added to the
orion-ejb-jar.xml file:
<finder-method query=
"NO_SYS_USER_OBJECT_HISTORY.USER_ID=UPPER($1) and
NO_SYS_USER_OBJECT_HISTORY.AUTOID NOT IN(
SELECT H1.AUTOID
FROM NO_SYS_USER_OBJECT_HISTORY H1,
(SELECT AUTOID
FROM NO_SYS_USER_OBJECT_HISTORY
WHERE USER_ID=UPPER($1)
ORDER BY DATE_TIME DESC) H2
WHERE ROWNUM <= $2
AND H1.AUTOID = H2.AUTOID)">
<!-- Generated SQL (pk only):
"select H1.autoid
from NO_SYS_USER_OBJECT_HISTORY
where NO_SYS_USER_OBJECT_HISTORY.USER_ID=UPPER(?)
and NO_SYS_USER_OBJECT_HISTORY.AUTOID NOT IN(
SELECT H1.AUTOID
FROM NO_SYS_USER_OBJECT_HISTORY H1,
(SELECT AUTOID
FROM NO_SYS_USER_OBJECT_HISTORY
WHERE USER_ID=UPPER(?)
ORDER BY DATE_TIME DESC) H2
WHERE ROWNUM <= ?
AND H1.AUTOID = H2.AUTOID) -->
<!-- Generated SQL (all columns):
"select H1.autoid, H1.USER_ID, H1.OBJECT_CLASS_ID,
H1.DATE_TIME, H1.COMMENT_TEXT, H1.ACTION,
H1.ACTION_DATA, H1.SITE_DESCRIPTION
from NO_SYS_USER_OBJECT_HISTORY
where NO_SYS_USER_OBJECT_HISTORY.USER_ID=UPPER(?)
and NO_SYS_USER_OBJECT_HISTORY.AUTOID NOT IN(
SELECT H1.AUTOID
FROM NO_SYS_USER_OBJECT_HISTORY H1,
(SELECT AUTOID
FROM NO_SYS_USER_OBJECT_HISTORY
WHERE USER_ID=UPPER(?)
ORDER BY DATE_TIME DESC) H2
WHERE ROWNUM <= ?
AND H1.AUTOID = H2.AUTOID) -->
<method>
<ejb-name>NoUserHistoryEntry</ejb-name>
<method-name>findOldest</method-name>
<method-params>
<method-param>java.lang.String</method-param>
<method-param>java.lang.Integer</method-param>
</method-params>
</method>
</finder-method>
The problem with the 10.1.2.0.2 generated finders is that it is prepending H1 when
it should be NO_SYS_USER_OBJECT_HISTORY which results in the following error:
Exception in thread "main" com.cdtelecom.vygroe.configuration.ConfigurationException:
com.evermind.server.rmi.OrionRemoteException:
Transaction was rolled back: Database error: java.sql.SQLException:
ORA-00904: "H1"."SITE_DESCRIPTION": invalid identifier
; nested exception is:
java.sql.SQLException: ORA-00904: "H1"."SITE_DESCRIPTION": invalid identifier
at com.cdtelecom.vygroe.configuration.ConfigurationSession.internalRecordAction(ConfigurationSession.java:869)
at com.cdtelecom.vygroe.configuration.ConfigurationSession.recordAction(ConfigurationSession.java:401)
at com.cdtelecom.vygroe.configuration.Configuration.recordActionSaveOrder(Configuration.java:886)
at com.cdtelecom.vygroe.configuration.Configuration.getOrder(Configuration.java:239)
at test10g.main(test10g.java:47)
I tried to manually edit the file but when I shutdown and restart oc4j it regenerates the file again.Jingzhi -- If you define the correct EJB-QL you should get the correct SQL generated for the finder. If that's not happening can you verify it against the OC4J v903 production release and see if it is still happening. I don't know if this helps with the JDeveloper problem specifically but if you don't need to create your own finders then that I hope should help.
Thanks -- Jeff -
Come error at doctype statement in ejb.jar.xml file
hello,
I use eclipse 3.1RC1 & lomboz emf-gef 3.1RC1 at linux os. when I create ejb project a error is created at line "doctype" in ejb-jar.xml file & it gives a error mess. java.sun.com can't be registratedtry :
p.stepid and p.stepversion are correct insert into <cmp-field> ?
and Processparameter is the correct name of <abstract-schema-name>?
is your <ejb-ql> insert in the right <entity> ?
findByProcessStep(Integer, Integer) is the unique name in your ejb-jar? and in the (LocalHome ||RemoteHome) -
How to use multiple ejb-jar.xml files
Hello -
If the project you work on has a lot of beans that you need to configure them in one ejb-jar.xml file. Then ejb-jar.xml file will be getting bigger and bigger. I am wondering if there is any way to divide the ejb-jar.xml file into multiple sub ejb-jar.xml files and then combin them together when deploy it. Same question question for the vendor ejb-jar.xml like weblogic-ejb-jar.xml.
Thanks!
BenHI Ben,
No, there is no notion of combining ejb-jar.xmls at deployment time in Java EE. There is no
set limit on the number of ejb components within an ejb-jar module either.
--ken -
Stateless session Bean - xml and ejb-jar.xml file ???
Dear Experts,
Stateless-session bean
For Creating an ear file
we need ejb-jar.xml and weblogic-ejb-jar.xml files
Is these files are already available
or we have to type these files ??
Advance Thanks
Rengaraj.RMy best advice: surrender to use an IDE.
You wonder sometimes at how much productivity (read as 'time') could be wasted by doing something that could be done automatically. For a learning experience or a once only exercise is fine but as a routine thing, not worth it.
Cheers -
Query about reentrant in ejb-jar.xml file(in case of entity Bean)
Hi all friends,
I am new to EJB I couldn't understand in ejb-jar.xml file in case Entity Bean[<reentrant>False</reentrant>
&<reentrant>true</reentrant>]what is the function of this tag and what is the effect of value true and false of this tag.Can any one please explain it.
Regards
BikashHi,
Re-entrant tag is used in the ejb-jar.xml to notify the container if you would want your bean to call itself through another bean.
Most of the time you would want it to be set to FALSE because you would have to consider the multi-threading issues if you set it TRUE.
Regards
Meka Toka -
How to write multiple ejb-jar.xml file in an ejb module
i am developing an ejb project. I hav a number of entity beans and session beans and their mapping in ejb-jar.xml. As the number of beans increases the entry of beans and mapping is also increasing. So i want to ask u that is there any mechanism so that i can divide the ejb-jar.xml file so that it will be easy to maintain it.
ejb-jar is the smallest composable unit for related EJB components. Your best bet is to create multiple ejb-jars and package them within the same enterprise application (.ear).
-
Sun-ejb-jar.xml file is increased after deploying
When I deploy my application the size of sun-ejb-jar.xml file is increased from 140K to 6.5M!!! When I review a new file I have found that all finder methods from all beans were included into the each entity beans. Is it correct?
Thank you,
Sergeyup
-
Global env-entry JNDI variables space for same ejb-jar.xml file
[Software]
jboss4.0.5
jdk 1.5
[Problem]
Is there any global <env-entry> tag for a Single EJB Module. Is there any way by which the JNDI variable can be accessed by all the modules except by binding the variables in the JNDI explixity in the code
Thanks in advance
CSJakhariaUnfortunately not. The EJB specification has always scoped the component environment
(java:comp/env) as a private environment for each EJB. The advantage is you can
assign entries within each bean easily without worrying about clashing with names selected
for other beans in the ejb-jar. That eases the process of assembling beans developed
separately into one ejb-jar since there is no possibility that their component environments
will clash.
However, the downside is just what you're pointing out, which is that in many cases
developers prefer to define a single dependency that is shared among all the
beans in the ejb module. That is the behavior of the component environment in a
web application.
We'll be looking into ways to simplify this for ejbs in a future revision of the specification.
--ken -
Local Interface in weblogic-ejb-jar.xml file
I used Local Interface in WLS 7.0, and specifies the jndi-name as
<weblogic-enterprise-bean>
<ejb-name>MailboxService</ejb-name>
<jndi-name>ejb/MailboxServiceHome</jndi-name>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>MailboxServiceLocal</ejb-name>
<jndi-name>ejb/MailboxServiceLocalHome</jndi-name>
</weblogic-enterprise-bean>
When I migrate to WLS 8.1, I keep receiving warning messages like:
"[java] WARNING: Warning from ejbc: <jndi-name> must be defined for a bean
with remo
te interface. 'RecognitionServiceLocal(Jar: C:\ebdev\dev\make\eb-ejb\..\..\dist\eb-ejb.j
ar)' does not have a remote interface."
What is wrong here?
Thanks in advance.jndi-name is specified for a remote interface.
local-jndi-name is specified for a local interface.
thanks,
Deepak Vohra
"Andy yang" <[email protected]> wrote:
>
I used Local Interface in WLS 7.0, and specifies the jndi-name as
<weblogic-enterprise-bean>
<ejb-name>MailboxService</ejb-name>
<jndi-name>ejb/MailboxServiceHome</jndi-name>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>MailboxServiceLocal</ejb-name>
<jndi-name>ejb/MailboxServiceLocalHome</jndi-name>
</weblogic-enterprise-bean>
When I migrate to WLS 8.1, I keep receiving warning messages like:
"[java] WARNING: Warning from ejbc: <jndi-name> must be defined
for a bean
with remo
te interface. 'RecognitionServiceLocal(Jar: C:\ebdev\dev\make\eb-ejb\..\..\dist\eb-ejb.j
ar)' does not have a remote interface."
What is wrong here?
Thanks in advance. -
Ejb-jar.xml not using fully qualified class names
HI,
I am trying yo upgrade my application from weblogic 8.1 to weblogic 9.2.3. My application has both session and enitybeans. I updated weblogic related jars with 9.x version. But while running ejbgen, i am getting the following exception.
*[java] weblogic.ejb.container.deployer.DeploymentDescriptorException: Unable to set the transaction attribute for method 'updateService(abcTO)' on EJB 'AbcService'. No matching method could be found. Please verify the method signature specified in the ejb-jar.xml file matches that of your Local interface for this EJB.*
In ejb-jar.xml file, it is not creating the fully qualified class name for abcTo in <method-param>. In component interface, the method signature is not contaning fully qualified class name for the parameters and return values.
If i change the signature in the bean with the fully qualified class name of the parameter, the ejb-jar.xml file is creating fine. But there are 100's of signatures i need to change if this is the only solution.
Can you please advice what i need to change when i upgrade from weblogic 8 to 9 series from session and entity bean's point of view?
Thanks in Advance
Naveen.
Edited by: avn_venki on Mar 16, 2009 7:15 AM
Edited by: avn_venki on Mar 16, 2009 7:15 AMejb-jar.xml has always required fully-qualified class names. If some vendors have accepted unqualified class names unfortunately that
behavior is non-portable. Your best bet is to fully-qualify the names. Perhaps you can find some tools to help you given the large
number of components in your application. -
"Could not locate the bean with the ejb-name XYZ in weblogic-ejb-jar.xml
Hi,
Please someone help me on this...
I'm trying to deploy an application on WLS 8.1 SP4
on HPUX IA64 arch. From the ear file WLS is able to
deploy 3 jars but for the last two jars it's throwing
the below error:
Could not locate the bean with the ejb-name xyz in weblogic-ejb-jar.xml
But ejb with name xyz is defined in the the weblogic-ejb-jar.xml file and it's also present in the
META-INF/ejb-jar.xml file.
I have no clue what's going wrong.
Any help is appreciated.
Thanks
Moulioops! Pls ignore my previous mail. It was for a different problem.
FOr the original problem of "couldn ot locate the bean with the ejb-name XZY in weblogic-ejb-jar.xml":
This happens if you don't have the below files defined
for a JAR/EAR file:
weblogic-ejb-jar.xml and weblogic-cmp-rdbms-jar.xml (needed if you have any Datasource mapped)
These two are basic files required for any JAR/EAR file.
If you dont' have it already you can generate them using
$WLS_HOME/bin/startWLBuilder.sh GUI tool bundled along
with WLS (I used 8.1 SP4) to generate these files ! This tool is really helpful.
- Mouli -
Application deployment order with weblogic-ejb-jar.xml and jndi-name
I have two applicatation working on Weblogic server v. 10.3.6.
First of them creating one ejb stateless bean and creates JNDI maping for it (in weblogic-ejb-jar.xml file):
<weblogic-enterprise-bean>
<ejb-name>ConfigMenegerBean</ejb-name>
<stateless-session-descriptor>
<stateless-session-descriptor>
<business-interface-jndi-name-map>
<business-remote>package.ConfigurationSessionRemote</business-remote>
<jndi-name>ConfigMeneger</jndi-name>
</business-interface-jndi-name-map>
</stateless-session-descriptor>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>ConfigMeneger</jndi-name>
</weblogic-enterprise-bean>
Second appication have to refer for this bean by JNDI using spring been lookup :
<jee:jndi-lookup id="configManager" jndi-name="ConfigMeneger"/>
I changed deployment order parameter for both apllication(first=100 and second=500) in order to first app start first and share bean by jndi to another application. Unfortuantelly I got an error :
javax.naming.NameNotFoundException: Unable to resolve 'ConfigMeneger'. Resolved ''; remaining name 'ConfigMeneger'
How can I configure deployment order that first application make jndi mapping for bean, before the second application will use it ?Ok in a way I have solved my problem (even if I am not completely satisfied by the way on how to proceed...). So thanks to message "JBuilder7.0 and Weblogic6.1" on EJB sun forum :
http://forum.java.sun.com/thread.jsp?thread=285735&forum=13&message=1255488
I have tried the following actions (mentionned in the other forum messages):
- To preserve changes to weblogic*.xml, the safest way is to change the ejb-borland.xml.
(I am not sure that I have applied this advice correctly, because I suppose that syntax is not similar in weblogic file or borland file).
And you can MANUALLY update the weblogic file in your JAR archive.
1. Open the EJB JAR file in Winzip and extract the weblogic-ejb-jar.xml file, so that a copy exists in your
project directory.
2. Open this file (in Notepad), add the WebLogic specific information, and then save the file.
3. Now, when you are finished with the build cycle and are ready to deploy, you may open the EJB jar file
and swap in the weblogic-ejb-jar.xml file."
Good Luck. -
JNDI name in ejb-jar.xml
Hi all,
I am deploying about 80 beans to WebSphere using the console. I was wondering if it was possible to set the jndi name of my beans in the standard ejb-jar.xml file within my jarfile.
I tried to add the trags <jndi-name> or <jndiname> to my ejb-jar.xml but it is ignored and I still have to input all the jndi names by myself.
Seems like the jndi-name resided in the vendor-specific ejb-jar.xml.
Max.Perhaps the <jndi-name> in weblogic-ejb-jar.xml:
<?xml version="1.0" ?>
<!DOCTYPE weblogic-ejb-jar (View Source for full doctype...)>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>CurrencyConverterBean</ejb-name>
<stateless-session-descriptor />
<jndi-name>conv</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Maybe you are looking for
-
How to catch Exception in backingbean which is thrown from the Model layer.
Hi, JDev Ver: 11.1.1.2.0 In my application there are two layer viewcontroller & model. In model layer I have created JPA service facade which does the database operation like persist, merge & remove entity. I am calling this service facade method fro
-
Compressor 4.1 waiting....
I've had the WORST luck using compressor 4.x of ANY Apple software since I started with my first Mac in 1987. Compressor repair has let me get the occassional job through on my old machine, but this version (4.1) has me livid. I'm on a late 2013 rMBP
-
How do I view videos on face book?
How do I view on face book?
-
CIN effect that global template
Dear CIN experts, I need CIN experts advise on query as mentioned below, -Suppose if i have global template in a project implementation or rollout and now i want implement SAP for country India,here how CIN will effect that global template in SD poin
-
About Dead Lock on apps tables in 11.5.10.2
Hi All, How to find and Kill dead lock on apps table (11.5.10) ? Reg Chirag Patel