Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[cem_devecioglu]

"00:00000:00001:2011/08/22 11:22:51.69 server  Database 'master' is now online."

this means that sybase start up properly with master database (which is critical for itself)


still checking the logs....

[tunnie]

"00:00000:00001:2011/08/22 11:22:51.69 server  Database 'master' is now online."

this means that sybase start up properly with master database (which is critical for itself)


still checking the logs....

Thanks Cem 

[cem_devecioglu]

cant see initalization of disks DATA_10 and DATA_11 :-/

seems like they partitioned data to multiple disks which means trouble :-/

[cem_devecioglu]

00:00000:00011:2011/08/22 11:22:52.83 server  Database 'replicator_test' cannot be opened. An earlier attempt at recovery marked it 'suspect'. Check the SQL Server errorlog for information as to the cause.

yep.. you cant touch a suspect database directly from DB tools.. it must be stopped first of all..

and also sql server does the same when it cant reach files physically :-/


also

server  Started UNDO pass for database 'billing'. The total number of log records to process is 6756.
00:00000:00011:2011/08/22 11:22:53.22 server  Undo pass for database 'billing': 6000 records done (88%); 756 records left.00:00000:00011:2011/08/22 11:22:53.22 server  Undo pass of recovery has processed 1 incomplete transactions.

this must have happened when its shut down..

[tunnie]

00:00000:00011:2011/08/22 11:22:52.83 server  Database 'replicator_test' cannot be opened. An earlier attempt at recovery marked it 'suspect'. Check the SQL Server errorlog for information as to the cause.

yep.. you cant touch a suspect database directly from DB tools.. it must be stopped first of all..

and also sql server does the same when it cant reach files physically :-/


also

server  Started UNDO pass for database 'billing'. The total number of log records to process is 6756.
00:00000:00011:2011/08/22 11:22:53.22 server  Undo pass for database 'billing': 6000 records done (88%); 756 records left.00:00000:00011:2011/08/22 11:22:53.22 server  Undo pass of recovery has processed 1 incomplete transactions.

this must have happened when its shut down..

Thanks Cem, yet another pointer to HD, not a problem if they had kept it RAID. 

[cem_devecioglu]

yep.. now reached the end of log..

according to logs Sybase working properly most of its databases brought online..

2 databases effected from problem

'replicator_test'  is suspect which you cant reach and see the files also..

another one is the 'billing database'

Started REDO pass for database 'billing'.

The total number of log records to process is 13705

server  Started UNDO pass for database 'billing'. The total number of log records to process is 6756.
00:00000:00011:2011/08/22 11:22:53.22 server  Undo pass for database 'billing': 6000 records done (88%); 756 records left.
00:00000:00011:2011/08/22 11:22:53.22 server  Undo pass of recovery has processed 1 incomplete transactions.

which means half of the records are written and committed and nearly half of the transactions are rolled back.. (so its not same as its last stage)

probably when op.system trying to recover disk/file system problems it erased some files of the replicator_test..

this is all I can say.. :-/

[tunnie]

Thanks Cem, much appreciated     

[cem_devecioglu]

Thanks Cem, much appreciated     

no probs.. I'd be happy if it helps a bit

[TheBoy]

Initial reaction, based on my MSSQL and MySQL limited knowledge, is possibly the underlying filesystem.  If the DB removes files itself, I'd like to think it was clever enough not to try to load them.  Not looked at the logs though.

Cem knows far more about RDBMS than I ever will, and he has cast his eyes over it.


I'm guessing if you had bought the licence, rather than run an illegal copy, you might have had some support from Sybase. Also guessing you don't have an active Redhat licence to cover the OS either

[cem_devecioglu]

Initial reaction, based on my MSSQL and MySQL limited knowledge, is possibly the underlying filesystem.  If the DB removes files itself, I'd like to think it was clever enough not to try to load them.  Not looked at the logs though.
Cem knows far more about RDBMS than I ever will, and he has cast his eyes over it.


I'm guessing if you had bought the licence, rather than run an illegal copy, you might have had some support from Sybase. Also guessing you don't have an active Redhat licence to cover the OS either

agreed..

and thanks 

[tunnie]

Initial reaction, based on my MSSQL and MySQL limited knowledge, is possibly the underlying filesystem.  If the DB removes files itself, I'd like to think it was clever enough not to try to load them.  Not looked at the logs though.

Cem knows far more about RDBMS than I ever will, and he has cast his eyes over it.


I'm guessing if you had bought the licence, rather than run an illegal copy, you might have had some support from Sybase. Also guessing you don't have an active Redhat licence to cover the OS either

Its no illegal, its legit, its just certain features are not available without the license, they lost various tools, one was the customer service tool. That was not deemed important enough!

Thanks everyone for their input 

We keep coming back to same conclusion of file system / hardware, I'm looking at that now   

[tunnie]

Also RedHat is all legal too its all above board 

[cem_devecioglu]

Initial reaction, based on my MSSQL and MySQL limited knowledge, is possibly the underlying filesystem.  If the DB removes files itself, I'd like to think it was clever enough not to try to load them.  Not looked at the logs though.

Cem knows far more about RDBMS than I ever will, and he has cast his eyes over it.


I'm guessing if you had bought the licence, rather than run an illegal copy, you might have had some support from Sybase. Also guessing you don't have an active Redhat licence to cover the OS either

Its no illegal, its legit, its just certain features are not available without the license, they lost various tools, one was the customer service tool. That was not deemed important enough!

Thanks everyone for their input 

We keep coming back to same conclusion of file system / hardware, I'm looking at that now   

Tunnie,

if you ask my opinion, although depending on the application,

it may be better for you to choose autocommit=yes=on whatever from DBMS configuration.. so in case of problems your losses will be very minimal..

good luck

[tunnie]

cheers Cem 

[TheBoy]

Also RedHat is all legal too its all above board 

Hokey dokey, in which case you have a support contract with them, so you can use them to assist with tracking down if its a hardware faiilure