Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page

Show all

DBE_PLDEVELOPER.gs_errors

Updated on 2024-05-07 GMT+08:00

Records errors that occur during PL/SQL object (stored procedure, function, package, and package body) compilation. For details, see the following column description.

After the plsql_show_all_error parameter is enabled, if an error occurs during compilation, the error is skipped and the compilation continues, and the error information is recorded in gs_errors. If the plsql_show_all_error parameter is disabled, and the value of behavior_compat_options is not skip_insert_gs_source, then an error is reported and related information is inserted into this table.

The owner of the table is the user who creates the table. Modifying the owner of the stored procedure or package does not modify the table information.

Table 1 DBE_PLDEVELOPER.gs_errors columns

Name

Type

Description

id

oid

Object ID.

owner

bigint

ID of the user who creates the object.

nspid

oid

Schema ID of an object.

name

name

Object name.

type

text

Object type (procedure/function/package/package body).

line

integer

Line number.

src

text

Error message.

CAUTION:
  1. If errors occur before AS/IS and after END when a packet header is created, the errors are not recorded in the gs_errors table. Instead, the error row numbers and content are directly returned on the client. The returned row numbers may be inaccurate. Some IS and END errors are not recorded in the gs_errors table.
  2. If errors occur before AS/IS and after END when a packet body is created, the errors are not recorded in the gs_errors table. Instead, the error row numbers and content are directly returned on the client. The returned row numbers may be inaccurate. Some IS and END errors are not recorded in the gs_errors table.
  3. If errors occur at the end of functions or stored procedures (after END) when a packet body is created, the errors are not recorded in the gs_errors table. Instead, the error row numbers and content are directly returned on the client. The row numbers may be inaccurate.
  4. If errors occur at the beginning of functions or stored procedures (before AS/IS) when a packet body is created, the error row numbers are incorrect.
  5. If a semicolon (;) is missing in the variable declaration when a packet header is created, the error is recorded in the gs_errors table but the row number is incorrect. If the parameter is enabled, the error is not recorded.
  6. In a stored procedure or function in the package body, the error declared by the autonomous transaction identifier PRAGMA AUTOMOUS_TRANSACTION may not be recorded in the gs_errors table.
  7. The client directly reports an error, but the gs_errors table does not record the error. If the row number reported by the client is incorrect, this requirement does not correct the row number.
  8. For an error in the middle of statements such as IF....THEN, FOR....LOOP, and WHEN.... THEN, or an EXCEPTION error, the error row number is in the current row instead of the row where the next semicolon is located.
  9. When the BEGIN in the stored procedure or function in the package is incorrect, the error row number is incorrect.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback