Database Inconsistency Warning

I tried to open from the external hard drive and I got the following message:
"Warning
An inconsistency in your database has been detected. The application will now quit, relaunch, and restore your database to a consistent state. This may take some time."
My opitions is to quit, and restore, but Aperture never restores the database. I get the message over and over again.
I tried holding the Command + Option to rebuiled library but it doesn't work..please help.

I've never had the situation you're both describing, but perhaps this will help...
When you hold down option-apple and force the database to rebuild, from my observations it seems to delete the old library file, and recreate the file from all the other spread-around-the-bundle files. It looks to me as though Apple were making sure the data could be accessed fast (via a SQL database file) and also was robust against corruption (lots of XML files).
So, perhaps it's not managing to delete that library file (a permissions problem ?). Try this:
Right-click (ctrl-click) on your library bundle, and select 'show package contents'
Double-click on the 'Aperture.aplib' folder
Drag the 'Library.apdb' file to the trash. If it doesn't go, you'll have to delete it with 'sudo'.
... and then re-launch Aperture. You should get a 'Library alert' dialogue box, at which point click on 'recover now'. It'll take a while if it's a large library...
-=C=-
Mac Pro Mac OS X (10.4.8)

Similar Messages

Database Inconsistency Nightmare

As an avid user and supporter of Aperture since it's release, I now have an new issue. I am a pro photojournalist using Aperture every day for all my magazine assignment work and I feel like I know the program very well after 2+ years of heavy daily use.
I have never had any serious problems with the program at all, until one week ago.
The problems started when I launched aperture and got a database inconsistency dialog box. I was not too worried as I have had this once or twice in the past and I just relaunched the app with apple and option keys down and rebuilt the database. Everything seemed ok but then I noticed that 2,400 of my 12,000 referenced images were tagged as missing. I thought this was strange, and I used "Manage Referenced Files" to see what was going on and reconnect the missing files. I also noticed that 2 subjects had a second version not in a stack that contained the thumbnail for each image without metadata, while the normal version and stack with metadata had no thumbnail! On my FireWire drive 1 which holds a first copy of all referenced files in my library, each subject has a corresponding folder and I started to reconnect the offline and missing files. For most of the subjects everything went fine, but then there were 4 subjects where I encountered very unexpected problems. Firstly the names of the Master images for some subjects had been changed more that one year earlier, but the reconnect dialog box showed the original filename from the camera as the master filename. It did not want to "Reconnect All" so the only way is one by one!
Then I notice that the smart folders set to show "Offline" and "Missing" masters are inaccurate for some reason.
I even have a few "Managed" masters that will not export because the dialog box comes up to tell me that the image is "Offline" or "Unavailable". What? Ok so at this point I decide that since I have everything backed up on two separate Firewire drives and a server in California, that it may just be cleaner to reinstall Aperture and revert to a recent Vault. I did this and guess what, same problems plus a few more headaches reconnecting masters!
The biggest problem at this point is that for two subjects, the captions and adjustments are in a version that has no thumbnail, shows the "Missing" tag in the Metadata panel listing the original filename from the camera as the Master Filename, while there is a new mysterious version 2 which has a thumbnail, no caption, the offline tag and and shows the correct Master Filename. If I reconnect the masters for these images it still shows as missing for the normal version which has the captions, keywords and adjustments.
At this point I have decided that for two of the subjects One is Versailles 600 images and the other Cyprus 700 images, that I will probably end up having to just reimport these two subjects and manually move the caption for each image.
This is all starting to make me call into question the stability of this type of system for archiving large amounts of images. True that with all the backups and the normal robustness of Aperture you should not loose images. But if the Masters get unlinked in a corrupt way from the database you CAN loose a large part of your post processing work. And the worst seams to be that this can happen even if you DO know what you are doing.
This does not at all mean I am going to stop using Aperture, but it does make me feel a little more weary from an archival standpoint about keeping all metadata and adjustments separate from master images.

