I have a trigger which updates the entries of another table while inserting one table. It is basically copy some of data to another table. I compiled is on toad and it worked successfully but when i try to insert a new values to table by using my web application entity framework throws an exception :
SQL Error: ORA-04098: trigger 'ExampleTrigger' is invalid and failed re-validation;
What should i do? I disabled the trigger and also droped it, tried again nothing is changed. Same error in related trigger.
Related
I have a problem deleting a workspace in APEX 19.2. From the graphical interface or from SQL, it returns this error:
Error removing workspace.
ORA-04091: table APEX_190200.WWV_FLOW_FEEDBACK is mutating, trigger/function may not see it ORA-06512: at "APEX_190200.WWV_FLOW_ISSUES_AD", line 2 ORA-04088: error during execution of trigger 'APEX_190200.WWV_FLOW_ISSUES_AD'
The PL / SQL code:
BEGIN
APEX_INSTANCE_ADMIN.REMOVE_WORKSPACE('DOGO_PRO','N','N');
END;
The workspace I am trying to delete is called "DOG_PRO", in the APEX interface, it stays in this state:
enter image description here
enter image description here
How can I delete the workspace?
I have created new workspaces and they are removed without problems but this workspace gives me that error.
I had the exact same error today with APEX 19.2.
I got it working by disabling the trigger WWV_FLOW_ISSUES_AD on the table APEX_190200.WWV_FLOW_ISSUES_AD as user SYS. Then I was able to delete the workspace and re-enabled the trigger.
As I don't use the Feedback Option in APEX the table APEX_190200.WWV_FLOW_FEEDBACK is empty and the trigger doesn't need to update any rows.
To disable the trigger use the following command:
alter trigger APEX_190200.WWV_FLOW_ISSUES_AD disable;
Now you should be able to delete the workspace in Instance Admin or SQL/Plus.
To re-enable the trigger use the following command:
alter trigger APEX_190200.WWV_FLOW_ISSUES_AD enable;
I can create SpatiaLite layers from SpatiaLite tables. However, I would like to create a layer based on a SpatiaLite view. I click on "Configure new Sql View" from the "New Layer" screen. Then I am able to create the sql view. However, after I create the new layer based on a SpatiaLite view, I cannot get queries to run against the SpatiaLite table. If I go into the newly created layer, I click on "Edit sql view", I type in a known working sql for this SpatiaLite db such as:
select * from lines
Then under Attributes, I click on "Refresh" and it shows no fields. Also if I click on "Layer Preview", select the layer and click on GML, I get the following error:
error:java.lang.RuntimeException: java.io.IOException java.lang.RuntimeException: java.io.IOException java.io.IOExceptionjava.sql.SQLException: [SQLITE_ERROR] SQL error or missing database (near "FROM": syntax error) [SQLITE_ERROR] SQL error or missing database (near "FROM": syntax error)
Somehow it is not finding the sqlite table. Any help would be appreciated.
Update #1
I found this in the geoserver.log file:
Could not find mapping for 'GEOMETRY', ignoring the column and setting the feature type read only
I took a look at all the info I found online and it looks to be a limitation of the SpatiaLite provider for GEOSERVER in that it does not allow to create custom SQL views in GEOSERVER.
I've created a form in the APEX and I need to edit a table via dblink, which is already created . So, when I ask to show me a data in this remoute table- it's work fine, but when I'm trying to edit data, I get the error:
"Table or view OPERATION#DBQA not found Contact your application
administrator."
In the SQL workshop>SQL Commands- it also works fine(
update usr.operation#dbqa
set description='admin3' where operation_id=10
)
Well, I've created view usr.operation_qa as select * from usr.operation#dbqa, but, anyway, I receive the same error
"Table or view OPERATION_QA not found Contact your application
administrator."
I'll repeat, a permission and dblink -are ok, couse it's worl in SQL Commands
Will be appreciate for any help or comments. Thanks!
I referred
http://docs.broadleafcommerce.org/core/current/getting-started
to get started with broadleaf commerce. While everything is good with installation, when i run the application as mentioned i get 2 errors. They are as below:
Database creation error: This error comes while starting jetty server.
SchemaExport - HHH000389: Unsuccessful: alter table
BLC_TRANS_ADDITNL_FIELDS drop constraint FK376DDE4B9E955B1D
SchemaExport - user lacks privilege or object not found:
PUBLIC.BLC_TRANS_ADDITNL_FIELDS
Static resoure mapping error: This error comes while i load any page which has image on it. Below are the details.
StaticAssetViewController - Unable to retrieve static asset Failed to
delete original file
'C:\user\AppData\Local\Temp\30\95\Hoppin-Hot-Sauce-Bottle---d41d8cd98f00b204e9800998ecf8427e.jpg'
after copy to
'C:\user\AppData\Local\Temp\img\sauces\Hoppin-Hot-Sauce-Bottle---d41d8cd98f00b204e9800998ecf8427e.jpg'
Note: StaticAssetView issue was resolved in BLC 3.2.
The database error shouldn't be an issue. When the app starts it first tries to clean the DB by dropping everything. If the tables or constraints don't exist you get this error and that is fine, later on in the start up sequence it will create all these DB objects.
I'm at my wits' end with this error.
I have a view which uses a function contained in a package in another schema. I've created a synonym to said package, and on my local dev DB, the view compiles correctly. On the build server, the view gives compilation errors.
When I run the select of the view manually, Oracle throws an ORA-00904 error on the synonym in the query. I just can't understand why it works in one place and not the other. The code on both servers is identical, as it's coming from our source control repository.
As phlogratos suggested, it was a privileges issue. As the user didn't have execute permissions on the package in the separate schema, it was causing this error.
The underlying problem was an issue with our script that applies grants, but it's good to know that references like this without permissions fail in this manner.