Solved: DB startup failed, terminating with error code 12

Dear All,

I'm new here.

My SAP background is Material Management Module.

We have a problem with SAP.

SAP do not start, after shutdown.

We have done it several times before, and there is no problem.

But this time, it just can't start.

Step by step we have done are :

1. login

2. su - oraXXX

3. lsnrctl start

4. exit

5. su - xxxadm

6. startsap

After that, we have an error:

DB startup failed, terminating with error code 12

What is the problem?

What should we do?

Thanks and Regards,

Gesang

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

Hi,

Please ensure your database is up and running. Please check the alert_SID.log file for more info.

as SIDadm, run R3trans -d and check the log.

Cheers,

Nicholas Chang

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Dear Nicholas Chang,

Database is up and running as well.

We can see the data from Toad for Oracle.

When i run "R3trans -d"

This is the Message:

This is R3trans version 6.14 (release 700 - 29.05.07 - 13:40:00).

unicode enabled version

2EETW000 sap_dext called with msgnr "2":

2EETW000 ---- db call info ----

2EETW000 function: db_ntab

2EETW000 fcode: NT_RDTDESCR

2EETW000 tabname: TADIR

2EETW000 len (char): 5

2EETW000 key: TADIR

2EETW000 retcode: 2

R3trans finished (0012).

peccp01:p01adm 23>

FYI..

Before SAP down, we have done

extend tablespace SAPSR3 @ 9 o'clock local time.

But, it's not by BRTOOLS.

The SAP down approximately @ 14 o'clock local time.

Is it correlated?

Thank you.

please paste the R3trans.log. Is located on the directory where you ran R3trans command.

Hi,

Looks like problem with your database libraries in SAP kernel directory. Have you performed any changes in kernel ??

Regards,

Deepak Kori

Hi..

/usr/sap/SID/SYS/exe/run/dboraslib.so

check this file are available or not

Hi Nicholas,

this is the log

peccp01:p01adm 21> R3trans -d

This is R3trans version 6.14 (release 700 - 29.05.07 - 13:40:00).

unicode enabled version

2EETW000 sap_dext called with msgnr "2":

2EETW000 ---- db call info ----

2EETW000 function: db_ntab

2EETW000 fcode: NT_RDTDESCR

2EETW000 tabname: TADIR

2EETW000 len (char): 5

2EETW000 key: TADIR

2EETW000 retcode: 2

R3trans finished (0012).

this is the directory

peccp01:p01adm 22> ls

dev_sapstart startdb.log stopsap_.log

mountsap.sh startsap_.log stopsap_DVEBMGS00.log

rfcexec.sec startsap_DVEBMGS00.log trans.log

sqlnet.log stopdb.log

peccp01:p01adm 23>

Hi Srinivasan,

Yes, the file is available.

What is it for?

Hi Deepak,

I'm not sure there is any changes in SAP kernel.

How can i check it?

thank you..

Hi,

Do you just perform a normal SAP shutdown and startsap? Any kernel upgrade or changes?

Could you please paste the trans.log here. Thanks.

You can provide the information in log

/oracle/<SID>/saptrace/background/alert_<SID>.log

Just the last 100.

That log give you the reason why your oracle not startup.

Hi Nicholas,

after i crosscheck my partner, there is a process that we have done too.

It's delete archivelog

the process is:

1. login root

2. su - oraSID

3. RMAN target/

4. delete archivelog all;

5. crosscheck archivelog all;

after that, we connect to SQL:

1. sqlplus

2. shutdown immediate;

after that:

startup

Hi Gesang,

Deletion of archive logs will not impact your SAP connection with database using r3trans -d command.

I shall suggest you the following

1) Stop SAP and database

2) Replace the SAP kernel of your problem server with the SAP kernel from working SAP system of Same landscape. For eg: If your affected system is production/ quality, you may copy the kernel from development system

3) Start database

4) Check R3trans -d

5) run the command startsap r3

Regards,

Deepak Kori

Dear Srinivasan,

This is the alert_SID.log:

This the proses extend.

Wed Jan 2 09:49:40 2013

ALTER TABLESPACE PSAPSR3 RESIZE 90G

Wed Jan 2 09:49:40 2013

ORA-32773 signalled during: ALTER TABLESPACE PSAPSR3 RESIZE 90G ...

Wed Jan 2 10:06:12 2013

Incremental checkpoint up to RBA [0x23ee.24fa.0], current log tail at RBA [0x23ee.275c.0]

Wed Jan 2 10:12:56 2013

CREATE TEMPORARY TABLESPACE PSAPSR31

