$sqlplus /nolog;
SQL>connect / as sysdba;
SQL>startup nomount;
SQL>exit;

$rman target / nocatalog
RMAN>set dbid=147749264
RMAN>run
{
allocate channel d1 type disk;
set CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO ‘$ORACLE_BASE/oradata/rman_backup/control%F’;
Restore spfile from autobackup;
Release channel d1;
}

Here is the error info: RMAN-06564: rman must use the t0 clause when the instance is started with spfile

This error info implies that you were using default SPFILE ($ORACLE_HOME/dbs/spfile<SID>.ora) to startup the database. Database STARTUP NOMOUNT will use the default PFILE or SPFILE.

Problem solving:

Method 1: remove spfile, startup nomount using pfile;

Method 2: from documentation,

If restoring to a nondefault location, then you could run commands as in the following example:
RESTORE SPFILE TO ‘/tmp/spfileTEMP.ora’; # if you are using a catalog
RESTORE SPFILE TO ‘/tmp/spfileTEMP.ora’ FROM AUTOBACKUP; # if in NOCATALOG mode

References:

1. http://www.orafaq.com/forum/t/56572/0/
2. [Chinese] http://space.itpub.net/7199859/viewspace-62315
3. http://forums.oracle.com/forums/thread.jspa?threadID=661030&tstart=45

$nohup ./rmanbkp.sh
nohup: cannot run command ‘./rmanbkp.sh’: Permission denied

$chmod +x rmanbkp.sh
$nohup ./rmanbkp.sh
nohup: appending output to ‘nohup.out’
nohup: cannot run command ‘./rmanbkp.sh’: No such file or directory

The first line in rmanbkp.sh was

#!/usr/bin/sh

It might be a shell problem. Check ksh path

$which ksh
/bin/ksh

Change it to

#!/bin/ksh

Or, it might be a path problem. Check sh path

$which sh
/bin/sh

Change it to

#!/bin/sh

Reference:

1. http://docs.jach.hawaii.edu/JAC/JACUN/008.0/node42.html
2. http://www.gammon.com.au/forum/?id=8009&page=1

$rman target / catalog
rman: can’t open target % ERROR INFO

Because there is another rman file in the system (use which to see the file location as follows). The ORACLE rman is in $ORACLE_HOME/bin.

$which rman
/usr/X11R6/bin/rman

Two ways to solve this problem:

1) Put $ORACLE_HOME/bin at the very beginning of $PATH in your environment

2) run with Oracle RMAN path

$ $ORACLE_HOME/bin/rman target / catalog <id>/<password>@<catalog database name>

Reference:

1. http://forums.oracle.com/forums/thread.jspa?threadID=198071
2. http://www.shutdownabort.com/dbaqueries/Backup_RMAN.php

Some silly problems may incur everyday:

• Wrong spelling. ex. “contraint” -> “constraint”
• Missing parenthesis
• Make sure all the commands in the scripts have the right path, for example, the RMAN case
• Correct shell choice

When we tried to change tablespace storage paramters in a DBCA created database, we may get the following error information because the storage settings for locally managed tablespaces cannot be altered.

ORA-25143: default storage clause is not compatible with allocation policy.

Or, if you want to create a tablespace dictionary managed, you might get this error information:

ORA-12913: Cannot create dictionary managed tablespace

In Unix, type “oerr ora 12913″, you’ll get:

*Cause: Attemp to create dictionary managed tablespace in database which has system tablespace as locally manged

*Action: Create a locally managed tablespace.

Using the following SQL scripts, you will find the status of SYSTEM tablespace.

select tablespace_name, extent_management
from dba_tablespaces
where tablespace_name = ‘SYSTEM’;

TABLESPACE_NAME EXTENT_MAN
—————- ———–
SYSTEM LOCAL

Every Oracle database contains a tablespace named SYSTEM, which Oracle creates automatically when the database is created. The SYSTEM tablespace is always online when the database is open. DBCA creates by default a database with locally managed system tablespace.

To take advantage of the benefits of locally managed tablespaces, you can create a locally managed SYSTEM tablespace, or you can migrate an existing dictionary managed SYSTEM tablespace to a locally managed format.

In a database with a locally managed SYSTEM tablespace, dictionary managed tablespaces cannot be created. It is possible to plug in a dictionary managed tablespace using the transportable feature, but it cannot be made writable.

Once a tablespace is locally managed, it cannot be reverted back to being dictionary managed.

You can create a database with a dictionary managed system tablespace. A simple SQL script can be created and then executed via SQL*Plus which will create your database with all the options you might want. A simple example:

create database yourdb controlfile reuse
maxdatafiles 1064
character set “AL32UTF8″
national character set “UTF8″
datafile
‘d:\yourfilesystem\yourdb_system_01.dbf’ size 250M
extent management dictionary
undo tablespace yourdb_undo
datafile ‘d:\anotherfilesystem\yourdb_undo_01.dbf’ size 400M
logfile
group 1 (………… etc… etc.

This is a very simplistic example with limited options included. You can check the “create database” command options in any Oracle reference with the appropriate version of database you are using. The GUI tools such as DBCA don’t always provide the easiest nor complete options available for managing your Oracle databases.

Reference: Oracle 9i How to Create Dictionary Managed Tablespace