Could this Be Database Corruption?
404nicg
Posts: 270
So I recently discovered the wonders of categorizing. I started putting a few items in categories. I was able to categorize about 10 clothing pieces and then it just stopped working. I went to go to the next item and followed the same categorization steps, and when I went to go check on it it wasn't in the spot that it had been categorized to. I tried a few different items and had the same issue. Tried restarting Daz but that did not help.
Also I bought a few items this morning and one of them is not showing up in my content library. Could these be two symptoms of database corruption? How can I fix it..I'm on a Mac. Thanks for your time.
Comments
Yes, that sounds like database corruption. Are you able to use PostgreSQL CMS?
1) If you haven't exported user data recently, do that first, so you can restore the categories that are still working.
2) Close DS.
3) Install PostgreSQL CMS. Don't bother with the "Convert Valentina DB to PostgreSQL".
4) Re-Import Metadata.
Thanks for your response.Bear with me.. how would I check the PostgreSqL CMS (not 100% sure what that is). Most of my content shows up in my content library as far as I can tell, but that one item doesn't. There may be other things missing but I haven't encountered any others so far. I never bother with Smart Content at all...I always load items from the content library.
And I don't even know how to export user data
Categories and Products in the Content Library, as well as searches, are also driven by CMS.
The original CMS in DS4.0 was driven by the Valentina DB server. A lot of people have had problems with database corruption, so PostgreSQL was introduced last year as a more stable alternative. Unless you use Carrara 8.5or ZoneAlarm it's a better alternative. You can download PostgreSQL CMS from your Product Library or install it with DIM. DIM will also have something to convert the Valentina DB to PostgreSQL, but since the Valentina DB is corrupt it probably won't work.
From the Content Library options menu (rectangle with horizontal lines in the upper corner of the Content Library pane) under "Content DB Maintenance" are "Export User Data" and "Re-Import Metadata". Export User Data creates a file in the Runtime:Support folder with any custom categories, tags, or metadata you've created, similar to the files that come with products. It can take a while to run if you have a lot, especially using Valentina. Re-Import Metadata will read the files in Runtime:Support and add that info to the database, it will let you choose whether to import User data as well. Re-Import with PostgreSQL is faster than with Valentina, but it can still take a while if you have a lot.
Gotcha! Okay followed your steps and the Categorization is back working. Thanks alot. That one item is still not showing up though, would I maybe delete it and then reinstall that content?
Also upon installing PostgreSQL is Valentina DB automatically removed? If not how do I uninstall it? It's my understanding that Valentina runs in the background of your computer even when DAZ isn't running. It seems that since my database has been acting up my laptop fans have been running non-stop so I want to be sure the two issues aren't connected before I take it in to have it checked out.
Under Windows, there's an uninstaller for Valentina in Start menu > DAZ 3D > DAZ Content Management Service
Which is the item that isn't showing up?
Ahh installing PostgreSQL CMS definitely got my fans quiet for the first time today. So yeah Valentina must have been going haywire beneath the surface as well.
The item is A Cozy Studio by Bluebird 3d.
http://www.daz3d.com/a-cozy-studio
It's in Poser format under props but when I get to it the folder reads as empty in the content library
The DS version should be in DAZ Studio Formats > [content library name] > Props > Bluebird 3D > A Cozy Studio
Oh wow I could've sworn I downloaded the DS version. Got it all straightened out. Thanks alot Mike you're a lifesaver. One last question...so I was reading that installing content while you have DAZ running is one of the main contributors to database corruption, which I'm definitely guilty of. Is this still true for PostgreSQL CMS or has that been resolved so it's no longer an issue?
PostgreSQL CMS is much less prone to corruption, but I still close DS while installing, just in case.
Thanks again for your help!