IMP-00093: Inconsistency between dumpfile constraint definition for table

I am getting the following error while importing table. I have checked and I can see the table and constraint exist.
Anyone know in what situition this warning will be trigger out? Will this warning give any impact to the table or database ? any solutions?
Export file created by EXPORT:V09.02.00 via conventional path
import done in US7ASCII character set and AL16UTF16 NCHAR character set
. importing PROD_USR's objects into PROD_USR
. . importing table "FLPBABA" 29 rows imported
IMP-00093: Inconsistency between dumpfile constraint definition for table FLPBABA with columns ("FQ_FLPBABA_UPD_TMS" , "F9_FLPBABA_B4_AFTER")
Import terminated successfully with warnings.
Message was edited by:
cocorico78

The full error message might explain a little.
Oracle Error :: IMP-00093
Inconsistency between dumpfile constraint definition for table string with columns (string)
Cause
Import failed to locate a base table for a constraint that was defined in the dump file and statistics were not imported.
Action
Check to see if the table and constraint exist. If the table and constraint exist, then report this to Oracle Support Services as an Import internal error.

Similar Messages

Difference between unique constraint and unique index

1. What is the difference between unique constraint and unique index when unique constraint is always indexed ? Which one is better in this case for better performance ?
2. Is Composite index of 3 columns x,y,z better
or having independent/ seperate indexes on 3 columns x,y,z is better for better performance ?
3. It has been very confusing for me to decide which columns to index, I have indexed most foreignkey columns, is it a good idea ? We do lot of selects and DMLS on most of our tables. Is there any query that I can run and find out if indexes are really being used and if they are improving any performance. I have analyzed and computed my indexes using ANALYZE index index_name validate structure and COMPUTE STATISTICS;
null

1. Unique index is part of unique constraint. Of course you can create standalone unique index. But is is no point to skip the logical view of business if you spend same effort to achive.
You create unique const. Oracle create the unique index for you. You may specify index characteristic in unique constraint.
2. Depends. You can't utilize the composite index if the searching condition is not whole or front part of the indexing key. You can't utilize your index if you query the table for y=2. That is.
3. As old words in database arena, Index may be good or bad for a table depending on the size of table, number of columns in the table... etc. It is very environmental dependent. In fact, It is part of database nomalization. Statistic is a way oracle use to determine the execution plan.
Steve
null

Inconsistency between catalog authoring tool & Search engine

Hi,
We are on CCM2.0 and SRM5.0 with catalog deployment in the same client as SRM.
In our implementation we are using master catalog and product catalog. We have very recently deleted around 65 items from our product catalog which is mapped to mater catalog and hence those 65 items are not found anymore in master catalog in CAT (Catalog authoring tool).
This master catalog when published, we expect that these 65 products should not be available for end users.
But end users can still see the deleted items through CSE (Catalog search engine). Thus there is data inconsistency between CAT & CSE.
Has anyone faced similar issue before if yes can you please share the same with us.
Edited by: Manoj Surve on Mar 24, 2009 7:05 AM

Run TCODE SE38 program /CCM/CLEANUP_MAPPING to look for errors/orphaned records in test mode.
If you want to clear out orphaned records uncheck the Test Mode but:
Warning: This program can slow down a production system as it clears out the memory buffers for user catalog searches and these have to be built up again by the users doing searches. This can be hours to days depending upon the size of your system and the number of users.
In Dev or UAt no problem.
Hope this helps?
Regards
Allen

Inconsistency between get-childitem -include and -exclude parameters

Hi,
Powershell 2.0
Does anyone else consider this a minor design bug in the Get-ChildItem command?
# create dummy files
"a","b","c" | % {$null | out-file "c:\temp\$_.txt"}
# this "fails", returns nothing
get-childitem c:\temp -include a*,b*
# this "works", returns desired files
get-childitem c:\temp\* -include a*,b*
# this "works", excludes undesired files
get-childitem c:\temp -exclude a*,b*
# this "fails", excludes undesired files BUT RECURSES sub-directories
get-childitem c:\temp\* -exclude a*,b*
I'm writing a wrapper script around the GCI cmdlet, but the inconsistency between the two parameters is problematic. My end user will surely just type a path for the path parameter, then wonder why -include returned nothing. I can't unconditionally
add an asterisk to the path parameter, since that messes up the exclude output.
I'm just wondering why Microsoft didn't make the parameter interaction consistent???
# includes desired files in the specified path
get-childitem -path c:\temp -include a*,b*
# excludes undesired files in the specified path
get-childitem -path c:\temp -exclude a*,b*
# combine both options
get-childitem -path c:\temp -include a*,b* -exclude *.log,*.tmp
# same as above, the asterisk doesn't matter
get-childitem -path c:\temp\* -include a*,b*
get-childitem -path c:\temp\* -exclude a*,b*
get-childitem -path c:\temp\* -include a*,b* -exclude *.log,*.tmp
# same as above, but explicitly recurse if that's what you want
get-childitem -path c:\temp\* -include a*,b* -recurse
get-childitem -path c:\temp\* -exclude a*,b* -recurse
get-childitem -path c:\temp\* -include a*,b* -exclude *.log,*tmp -recurse
If I execute the "naked" get-childitem command, the asterisk doesn't matter...
# same results
get-childitem c:\temp
get-chileitem c:\temp\*
If this isn't considered a bug, can you explain why the inconsistency between the two parameters when combined with the -path parameter?
Thanks,
Scott

