cancel
Showing results for 
Search instead for 
Did you mean: 

error after 10g upgrade.

Former Member
0 Kudos

Dear all,

We upgraded from oracle 9i to 10g. But after upgrading when I schedule online backup and click on the tapes in DB13. I get the following errors.

BRBACKUP:

BR0278E Command output of '/oracle/TAP/102_64/bin/sqlplus':

SQL*Plus: Release 10.2.0.2.0 - Production on Thu Jun 14 14:47:52 2007

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

SQL> Connected to an idle instance.

SQL>

SQL> ORA-27123: unable to attach to shared memory segment

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

SQL> Disconnected

BR0279E Return code from '/oracle/TAP/102_64/bin/sqlplus': 0

BR0302E SQLPLUS call for database instance TAP failed

BR0306E Start and open of database instance TAP failed

Can any one pls help me.

Rgds

Lalit Rana

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Check permissions for /oracle/client/10x_64 and all subfolders/files

Check dependancies with -

ldd /usr/sap/<SID>/SYS/exe/run/dboraslib.o

fidel_vales
Employee
Employee
0 Kudos

Hi,

There seem to be an authorization problem.

Can you check the authorizations of oracle executable?

ls -l $ORACLE_HOME/bin/oracle

check note 583861 for more information

markus_doehr2
Active Contributor
0 Kudos

- check that your shell allows creating a huge stack size (limit/ulimit)

- decrease the size of your SGA and check if you can get the database up

on what OS level and MP is your system?

--

Markus

Former Member
0 Kudos

Thanx Markus for your reply. We are using AIX 5.2 version.

The database is up only. This error is comming while scheduling backup in db13 (when I click on "Tapes" button).

Rgds

markus_doehr2
Active Contributor
0 Kudos

Check under what user the br*tools are running:

ls -l /usr/sap/<SID>/exe

Do they have the ora<sid> owner and the sticky bit set? (that is done after a kernel upgrade by the script saproot.sh)

--

Markus

Former Member
0 Kudos

Still the problem remains same after doing what was suggested by you.

Rgds

Amit

markus_doehr2
Active Contributor
0 Kudos

Does this happen only when you schedule through DB13 or does this also happen when you execute the program with the same paramters as user <sid>adm?

--

Markus