Oracle

Oracle Server is a fully-functioning Relational Database Management System (RDBMS). UPSTREAM supports the following ways of backing it up.

• UPSTREAM can operate as an Oracle Media Manager Library product that allows it to be used with Oracle Recovery Manager. See Section “Oracle Media Manager Support (RMAN)”.
  

• Beginning with UPSTREAM Client Version 4.1, there are two methods available to perform Oracle RMAN interface backups:
  

• 
  
  • The backward compatible method using the UPSTREAM Client software to communicate with the UPSTREAM Storage Server. This allows existing customers to upgrade to v4.1 without changes. This method will be referred to as the “RMAN UPSTREAM Client” method.
    

• 
  
  • A new method in which the RMAN interface communicates directly to the UPSTREAM Storage Server, bypassing the UPSTREAM Client. This provides customers with enhanced performance but does require RMAN scripting changes to be performed. This method is referred to as the “RMAN UPSTREAM Clientless” method.
    

Both methods produce compatible output that can be utilized by the other method during recovery operations going forward and particularly if a fall-back should be necessary.

Oracle RMAN Interface

1. The Oracle RMAN configuration Interface in the Web Portal is used to dynamically configure the supporting files and parameters.
2. The Oracle DBA constructs/alters their existing backup script. UPSTREAM is defined as an Oracle Media Manager. The DBA also configures RMAN/Oracle and possibly CRON to decide when the backups will run.
3. The RMAN backup script is invoked. If there is an existing process to do this already implemented, this will work fine.
4. RMAN receives the request and it performs its normal processing. At this point the number of RMAN configured channels is used to begin many parallel connections through to the storage server. Each channel will record its data on its own media.
5. Once the request has begun processing, a pipe connection is made to the UPSTREAM libobk.so interface module and Oracle backup data begins to flow.
6. The libobk.so module reformats/sends that data to the UPSTREAM Client on the local Linux System. It establishes a TCP/IP connection to the storage server and reformats/transmits the data.
7. The z⁄OS storage server receives this data, reformats it for storage and places it on the backup media. At the appropriate time, it updates the UPSTREAM database, z⁄OS user catalog, and tape management database.

The z⁄OS Storage Server receives this data, reformats it for storage and places it on the backup media. At the appropriate time, it updates the UPSTREAM database, z⁄OS user catalog, and tape management database.

Oracle RMAN UPSTREAM Interface Installation

RMAN for Windows Configuration

RMAN for UNIX Configuration

RMAN Operations for UPSTREAM

Oracle Media Manager Support (RMAN)#

UPSTREAM can operate as an Oracle Media Manager Library product that allows it to be used with Oracle Recovery Manager.

The Oracle Recovery Manager is an full-featured backup facility. Through its use, you can use UPSTREAM to perform full, incremental, and tablespace backups of databases, tablespaces, and datafiles. Some of the features supported include backup sets, image copies, stored scripts, Recovery Manager reports, tags, integrity checking, and more. All the powerful features of recovery manager are now available to UPSTREAM users under both local and Storage Server control.

Because the Oracle Recovery Manager is so complex, we recommend that you become familiar with its use before referencing this documentation. See the Oracle Backup and Recovery Guide for a complete description of the Recovery Manager. Since backup and restore operations are controlled there and since UPSTREAM is merely a Media Manager Library the description of backups and restores is left to that guide.

Installation

Before beginning installation of UPSTREAM media manager software, make sure that you are familiar with Recovery Manager basic backup/recovery techniques. Recovery Manager is distributed with built in capabilities of doing disk backups. Prepare and run a test set of small backup and recovery jobs to verify that all your scripts work correctly.

Also make sure that your UPSTREAM is installed and properly configured, and you can run successful backups and restores.

Windows Installation

The UPSTREAM interface to Recovery Manager is the dynamic link library orasbt.dll. It is normally copied into your UPSTREAM directory during the UPSTREAM install together with usorasbt.cfg.sample sample configuration files and usorasbt.dat.sample sample UPSTREAM parameter file.

To install the UPSTREAM Media Manager library:

• Stop the Oracle service for your instance. Oracle opens this DLL during Oracle service start up and keeps it open until you stop Oracle. Go into the Control Panel, select the Services applet, highlight the OracleService{instance} for each database instance you have installed and press the Stop button.
  
• Rename the current orasbt.dll. Oracle has placed the default Media Manager Library into your Windows system directory (%SystemRoot%\system32). Use a command line rename command or Explorer to rename the file to some other name (such as orasbt.default) in case you wish to uninstall UPSTREAM at some later time.
  
• Copy orasbt.dll from the UPSTREAM directory to your Windows system directory.
  
• You can now restart the Oracle services using the Services applet in the Control Panel.
  

UNIX Installation

On UNIX systems three files are included in the UPSTREAM distribution to support interface to Oracle Recovery Manager: shared library libobk (extension differs from system to system), usorasbt.cfg.sample sample configuration file, and usorasbt.dat.sample sample UPSTREAM parameter file.

Go to $ORACLE_HOME/lib directory and create a link to libobk shared library in your UPSTREAM directory (substitute if it exists):

• 132_List1_Bullet_1102493 • libobk.so for SUN Solaris and Linux
  
• 132_List1_Bullet_1102494 • libobk.a for AIX
  
• 132_List1_Bullet_1102495 • libobk.sl for HP-UX (make sure it has execute permissions set!)
  

For example:

{{id name="Oracle-132_JCL_1063950"/}}

{{id name="Oracle-1063950"/}}

ln -s /opt/fdrupstream/libobk.so /ora01/oracle/lib/libobk.so\\The next time you start Oracle Recovery Manager (RMAN), UPSTREAM Media Manager is activated.

If you are getting error messages referencing libobk or shr.o, double-check the symbolic link libobk.* created, existence of libobk shared library in your UPSTREAM directory, and then contact BMC Support.

Configuring UPSTREAM for Recovery Manager

Starting with version of 2.0.6.0 of usorasbt UPSTREAM operates in multi-user mode; one or more instances of UPSTREAM running in parallel accepting backup/restore requests from different sources (like Storage Server initiates, database agents, etc.). Using this mode allows you to take full advantage of RMAN multi-channel backups.

To be able to use UPSTREAM as your Oracle backup media management software you have to create/update a configuration file that points to the main UPSTREAM instance (daemon or Windows service) and sets usorasbt operational parameters. A sample configuration file usorasbt.cfg.sample is provided by installation in the UPSTREAM directory.

The usorasbt configuration file consists of the following:

• 132_List1_Bullet_1063978 • PARAMETER /opt/fdrupstream/usorasbt.dat – Required. The template parameter file (see further note).
  
