Too many arguments passed in(2023). Limit is 2000 in Apex

Error:

Too many arguments passed in(2023). Limit is 2000


Solution:

Add the marked line in plsql.conf file and then restart ohs service

[root@IOFFSHORE ohs1]# vim /u01/oracle/middleware/asinst_1/config/OHS/ohs1/moduleconf/plsql.conf

PlsqlLogEnable On

PlsqlLogDirectory "${ORACLE_INSTANCE}/diagnostics/logs/${COMPONENT_TYPE}/${COMPONENT_NAME}"

# PlsqlIdleSessionCleanupInterval 15 (default)

# PlsqlDMSEnable On (default)
PlsqlMaxParameters 4000

# ============================================================================
# Database Access Descriptors Settings Section
# ============================================================================
include "${ORACLE_INSTANCE}/config/${COMPONENT_TYPE}/${COMPONENT_NAME}/mod_plsql/dads.conf"


-------Now restart the ohs1 component-----

[root@IOFFSHORE ohs1]# cd /u01/oracle/middleware/asinst_1/bin/
[root@IOFFSHORE bin]# ./opmnctl stopall
opmnctl stopall: stopping opmn and all managed processes...
[root@IOFFSHORE bin]# ./opmnctl startall
opmnctl startall: starting opmn and all managed processes...
================================================================================
opmn id=IOFFSHORE:6701
Response: 2 of 3 processes started.

ias-instance id=asinst_1
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
ias-component/process-type/process-set:
  emagent_asinst_1/EMAGENT/EMAGENT/

Error
--> Process (index=1,uid=2072455298,pid=91782)
  failed to start a managed process after the maximum retry limit
  Log:
  /u01/oracle/middleware/asinst_1/diagnostics/logs/EMAGENT/emagent_asinst_1/console~EMAGENT~1.log

[root@IOFFSHORE bin]# ./opmnctl status

Processes in Instance: asinst_1
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status
---------------------------------+--------------------+---------+---------
emagent_asinst_1                 | EMAGENT            |     N/A | Down
RptSvr_IOFFSHORE_asinst_1        | ReportsServerComp~ |   91568 | Alive
forms                            | FormsRuntime       |   91406 | Alive
forms                            | FormsRuntime       |   91225 | Alive
forms                            | FormsRuntime       |   84824 | Alive
ohs1                             | OHS                |   91566 | Alive

[root@IOFFSHORE bin]#

ora 01031 insufficient privileges oracle apex 12cr2

Error: Getting the following error after upgrade Database from Oracle 12c R1 to Oracle 12c R2

ora 01031 insufficient privileges oracle apex 12cr2

Solution

SQL> show parameter sql

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
optimizer_capture_sql_plan_baselines boolean     FALSE
optimizer_use_sql_plan_baselines     boolean     TRUE
plsql_ccflags                        string
plsql_code_type                      string      INTERPRETED
plsql_debug                          boolean     FALSE
plsql_optimize_level                 integer     2
plsql_v2_compatibility               boolean     FALSE
plsql_warnings                       string      DISABLE:ALL
sql92_security                       boolean     TRUE
sql_trace                            boolean     FALSE
sqltune_category                     string      DEFAULT
SQL>

younus01
689456

SQL> alter system set sql92_security=FALSE scope=spfile;

System altered.

SQL>

If the SQL92_SECURITY initialization parameter is set to TRUE and the DELETE operation references table columns, such as the columns in a where_clause, then you must also have the SELECT object privilege on the object from which you want to delete rows.

https://docs.oracle.com/en/database/oracle/oracle-database/19/sqlrf/DELETE.html#GUID-156845A5-B626-412B-9F95-8869B988ABD7

So if you only grant delete, a plain delete with no where clause will work. But you need select to use a where clause (assuming you've set SQL92_SECURITY; true is the default).