-
Titre
Does the Oracle cartridge support container and plugable databases in Foglight? -
Description
How to add Oracle 12c container and pluggable databases to Foglight?
-
Cause
For Oracle 12C - Pluggable, modifications have been made to show data for Pluggable database's:New icon in the Databases dashboard which indicated that the instance is 'Pluggable'.- Alarms for Pluggable database's.
- New 'Pluggable Databases' dashboard.
- The next screen show data regarding Pluggable database's: 'Initialization Parameters' , 'Invalid Objects', 'Locks' ,'Tablespaces and Datafiles' , 'Overall Datafiles I/O' and 'Sessions'.
-
Résolution
Plugable (CDB) database support was added beginning with the 5.6.7.2 Oracle cartridge. However, due to a known Oracle issue on version 12C pluggable, the Datafile Fragmentation and Tablespace Fragmentation collections retrieve data for cdb$root only. This has been logged as Defect ID ODB-10750 and is listed in the release notes.
Oracle 12c and higher is only supported if the user is both a common user and can log into the CDB$ROOT container. This is a known limitation of monitoring.
Enhancement Request FOG-10585 has been logged to enable agent installation and monitoring on PDB-only environments.1) User should be a common user, in that the database user identity and password is known in the root and in every existing and future pluggable database (PDB).
Here is additional information from Oracle.2) The user needs to confirm that the user account can log into the CDB$ROOT (root) container.
The error "ORA-65096: invalid common user or role name when running the script on the container" may appear if the common user name is not valid.
By default in Oracle the name of every user-created common user must begin with the characters c## or C##. (Oracle-supplied common user names do not have this restriction.) Further details here.
To create a Common user like 'foglight' without the prefix, before creating the user run:
alter session set "_ORACLE_SCRIPT"=true;
See in this webpage.
3) The user can search for Oracle 12 via Google based on "About Creating a CDB and Enable
4) In reference to this link, please try this from the FGLAM agent manager host:The user can use the following commands from the FGLAM agent manager host.--Connecting to a Pluggable Database (PDB)Direct connections to pluggable databases must be made using a service. Each pluggable database automatically registers a service with the listener. This is how any application will connect to a pluggable database, as well as administrative connections.SQL> -- EZCONNECTSQL> CONN system/password@//localhost:1521/pdb1Connected.SQL>SQL> -- tnsnames.oraSQL> CONN system/password@pdb1Connected.SQL>The connection using a TNS alias requires an entry in the "$ORACLE_HOME/network/admin/tnsnames.ora" file, such as the one shown below.PDB1 =(DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = ol6-121.localdomain)(PORT = 1521))(CONNECT_DATA =(SERVER = DEDICATED)(SERVICE_NAME = pdb1)))PDB users with the SYSDBA, SYSOPER, SYSBACKUP, or SYSDG privilege can connect to a closed PDB. All other PDB users can only connect when the PDB is open. As with regular databases, the PDB users require the CREATE SESSION privilege to enable connections.---Displaying the Current ContainerThe SHOW CON_NAME and SHOW CON_ID commands in SQL*Plus display the current container name and ID respectively.SQL> SHOW CON_NAMECON_NAME------------------------------CDB$ROOTSQL>SQL> SHOW CON_IDCON_ID------------------------------1SQL>Once all the requirements are set, adding Pluggable Database is like adding any other Oracle database via Monitor wizard from the Database dashboard within the Foglight Console. Please, ensure the user account is correct to link to the PDB. The user can use the above connection string to test PDB connection. -
Identifiant du défaut
FOG-10585 -
Informations supplémentaires
If connection problem continues, Support Team needs the following: 1) Screenshot of the issue with the timestamp. 2). Is it possible to try using an Oracle account not named SYSTEM that has SYSDBA, SYSOPER, SYSBACKUP, or SYSDB privileges? We have seen in earlier releases of the Oracle cartridge where there were issues using an account named SYSTEM. 3). What are the results from these queries using the SYSTEM account that you have been using to connect. select decode(cdb,'YES',1,0) is_pluggable From v$database; select cdb From v$database; select sid,con_id from V$session where sid=sys_context('USERENV','SID'); Please, try a different user account that is not named System for testing purposes. 4) Valid logs from the FGLAM support bundle for Support Team to investigate. Please, create FglAM support bundle by expanding Administration | Agents | FglAM Support Bundle. If the FGLAM logs are corrupted, Support Team can assist in removing old logs from old cartridges on the FGLAM.