Mani's Blog

August 16, 2012

Oracle Startup fails with ORA-27102: out of memory Solaris-AMD64 Error: 22: Invalid argument

Filed under: Database,Oracle — mani @ 9:51 pm

Issue: Oracle startup on Solaris 10G failed with following errors.

oracle@xnodb916:~$ dba

SQL*Plus: Release 10.2.0.3.0 – Production on Thu Aug 16 21:33:24 2012

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

Connected to an idle instance.

SQL> startup nomount pfile=/local/opt/oracle/product/10.2.0.3/db5/dbs/initDSP0001.ora
ORA-27102: out of memory
Solaris-AMD64 Error: 22: Invalid argument

Solution:

*Solution:*   This error represents that max-shm-memory is not sized correctly.  Either reduce Oracle memory usage on appropriate parameters.  (OR) Increase max-shm-memory
In increase max-shm-memory, run following command as root:  Change the memory value based on your memory availability.
root@xnodb916:~# prctl -n project.max-shm-memory -v 25gb -r -i project user.oracle
root@xnodb916:~# prctl -n project.max-shm-memory -v 35gb -r -i project user.oracle

Reducing memory allocation on init***.ora fixed the issue.

Reduced shared_pool_size, pga_aggregate_target and db_cache_size.  Then started the DB successfully.

SQL> startup nomount pfile=/local/opt/oracle/product/10.2.0.3/db5/dbs/initDSP0001.ora
ORACLE instance started.

Total System Global Area 1.2046E+10 bytes
Fixed Size                  2191376 bytes
Variable Size             731680752 bytes
Database Buffers         1.1308E+10 bytes
Redo Buffers                4325376 bytes
SQL>

If AMM is enabled then SGA_TARGET and SGA_MAX_SIZE need to be reduced.

Advertisements

“RMAN-06053: unable to perform media recovery because of missing log” “ORA-01194: file 2 needs more recovery to be consistent”

Filed under: Backup,Database,Oracle,RMAN — mani @ 6:23 pm

Issue:  While restoring 10g database, ran into following issue
“ORA-01194: file 2 needs more recovery to be consistent”
“RMAN-06053: unable to perform media recovery because of missing log”

RMAN> run {
allocate channel d1 device type disk;
allocate channel d2 device type disk;
allocate channel d3 device type disk;
allocate channel d4 device type disk;
restore database;
switch datafile all;
switch tempfile all;
recover database;
}2> 3> 4> 5> 6> 7> 8> 9> 10>

allocated channel: d1
channel d1: sid=156 devtype=DISK

allocated channel: d2
channel d2: sid=155 devtype=DISK

allocated channel: d3
channel d3: sid=154 devtype=DISK

allocated channel: d4
channel d4: sid=153 devtype=DISK

Starting restore at 16-AUG-12

channel d1: starting datafile backupset restore
channel d1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /local/opt/oracle/oradata/XNODBGRD/system01.dbf
restoring datafile 00002 to /local/opt/oracle/oradata/XNODBGRD/undotbs01.dbf
restoring datafile 00003 to /local/opt/oracle/oradata/XNODBGRD/sysaux01.dbf
restoring datafile 00004 to /local/opt/oracle/oradata/XNODBGRD/users01.dbf
restoring datafile 00005 to /local/opt/oracle/oradata/XNODBGRD/mgmt.dbf
restoring datafile 00006 to /local/opt/oracle/oradata/XNODBGRD/mgmt_ecm_depot1.dbf
restoring datafile 00007 to /local/opt/oracle/oradata/XNODBGRD/tools01.dbf
channel d1: reading from backup piece /local/data/oracle/nfs/XNODBGRD/backupset/2012_08_15/o1_mf_nnndf_BKP_XNODBGRD_FULL_08_82pc74fq_.bkp

channel d1: restored backup piece 1
piece handle=/local/data/oracle/nfs/XNODBGRD/backupset/2012_08_15/o1_mf_nnndf_BKP_XNODBGRD_FULL_08_82pc74fq_.bkp tag=BKP_XNODBGRD_FULL_081512050003
channel d1: restore complete, elapsed time: 00:25:45
Finished restore at 16-AUG-12

Starting recover at 16-AUG-12

starting media recovery

Oracle Error:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 2 needs more recovery to be consistent
ORA-01110: data file 2: ‘/local/opt/oracle/oradata/XNODBGRD/undotbs01.dbf’

released channel: d1
released channel: d2
released channel: d3
released channel: d4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/16/2012 18:03:00
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 81113 lowscn 1817591460 found to restore

RMAN>

Solution:

Set the sequence until necessary and recover the database.

RMAN> run {
2> set until sequence 81112;
3> recover database;
4> }

Blog at WordPress.com.