TEMPFILE '/oracle/P01/sapdata2/temp_1/temp.data2.dbf' SIZE 20000M REUSE

AUTOEXTEND ON NEXT 1M MAXSIZE unlimited

EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M

Wed Jan 2 10:12:57 2013

Completed: CREATE TEMPORARY TABLESPACE PSAPSR31

TEMPFILE '/oracle/P01/sapdata2/temp_1/temp.data2.dbf' SIZE 20000M REUSE

AUTOEXTEND ON NEXT 1M MAXSIZE unlimited

EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M

Wed Jan 2 10:14:07 2013

ALTER DATABASE DEFAULT TEMPORARY TABLESPACE PSAPSR31

Wed Jan 2 10:14:07 2013

Completed: ALTER DATABASE DEFAULT TEMPORARY TABLESPACE PSAPSR31

Wed Jan 2 10:36:12 2013

Incremental checkpoint up to RBA [0x23ee.5cc8.0], current log tail at RBA [0x23ee.5ea6.0]

Wed Jan 2 11:06:12 2013

Incremental checkpoint up to RBA [0x23ee.791e.0], current log tail at RBA [0x23ee.799f.0]

Wed Jan 2 11:27:00 2013

Beginning log switch checkpoint up to RBA [0x23ef.2.10], SCN: 4745225335

Thread 1 advanced to log sequence 9199

Current log# 4 seq# 9199 mem# 0: /oracle/P01/origlogB/log_g14m1.dbf

Current log# 4 seq# 9199 mem# 1: /oracle/P01/mirrlogB/log_g14m2.dbf

Wed Jan 2 11:32:01 2013

Completed checkpoint up to RBA [0x23ef.2.10], SCN: 4745225335

And this is the log approximately when SAP down:

Wed Jan 2 14:36:18 2013

Incremental checkpoint up to RBA [0x23f1.9470.0], current log tail at RBA [0x23f1.9a57.0]

Wed Jan 2 14:53:24 2013

Beginning log switch checkpoint up to RBA [0x23f2.2.10], SCN: 4745243731

Thread 1 advanced to log sequence 9202

Current log# 1 seq# 9202 mem# 0: /oracle/P01/origlogA/log_g11m1.dbf

Current log# 1 seq# 9202 mem# 1: /oracle/P01/mirrlogA/log_g11m2.dbf

Wed Jan 2 14:56:47 2013

DROP TABLESPACE PSAPSR3

Wed Jan 2 14:56:47 2013

ORA-1549 signalled during: DROP TABLESPACE PSAPSR3 ...

Wed Jan 2 14:58:29 2013

Completed checkpoint up to RBA [0x23f2.2.10], SCN: 4745243731

Wed Jan 2 14:59:32 2013

DROP TABLESPACE PSAPSR3 INCLUDING CONTENTS AND DATAFILES

Wed Jan 2 15:01:03 2013

Beginning log switch checkpoint up to RBA [0x23f3.2.10], SCN: 4745254089

Thread 1 advanced to log sequence 9203

Current log# 4 seq# 9203 mem# 0: /oracle/P01/origlogB/log_g14m1.dbf

Current log# 4 seq# 9203 mem# 1: /oracle/P01/mirrlogB/log_g14m2.dbf

Wed Jan 2 15:02:53 2013

Beginning log switch checkpoint up to RBA [0x23f4.2.10], SCN: 4745267848

Thread 1 advanced to log sequence 9204

Current log# 3 seq# 9204 mem# 0: /oracle/P01/origlogA/log_g13m1.dbf

Current log# 3 seq# 9204 mem# 1: /oracle/P01/mirrlogA/log_g13m2.dbf

Wed Jan 2 15:04:36 2013

Beginning log switch checkpoint up to RBA [0x23f5.2.10], SCN: 4745281281

Thread 1 advanced to log sequence 9205

Current log# 2 seq# 9205 mem# 0: /oracle/P01/origlogB/log_g12m1.dbf

Current log# 2 seq# 9205 mem# 1: /oracle/P01/mirrlogB/log_g12m2.dbf

Wed Jan 2 15:06:04 2013

Completed checkpoint up to RBA [0x23f3.2.10], SCN: 4745254089

Wed Jan 2 15:06:18 2013

Incremental checkpoint up to RBA [0x23f3.1cea.0], current log tail at RBA [0x23f5.86da.0]

Wed Jan 2 15:06:44 2013

Beginning log switch checkpoint up to RBA [0x23f6.2.10], SCN: 4745297371