• 132_List1_Bullet_1063979 • PROFILE ORCL – Optional, but strongly recommended. If it is not specified UPSTREAM uses the Oracle instance name as an UPSTREAM backup profile. If you want to use a different backup profile name, specify it here, and make sure that it is a unique name. You must configure this backup profile as a “generic prefix”, and it must be no more than 7 characters long. This value can get overwritten by USBKPROFILE environment variable.
  
• 132_List1_Bullet_1063980 • USINPORT 1972 – Required. The port number the running UPSTREAM daemon (UNIX) or service (Windows) is listening on (INPORT parameter of the UPSTREAM configuration file in use). This parameter indicates that UPSTREAM will be used in a MULTI-user mode. You have to have an UPSTREAM daemon (UNIX) or service (Windows) running on this same machine.
  
• 132_List1_Bullet_1063981 • WORKPATH /opt/usorasbt – Required. The full path to the directory where Oracle users have full read/write access.
  
• 132_List1_Bullet_1063982 • LOGFILE /home/oracle/usorasbt.log – Optional, but strongly recommended. Specifies the name of the log file where all database backup/restore activities using UPSTREAM are recorded. Should be placed in the directory with read/write access for Oracle users. If not specified, the log is not created.
  
• 132_List1_Bullet_1063983 • CHANNELS 36 – Optional. The maximum (and the default) number is 36. RMAN allows you to specify a number of backup/restore channels to use in parallel to improve the performance. Starting with 1.1.0.2 version of UPSTREAM MMAPI you can take advantage of this RMAN feature and am able to run parallel UPSTREAM backups/restores if requested by RMAN. You specify the number of parallel RMAN sessions (channels) in the RMAN script. Each UPSTREAM backup session performs a backup using a backup profile name generated by adding a unique one-symbol session identifier to the original backup profile name. The total number of UPSTREAM backups (that is the sum of all RMAN backup channels) running in parallel and using the same UPSTREAM backup profile is limited by this parameter. The UPSTREAM backup profile name must be no longer than 7 characters and configured as a “generic prefix”.
  
• 132_List1_Bullet_1114509 • STARTCHANNEL 0 - This parameter specifies the initial character from which the sequence of unique one-symbol identifiers are appended to the backup profile prefix. The default is 0, but in some cases you may want to start with a letter (like A).
  
• 132_List1_Bullet_1063984 • USERNAME ORACLE – Optional. The name of the registered UPSTREAM user if required by security settings.
  
• 132_List1_Bullet_1063985 • NOTRACE – Oracle has a default setting that enables tracing of the MMAPI layer. The trace file name is sbtio.log and it may appear in different locations under $ORACLE_HOME depending on the configuration settings. After you successfully finish your evaluation we recommend adding this parameter to suppress writing the trace entries. It is recommended to know where your sbtio.log file resides and clean (remove) it from time to time to recover the disk space during and after the evaluation process.
  
• 132_List1_Bullet_1063990 • USIPADDR specifies the IP address of the local UPSTREAM. Specify this address here ONLY if you have multiple network adapters and you specified Local TCP/IP Receive Address in Advanced Configuration (TCPINADAPTER parameter in upstream.cfg file).
  
• 132_List1_Bullet_1063991 • ALIASFILE /opt/fdrupstream/alias.ora – Optional. If you decided not to use PROFILE and your database instance name is not valid for an UPSTREAM backup profile name, use an alias for your backup profile name. Create an ASCII file with one or more lines. Each line contains a pair of names separated by a space; database instance name, and its alias, that is used as a backup profile name for this database instance.
  

Most users place the usorasbt.cfg file in the UPSTREAM directory and then use environment variable USORASBTCFG (see below) to point to it from Recovery Manager. Make sure that usorasbt.cfg file is accessible for read by the Oracle owner (user account that installed Oracle database).

If you decide to use the same usorasbt.cfg for backups of multiple databases, make sure that you either have a unique profile for every database (by having USBKPROFILE in the RMAN channel specification) or the names of backup pieces for those databases are unique and identifiable (by using RMAN FORMAT parameter).

You must create a template parameter file for UPSTREAM to use when backing up Oracle. You can create it by starting UPSTREAM, going into the backup dialog, specifying the desired options, and saving the parameter file under the name you specified in the usorasbt.cfg configuration file PARAMETER. Sample parameter file usorasbt.dat.sample is provided during installation. Even though some settings in this file is overwritten by usorasbt, you should specify:

• 132_List1_Bullet_1063998 • Storage Type for backups (STORAGETYPE parameter). If you perform disk backups and working with Oracle 8.0, you have to go to ‘More…’ screen and specify a DASDOVERRIDE parameter. Oracle 8.0 utilities do not always provide us with the size of the backup to be performed, so you have to specify the number of bytes in the biggest backup set you expect. Starting with Oracle 8.1.7 RMAN provides us with the valid backup size.
  
• 132_List1_Bullet_1063999 • Compression Level in “More…” screen (COMPRESSLEVEL parameter).
  
• 132_List1_Bullet_1102584 • Local Backup parameters if you are using UPSTREAM SOS. If you are running in a multi-user mode and want to take full advantage of SOS Local Backup (specified LOCALBACKUP 2) and multiple backup channels, so that every one of RMAN backups running in parallel uses it’s own local backup disk, follow these recommendations. Prepare a number of local backup disks with volume names following the pattern: ccccc0, ccccc1, …, cccccN, where “ccccc” is a 5-character volume prefix followed by a number starting with 0 (see UPSTREAM Setup chapter for details). You have to prepare as many such volumes as many backup channels you are planning to use (or the limit you set in CHANNELS parameter in usorasbt.cfg file). In the usora.dat file (or any other template parameter file specified in PARAMETER parameter usorasbt.cfg file) specify (together with other local backup parameters, like LOCALBACKUP etc):
  

{{id name="Oracle-132_JCL_1102588"/}}

{{id name="Oracle-1102588"/}}

LOCALBACKUPDIR ccccc%\\where “ccccc” is the volume prefix above. For each backup channel this name is resolved to the appropriate valid volume name to use in SOS Local Backup.

There are 2 new options you have for LOCALBACKUPDIR when using UPSTREAM SOS:

• 132_List1_Bullet_1102597 • For UPSTREAM to allocate the first encountered SOS Local Disk (even if it is in use by some other UPSTREAM) specify:
  
• 132_List1_Bullet_1102601 • LOCALBACKUPDIR *
  
• 132_List1_Bullet_1102605 • For UPSTREAM to allocate the first SOS Local Disk that is not in use by any other UPSTREAM specify:
  

{{id name="Oracle-132_JCL_1102609"/}}

