Backing Up Oracle - Computing at Cornell

RMAN> run{
2> allocate channel t1 type 'sbt_tape';
3> backup (database);
4> }
...
RMAN-08503: piece handle=0ncm82dr_1_1 comment=API Version 1.1,MMS Version 2.1.10
.0
RMAN-08525: backup set complete, elapsed time: 00:02:48
RMAN-08031: released channel: t1
After taking the backup we ran the SQL query select * from backups where
node_name=’JAMAICA_ORACLE’. The entry in the quotes is case sensitive and
must be upper case. The output of this command tells us that the backup
object was sent by a client program (TDP Oracle) that authenticated with the
TSM server as node JAMAICA_ORACLE. The client program did not specify
which management class to use with this object so the TSM server bound the
default management class for the node to this backup object. TDP for Oracle
for Windows uses \adsmorc as the FILESPACE_NAME when sending the
object to the TSM server. The HL_NAME or high level qualifier is \orcnt\. For
the LL_NAME or low level qualifier, TSM uses the piece name that is
automatically generated by RMAN. The LL_NAME can be controlled by using
the format option in the RMAN script.
tsm: BRAZIL>select * from backups where node_name='JAMAICA_ORACLE'
ANR2963W This SQL query may produce a very large result table, or may require a
significant amount of time to compute.
Do you wish to proceed? (Yes (Y)/No (N)) y
NODE_NAME: JAMAICA_ORACLE
FILESPACE_NAME: \adsmorc
STATE: ACTIVE_VERSION
TYPE: FILE
HL_NAME: \orcnt\
LL_NAME: 0ncm82dr_1_1
OBJECT_ID: 94130
BACKUP_DATE: 2001-04-02 08:36:30.000000
DEACTIVATE_DATE:
OWNER:
CLASS_NAME: DEFAULT
4.5.2.2 Viewing the description of an archive object
TDP for Oracle does not store any database objects as archive objects on the
TSM server. You could use the TSM backup-archive client archive feature to
perform an operating system or file level backup of the Oracle database files.
The archive feature does not perform versioning, but keeps all objects under
an archive description.
38 Backing Up Oracle using Tivoli Storage Management