Thanks for all your replies. And yes the Project container is a fantastic way to back things up. It is especially useful for moving a project from one Library to another without risk of overwriting files.
Naturally if I could get my corrupt projects in order I would export the projects, including the masters and then reimport them. But Aperture is not going to let me do that with these corrupt Projects, as the masters are not be properly linked. I have tried everything I could think of.
There are still some really weird things going on with the database in my library. One really strange thing is that some referenced images that DO have the master linked and show the normal reference tag, but will not Consolidate as the dialog comes up "The selection does not contain any referenced files".
But then for the same image you can choose "Show in finder" and it goes straight to the master on it's external drive! How strange is that. For that matter it will also not "Relocate Master" for the image because it says that the master is "Offline or cannot be found". OK then here comes the weirdest part: It will export the image without a hitch! Managed referenced files shows these images as connected and black.
Then the other really bad thing is that some of the managed images will not export or relocate as the dialog comes up "Offline or cannot be found". I have rebuilt the library and everything else to no avail.
The thing that bothers me about this is that if this can happen to me, who spends untold hours on Aperture and on the computer in general and I believe I do know quite a lot about the program, what is going to happen to the many photographers who do not fully grasp the abstract file management of Aperture?
Maybe it is more stable to run your Library as Managed, but for working photographers who are usually laptop users it is almost essential to keep the masters on an external Ruggged drive. If you put the Library on the external drive the performance which is already sometimes sluggish when you need to work very quickly (even with the most powerful MacBook Pro) becomes too beach ball when on an external drive.
In any event I think that if I can ever get my Library back in order, in addition to the many backups of masters and vaults, I am going to export each project including masters and back that up too on a regular basis. Seems like a lot of work backing up to maintain the integrity of a database!
Cheers

Cannot Activate data type in ABAP Database Inconsistent

Hi,
can you please help me on this? We could not activate the data type abap proxy in SPROXY.
Here is the error:
Database inconsistent: TABL XYZ not found.
The object is inactive. Is there a way to delete the object in the backend?
Or do you know other way to solve this?

I already recreated the object in ESR, but we are still getting the error in SPROXY whether you regenerate, delete or activate proxy. If I checked the proxy name, it is in a form of a structure and is activated but the data type in SPROXY is still in inactive mode.
I could not remember how this error came up but it seems dependent objects for the data type are not generated properly that's why the error is TABL object is not found.
Do you have other way on how to delete the inactive proxy in ABAP?

Deleting all special GL can cause Database inconsistency?

Hi Expert,
With reference to the subject, I wonder deleting special GL indicators can cause database inconsistency.
My Case:
I deleted all of the SAP special GL indicator, and recreated those I want with my own naming convention, which some of them same with the standard come with SAP. I did it in client 100, and not yet SCC1 to sandbox (client 120).
After the deletion, when I run FB01, FB03, etc, I faced error: Inconsistency in the length of DDIC data type "FBSEG ...
I faced both problem in client 100 and 120 (I have not changed anything here).
Question:
Is it my deletion cause the database inconsistency?
Why client 120 also have same error?
Now, basis is figuring the problem, and suspect also the database issue, and not my special GL deletion.
Kindly advise.
Thanks and regards,
sbmel

Dear expert
Instead of deleting special G/l indicator you can follow "use transaction FB00, under Document Entry tab there is General Entry Option where select No Special G/L transaction"
1329034 - "Correcting inconsistency
check notes 707715, 929259
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21f0d1446011d189700000e8322d00/frameset.htm
Regards
Ajeesh.s

Next Number Maintenance - Database inconsistency

Hi ,
I did basic configurations in SAP ME. I also did Next number maintenance as a part of configuration. I have created few shop orders and completed successfully with NC .
Recently we have upgraded to SAP ME 5.2.4.3 from 5.2.4.1
Now I have added some more materials to the same plant and trying to create inventory for those materials in Inventory Receipt.
I am getting the following message.
Database inconsistency: "Invalid Next Number return" (Message 1006)
I am able to create inventory for the old materials even now.But not for the newly added materials.
Did I miss something after patch upgrade? or is it configuration problem?
Regards,
Guru.

Hi,
it looks weird. Could you look at the default trace? What is the stack trace behind the exception you get?
What if you try just to copy old material under a new name? Does it work?
Regards,
Anton

How to solve "Database inconsistent" error?

