My Oracle Support Banner

ORA-00904: TABLE_SCHEMA : INVALID IDENTIFIER - Under DBA-Export Jobs (Doc ID 2307453.1)

Last updated on MAY 30, 2023

Applies to:

Oracle SQL Developer - Version 17.2 to 17.3
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

DBA Functions (like User Mgmt)

SQL Developer v17.2 refers to an incorrect column while trying to display Export DATAPUMP job status in DBA menu tree.

The following error is being displayed:

CHECKING PRIMARY TABLE
  
Error starting at line : 13 in command -
DECLARE
  mycount NUMBER:=0;
  JOB_STATE varchar2(1000):='&&job_state';
BEGIN
  :UTL_ERROR :=NULL;
  SELECT COUNT(*)
  INTO mycount
  FROM Dba_tab_privs
  WHERE table_name ='UTL_FILE'
  AND privilege ='EXECUTE'
  AND table_schema ='SYS';
  IF (mycount =0) THEN
  raise NO_DATA_FOUND;
  END IF;
  IF ((JOB_STATE IS NULL) OR (JOB_STATE!='NOT RUNNING')) THEN
  :UTL_ERROR:='STATE IS NOT ''NOT RUNNING''';
  END IF;
EXCEPTION
WHEN no_data_found THEN
  :UTL_ERROR:='NO EXECUTE ON SYS.UTL_FILE';
END;
Error report -
ORA-06550: line 11, column 7:
PL/SQL: ORA-00904: "TABLE_SCHEMA": invalid identifier
ORA-06550: line 6, column 3:
PL/SQL: SQL Statement ignored
06550. 00000 - "line %s, column %s:\n%s"
*Cause: Usually a PL/SQL compilation error.
*Action:




Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.