The Get-ChildItem cmdlet syntax is horrific for advanced use. It's not a bug in the classic sense, so you shouldn't call it that. However, feel free to call it awful, ugly, disastrous, or any other deprecatory adjective you like - it really is
nasty.
Get-ChildItem's unusual behavior is rooted in one of the more 'intense' dialogues between developers and users in the beta period. Here's how I recall it working out; some details are a bit fuzzy for me at this point.
Get-ChildItem's original design was as a tool for enumerating items in a namespace -
similar to but not equivalent to dir and
ls. The syntax and usage was going to conform to standard PowerShell (Monad at the time) guidelines.
In a nutshell, what this means is that the Path parameter would have truly just meant Path - it would not have been usable as a combination path specification and result filter, which it is now. In other words
(1) dir c:\temp
means you wanted to return children of the container c:\temp
(2) dir c:\temp\*
means you wanted to return children of all containers inside
c:\temp. With (2), you would never get c:\tmp\a.txt returned, since a.txt is not a container.
There are reasons that this was a good idea. The parameter names and filtering behavior was consistent with the evolving PowerShell design standards, and best of all the tool would be straightforward to stub in for use by namespace
providers consistently.
However, this produced a lot of heated discussion. A rational, orthogonal tool would not allow the convenience we get with the dir command for doing things like this:
(3) dir c:\tmp\a*.txt
Possibly more important was the "crash" factor. It's so instinctive for admins to do things like (3) that our fingers do the typing when we list directories, and the instant failure or worse, weird, dissonant output we would get with a more pure Path
parameter is exactly like slamming into a brick wall.
At this point, I get a little fuzzy about the details, but I believe the Get-ChildItem syntax was settled on as a compromise that wouldn't derail people expecting files when they do (3), but would still allow more complex use. I think that this
is done essentially by treating all files as though they are containers for themselves. This saves a lot of pain in basic use, but introduces other pain for advanced use.
This may shed some light on why the tool is a bit twisted, but it doesn't do a lot to help with your particular wrapping problem. You'll almost certainly need to do some more complicated things in attempting to wrap up Get-ChildItem. Can you describe some
details of what your intent is with the wrapper? What kind of searches by what kind of users, maybe? With those details, it's likely people can point out some specific approaches that can give more consistent results.

Inconsistency between tbtco and tbtcs

Hello guys,
we have a big problem after our HWU upgrade.
We have copied the content of tbtco into a new table tbtco_copy before the upgrade to save all the job entries.
After this we have deleted the contant of tbtco. So we had no scheduled jobs for the HWU
After the HWU we have copied back the content of tbtco_copy into tbtco.
But now we have a inconsistency between tbtco and tbtcs. This means that all planed and released jobs are not starting (delay goes up).
How we can start this jobs << Removed >>
Br
Christian
Edited by: Rob Burbank on Apr 19, 2009 4:23 PM

USer TR: SM65

There is an inconsistency between the authentication mode of target web application and the source web application after migrating to claims

I've had my farm upgraded from SP2010 to SP2013 for over 6 months now and all is well, however, I was refreshing my staging environment from production and I noticed that one of the databases still shows these errors when I run test-spcontentdatabase:
Category : Configuration
Error : False
UpgradeBlocking : False
Message : The [SharePoint Web App] web application is configured with claims authentication mode however the content database you are trying to attach is intended to be used against
a windows classic authentication mode.
Remedy : There is an inconsistency between the authentication mode of target web application and the source web application. Ensure that the authentication mode setting in upgraded web application is the
same as what you had in previous SharePoint 2010 web application. Refer to the link "http://go.microsoft.com/fwlink/?LinkId=236865" for more information.
This doesn't make sense considering I converted the production web application to claims during the upgrade and then verified all sites were working with claims logins. I also verified that existing AD user identities were converted to claims by checking out
the database tables. Yet test-spcontentdatabase still thinks there is a mismatch here.
My farm is SP1 and no further CUs. The point of this particular refresh is so I can update to the November CUs in my test farm. Anyone else see this? Seems like it's a bug/safe to ignore because my stuff is working.
Thanks,
Aaron

See:
http://thesharepointfarm.com/2014/11/test-spcontentdatabase-classic-to-claims-conversion/
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Task Flow Transaction Handling Inconsistent between JDeveloper R1 & R2.