Hi,
when clicking on a task in my UWL i get this error. Why is that? How can i solve it?
TIA
Michael
500   Internal Server Error           SAP NetWeaver Application Server/Java AS
The initial exception that caused the request to fail, was:
com.sap.bpem.tm.exception.TechnicalTaskException: Database inconsistent, please contact your system administrator
    at com.sap.bpem.tm.impl.TaskManagerImpl.identifyNoSuchTaskExceptionFlavor(TaskManagerImpl.java:1567)
    at com.sap.bpem.tm.impl.TaskManagerImpl.getTaskInstanceObject(TaskManagerImpl.java:1524)
    at com.sap.bpem.tm.impl.TaskManagerImpl.getTask(TaskManagerImpl.java:1032)
    at com.sap.bpem.tm.impl.TaskManagerBean.getTask(TaskManagerBean.java:79)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    ... 91 more
See full exception chain for details.
Failed to process request. Please contact your system administrator.
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
For further information about the Web Dynpro error page, error analysis and a description of well-known error situations, see SAP note 1113811.
System Environment
Client
Web Dynpro Client Type     HTML Client
User agent     Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7
Client Type     ns7
Client Type Profile     nn7
ActiveX     disabled
Java Applets     enabled
Accessibility mode     disabled
Rendering engine:     Lightspeed
Inline CSS:      enabled
Validate by rendering:      enabled
Server
Web Dynpro Runtime     vendor: 'sap.com', name: 'tc/wd/webdynpro', location: 'SAP AG', counter: '7.1101.20081121165726.0000', change number: '34307', codeline: NW711_01_REL
J2EE Engine     7.11.3710.34306.20081117170308
System ID (SID)     HNC
Server Node ID     |5055250|50552|Server 00 00_50552|saphnc/10.213.20.68|SERVER|RUNNING
Java VM     SAP Java 64-Bit Server VM, version:5.1.024, vendor: SAP AG
Operating system     Windows 2003, version: 5.2, architecture: amd64
Application
Java EE Application (deployable object)     sap.com/tcbpemwdui~taskinstance
Web Dynpro Application     ATaskExecution
Request URI     /webdynpro/dispatcher/sap.com/tcbpemwdui~taskinstance/ATaskExecution
Version     vendor: 'sap.com', name: 'tc/bpem/wdui/taskinstance', location: 'SAP AG', counter: '7.1101.20081107110357.0000', change number: '31'
Session & Other
Session Locale     de_DE
Session Timezone     Central European Time
Time of Failure     Tue Mar 24 12:18:45 CET 2009 (Java Time: 1237893525656)
Session User     ClientUser(id=USER.PRIVATE_DATASOURCE.un:neumann, name=neumann)
Client Session Id     p6E1GkmC7IqjpxmHR9bKm6ipRLUa3H83IAESI00A_SAP
Client Window Id     WIDx1237893542193
Application Session Id     pBsSrSGyXYyMkAL31ExbcA9YvaW5iZijHiiopfzm48oA
Web Dynpro Code Generation Infos
sap.com/tcbpemwdui~appcontainer
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapDictionaryGenerationCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:24:23+0000, changelist=31630, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapDictionaryGenerationTemplates     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:24:49+0000, changelist=31630, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapGenerationFrameworkCore     7.1101.20081107110357.0000
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapIdeWebDynproCheckLayer     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:36:35+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapMetamodelCommon     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:14:39+0000, changelist=32070, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapMetamodelCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:11:46+0000, changelist=32070, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapMetamodelDictionary     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:19:49+0000, changelist=31632, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapMetamodelWebDynpro     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:25:44+0000, changelist=32739, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapWebDynproGenerationCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:36:46+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapWebDynproGenerationTemplates     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:37:12+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~appcontainer: SapWebDynproRuntimeGen     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:34:49+0000, changelist=32183, host=pwdfm245, is-central=true)
sap.com/tcbpemwdui~attachments
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapDictionaryGenerationCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:24:23+0000, changelist=31630, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapDictionaryGenerationTemplates     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:24:49+0000, changelist=31630, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapGenerationFrameworkCore     7.1101.20081107110357.0000
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapIdeWebDynproCheckLayer     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:36:35+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapMetamodelCommon     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:14:39+0000, changelist=32070, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapMetamodelCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:11:46+0000, changelist=32070, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapMetamodelDictionary     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:19:49+0000, changelist=31632, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapMetamodelWebDynpro     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:25:44+0000, changelist=32739, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapWebDynproGenerationCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:36:46+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapWebDynproGenerationTemplates     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:37:12+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~attachments: SapWebDynproRuntimeGen     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:34:49+0000, changelist=32183, host=pwdfm245, is-central=true)
sap.com/tcbpemwdui~notes

WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapDictionaryGenerationCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:24:23+0000, changelist=31630, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapDictionaryGenerationTemplates     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:24:49+0000, changelist=31630, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapGenerationFrameworkCore     7.1101.20081107110357.0000
WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapIdeWebDynproCheckLayer     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:36:35+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapMetamodelCommon     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:14:39+0000, changelist=32070, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapMetamodelCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:11:46+0000, changelist=32070, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapMetamodelDictionary     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:19:49+0000, changelist=31632, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapMetamodelWebDynpro     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:25:44+0000, changelist=32739, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapWebDynproGenerationCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:36:46+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapWebDynproGenerationTemplates     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:37:12+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~notes: SapWebDynproRuntimeGen     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:34:49+0000, changelist=32183, host=pwdfm245, is-central=true)
sap.com/tcbpemwdui~taskinstance
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapDictionaryGenerationCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:24:23+0000, changelist=31630, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapDictionaryGenerationTemplates     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:24:49+0000, changelist=31630, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapGenerationFrameworkCore     7.1101.20081107110357.0000
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapIdeWebDynproCheckLayer     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:36:35+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapMetamodelCommon     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:14:39+0000, changelist=32070, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapMetamodelCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:11:46+0000, changelist=32070, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapMetamodelDictionary     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:19:49+0000, changelist=31632, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapMetamodelWebDynpro     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:25:44+0000, changelist=32739, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapWebDynproGenerationCore     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:36:46+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapWebDynproGenerationTemplates     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:37:12+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcbpemwdui~taskinstance: SapWebDynproRuntimeGen     7.1101.20081107110357.0000 (release=NW711_01_REL, buildtime=2008-11-08T19:34:49+0000, changelist=32183, host=pwdfm245, is-central=true)
sap.com/tcwdapi
WD web module webdynpro/resources/sap.com/tcwdapi: SapDictionaryGenerationCore     7.1101.20081121165726.0000 (release=NW711_01_REL, buildtime=2008-11-22T19:30:00+0000, changelist=31630, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcwdapi: SapDictionaryGenerationTemplates     7.1101.20081121165726.0000 (release=NW711_01_REL, buildtime=2008-11-22T19:30:16+0000, changelist=31630, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcwdapi: SapGenerationFrameworkCore     7.1101.20081121165726.0000
WD web module webdynpro/resources/sap.com/tcwdapi: SapIdeWebDynproCheckLayer     7.1101.20081121165726.0000 (release=NW711_01_REL, buildtime=2008-11-22T19:43:48+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelCommon     7.1101.20081121165726.0000 (release=NW711_01_REL, buildtime=2008-11-22T19:21:10+0000, changelist=32070, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelCore     7.1101.20081121165726.0000 (release=NW711_01_REL, buildtime=2008-11-22T19:17:50+0000, changelist=32070, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelDictionary     7.1101.20081121165726.0000 (release=NW711_01_REL, buildtime=2008-11-22T19:25:15+0000, changelist=31632, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcwdapi: SapMetamodelWebDynpro     7.1101.20081121165726.0000 (release=NW711_01_REL, buildtime=2008-11-22T19:31:48+0000, changelist=32739, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcwdapi: SapWebDynproGenerationCore     7.1101.20081121165726.0000 (release=NW711_01_REL, buildtime=2008-11-22T19:43:58+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcwdapi: SapWebDynproGenerationTemplates     7.1101.20081121165726.0000 (release=NW711_01_REL, buildtime=2008-11-22T19:44:06+0000, changelist=32179, host=pwdfm245, is-central=true)
WD web module webdynpro/resources/sap.com/tcwdapi: SapWebDynproRuntimeGen     7.1101.20081121165726.0000 (release=NW711_01_REL, buildtime=2008-11-22T19:42:01+0000, changelist=32183, host=pwdfm245, is-central=true)
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session ApplicationSession(id=pBsSrSGyXYyMkAL31ExbcA9YvaW5iZijHiiopfzm48oA, name=com.sap.tc.bpem.wdui.taskinstance.ataskexecution.ATaskExecution). The causing exception is nested. RID=8a21d490186511de8a38000c2932868d
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doPreprocessing(ClientSession.java:680)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:239)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:258)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:202)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:127)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:95)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:92)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:104)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:61)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:466)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:291)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:396)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:385)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:76)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:240)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)

