Remote Agent for Linux and Unix Servers (RALUS) RMAN Backup fails with access denied when backing up Oracle from a Linux Machine when the agent and backup job are configured incorrectly.

Article:TECH59723

Created: 2010-01-22

Updated: 2010-01-22

Article URL http://www.symantec.com/docs/TECH59723

Article Type
Technical Solution

Product(s)

Show all

Environment

Show all

Languages

Show all

Problem

Remote Agent for Linux and Unix Servers (RALUS) RMAN Backup fails with access denied when backing up Oracle from a Linux Machine when the agent and backup job are configured incorrectly.

Solution

Oracle under Linux requires a different credential set to be used due to rights set during the Oracle installation. Perform the following steps to set the permissions properly:

The user account used for Linux machine authentication will be Oracle (Default User created during ORA install)

Make sure the Oracle Account is part of the BEOper group by running "id oracle". To change group membership, the "usermod" command is one option available

(NOTE: The oracle account may optionally be joined to the root group. This should only be done if backup jobs will be backing up the linux file system and oracle instances within the same selection list. Alternatively, jobs with both types of resources can be created and the different resources can be assigned individual credentials from the Job Properties > Resource Credentials configuration screen.)

Linux server Database Access configuration

1. Login as root and run AgentConfig from command prompt /opt/VRTSralus/bin/AgentConfig

2. Type 1 to Configure database access

3. Type 1 to Add system credentials for Oracle operations

4. Enter oracle for Enter a user name that has local system credentials or the account you have created which is a member of beoper and oinstall groups

5. Type the password for oracle

6. Type password again

7. Type Y for Do you want to use the full computer name /IP address for Oracle operations?

8. Type the Linux server name for Enter the full computer name or IP address. Make a note of this value because it is required later and is case-sensitive.

9. Type N for Do you want to use a custom port to connect to the media server during Oracle operations?

10. Type Y for Commit Oracle operation settings to the configuration file?

11. Type 5 to quit and return to the main menu.

Linux server Oracle Instance configuration

1. From the AgentConfig main menu, type 2 to Configure Oracle instance information

2. Type 1 to Add a new Oracle instance to protect

3. From list displayed, select 1 to add the database instance

4. Type sys for Enter the Oracle database SYSDBA user name. You can enter a different database user. Details for creating a different account are in the related technote http://support.veritas.com/docs/230036

5. Type the password for Enter the Oracle SYSDBA password

6. Type the password again.

7. Type the Backup Exec media server name for Enter the media server name or IP address

8. Type N for Do you use a recovery catalog

9. Type N for Do you want to use a customized job template

10. Type Y for Commit Oracle operation settings to the configuration file?

On the media server:

1. Go to Network >Logon Accounts. Create an entry for the Oracle Account

2. Under Tools >Options >Oracle>Modify List, set Oracle as the account for the servername as it was specified in AgentConfig tool above under Database Access, step number 8. When using the FQDN, use the same capitalisation that was used when the value was entered in AgentConfig: the entry in AgentConfig needs to be consistent with the entry on the media server.

3. Create a new backup job using oracle as the account used to connect to the Linux server and Oracle instance(s). Run a backup to test