We have a solution developed using Jdeveloper 11.1.2.1.0.
To describe the use case I will use the HR schema.
The user must be able to view Regions and navigate to Countries and Locations in a hierarchical way. At each level he must be allowed to view and maintain the detail of the current record at that level. The user must also be able to navigate directly to a level and perform a search to view the data and from there be allowed to to view and maintain the detail of the current record at that level.
So I have created the following design to achieve this and take into consideration that I need to reuse my task flows that maintain the data.
Business Services (Model Project)
1. HierarchyAM, containing Read Only VO’s of the various levels nested by association/view link.
2. Region + Countries + Locations
3. Search#Level#AM, A separate AM for each level, containing the Read Only VO per level.
4. Maintain#Level#AM, A Separate AM for each level, containing an updateable VO per level.
UI (View Controller Project)
I created the following BTF’s (To try and keep the post short as possible I will only provide detail for a single level to explain the issues)
*1. HiererchyBTF*
a.     Contains a fragment.
b.     Added RegionHierarchyBtf, CountryHierarchyBTF, LocationHierarchyBTF to the above fragment as dynamic regions.
c.     Task flow transaction <No Controller Transaction>, isolated.
*2. RegionHierarchyBTF. (The same BTF’s are created for each level in the hierarchy)*
a.     Contains a fragment.
b.     Exposed HierarchyAM<RegionRoVO>
c.     Task flow transaction <No Controller Transaction>, shared.
d.     Includes a call to the EditRegionBTF.
*3. SearchRegionBTF (The same BTF’s are created for each level in the hierarchy)*
a.     Contains a fragment.
b.     Exposed SearchRegionAM<RegionRoVO>
c.     Task flow transaction <No Controller Transaction>, isolated.
d.     Includes a call to the EditRegionBTF.
*4. EditRegionBTF*
a.     Contains a fragment.
b.     Exposed MaintainRegionAM<RegionVO>
c.     Task flow transaction <Use Existing Transaction if Possible>, isolated.
Runtime behaviour with above configuration.
1.     Running the HiererchyBTF and navigation the levels works in all versions.
2.     Calling an edit BTF allows me to edit the current record and successfully commit the data in all versions.
3.     Calling an edit BTF for the same record immediately thereafter, allows me to edit the record and commit the data successfully in all versions.
4.     Running any of search BTF’s and calling the edit BTF works in all versions.
Runtime behaviour and changing the EditRegionBTF task flow transaction to Shared.
1.     Running the HiererchyBTF and navigation the levels works in all versions.
2.     Calling an edit BTF allows me to edit the current record in the table and successfully commit the data in all versions.
3.     Calling an edit BTF for the same record immediately thereafter, allows me to edit the record and commit the data successfully in 11.1.1.4.0 & 11.1.1.6.0 only. If I perform the same scenario in 11.1.2.1.0 I receive the following exception.
a.     JBO-25003: Object MaintainLocationAM of type ApplicationModule is not found.
4.     Repeating the process, but after editing the first record, edit the second record in the table the error is not encountered. If, after successfully editing the second record and committing the data successfully, I again edit the first record I edited, I receive the same exception as in point 3.
5.     Running any of search BTF’s and calling the edit BTF works in all versions.
For the purpose of having a reusable edit task flow, I need to have the task flow transaction configuration as <Use Existing Transaction if Possible>, shared. This enables me to have the edit task flow as a parent as well as a child task flow and use the task flow functionality irrespective if it is controlling the transaction or not.
My questions are;
1. Is my design acceptable for the solution I am developing, I am more specifically questioning my separation of the AM’s to achieve loosely coupled task flows.
2. Is there a bug (I have done a search on MOS) that details this behaviour.
3. As, in my opinion, this is a common requirement, why is there inconsistency between the versions.
The demo for each version can be made available.
Regards.
Leon.
Edited by: Leon Dorfling on Feb 21, 2013 1:44 AM

Hi Frank,
+1. Its the first sting I stumbled on reading your post. Unless the read-only view object AMs are shared across users (application scope) I don't see why you want to have them in a separate AM. I don't see a benefit in a purely read-only view object that is not backed up by entities and thus would follow Oracle's recommendation to always use entities with view objects.+
The read-only vo's are based on eo's. I separated the AM as the search use cases are independent of one another. So my understanding, from a performance perspective, is to not have all the read-only vo's of the entire hierarchy of products in a single AM if I am only going to access one of them. If I do not understand correctly, can you please assist me in better understanding.
+2. For sure this behavior doesn't sound right and should be filed. You may want to check 11.2.3 in case it has been fixed in there already.+
As posted by Chris, I have through MOS found that it has been fixed in a later version.
Btw.: "Calling an edit BTF for the same record immediately thereafter, allows me to edit the record and commit the data successfully" how do you call this task flow dynamic region or task flow call activity ?
The BTF's are called using a backing bean.
Regards
Leon.

In web dynpro i want explanation/definition for the following things

Hi dudes,
I want explanation *** definition for the following
(1) web dynpro
(2) Cardinality
(3) methods
(4) Nodes
(5) Attributes
(6) Interface
(7) Views
(8) Windows
(9) Mapping
(10)Binding
(11)Model
(12)Controller