Suppress Power Query's Native Database Query Warning

Is there a way to suppress the "Native Database Query" warning issued by Power Query when running a SQL query directly against a Teradata database? This warning states, "You are about to run a native database query. Native queries
can make changes to the database. Would you like to run the following query?"

If we never prompted here, then I could send you a workbook with the embedded query "drop table foo". You'd open it, Power Query would run analysis and we'd execute the statement -- all before you had any idea what had happened. It's true that
there are many potential users for whom showing the SQL text isn't useful. Hopefully, those users don't have the kinds of server permission that would let a query run with their credentials do lasting damage. But the prompt is to deal with the very possible
risk of having even a sophisticated user run a query by accident that they shouldn't have.
The original intent of the feature was to support a scenario where a user says "I already have a SQL query whose output I want to consume into Power Query; why can't I just use that?" It did not take parameterization into account. We subsequently
considered adding parameterization to this method, but didn't feel that we could sufficiently guarantee security. That is, if your query text is Sql.Database("server", "database", [Query="exec @sql", Parameters=[sql="drop
table foo"]], the user would be prompted only with "exec @sql" and the malicious payload would be delivered invisibly.
We very much do not want to have the responsibility of parsing multiple different dialects of SQL to try to guess whether or not it contains potentially-malicious code.
Our current thinking on this is that we might let advanced users write "trusted code" which has to go through a separate verification step. Code of this type might be able to generate SQL statements without a user prompt. So a workbook might have
a dependency on the "My Trusted Code" module, and simply won't run if that module hasn't been installed on the local machine. The user would then need a trustworthy (but convenient) way to obtain that module from a trustworthy source.

Aperture 10.8.3 library upgrade database inconsistency?

After updating to Aperture 3.4.4, I am unable to update vaults from either of my two Aperture libraries. A warning reads "An inconsistency in your database has been detected. The application will now quit, relaunch, and restore your database to a consistent state. This may take some time." In fact, that does not happen (waited 12 hours). I have gone through all three levels of Library first aid with no joy. Libraries are 288 GB and 128 GB. Is there a fix? Should I delete the vaults and set up new ones, or is the problem with my Aperture libraries themselves?

I had always been reluctant to "Repair Database". fearing it might screw something up and will do that in the future prior to upgrades.
Bill
Bill,
"repair database" and "repair permissions" are routine maintainance operations, perfectly safe to use.
They will check the permissions and the integrity of the internal databases and fix minor glitches. Only it may take some time, if your library is large.
I use these tools routinely to ensure my library is in perfect working condition before any major operations, like updating the library to a new Aperture version or moving it to a new location.
The third fix "rebuild library" will do a major reconstruction of the library, and if the library is already badly damaged it might make matters worse. It is highly recommended to check the backup of the library, if it is up to date, before rebuilding.
I could not do a restore from my SuperDuper Clone because it runs nightly and had already cloned the problematic libraries before I realized there was a problem.
I second Kirby's advice to use clones instead of the vault.
Just one more thing to add: Clones and vaults are only snapshots of one moment in time, and if you update your clone or vault you cannot go back in time. I include my Aperture library into my regular TimeMachine backup, so I can go back to previous versions, if need be, in addition to the clone.
In total I have three backups of every library.
If you do not have at least two backups, go for it. Your system may fail, when you are backing up, and both the backup and the computer may be damaged. This happened to me during a bad thunderstorm, when a lightning stroke close to our house and caused a power failure. I was very happy to have a second backup, on a drive that had not been turned on at that time.

