Skip to main content

ORA-00600: internal error code, arguments: [pesldl03_MMap: errno 1 errmsg Operation not permitted

ORA-00600: internal error code, arguments: [pesldl03_MMap: errno 1 errmsg Operation not permitted



Issue:


ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 1 with process name "DW00" prematurely terminated
ORA-31671: Worker process DW00 had an unhandled exception.
ORA-00600: internal error code, arguments: [pesldl03_MMap: errno 1 errmsg Operation not permitted
], [], [], [], [], [], [], [], [], [], [], []
ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 2 with process name "DW00" prematurely terminated
ORA-31671: Worker process DW00 had an unhandled exception.
ORA-00600: internal error code, arguments: [pesldl03_MMap: errno 1 errmsg Operation not permitted


Reason


The issue occurs since 11g as we are now using /dev/shm when using native PLSQL compilation.
This requires that /dev/shm is of type tmpfs and is mounted with the following options:With rw and exec permissions set on it
Without noexec or nosuid set on it
If /dev/shm is mounted with "noexec" such an error occurs.
This was addressed in
Bug 18076018 - ORA-600 [PESLDL03_MMAP: ERRNO 1 ERRMSG OPERATION NOT PERMITTED]
closed as "Not a Bug" with reference to the documentation which clearly states that /dev/shm may not be mounted with "noexec" option.


Solution:


Make sure that DB should have enough SGA value


Ensure that the /dev/shm mount area is of type tmpfs and is mounted with the following options:

With rw and exec permissions set on it
Without noexec or nosuid set on it


Old setting in OS for Server1/ server2
tmpfs /dev/shm tmpfs defaults,nodev,nosuid,noexec 0 0


New setting in OS for Server1/ server2
tmpfs /dev/shm tmpfs defaults 0 0

Mount options can be verified as Oracle or root user with the commands below;

$ mount | grep /dev/shm
shmfs on /dev/shm type tmpfs (rw) .... This is the recommended setting.

Login as root to modify the mount options

-- Mount with 'rw' option
# mount -t tmpfs shmfs -o rw /dev/shm

--Verify the change

# mount | grep /dev/shm

Reboot the server.


If you like please follow and comment
Labels:

Comments

Post a Comment

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...
Post a Comment
Read more

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...
Post a Comment
Read more

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...
Post a Comment
Read more