Click here to Skip to main content
15,498,796 members
Home / Discussions / Database
   

Database

 
QuestionSybase Access Violaion Error Pin
Ankit RS6-May-15 22:32
MemberAnkit RS6-May-15 22:32 
SuggestionRe: Sybase Access Violaion Error Pin
ZurdoDev7-May-15 5:08
professionalZurdoDev7-May-15 5:08 
GeneralRe: Sybase Access Violaion Error Pin
Sascha Lefèvre7-May-15 7:25
professionalSascha Lefèvre7-May-15 7:25 
QuestionRe: Sybase Access Violaion Error Pin
Ankit RS8-May-15 1:36
MemberAnkit RS8-May-15 1:36 
AnswerRe: Sybase Access Violaion Error Pin
Sascha Lefèvre8-May-15 11:02
professionalSascha Lefèvre8-May-15 11:02 
QuestionUnion on a join Pin
jkirkerx6-May-15 10:20
professionaljkirkerx6-May-15 10:20 
AnswerRe: Union on a join Pin
Richard Deeming6-May-15 10:40
mveRichard Deeming6-May-15 10:40 
GeneralRe: Union on a join Pin
jkirkerx6-May-15 12:40
professionaljkirkerx6-May-15 12:40 
GeneralRe: Union on a join Pin
jkirkerx7-May-15 13:24
professionaljkirkerx7-May-15 13:24 
Questionpostgresql VACUUM Pin
V.6-May-15 0:55
professionalV.6-May-15 0:55 
So I managed to run into the error:
"ERROR: database is not accepting commands to avoid wraparound data loss in database "mydb" HINT: Stop the postmaster and use a standalone backend to vacuum that database. You might also need to commit or roll back old prepared transactions."

I followed google into the solution of restarting the database in standalone mode (like here[^]), but when I run:
SQL
VACUUM FULL mytable;
it gives me the message:
backend> VACUUM FULL mytable;
2015-05-06 09:45:09 UTC WARNING:  database "mydb" must be vacuumed within 999976 transactions
2015-05-06 09:45:09 UTC HINT:  To avoid a database shutdown, execute a database-wide VACUUM in that database.
        You might also need to commit or roll back old prepared transactions.
2015-05-06 09:47:53 UTC WARNING:  database "mydb" must be vacuumed within 999975 transactions
2015-05-06 09:47:53 UTC HINT:  To avoid a database shutdown, execute a database-wide VACUUM in that database.
        You might also need to commit or roll back old prepared transactions.
2015-05-06 09:47:53 UTC WARNING:  database "mydb" must be vacuumed within 999974 transactions
2015-05-06 09:47:53 UTC HINT:  To avoid a database shutdown, execute a database-wide VACUUM in that database.
        You might also need to commit or roll back old prepared transactions.
backend>
I have no idea what I can do with this.. Just continue the VACUUM for all tables?

thanks.
V.

(MQOTD rules and previous solutions)

JokeRe: postgresql VACUUM Pin
Tim Carmichael6-May-15 5:52
MemberTim Carmichael6-May-15 5:52 
GeneralRe: postgresql VACUUM Pin
Mycroft Holmes6-May-15 15:06
professionalMycroft Holmes6-May-15 15:06 
GeneralRe: postgresql VACUUM Pin
Tim Carmichael6-May-15 15:49
MemberTim Carmichael6-May-15 15:49 
GeneralRe: postgresql VACUUM Pin
V.6-May-15 21:41
professionalV.6-May-15 21:41 
GeneralRe: postgresql VACUUM Pin
Mycroft Holmes6-May-15 23:04
professionalMycroft Holmes6-May-15 23:04 
GeneralRe: postgresql VACUUM Pin
V.6-May-15 23:06
professionalV.6-May-15 23:06 
GeneralRe: postgresql VACUUM Pin
Mycroft Holmes6-May-15 23:16
professionalMycroft Holmes6-May-15 23:16 
GeneralRe: postgresql VACUUM Pin
Tim Carmichael7-May-15 1:01
MemberTim Carmichael7-May-15 1:01 
AnswerRe: postgresql VACUUM Pin
Tim Carmichael7-May-15 3:15
MemberTim Carmichael7-May-15 3:15 
GeneralRe: postgresql VACUUM Pin
V.7-May-15 4:41
professionalV.7-May-15 4:41 
QuestionSequence number in DB2 Pin
sudevsu5-May-15 10:57
Membersudevsu5-May-15 10:57 
QuestionTest sol Pin
Stephen Holdorf30-Apr-15 12:24
MemberStephen Holdorf30-Apr-15 12:24 
GeneralRe: Help with a SQL query Pin
PIEBALDconsult30-Apr-15 20:33
professionalPIEBALDconsult30-Apr-15 20:33 
GeneralRe: Help with a SQL query Pin
Stephen Holdorf1-May-15 3:54
MemberStephen Holdorf1-May-15 3:54 
GeneralRe: Help with a SQL query Pin
Stephen Holdorf20-May-15 4:27
MemberStephen Holdorf20-May-15 4:27 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.