{{id name="Oracle-1102609"/}}

LOCALBACKUPDIR !\\Older versions of Oracle (before version 8.1) do not supply us with the size of the backup, so you have to set DASDOVERRIDE parameter (even for tape backups!) to the number of bytes you want to allocate on the SOS local disk for the backup.

Parameters that are automatically overridden by the UPSTREAM Recovery Manager facility includes:

Backup Profile

• 
  
  • =====

The Oracle instance name is used. Recovery Manager determines when to delete backups and they are deleted automatically via UPSTREAM so we recommend that in the Storage Server configuration for your Backup Profile you specify a retention period that is quite long so as not to defeat the Recovery Manager retention algorithms. You may need to configure a Backup Profile on the Storage Server by this name if the GLOBAL profile does not meet your needs.

File specifications

• 
  
  • =====

UPSTREAM generates the file names to be used.

Backup type

• 
  
  • =====

You do not need to specify separate configuration files for full backups and incremental backups as these are set as appropriate.

Restart

• 
  
  • =====

Restart is not supported.

Using Recovery Manager with UPSTREAM

You usually specify the UPSTREAM backup profile you want to use by including PROFILE configuration parameter in usorasbt.cfg file, or by specifying USBKPROFILE environment variable in the script that invokes RMAN (overwrites value in usorasbt.cfg). You have to configure this backup profile before starting production backups, otherwise they use your generic profile settings.

We must configure UPSTREAM backup profiles for Oracle backups as a “generic prefix” profiles, so you can have the advantage of RMAN multi-channel operations. Remember that the backup prefix MUST NOT be more than 7 characters long allowing at least 1 character for the channel number.

It is recommended (especially for multi-channel backups) that in the UPSTREAM backup profile configuration to specify DSN prefix special way; its last qualifier matches the profile name. In this case the DSN prefix created is replaced with the profile name used for the backup ensuring the uniqueness of the file name.

It is not recommended to remove UPSTREAM backups created by RMAN directly using UPSTREAM (bypassing RMAN). RMAN keeps internal track of its backups (either in its own database, or using the control file, depending on how you configured it), and may rely on those backups in the recovery process. To perform a clean-up of the backups you do not need, use the RMAN “change … delete” command (see “Keeping backups” section in the Oracle “Backup and Recovery Guide, Recovery Manager Scenarios”).

When RMAN deletes a backup from its backup list, it send the request to UPSTREAM to delete the associated backup on the Storage Server side.

If, after you deleted all the RMAN backups taken before a particular date, there are still some UPSTREAM backups for the same backup profile that were taken before that date, you can delete those UPSTREAM backups. Most likely it was a result of some operational errors. Please, note those backups, and report this situation to BMC Support if you think that it was a software problem.

RMAN has a special command, CROSSCHECK, that allows you to verify that all the backups RMAN keeps in its backup database exist in the UPSTREAM backup repository, We advise you to use this RMAN facility regularly to make sure that there are no problems with data accessibility when the recovery is needed.

There is a set of environment variables that helps you to control UPSTREAM backup process:

USORASBTCFG

The full name of the usorasbt configuration file if not in the UPSTREAMPATH directory.

USPATH

Specifies the directory where UPSTREAM software (including usorasbt.cfg file) is installed.

NEWTAPE = YES | NO | FULL

Allows you to control the creation of new tapes (see the NEWTAPE discussion below).

USBKPROFILE

The UPSTREAM backup profile name to overwrite the value that is set by PROFILE parameter in the usorasbt configuration file (or to set it if PROFILE was not defined). Must be no more than 7 characters long and configured as a “generic prefix”.

USORAUSWAITTO

Limit the time (in seconds) usorasbt waits during backup for an UPSTREAM backup channel to become available. You should only need to increase this value if the system is very busy or if you have specified a number of channels which is greater than can be started quickly. The default is 20 seconds.

CROSSCHECK

Optimizes backup inquiries during RMAN CROSSCHECK operations by retrieving the list of RMAN backups from the host system only once per session. Use this only during your RMAN maintenance operation when there is no other backup in progress.

USORAPROFILEWAITTO

Limits the time (in seconds) usorasbt waits during restore until the required profile channel becomes available. Unlimited wait is the default.

DAYSOLD

Defines the number of days to keep in usorasbt.log file, there is no clean up if not specified.

If you do not specify neither USPATH nor USORASBTCFG, usorasbt tries to find the usorasbt.cfg file in the default UPSTREAM directory (C:\Program Files\Innovation Data Processing\UPSTREAM for Windows and /usr/lpp/fdrupstream or /opt/fdrupstream on UNIX).

To take the full control over the creation of new tapes using the NEWTAPE environment variable you must configure your backup profile in the Storage Server in the following way:

• 132_List1_Bullet_1064069 • The backup profile must be no more than 7 characters. We recommend explicitly specifying it in the usorasbt.cfg file by using the PROFILE parameter.
  
• 132_List1_Bullet_1064070 • PREFIX=YES if using the Client Profile Configuration, check Profile a Generic Prefix.
  
• 132_List1_Bullet_1064071 • NEWTAPEI = NO if using the Client Profile Configuration, do not check New tape for Incr. Merge.
  
• 132_List1_Bullet_1064076 • NEWTAPEF = YES if using the Client Profile Configuration, check New tape for Full Merge.
  
• 132_List1_Bullet_1064077 • MERGE=YES if using the Client Profile Configuration, check Merge backups allowed.
  
• 132_List1_Bullet_1064078 • DASD=YES if using the Client Profile Configuration, check Seq. DASD Backups Allowed. This is required even if you do not use disk backups.
  
• 132_List1_Bullet_1064079 • TAPE=YES if using the Client Profile Configuration, check Seq. Tape Backups Allowed. This is required even if you do not use tape backups.
  

We strongly recommend that you specify the last file name qualifier in the DSN prefix (for both tape and DASD) to match the name of the backup prefix (this ensures that all the backup file names created are unique). For example:

• 132_List1_Bullet_1064081 • Backup profile prefix: ORCLBKP
  
• 132_List1_Bullet_1064082 • DSN prefix: MY.BACKUP.ORCLBKP
  

This results in backups of:

• 132_List1_Bullet_1064085 • Channel 1: backup profile is ORCLBKP0, DSN is MY.BACKUP.ORCLBKP0…

• 132_List1_Bullet_1064086 • Channel 2: profile is ORCLBKP1, DSN is MY.BACKUP.ORCLBKP1…

• 132_List1_Bullet_1064087 • and so on …
  

When your UPSTREAM backup profile is properly configured, you can easily control the creation of new tapes for your backups from RMAN scripts using ALLOCATE CHANNEL command:

