Timesten auto Recovery
an error happened on my timesten, it dosen‘t work ,After about 30 minutes,it Recovered .
why dose this error happened， i Didn’t do anything. who can help me ???
20:28:52.04 Err : : 4839: 6757/6000000000743ff0: Assertion failed: (((np)->flags) & ((sbTnFlag_t) 0x8)) || (((np)->flags) & ((sbTnFlag_t) 0x4)) [ttree.c:4.391:tnInsert:8652] PID 6757 (timestenrepd) CONN 208 (RECEIVER) 2012-08-01 20:28:51.998
20:28:52.14 Err : : 4839: 6757/6000000000743ff0: Data store marked invalid [ttree.c:4.391:tnInsert:8652] PID 6757 (timestenrepd) CONN 208 (RECEIVER) Context 0x6000000000743ff0
20:28:52.29 Err : : 4839: 4842/6000000000f23ff0: Checkpoint failure (db.c, line 19415). Apparent cause is database invalidation by another connection.
20:28:52.29 Warn: : 4839: 4842/6000000000ee5010: Forced Disconnect /ttdata/ocs/data1
20:28:52.30 Err : : 4842: TT14000: TimesTen daemon internal error: subd: flusher thread failed in sb_dbLogFlusherSvc, tt error 994 (TT0994: Data store connection terminated. Please reconnect. -- file "dbAPI.c", lineno 9535, procedure "sb_dbLogFlusherSvc")
20:28:52.30 Err : : 4842: TT14000: TimesTen daemon internal error: subd: flusher thread failed to disconnect, tt error 0 (TT0846: Data store connection invalid or not current -- file "dbAPI.c", lineno 3135, procedure "sb_dbDisconnect()").
20:28:52.30 Warn: : 4839: 4842/6000000000f23ff0: Forced Disconnect /ttdata/ocs/data1
20:28:52.30 Warn: : 4839: 4842 ----------: Disconnecting from an old instance
20:28:52.30 Err : : 4842: subd: scheduled checkpoint failed, error TT0994: Data store connection terminated. Please reconnect. -- file "dbAPI.c", lineno 3478, procedure "sb_dbCkpt()"
20:28:52.33 Warn: : 4842: Stopping subdaemon monitor for /ttdata/ocs/data1 because db is invalid.
20:28:52.38 Warn: : 4839: 4842/6000000001043ff0: Forced Disconnect /ttdata/ocs/data1
20:28:52.38 Warn: : 4839: 4842 ----------: Disconnecting from an old instance
20:28:52.38 Err : : 4842: TT14000: TimesTen daemon internal error: subd: monitor thread failed in sb_dbCgExistWithOraObj, tt error 994
20:28:52.38 Err : : 4842: TT14000: TimesTen daemon internal error: subd: monitor thread failed to disconnect, tt error 846.
20:28:52.40 Err : : 4842: TT14000: TimesTen daemon internal error: subd: checkpoint thread failed to disconnect, tt error 846.
20:28:52.52 Warn: : 4839: 28451 60000000001b60e0: Data store in process of loading, try later
20:28:52.64 Warn: : 4839: 11525/6000000000060650: Forced Disconnect /ttdata/ocs/data1
20:28:52.64 Warn: : 4839: 11525 ----------: Disconnecting from an old instance
20:28:52.90 Warn: : 4839: 4842 ------------------: subdaemon process exited
20:28:52.90 Warn: : 4839: 4842 exited while connected to data store '/ttdata/ocs/data1' shm 371461879 count=3
20:28:52.90 Warn: : 4839: daRecovery: subdaemon 4842, managing data store, failed: invalidate (failcode=202)
20:28:53.09 Warn: : 4839: 11175/6000000000311620: Forced Disconnect /ttdata/ocs/data1
20:28:53.09 Warn: : 4839: 11175 ----------: Disconnecting from an old instance
20:28:53.35 Warn: : 4839: 6757 exited while connected to data store '/ttdata/ocs/data1' shm 371461879 count=7
20:28:53.35 Err : : 4839: TT14000: TimesTen daemon internal error: Could not find the sole user of the data store
20:28:53.35 Err : : 4839: TT14000: TimesTen daemon internal error: Could not find the sole user of the data store
20:28:53.35 Err : : 4839: TT14000: TimesTen daemon internal error: Could not find the sole user of the data store
20:28:53.40 Err : : 4839: TT14000: TimesTen daemon internal error: Could not find the sole user of the data store
20:28:53.40 Err : : 4839: TT14000: TimesTen daemon internal error: Could not find the sole user of the data store
20:28:53.40 Warn: : 4839: Couldn't find data store's user: invalidate
20:28:53.41 Warn: : 4839: 7765/60000000007fe350: Forced Disconnect /ttdata/ocs/data1
20:28:53.41 Warn: : 4839: 7765 ----------: Disconnecting from an old instance
20:28:53.42 Warn: : 4839: 7765/6000000000778f60: Forced Disconnect /ttdata/ocs/data1
20:28:53.42 Warn: : 4839: 7765 ----------: Disconnecting from an old instance
20:28:53.42 Warn: : 4839: 7765/60000000005f59c0: Forced Disconnect /ttdata/ocs/data1
20:28:53.42 Warn: : 4839: 7765 ----------: Disconnecting from an old instance
20:28:53.51 Warn: : 4839: 12205/6000000000060650: Forced Disconnect /ttdata/ocs/data1
20:28:58.34 Warn: : 4839: 11709 ----------: Disconnecting from an old instance
20:28:58.48 Warn: : 4839: 11668/6000000000060650: Forced Disconnect /ttdata/ocs/data1
20:28:58.48 Warn: : 4839: 11668 ----------: Disconnecting from an old instance
20:28:58.95 Warn: : 4839: 7765/600000000064cd90: Forced Disconnect /ttdata/ocs/data1
20:28:58.95 Warn: : 4839: 7765 ----------: Disconnecting from an old instance
20:28:58.95 Warn: : 4839: 7765/6000000000182900: Forced Disconnect /ttdata/ocs/data1
20:28:58.95 Warn: : 4839: 7765 ----------: Disconnecting from an old instance
20:28:58.95 Warn: ORA: 7765: ora-7765-0001-xxagent04639: Warning: Statement SQLDisconnect(agentHdbc)
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01017: Error: [TimesTen]TT0994: Data store connection terminated. Please reconnect. -- file "dbAPI.c", lineno 3132, procedure "sb_dbDisconnect()", ODBC SQL state = S1000, Additional Warning = 994
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01042: Detected invalid data store.
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01017: Error: [TimesTen]TT0994: Data store connection terminated. Please reconnect. -- file "db.c", lineno 14954, procedure "sbDbAppExit()", ODBC SQL state = S1000, Additional Warning = 994
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01042: Detected invalid data store.
20:28:58.95 Warn: : 4839: 7765/60000000003083a0: Forced Disconnect /ttdata/ocs/data1
20:28:58.95 Warn: : 4839: 7765 ----------: Disconnecting from an old instance
20:28:58.95 Warn: ORA: 7765: ora-7765-0001-xxagent04645: Warning: Statement SQLDisconnect(timerHdbc)
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01017: Error: [TimesTen]TT0994: Data store connection terminated. Please reconnect. -- file "dbAPI.c", lineno 3132, procedure "sb_dbDisconnect()", ODBC SQL state = S1000, Additional Warning = 994
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01042: Detected invalid data store.
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01017: Error: [TimesTen]TT0994: Data store connection terminated. Please reconnect. -- file "db.c", lineno 14954, procedure "sbDbAppExit()", ODBC SQL state = S1000, Additional Warning = 994
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01042: Detected invalid data store.
20:28:58.95 Warn: : 4839: 7765/60000000004083a0: Forced Disconnect /ttdata/ocs/data1
20:28:58.95 Warn: : 4839: 7765 ----------: Disconnecting from an old instance
20:28:58.95 Warn: ORA: 7765: ora-7765-0001-xxagent04652: Warning: Statement SQLDisconnect(agingHdbc)
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01017: Error: [TimesTen]TT0994: Data store connection terminated. Please reconnect. -- file "dbAPI.c", lineno 3132, procedure "sb_dbDisconnect()", ODBC SQL state = S1000, Additional Warning = 994
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01042: Detected invalid data store.
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01017: Error: [TimesTen]TT0994: Data store connection terminated. Please reconnect. -- file "db.c", lineno 14954, procedure "sbDbAppExit()", ODBC SQL state = S1000, Additional Warning = 994
20:28:58.95 Err : ORA: 7765: ora-7765-0001-bcStuff01042: Detected invalid data store.
20:28:59.00 Warn: : 4839: 11174/6000000000060650: Forced Disconnect /ttdata/ocs/data1
20:28:59.00 Warn: : 4839: 11174 ----------: Disconnecting from an old instance
20:28:59.38 Warn: : 4839: 11685/6000000000311620: Forced Disconnect /ttdata/ocs/data1
20:28:59.38 Warn: : 4839: 11685 ----------: Disconnecting from an old instance
20:28:59.84 Warn: : 4839: 11661/6000000000311620: Forced Disconnect /ttdata/ocs/data1
20:28:59.84 Warn: : 4839: 11661 ----------: Disconnecting from an old instance
20:28:59.89 Warn: : 4839: 9707/6000000000311620: Forced Disconnect /ttdata/ocs/data1
20:28:59.89 Warn: : 4839: 9707 ----------: Disconnecting from an old instance
20:29:00.15 Warn: : 4839: 11167/6000000000311620: Forced Disconnect /ttdata/ocs/data1
20:29:00.15 Warn: : 4839: 11167 ----------: Disconnecting from an old instance
20:29:00.15 Warn: : 4839: 11724/6000000000060650: Forced Disconnect /ttdata/ocs/data1
20:29:00.15 Warn: : 4839: 11724 ----------: Disconnecting from an old instance
20:29:00.92 Warn: : 4839: 11700/6000000000060650: Forced Disconnect /ttdata/ocs/data1
20:29:00.92 Warn: : 4839: 11700 ----------: Disconnecting from an old instance
20:29:00.92 Warn: : 4839: 12217/6000000000311620: Forced Disconnect /ttdata/ocs/data1
20:29:00.92 Warn: : 4839: 12217 ----------: Disconnecting from an old instance
20:29:01.03 Warn: : 4839: 11717/6000000000311620: Forced Disconnect /ttdata/ocs/data1
20:29:01.03 Warn: : 4839: 11717 ----------: Disconnecting from an old instance
20:29:01.37 Warn: : 4839: 11676/6000000000060650: Forced Disconnect /ttdata/ocs/data1
20:29:01.37 Warn: : 4839: 11676 ----------: Disconnecting from an old instance
20:29:01.49 Warn: : 4839: 11175 exited while connected to data store '/ttdata/ocs/data1' shm 371461879 count=11
20:29:01.95 Warn: : 4839: 11693/6000000000311620: Forced Disconnect /ttdata/ocs/data1
20:29:01.95 Warn: : 4839: 11693 ----------: Disconnecting from an old instance
20:29:02.30 Warn: : 4839: 11669/6000000000311620: Forced Disconnect /ttdata/ocs/data1
20:29:02.30 Warn: : 4839: 11669 ----------: Disconnecting from an old instance
20:29:03.39 Warn: : 4839: 11725 exited while connected to data store '/ttdata/ocs/data1' shm 371461879 count=11
20:29:03.97 Warn: : 4839: 11677 exited while connected to data store '/ttdata/ocs/data1' shm 371461879 count=11
20:29:28.27 Warn: : 4839: 11527 exited while connected to data store '/ttdata/ocs/data1' shm 371461879 count=11
20:29:31.86 Warn: : 4839: 11661 exited while connected to data store '/ttdata/ocs/data1' shm 371461879 count=11
20:29:32.22 Warn: : 4839: 9707 exited while connected to data store '/ttdata/ocs/data1' shm 371461879 count=11
20:36:53.19 Warn: : 4839: 4843/60000000000c0020: Recovery started
21:08:35.34 Warn: : 4843: subd: Warning identified in [sub.c: line 3188]
21:08:35.34 Warn: : 4843: subd: (Warning 20100): TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 11566, procedure "sbDbConnect"
21:08:35.34 Warn: : 4843: file "db.c", lineno 11566, procedure "sbDbConnect"
21:08:35.35 Warn: : 4843: subd: connect trouble, rc 2, reason 20100
21:08:35.35 Warn: : 4843: Warn 20100: TT20100: This connection required recovery due to an improper shutdown -- file "db.c", lineno 11566, procedure "sbDbConnect"
21:08:39.54 Err : ORA: 28458: ora-28458-0009-raStuff09836: Unexpected row count. Expecting 1. Got 0.
21:55:13.91 Warn: ORA: 28458: ora-28458-0014-refresh10886: Autorefresh was not able to acquire lock on one of the cache groups, may be because a DDL transaction is open on the cache group. Autorefresh will be retried again
21:55:43.90 Warn: ORA: 28458: ora-28458-0014-refresh10886: Autorefresh was not able to acquire lock on one of the cache groups, may be because a DDL transaction is open on the cache group. Autorefresh will be retried again
21:56:16.35 Warn: ORA: 28458: ora-28458-0015-refresh10886: Autorefresh was not able to acquire lock on one of the cache groups, may be because a DDL transaction is open on the cache group. Autorefresh will be retried again
21:56:19.54 Warn: ORA: 28458: ora-28458-0015-refresh10886: Autorefresh was not able to acquire lock on one of the cache groups, may be because a DDL transaction is open on the cache group. Autorefresh will be retried again
21:56:22.76 Warn: ORA: 28458: ora-28458-0015-refresh10886: Autorefresh was not able to acquire lock on one of the cache groups, may be because a DDL transaction is open on the cache group. Autorefresh will be retried again
21:57:13.87 Warn: ORA: 28458: ora-28458-0014-refresh10886: Autorefresh was not able to acquire lock on one of the cache groups, may be because a DDL transaction is open on the cache group. Autorefresh will be retried again
Because the receiver thread in the replication agent hit an Assertion Failure and the datastore was invalidated ie taken out of memory and then - presumably - recovered and automatically reloaded. While this was going on existing connections would have been disconnected and new ones prevented from being made.
You need to log an SR so we can try to establish what caused the Assertion Failure, whether it's a known bug that's fixed in a later release, or a new one.
Similar Messages
-
How do I disable auto-recovery files from opening every time I open Photoshop?
Hi! I have read several forums about how to disable the auto-recovery feature. However, I don't want to disable the auto-recovery because I like that it saves my work in case of crash. It's just annoying that everytime I open photoshop all those previous files auto open. Is there anyway to make it stop? I read that there is a file that you delete, but will that stop the auto-recovery feature? Thanks in advance for your help!
Oh! It's Photoshop CS 6 and the os is Mountain Lion. Thanks!On Windows, if Photoshop crashes, the autorecovery files are not cleared. On next launch, Photoshop sees those autorecovery files and reopens them.
When Photoshop closes successfully, it deletes these autorecovery files, and thus on the next launch no recovery files should be opened.
So if your files are continually opening, then Photoshop is in essence crashing every time you close it (assuming you are trying to close Photoshop each time).
May need to look at doing things like recreating the preference files or running Photoshop in a new user. -
Where are the auto recovery files stored for Visio 2010?
I have auto recovery set for every 5 minutes. I have been working on a file that has been saved several times a day. Today when just moving a shape Viso 2010 crashed after I had been working on the file for over 2 hours. Auto recovery popped
up every 5 minutes indicating it was saving the file. After the crash the ony file I could find was the file as it was when I first opened it this AM. None of the work done today was saved.
Did auto recovery completely fail? Where can I look for the auto recovery file?
I have not done a reboot because I am afraid that if the file exits it will be gone for sure if I reboot. Any suggestions are welcome.
There must be a temp file or something that I can look for but not sure what the extension would be or the location.
Hopefully someone here can help.
thanks,
greg
Greg J WilsonHow do I know? You state the the auto-save file extension is .vxd - that's the Visio document XML format.
You can change this in File -> Options -> Save
As for the crashes, are there any messages when a crash occurs?
Check that the video drivers you have are the latest, try a different screen resolution to see if that changes anything and turn off or change any screen accelerators.
-- Paul Herber, Sandrila Ltd. http://www.sandrila.co.uk/ Engineering and software shapes for Visio.
My mistake - the file format is .vsd - standard visio format
Here is the info from the event viewer for the specific crash that caused me temporary pain.
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider
Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated
SystemTime="2011-07-25T17:15:25.000000000Z" />
<EventRecordID>83552</EventRecordID>
<Channel>Application</Channel>
<Computer>gw-Tosh_laptop</Computer>
<Security
/>
</System>
<EventData>
<Data>VISIO.EXE</Data>
<Data>14.0.6022.1000</Data>
<Data>4d6eacd6</Data>
<Data>unknown</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>c0000005</Data>
<Data>8469f91f</Data>
<Data>1668</Data>
<Data>01cc4ae02611b81c</Data>
<Data>C:\Program
Files\Microsoft Office\Office14\VISIO.EXE</Data>
<Data>unknown</Data>
<Data>af70a4ff-b6e1-11e0-82fc-001e33913568</Data>
</EventData>
</Event>
Greg J Wilson -
How to use auto recovery from word 2011?
Hi
Yesterday I spent the whole day writing up a report for work to the point where I fell asleep last night with the document still opened. This morning I had a little more to do on it and when I tried to press save (like a did all day yesterday) it wouldn't save. I ended up just closing it down without saving because there was no point going on if it wasn't going to save any of my new stuff. So when I tried to open the file again it has reverted back to the document I started and saved over a week ago - MINUS ALL OF MY WORK FROM YESTERDAY!! I've tried finding it in my auto-recovery file but it is empty. What do I do?
These are possible issues that I think may stop me from finding the problem:
1. The document is saved on my USB
2. Microsoft Office wanted to update and I clicked not now as I was in the middle of this report.
Could these things affect my outcome?
PLEASE HELP!!!!Could you please elaborate?
Is there a file in the Folder "PSAutoRecover" on your scratch disk? -
Auto recovery;
What are the steps to auto recovery in case of the database is a standalone.
can we write the script to do it automatically.
if so links pls
Thanks!936666 wrote:
Auto recovery;
What are the steps to auto recovery in case of the database is a standalone.
can we write the script to do it automatically.
if so links pls
Thanks!
The details of every recovery is dependent on the nature and extent of the failure. This requires analysis by the DBA. That's what we get paid the big bucks for. -
Can Auto Recovery be disabled in InDesign CC for PC?
I have InDesign running on a server and its sole purpose to is create previews of ID documents for my Digital Asset Management system. The auto recovery halts previews from being made through the DAM and really slows down my system. Isn't there a way I could disable document recovery entirely, since it's not actually helping me in this case?
I can assure you that it's a legal, licensed copy of the CC! My DAM just picks up activity from our production server and creates thumbnail previews of our ID documents.
Thanks for your input! -
How to fix auto recovery crush? Im in deadline. it was my whole day work, pls help..
how to fix auto recovery crush? Im in deadline. it was my whole day work, pls help..
Close ID, find the HIDDEN InDesign Recovery folder (It will be next to InDesign SavedData, and you can find the path to that for your OS at Replace Your Preferences ), and empty it, then restart ID normally, not by double-clicking a file.
If your file was not damaged during the crash, it should open from the File menu at the last saved state. You will lose anything you did to the file since the last save. -
I don't have any need at all for the auto-recovery feature, really. All it does is cause a delay for me (when the server goes down). I've never used it, never needed it, ever, and I wouldn't trust it to present me with every change I made anyway. I'd rather start over. Please give me a way to turn it off.
vernehenzel wrote:
I don't have any need at all for the auto-recovery feature, really. All it does is cause a delay for me (when the server goes down). I've never used it, never needed it, ever, and I wouldn't trust it to present me with every change I made anyway. I'd rather start over. Please give me a way to turn it off.
I believe that you can set InDesign to run scripts at startup and quitting time. As noted in this article, http://indesignsecrets.com/rebuilding-indesign-preferences.php, the saved data file can be deleted and automatically recreated on startup.
For help on creating the script you'd need and how to implement it, try the InDesign scripting forum.
HTH
Regards,
Peter
Peter Gold
KnowHow ProServices -
Hi, all
I understood vPC auto-recovery feature as the following but are they correct?
vPC auto-recovery becomes effective command only when vPC role is secondary.
In order to change to secondary state, a pair of vPC devices need synchronize.
Even if one of a pair vPC devices fails boot after a power cut, vPC auto-recovery does not work. The vPC role is "none established" because the vPC device does not synchronize with peer vPC device.
Thank you for your cooperation in advance.Hi Satoru,
This document explains pretty well how auto-recovery works.
http://www.cisco.com/c/dam/en/us/td/docs/switches/datacenter/sw/design/vpc_design/vpc_best_practices_design_guide.pdf -
Auto recovery in Excel failing
Hi guys.
My finance team uses many s'sheets encompassing pivot tables, macros, charts etc. Many of these are in the region of 70Mb in size.
The auto recovery process on one of my guy's laptop seems to fail causing the program to freeze and recovery is not possible. Is 70Mb to large? the physical memory and the processor are not being hammered when he launches task manager, the virtual
memory is set as recommended, am I missing something?
Can anyone shed some light on this please?
Many thanks, KR, NickFrom where the transaction is initiated, from BPEL or some other source system.
I would always suggest to keep the transactional control into the end points. Your source should catch the BPEL faults and make a call to middleware again in case if data is critical. OR you can store the faults in some DB or delimited files and you might have some bpel process which will pick up the faulted data from the table or file and retrying the target endpoint until success. -
Auto recovery and why is it happening?????
As I am working in excel or word, could be other programs, I notice a quick flash at the bottom of the excel sheet say " auto recovery". It seems to save what I am working on because you can't "undo" what you were working on once it flashes " auto recovery". This is a work computer, so I don't know if the company has a remote connect that they are able to save or copy what I am working on. It is frustrating since I can't "undo" things.
Maybe someone knows what I am talking about.Welcome to Apple Discussions.
I'd recommend posting in the MS Office forum.
http://www.microsoft.com/uk/mac/help.mspx
Regards,
Roger -
Hi together
I saved by mistake an Excel-File in the folder Auto recovery, I can see the folder when I open new sheet and click save as. I looked already in the folder Microsoft office/office 2011, there is none folder auto recovery. Where is this folder? Is there a chance to find and open the Excel-File?
Thank you very much for your support.
MarceioThis would be best asked on Microsoft's Office forums, don't you think?
That being said, it is found in the Microsoft section of your library's Applications Support folder.
Yours, NOT the system's, mind you. -
I hope the is a differnence between auto-save (as listed in you document properties) and Auto-Recovery (as set in Prefs). I would like some "protection" but I don't want flash saving over my file unless I tell it to save. I got burn last night while "experimenting" and and did a "revert" only to find that flash had saved over my file, what a pain. I went to find the "recovery" file only to not find one anywhere. My search on the net are conflicted with wheather or not these 2 features are the same. In my case both items where checked and both set to 10min (the default). soooo....
Please tell me that Auto-Recovery is different, is that it doesn't save over my file, ie it keeps a real back-up someplace, AND where i can find this "recovery" file. ?
This feature seems strange, why not do a std auto back-up to a user selected number of versions in a user selected location ?
Thanks
JoelThanks. After poking around for a while I kinda figured this out. I was just glad to find out I could get some kind of "back-up" function from Auto Recovery, because "Auto Save" is a nightmare. I can't understand where anyone would want to use this feature at all. Anything that saves over what your working on before your ask for the file to be saved is looking for trouble. I found it out the hard way. I had "auto Save" on and after messing around trying a few different things, none of which worked or I liked, I thought I would simply close and re-open the original file only to find "auto save" had saved over my original file. I can't see any place where this feature would be anything but a pitb. If they want a auto save feature it should be saving versions of the original (up to a user specified number of instances) in the seperate folder. Never under any curcumstances should the original file be saved over unless the users presses SAVE. Auto recovery would be more useful if it didn't erase everytime you restarted the app. Flash needs to look at the back-up and versioning systems that AE and PPro use.
It's one of those things that bother you about the whole "suite" concept. Adobe owns all these apps and while some of them do play well together to an extent, for the most part it is still a collection of indiviuals. While there have been some changes to get the "look" of the apps to be close, the actual functioning of the UI in the differnt apps isn't where it needs to be. There needs to be a Suite "czar" that makes all the apps do std UI things the same using the same keys etc. for example AE, PPro, Flash, Photoshop, fireworks, all use different keys to zoom in/out or of your image/stage/comp/viewer/monitor window ie main workspace or to enable the mouse "wheel" for zooming. PPro still refuses to use the spacebar to toggle the hand tool like every other "suite app". anyway. a std system for back-up and versioning is need across the suite.
thanks
Joel -
Multi-threaded, 64-bit, Auto-Recovery/Auto-Save
Illustrator needs more horsepower. Make it 64-bit and able to use more of the cores that more and more users have these days.
Illustrator now runs much better than some of the older versions, but abrupt crashing sadly still happens. At some of the worst times.
Can we please have an Auto-Recovery (like InDesign... ) or Auto-Save option in the Preferences?
Sometimes 'doing it over again' is just not acceptable.Hi,
I suggest you to increase the value kernel.shmmax = 8589934592 of this parameter in sysctl.conf to kernel.shmmax = 1288490188
Later if you want to increase the size of SGA then you need to modify the kernel.shmmax = 8589934592 value. In general practice we keep kernel.shmmax value little greater then the value of SGA.
Refer MOS tech note:
*ORA-27102 Database Will Not Start With SHMMAX Set To 8589934592 (8GB) [ID 461519.1]*
*Linux Big SGA, Large Memory, VLM - White Paper [ID 260152.1]*
thanks,
X A H E E R
Edited by: ora_tech on Dec 26, 2010 10:14 AM -
CS6 opens with Auto Recovery files every launch.
I know where the recovery files are. Finding and deleting them isn't the issue.
My understanding of Auto Recover is that when a working file is saved and closed, the corresponding Auto Recover psb should be trashed automatically.
Every evening I save and close all my work, quit Photoshop and shut down the Mac. Every morning when I start Photoshop, at least one Auto Recovery file opens. It's the last file(s) I was working on the previous evening.
I've toggled Auto Recover on/off, trashed the folder and had CS6 recreate it. Nothing works. Every morning, I am presented with a psb of the previous evening's work.
My scratch disk is a dedicated 100gb SSD. I have triple verified that CS6 is not writing recovery files to a different location.
Any ideas?
Thanks,
RobIs there any problem at/after quitting Photoshop?
Boilerplate-text:
Are Photoshop and OS fully updated and have you performed the usual trouble-shooting routines (trashing prefs by pressing command-alt-shift/ctrl-alt-shift while starting Photoshop until the appropriate dialog appears after making sure all customized presets like Actions, Patterns, Brushes etc. have been saved and making a note of the Preferences you’ve changed, 3rd party plug-ins deactivation, system maintenance, cleaning caches, font validation, etc.)
Maybe you are looking for
-
Switching from OsX to Windows on macbook pro w Retina
I already had windows installed on my mac, but now I can't access it and bootcamp is prompting me install windows... its already installed. Please help me.
-
I rebooted my macbook pro recently and downloaded mountain lion. Afterwards iPhoto dissapeared and I canr seem to restore it. Any suggestions?
-
Kernel_task is using a lot of memory
I am curious if it is normal to have Kernel_task take 1.8 GB of memory? It seems to be the consistent reason as to why our server is running slow? Thanks for any help....
-
I've signed in and out several times
-
Getting error as RGSUM could not be updated.In j1iex when we change material type from raw to consumable.in j1id they have maintained mat type as consumable which was raw earlier at the time of po creation.