Hi,
Here are the defintions for the terms you hav requested-
Web Dynpro Architecture
Definition
Web Dynpro is the SAP NetWeaver programming model for user interfaces (UIs).
The Web Dynpro model is based on the Model View Controller paradigm, and has the
following features that build on the classic dynpro model:
Clear separation of business logic and display logic
Uniform metamodel for all types of user interfaces
Execution on a number of client platforms
Extensive platform independence of interfaces
Web Dynpro provides support for developing Web representation of a business application.
You use specific tools to describe the properties of a Web Dynpro application in the form of
Web Dynpro metadata. The necessary source code is then generated automatically and
executed at runtime. In addition to the events offered by the framework, you can also define
your own events for a Web Dynpro application. However, the event handling must always be
programmed in separate source code areas which are executed automatically when the event
is triggered at runtime.
In Web Dynpro, each user interface is always made up of the same basic elements. These
elements of the metamodel can be statically declared using Web Dynpro tools.
It is also possible to implement elements of the metamodel at runtime and to change them or
reintegrate them at runtime. Using these implementations, you can make any changes or
enhancements to a user interface that has been created by declarative methods by
generating new interface structures at runtime.
This means that you can combine declarative processes and the implementation of source
code.
A Web Dynpro component is a reusable entity. It summarizes all components that are
required as part of this programming unit for an executable Web Dynpro application.
The Web Dynpro component concept offers a number of advantages:
Structuring of the programming
Creation of easily manageable application blocks
Reusability of whole components
Decoupling of software projects in both time and space
The Web Dynpro component contains any number of windows and views and their
corresponding controllers. Additional Web Dynpro components can also be referenced.
View
A view describes the layout and behavior of a rectangular area of a user interface.
Every Web Dynpro application has at least one view. The layout of a view is made up of
different user interface elements, which can be nested in each other. The positioning of
interface elements in one view is supported by the supplied layout variants.
In addition to the visible part, the layout, a view also contains a controller and a context. The
data to which the elements of the view can be bound are stored and managed in the view
context, enabling them to be represented or used on the screen. The view controller can
contain methods for data retrieval or for processing user input.
Window
A window is used to combine several Views and View Sets (the concept of view sets is only
offered in Web Dynpro for Java). A view can only be displayed by the browser if it has been
embedded in a window. A window always contains one or more views, which are connected
by navigation links. One of these views, or a view set, is specified as the start view and is
displayed the first time the window is called.
Windows have inbound and outbound plugs.
Inbound Plugs and Outbound Plugs
A window has one or several inbound or outbound plugs. Using these plugs, a window can be
included into a navigation chain. The concept of these plugs corresponds to the concept of
the plug for a view. Each plug of a window is visible within the entire window and can be used
for navigating within this window. In addition, one or several plugs can be made accessible to
the component interface so that they are visible even beyond the limits of the component in
question. They thus belong to the interface view of the relevant window.
They are used to navogate from one view to other and pass the data between the views. Which view to be called next from current view - the flow of views is descriebd here using Plugs.
Controller
Controllers are the active parts of a Web Dynpro application. They define how the user can
interact with the Web Dynpro application. The data that a controller can access is defined in
the corresponding context. Different instances of controllers and contexts exist within a Web
Dynpro application.
View Controller
Each view has exactly one view controller, which processes the actions performed by the user in the view.
A view also has exactly one view context, which contains the data required for the view.
Interface Controller
Each Web Dynpro component contains exactly one component controller. This controller is a
global controller that is visible also outside the component. It is thus part of the interface of a
Web Dynpro component.
Context
Definition
The data used in the component or in the view are stored in the context. Read-write access to
this data is available using the controllers as a starting point.
Structure
The data from the contexts is managed in a hierarchical structure. Each context has a root
node, underneath which the individual data fields (attributes) are stored in a tree structure.
You create this tree structure according to the structure of your application.
CONTEXT is generally called as a ROOT Node.
Each context has nodes and attributes also.
Cardinatlity
Each node contains data fields that represent one of the following:
u2022
An individual instance of an object type
u2022
A table of instances.
This property of a node is known as its cardinality. The following table summarizes the
possible cardinalities for a node:
Cardinality Description
1:1 The node contains only one element instance, which is instantiated automatically.
0:1 The node contains only one element instance, which must not be instantiated.
1:n The node can contain multiple element instances, of which at least one must always be
instantiated (and is instantiated automatically).
0:n The node can contain multiple element instances, of which none have to be instantiated.
Further information about this and other properties of context nodes is available in the section
Context-Nodes: Properties.
Recursion Nodes
Dynamic node nesting is possible within a context, creating what is called a recursion node.
The node that is used for recursion is always a predecessor of the new node. The newly
created recursion node is a reference to a predecessor node and therefore cannot be
processed separately. Instead it takes on the structure of the node to be repeated.
Data Binding and Mapping
Within the Web Dynpro architecture, the contexts of the different controllers can be linked in
different ways:
u2022
A UI element of the user interface of the view can be linked with an element of the view
context.
u2022
A mapping can be defined between two global controller contexts, or from a view
context to a global controller context.
The context of a global controller can be linked to a Web Dynpro Model.
Defining Mapping Between Two Contexts
The elements of a view context can be locally defined. In this case (represented in the graphic
below as a "Local Node"), all the contained attributes are only visible within the relevant view.
When the view disappears, the attribute values are deleted.
Event
The component controller allows you to create events.
Events are used to communicate between controllers and enable one controller to trigger
event handlers in a different controller.
Cross-component communication can be implemented using the interface controlleru2019s events.
Events that were created in the component controller are visible within the component only.
Inbound Plugs
Inbound plugs in a view also react like an event. Therefore, when a view is called using an
inbound plug, the event handler that is optionally available for the inbound plug is always
called first. In this case event handling takes place within the current view controller.
UI Element Events
Some UI elements, such as the Button element have special events that are linked with user
actions. These events are predefined and have to be linked with an action at design time.
Actions for UI Element Events
Some UI elements such as the button element can react to a useru2019s interaction: clicking on
the corresponding pushbutton can trigger a handling method to be called within the view
controller. Such UI elements are equipped with one or several general events, which can be
linked with a specific action at design time (switching to a subsequent view, for example). If
such an action is created, an event handler method for this action is created automatically. In
this way, you can equip a UI element event (which has been inserted several times into a
view) with different actions as necessary. The event is then processed by the corresponding
event handler depending on the action that is linked.
Interfaces of Web Dynpro Components
Each component has an interface in order to enable communication between Web Dynpro
components and to enable a component to be called up by a user. This interface consists of
two parts:
Interface View of a Window Contained in a Component
The interface view of a Web Dynpro window is used to link a window with a Web Dynpro
application that can be called by the user.
Reward if helpful.
Best Wishes,
Chandralekha