• 132_List1_Bullet_1068183 • Specify NEWTAPE=YES for the channel(s) in the RMAN script if you want this backup to start on a new tape. All the backup files created during this backup (more than one if you have FILESPERSET, or more backup commands before you release the channel) go to the same newly created tape.
  
• 132_List1_Bullet_1064093 • Specify NEWTAPE=NO (or omit NEWTAPE) if you want all the backup files in the set to append to the previous tape.
  
• 132_List1_Bullet_1064094 • Specify NEWTAPE=FULL if you intend to vault RMAN backups. In this case an UPSTREAM dummy first-time-full backup is created before the RMAN backup. This starts the RMAN backup on a new tape (like NEWTAPE=YES), but also this full backup serves as a stop point for vaulting procedures. These dummy backups get deleted (all but the latest one(s)) as RMAN deletes its own backups during maintenance.
  

Recommendation: Specify HOLDTAPE Y in the template parameter file (the file specified in PARAMETER in usorasbt.cfg) if you expect to have more than one backup file created during RMAN backup. It prevents tapes from being unloaded between backups.

When you create Recovery Manager scripts, you must specify the following parameters in channel allocation:

• 132_List1_Bullet_1064099 • type ‘sbt_tape’ This instructs Recovery Manager to use media manager software installed (i.e. UPSTREAM), not internal disk backup support.
  
• 132_List1_Bullet_1068589 • PARMS=”ENV=(USORASBTCFG=<full path to usorasbt configuration file> [,env-name=env-value])”
  

or

{{id name="Oracle-132_JCL_1068591"/}}

{{id name="Oracle-1068591"/}}

PARMS=”ENV=(USPATH=<UPSTREAM directory>[,env-name=env-value])”\\For example (all in one line, replacing ellipses with any optional parameters):

Pre-Configuring the Backup Channel

You pre-configure the backup channel (for example):

{{id name="Oracle-132_JCL_1068611"/}}

{{id name="Oracle-1068611"/}}

CONFIGURE CHANNEL DEVICE TYPE ussbt PARMS=’ENV=(USORASBTCFG=/opt/fdrupstream/usorasbt.cfg)’\\Note that the above must be on one line. When you specify your backups or restores use in your scripts:

{{id name="Oracle-132_JCL_1068615"/}}

{{id name="Oracle-1068615"/}}

ALLOCATE CHANNEL ch1 TYPE ussbt;\\This is an example of a simple RMAN script that uses the CONFIGURE CHANNEL command from above:

We strongly recommend that you define LOGFILE configuration parameter, and that is the place to check the backup/restore results if RMAN returns an error. For a more detailed explanation of errors occurred during the backup process check UPSTREAM log (LOGFILE parameter of the UPSTREAM configuration file).

usorasbt caches backup information to improve performance, especially for maintenance procedures. We recommend that you run all your maintenance jobs (cross-checks, backup removing, etc.) through one channel, and not in parallel with other backup/recovery operations.

Earlier versions of RMAN don’t always provide usorasbt with the size of the upcoming backup, that’s why UPSTREAM inquire version reports may not show the correct size of the MMAPI Oracle backups.

There is a possibility that during a multi-channel restore operation RMAN requests data from one backup channel (UPSTREAM backup profile) through more than one restore channel. If the backup data was on tape usorasbt postpones all the competing restore channels but one to serialize restores from one backup channel. The wait for the backup channel (UPSTREAM backup profile) is unlimited by default. By specifying the USORAPROFILEWAITTO environment variable you can limit this wait period. Be aware that if the USORAPROFILEWAITTO limit expires before the channel becomes available, the RMAN restore fails.

Initiating UPSTREAM RMAN Backups from the UPSTREAM Storage Server

After you created and tested your RMAN backup scripts, you may want to set it up so that these scripts are initiated from the Storage Server side.

This is a sample z⁄OS mainframe job to start full.sh script using UPSTREAM Run Job facility:

{{id name="Oracle-132_JCL_1068672"/}}

{{id name="Oracle-1068672"/}}

~/~/AGKTST2 JOB (ACCOUNT),’NAME’,CLASS=N,NOTIFY=AGK
~/~/TSTOS201 EXEC PGM=USTBATCH,PARM=’NOTIMER’
~/~/STEPLIB DD DISP=SHR,DSN=USTSYS.TESTLIB
~/~/SYSUDUMP DD SYSOUT=*
~/~/USTLOG DD SYSOUT=*
~/~/USTPARM DD *
APPLPREF=UPSTR
USAPPL=UPSTREAM
LOGMODE=USTMODE
MAXRETRY=0
CONV=WAIT
TCPTARG=192.168.150.104,1973
ACTION 5 * RUN A JOB
JOBOPTIONS 35 * WAIT FOR THE JOB TO TERMINATE
FILES /home/oracle/backups/full.sh
ATTENDED N
ENDPARM *
~/~/\\Keep in mind that the script (full.sh in this example) runs under superuser (root) account. Depending on your Oracle setup and configuration, you may need to include root user in the dba group and set some environment variables (like ORACLE_SID and ORACLE_HOME) in the script before invoking RMAN itself:

{{id name="Oracle-132_JCL_1068692"/}}

{{id name="Oracle-1068692"/}}

ORACLE_SID=orcl817
export ORACLE_SID
ORACLE_HOME=/ora01/oracle/8.1.7
export ORACLE_HOME
RMAN target …\\If you have a RMAN script prepared for running under Oracle account already (for example: script is full.sh in /home/oracle directory, and the user name is oracle), you can create another script to be specified in the UPSTREAM batch file in FILES spec that starts the RMAN script in the right environment (consists of one line only):

{{id name="Oracle-132_JCL_1068700"/}}

{{id name="Oracle-1068700"/}}

su - oracle –c /home/oracle/full.sh\\If your UPSTREAM on the Storage Server side operates with the SECLEVEL higher than 0 you can take advantage of the prevalidated security option available in version 3.2.2 and higher. When starting RMAN backups through the Storage Server initiated scripts with CONV=WAIT specified, set in the USTBATCH job:

{{id name="Oracle-132_JCL_1068704"/}}

{{id name="Oracle-1068704"/}}

USERID &JOB
PASSWORD &JOB\\In the template parameter file (the file specified under PARAMETER in usorasbt.cfg) also set:

{{id name="Oracle-132_JCL_1068709"/}}

{{id name="Oracle-1068709"/}}

USERID &JOB
PASSWORD &JOB\\These settings allow the instance of UPSTREAM started on behalf of RMAN to use the same security attributes as the USTBATCH session that started it.

