- Remove oracle specific attribute implicit_release as

  suggested in semantic conventions review for now.

Author: sudarshan12s

plugins/node/opentelemetry-instrumentation-oracledb/src/OracleTelemetryTraceHandler.ts

@@ -45,7 +45,6 @@ type TraceHandlerBaseCtor = new () => any;
 const OUT_BIND = 3003; // bindinfo direction value.
 
 // Local modules.
-import { AttributeNames } from './constants';
 import { OracleInstrumentationConfig, SpanConnectionConfig } from './types';
 import { TraceSpanData, SpanCallLevelConfig } from './internal-types';
 import { SpanNames, DB_SYSTEM_VALUE_ORACLE } from './constants';
@@ -329,12 +328,6 @@ export function getOracleTelemetryTraceHandlerClass(
             roundTrip
           );
         }
-        if (traceContext.additionalConfig.implicitRelease) {
-          span.setAttribute(
-            AttributeNames.ORACLE_IMPLICIT_RELEASE,
-            traceContext.additionalConfig.implicitRelease
-          );
-        }
         if (traceContext.error) {
           span.recordException(traceContext.error);
           span.setStatus({

plugins/node/opentelemetry-instrumentation-oracledb/src/constants.ts

@@ -16,12 +16,6 @@
  * Copyright (c) 2025, Oracle and/or its affiliates.
  * */
 
-// Oracle specific attributes not covered by standard semantic conventions.
-// See: https://github.com/open-telemetry/semantic-conventions/pull/1911
-export enum AttributeNames {
-  ORACLE_IMPLICIT_RELEASE = 'oracle.db.implicit_release',
-}
-
 // Contains span names produced by instrumentation
 // It lists the RPC names (suffix with _MSG like EXECUTE_MSG) and
 // exported oracledb functions (like EXECUTE).