Inconsistency between a document field and the prof. segment number

Hi,
While processing an invoice in one company code for vendor# XXX with the PO# AAAA line# 10, it is showing below error message while posting. Please advise on the below error or fix the issue to post the invoice in to SAP. The using screen T-code is miro.
Inconsistency between a document field and the prof. segment number
*Message no. KE396
*Diagnosis
A line item was assigned to a profitability segment (number 0008629207) which has the value 0000101000 for characteristic Profit Center. The original document (FI document, sales order, internal order, etc.), however, contains 0000102020 in this field. It is therefore inconsistent with the profitability segment found.
System response
The characteristics in Profitability Analysis (CO-PA) must have the same characteristic values as the original document. For example, you cannot assign a sales order to a different customer or product than the one contained in the original sales order. If you wish to fill the characteristics with different contents, you must change the original fields.
Procedure
Enter the correct characteristic values on the CO-PA assignment screen. The system will automatically assign a corresponding profitability segment number. If it is not possible to enter values in some of these fields, delete the entire assignment to a profitability segment number and then enter it again.
As a rule, you should first enter the fields in the original sender document and then make the assignment to a profitability segment.
What should I do for the above pl ?
Regards
Murali

Hi,
While doing PGR at VL32N, we are facing this error. Can someone assist.
Regards,
Aruna

IT2001 error, no time constraint reachion for infotype 2001 with tm const00

Dear Seriors,
When I try to add any absence, it show the below given error message (red colour), but if I hit the enter button it allows me to mark absence.
no time constraint reachion for infotype 2001 with time constraint class 001
What might be the reason?
Regards
ET

The time constraint class is used to check for collisions between Time Management infotypes (2001 to 2012). It allows you to specify different regulations for checking for collisions between individual subtypes.
The views Time Constraint Reaction to Time Management Infotypes (V_554Y_B) and Global Time Constraint Reaction (V_T554Y) contain rules for the collision check.
Please explore on this.

Property and Property Definition for a Node

Hi all,
While retrieving meta data for each node, I could not understand whether Property for a node represents meta data or Property Definition. Please provide a clear understanding and difference between the two.
Second, is there a predefined fixed set of Property and Property Definition for a node (for any given portal application)?
Provide inputs.
Thanks,
Shakti

Hi Shakti,
A node has two types of metadata -- the built-in system metadata such as node name, node path, node objectClass, create date, modified date, created by, etc -- visible via getXXX methods on the Node object, and the user-defined metadata.
The system metadata applies to all nodes regardless of ObjectClass (and also to nodes without any ObjectClass).
The user-defined metadata depends on the Node's ObjectClass. A node with no objectClass cannot have any user-defined metadata. A node with an objectClass can have the metadata defined by the ObjectClass's Property Definitions.
Suppose Node n has ObjectClass "StringType", and StringType ObjectClass has two property definitions -- StringVal (single-valued string), and BinaryVal (single-valued binary). In this case, Node n can have zero, one, or two user-defined properties from the set 'StirngVal' and 'BinaryVal'.
In short, a PropertyDefinition is a schema, part of the ObjectClass definition, whereas a Property is an instance of a PropertyDefinition attached to a node of the ObjectClass.
-Steve

[Error ORABPEL - 10900]... : Can not find definition for element 'process'

Hi,
When I try to deploy a bpel process using JDeveloper I'm having the following xml parse error:
Error(21):
[Error ORABPEL-10900]: xml parser error
[Description]: in line 21 of "file:/C:/JDeveloper/jdev/mywork/NERGA/CriarProjectoSA/bpel/CriarProjectoSA.bpel", XML parsing failed because file:/C:/JDeveloper/jdev/mywork/NERGA/CriarProjectoSA/bpel/CriarProjectoSA.bpel<Line 21, Column 63>: XML-24538: (Error) Can not find definition for element 'process'.
[Potential fix]: Fix the invalid XML.
I don't understand why... Any idea?

