Introduction: This document provides a comprehensive guide to resolving “Query Timeout Expired” errors in SQL Server. These errors typically occur when a query execution exceeds the configured timeout period due…
Read MoreIntroduction Moving SQL Server database files is a common task for database administrators, whether due to storage reorganization, performance optimization, or migration to a new environment. Ensuring a smooth transition…
Read MoreIntroduction This document explains the process of configuring Foglight Blackouts to suppress alerts, particularly for ‘Days since Last Backup’ notifications generated by secondary database instances. Secondary instances, typically used in…
Read MoreIntroduction: Splitting of order lines, this can be done during shipping last part of sales order, generally we come across this scenario, when we want to ship partial quantity when…
Read MoreIntroduction : The error “DPY-4011: The database or network closed the connection” can occur when attempting to connect to an Oracle Database using the python-oracledb Thin mode. This issue often arises when Native Network Encryption (NNE) is enabled, as NNE requires the Thick mode to function properly. In this blog, we’ll explore the root cause of this error and provide a step-by-step guide to resolve it, ensuring a stable and secure database connection. Error Message: “DPY-4011: the database or network closed the connection” Understanding DPY-4011 : The DPY-4011 error indicates that the connection failed due to incompatibilities between the Thin mode of python-oracledb and the database’s NNE settings. Thin mode, while lightweight and easy to use, does not support NNE. Switching to Thick mode resolves the issue by enabling NNE support. Prerequisites for Troubleshooting: Verify if NNE is Enabled Run the following query to check if NNE is enabled in your database with the following querry. SQL> SELECT network_service_banner FROM v$session_connect_info; If NNE is enabled, the output will display encryption and crypto-checksumming services. If not, only basic services will appear. Steps to Resolve DPY-4011: Step 1: Install Oracle Client Libraries Download and install the Oracle Instant Client on your system. For example: Version: 19.19.0.0.0 Download Link: https://download.oracle.com/otn_software/linux/instantclient/1919000/instantclient-basic-linux.x64-19.19.0.0.0dbru.el9.zip Extract the contents to a directory, e.g., /opt/oracle/instantclient Step 2: Configure Environment Variables Update your shell profile (e.g., ~/.bashrc) to include the Oracle Instant Client library paths: export LD_LIBRARY_PATH=/opt/oracle/instantclient:$LD_LIBRARY_PATH export PATH=/opt/oracle/instantclient:$PATH Reload the profile: source ~/.bashrc Step 3: Enable Thick Mode in Your Python Script Modify your Python script to initialize the Oracle Client in Thick mode. Example: import oracledb oracledb.init_oracle_client(lib_dir=”/opt/oracle/instantclient”) Run your script in a new session to apply the changes: nohup python your_script.py & Conclusion: The DPY-4011 error, caused by Native Network Encryption requirements, is resolved by enabling Thick mode in python-oracledb and configuring the Oracle Instant Client. By following the steps outlined in this guide, you can ensure reliable and secure connections to your Oracle Database. Proactive monitoring and best practices will further enhance the stability of your database applications.
Read MoreIntroduction: Creating a new Pluggable Database (PDB) in Oracle is a routine task for DBAs. However, errors like ORA-65122: Pluggable database GUID conflicts with the GUID of an existing container can sometimes arise, particularly when using the CREATE PLUGGABLE DATABASE command. In this blog, we’ll explore a real-world scenario where this error occurred, analyze its cause, and provide steps to resolve it effectively. Error: ORA-65122: Pluggable database GUID conflicts with the GUID of an existing container. SQL> create pluggable database TEST2_NEW using ‘/tmp/dba/PROD2_txfr.xml’ nocopy tempfile reuse; create pluggable database TEST2_NEW using ‘/tmp/dba/PROD2_txfr.xml’ nocopy tempfile reuse * ERROR at line 1: ORA-65122: Pluggable database GUID conflicts with the GUID of an existing container. Cause: The ORA-65122 error occurs when the GUID (Globally Unique Identifier) of the new PDB being created matches the GUID of an existing PDB or container. In this case, the source file (PROD2_txfr.xml) used for creating the PDB contained metadata that resulted in a GUID conflict with an existing container. This issue often arises when using the USING clause with XML metadata generated from an existing database or when a PDB is being recreated from a source that retains its original GUID. Solution: To resolve this, the AS CLONE clause was added to the creation command. This clause instructs Oracle to treat the new PDB as a clone of the source, generating a unique GUID to avoid conflicts. The modified command was: SQL> create pluggable database TEST2_NEW as clone using ‘/tmp/dba/PROD2_txfr.xml’ nocopy tempfile reuse; Pluggable database created. SQL> sho pdbs; CON_ID CON_NAME OPEN MODE RESTRICTED 2 PDB$SEED READ ONLY NO 3 TEST2_NEW MOUNTED SQL> Conclusion: Errors like ORA-65122 can interrupt routine DBA operations, but understanding their root cause and using features like the AS CLONE clause can provide an efficient resolution. This scenario highlights the importance of careful planning and testing during PDB creation to ensure a smooth process. By adopting the best practices outlined above, you can avoid similar issues and enhance database operations in your Oracle environment.
Read MoreIntroduction: This blog explains about Policy Based Routing. What is a Policy Based Routing? In general, a layer 3 device takes routing decision based on the route look…
Read MoreVIRTUAL SWITCHING SYSTEM Introduction: This blog explains Virtual Switching System (VSS). What is a Virtual Switching System (VSS)? In general network switches were used as standalone device.…
Read MoreSQL server MAX server memory configuration Introduction:- This document addresses SQL Server memory issues, including errors in resource pools internal and default, which impact query execution and system performance. It provides…
Read MoreSQL Server Database not accessible suspect mode. Introduction:- This document provides a concise guide for troubleshooting and resolving SQL Server databases in suspect mode, which prevents user access. It outlines…
Read More