Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Installing Standby Database

Hello,

after switching from Oracle to Sybase two years ago (customer wish) I had to set up some standby databases, that works and the these standby dbs running fine, until a few days ago. One standby stops working during applying some transaction logs. Normally I would load the latest backup of the <SID> db and start applying again from that point, but the database service (Win2k8 R2 SP1) stops working. The service stays in starting mode, the log file doesn't log an error!

I didn't found a way to get the service running again, so I decided to reinstall the whole standby system.

Newest SWPM, uninstall > install (what's new, SWPM added new sybase users even they exists in AD (productiv side) (I had to change the user on the PRD system, because the internal windows id was changed)

So, Sybase service is running fine again and the SAP system was up.

Next step was, to reload the master db with the newest backup, start single user modus and loaded master db successfully.

After that, I started Sybase via service and logged on, and get the following error message:

Msg 921, Level 14, State 1:

Server 'SID':

Database 'saptools' has not been recovered yet - please wait and try again.

Msg 4001, Level 11, State 1:

Server 'SID':

Cannot open default database 'saptools'.

In the SID.log I get the following error messages: (just the main part)

00:0006:00000:00001:2016/03/31 14:42:06.28 server  Database 'master' is now online.

00:0006:00000:00001:2016/03/31 14:42:08.28 server  Database 'sybsystemdb' is now online.

00:0006:00000:00001:2016/03/31 14:42:08.45 server  Database 'model' is now online.

00:0006:00000:00001:2016/03/31 14:42:08.92 server  Database 'tempdb' is now online.


00:0006:00000:00001:2016/03/31 14:42:08.93 server  Error: 926, Severity: 14, State: 1

00:0006:00000:00001:2016/03/31 14:42:08.93 server  Database 'sybsystemprocs' cannot be opened. An earlier attempt at recovery marked it 'suspect'. Check the ASE errorlog for information as to the cause.

00:0006:00000:00001:2016/03/31 14:42:08.95 server  Unable to proceed with the recovery of dbid <31514> because of previous errors.

00:0006:00000:00001:2016/03/31 14:42:08.95 server  Continuing recovery with the next database.

00:0006:00000:00001:2016/03/31 14:42:08.95 server  System stored procedures are not currently accessible due to a recovery error. Please consult the errorlog. You may need to drop and re-create the sybsystemprocs database and re-run the installmaster SQL script if the error is unrecoverable.

00:0006:00000:00001:2016/03/31 14:42:09.90 server  Error: 2812, Severity: 16, State: 5

00:0006:00000:00001:2016/03/31 14:42:09.90 server  Stored procedure 'sp_do_poolconfig' not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).


00:0013:00000:00018:2016/03/31 14:42:09.95 server  Recovering database 'saptools'.

00:0013:00000:00018:2016/03/31 14:42:09.96 server  Started estimating recovery log boundaries for database 'saptools'.

00:0013:00000:00018:2016/03/31 14:42:09.96 kernel  attempted read from memory location 0000000000000092 from instruction at location 0x000000000055088F

00:0013:00000:00018:2016/03/31 14:42:09.96 kernel  Adaptive Server Enterprise system exception (0xc0000005) generated by a storage access violation.

00:0013:00000:00018:2016/03/31 14:42:10.45 kernel  Symbolic stack trace information is successfully loaded

00:0013:00000:00018:2016/03/31 14:42:10.55 kernel  pc: 0x000000000055088F apl__startscan+ 0x69f (0x00000000FFFFFFFF, 0x0000000000000001, 0x0000000007F7F340, 0x0000000000000001)

00:0013:00000:00018:2016/03/31 14:42:10.55 kernel  pc: 0x000000000054FAF6 startptnscan+ 0x4c6 (0x0000000000000069, 0x0000000075656200, 0x0000000007F7F6B0, 0x0000000000000069)

00:0013:00000:00018:2016/03/31 14:42:10.55 kernel  pc: 0x00000000004E182D xsc__syslogs_setscan+ 0x1cd (0x0000000020042150, 0x0000000000000000, 0x00000000723B39C0, 0x0000000000000000)

