Here, you have an small explanation about each parameter :
SESSIONS_PER_USER: The user can have any number of concurrent sessions.
CPU_PER_SESSION: In a single session, the user can consume an unlimited amount of CPU time.
CPU_PER_CALL: A single call made by the user cannot consume more than 30 seconds of CPU time.
CONNECT_TIME: A single session cannot last for more than 45 minutes.
LOGICAL_READS_PER_SESSION: In a single session, the number of data blocks read from memory and disk is subject to the limit specified in the DEFAULT profile.
LOGICAL_READS_PER_CALL: A single call made by the user cannot read more than 1000 data blocks from memory and disk.
PRIVATE_SGA: A single session cannot allocate more than 15 kilobytes of memory in the SGA.
COMPOSITE_LIMIT: in a single session, the total resource cost cannot exceed 5 million service units. The formula for calculating the total resource cost is specified by the ALTER RESOURCE COST statement.
Those are not the only paramters ,but this its a great example to start diferent tests.
I’m here again, to give an small explanation of why, we need know how to deinstall an Release Update.
It’s depends, on my case, the last RU had some issues in the import datapump.
After review all cases and aply some workarounds, and debug and review all logs and traces with the ADRCI tool to stay sure of my desicion, deinstall.
I review the oracle document from MOS: Database 19c Release Updates and Revisions Bugs Fixed Lists (Doc ID 2523220.1)
The first step is verificate the number of the RU, to start with the procediment:
TO_CHAR(action_time, 'YYYY-MM-DD') AS action_time,
order by CON_ID, action_time, patch_id;
This query help us, with the list of the number, to verified the last patch applied.
In some caso to buil a report or its necesary know the version on own exadata machine to take some desicion to increaze the storage, virtualized or apply an upgrade we can find this information in the file databasemachine.xml :
With this command line we know where to find the file :
[root@exa01dbadm01 ~]# locate databasemachine.xml | xargs ls -l
when knowing which is the date of the file, we know which is the last updated, and there we filter which is our XML file, in order to obtain the version of the computer equipment:
Good Morning Guys ! I am started on a new challenge, and my articles will be write in English Mode, because the best part of my public, and messages that I receive every day are from India, England, USA and many countrys from world.
I love the Community and promess continuing givin support and answers to a lots of mails on Spanish that I receive every week. Let’s start!
Oracle Golden Gate
Exadata Image Version
Oracle Grid Infrastructure
We’ll start with an summary of tasks that we need keep in mind to start with confguration and installation of Oracle Golden Gate on a RAC environment. It’s necessary :
An a share file system, we choice ACFS (ASM Cluster File System) under grid infrastructure 12.1.0
Oracle Golden Gate.
Creating and configuring ACFS on Exadata
When we working on an Oracle RAC environment, we must install an OGG on a cluster file system. As part of the architecture design, we choose the ACFS, but we could use NFS or DBFS.
My desicion was based on my experience with this FS and listening the council from others partners , that were used on ODA implementations.
Basically, my procedure are same that on Non Exadata Environments:
On the next screen, we can see the name of the candidate DG.
Generally, we find typically three disk groups.
We choose the DBFS_DG .
Choose the Volume tab.
Click the Create button to create a new Volume (remember that we need the OGG FS).
Nos encontrabamos remapeando instancias de Oracle Cloud Control 12c hacia Oracle Cloud Control 13c, como parte de la planificacion de un nuevo esquema de monitoreo, y gestion de Tickets de Soporte.
En una las bases de Exadata que recientemente habian sido agregadas sin problemas, intentamos revisar las metricas en el dashboad y nos encontramos con un error el target.
“Dynamic Category property error, Get dynamic property error, No such metadata, Computation of a critical dynamic property failed. Retries Completed”
Cual fue la causa ?
Revisando en la tabla dba_registry_history, nos encontramos con que falta la columna bundle_series.
SQL> desc dba_registry_history
Name Null? Type
------------- -------- ----------------------------