[Info-ingres] "Starting the Recovery Server" hangs, CA Brightstor, ingres, file system full

DATABASE

RE: [Info-ingres] "Starting the Recovery Server" hangs, CA Brightstor, ingres, file system full

Postby martin.bowes » Fri, 08 Apr 2005 18:33:43 GMT

Hi Jono,


	Lets face it, anything would be an improvement for Sven. A 
triple of 9Gs set up as a Raid5 would be a vast improvement.


	That was my thought as well. But I'm also entertaining the 
thought that no backups have been done at all. Plus the possibility that 
the backups may be uncompressed.

	I'd also guess no journaling. 

	Which at least makes the  recovery option after the log is 
rebuilt is simple. You run with what you've got!

	Marty
Random Duckman Quote #69:
Uranus: How about here?                 Duckman: Too hilly.
Fluffy: Or here?                        Duckman: Too flat.
Uranus: Here?                           Duckman: Too republican.
Fluffy: Here?
Duckman: Too...Corny, think of a word.  Cornfed: Salty?
Duckman: Salty...unbelievable, he has one line and...Fine...we're going 
to
         go with 'too salty.'



RE: [Info-ingres] "Starting the Recovery Server" hangs, CA Brightstor, ingres, file system full

Postby martin.bowes » Fri, 08 Apr 2005 21:30:30 GMT

Hi Mike,

	So a Raid 4 would really, really{*filter*}you off!

	Post-It notes? Doesnt that make Postgress?

	Marty







Random Farscape Quote #18:
Aeryn - Its my turn, this is my plan!
John  - Thats your plan! Wile. E. Coyote comes up with better plans 
than that.


Similar Threads:

1.[Info-ingres] "Starting the Recovery Server" hangs, CA Brightstor, ingres, file system full

Hi Sven,
	I have some bad news for you...
	NEVER DELETE THE TRANSACTION LOG FILE!

	What you have deleted is the most vital component of the 
transaction logging system. 

	Do you have a dual log file configured? I suspect the answer is 
no. In which case about all you can do is configure a brand new log file 
and you'll just have to put up with whatever damage to the databases 
has been caused by this problem.

	The only thing you can do from here, is try to prevent the 
original problem happening again. The path for the log file is a tad 
interesting and leads me to suspect that your journals and checkpoints 
may be in similarly interesting locations.

	Could you please do an ingprenv and send the output along 
with a df -k.

	Martin Bowes
Random Duckman Quote #33:
Ajax - If the answers not 'Isoceles Triangle' then I've wasted another
       year of school.

2.[Info-ingres] "Starting the Recovery Server" hangs, CA Brightstor, ingres, file system full - SOLVED

3."Starting the Recovery Server" hangs, CA Brightstor, ingres, file system full

4.[Info-ingres] "Starting the Recovery Server" hangs, CA Bri ghtstor, ingres, file system full

5.[Info-ingres] "Starting the Recovery Server" hangs, CA Bright stor, ingres, file system full

6. [Info-ingres] Fwd: [Info-ingres] E_SC0327 User connections to the Recovery Server are not supported

7. [Info-ingres] RES: [Info-ingres] CA World Ingres Sessions

8. [Info-ingres] Unable to start ingres r3: "Unable to remove shared memory file"



Return to DATABASE

 

Who is online

Users browsing this forum: No registered users and 77 guest