00:0013:00000:00018:2016/03/31 14:42:10.55 kernel  pc: 0x00000000004E1B39 xls_startscan+ 0x239 (0x00000000706CC8C0, 0x00000000706CC8C0, 0x0000000020B6C948, 0x0000000000000009)

00:0013:00000:00018:2016/03/31 14:42:10.55 kernel  pc: 0x0000000000688C4E ckpt_get_record+ 0x4e (0x0000000000000009, 0x0000000000000001, 0x0000000000000001, 0x0000000000000009)

00:0013:00000:00018:2016/03/31 14:42:10.55 kernel  pc: 0x0000000000412595 rec_logbounds+ 0x3d5 (0x0000000000000001, 0x00000000706CC8C0, 0x0000000000000000, 0x0000000075654930)

00:0013:00000:00018:2016/03/31 14:42:10.55 kernel  pc: 0x0000000000646FCA recovery+ 0x4da (0x000000000125C271, 0x0000000000000001, 0x00000000706CC8C0, 0x0000000000000011)

00:0013:00000:00018:2016/03/31 14:42:10.55 kernel  pc: 0x0000000000677ED1 boot__recover_and_online+ 0x101 (0x00000000B19AA000, 0x00000000B19AA000, 0x0000000000000001, 0x0000000075654930)

00:0013:00000:00018:2016/03/31 14:42:10.55 kernel  pc: 0x00000000006D5DC6 rec__boot_recover_dbs+ 0x126 (0x00000000B19AA000, 0x0000000006C1FB78, 0x0000000000000003, 0x0000000000000008)

00:0013:00000:00018:2016/03/31 14:42:10.55 kernel  pc: 0x00000000015D7B22 rec__parallel_hdlr+ 0x232 (0x0000000006C1FB78, 0x0000000029587230, 0x0000000000000000, 0x0000000000000000)

00:0013:00000:00018:2016/03/31 14:42:10.55 kernel  pc: 0x000000000065965F kpntwrapper+ 0x4f (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)

00:0013:00000:00018:2016/03/31 14:42:10.55 kernel  pc: 0x0000000077608FED CreateFiberEx+ 0x27d (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)

00:0013:00000:00018:2016/03/31 14:42:10.55 kernel  end of stack trace, spid 18, kpid 3735581, suid 0

00:0006:00000:00001:2016/03/31 14:42:11.33 server  Database 'SID' is now online.

00:0006:00000:00001:2016/03/31 14:42:19.18 server  Database 'saptempdb' is now online.

00:0006:00000:00001:2016/03/31 14:42:20.19 server  Database 'sybmgmtdb' is now online.


00:0006:00000:00001:2016/03/31 14:42:20.19 server  Error: 926, Severity: 14, State: 1

00:0006:00000:00001:2016/03/31 14:42:20.19 server  Database 'sybsystemprocs' cannot be opened. An earlier attempt at recovery marked it 'suspect'. Check the ASE errorlog for information as to the cause.

00:0006:00000:00001:2016/03/31 14:42:20.23 server  Error: 2812, Severity: 16, State: 5

00:0006:00000:00001:2016/03/31 14:42:20.23 server  Stored procedure 'sp_do_poolconfig' not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of o

I didn't see an error like this before and I don't know how the "sybsystemprocs" db get marked as "suspect".

I retried to load the master db, that works, but if I try to load saptools, nothing happened. After "go", no error no other information.

Any idea how to get back to a "working" Sybase database?

Thank you!

Best regards,

Tobias

replied

Hi and thanks for your help!

I don't know why, but I never had trouble like that before.

Even after uninstalling all SAP&Sybase components and a fresh installation, I didn't get the DB running.

After hours of searching, my final solution was to wait for our freshly delivered new hardware and installing the whole system inclusive newer Sybase version on that hardware.

Best regards,

Tobias

1 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question