cancel
Showing results for 
Search instead for 
Did you mean: 

Error during startsap all

Former Member
0 Kudos

Hi,

I am starting the services using startsap all command in IBM aix server oracle 10g. i am getting belo error message.

-


Wed Sep 23 15:50:38 IST 2009

LOGFILE FOR STARTING ORACLE

Trying to start KBP database ...

-


Wed Sep 23 15:50:38 IST 2009

checking required environment variables

ORACLE_HOME is >/oracle/KBP/102_64<

ORACLE_SID is >KBP<

-


Wed Sep 23 15:50:38 IST 2009

check initora

-


Wed Sep 23 15:50:38 IST 2009

check initora

-


Wed Sep 23 15:50:38 IST 2009

checking V2 connect

n 23-SEP-2009 15:50:38

Copyright (c) 1997, 2005, Oracle. All rights reserved.

Used parameter files:

/usr/sap/KBP/SYS/profile/oracle/sqlnet.ora

Used TNSNAMES adapter to resolve the alias

= KBP) (GLOBAL_NAME = KBP.WORLD)))

OK (50 msec)

tnsping: V2 connect to KBP

-


Wed Sep 23 15:50:38 IST 2009

Connect to the database to check the database state:

R3trans: connect check finished with return code: 12

Database not available

-


Wed Sep 23 15:50:38 IST 2009

Shutdown database

First trying to shutdown the database - May be,

the database is in the nomount or mount state

-


Wed Sep 23 15:50:39 IST 2009

starting database

SQL*Plus: Release 10.2.0.2.0 - Production on Wed Sep 23 15:50:39 2009

Copyright (c) 1982, 2005, Oracle. All Rights Reserved.

Connected to an idle instance.

ORACLE instance started.

Total System Global Area 2097152000 bytes

Fixed Size 2072544 bytes

Variable Size 1056964640 bytes

Database Buffers 1023410176 bytes

Redo Buffers 14704640 bytes

ORA-00221: error on write to control file

ORA-00206: error in writing (block 1, # blocks 1) of control file

ORA-00202: control file: '/oracle/KBP/origlogA/cntrl/cntrlKBP.dbf'

ORA-27041: unable to open file

IBM AIX RISC System/6000 Error: 13: Permission denied

Additional information: 3

bit Production

With the Partitioning and Data Mining options

-


Wed Sep 23 15:50:49 IST 2009

Connect to the database to verify, that the database is now open

R3trans check finished with return code: 12

      • ERROR: Startup of database failed

Notify Database Administrator.

/usr/sap/KBP/SYS/exe/run/startdb: Terminating with error code 12

kindly do the needful to solve the problem.

kvl

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

The issue is due to the permissions on oracle files/file system.

Please see the oss note

Note 583861 - UNIX: Errors due to Oracle executable.

Check whether the authorizations for the file are set correctly (NT, W2K: "Full Control for Everyone"). The error can also occur if another process, such as external backup tool or virus scanner is blocking the file, or if a block of this type of process is hanging after the process terminates. On UNIX, you should also check the Oracle Executable for correct authorizations (6751) in $ORACLE_HOME/bin (Note 583861). If the error occurs when you execute the BR*TOOLS, check whether it has the correct authorizations (Note 651351).

Thanks,

Shambo

Former Member
0 Kudos

Hi,

Error resolved using sap note 583861.

kvl

Answers (1)

Answers (1)

markus_doehr2
Active Contributor
0 Kudos

> Total System Global Area 2097152000 bytes

> Fixed Size 2072544 bytes

> Variable Size 1056964640 bytes

> Database Buffers 1023410176 bytes

> Redo Buffers 14704640 bytes

> ORA-00221: error on write to control file

> ORA-00206: error in writing (block 1, # blocks 1) of control file

> ORA-00202: control file: '/oracle/KBP/origlogA/cntrl/cntrlKBP.dbf'

> ORA-27041: unable to open file

> IBM AIX RISC System/6000 Error: 13: Permission denied

> Additional information: 3

> kindly do the needful to solve the problem.

We can't solve the problem for you You have to check the permissions of the mentioned file.

Markus

Former Member
0 Kudos

Check note 546006 .

Thanks

Anish

Former Member
0 Kudos

You need to do some basic stuff first

1. Is the Database up ??

2. If so, do R3trans -d and look at trans.log which is wirtten in the same directory you executed the command from.

Fix that error and then only proceed with starting SAP

Pravin