If you are not able to use &JOB, or are submitting a backup from the Oracle side (with SECLEVEL higher that 0 on the Storage Server), then you have to embed your USERNAME and PASSWORD in the template parameter file. You can use USMODIFY utility supplied with Client to accomplish that.

Backup and Recovery Considerations

As RMAN manages backup and recovery operations, it requires a place to store necessary information about the database and the backups taken. RMAN always stores this information in the target database control file. You can also store RMAN metadata in a recovery catalog schema contained in a separate database. The recovery catalog schema must be stored in a database other than the target database. RMAN periodically migrates information from the control file to the recovery catalog.

The recovery catalog is maintained solely by RMAN; the target database never accesses it directly. RMAN propagates information about the database structure, archived redo logs, backup sets, and datafile copies into the recovery catalog from the target database’s control file. Here are some recommendations on how to maintain RMAN backup repository.

• 132_List1_Bullet_1068738 • It is strongly recommended that you include the Oracle control file in each and every RMAN backup. Pre-configure RMAN with CONFIGURE CONTROLFILE AUTOBACKUP ON (Oracle9i) or have in every backup script command INCLUDE CURRENT CONTROL FILE.
  
• 132_List1_Bullet_1068739 • Keep all the relevant RMAN data in the control file by specifying a long enough CONTROL_FILE_RECORD_KEEP_TIME parameter in the initsid file. This is absolutely required if you work without recovery catalog, and it allows you to proceed with full database recovery (disaster or off-site) without restoring the recovery database.
  
• 132_List1_Bullet_1068740 • RMAN can create message logs if you startup RMAN with the MESSAGELOG parameter. These logs may come in handy in case of the disaster recovery if you have to help RMAN to find the right backup pieces and to set your DBID. Keeping message logs requires some management on your part in cleaning up the old ones.
  
• 132_List1_Bullet_1068741 • Make sure you perform the required maintenance on the recovery catalog (register, re-synchronize, reset the target database, etc.). RMAN does not maintain the recovery catalog automatically for you!
  
• 132_List1_Bullet_1068742 • Make backups of the recovery catalog itself: you can use RMAN or shutdown the recovery database (while RMAN is not active) and proceed with offline backups.
  
• 132_List1_Bullet_1077081 • Do not forget to backup Oracle software, configuration, initialization parameter and password files and Oracle Net files (usually the whole $ORACLE_HOME directory except oradata subdirectory) at the file level (using regular UPSTREAM file level backups). Make sure that the control file(s) are NOT included in the regular file backups. In case of a disaster recovery, you MUST restore the control file from your RMAN backups because the control file backed up during regular file backup can be outdated or in an inconsistent state and prevents database instance from starting.
  

Advanced Backup Scenarios

The method described above will allow UPSTREAM to work with Oracle and produce complete backups. However, if you’d like to optimize the performance of your backups we recommend considering one of these sample approaches:

