Monthly Archives: January 2025

Query to get Shipping and Inventory Material Transactions in fusion.

SELECT dha.source_order_number, dha.order_number, dfla.status_code, dfla.source_line_number   FROM  fusion.doo_headers_all dha, fusion.doo_fulfill_lines_all dfla, fusion.wsh_delivery_assignments wda, fusion.wsh_new_deliveries wnd, fusion.wsh_delivery_details wdd, fusion.inv_material_txns imt  WHERE dha.header_id=dfla.header_id    AND dfla.fulfill_line_id=wdd.source_shipment_id    AND wdd.delivery_detail_id=wda.delivery_detail_id    AND wda.delivery_id=wnd.delivery_id(+)…

Read More

Query to get Inventory on hand quantity details in fusion.

SELECT esi.inventory_item_id, esi.item_number, esi.organization_id, inv.organization_code, esi.enabled_flag, esi.end_date_active, ohq.transaction_quantity onhand_qty   FROM fusion.egp_system_items_b esi, fusion.inv_org_parameters inv, fusion.inv_onhand_quantities_detail ohq  WHERE  inv.organization_id=esi.organization_id    AND inv.organization_id=ohq.organization_id    AND esi.inventory_item_id=ohq.inventory_item_id

Read More

File Share Witness server Offline Issue in SQL Server.

1. Introduction This document provides a detailed investigation and resolution report for the File Share Witness server issue observed in the failover cluster for the server TEST. It outlines the findings, steps…

Read More

Queue enable issue in SQL Server

Introduction This document provides a detailed procedure for diagnosing and resolving the issue of a SQL Server queue that automatically disables itself after being re-enabled. This behavior is often caused…

Read More

DBCC CHECKDB Command in SQL Server

Introduction  The DBCC CHECKDB command is an essential tool in SQL Server for ensuring the physical and logical integrity of databases. It helps detect any corruption in the database structure,…

Read More

SQL Server Query/Job Timeout Expired troubleshooting

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 More

Steps to move SQL Server database files

Introduction 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 More

Steps to Blackouts the alerts in Foglight

Introduction 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 More

Splitting shipping lines

Introduction: 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 More

Resolving DPY-4011: The Database or Network Closed the Connection

Introduction : 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 More