cancel
Showing results for 
Search instead for 
Did you mean: 

ORA-27092 when running startsap

Former Member
0 Kudos

Hi All,

We have a weird one. Following a reboot of out AIX 6.1 box, we are unable to start SAP as it fails when starting the database:

Caused by: java.sql.SQLException: ORA-01116: error in opening database file 5

ORA-01110: data file 5: '/oracle/EPD/sapdata4/sr3db_2/sr3db.data2'

ORA-27092: size of file exceeds file size limit of the process

Additional information: 131071

Additional information: 256001

Now, a few points that make this an odd issue.

sidadm has unlimited ulimits on this box:

time(seconds) unlimited

file(blocks) unlimited

data(kbytes) unlimited

stack(kbytes) unlimited

memory(kbytes) unlimited

coredump(blocks) unlimited

nofiles(descriptors) unlimited

threads(per process) unlimited

processes(per user) unlimited

And with the SIDADM user, I can run SQLplus and start/stop the database without issue. However, SAP is not startable for the reason above and an R3trans -d run returns the same error code.

Any thoughts? Thanks!

Accepted Solutions (1)

Accepted Solutions (1)

stefan_koehler
Active Contributor
0 Kudos

Hello Tim,

> And with the SIDADM user, I can run SQLplus and start/stop the database without issue

but the oracle database runs under ora<SID> ... what is the ulimit of this user?

Regards

Stefan

Answers (4)

Answers (4)

Former Member
0 Kudos

Dear All,

I facing same error which is generated from DB13 only (not command prompt). the problem is stated after system is shutdown abnormal. after restarted, these error always generated.

10.01.2012 16:19:47 Job started

10.01.2012 16:19:47 Step 001 started (program RSDBAJOB, variant &0000000000998, user ID JOHNMAR)

10.01.2012 16:19:47 Execute logical command BRCONNECT On host sapdev

10.01.2012 16:19:47 Parameters: -u / -jid CHECK20120110161947 -c -f check

10.01.2012 16:19:47 BR0801I BRCONNECT 7.20 (16)

10.01.2012 16:19:47 BR0805I Start of BRCONNECT processing: cehqcljn.chk 2012-01-10 16.19.47

10.01.2012 16:19:47 BR0484I BRCONNECT log file: /oracle/DEV/sapcheck/cehqcljn.chk

10.01.2012 16:19:47 BR0477I Oracle pfile /oracle/DEV/102_64/dbs/initDEV.ora created from spfile /oracle/DEV/102_64/dbs/spfileDEV.ora

10.01.2012 16:19:47 BR0280I BRCONNECT time stamp: 2012-01-10 16.19.47

10.01.2012 16:19:47 BR0301E SQL error -1116 at location BrLicCheck-12, SQL statement:

10.01.2012 16:19:47 'SELECT MAX(SYSTEMNAME), MAX(SYSID) FROM SAP_MLICHECK WHERE EXPIRATION_DATE = (SELECT MAX(EXPIRATION_DATE) FROM SAP_MLICHECK)'

10.01.2012 16:19:47 ORA-01116: error in opening database file 17

10.01.2012 16:19:47 ORA-01110: data file 17: '/oracle/DEV/sapdata2/sr3_14/sr3.data14'

10.01.2012 16:19:47 ORA-27092: size of file exceeds file size limit of the process

10.01.2012 16:19:47 Additional information: 262143

10.01.2012 16:19:47 Additional information: 453121

10.01.2012 16:19:47 BR0280I BRCONNECT time stamp: 2012-01-10 16.19.47

10.01.2012 16:19:47 BR0301W SQL error -1116 at location brc_dblog_open-1, SQL statement:

10.01.2012 16:19:47 'INSERT INTO SAP_SDBAH (BEG, FUNCT, SYSID, OBJ, RC, ENDE, ACTID, LINE) VALUES ('20120110161947', 'chk', 'DEV', 'DATABASE', '9999

10.01.2012 16:19:47 ORA-01116: error in opening database file 34

10.01.2012 16:19:47 ORA-01110: data file 34: '/oracle/DEV/sapdata2/sr3_31/sr3.data31'

10.01.2012 16:19:47 ORA-27092: size of file exceeds file size limit of the process

10.01.2012 16:19:47 Additional information: 262143

10.01.2012 16:19:47 Additional information: 706561

10.01.2012 16:19:47 BR0324W Insertion of database log header failed

10.01.2012 16:19:47

10.01.2012 16:19:47 BR0806I End of BRCONNECT processing: cehqcljn.chk2012-01-10 16.19.47

10.01.2012 16:19:47 BR0280I BRCONNECT time stamp: 2012-01-10 16.19.47

10.01.2012 16:19:47 BR0804I BRCONNECT terminated with errors

10.01.2012 16:19:47 External program terminated with exit code 3

10.01.2012 16:19:47 BRCONNECT returned error status E

10.01.2012 16:19:47 Job finished

You may need to check oracle metalink . this below solution may be helpful but it' s working for me.

1. stopsap and all sap processes

2. delete all things in /tmp

3. check your user and group <sid>adm, ora<sid>

Ex:

sapsys: devadm,sapadm,daaadm

dba: :oradev,devadm

oper: oradev,devadm

4. change /etc/security/limits:

default:

fsize = 2097151

core = 2097151

cpu = -1

data = 262144

rss = 65536

stack = 65536

nofiles = 32000

root:

fsize = -1

core = -1

cpu = -1

data = -1

rss = -1

pconsole:

stack_hard = 131072

data = 1280000

data_hard = 1280000

esaadmin:

stack = 393216

stack_hard = 393216

devadm:

fsize = -1

data = -1

stack = -1

core = -1

rss = -1

nofiles = -1

threads = -1

nproc = -1

cpu_hard = -1

fsize_hard = -1

data_hard = -1

stack_hard = -1

stack = -1

nofiles = -1

threads_hard = -1

nproc_hard = -1

oradev:

fsize = -1

data = -1

stack = -1

core = -1

rss = -1

nofiles = -1

threads = -1

nproc = -1

cpu_hard = -1

fsize_hard = -1

data_hard = -1

stack_hard = -1

core_hard = 2097151

rss_hard = -1

nofiles_hard = -1

threads_hard = -1

nproc_hard = -1

5. startsap and try DB13 again

Good luck

Former Member
0 Kudos

Hey Guys,

Thanks to all of you for the quick response. For the record, both epdadm and oraepd had ulimits 'unlimited' for all values when we tested all of this.

When we checked the results of "startsap" run as epdadm we found that while the startup script failed, and returned a failed error message, the database actually started. However, after the database started, and the startup script ran "R3trans -d", we received the failure. (R3trans -x worked without issue).

For some reason we still do not understand, when we ran R3trans as epdadm, the ulimits assigned to epdadm did not pick up.

The solution, as much as it pains me as a UNIX friendly guy, was to reboot the server. Following the reboot, these phantom ulimits disappeared and the correct ulimit settings took over. The system has since returned to normal.

Again - thanks guys for the fast response.

Cheers,

Tim

Former Member
0 Kudos

Hello,

Stefan is correct, check the ulimit for ora<sid> user.

Check SAP Note 553854, point no:4 in Solutions part.

Regards,

Yoganand.V

sunny_pahuja2
Active Contributor
0 Kudos

Hi,

also, check SAP Note 129439 - Maximum file sizes with Oracle

Thanks

Sunny