When Oracle writes a trigger, an error is reported during execution, and the error prompt information is shown in the figure above. Similar trigger statements generally have syntax errors. Re audit the statement and execute it again
If you are using PL/SQL developer, you can check the triggers in the object bar under the current user to find the newly written trigger. If there is an error, there is a small red X in the icon in front of the corresponding trigger name
Similar Posts:
- How to Solve Oracle ORA-09925 error: Unable to create audit trail file
- The applet reports an error thirdscripterror DateValue is not defined;
- MYSQL Developer Error:Unable to find a Java Virtual Machine
- SQL Developer:Unable to find a Java Virtual Machine [Solved]
- [Solved] Redis MISCONF ERROR: Redis is configured to save RDB snapshots
- The command / usr / bin / xdpyinfo cannot be used to automatically check the display color
- WPF TextBox Placeholder
- mysql 1142 – SELECT command denied to user ‘root_ssm’@’localhost’ for table …
- On the initialization of dynamically generated elements by select2
- How to SolveRedis adding hash Error