You could use logminer to reconstruct SQL statements if you want to dig into it. You can also create a trigger to ensure column value is whole number or create check constraint:

SQL> CREATE TABLE TBL(N NUMBER);


Table created.


SQL> ALTER TABLE TBL ADD CONSTRAINT CHECK_IF_WHOLE_NUMBER CHECK(N = TRUNC(N));


Table altered.


SQL> INSERT INTO TBL VALUES(1);


1 row created.


SQL> INSERT INTO TBL VALUES(1.5);

INSERT INTO TBL VALUES(1.5)

*

ERROR at line 1:

ORA-02290: check constraint (SCOTT.CHECK_IF_WHOLE_NUMBER) violated



SQL>

SY.

Hello Bruno,

I ran the test on CDB$ROOT to isolate PDB limitation issues.

The same behavior occurs with PDBs, no more than two schedulers are executed simultaneously in each PDB, but when running on different PDBs, than can be more than two schedulers simultaneously in the CDB.

The problem is that we have routines in the application that control parallelism by scheduler, and with only 2 running this compromises performance.

Thanks,
Everson