BCS Program Termination - Database Inconsistency

We are using SEM-BW 4.0, SAP-BW 3.5, running BCS. We are trying to change the Breakdown Category of an FS Item going forward. The system allows to change and save the Breakdown Category as needed, but when we attempt to post a manual entry or run the data stream or any tasks, the BCS system crashes with the following error:
Transaction: UCWB_INT
Program: CL_UC_SELCOND_FACTORY in IF_UC_CUST_FACTORY~GET_INSTANCE_BY_GUID
The main program was UCUWB000
There is a composite note 859500 that explains GUID errors and how to prevent them from occurring in the future. We have either implemented all of the notes mentioned (via Support Packs) or they do not pertain to our release. However, this problem continues to happen. SAP indicates that even though these notes are applied, the database will be inconsistent and will need intervention from SAP to get it fixed. Since this has been occurring in our test system, we have been able to restore the system from backup. We have also seen note 805360 - Change of Breakdown Categories.
Has anybody else run into this issue, and if so, how did you get it resolved? We cannot let this happen in our production environment.
Any assistance is appreciated.

We are having the same issue when we try to execute few consolidation tasks. We have sent a message to SAP support and they are looking into the same.
We are not able to understand what GUI inconsistency means

Biztalk database inconsistency

Hi
I have a problem where I have two biztalk servers in the same group, and one of them have become very slow.
It is slow in the administrative console, and it is slow to process messages. The other server is fast in both the administrative console and process messages fast.
Is there possible that a inconsistency in one of the biztalk databases causes such a problem?

The Databases are, I assume, on a separate server. If so then Databases are not at fault. You need to check the network connectivity from the two servers to the DB server, Windows Firewall, MS DTC. If you have cloned a BizTalk Server to setup the second
one then the System Id would be the same (unless you used SysPrep) in which case the reason for slowness is likely to be because of MS DTC which is traceable to the non-unique System Id.
Regards.

Database inconsistency

Have you used RUTMSJOB before?
I run this report in SE38 and hits error, in the log file, it says some of the table/view is not consistence.
I went to SE14, entered the mentioned table/view then go to Extra ->Database Object ->Check, I have the same error saying there is inconsistency.
In SE14, I select the option u201CSave datau201D then click on Activate and Adjust data, but the problem is not solved.
Do you know how we can solve this problem?

Yes, I have correct error option. When I click on the correct error option, I have the message asking me to correct the error via SE14.
In SE14, I correct the error manually but dons't seem work.
Please advise, thanks.

Database limit warning when creating database copy

Exchange 2010 Standard SP3 RU3.
2 Server mailbox DAG.
I have 5 mailbox databases mounted. I have a copy of each database. WHen I try to create a copy for the 5th mailbox database I get the following warning "Server has reached the maximum database limit of 5.
Looking at my server, There was an old database that was never used in the exchange directory but its not listed in the EMC.
Is it possible that information about an old database still exists in AD? Where can I verify in Adsiedit what exchange databases it sees?

Hi,
One server limited to 5 databases in Exchange 2010 Standard edition.
So, from the description of your screenshot I summary the following information:
The following databases stayed on NASD-MBX1:
Mailbox Database Admin
Mailbox Database Faculty
Mailbox Database Faculty Large
Mailbox Database Faculty Medium
Mailbox Database Faculty Small (Mounted)
The following databases stayed on NASD-MBX2:
Mailbox Database Admin (Mounted)
Mailbox Database Faculty (Mounted)
Mailbox Database Faculty Large (Mounted)
Mailbox Database Faculty Medium (Mounted)
Public Folder Database (It should be here, right?) (Mounted)
Now, if we try to make a copy of “Mailbox Database Faculty Small”,
it will be available as a passive database copy on NASD-MBX2. However, there are five Database mounted on NASD-MBX2 including the Public Folder Database. So it will
get the error “Server has reached the maximum database limit of 5”. We can delete the Public Folder Database to test it.
In ADSIEdit, please refer the following image to find these databases.
Best Regards.

