09-22-2015 03:12 PM
I am configuring Oracle Agent on Linux and have a few questions about setup.
Oracle Grid Infrastructure 12.1.0.2.3 (Oracle ASM 12.1.0.2.3 configured)
Oracle Database 12.1.0.2.3 with Real Application Cluster option (2 node cluster) and Single Tenant (multitenant option)
The cluster files, data files and recovery files are on Oracle Automatic Storage Management (ASM).
The Oracle software is installed on local driver ext4.
Page# reference Backup Exec 15 Administration Guide
***************************************************************************
PAGE 1193
***************************************************************************
Installed Agent on Linux as ROOT user
********************************************************************************************
PAGE 988
********************************************************************************************
9/22/2015 QUESTION
Is the logon OS user who starts AgentConfig for Oracle Instance configuration REQUIRED to have ROOT privilege?
9/22/2015 QUESTION
Is the logon OS user who starts AgentConfig for Oracle Instance configuration REQUIRED to be part of BEOPER group?
9/22/2015 QUESTION
Is the logon OS user who starts AgentConfig for Oracle Instance configuration REQUIRED to have any other privileges?
For example, ORACLENAME.
PAGE 980
The name is in the format RAC-<dbname>-<dbid>, where dbname is the database name, and dbid is the database ID.
9/22/2015 QUESTION
<dbname> is the database name. Should we use the Initialization Parameter value of db_name as the <dbname>?
9/22/2015 QUESTION
Page 980 says, “…enter the fully qualified domain name of each physical node.” The db_name is listed as CDBSBLT, without the fully qualified domain name. Should we add the Initialization Parameter value db_domain to the db_name?
<db_name> + <db_domain> = CDBSBLT + CTC.CA.GOV = CDBSBLT.CTC.CA.GOV
PAGE 977
Oracle 12c notes
New SYSBACKUP privilege for RMAN
For Oracle 12c and later, the Oracle Agent supports backup and restore tasks only with a user that has SYSBACKUP privileges.
PAGE 981
Displays the user name for the Oracle instance. If the credentials for the Oracle instance change, you must enter a user with SYSDBA rights to the Oracle instance. For Oracle RAC nodes, enter the same set of credentials for all of the nodes. For an Oracle 12c database, you must enter a user name that has SYSBACKUP privileges.
9/22/2015 CUSTOMER QUESTION
Is this statement correct, "the credentials cannot be verified if the user account with which you are logged on is a member of the Oracle DBA group?" Did they mean that "the credentials CAN be verified"?
9/22/2015 QUESTION
Are the "credentials for an instance" referring to an OS user account or Database user account?
9/22/2015 QUESTION
For RAC AND 12c database, the User Name (database user account) must have SYSBACKUP privilege and be entered on all nodes in cluster. Does the RAC and 12c database User Name (database user account) need to have SYSDBA privilege? The Page 977 seems to indicate no but I am uncertain whether page 981 refers to RAC and 12c databases.
9/22/2015 QUESTION
If the database uses a Fast Recovery Area then will the auxiliary database data files be created in the Fast Recovery Area?
Please confirm the following is true for Linux: PAGE 982 - If the database that you want to restore uses a Fast Recovery Area, RMAN creates the auxiliary database files in this area in the <FRA>/<SID>/datafile directory.
9/22/2015 QUESTION
If the database uses a Fast Recovery Area then will we be leaving this entry blank?
Please confirm the following is true for Linux: PAGE 982 - If you do not specify this path, RMAN assumes that the Fast Recovery Area is configured and has sufficient space.
9/22/2015 QUESTION
If the AUXILIARY INSTANCE PATH must be left blank since Fast Recovery Area on ASM is being used, then does the Oracle User (database user account) have to have explicit read/write access privileges to Fast Recovery Area in ASM Disk Group? How?
********************************************************************************************
PAGE 992
********************************************************************************************
PAGE 992
Note: When you use the Backup Exec Agent Utility, the USER ACCOUNT with which you are logged on should be a MEMBER OF THE ORACLE DBA GROUP.
You must have ADMINISTRATOR PRIVILEGES to run the Backup Exec Agent Utility.
To enable database access for Oracle operations on Linux servers
9/22/2015 QUESTION
Does the User Account (OS User Account) that starts the Backup Exec Agent Utility for “Enabling Database Access for Oracle Operations on Linux Servers” need to be a member of the Oracle DBA group (OSDBA) as this wasn’t a requirement for configuring the Oracle Instance?
9/22/2015 QUESTION
Does the User Account (OS User Account) that starts the Backup Exec Agent Utility need to be a member of the BEOPER group?
9/22/2015 QUESTION
Is ROOT privilege required for “Enabling Database Access for Oracle Operations on Linux Servers” because I don’t see that requirement anywhere in the documentation other than initial agent for Linux installation?
9/22/2015 QUESTION
Does this need to be the same OS user account that configured Oracle Instance for Linux Servers?
9/22/2015 QUESTION
Is ROOT privilege required for this OS User account because I don’t see that requirement anywhere in the documentation other than initial agent for Linux installation?
09-22-2015 03:13 PM
Thanks for any help in advance.