tivoli_data_protection_for_oracle_tdpo
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| tivoli_data_protection_for_oracle_tdpo [2018/12/08 12:49] – created 0.0.0.0 | tivoli_data_protection_for_oracle_tdpo [2019/01/30 11:32] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Tivoli_Data_Protection_for_Oracle_(TDPO) ====== | ||
| - | |||
| 'work in progress' | 'work in progress' | ||
| - | =====Setting up RMAN to backup directly to tape===== | + | ==== Setting up RMAN to backup directly to tape ==== |
| - | RMAN cannot backup directly to tape due to there being many different tape backup suppliers.<br /> | + | RMAN cannot backup directly to tape due to there being many different tape backup suppliers.\\ |
| The solution is the TDPO interface to which tape suppliers supply parameters. RMAN then knows what to do. | The solution is the TDPO interface to which tape suppliers supply parameters. RMAN then knows what to do. | ||
| - | ====Files involved==== | + | === Files involved === |
| - | * dsm.sys | + | * dsm.sys |
| - | * dsm.opt | + | * dsm.opt |
| - | * tdpo.opt | + | * tdpo.opt |
| - | =====Setting up DataPump to backup directly to tape===== | + | ==== Setting up DataPump to backup directly to tape ==== |
| - | ====Files involved==== | + | === Files involved === |
| - | * dsm.sys | + | * dsm.sys |
| - | By default dsm.sys is located in / | + | By default dsm.sys is located in / |
| An example using PROMPT | An example using PROMPT | ||
| - | < | + | < |
| + | SErvername | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | </ | ||
| An example using GENERATE | An example using GENERATE | ||
| - | < | + | < |
| + | SErvername | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | </ | ||
| - | < | + | < |
| + | cat tdpo_SINTP1.opt | ||
| + | DSMI_ORC_CONFIG | ||
| + | DSMI_LOG | ||
| + | TDPO_FS | ||
| + | TDPO_NODE | ||
| + | TDPO_PSWDPATH | ||
| + | * tdpo_trace_flags orclevel0 orclevel1 orclevel2 | ||
| + | * tdpo_trace_file | ||
| + | </ | ||
| or | or | ||
| - | < | + | < |
| + | cat tdpo.opt | ||
| + | DSMI_ORC_CONFIG | ||
| + | DSMI_LOG | ||
| + | TDPO_FS | ||
| + | * tdpo_trace_flags orclevel0 orclevel1 orclevel2 | ||
| + | * tdpo_trace_file / | ||
| + | </ | ||
| Line 30: | Line 85: | ||
| From [[http:// | From [[http:// | ||
| - | ======RMAN configuration with Tivoli Data Protection for Oracle (TDPO)====== | + | ===== RMAN configuration with Tivoli Data Protection for Oracle (TDPO) ===== |
| - | tdpo is generally installed in either / | + | tdpo is generally installed in either / |
| - | The configuration and testing described in this document have been done on Red Hat Enterprise Linux Server release 5.5 (Tikanga) 64 bits with Oracle 11gR2 (11.2.0.2.0) and 10gR2 (10.2.0.5.0).<br /> | + | The configuration and testing described in this document have been done on Red Hat Enterprise Linux Server release 5.5 (Tikanga) 64 bits with Oracle 11gR2 (11.2.0.2.0) and 10gR2 (10.2.0.5.0).\\ |
| - | First let you preferred system administrator install the product for you, you should find it in:<br /> | + | First let you preferred system administrator install the product for you, you should find it in:\\ |
| - | < | + | < |
| + | [[root@oracleserver.domainname /]]# ll / | ||
| + | total 20 | ||
| + | drwxr-xr-x 4 root bin 4096 Jun 7 15:28 api | ||
| + | drwxr-xr-x 3 root bin 4096 Jun 7 15:27 icc32 | ||
| + | drwxr-xr-x 3 root bin 4096 Jun 7 15:28 icc64 | ||
| + | drwxr-xr-x 3 root bin 4096 Jun 7 15:27 lang | ||
| + | drwxr-xr-x 5 root root 4096 Jun 7 15:29 oracle | ||
| + | </ | ||
| The Tivoli Storage Manager (TSM) server configuration part is in: | The Tivoli Storage Manager (TSM) server configuration part is in: | ||
| - | < | + | < |
| + | [[root@oracleserver.domainname /]]# ll / | ||
| + | total 4044 | ||
| + | -rwxr-xr-x 1 root root 810 Jul 13 06:33 dsm.opt | ||
| + | -r--r--r-- 1 root bin 782 Dec 5 2006 dsm.opt.smp | ||
| + | -rwxr-xr-x 1 root root 1194 Jul 13 12:17 dsm.sys | ||
| + | -r--r--r-- 1 root bin 971 Dec 5 2006 dsm.sys.smp | ||
| + | -rwsr-xr-x 1 root bin 1832042 Nov 28 2006 dsmtca | ||
| + | lrwxrwxrwx 1 root bin 16 Jun 7 15:28 en_US -> ../ | ||
| + | -r-xr-xr-x 1 root bin 2274183 Nov 28 2006 libApiTSM64.so | ||
| + | drwxr-xr-x 2 root bin 4096 Jun 7 15:28 sample | ||
| + | </ | ||
| The TSM client configuration (TDPO) part is in: | The TSM client configuration (TDPO) part is in: | ||
| - | < | + | < |
| + | [[root@oracleserver.domainname /]]# ll / | ||
| + | total 1536 | ||
| + | -rwxrw-rw- 1 root root 67 Mar 21 2007 agent.lic | ||
| + | -rwxrwxr-x 1 root root 29 Jul 13 06:31 dsm.opt | ||
| + | drwxr-xr-x 2 root root 4096 Jun 7 15:29 en_US | ||
| + | -rwxr-xr-x 1 root root 575528 Mar 21 2007 libobk.so | ||
| + | -rwxr-xr-x 1 root root 491744 Mar 21 2007 tdpoconf | ||
| + | -rw-rw---- 1 root dba 279 Jul 13 12:18 tdpoerror.log | ||
| + | -rw-r--r-- 1 root root 48 Jul 13 08:37 TDPO.oracleserver.domainname | ||
| + | -rwxrwxr-- 1 root root 412 Jul 13 06:34 tdpo.opt | ||
| + | -rwxr-xr-x 1 root root 693 Mar 21 2007 tdpo.opt.smp | ||
| + | -rwxr-xr-x 1 root root 693 Jun 7 15:54 tdpo.optyd11072011 | ||
| + | -rwx--x--x 1 root root 442632 Mar 21 2007 tdposync | ||
| + | </ | ||
| TSM Configuration | TSM Configuration | ||
| Line 48: | Line 136: | ||
| Configuration is made of four files: | Configuration is made of four files: | ||
| - | < | + | < |
| + | [[root@oracleserver.domainname /]]# cat / | ||
| + | Servername tsmserver.sgp.st.com | ||
| + | |||
| + | [[root@oracleserver.domainname /]]# cat / | ||
| + | SErvername | ||
| + | | ||
| + | | ||
| + | | ||
| + | NODENAME | ||
| + | PASSWORDACCESS PROMPT | ||
| + | PASSWORDDIR / | ||
| + | SCHEDLOGNAME "/ | ||
| + | SCHEDLOGRETENTION | ||
| + | ERRORLOGNAME | ||
| + | ERRORLOGRETENTION 5 | ||
| + | |||
| + | [[[email protected] /]]# cat / | ||
| + | DSMI_ORC_CONFIG | ||
| + | DSMI_LOG | ||
| + | |||
| + | TDPO_FS | ||
| + | TDPO_NODE | ||
| + | TDPO_OWNER | ||
| + | TDPO_PSWDPATH | ||
| + | |||
| + | TDPO_DATE_FMT | ||
| + | TDPO_NUM_FMT | ||
| + | TDPO_TIME_FMT | ||
| + | |||
| + | TDPO_MGMT_CLASS_2 | ||
| + | TDPO_MGMT_CLASS_3 | ||
| + | TDPO_MGMT_CLASS_4 | ||
| + | </ | ||
| Create the password file to be able to access to TSM server: | Create the password file to be able to access to TSM server: | ||
| - | < | + | < |
| + | [[root@oracleserver.domainname /]]# ./tdpoconf passw | ||
| + | |||
| + | IBM Tivoli Storage Manager for Databases: | ||
| + | Data Protection for Oracle | ||
| + | Version 5, Release 4, Level 1.0 | ||
| + | (C) Copyright IBM Corporation 1997, 2007. All rights reserved. | ||
| + | |||
| + | |||
| + | * ********************************************************** | ||
| + | * IBM Tivoli Storage Manager for Databases Utility | ||
| + | * Password file initialization/ | ||
| + | * ********************************************************** | ||
| + | |||
| + | Please enter current password: | ||
| + | |||
| + | |||
| + | Please enter new password: | ||
| + | |||
| + | |||
| + | Please reenter new password for verification: | ||
| + | |||
| + | |||
| + | ANU0260I Password successfully changed. | ||
| + | </ | ||
| This command create the following password file: | This command create the following password file: | ||
| - | < | + | < |
| + | [[root@eul3001 bin64]]# ll / | ||
| + | -rw-r--r-- 1 root root 48 Jul 13 08:37 / | ||
| + | </ | ||
| Verify all is fine with: | Verify all is fine with: | ||
| - | < | + | < |
| + | [[root@oracleserver.domainname bin64]]# ./tdpoconf SHOWENVironment | ||
| + | |||
| + | IBM Tivoli Storage Manager for Databases: | ||
| + | Data Protection for Oracle | ||
| + | Version 5, Release 4, Level 1.0 | ||
| + | (C) Copyright IBM Corporation 1997, 2007. All rights reserved. | ||
| + | |||
| + | |||
| + | Data Protection for Oracle Information | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | |||
| + | Tivoli Storage Manager Server Information | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | |||
| + | Session Information | ||
| + | Owner Name: | ||
| + | Node Name: oracleserver.domainname | ||
| + | Node Type: TDPO LinuxAMD64 | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | </ | ||
| Oracle Configuration | Oracle Configuration | ||
| Line 66: | Line 247: | ||
| The Oracle configuration is quite simple, you just need to create a symbolic link on TDPO library in all your $ORACLE_HOME/ | The Oracle configuration is quite simple, you just need to create a symbolic link on TDPO library in all your $ORACLE_HOME/ | ||
| - | < | + | < |
| + | [[oracleg@oracleserver.domainname ~]]$ ln -s / | ||
| + | [[oracle@oracleserver.domainname ~]]$ ll $ORACLE_HOME/ | ||
| + | lrwxrwxrwx 1 oraracle dba 45 Jul 13 12:00 / | ||
| + | </ | ||
| Then ensure dba Unix group (better to provide access to DBA group in case you have multiple Oracle accounts on your server) is able to write in all log files you defined in all TSM configuration files and be able to read tdpo.opt configuration file. | Then ensure dba Unix group (better to provide access to DBA group in case you have multiple Oracle accounts on your server) is able to write in all log files you defined in all TSM configuration files and be able to read tdpo.opt configuration file. | ||
| Line 72: | Line 257: | ||
| With Unix commands it gives something like: | With Unix commands it gives something like: | ||
| - | < | + | < |
| + | [[root@oracleserver.domainname /]]# chmod a+r / | ||
| + | [[root@oracleserver.domainname /]]# chown root:dba / | ||
| + | [[[email protected] /]]# chmod g+rw / | ||
| + | [[[email protected] /]]# chown -R root:dba / | ||
| + | [[[email protected] /]]# chmod g+rw / | ||
| + | </ | ||
| All errors I personally encountered were linked to missing rights on either log files (write permission) and read rights on configuration files. Don’t be too generous while giving those rights… | All errors I personally encountered were linked to missing rights on either log files (write permission) and read rights on configuration files. Don’t be too generous while giving those rights… | ||
| Line 78: | Line 269: | ||
| And that’s it ! You are done, you can test all is working with (even before starting RMAN): | And that’s it ! You are done, you can test all is working with (even before starting RMAN): | ||
| - | < | + | < |
| + | [[oracle@oracleserver.domainname admin]]$ sbttest test | ||
| + | The sbt function pointers are loaded from libobk.so library. | ||
| + | -- sbtinit succeeded | ||
| + | Return code -1 from sbtinit, bsercoer = 0, bsercerrno = 0 | ||
| + | Message 0 not found; | ||
| + | </ | ||
| RMAN backup | RMAN backup | ||
| Line 84: | Line 281: | ||
| I’m not entering in all options of powerful RMAN command but below simple script will perform your first tape backup: | I’m not entering in all options of powerful RMAN command but below simple script will perform your first tape backup: | ||
| - | < | + | < |
| + | - !/bin/ksh | ||
| + | - Trapping errors ------------------------------------------------------------- | ||
| + | trap ' | ||
| + | - OS management --------------------------------------------------------------- | ||
| + | OSTYPE=$(uname -s) | ||
| + | case $OSTYPE in | ||
| + | " | ||
| + | alias ll="/ | ||
| + | " | ||
| + | alias ll="/ | ||
| + | alias awk="/ | ||
| + | alias grep="/ | ||
| + | " | ||
| + | alias grep=egrep | ||
| + | alias echo=" | ||
| + | alias ll="ls -l" ;; | ||
| + | esac | ||
| - | =====Troubleshooting===== | + | - Variables ------------------------------------------------------------------- |
| - | This has to work first.<br /> | + | JOB_NAME=$(basename $0) |
| + | TODAY=`date +' | ||
| + | LOG_FILE=/ | ||
| + | |||
| + | - Main Here ------------------------------------------------------------------- | ||
| + | |||
| + | JOB_START=`date +%s` | ||
| + | echo "\ | ||
| + | Starting at `date +' | ||
| + | " | ||
| + | |||
| + | rman << EOF | ||
| + | connect target / | ||
| + | connect catalog rman/ | ||
| + | |||
| + | CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 9 DAYS; | ||
| + | CONFIGURE BACKUP OPTIMIZATION ON; | ||
| + | CONFIGURE CONTROLFILE AUTOBACKUP OFF; | ||
| + | CONFIGURE DEFAULT DEVICE TYPE TO sbt; | ||
| + | CONFIGURE CHANNEL DEVICE TYPE sbt PARMS 'ENV=(TDPO_OPTFILE=/ | ||
| + | CONFIGURE DEVICE TYPE sbt PARALLELISM 1 BACKUP TYPE TO COMPRESSED BACKUPSET; | ||
| + | |||
| + | run | ||
| + | { | ||
| + | allocate channel sbt1 type sbt parms ' | ||
| + | allocate channel sbt2 type sbt parms ' | ||
| + | allocate channel sbt3 type sbt parms ' | ||
| + | allocate channel sbt4 type sbt parms ' | ||
| + | |||
| + | backup as compressed backupset database include current controlfile tag ' | ||
| + | backup as compressed backupset archivelog all delete all input tag ' | ||
| + | |||
| + | release channel sbt1; | ||
| + | release channel sbt2; | ||
| + | release channel sbt3; | ||
| + | release channel sbt4; | ||
| + | } | ||
| + | EOF | ||
| + | |||
| + | JOB_END=`date +%s` | ||
| + | echo "\ | ||
| + | Ending at `date +' | ||
| + | echo "\ | ||
| + | Completed in $((($JOB_END - $JOB_START)/ | ||
| + | echo "\ | ||
| + | Normal Exit" | ||
| + | </ | ||
| + | |||
| + | ==== Troubleshooting | ||
| + | This has to work first.\\ | ||
| If this doesn' | If this doesn' | ||
| - | < | + | < |
| + | run {\t | ||
| + | | ||
| + | } | ||
| + | </ | ||
| - | ====**Problem: | + | === **Problem: |
| - | < | + | < |
| + | RMAN-00571: =========================================================== | ||
| + | RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== | ||
| + | RMAN-00571: =========================================================== | ||
| + | RMAN-03009: failure of allocate command on c1 channel at 06/08/2014 11:14:54 | ||
| + | ORA-19554: error allocating device, device type: SBT_TAPE, device name: | ||
| + | ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer | ||
| + | SVR4 Error: 2534: Unknown system error | ||
| + | Additional information: | ||
| + | ORA-19511: Error received from media manager layer, error text: | ||
| + | SBT error = 7011, errno = 2534, sbtopen: system error | ||
| + | </ | ||
| **Solution: | **Solution: | ||
| - | < | + | < |
| + | Node was created on the wrong TSM server | ||
| + | Probably only see this message if database is in one datacentre but backed up to another one. | ||
| + | </ | ||
| - | ====**Problem: | + | === **Problem: |
| - | < | + | < |
| + | Starting backup at 06-JUN-2014 15:43:34 | ||
| + | current log archived | ||
| + | RMAN-00571: =========================================================== | ||
| + | RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== | ||
| + | RMAN-00571: =========================================================== | ||
| + | RMAN-03002: failure of backup command at 06/06/2014 15:43:36 | ||
| + | ORA-19554: error allocating device, device type: SBT_TAPE, device name: | ||
| + | ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer | ||
| + | SVR4 Error: 2534: Unknown system error | ||
| + | Additional information: | ||
| + | ORA-19511: Error received from media manager layer, error text: | ||
| + | SBT error = 7011, errno = 2534, sbtopen: system error | ||
| + | |||
| + | RMAN> | ||
| + | </ | ||
| **Solution: | **Solution: | ||
| - | < | + | < |
| + | * If it's a load balancing cluster, tdpo needs to be installed and configured on both sides. | ||
| + | dsm.opt, tdpo.opt, dsm.sys and TSM.PWD all have to be in the same directories on both sides. | ||
| - | ====**Problem: | + | * check that $ORACLE_HOME/ |
| - | < | + | |
| + | * check the backup_rman_functions.ini has the correct information regarding location of opt files. (specific to us) | ||
| + | </ | ||
| + | |||
| + | === **Problem: | ||
| + | < | ||
| + | RMAN-00571: =========================================================== | ||
| + | RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== | ||
| + | RMAN-00571: =========================================================== | ||
| + | RMAN-03009: failure of allocate command on c1 channel at 12/18/2012 18:12:29 | ||
| + | ORA-19554: error allocating device, device type: SBT_TAPE, device name: | ||
| + | ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer | ||
| + | IBM AIX RISC System/6000 Error: 406: Unknown system error | ||
| + | Additional information: | ||
| + | ORA-19511: Error received from media manager layer, error text: | ||
| + | SBT error = 7011, errno = 406, sbtopen: system error | ||
| + | </ | ||
| **Solution: | **Solution: | ||
| - | < | + | < |
| - | ====**Problem: | + | cd /etc/tsm |
| - | < | + | chmod 644 dsm.sys |
| - | **Solution: | + | </ |
| - | Configuration error!<br /> | + | === **Problem: |
| - | Check the dsm.opt, tdpo.opt, inclexcl.lst and dsm.sys files. Compare them with a system that works.<br /> | + | < |
| - | Found my error in dsm.sys:<br /> | + | RMAN-00571: =========================================================== |
| - | Name of the tsm server was wrong and I removed the line " | + | RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== |
| - | Check the parameter DSMI_LOG in tdpo.opt file<br /> | + | RMAN-00571: =========================================================== |
| - | Make sure that the directory it points to (and its files) is writeable by the user doing the work<br /> | + | RMAN-03009: failure of allocate command on t1 channel at 06/07/2014 17:09:58 |
| + | ORA-19554: error allocating device, device type: SBT_TAPE, device name: | ||
| + | ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer | ||
| + | SVR4 Error: 400: Unknown system error | ||
| + | Additional information: | ||
| + | ORA-19511: Error received from media manager layer, error text: | ||
| + | SBT error = 7011, errno = 400, sbtopen: system error | ||
| + | </ | ||
| + | **Solution: | ||
| + | Configuration error!\\ | ||
| + | Check the dsm.opt, tdpo.opt, inclexcl.lst and dsm.sys files. Compare them with a system that works.\\ | ||
| + | Found my error in dsm.sys:\\ | ||
| + | Name of the tsm server was wrong and I removed the line " | ||
| + | Check the parameter DSMI_LOG in tdpo.opt file\\ | ||
| + | Make sure that the directory it points to (and its files) is writeable by the user doing the work\\ | ||
| Remember TSM comments are * not # ! | Remember TSM comments are * not # ! | ||
| - | < | + | < |
| + | chown oraibm:dba / | ||
| + | chmod 777 / | ||
| + | </ | ||
| - | ====**Problem: | + | === **Problem: |
| - | < | + | < |
| + | - RMAN-00571: =========================================================== | ||
| + | - RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== | ||
| + | - RMAN-00571: =========================================================== | ||
| + | - RMAN-03009: failure of allocate command on c1 channel at 12/17/2012 14:58:05 | ||
| + | - ORA-19554: error allocating device, device type: SBT_TAPE, device name: | ||
| + | - ORA-27211: Failed to load Media Management Library | ||
| + | - Additional information: | ||
| + | </ | ||
| **Solution: | **Solution: | ||
| - | < | + | < |
| - | ====**Problem: | + | cd / |
| - | < | + | ls -ltr |
| + | chmod 755 libobk.a | ||
| + | </ | ||
| + | === **Problem: | ||
| + | < | ||
| + | - RMAN-00571: =========================================================== | ||
| + | - RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== | ||
| + | - RMAN-00571: =========================================================== | ||
| + | - RMAN-03009: failure of allocate command on c1 channel at 12/17/2012 15:34:08 | ||
| + | - ORA-19554: error allocating device, device type: SBT_TAPE, device name: | ||
| + | - ORA-27000: skgfqsbi: failed to initialize storage subsystem (SBT) layer | ||
| + | - IBM AIX RISC System/6000 Error: 106: Reserved errno was encountered | ||
| + | - Additional information: | ||
| + | - ORA-19511: Error received from media manager layer, error text: | ||
| + | - SBT error = 7011, errno = 106, sbtopen: system error | ||
| + | </ | ||
| **Solution: | **Solution: | ||
| - | < | + | < |
| + | cd / | ||
| + | chown oraibm: | ||
| + | chmod ug+rwx dsmerror.log | ||
| + | </ | ||
| + | |||
| + | ==== Other ==== | ||
| + | * Check results from: | ||
| + | < | ||
| + | tdpoconf showenv -tdpo_optfile=/ | ||
| + | </ | ||
| + | * Check the logs you'll find in directory pointed by the parameter DSMI_LOG in your tdpo confirguration file. The file is tdpoerror.log. There is also a trace file generated in user_dump_dest. | ||
| + | * Check you have a file agent.lic in opt/ | ||
| + | |||
| + | ==== References ==== | ||
| - | =====Other===== | + | * Installation de Tivoli Data Protection pour Oracle by albanlepunk |
| - | * Check results from: | + | * |
| - | < | + | |
| - | * Check the logs you'll find in directory pointed by the parameter DSMI_LOG in your tdpo confirguration file. The file is tdpoerror.log. There is also a trace file generated in user_dump_dest. | + | * |
| - | * Check you have a file agent.lic in opt/tivoli/tsm/client/oracle/ | + | |
| - | =====References===== | ||
| - | * Installation de Tivoli Data Protection pour Oracle by albanlepunk | ||
| - | * Tivoli Storage Manager client node lacks authority to delete backup copies | ||
| - | * Oracle RMAN 11g Backup and Recovery | ||
| - | * [[http:// | ||
tivoli_data_protection_for_oracle_tdpo.1544273361.txt.gz · Last modified: 2018/12/08 12:49 by 0.0.0.0