Ok.
This is my BPEL code. The sapattern tags are from a program that is generating part of the code. The JDeveloper doesn't show any error, I only get the error when I try to deploy.
<?xml version = "1.0" encoding = "UTF-8" ?>
<process name="CriarProjectoSA"
targetNamespace="http://xmlns.oracle.com/CriarProjectoSA"
suppressJoinFailure="no"
xmlns="http://xmlns.oracle.com/CriarProjectoSA"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:ns4="http://xmlns.oracle.com/CriarProjectoSA"
xmlns:ns7="http://xmlns.oracle.com/bpel/services/IdentityService/xpath"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:ns5="http://schemas.oracle.com/xpath/extension"
xmlns:ns6="http://xmlns.oracle.com/bpel/workflow/xpath"
xmlns:ns11="http://www.oracle.com/XSL/Transform/java/oracle.tip.esb.server.headers.ESBHeaderFunctions"
xmlns:ns9="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.ExtFunc"
xmlns:ns1="http://xmlns.oracle.com/ValidacaoProjectos"
xmlns:ns3="http://www.nerga.pt" xmlns:ns2="http://tempuri.org/"
xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
xmlns:ns10="http://www.oracle.com/XSL/Transform/java/oracle.tip.pc.services.functions.Xpath20"
xmlns:ns8="http://schemas.xmlsoap.org/ws/2003/03/business-process/">

<sapattern>
<guid>41207640-d934-480f-902a-b3764f3d9c9f</guid>
</sapattern>
<partnerLinks>
<partnerLink name="client" partnerLinkType="ns4:CriarProjectoSA"
myRole="CriarProjectoSAProvider"/>
<partnerLink name="NergaIS" partnerLinkType="ns2:ServiceSoap_PL"
myRole="ServiceSoap_Role" partnerRole="ServiceSoap_Role"/>
<partnerLink name="ValidacaoProjectos"
partnerLinkType="ns1:ValidacaoProjectos"
myRole="ValidacaoProjectosRequester"
partnerRole="ValidacaoProjectosProvider"/>
<sapattern>

<guid>e728e550-f404-47bf-aa13-72429480cbc6</guid>
<guid>3111d1af-0b31-4d02-b3fc-73d14ce95405</guid>
<guid>e9cdca59-888a-4e67-af54-a63ce2347ad3</guid>
</sapattern>
</partnerLinks>
<variables>
<variable name="outputVariable"
messageType="ns4:CriarProjectoSAResponseMessage"/>
<variable name="inputVariable"
messageType="ns4:CriarProjectoSARequestMessage"/>
<sapattern>

<guid>2503e820-3add-4cd1-bbc5-5cc5fff57090</guid>
<guid>8bcc3532-46b7-4e88-816f-72ecdaee76ab</guid>
</sapattern>
<variable name="invocaVP_initiate_InputVariable"
messageType="ns1:ValidacaoProjectosRequestMessage"/>
<variable name="recebeVP_onResult_InputVariable"
messageType="ns1:ValidacaoProjectosResponseMessage"/>
<variable name="InvocaAdicionarProjecto_InputVariable"
messageType="ns2:AdicionarProjectoSoapIn"/>
<variable name="InvocaAdicionarProjecto_OutputVariable"
messageType="ns2:AdicionarProjectoSoapOut"/>
</variables>
<sequence>
<receive name="recebeTemplate" joinCondition="False" partnerLink="client"
portType="ns4:CriarProjectoSA" operation="process"
variable="inputVariable" createInstance="yes">
<sapattern>

<guid>e728e550-f404-47bf-aa13-72429480cbc6</guid>
<guid>68e62379-55ac-48eb-b681-aee8f5a7696d</guid>
</sapattern>
</receive>
<scope variableAccessSerializable="no" name="ValidarExigências"
joinCondition="False">
<faultHandlers>
<catchAll>
<assign name="assignInvalid">
<bpelx:append>
<bpelx:from expression="concat(ns8:getVariableData('inputVariable','payload','/ns3:Template/ns3:Projecto/ns3:Observacoes'), string('Projecto inválido!!'))"/>
<bpelx:to variable="inputVariable" part="payload"
query="/ns3:Template/ns3:Projecto/ns3:Observacoes"/>
</bpelx:append>
</assign>
</catchAll>
</faultHandlers>
<sapattern>

<guid>2e56af66-6622-43e0-9adc-6d5f109cf374</guid>
</sapattern>
<sequence name="ValidarExigências" joinCondition="False">
<assign name="assignVPIn">
<copy>
<from variable="inputVariable" part="payload"/>
<to variable="invocaVP_initiate_InputVariable" part="payload"/>
</copy>
</assign>
<sapattern>

<guid>2e56af66-6622-43e0-9adc-6d5f109cf374</guid>
</sapattern>
<invoke name="invocaVP" joinCondition="False"
partnerLink="ValidacaoProjectos" portType="ns1:ValidacaoProjectos"
operation="initiate"
inputVariable="invocaVP_initiate_InputVariable">
<sapattern>