CiscoWorks LMS 4.0.1 - Database inconsistency

Hello all,
I have a problem with LMS 4.0.1.
In the Inventory / Device Administration, I see all the devices, monitoring works perfect (highutilization, operationallydown, etc.). User Tracking works fine for 85% of the devices (15% is the newer devices added recently).
In the topology services, I can't see the new devices.
I try to explain more detailed.
Let's assume we have 3 switches (SW1, SW2, SW3), and I just added SW4 and SW5 to LMS.
In the monitoring/inventory, 5 switches are fine.
User tracking works fine for the first 3 switches.
Topology works for the first 3 switches, I can't see the 2 new devices in the All Devices group.
I thought the LMS uses one database for devices, but it seems to be there are two (or more) databases.
How could I check the consistenxy and how could I solve the problem (SW4 and SW5 should be in All Devices Group..)
Thanks in advance, and please let me know if there is a good article about this...

Since cisco has removed the possibility to filter devices from going to an application for LMS, hence all application are in auto allocation, there is nothing you can do to influence the devices to be present in any application.
They should just be in all applications. It should just work (automagically :-)
I don't have any larger network customer anymore, and only 2 small network customers with 28 and 43 devices where all devices, are still in all applications according to the collection summary, but I doubt it will last.
For all others failed + succeeded does not match the number of managed devices and is different for the various collectors. This basically renders the view useless.
TAC solution is to clear the databases but it won't last long.
I hope cisco fixes this before migrating the LMS functionality into NCS.
Cheers,
Michel

Database configuration warning use netca for listener

Hi,
I am using Red Hat 5.4 AS 32 bit and want to install oracle 11gR2 32 bit.
Problem is occurring when installation is going on last
Warning Message is like "listener is not configure use netca"
Thanks in advance

After correction port in listener
[oracle@tsh admin]$ lsnrctl start
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 27-OCT-2012 15:06:01
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Starting /oracle/product/11.2.0/db_1/bin/tnslsnr: please wait...
TNSLSNR for Linux: Version 11.2.0.1.0 - Production
System parameter file is /oracle/product/11.2.0/db_1/network/admin/listener.ora
Log messages written to /oracle/diag/tnslsnr/tsh/listener/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC0)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.170.200.96)(PORT=1538)))
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC0)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 27-OCT-2012 15:06:03
Uptime 0 days 0 hr. 0 min. 0 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /oracle/product/11.2.0/db_1/network/admin/listener.ora
Listener Log File /oracle/diag/tnslsnr/tsh/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC0)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=172.170.200.96)(PORT=1538)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "tsh" has 1 instance(s).
Instance "tsh", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
[oracle@tsh admin]$
Listener.ora
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 172.170.200.96)(PORT = 1538))
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /oracle/product/11.2.0/db_1)
(PROGRAM = extproc)
(SID_DESC =
(ORACLE_HOME = /oracle/product/11.2.0/db_1)
(SID_NAME = tsh)
ADR_BASE_LISTENER = /oracle
tnsanes.ora
TSH =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 172.170.200.96)(PORT = 1538))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = tsh.ag.com)
)

Metadata Incosistency Warning

Hi,
I am getting the following inconsistency warning which is generating a sql error when Answers attempts to run queries:
"[39008] Logical Dimension table <<Logical Table>> has a source <<Physical Table>> that does not join to any fact source"
This warning appeared after I had re-imported the Physical Table to pick up a new field.
In my Phyical Diagram I am connecting my one Phycial Table to 4 tables that are coming from Excel Spreadsheet.
The tables are connected using Foreign Key relationship.
I have deleted the joins and re-joined the the tables but am still recieving the warning above.
Can anybody recommend as to what should be my next step?
Thanks!

Having verified that all three of these conditions are satisfied and still having the 39008 error, I found one more condition that has to be met.
4. The logical level key in the dimension is a key in the logical table.
For example, if your have a logical table
Models
dim_model_key
model
And you have a Dimension with two levels:
All Models
Model Key
Then the field that you use as the logical level key in the dimension must also be declared as key in the logical table.

Database Inconsistency Warning

Similar Messages

Maybe you are looking for