Thread 1 advanced to log sequence 9206

Current log# 1 seq# 9206 mem# 0: /oracle/P01/origlogA/log_g11m1.dbf

Current log# 1 seq# 9206 mem# 1: /oracle/P01/mirrlogA/log_g11m2.dbf

Wed Jan 2 15:06:44 2013

ORA-604 signalled during: DROP TABLESPACE PSAPSR3 INCLUDING CONTENTS AND DATAFILES ...

Wed Jan 2 15:07:55 2013

Completed checkpoint up to RBA [0x23f4.2.10], SCN: 4745267848

Wed Jan 2 15:09:38 2013

Completed checkpoint up to RBA [0x23f5.2.10], SCN: 4745281281

Wed Jan 2 15:11:47 2013

Completed checkpoint up to RBA [0x23f6.2.10], SCN: 4745297371

Wed Jan 2 15:18:04 2013

Beginning log switch checkpoint up to RBA [0x23f7.2.10], SCN: 4745349880

Thread 1 advanced to log sequence 9207

Current log# 4 seq# 9207 mem# 0: /oracle/P01/origlogB/log_g14m1.dbf

Current log# 4 seq# 9207 mem# 1: /oracle/P01/mirrlogB/log_g14m2.dbf

Wed Jan 2 15:18:04 2013

Shutting down instance: further logons disabled

Wed Jan 2 15:18:04 2013

Completed checkpoint up to RBA [0x23f7.2.10], SCN: 4745349880

Wed Jan 2 15:18:04 2013

Stopping background process QMNC

Wed Jan 2 15:18:04 2013

Stopping background process CJQ0

Wed Jan 2 15:18:06 2013

Stopping background process MMNL

Wed Jan 2 15:18:07 2013

Stopping background process MMON

Wed Jan 2 15:18:08 2013

Shutting down instance (immediate)

License high water mark = 39

Wed Jan 2 15:18:08 2013

Stopping Job queue slave processes

Wed Jan 2 15:18:08 2013

Job queue slave processes stopped

Wed Jan 2 15:18:09 2013

ALTER DATABASE CLOSE NORMAL

Wed Jan 2 15:18:12 2013

SMON: disabling tx recovery

SMON: disabling cache recovery

Wed Jan 2 15:18:12 2013

Shutting down archive processes

Archiving is disabled

Wed Jan 2 15:18:17 2013

ARCH shutting down

ARC1: Archival stopped

Wed Jan 2 15:18:22 2013

ARCH shutting down

ARC0: Archival stopped

Wed Jan 2 15:18:23 2013

Thread 1 closed at log sequence 9207

Successful close of redo thread 1

Wed Jan 2 15:18:23 2013

Completed: ALTER DATABASE CLOSE NORMAL

Wed Jan 2 15:18:23 2013

ALTER DATABASE DISMOUNT

Completed: ALTER DATABASE DISMOUNT

ARCH: Archival disabled due to shutdown: 1089

Shutting down archive processes

Archiving is disabled

Archive process shutdown avoided: 0 active

ARCH: Archival disabled due to shutdown: 1089

Shutting down archive processes

Archiving is disabled

Archive process shutdown avoided: 0 active

Wed Jan 2 15:28:18 2013

Starting ORACLE instance (normal)

Wed Jan 2 15:28:18 2013

Specified value of sga_max_size is too small, bumping to 2399141888

LICENSE_MAX_SESSION = 0

LICENSE_SESSIONS_WARNING = 0

Picked latch-free SCN scheme 3

Autotune of undo retention is turned on.

IMODE=BR

ILAT =10

LICENSE_MAX_USERS = 0

SYS auditing is disabled

ksdpec: called for event 13740 prior to event group initialization

Starting up ORACLE RDBMS Version: 10.2.0.2.0.

System parameters with non-default values:

processes = 80

sessions = 96

event = 10191 trace name context forever, level 1

sga_max_size = 2399141888

shared_pool_size = 1174405120

shared_pool_reserved_size= 115964116

filesystemio_options = setall

control_files = /oracle/P01/origlogA/cntrl/cntlrP01.dbf, /oracle/P01/origlogB/cntrl/cntrlP01.dbf, /oracle/P01/sapdata1/cntrl/cntrlP01.dbf

control_file_record_keep_time= 30

db_block_size = 8192

db_cache_size = 1174405120

compatible = 10.2.0

log_archive_dest = /oracle/P01/oraarch/P01arch

log_buffer = 14501888

log_checkpoint_interval = 0

db_files = 254

log_checkpoints_to_alert = TRUE