<guid>f3bc9c04-f4d2-4e96-acc8-7a6c88a8ced5</guid>
</sapattern>
</invoke>
<receive name="recebeVP" joinCondition="False"
partnerLink="ValidacaoProjectos"
portType="ns1:ValidacaoProjectosCallback" operation="onResult"
createInstance="no" variable="recebeVP_onResult_InputVariable">
<sapattern>

<guid>e9cdca59-888a-4e67-af54-a63ce2347ad3</guid>
<guid>1eba96a8-330a-4e4d-a14b-cdf6641fa614</guid>
</sapattern>
</receive>
<assign name="assignVPOut">
<copy>
<from variable="recebeVP_onResult_InputVariable" part="payload"/>
<to variable="inputVariable" part="payload"/>
</copy>
</assign>
</sequence>
</scope>
<scope variableAccessSerializable="no" name="AdicionarProjecto"
joinCondition="False">
<sapattern>

<guid>89c02eae-7788-4892-a616-e46b65ef1b50</guid>
</sapattern>
<sequence name="InvocarISAdicionarProjecto" joinCondition="False">
<assign name="assignIS">
<copy>
<from variable="inputVariable" part="payload"
query="/ns3:Template/ns3:Projecto/ns3:NomeProjecto"/>
<to variable="InvocaAdicionarProjecto_InputVariable" part="parameters"
query="/ns2:AdicionarProjecto/ns2:nome"/>
</copy>
<copy>
<from variable="inputVariable" part="payload"
query="/ns3:Template/ns3:Projecto/ns3:TipoProjecto"/>
<to variable="InvocaAdicionarProjecto_InputVariable" part="parameters"
query="/ns2:AdicionarProjecto/ns2:tipo"/>
</copy>
</assign>
<sapattern>

<guid>89c02eae-7788-4892-a616-e46b65ef1b50</guid>
</sapattern>
<invoke name="InvocaAdicionarProjecto" joinCondition="False"
partnerLink="NergaIS" portType="ns2:ServiceSoap"
operation="AdicionarProjecto"
inputVariable="InvocaAdicionarProjecto_InputVariable"
outputVariable="InvocaAdicionarProjecto_OutputVariable">
<sapattern>

<guid>76519bd3-c506-4c79-8190-8ff09abdd27d</guid>
</sapattern>
</invoke>
</sequence>
</scope>
<assign name="assignOutput">
<copy>
<from variable="inputVariable" part="payload"
query="/ns3:Template/ns3:Projecto"/>
<to variable="outputVariable" part="payload"/>
</copy>
</assign>
<reply name="devolveProjecto" joinCondition="False" partnerLink="client"
portType="ns4:CriarProjectoSA" operation="process"
variable="outputVariable">
<sapattern>

<guid>e728e550-f404-47bf-aa13-72429480cbc6</guid>
<guid>0dbefef0-3d04-4356-abbc-b291ea40d256</guid>
</sapattern>
</reply>
</sequence>
</process>

.v2.XMLParseException:Can not find definition for element 'descriptor'

I am getting the following error, while running 'empps.jsp' ...when executing the tutorial given at
ERROR Details:
500 Internal Server Error
javax.servlet.jsp.JspException: javax.faces.el.EvaluationException: Error getting property 'employees' from bean of type jsftoplink.model.EmployeesClient: Exception [TOPLINK-25004] (Oracle TopLink - 10g Release 3 (10.1.3.1.0) (Build 061004)): oracle.toplink.exceptions.XMLMarshalExceptionException Description: An error occurred unmarshalling the documentInternal Exception: Exception [TOPLINK-27101] (Oracle TopLink - 10g Release 3 (10.1.3.1.0) (Build 061004)): oracle.toplink.platform.xml.XMLPlatformExceptionException Description: An error occurred while parsing the document.Internal Exception: oracle.xml.parser.v2.XMLParseException: Can not find definition for element 'class-descriptor-type' at com.sun.faces.taglib.html_basic.DataTableTag.doEndTag(DataTableTag.java:501) at emps.jspService(_emps.java:629)
Pls help me in resolving this issue.

I am still gettng the same error. The xml file is now
<?xml version="1.0" encoding="UTF-8"?>
<CUSTOMER xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="" ID="568945">
<FIRSTNAME>Arnold</FIRSTNAME>
<LASTNAME>McEriccson</LASTNAME>
<ADDRESS>
<LINE1>31, Nomadic Avevnue</LINE1>
<LINE2>Pasadena Clove</LINE2>
<CITY>WoolTown, MT</CITY>
<ZIP>45263</ZIP>
</ADDRESS>
<BIRTHDATE>1967-08-13</BIRTHDATE>
</CUSTOMER>
The xsd file is:
<?xml version="1.0" encoding="UTF-8"?><xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:element name="CUSTOMER">
<xs:complexType>
<xs:sequence>
<xs:element name="FIRSTNAME" type="xs:string"/> <xs:element name="LASTNAME" type="xs:string"/> <xs:element name="ADDRESS"> <xs:complexType>
<xs:sequence>
<xs:element name="LINE1" type="xs:string"/> <xs:element name="LINE2" type="xs:string"/> <xs:element name="CITY"/>
<xs:element name="ZIP" type="xs:int"/> </xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="BIRTHDATE" type="xs:date"/> </xs:sequence>
<xs:attribute name="ID" type="xs:double"/> </xs:complexType>
</xs:element>
</xs:schema>
There seems to be something fairly obvious that i am missing.