1. 132_List1_Num_First_1102647 1. Take regular RMAN backups of datafiles and archived redo logs according to your schedule. If you have EMC Symmetrix Storage Subsystem, you can take advantage of UPSTREAM SOS to speed up your backups (see UPSTREAM SOS section of this manual). Apply recommendations from “Identify the Local Backup Disk” in Section to the template parameter file specified in usorasbt.cfg in the PARAMETER parameter (usorasbt.dat is the default).
   
   1. 132_List1_Num_Next_1102654 2. If you have Oracle database files installed on EMC2 Symmetrix Storage Subsystem, you can use FDRSOS backup solution. To perform FDRSOS backups of your Oracle database you have to shut it down for the duration of the backup. If this is not an option, try to take advantage of a TimeFinder option of EMC2 Symmetrix Storage Subsystem (see Section “Non Disruptive Backups Using BCVs or FlashCopy”. Just keep in mind that you have to either shutdown your database or put it into backup mode (ALTER … BEGIN BACKUP) before the split of the BCV pair. Startup or return database from backup state (ALTER … END BACKUP) after the split is done. For further considerations and available options see “EMC Solutions Enabler SYMCLI TimeFinder Component Product Guide” section “BCV Splits Impacting DB Applications”. To be able to perform all types of recovery take RMAN backups of the archived redo logs regularly.
      
   2. 132_List1_Num_Next_1102664 3. RMAN allows you to create image copies of your datafiles, archived redo logs and control files to some disk location. Oracle doesn’t use these files, so you can include them in your regular file backups (UPSTREAM or FDRSOS if you copy all the datafiles on an EMC device). Disaster recovery procedure for this scenario doesn’t require RMAN: after all the system and Oracle software is recovered you need to restore the most current copies of the datafiles and control file(s) to their original locations, then restore all the archived redo logs since the oldest image copy of the datafile restored, and then start Oracle to perform RECOVER DATABASE UNTIL… operation. After successful recovery open database in RESETLOGS mode, because online redo logs are unavailable.
      

Disaster or Off-Site Recovery

You have to install or restore your operating system environment and your Oracle software with all the parameter, configuration, and initialization files ($ORACLE_HOME directory) first. Make sure that the right set of backup tapes was used to regenerate UPSTREAM on-line repository on the Storage Server side.

Prepare and test your disaster recovery plan based on Oracle recommendations from “Performing Recovery After a Total Media Failure” (Oracle8i Recovery Manager User’s Guide and Reference) or “Performing Disaster Recovery” (Oracle9i Recovery Manager User’s Guide). These recommendations, in short, consist of the following steps:

1. 132_List1_Num_First_1068778 1. After Oracle initialization, network, password files, etc. restored, start Oracle instance in NOMOUNT mode and restrict connections to DBA-only users.
   
   1. 132_List1_Num_Next_1068779 2. If your control file was large enough to keep all the latest backup information (as recommended), you do not have to restore the recovery catalog. Start RMAN without connecting to the target database and specify the DBID for the target database (SET DBID command). If you have restored your recovery catalog and it was dedicated to this database only (no other databases were registered in it) you do not have to set the DBID as the recovery catalog has it.
      
   2. 132_List1_Num_Next_1068780 3. Connect to the target database and restore your control file.
      
   3. 132_List1_Num_Next_1068781 4. Specify the latest backed up archived redo log or its time in SET UNTIL command, and mount the restored control file.
      
   4. 132_List1_Num_Next_1068782 5. Restore the datafiles. If you used FDRSOS to backup datafiles (scenario #2), skip this step.
      
   5. 132_List1_Num_Next_1068783 6. Recover the database. (You can specify the recovery limit using UNTIL clause of the RECOVERY command instead of SET UNTIL … in step 4).
      
   6. 132_List1_Num_Next_1068784 7. Open database in RESETLOGS mode.
      

Oracle recommends to immediately close the database and perform a full backup after opening a database in RESETLOGS mode because this creates a new incarnation of the database.

Error Reporting

Even though all the backup events, including errors, are logged in the log file specified in LOGFILE parameter of orasbt.cfg file, you see them first in the Recovery Manager output:

{{id name="Oracle-132_Computer_display_1132856"/}}

{{id name="Oracle-1132856"/}}

Recovery Manager: Release 8.0.5.0.0 - Production
\\RMAN-06009: using target database controlfile instead of recovery catalog
RMAN-06005: connected to target database: ORCL
\\RMAN> run {
2> allocate channel ch1 type ‘sbt_tape’ debug=2;
3> backup format ‘\test%t%s%p’ tablespace user_data;
4> }
5>
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: ch1
RMAN-08500: channel ch1: sid=10 devtype=SBT_TAPE
\\RMAN-03022: compiling command: backup
RMAN-03023: executing command: backup
RMAN-08008: channel ch1: starting datafile backupset
RMAN-08502: set_count=41 set_stamp=392992363
RMAN-08010: channel ch1: including datafile 2 in backupset
RMAN-00569: ================error message stack follows================
RMAN-03007: retryable error occurred during execution of command: backup
RMAN-07004: unhandled exception during command execution on channel ch1
RMAN-10032: unhandled exception during execution of job step 1: ORA-06512: at line 88
RMAN-10035: exception raised in RPC: ORA-19624: operation failed, retry possible
\\ORA-19506: failed to create sequential file, name="\test392992363411", parms=""
ORA-27006: sbtremove returned error
\\OSD-00115: Message 115 not found; product=RDBMS80; facility=SOSD (OS083)
ORA-06512: at “SYS.DBMS_BACKUP_RESTORE”, line 408
RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECREATE
\\Recovery Manager complete\\In the listing above error message 115 shows not found as it is not a Recovery Manager message (sometimes it is reported as OS error message). If the error number is in the 100 – 150 range, then it is most likely an orasbt error message number. Looking the message up in Section “Orasbt Error Messages” you can see that it is an UPSTREAM startup error and you should check if the UPSTREAM parameter in the usorasbt.cfg file has a valid full file spec for uscmd and that it is accessible for Oracle.

23.7 Orasbt Error Messages

100

{{id name="Oracle-132_MsgTxt_1072103"/}}

{{id name="Oracle-1072103"/}}

Internal memory allocation problems\\ Action: Check if your are running low on memory, contact BMC Support.

102

{{id name="Oracle-132_MsgTxt_1072171"/}}

{{id name="Oracle-1072171"/}}

Neither UPSTREAMPATH nor USORASBTCFG environment variables specified.\\103

{{id name="Oracle-132_MsgTxt_1072181"/}}

{{id name="Oracle-1072181"/}}

Unable to open template parameter file specified in usorasbt.cfg in PARAMETER\\ Action: Check if the file specification is correct and that it is accessible by Oracle.

104

{{id name="Oracle-132_MsgTxt_1072233"/}}

{{id name="Oracle-1072233"/}}

Unable to create a new parameter file\\ Reason: Orasbt attempts to create its temporary files in the UPSTREAM working directory specified in WORKPATH parameter in UPSTREAM configuration file – CONFIGFILE parameter from usorasbt.cfg file.

 Action: Check if Oracle has write access to that directory.

105

{{id name="Oracle-132_MsgTxt_1072243"/}}

{{id name="Oracle-1072243"/}}

Error in reading from a template parameter file\\ Action: See error 102 comments.

106

{{id name="Oracle-132_MsgTxt_1072253"/}}

{{id name="Oracle-1072253"/}}

Error in writing to a new parameter file\\ Action: See error 104 comments.

108

{{id name="Oracle-132_MsgTxt_1072263"/}}

{{id name="Oracle-1072263"/}}

((% class="Restriction" style="font-family: Stone Sans;font-style: Italic;font-size: 8.1pt;text-decoration: none;text-transform: none;font-stretch: normal;color: rgb(255,109,61);background-color: transparent;letter-spacing: 0.03em;" %)UNIX only(%%)) Communication pipe to UPSTREAM not opened for inquiry versions\\ Action: Check other messages in usorasbt.log and upstream.log for UPSTREAM start up problems.

109

{{id name="Oracle-132_MsgTxt_1072276"/}}

{{id name="Oracle-1072276"/}}

((% class="Restriction" style="font-family: Stone Sans;font-style: Italic;font-size: 8.1pt;text-decoration: none;text-transform: none;font-stretch: normal;color: rgb(255,109,61);background-color: transparent;letter-spacing: 0.03em;" %)UNIX only(%%)) Errors closing communication pipe to UPSTREAM\\ Action: See error 108 comments.

110

{{id name="Oracle-132_MsgTxt_1077641"/}}

{{id name="Oracle-1077641"/}}

UPSTREAM reported an error\\ Action: Check usorasbt.log and upstream.log for error messages.

111

{{id name="Oracle-132_MsgTxt_1077646"/}}

{{id name="Oracle-1077646"/}}

((% class="Restriction" style="font-family: Stone Sans;font-style: Italic;font-size: 8.1pt;text-decoration: none;text-transform: none;font-stretch: normal;color: rgb(255,109,61);background-color: transparent;letter-spacing: 0.03em;" %)NT only(%%)) Unable to open us.ret file\\ Reason: UPSTREAM creates us.ret file with the operation return code and some additional information in the working directory (WORKPATH parameter of UPSTREAM configuration file specified in CONFIGFILE parameter of usorasbt.cfg file).

 Action: Check if that directory and file and accessible by Oracle.

111

{{id name="Oracle-132_MsgTxt_1077632"/}}

{{id name="Oracle-1077632"/}}

((% class="Restriction" style="font-family: Stone Sans;font-style: Italic;font-size: 8.1pt;text-decoration: none;text-transform: none;font-stretch: normal;color: rgb(255,109,61);background-color: transparent;letter-spacing: 0.03em;" %)UNIX only(%%)) Unable to open a pipe to getret program\\ Action: Check if getret executable is installed, check usorasbt.log file, contact BMC Support.

112

{{id name="Oracle-132_MsgTxt_1072322"/}}

{{id name="Oracle-1072322"/}}

((% class="Restriction" style="font-family: Stone Sans;font-style: Italic;font-size: 8.1pt;text-decoration: none;text-transform: none;font-stretch: normal;color: rgb(255,109,61);background-color: transparent;letter-spacing: 0.03em;" %)NT only(%%)) Unable to read us.ret file\\ Action: See error 111 comments.

112

{{id name="Oracle-132_MsgTxt_1072331"/}}

{{id name="Oracle-1072331"/}}

((% class="Restriction" style="font-family: Stone Sans;font-style: Italic;font-size: 8.1pt;text-decoration: none;text-transform: none;font-stretch: normal;color: rgb(255,109,61);background-color: transparent;letter-spacing: 0.03em;" %)UNIX only(%%)) Unable to read from pipe to getret program\\ Action: See error 111 comments.

113

{{id name="Oracle-132_MsgTxt_1072340"/}}

{{id name="Oracle-1072340"/}}

UPSTREAM failed the requested operation\\ Action: See usorasbt.log and upstream.log files for details.

114

{{id name="Oracle-132_MsgTxt_1072349"/}}

{{id name="Oracle-1072349"/}}

Unable to read version number from us.ret file\\ Reason: Usually indicates problems with UPSTREAM.

 Action: Check usorasbt.log and upstream.log for details.

115

{{id name="Oracle-132_MsgTxt_1072358"/}}

{{id name="Oracle-1072358"/}}

Errors in UPSTREAM startup\\ Action: Check if UPSTREAM parameter of usorasbt.cfg file has a valid full file spec for uscmd and that it is accessible for Oracle.

116

{{id name="Oracle-132_MsgTxt_1072367"/}}

{{id name="Oracle-1072367"/}}

((% class="Restriction" style="font-family: Stone Sans;font-style: Italic;font-size: 8.1pt;text-decoration: none;text-transform: none;font-stretch: normal;color: rgb(255,109,61);background-color: transparent;letter-spacing: 0.03em;" %)UNIX only(%%)) Error creating an UPSTREAM process\\ Action: Contact BMC Support.

117

{{id name="Oracle-132_MsgTxt_1072376"/}}

{{id name="Oracle-1072376"/}}

File name for backup file generated by Recovery Manager exceeds 244 characters\\ Action: Re-specify backup format parameter in your Recovery Manager script.

118

{{id name="Oracle-132_MsgTxt_1072385"/}}

{{id name="Oracle-1072385"/}}

UPSTREAM is too busy with other Recovery Manager backup/restore operations\\ Reason: You can run up to 36 (default value) UPSTREAM backup or restore at a time. usorasbt waits for up to predefined period of time (specified by USORAUSWAITTO environment variable, the default value is 10 min.) for UPSTREAM to become available before reporting this error.

 Action: Verify that you have an UPSTREAM daemon (UNIX) or service (Windows) running, or check the total number of RMAN backup channels (for all Oracle instances) using the same UPSTREAM backup profile in parallel.

119

{{id name="Oracle-132_MsgTxt_1072395"/}}

{{id name="Oracle-1072395"/}}

Unable to create a data pipe to UPSTREAM\\ Action: Check usorback.log and upstream.log for errors in UPSTREAM start up or running;

120

{{id name="Oracle-132_MsgTxt_1072404"/}}

{{id name="Oracle-1072404"/}}

Errors opening data pipe to UPSTREAM\\ Action: See error 119 comments.

121

{{id name="Oracle-132_MsgTxt_1072413"/}}

{{id name="Oracle-1072413"/}}

Errors while waiting for UPSTREAM to open data pipe\\ Action: See error 119 comments.

122

{{id name="Oracle-132_MsgTxt_1072422"/}}

{{id name="Oracle-1072422"/}}

Wait for UPSTREAM to open data pipe connection timed out\\ Reason: usorasbt waits for up to 300 seconds for UPSTREAM to open data pipe connection.

 Action: If it may take more than that for UPSTREAM to start up, adjust this wait time out by specifying USORAUSWAITTO environment variable (see previous section).

123

{{id name="Oracle-132_MsgTxt_1072461"/}}

{{id name="Oracle-1072461"/}}

((% class="Restriction" style="font-family: Stone Sans;font-style: Italic;font-size: 8.1pt;text-decoration: none;text-transform: none;font-stretch: normal;color: rgb(255,109,61);background-color: transparent;letter-spacing: 0.03em;" %)NT only(%%)) Error setting blocking mode for data pipe\\ Action: Contact BMC Support.

124

{{id name="Oracle-132_MsgTxt_1072470"/}}

{{id name="Oracle-1072470"/}}

((% class="Restriction" style="font-family: Stone Sans;font-style: Italic;font-size: 8.1pt;text-decoration: none;text-transform: none;font-stretch: normal;color: rgb(255,109,61);background-color: transparent;letter-spacing: 0.03em;" %)NT only(%%)) Error flushing data pipe to UPSTREAM\\ Action: Contact BMC Support.

125

{{id name="Oracle-132_MsgTxt_1072482"/}}

{{id name="Oracle-1072482"/}}

UPSTREAM ended while usorasbt was waiting on data pipe\\ Action: Check usorasbr.log and upstream.log for UPSTREAM startup and run errors.

126

{{id name="Oracle-132_MsgTxt_1072492"/}}

{{id name="Oracle-1072492"/}}

((% class="Restriction" style="font-family: Stone Sans;font-style: Italic;font-size: 8.1pt;text-decoration: none;text-transform: none;font-stretch: normal;color: rgb(255,109,61);background-color: transparent;letter-spacing: 0.03em;" %)NT only(%%)) Errors obtaining UPSTREAM exit code\\ Action: Check usorasbt.log, upstream.log, and contact BMC Support.

127

{{id name="Oracle-132_MsgTxt_1072506"/}}

{{id name="Oracle-1072506"/}}

Errors writing to UPSTREAM data pipe\\ Action: Check usorasbt.log, upstream.log, and contact BMC Support.

128

{{id name="Oracle-132_MsgTxt_1072516"/}}

{{id name="Oracle-1072516"/}}

Unable to access usorasbt.cfg file\\ Action: Check if you specified the right USORASBTCFG or UPSTREAMPATH environment variables (see previous section), check if Oracle has read access to usorasbt.cfg file.

129

{{id name="Oracle-132_MsgTxt_1072528"/}}

{{id name="Oracle-1072528"/}}

Unable to read from **usorasbt.cfg** file\\ Action: Check if you have read access to the file.

130

{{id name="Oracle-132_MsgTxt_1072539"/}}

{{id name="Oracle-1072539"/}}

Unable to access UPSTREAM configuration file specified in CONFIGFILE parameter in **usorasbt.cfg** file\\ Action: Check if the full file name is correct and if Oracle has read access to the file.

131

{{id name="Oracle-132_MsgTxt_1072550"/}}

{{id name="Oracle-1072550"/}}

Backup profile name is invalid\\ Reason: Backup profile name is your Oracle database instance name, it should be no longer than 7 alphanumeric characters (excluding $, #, @) and starts with an alphabetic character.

132

{{id name="Oracle-132_MsgTxt_1072580"/}}

{{id name="Oracle-1072580"/}}

The required UPSTREAM parameter not found in **usorasbt.cfg** file.\\133

{{id name="Oracle-132_MsgTxt_1072590"/}}

{{id name="Oracle-1072590"/}}

The required CONFIGFILE parameter not found in **usorasbt.cfg** file.\\134

{{id name="Oracle-132_MsgTxt_1072600"/}}

{{id name="Oracle-1072600"/}}

The required PARAMETER parameter not found in **usorasbt.cfg** file.\\135

{{id name="Oracle-132_MsgTxt_1072610"/}}

{{id name="Oracle-1072610"/}}

The USPATH parameter not found in **usorasbt.cfg** file and UPSTREAMPATH environment variable is not specified (see previous section).\\136

{{id name="Oracle-132_MsgTxt_1072620"/}}

{{id name="Oracle-1072620"/}}

UPSTREAM directory is not accessible for Oracle.\\137

{{id name="Oracle-132_MsgTxt_1072629"/}}

{{id name="Oracle-1072629"/}}

((% class="Restriction" style="font-family: Stone Sans;font-style: Italic;font-size: 8.1pt;text-decoration: none;text-transform: none;font-stretch: normal;color: rgb(255,109,61);background-color: transparent;letter-spacing: 0.03em;" %)UNIX only(%%)) Error obtaining data pipe flags\\ Action: Contact BMC Support .

138

{{id name="Oracle-132_MsgTxt_1072642"/}}

{{id name="Oracle-1072642"/}}

((% class="Restriction" style="font-family: Stone Sans;font-style: Italic;font-size: 8.1pt;text-decoration: none;text-transform: none;font-stretch: normal;color: rgb(255,109,61);background-color: transparent;letter-spacing: 0.03em;" %)UNIX only(%%)) Error setting data pipe flags\\ Action: Contact BMC Support .

139

{{id name="Oracle-132_MsgTxt_1077877"/}}

{{id name="Oracle-1077877"/}}

Error reading UPSTREAM data pipe\\ Action: Check usorback.log and upstream.log for errors in UPSTREAM start up or running.

140

{{id name="Oracle-132_MsgTxt_1072661"/}}

{{id name="Oracle-1072661"/}}

Wrong backup profile reported in inquiry versions output\\ Action: Contact BMC Support.

141

{{id name="Oracle-132_MsgTxt_1072675"/}}

{{id name="Oracle-1072675"/}}

No version information obtained from UPSTREAM\\ Reason: Usually caused by UPSTREAM problems.

 Action: Check usorasbt.log and upstream.log files for errors in UPSTREAM start up and running.

142

{{id name="Oracle-132_MsgTxt_1072685"/}}

{{id name="Oracle-1072685"/}}

((% class="Restriction" style="font-family: Stone Sans;font-style: Italic;font-size: 8.1pt;text-decoration: none;text-transform: none;font-stretch: normal;color: rgb(255,109,61);background-color: transparent;letter-spacing: 0.03em;" %)NT only(%%)) Error opening inquire versions output\\ Reason: UPSTREAM creates a temporary report file in UPSTREAM working directory (WORKPATH parameter of UPSTREAM configuration file specified in CONFIGFILE parameter of usorasbt.cfg file).

 Action: Check if this directory is accessible by Oracle. Check usorasbt.log and upstream.log for errors in UPSTREAM startup and run. Contact BMC Support.

142

{{id name="Oracle-132_MsgTxt_1072696"/}}

{{id name="Oracle-1072696"/}}

((% class="Restriction" style="font-family: Stone Sans;font-style: Italic;font-size: 8.1pt;text-decoration: none;text-transform: none;font-stretch: normal;color: rgb(255,109,61);background-color: transparent;letter-spacing: 0.03em;" %)UNIX only(%%)) **usorasbt** reads versions listing directly from UPSTREAM output.\\ Action: Check usorasbt.log and upstream.log for errors in UPSTREAM startup and run.

143

{{id name="Oracle-132_MsgTxt_1072706"/}}

{{id name="Oracle-1072706"/}}

Error accessing inquiry versions output\\ Action: See error 142 comments for the appropriate OS.

144

{{id name="Oracle-132_MsgTxt_1072716"/}}

{{id name="Oracle-1072716"/}}

Error accessing database profile alias file.\\145

{{id name="Oracle-132_MsgTxt_1072726"/}}

{{id name="Oracle-1072726"/}}

Error sending RUN_FUNCTION to UPSTREAM.\\146

{{id name="Oracle-132_MsgTxt_1072736"/}}

{{id name="Oracle-1072736"/}}

Error accessing UPSTREAM.\\147

{{id name="Oracle-132_MsgTxt_1072746"/}}

{{id name="Oracle-1072746"/}}

Error sending parameters to UPSTREAM.\\148

{{id name="Oracle-132_MsgTxt_1072756"/}}

{{id name="Oracle-1072756"/}}

UPSTREAM rejected processing of the function\\ Reason: user name required by the UPSTREAM security, but was wrong or not specified.

149

{{id name="Oracle-132_MsgTxt_1072765"/}}

{{id name="Oracle-1072765"/}}

Error receiving final response from UPSTREAM.\\150

{{id name="Oracle-132_MsgTxt_1072775"/}}

{{id name="Oracle-1072775"/}}

WORKPATH configuration parameter was not specified.\\151

{{id name="Oracle-132_MsgTxt_1072784"/}}

{{id name="Oracle-1072784"/}}

Incomplete buffer received from UPSTREAM. Internal error.\\ Action: Contact BMC Support.

152

{{id name="Oracle-132_MsgTxt_1072793"/}}

{{id name="Oracle-1072793"/}}

Invalid NEWTAPE env. var. Must be FULL, INCR, YES, or NO.\\153

{{id name="Oracle-132_MsgTxt_1072802"/}}

{{id name="Oracle-1072802"/}}

Operator intervention not supported.\\154

{{id name="Oracle-132_MsgTxt_1072811"/}}

{{id name="Oracle-1072811"/}}

Profile name is too long.\\155

{{id name="Oracle-132_MsgTxt_1072820"/}}

{{id name="Oracle-1072820"/}}

ProxyCopy not supported.\\156

{{id name="Oracle-132_MsgTxt_1072829"/}}

{{id name="Oracle-1072829"/}}

Profile (through Oracle DB name) not specified.\\157

{{id name="Oracle-132_MsgTxt_1072060"/}}

{{id name="Oracle-1072060"/}}

Single-user mode is no longer supported.\\158

{{id name="Oracle-132_MsgTxt_1072027"/}}

{{id name="Oracle-1072027"/}}

Waiting for restore PROFILE timed out.\\