 Posted 3/11/2009 1:46:35 AM
|
|
|
|
I recently saw this in the alert log:
Errors in file /u8oracle/local/QA/bdump/qa_dbw0_164816.trc:
ORA-01157: cannot identify/lock data file 15 - see DBWR trace file
ORA-01110: data file 15: '/u8oraindex1/QA/libraryx_01.dbf'
ORA-27092: size of file exceeds file size limit of the process
Additional information: 131071
Additional information: 281601
Tue Mar 10 22:13:06 2009
Errors in file /u8oracle/local/QA/bdump/qa_dbw0_164816.trc:
ORA-01157: cannot identify/lock data file 18 - see DBWR trace file
ORA-01110: data file 18: '/ux228oradata1/QA/masterd_01.dbf'
ORA-27092: size of file exceeds file size limit of the process
Additional information: 131071
Additional information: 704001
Tue Mar 10 22:13:06 2009
Errors in file /u8oracle/local/QA/bdump/qa_dbw0_164816.trc:
ORA-01157: cannot identify/lock data file 19 - see DBWR trace file
ORA-01110: data file 19: '/u8oraindex1/QA/masterx_01.dbf'
ORA-27092: size of file exceeds file size limit of the process
Cause:
The account that is used to run the stored procedure or simple SQL query could yield the above errors. The issue was related to the ULIMIT set to the user account.
Solution:
Have UNIX administrator reset the ULIMIT to a higher value or "unlimited" .
I checked my environment and it was set to unlimited:
proddbserv01: /u8oracle/local/QA/bdump/> ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 4194304
memory(kbytes) unlimited
coredump(blocks) 2097151
nofiles(descriptors) 2000
and still saw in the alert log the error message. Then I realized that the database was not started using the oracle account which has the unlimited settings. It was started by another user. I then logged in to sqlplus and shutdown immediate and then issued startup.
This worked and the database started up successfully.
Hope this helps.
Thanks,
|
|
|
|