STRUTS - Cannot retrieve definition for form bean null -aaaarrrrgh

Hi Folks,
my head hurts and i become crazy... i know that a lot of people asked this question before, but i did not found any suitable solution.
I have simple a jsp page, containing a form which should be handled by struts. I tried everything, but i did not found my mistake.
Can anyone help me please?
JSP:
<%@ taglib uri="/WEB-INF/struts-bean.tld" prefix="bean"%>
<%@ taglib uri="/WEB-INF/struts-html.tld" prefix="html"%>
<%@ page contentType="text/html;charset=windows-1252"%>
<html:html locale="true">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<title>Anmeldung f?r GOLEM Quickplayout</title>
</head>
<body>
<html:errors/>
<html:form action="checkLogin.do">
<table cellspacing="3" cellpadding="2" border="0" width="100%" align="left">
    <tr>
      <td>
        <bean:message key="prompt.username"/>
      </td>
      <td>
        <html:text property="username"/>
      </td>
    </tr>
    <tr>
      <td>
        <bean:message key="prompt.password"/>
      </td>
      <td>
        <html:text property="password"/>
      </td>
    </tr>
</table>
</html:form>i tryed a lot for the FORM -Tag, for instance:
<html:form action="checkLogin.do"> or
<html:form action="/checkLogin.do"> or
<html:form action="/checkLogin"> but all throws the same exception. :(
struts-config.xml
<form-beans>
    <form-bean name="loginForm" type="de.orb.quick.view.LoginForm"/>
</form-beans>
<action-mappings>
<action path="/login" type="de.orb.quick.view.LoginAction" name="loginForm" input="/login.jsp" scope="session" unknown="true">
    <forward name="success" path="/showData.jsp"/>
</action>
    <action path="/checkLogin" type="de.orb.quick.view.CheckLogonAction" unknown="false" input="/login.jsp">
      <forward name="success" path="/storeRequestData.do"/>
      <forward name="failure" path="/login.do"/>
    </action>
Exception:
javax.servlet.jsp.JspException: Cannot retrieve definition for form bean null
     at org.apache.struts.taglib.html.FormTag.lookup(FormTag.java:831)
     at org.apache.struts.taglib.html.FormTag.doStartTag(FormTag.java:506)
     at _login._jspService(login.jsp:11)     [/login.jsp]
LoginAction:
public ActionForward execute(ActionMapping mapping, ActionForm form, HttpServletRequest request, HttpServletResponse response) throws IOException, ServletException {
    return mapping.findForward("success");
LoginForm:
public class LoginForm extends ActionForm {
private String password = "";
private String username = "";
public void reset(ActionMapping mapping, HttpServletRequest request) {
    super.reset(mapping, request);
public ActionErrors validate(ActionMapping mapping, HttpServletRequest request) {
    return super.validate(mapping, request);
public String getPassword() {
    return password;
public void setPassword(String password) {
    this.password = password;
public String getUsername() {
    return username;
public void setUsername(String username) {
    this.username = username;
}Sorry for this stupid question, but how can i avoid this exception while using struts TagLibs?
I tried to face the jsp with another action, but this does not change anything.
Thank you in advance
Mirko

javax.servlet.jsp.JspException: Cannot retrieve definition for form bean myfrom
     at org.apache.struts.taglib.html.FormTag.lookup(FormTag.java:831)
     at org.apache.struts.taglib.html.FormTag.doStartTag(FormTag.java:506)
     at jsp_servlet.__index._jspService(__index.java:155)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6291)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3575)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2573)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)

Cannot retrieve definition for form bean null

Hi,
          I have a page jsp which contains a form. This form contains an action
          towards (page.do ).
          I configured struts-config.xml file in whom I put a configuration of
          action ( type=xxx.pageAction ) but not form because I have not need of
          it.
          During the execution it show that it tries to instantiate a bean of form
          corresponding to a configuration of action and post this error message
          " Root causes of ServletException javax.servlet.jsp. JspException:
          Cannot retrieve definition for form bean null "
          Could you indicate to me where is the problem ?
          Here is my configuration :
          < html:form action = " page.do " method = " post " >
          </html:form >
          <action path="/page"
          type="xxx.pageAction">
          <forward name="show" path="/page.jsp"/>
          </action>
          Thanks in advance
          Rachid.


There's little reason to use Struts infrastructure to set this up since you have no model, and the controller aspect is well-defined (just go to "NewProject"!). You're basically providing a link from one page to another, akin to doing an <a href>, and you wouldn't use Struts to do a simple link :).
I would just just use standard HTML.
If you're okay with using Javascript, this is the simplest:
<input type="button" onClick="document.location='NewProject'">
Or you can use a standard HTML form, as you've basically done already:
<form action="NewProject" method="get">
<input type="submit" value="Create">
</form>

IMP-00093: Inconsistency between dumpfile constraint definition for table

Similar Messages

Maybe you are looking for