If you are on the latest Exadata plugin for EM 13.3 (well, even the 13.2 version of the plugin). Be aware that there’s a bug where if the Exadata nodes’ names are longer than 7 characters, you cannot discover them.
EM just throws a weird error with below legend:
SEVERE: makeTargetsXml for each rack#: 1 e=java.lang.StringIndexOutOfBoundsException: String index out of range: -1
The solution is to apply the latest (March 2019) Bundle Patch to the agents running on the Exadata’s compute nodes.
More info on below MOS note:
Exadata Discovery Fails With “No New Component Is Discovered. Click Cancel” (Doc ID 2477624.1)
Another good excuse to keep your EM system up to date.
While trying to add an additional OMS to the current OEM 13.3 GCDomain using the provisioning console there’s an error in the Install homes step.
The error contains the following message:
Caused by: oracle.sysman.oii.oiif.oiifb.OiifbEndIterateException:
oracle.sysman.oii.oiif.oiifb.OiifbEndIterateException: SEVERE:Values for the following variables could not
be obtained from the command line or response file(s):
Silent install cannot continue.
This issue is related to Bug 28290139 and the workaround can be found in MOS 2432095.1 After performing the workaround the OMS addition job needs to be executed from scratch. This resolves the issue.
Oracle Autonomous Data Warehouse (ADW) is one of the so-called DB as a Service (DBaaS) or probably we should call it Data Warehouse as a Service (DWaaS) with the difference that this service is completely automatic and autonomous.
This service is comprised by an Oracle Database (of course) already pre-configured for analytics, data lakes and data warehouse workloads. This Oracle Database (PDB) has 18c features running on Exadata hardware. Oracle Exadata software is 18c with features like In-Memory delivered from the cell server.
There’s a service console that helps to manage the ADW services.
On top of this, Machine Learning (ML) tools help with data analysis and data models. Development tools like SQL Developer are useful to create objects, load data and more.
Let’s now talk about tasks that happen automatically:
Automatic statistics gathering during direct-path load operations
Automatic Indexing (soon)
Automatic Tablespace Management
Automated backups and patching
ADW is also capable of repair itself. Machine Learning is used to detect anomalies and uses pattern recognition to determine if this problem is already in the problem knowledge-base. If is a known problem, it will apply the fix automatically.
On the security side all the information is encrypted at rest. This means that backups and all data in the tablespaces is encrypted using TDE.
The connectivity between ADW and the rest of the world is secured be default. Oracle provides a wallet file that contains all the connectivity information required to login.
If you open this file you’ll notice that all connectivity is being done through SSL.
Provisioning is quite easy using the service console. From the main dashboard you can click on “Create a data warehouse” button.
Select the Workload type between Autonomous Data Warehouse ADW or Autonomous Transaction Processing ATP loads.
Next you choose a compartment where the ADW database is going to live. For this example I’m going to choose ADWTest01 compartment. It is not recommended to use the root compartment.
Then we are going to set the Display and Database names. For this example, I’m choosing 1 OCPU and 1 TB of storage. Keep in mind that ADW is elastic, this means we can add more OCPUs and Storage on the fly without the need for downtime.
From the Administrator Credentials section we are going to set the ADMIN account password.
Next is license type. You can choose to use a license that you already own or subscribe to a new one.
Last but not least is the Tags section. You can add a tag to this ADW database to better manage it inside your tenancy.
Let’s now click Create Autonomous Database and wait few minutes for OCI to provision it.
The orange ADW icon will turn green once the ADW database is fully provisioned.
In my next post I’ll cover how to connect o the ADW database and how to load data to it.
Oracle Cloud Infrastructure requires a VCN (Virtual Cloud Network) to be created in order to connect to DB Systems (Bare Metal and VM). There are basically tow options to configure this VCN.
·Public Subnet with Internet Gateway
The Public Subnet with Internet Gateway will expose the network to the Internet. The Internet Gateway is a virtual router that provides a path for traffic between he VCN and the Internet. This option is mainly recommended for non-production workloads.
The Private Subnet cannot be reached from the Internet. You will need to configure a Dynamic routing Gateway (DRG) with either FastConnect or IPSec VPN on your on-premises site.
Once the VCN is created, you can associate the Bare Metal or the VM system to it. The navigation menu to create the VCN is Menu -> Networking -> Virtual Cloud Networks
Then click on Create Virtual Cloud Network and follow the wizard.
Once you create your VCN it will show as a (green) available icon.
b)If your issue is more with tablespace quotas, TEMP or UNDO you may want to enable RESUMABLE session
RESUMABLE is an option which allows the session to go into a suspended state in such a way that it won’t fail/abort. The session cannot wait forever though, this is controlled by RESUMABLE_TIMEOUT initialization parameter.
In order to enable this option at the session level you have to execute below SQL statement:
SQL> ALTER SESSION ENABLE RESUMABLE;
Alertlog file will record if the session entered into suspended mode.
Some examples are:
########### statement in resumable session ‘User TEST1(32), Session 3, Instance 2’ was suspended due to ORA-01536: space quota exceeded for tablespace ‘USERS’
########### statement in resumable session ‘User TEST1(32), Session 15, Instance 1’ was suspended due to ORA-01562: failed to extend rollback segment number 4
########### statement in resumable session ‘User TEST1(32), Session 23, Instance 1’ was suspended due to ORA-01652: unable to extend temp segment by 32 in tablespace TEMP
########### statement in resumable session ‘User TEST1(54), Session 2, Instance 1’ was suspended due to ORA-01653: unable to extend table TEST1.TEST_RESUMABLE by 256 in tablespace USERS
While the session is into this suspended state it will account time to the “statement suspended, wait error to be cleared” wait event.
Once the error that sent the session to the suspended state is fixed, the session will resume its work.