[ORACLE] Quick tips: Autonomous Health Framework (AHF) files cleanup.

Hello everyone.

 

How are you doing?

 

Today, I going to show you a quick tip about the AHF - Autonomous Health Framework.

 

In case your autopurge is off, and your disk space is slowing, you can do a manual purge.

 

And it's a simple operation.

 

1) Check the space

 

df -h

 

2) Lists all the files that would be deleted without deletion - as root.

 

For example, I'm only going to clear the last 10 days (my retention is 30 days). 

  

tfactl purge -older 20d -dryrun

 

 

 

3) Delete the files
 
tfactl purge -older 25d
 
I could run it using hours, for example:
 
tfactl purge -older 200h 

The full syntax and parameters are:

 

 

 

4) Check the space

 

 

5) To enable autopurge:

 

tfactl set autopurge=on

 

 

You can manage the options using tfactl menu:

 

tfactl menu

 

 

For more information: tfactl purge

 

And, there you go. The space has been cleared.

 

It`s as simple as that!

 

I hope this tip helps you.

 

Regards

Mario

 

 

[ORACLE] Increasing the number of cores in a virtualized Oracle Database Appliance.

Hello everyone.

How are you going?

Today, I'll show you the process to increase the number of cores in a virtualized ODA HA X7-2.

Important: This process must be validated with Oracle Support, always.

 

Furthermore, remember that:  

• This step-by-step worked for me, but it may not work for you. 
• It's a test environment. The real life will be different, for sure.
• This post is for study and testing as well and has no concern for performance and security best practices.

So, let's get started!

 

The first step is create a new BIOS xml file to change the number of the cores.

su -

ubiosconfig export all -x bios.xml

We need to change te parameter below:

vi bios.xml

From: <Active_Processor_Cores>3</Active_Processor_Cores>

To:      <Active_Processor_Cores>4</Active_Processor_Cores>

In my example, I'll change to 3 cores for 4 cores.

Now, we need to import the new parameter.

su - 

ubiosconfig import config -f --expert -y -x bios.xml

Reboot the node and we have 4 cores on node 1. Repeat the process for node 2.

Before:

After:

After this, it was easy!

odacli update-cpucore --cores 8

{

  "jobId" : "388ac288-abaf-4304-8a3b-b033e4ca7dde",

  "status" : "Created",

  "message" : null,

  "reports" : [ ],

  "createTimestamp" : "July 11, 2024 02:49:22 AM BRT",

  "resourceList" : [ ],

  "description" : "CPU cores  service update",

  "updatedTime" : "July 11, 2024 02:49:22 AM BRT"

}

And, there you go!

I hope it helps!

Regards

Mario

[ORACLE] How to create a test environment with Oracle 23ai running on MacBook Pro M3 Pro.

Hello everyone.

How are you going?

I've finally surrendered to the Macbook's allure for work. 

And my first challange was to run the Oracle 23ai in my Mac.

So, let's get started!

First, we need to install the homebrew.

/bin/bash -c 

"$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)" 

We don't have an installer to Oracle 23ai for the Mac M3. 

So, I'm use Colima + Docker + QEMU to emulate x86_64 arch and run the Oracle 23ai. 

Colima is an open source container runtime for macOS with minimal configuration. In addition,

QEMU was an open source software virtualization tool that performs hardware emulation. 

Now, we need to install Docker, Docker-compose, Colima and reinstall QEMU.

   

   brew update

   brew install docker

   brew install docker-compose

 

   brew install colima

   brew reinstall qemu

* Yes, I forgot to take the screenshots 

We are to install Rosetta, as well.

   oftwareupdate --install-rosetta

According Apple, "Rosetta is not an app that you open or interact with. Rosetta works

automatically in the background whenever you use an app that was built only for Mac

computers with an Intel processor. It translates the app for use with Apple silicon."

Check the colima status.

   colima help

Stop and delete the old profile.

   colima stop

   colima delete

And start Colima with the parameters bellow:

   colima start --cpu 4 --memory 10 --arch x86_64 --vm-type vz --vz-rosetta

   Where:

      --vm-type=vz             ==> Virtual machine type.

      --vz-rosetta                ==> Enable Rosetta for amd64 emulation.

      --mount-type=virtiofs ==> Volume Mount Driver for vz.

      --arch x86_64            ==> Architecture (x86_64).

   colima status

* The default VM created by Colima has 2 CPUs, 60GB storage and 2GB memory runing

Ubuntu.

Access the Colima console:

   colima ssh

   # Check if Colima is using the new profile

   docker context ls

Finally, create a docker container running Oracle 23ai:

 docker run -d -it --name Orcl23ai /

    -p 1527:1521 /

    -p 5507:5500 /

    -p 8087:8080 /

    -p 8447:8443 

    -e ORACLE_PWD=E 

    container-registry.oracle.com/database/free:latest

Check the container and database.

   docker ps --format "table {{.ID}}\t{{.Status}}\t{{.Names}}\t{{.Ports}}"

   docker exec -it Orcl23ai /bin/bash

And thats it. As simple as that.

If you can watch this installation, you can see these videos from my friend Eduardo Claro:

Installing Colima and Docker in Apple Silicon ARM based machines

You can also consult the documentation here - it's for Oracle Autonomous Database Free Container Image, but the process is the same.

I hope it helps you.

Regards

Mario

[ORACLE] ORA-46362: Could not translate variable ORACLE_BASE.

Hello evceryone!

I hope you're doing well!

Today, when I tried to start a database using SRVCTL, I made the error below.

[GTP1.ora-rac01 dbs]$ srvctl start database -d GTP

When I started the database using SQLPLUS, it was normal.

I checked the ORACLE_BASE variable.

    [GTP1.ora-rac01 dbs]$ echo $ORACLE_BASE/

    /u01/app/oracle/

And I check the database configuration, as well.

    [GTP1.ora-rac01 dbs]$ srvctl config database -d GTP

Everything seemed normal.

When I check on "Database Error Messages", the error became clearer to me.

This database was restored and its environment variables were wrong. 

Why? I have no idea! 

The solution was to change the ORACLE_HOME variable using SRVCTL SETENV. 

[GTP1.ora-rac01 dbs]$ srvctl setenv database -db GTP -env ORACLE_BASE=$ORACLE_BASE

And there you go! As simple as that!

After that, the database can be started normally.

I hope that it helps you!

Regards

Mario

[ORACLE] Simple trick about DBMS_JOBS.

Hello everyone!!!

Hope you're doing well!

Today, I'm going to show you a simple trick about dbms_job. 

Ok, Ok!!! I know we should use the dbms_scheduler, but sometimes the customer uses an "old school" schedule, and they don't want to change.

In this case, if you run a creation with the SYS user, for example, the job will be created under the SYS User.

But you can change this using SYS.DBMS_IJOB.CHANGE_ENV.

For example:

exec dbms_job.submit (

   job       => jobno,
   what      => 'begin USER_DEST.proc; end;',
   next_date => SYSDATE+1,
   interval  => 'trunc(sysdate + 1) + 10/1440');   
  

SELECT 

JOB, 
LOG_USER,
PRIV_USER,
SCHEMA_USER,
LAST_DATE,
LAST_SEC,
WHAT 
FROM dba_jobs
WHERE JOB = 18068;

    JOB LOG_USER PRIV_USER SCHEMA_USER LAST_DATE LAST_SEC  WHAT
------- -------- --------- ----------- --------- --------- -------  

  18068 SYS     SYS    SYS        17-JUN-24 09:00:00 USER_DEST.proc;

If I need to change the owner:

EXEC SYS.DBMS_IJOB.CHANGE_ENV(
JOB    => 18068, 
LUSER  => 'USER_DEST', 
PUSER  => 'USER_DEST', 
CUSER  => 'USER_DEST', 
NLSENV => NULL);

Where:
JOB    => Job number 
LUSER  => Log user
PUSER  => Priv user
CUSER  => Schema User
NLSENV => NLS Language

Example:
-- Change only PRIV_USER
EXEC SYS.DBMS_IJOB.CHANGE_ENV(18068,NULL,'USER_DEST',NULL,NULL);
COMMIT;

-- Change all
EXEC SYS.DBMS_IJOB.CHANGE_ENV(18068,'USER_DEST','USER_DEST','USER_DEST',NULL);
COMMIT;

SELECT 

JOB, 
LOG_USER,
PRIV_USER,
SCHEMA_USER,
LAST_DATE,
LAST_SEC,
WHAT 
FROM dba_jobs
WHERE JOB = 18068;

    JOB LOG_USER   PRIV_USER  SCHEMA_USER LAST_DATE LAST_SEC  WHAT
------- ---------  ---------  ----------- --------- --------- -------

  18068 USER_DEST  USER_DEST  USER_DEST   17-JUN-24 09:00:00 USER_DEST.proc;

As simple as that!

I hope this helps you!

Regards

Mario