dml_locks = 4000

undo_management = AUTO

undo_tablespace = PSAPUNDO

undo_retention = 43200

recyclebin = off

remote_os_authent = TRUE

remote_login_passwordfile= EXCLUSIVE

job_queue_processes = 1

background_dump_dest = /oracle/P01/saptrace/background

user_dump_dest = /oracle/P01/saptrace/usertrace

core_dump_dest = /oracle/P01/saptrace/background

optimizer_features_enable= 10.2.0.1

sort_area_size = 2097152

sort_area_retained_size = 0

db_name = P01

open_cursors = 800

_optim_peek_user_binds = FALSE

pga_aggregate_target = 1546188226

workarea_size_policy = AUTO

statistics_level = typical

PMON started with pid=2, OS id=2834

PSP0 started with pid=3, OS id=2841

MMAN started with pid=4, OS id=2853

DBW0 started with pid=5, OS id=2860

LGWR started with pid=6, OS id=2873

CKPT started with pid=7, OS id=2883

SMON started with pid=8, OS id=2885

RECO started with pid=9, OS id=2888

CJQ0 started with pid=10, OS id=2890

MMON started with pid=11, OS id=2892

MMNL started with pid=12, OS id=2895

Wed Jan 2 15:28:20 2013

ALTER DATABASE MOUNT

Wed Jan 2 15:28:24 2013

Setting recovery target incarnation to 1

Wed Jan 2 15:28:24 2013

Successful mount of redo thread 1, with mount id 1516783572

Wed Jan 2 15:28:24 2013

Database mounted in Exclusive Mode

Completed: ALTER DATABASE MOUNT

Wed Jan 2 15:28:24 2013

ALTER DATABASE OPEN

Wed Jan 2 15:28:25 2013

LGWR: STARTING ARCH PROCESSES

ARC0 started with pid=14, OS id=2899

Wed Jan 2 15:28:25 2013

ARC0: Archival started

ARC1: Archival started

LGWR: STARTING ARCH PROCESSES COMPLETE

ARC1 started with pid=15, OS id=2901

Wed Jan 2 15:28:25 2013

ARC0: STARTING ARCH PROCESSES

Wed Jan 2 15:28:25 2013

Thread 1 opened at log sequence 9207

Current log# 4 seq# 9207 mem# 0: /oracle/P01/origlogB/log_g14m1.dbf

Current log# 4 seq# 9207 mem# 1: /oracle/P01/mirrlogB/log_g14m2.dbf

Successful open of redo thread 1

Wed Jan 2 15:28:25 2013

Is there something wrong?

Hi,

Its ok.

>sqlplus "/as sysdba"

SQL>startup

Try this. then start sap.

Dear Srinivasan,

I have done your step by step.

But it got the same result.

Terminating with error code 12

DB startup failed

need another solution..

Dear Srinivasan,

I have done your step by step.

But it got the same result.

Terminating with error code 12

DB startup failed

need another solution..

Hi,

Please try this.

https://scn.sap.com/thread/462019

Dear Deepak,

The big problem is..

This is Production server that can't up.

https://scn.sap.com/thread/755529

according above link..

How can i replace the production kernel with Development kernel?

or..

Can we use Development Server as Prod Server, by importing data from Prod oracle?

thank you for your response.

Hi,

Just copy kernel exe file from Dev to Prod

Development Server: /sapmnt/<SID>/exe to Production Server: /sapmnt/<SID>/exe

@Srinivasan,

I have compare with command ls in Dev Server and Prod Server in folder exe.

They have similar content in amount & name in both server.

So..

I think SAP Prod kernel is not corrupt, isn't it?

Answers (2)

Dear All,

Sorry for late reply..

The fact is..

We acknowledge that SAP database is corrupt.

There are more than 2000 table is missing in the Prod Server.

We try to patch the Prod database from Dev Server.

The SAP Prod can start, but there is nothing we can do because we found error on each t-code that we try.

So, we decide to restore from the last backup.

After all.

Thank you for all your response and advise.

God Bless u all.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

1. Run the R3trans -x with sidadm.

and paste the content of trans.log which will get created in the current directory.

With Regards

Ashutosh Chaturvedi

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Ask a Question

DB startup failed, terminating with error code 12

Accepted Solutions (1)

Accepted Solutions (1)

Answers (2)

Answers (2)

Re: ASEGURAMIENTO DE TABLAS

Re: Getting error while Creating role in BRM

Re: How to enable the add, delete,edit system on s...

Re: CJS-30252 Running priviledged function stop of...

Successfactors login issue.